Network Working Group K. Morneault
Request for Comments: 3331 Cisco Systems
Category: Standards Track R. Dantu
NetRake
G. Sidebottom
Signatus Technologies
B. Bidulock
OpenSS7
J. Heitz
Lucent
September 2002
Network Working Group K. Morneault
Request for Comments: 3331 Cisco Systems
Category: Standards Track R. Dantu
NetRake
G. Sidebottom
Signatus Technologies
B. Bidulock
OpenSS7
J. Heitz
Lucent
September 2002
Signaling System 7 (SS7) Message Transfer Part 2 (MTP2) - User Adaptation Layer
信令系统7（SS7）消息传输第2部分（MTP2）-用户适配层
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 defines a protocol for the backhauling of Signaling System 7 Message Transfer Part 2 (SS7 MTP2) User signalling messages over IP using the Stream Control Transmission Protocol (SCTP). This protocol would be used between a Signalling Gateway (SG) and Media Gateway Controller (MGC). It is assumed that the SG receives SS7 signalling over a standard SS7 interface using the SS7 Message Transfer Part (MTP) to provide transport. The Signalling Gateway would act as a Signalling Link Terminal.
本文件定义了使用流控制传输协议（SCTP）通过IP回传信令系统7消息传输第2部分（SS7 MTP2）用户信令消息的协议。该协议将在信令网关（SG）和媒体网关控制器（MGC）之间使用。假设SG使用SS7消息传输部分（MTP）通过标准SS7接口接收SS7信令以提供传输。信令网关将充当信令链路终端。
Table of Contents
目录
1. Introduction.............................................. 2
1.1 Scope.................................................. 3
1.2 Terminology............................................ 3
1.3 M2UA Overview.......................................... 5
1.4 Services Provided by the M2UA Adaptation Layer......... 7
1.5 Functions Provided by the M2UA Layer................... 9
1.6 Definition of the M2UA Boundaries..................... 12
2. Conventions.............................................. 16
3. Protocol Elements........................................ 16
3.1 Common Message Header................................. 16
3.2 M2UA Message Header................................... 22
3.3 M2UA Messages......................................... 23
4. Procedures............................................... 58
4.1 Procedures to Support the M2UA-User Layer............. 58
4.2 Receipt of Primitives from the Layer Management....... 59
4.3 AS and ASP State Maintenance.......................... 61
4.4 Link Key Management Procedures........................ 73
5. Examples of MTP2 User Adaptation (M2UA) Procedures....... 75
5.1 Establishment of associations between SGP and MGC..... 75
examples
5.2 ASP Traffic Fail-over Examples........................ 77
5.3 SGP to MGC, MTP Level 2 to MTP Level 3 Boundary
Procedures............................................ 78
6. Timer Values............................................. 85
7. Security Considerations.................................. 85
7.1 Threats................................................ 85
7.2 Protecting Confidentiality............................. 86
8. IANA Considerations...................................... 86
8.1 SCTP Payload Protocol Identifier....................... 86
8.2 M2UA Protocol Extensions............................... 86
9. Acknowledgements......................................... 87
10. References............................................... 88
Appendix A: Signalling Network Architecture.................. 90
Authors' Addresses........................................... 92
Full Copyright Statement..................................... 94
1. Introduction.............................................. 2
1.1 Scope.................................................. 3
1.2 Terminology............................................ 3
1.3 M2UA Overview.......................................... 5
1.4 Services Provided by the M2UA Adaptation Layer......... 7
1.5 Functions Provided by the M2UA Layer................... 9
1.6 Definition of the M2UA Boundaries..................... 12
2. Conventions.............................................. 16
3. Protocol Elements........................................ 16
3.1 Common Message Header................................. 16
3.2 M2UA Message Header................................... 22
3.3 M2UA Messages......................................... 23
4. Procedures............................................... 58
4.1 Procedures to Support the M2UA-User Layer............. 58
4.2 Receipt of Primitives from the Layer Management....... 59
4.3 AS and ASP State Maintenance.......................... 61
4.4 Link Key Management Procedures........................ 73
5. Examples of MTP2 User Adaptation (M2UA) Procedures....... 75
5.1 Establishment of associations between SGP and MGC..... 75
examples
5.2 ASP Traffic Fail-over Examples........................ 77
5.3 SGP to MGC, MTP Level 2 to MTP Level 3 Boundary
Procedures............................................ 78
6. Timer Values............................................. 85
7. Security Considerations.................................. 85
7.1 Threats................................................ 85
7.2 Protecting Confidentiality............................. 86
8. IANA Considerations...................................... 86
8.1 SCTP Payload Protocol Identifier....................... 86
8.2 M2UA Protocol Extensions............................... 86
9. Acknowledgements......................................... 87
10. References............................................... 88
Appendix A: Signalling Network Architecture.................. 90
Authors' Addresses........................................... 92
Full Copyright Statement..................................... 94
This document defines a protocol for the backhauling of SS7 [1] MTP2 User [2] [3] [4] (i.e. MTP3) signalling messages over IP using the Stream Control Transmission Protocol (SCTP) [8]. This protocol would be used between a Signalling Gateway (SG) and Media Gateway Controller (MGC).
本文件定义了使用流控制传输协议（SCTP）[8]通过IP回传SS7[1]MTP2用户[2][3][4]（即MTP3）信令消息的协议。该协议将在信令网关（SG）和媒体网关控制器（MGC）之间使用。
There is a need for Switched Circuit Network (SCN) signalling protocol delivery from a Signalling Gateway (SG) to a Media Gateway Controller (MGC) [9]. The delivery mechanism addresses the following objectives:
需要将交换电路网络（SCN）信令协议从信令网关（SG）传送到媒体网关控制器（MGC）[9]。交付机制涉及以下目标：
* Support for MTP Level 2 / MTP Level 3 interface boundary * Support for communication between Layer Management modules on SG and MGC * Support for management of SCTP active associations between the SG and MGC
* 支持MTP 2级/MTP 3级接口边界*支持SG和MGC上的层管理模块之间的通信*支持管理SG和MGC之间的SCTP活动关联
The SG will terminate up to MTP Level 2 and the MGC will terminate MTP Level 3 and above. In other words, the SG will transport MTP Level 3 messages over an IP network to a MGC.
SG将终止至MTP 2级，MGC将终止MTP 3级及以上。换句话说，SG将通过IP网络将MTP级别3消息传输到MGC。
Application Server (AS) - A logical entity serving a specific application instance. An example of an Application Server is a MGC handling the MTP Level 3 and call processing for SS7 links terminated by the Signalling Gateways. Practically speaking, an AS is modeled at the SG as an ordered list of one or more related Application Server Processes (e.g., primary, secondary, tertiary, ...).
应用程序服务器（AS）-为特定应用程序实例提供服务的逻辑实体。应用服务器的一个示例是处理MTP级别3和信令网关终止的SS7链路的呼叫处理的MGC。实际上，在SG处，AS被建模为一个或多个相关应用服务器进程（例如，主、次、三级等）的有序列表。
Application Server Process (ASP) - A process instance of an Application Server. Examples of Application Server Processes are active or standby MGC instances.
应用程序服务器进程（ASP）-应用程序服务器的进程实例。应用服务器进程的示例是活动或备用MGC实例。
Association - An association refers to a SCTP association. The association will provide the transport for the delivery of protocol data units for one or more interfaces.
关联-关联是指SCTP关联。该协会将为一个或多个接口的协议数据单元的交付提供传输。
Backhaul - Refers to the transport of signalling from the point of interface for the associated data stream (i.e., SG function in the MGU) back to the point of call processing (i.e., the MGCU), if this is not local [9].
回程-指从相关数据流接口点（即MGU中的SG功能）到呼叫处理点（即MGCU）的信令传输，如果这不是本地的[9]。
Fail-over - The capability to reroute signalling traffic as required to an alternate Application Server Process within an Application Server in the event of failure or unavailability of a currently used Application Server Process. Fail-back MAY apply upon the return to service of a previously unavailable Application Server Process.
故障转移—在当前使用的应用程序服务器进程出现故障或不可用时，根据需要将信令流量重新路由到应用程序服务器内的备用应用程序服务器进程的能力。故障回复可在以前不可用的应用程序服务器进程恢复服务时应用。
Host - The computing platform that the ASP process is running on.
主机—运行ASP进程的计算平台。
Interface - For the purposes of this document, an interface is a SS7 signalling link.
接口-在本文件中，接口是SS7信令链路。
Interface Identifier - The Interface Identifier identifies the physical interface at the SG for which the signalling messages are sent/received. The format of the Interface Identifier parameter can be text or integer, the values of which are assigned according to network operator policy. The values used are of local significance only, coordinated between the SG and ASP.
接口标识符-接口标识符标识SG上发送/接收信令消息的物理接口。接口标识符参数的格式可以是文本或整数，其值根据网络运营商策略分配。使用的值仅具有局部意义，在SG和ASP之间进行协调。
Layer Management - Layer Management is a nodal function in an SG or ASP that handles the inputs and outputs between the M2UA layer and a local management entity.
层管理-层管理是SG或ASP中的节点功能，用于处理M2UA层和本地管理实体之间的输入和输出。
Link Key - The link key is a locally unique (between ASP and SG) value that identifies a registration request for a particular Signalling Data Link and Signalling Terminal pair.
链路密钥-链路密钥是本地唯一的（ASP和SG之间）值，用于标识特定信令数据链路和信令终端对的注册请求。
MTP - The Message Transfer Part of the SS7 protocol
MTP-SS7协议的消息传输部分
MTP2 - MTP Level 2, the signalling data link layer of SS7
MTP2-MTP级别2，SS7的信令数据链路层
MTP3 - MTP Level 3, the signalling network layer of SS7
MTP3-MTP级别3，SS7的信令网络层
MTP2-User - A protocol that uses the services of MTP Level 2 (i.e. MTP3).
MTP2用户-使用MTP级别2（即MTP3）服务的协议。
Network Byte Order: Most significant byte first, a.k.a Big Endian.
网络字节顺序：最高有效字节优先，也称为大端字节。
Signalling Data Link - An SDL refers to a specific communications facility that connects two Signalling Link Terminals.
信令数据链路-SDL指连接两个信令链路终端的特定通信设施。
Signalling Gateway (SG) - An SG is a signalling agent at the edge of the IP network. An SG appears to the SS7 as one or more Signalling Link Terminals that are connected to one or more Signalling Data Links in the SS7 network. An SG contains a set of one or more unique Signalling Gateway Processes, on which one or more is normally actively processing traffic. Where an SG contains more than one SGP, the SG is a logical entity.
信令网关（SG）-SG是IP网络边缘的信令代理。在SS7看来，SG是连接到SS7网络中的一个或多个信令数据链路的一个或多个信令链路终端。SG包含一组一个或多个唯一的信令网关进程，其中一个或多个信令网关进程通常正在积极处理流量。如果SG包含多个SGP，则SG是一个逻辑实体。
Signalling Gateway Process (SGP) - A process instance that uses M2UA to communicate to and from a Signalling Link Terminal. It serves as an active, backup or load-sharing process of a Signalling Gateway.
信令网关进程（SGP）-使用M2UA与信令链路终端进行通信的进程实例。它用作信令网关的活动、备份或负载共享过程。
Signalling Link Terminal (SLT) - Refers to the means of performing all of the functions defined at MTP level 2 regardless of their implementation [2,3].
信令链路终端（SLT）-指执行MTP 2级定义的所有功能的方式，无论其实现方式如何[2,3]。
Stream - A stream refers to an SCTP stream; a unidirectional logical channel established from one SCTP endpoint to another associated SCTP endpoint, within which all user messages are delivered in-sequence except for those submitted to the unordered delivery service.
流-流指SCTP流；从一个SCTP端点到另一个相关SCTP端点建立的单向逻辑通道，在该通道内，除提交给无序传递服务的用户消息外，所有用户消息都按顺序传递。
The framework architecture that has been defined for SCN signalling transport over IP [9] uses two components: a signalling common transport protocol and an adaptation module to support the services expected by a particular SCN signalling protocol from its underlying protocol layer.
为IP上的SCN信令传输定义的框架架构[9]使用两个组件：信令通用传输协议和适配模块，以支持特定SCN信令协议从其底层协议层预期的服务。
Within this framework architecture, this document defines a SCN adaptation module that is suitable for the transport of SS7 MTP2 User messages. The only SS7 MTP2 User is MTP3. The M2UA uses the services of the Stream Control Transmission Protocol [8] as the underlying reliable signalling common transport protocol.
在此框架架构内，本文档定义了一个SCN适配模块，该模块适用于SS7 MTP2用户消息的传输。唯一的SS7 MTP2用户是MTP3。M2UA使用流控制传输协议[8]的服务作为底层可靠信令公共传输协议。
In a Signalling Gateway, it is expected that the SS7 MTP2-User signalling is transmitted and received from the PSTN over a standard SS7 network interface, using the SS7 Message Transfer Part Level 1 and Level 2 [2,3,4] to provide reliable transport of the MTP3-User signalling messages to and from an SS7 Signalling End Point (SEP) or Signalling Transfer Point (STP). The SG then provides an interworking of transport functions with the IP transport, in order to transfer the MTP2-User signalling messages to and from an Application Server Process where the peer MTP2-User protocol layer exists.
在信令网关中，预计SS7 MTP2用户信令通过标准SS7网络接口从PSTN发送和接收，使用SS7消息传输部分1级和2级[2,3,4]提供MTP3用户信令消息到SS7信令端点（SEP）的可靠传输或信令传输点（STP）。然后，SG提供传输功能与IP传输的互通，以便在存在对等MTP2用户协议层的应用服务器进程之间传输MTP2用户信令消息。
In a Signalling Gateway, it is expected that the SS7 signalling is received over a standard SS7 network termination, using the SS7 Message Transfer Part (MTP) to provide transport of SS7 signalling messages to and from an SS7 Signalling End Point (SEP) or SS7 Signalling Transfer Point (STP). In other words, the SG acts as a Signalling Link Terminal (SLT) [2,3]. The SG then provides an interworking of transport functions with IP Signalling Transport, in order to transport the MTP3 signalling messages to the MGC where the peer MTP3 protocol layer exists, as shown below:
在信令网关中，预期通过标准的SS7网络终端接收SS7信令，使用SS7消息传输部分（MTP）向SS7信令端点（SEP）或SS7信令传输点（STP）提供SS7信令消息的传输。换句话说，SG充当信令链路终端（SLT）[2,3]。然后，SG提供传输功能与IP信令传输的互通，以便将MTP3信令消息传输到存在对等MTP3协议层的MGC，如下所示：
****** SS7 ****** IP *******
*SEP *-----------* SG *-------------* MGC *
****** ****** *******
****** SS7 ****** IP *******
*SEP *-----------* SG *-------------* MGC *
****** ****** *******
+----+ +----+
|S7UP| |S7UP|
+----+ +----+
|MTP + |MTP |
| L3 | (NIF) |L3 |
+----+ +----+----+ +----+
|MTP | |MTP |M2UA| |M2UA|
| | | +----+ +----+
|L2 | |L2 |SCTP| |SCTP|
|L1 | |L1 +----+ +----+
| | | |IP | |IP |
+----+ +---------+ +----+
+----+ +----+
|S7UP| |S7UP|
+----+ +----+
|MTP + |MTP |
| L3 | (NIF) |L3 |
+----+ +----+----+ +----+
|MTP | |MTP |M2UA| |M2UA|
| | | +----+ +----+
|L2 | |L2 |SCTP| |SCTP|
|L1 | |L1 +----+ +----+
| | | |IP | |IP |
+----+ +---------+ +----+
NIF - Nodal Interworking Function SEP - SS7 Signalling Endpoint IP - Internet Protocol SCTP - Stream Control Transmission Protocol (Reference [8])
NIF-节点互通功能SEP-SS7信令端点IP-互联网协议SCTP-流控制传输协议（参考文献[8]）
Figure 1 M2UA in the SG to MGC Application
图1 SG至MGC应用中的M2UA
Note: STPs MAY be present in the SS7 path between the SEP and the SG.
注：SEP和SG之间的SS7路径中可能存在STP。
It is recommended that the M2UA use the services of the Stream Control Transmission Protocol (SCTP) [8] as the underlying reliable common signalling transport protocol. The use of SCTP provides the following features:
建议M2UA使用流控制传输协议（SCTP）[8]的服务作为底层可靠的通用信令传输协议。SCTP的使用提供了以下功能：
- explicit packet-oriented delivery (not stream-oriented) - sequenced delivery of user messages within multiple streams, with an option for order-of-arrival delivery of individual user messages, - optional multiplexing of user messages into SCTP datagrams,
- 显式面向数据包的交付（非面向流）-在多个流中按顺序交付用户消息，可选择单个用户消息的到达顺序交付，-可选择将用户消息多路复用为SCTP数据报，
- network-level fault tolerance through the support of multi-homing at either or both ends of an association, - resistance to flooding and masquerade attacks, and - data segmentation to conform to discovered path MTU size
- 通过在关联的一端或两端支持多主、抵抗泛洪攻击和伪装攻击，以及数据分割以符合发现的路径MTU大小，实现网络级容错
There are scenarios without redundancy requirements and scenarios in which redundancy is supported below the transport layer. In these cases, the SCTP functions above MAY NOT be a requirement and TCP can be used as the underlying common transport protocol.
有些场景没有冗余要求，有些场景在传输层下支持冗余。在这些情况下，上述SCTP功能可能不是必需的，TCP可以用作底层公共传输协议。
The M2UA layer supports ASP fail-over functions in order to support a high availability of call and transaction processing capability. All MTP2-User messages incoming to a SGP from the SS7 network are assigned to the unique Application Server, based on the Interface Identifier of the message.
M2UA层支持ASP故障转移功能，以支持呼叫和事务处理能力的高可用性。根据消息的接口标识符，从SS7网络传入SGP的所有MTP2用户消息都分配给唯一的应用程序服务器。
The M2UA layer supports a n+k redundancy model (active-standby, load sharing, broadcast) where n is the minimum number of redundant ASPs required to handle traffic and k ASPs are available to take over for a failed or unavailable ASP. Note that 1+1 active/standby redundancy is a subset of this model. A simplex 1+0 model is also supported as a subset, with no ASP redundancy.
M2UA层支持n+k冗余模型（主动备用、负载共享、广播），其中n是处理流量所需的最小冗余ASP数量，k个ASP可用于接管故障或不可用的ASP。请注意，1+1主动/备用冗余是该模型的一个子集。simplex 1+0模型也支持作为子集，没有ASP冗余。
It is recommended that the SGP and ASP be able to support both client and server operation. The peer endpoints using M2UA SHOULD be configured so that one always takes on the role of client and the other the role of server for initiating SCTP associations. The default orientation would be for the SGP to take on the role of server while the ASP is the client. In this case, ASPs SHOULD initiate the SCTP association to the SGP.
建议SGP和ASP能够同时支持客户端和服务器操作。应配置使用M2UA的对等端点，以便其中一个始终扮演客户端角色，另一个始终扮演服务器角色，以启动SCTP关联。默认方向是SGP承担服务器角色，而ASP是客户端。在这种情况下，ASP应启动与SGP的SCTP关联。
The SCTP and TCP Registered User Port Number Assignment for M2UA is 2904.
M2UA的SCTP和TCP注册用户端口号分配为2904。
The SS7 MTP3/MTP2(MTP2-User) interface is retained at the termination point in the IP network, so that the M2UA protocol layer is required to provide the equivalent set of services to its users as provided by the MTP Level 2 to MTP Level 3.
SS7 MTP3/MTP2（MTP2用户）接口保留在IP网络的终端点，因此要求M2UA协议层向其用户提供MTP级别2至MTP级别3提供的等效服务集。
M2UA supports a MTP Level 2 / MTP Level 3 interface boundary that enables a seamless, or as seamless as possible, operation of the MTP2-User peers in the SS7 and IP domains. An example of the primitives that need to be supported can be found in [10].
M2UA支持MTP 2级/MTP 3级接口边界，支持SS7和IP域中MTP2用户对等点的无缝或尽可能无缝的操作。需要支持的原语示例见[10]。
1.4.2 Support for communication between Layer Management modules on SG and MGC
1.4.2 支持SG和MGC上的层管理模块之间的通信
The M2UA layer needs to provide some messages that will facilitate communication between Layer Management modules on the SG and MGC. To facilitate reporting of errors that arise because of the backhauling MTP Level 3 scenario, the following primitive is defined:
M2UA层需要提供一些消息，以促进SG和MGC上的层管理模块之间的通信。为了便于报告由于回程MTP 3级方案而产生的错误，定义了以下原语：
M-ERROR
M误差
The M-ERROR message is used to indicate an error with a received M2UA message (e.g., an interface identifier value is not known to the SG).
M错误消息用于指示接收到的M2UA消息的错误（例如，SG不知道接口标识符值）。
The M2UA layer on the SG keeps the state of the configured ASPs. A set of primitives between M2UA layer and the Layer Management are defined below to help the Layer Management manage the association(s) between the SG and the MGC. The M2UA layer can be instructed by the Layer Management to establish a SCTP association to a peer M2UA node. This procedure can be achieved using the M-SCTP ESTABLISH primitive.
SG上的M2UA层保持已配置ASP的状态。下面定义了M2UA层和层管理之间的一组原语，以帮助层管理管理SG和MGC之间的关联。层管理可以指示M2UA层建立与对等M2UA节点的SCTP关联。此过程可使用M-SCTP建立原语实现。
M-SCTP_ESTABLISH
M-SCTP_建立
The M-SCTP_ESTABLISH primitive is used to request, indicate and confirm the establishment of a SCTP association to a peer M2UA node.
M-SCTP_建立原语用于请求、指示和确认建立与对等M2UA节点的SCTP关联。
M-SCTP_RELEASE
M-SCTP_释放
The M-SCTP_RELEASE primitives are used to request, indicate, and confirm the release of a SCTP association to a peer M2UA node.
M-SCTP_释放原语用于请求、指示和确认向对等M2UA节点释放SCTP关联。
The M2UA layer MAY also need to inform the status of the SCTP association(s) to the Layer Management. This can be achieved using the following primitive.
M2UA层可能还需要将SCTP关联的状态通知管理层。这可以使用以下原语实现。
M-SCTP_STATUS
M-SCTP_状态
The M-SCTP_STATUS primitive is used to request and indicate the status of underlying SCTP association(s).
M-SCTP_状态原语用于请求和指示底层SCTP关联的状态。
The Layer Management MAY need to inform the M2UA layer of an AS/ASP status (i.e., failure, active, etc.), so that messages can be exchanged between M2UA layer peers to stop traffic to the local M2UA user. This can be achieved using the following primitive.
层管理可能需要通知M2UA层AS/ASP状态（即，故障、活动等），以便可以在M2UA层对等方之间交换消息以停止到本地M2UA用户的通信。这可以使用以下原语实现。
M-ASP_STATUS
M-ASP\U状态
The ASP status is stored inside the M2UA layer on both the SG and MGC sides. The M-ASP_STATUS primitive can be used by Layer Management to request the status of the Application Server Process from the M2UA layer. This primitive can also be used to indicate the status of the Application Server Process.
ASP状态存储在SG和MGC侧的M2UA层内。层管理可以使用M-ASP_状态原语从M2UA层请求应用程序服务器进程的状态。此原语还可用于指示应用程序服务器进程的状态。
M-ASP_MODIFY
M-ASP_修改
The M-ASP_MODIFY primitive can be used by Layer Management to modify the status of the Application Server Process. In other words, the Layer Management on the ASP side uses this primitive to initiate the ASPM procedures.
层管理可以使用M-ASP_MODIFY原语修改应用程序服务器进程的状态。换句话说，ASP端的层管理使用此原语来启动ASPM过程。
M-AS_STATUS
M-AS_状态
The M-AS_STATUS primitive can be used by Layer Management to request the status of the Application Server. This primitive can also be used to indicate the status of the Application Server.
层管理可以使用M-AS_STATUS原语请求应用程序服务器的状态。此原语还可用于指示应用程序服务器的状态。
The M2UA layer MUST maintain a map of an Interface ID to a physical interface on the Signalling Gateway. A physical interface would be a V.35 line, T1 line/time slot, E1 line/time slot, etc. The M2UA layer MUST also maintain a map of the Interface Identifier to SCTP association and to the related stream within the association.
M2UA层必须在信令网关上维护接口ID到物理接口的映射。物理接口将是V.35线、T1线/时隙、E1线/时隙等。M2UA层还必须维护接口标识符到SCTP关联和关联内相关流的映射。
The SGP maps an Interface Identifier to an SCTP association/stream only when an ASP sends an ASP Active message for a particular Interface Identifier. It must be noted, however, that this mapping is dynamic and could change at any time due to a change of ASP state. This mapping could even temporarily be invalid, for example during fail-over of one ASP to another. Therefore, the SGP MUST maintain the states of AS/ASP and reference them during the routing of any messages to an AS/ASP.
只有当ASP发送特定接口标识符的ASP活动消息时，SGP才会将接口标识符映射到SCTP关联/流。但是，必须注意的是，此映射是动态的，并且可能由于ASP状态的更改而随时更改。这种映射甚至可能暂时无效，例如在一个ASP到另一个ASP的故障转移期间。因此，SGP必须维护AS/ASP的状态，并在将任何消息路由到AS/ASP期间引用它们。
Note that only one SGP SHOULD provide Signalling Link Terminal services to an SS7 link. Therefore, within an SG, an Application Server SHOULD be active for only one SGP at any given point in time.
请注意，只有一个SGP应向SS7链路提供信令链路终端服务。因此，在一个SG中，在任何给定的时间点，一个应用服务器应该只对一个SGP处于活动状态。
An example of the logical view of the relationship between an SS7 link, Interface Identifier, AS and ASP in an SGP is shown below:
SGP中SS7链路、接口标识符AS和ASP之间关系的逻辑视图示例如下所示：
/-------------------------------------------------+
/ /----------------------------------------------|--+
/ / v |
/ / +----+ act+-----+ +-------+ -+--+|-+-
SS7 link1-------->|IID |-+ +-->| ASP |-->| Assoc | v
/ +----+ | +----+ | +-----+ +-------+ -+--+--+-
/ +->| AS |--+ Streams
/ +----+ | +----+ stb+-----+
SS7 link2-------->|IID |-+ | ASP |
+----+ +-----+
/-------------------------------------------------+
/ /----------------------------------------------|--+
/ / v |
/ / +----+ act+-----+ +-------+ -+--+|-+-
SS7 link1-------->|IID |-+ +-->| ASP |-->| Assoc | v
/ +----+ | +----+ | +-----+ +-------+ -+--+--+-
/ +->| AS |--+ Streams
/ +----+ | +----+ stb+-----+
SS7 link2-------->|IID |-+ | ASP |
+----+ +-----+
where IID = Interface Identifier
其中IID=接口标识符
A SGP MAY support more than one AS. An AS MAY support more than one Interface Identifier.
SGP可以支持多个AS。AS可以支持多个接口标识符。
1.5.2 Support for the management of SCTP associations between the SGPs and ASPs
1.5.2 支持SGP和ASP之间SCTP关联的管理
The M2UA layer at the SG maintains the availability state of all configured ASPs, in order to manage the SCTP associations and the traffic between the SG and ASPs. As well, the active/inactive state of remote ASP(s) are also maintained. The Active ASP(s) are the one(s) currently receiving traffic from the SG.
SG处的M2UA层维护所有配置的ASP的可用性状态，以便管理SCTP关联以及SG和ASP之间的流量。此外，还将维护远程ASP的活动/非活动状态。活动ASP是当前从SG接收流量的ASP。
The M2UA layer MAY be instructed by local management to establish an SCTP association to a peer M2UA node. This can be achieved using the M-SCTP_ESTABLISH primitive to request, indicate and confirm the establishment of an SCTP association with a peer M2UA node.
本地管理层可以指示M2UA层建立与对等M2UA节点的SCTP关联。这可以使用M-SCTP\u-build原语来请求、指示和确认与对等M2UA节点建立SCTP关联。
The M2UA layer MAY also need to inform local management of the status of the underlying SCTP associations using the M-SCTP_STATUS request and the indication primitive. For example, the M2UA MAY inform local management of the reason for the release of an SCTP association, determined either locally within the M2UA layer or by a primitive from the SCTP.
M2UA层可能还需要使用M-SCTP_状态请求和指示原语通知本地管理层底层SCTP关联的状态。例如，M2UA可以通知本地管理层释放SCTP关联的原因，该关联可以在M2UA层内本地确定，也可以由来自SCTP的原语确定。
Also the M2UA layer may need to inform the local management of the change in status of an ASP or AS. This may be achieved using the M-ASP STATUS request or M-AS_STATUS request primitives.
此外，M2UA层可能需要通知本地管理层ASP或AS状态的变化。这可以通过使用M-ASP状态请求或M-AS_状态请求原语来实现。
The M2UA layer on the SG MUST maintain the state of the ASPs it is supporting. The state of an ASP changes because of the reception of peer-to-peer messages (ASPM messages as described in Section 3.3.2) or the reception of indications from the local SCTP association. The ASP state transition procedures are described in Section 4.3.1.
SG上的M2UA层必须保持其支持的ASP的状态。由于接收到对等消息（如第3.3.2节所述的ASPM消息）或接收到来自本地SCTP协会的指示，ASP的状态会发生变化。第4.3.1节描述了ASP状态转换程序。
At a SGP, an Application Server list MAY contain active and inactive ASPs to support ASP fail-over procedures. When, for example, both a primary and a backup ASP are available, the M2UA peer protocol is required to control which ASP is currently active. The ordered list of ASPs within a logical Application Server is kept updated in the SGP to reflect the active Application Server Process.
在SGP中，应用程序服务器列表可能包含活动和非活动的ASP，以支持ASP故障转移过程。例如，当主ASP和备份ASP都可用时，需要M2UA对等协议来控制哪个ASP当前处于活动状态。逻辑应用程序服务器中的ASP有序列表在SGP中保持更新，以反映活动的应用程序服务器进程。
Also the M2UA layer MAY need to inform the local management of the change in status of an ASP or AS. This can be achieved using the M-ASP_STATUS or M-AS_STATUS primitives.
此外，M2UA层可能需要通知本地管理层ASP或AS状态的变化。这可以通过使用M-ASP_状态或M-AS_状态原语来实现。
SCTP allows a user specified number of streams to be opened during initialization of the association. It is the responsibility of the M2UA layer to ensure proper management of these streams. Because of the unidirectional nature of streams, a M2UA layer is not aware of the stream information from its peer M2UA layer. For this reason, the Interface Identifier is in the M2UA message header.
SCTP允许在关联初始化期间打开用户指定数量的流。M2UA层负责确保这些流的正确管理。由于流的单向性，M2UA层不知道来自其对等M2UA层的流信息。因此，接口标识符位于M2UA消息头中。
The use of SCTP streams within M2UA is recommended in order to minimize transmission and buffering delay, thereby, improving the overall performance and reliability of the signalling elements. A separate SCTP stream can be used for each SS7 link. Or, an implementation may choose to split the SS7 link across several streams based on SLS. This method may be of particular interest for high speed SS7 links (MTP3b) since high speed links have a 24-bit sequence number and the stream sequence number is 16-bits.
建议在M2UA中使用SCTP流，以最小化传输和缓冲延迟，从而提高信令元件的整体性能和可靠性。每个SS7链路都可以使用单独的SCTP流。或者，实现可以选择基于SLS在多个流之间分割SS7链路。由于高速链路具有24位序列号且流序列号为16位，因此该方法可能对高速SS7链路（MTP3b）特别感兴趣。
SCTP Stream '0' SHOULD NOT be used for MTP2 User Adaptation (MAUP) messages (see Section 3) since stream '0' SHOULD only be used for ASP Management (ASPM) messages (see Section 4.3.3).
SCTP流“0”不应用于MTP2用户自适应（MAUP）消息（请参阅第3节），因为流“0”应仅用于ASP管理（ASPM）消息（请参阅第4.3.3节）。
The M2UA layer on the SGP SHOULD pass an indication of unavailability of the M2UA-User (MTP3) to the local Layer Management, if the currently active ASP moves from the ACTIVE state. The actions taken by M2UA on the SGP with regards to MTP Level 2 should be in accordance with the appropriate MTP specifications.
如果当前活动的ASP从活动状态移动，则SGP上的M2UA层应将M2UA用户（MTP3）不可用的指示传递给本地层管理。M2UA对SGP采取的与MTP 2级相关的行动应符合适当的MTP规范。
It is possible for the M2UA layer to be informed of the IP network congestion onset and abatement by means of an implementation dependent function (i.e. an indication from the SCTP). The handling of this congestion indication by M2UA is implementation dependent. However, the actions taken by the SG should be in accordance with the appropriate MTP specification and should enable SS7 functionality (e.g. flow control) to be correctly maintained.
M2UA层可以通过依赖于实现的功能（即来自SCTP的指示）被告知IP网络拥塞的开始和缓解。M2UA对该拥塞指示的处理取决于实现。但是，SG采取的行动应符合适当的MTP规范，并应能够正确维护SS7功能（如流量控制）。
After a fail-over of one ASP to another ASP, it may be necessary for the M2UA on the ASP to audit the current SS7 link state to ensure consistency. The M2UA on the SGP would respond to the audit request with information regarding the current state of the SS7 link (i.e. in-service, out-of-service, congestion state, LPO/RPO state).
在一个ASP故障切换到另一个ASP后，ASP上的M2UA可能需要审核当前SS7链路状态以确保一致性。SGP上的M2UA将使用有关SS7链路当前状态（即在用、停用、拥塞状态、LPO/RPO状态）的信息响应审计请求。
DATA ESTABLISH RELEASE STATE DATA RETRIEVAL DATA RETRIEVAL COMPLETE
数据建立发布状态数据检索数据检索完成
DATA ESTABLISH RELEASE STATE DATA RETRIEVAL DATA RETRIEVAL COMPLETE
数据建立发布状态数据检索数据检索完成
The upper layer and layer management primitives provided by SCTP are provided in Reference [8] Section 10.
参考文献[8]第10节提供了SCTP提供的上层和层管理原语。
M-SCTP_ESTABLISH request Direction: LM -> M2UA Purpose: LM requests ASP to establish an SCTP association with an SGP.
M-SCTP_建立请求方向：LM->M2UA目的：LM请求ASP与SGP建立SCTP关联。
M-SCTP_ESTABLISH confirm Direction: M2UA -> LM Purpose: ASP confirms to LM that it has established an SCTP association with an SGP.
M-SCTP_建立确认方向：M2UA->LM目的：ASP向LM确认其已与SGP建立SCTP关联。
M-SCTP_ESTABLISH indication Direction: M2UA -> LM Purpose: SGP informs LM that an ASP has established an SCTP association.
M-SCTP_建立指示方向：M2UA->LM目的：SGP通知LM ASP已建立SCTP关联。
M-SCTP_RELEASE request Direction: LM -> M2UA Purpose: LM requests ASP to release an SCTP association with SGP.
M-SCTP_发布请求方向：LM->M2UA目的：LM请求ASP发布与SGP的SCTP关联。
M-SCTP_RELEASE confirm Direction: M2UA -> LM Purpose: ASP confirms to LM that it has released SCTP association with SGP.
M-SCTP_发布确认方向：M2UA->LM目的：ASP向LM确认其已发布与SGP的SCTP关联。
M-SCTP_RELEASE indication Direction: M2UA -> LM Purpose: SGP informs LM that ASP has released an SCTP association.
M-SCTP_释放指示方向：M2UA->LM目的：SGP通知LM ASP已释放SCTP关联。
M-SCTP_RESTART indication Direction: M2UA -> LM Purpose: M2UA informs LM that a SCTP Restart indication has been received.
M-SCTP_重启指示方向：M2UA->LM目的：M2UA通知LM已收到SCTP重启指示。
M-SCTP_STATUS request Direction: LM -> M2UA Purpose: LM requests M2UA to report status of SCTP association.
M-SCTP_状态请求方向：LM->M2UA目的：LM请求M2UA报告SCTP关联状态。
M-SCTP_STATUS indication Direction: M2UA -> LM Purpose: M2UA reports status of SCTP association.
M-SCTP_状态指示方向：M2UA->LM目的：M2UA报告SCTP关联的状态。
M-ASP_STATUS request Direction: LM -> M2UA Purpose: LM requests SGP to report status of remote ASP.
M-ASP_状态请求方向：LM->M2UA目的：LM请求SGP报告远程ASP的状态。
M-ASP_STATUS indication Direction: M2UA -> LM Purpose: SGP reports status of remote ASP.
M-ASP_状态指示方向：M2UA->LM目的：SGP报告远程ASP的状态。
M-AS_STATUS request Direction: LM -> M2UA Purpose: LM requests SG to report status of AS.
M-AS_状态请求方向：LM->M2UA目的：LM请求SG报告AS状态。
M-AS_STATUS indication Direction: M2UA -> LM Purpose: SG reports status of AS.
M-AS_状态指示方向：M2UA->LM目的：SG报告AS状态。
M-NOTIFY indication Direction: M2UA -> LM Purpose: ASP reports that it has received a NOTIFY message from its peer.
M-NOTIFY指示方向：M2UA->LM目的：ASP报告它已收到来自其对等方的NOTIFY消息。
M-ERROR indication Direction: M2UA -> LM Purpose: ASP or SGP reports that it has received an ERROR message from its peer.
M-错误指示方向：M2UA->LM目的：ASP或SGP报告其已收到来自其对等方的错误消息。
M-ASP_UP request Direction: LM -> M2UA Purpose: LM requests ASP to start its operation and send an ASP UP message to the SGP.
M-ASP_UP请求方向：LM->M2UA目的：LM请求ASP启动其操作，并向SGP发送ASP UP消息。
M-ASP_UP confirm Direction: M2UA -> LM Purpose: ASP reports that it has received an ASP UP Acknowledgment message from the SGP.
M-ASP_UP confirm Direction:M2UA->LM Purpose:ASP报告已收到来自SGP的ASP UP确认消息。
M-ASP_DOWN request Direction: LM -> M2UA Purpose: LM requests ASP to stop its operation and send an ASP DOWN message to the SGP.
M-ASP_DOWN请求方向：LM->M2UA目的：LM请求ASP停止其操作，并向SGP发送ASP DOWN消息。
M-ASP_DOWN confirm Direction: M2UA -> LM Purpose: ASP reports that is has received an ASP DOWN Acknowledgment message from the SGP.
M-ASP_向下确认方向：M2UA->LM目的：接收到来自SGP的ASP向下确认消息的ASP报告。
M-ASP_ACTIVE request Direction: LM -> M2UA Purpose: LM requests ASP to send an ASP ACTIVE message to the SGP.
M-ASP_活动请求方向：LM->M2UA目的：LM请求ASP向SGP发送ASP活动消息。
M-ASP_ACTIVE confirm Direction: M2UA -> LM Purpose: ASP reports that is has received an ASP ACTIVE Acknowledgment message from the SGP.
M-ASP_活动确认方向：M2UA->LM目的：收到来自SGP的ASP活动确认消息的ASP报告。
M-ASP_INACTIVE request Direction: LM -> M2UA Purpose: LM requests ASP to send an ASP INACTIVE message to the SGP.
M-ASP_非活动请求方向：LM->M2UA目的：LM请求ASP向SGP发送ASP非活动消息。
M-ASP_INACTIVE confirm Direction: M2UA -> LM Purpose: ASP reports that is has received an ASP INACTIVE Acknowledgment message from the SGP.
M-ASP_非活动确认方向：M2UA->LM目的：接收到来自SGP的ASP非活动确认消息的ASP报告。
M-LINK_KEY_REG Request Direction: LM -> M2UA Purpose: LM requests ASP to register Link Key with SG by sending REG REQ message.
M-LINK_KEY_REG请求方向：LM->M2UA目的：LM通过发送REG REQ消息请求ASP向SG注册链接密钥。
M-LINK_KEY_REG Confirm Direction: M2UA -> LM Purpose: ASP reports to LM that it has successfully received a REG RSP message from SG.
M-LINK_KEY_REG确认方向：M2UA->LM目的：ASP向LM报告其已成功接收到来自SG的REG RSP消息。
M-LINK_KEY_REG Indication Direction: M2UA -> LM Purpose: SG reports to LM that it has successfully processed an incoming REG REQ message from ASP.
M-LINK_KEY_REG指示方向：M2UA->LM目的：SG向LM报告其已成功处理来自ASP的传入REG REQ消息。
M-LINK_KEY_DEREG Request Direction: LM -> M2UA Purpose: LM requests ASP to de-register Link Key with SG by sending DEREG REQ message.
M-LINK_KEY_DEREG请求方向：LM->M2UA目的：LM通过发送DEREG REQ消息请求ASP向SG注销链路密钥。
M-LINK_KEY_DEREG Confirm Direction: M2UA -> LM Purpose: ASP reports to LM that it has successfully received a DEREG RSP message from SG.
M-LINK_KEY_DEREG Confirm Direction:M2UA->LM Purpose:ASP向LM报告其已成功接收到来自SG的DEREG RSP消息。
M-LINK_KEY_DEREG Indication Direction: M2UA -> LM Purpose: SG reports to LM that it has successfully processed an incoming DEREG REQ message from ASP.
M-LINK_KEY_DEREG指示方向：M2UA->LM目的：SG向LM报告其已成功处理来自ASP的传入DEREG REQ消息。
The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, NOT RECOMMENDED, MAY, and OPTIONAL, when they appear in this document, are to be interpreted as described in [RFC2119].
本文件中出现的关键词必须、不得、必需、应、不应、应、不应、推荐、不推荐、可和可选时，应按照[RFC2119]中的说明进行解释。
This section describes the format of various messages used in this protocol.
本节介绍本协议中使用的各种消息的格式。
The protocol messages for MTP2-User Adaptation require a message structure that contains a version, message class, message type, message length, and message contents. This message header is common among all signalling protocol adaptation layers:
MTP2用户自适应的协议消息需要包含版本、消息类、消息类型、消息长度和消息内容的消息结构。此消息头在所有信令协议适配层中是通用的：
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 | Spare | Message Class | Message Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message 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 | Spare | Message Class | Message Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2 Common Message Header
图2公共消息头
All fields in an M2UA message MUST be transmitted in the network byte order, unless otherwise stated.
除非另有说明，M2UA消息中的所有字段必须以网络字节顺序传输。
The version field contains the version of the M2UA adaptation layer. The supported versions are:
版本字段包含M2UA适配层的版本。受支持的版本包括：
Value Version
----- -------
1 Release 1.0
Value Version
----- -------
1 Release 1.0
The Spare field is 8-bits. It SHOULD be set to all '0's by the sender and ignored by the receiver.
备用字段为8位。发送方应将其设置为所有“0”，接收方应将其忽略。
The following List contains the valid Message Classes:
以下列表包含有效的消息类：
Message Class: 8 bits (unsigned integer)
消息类：8位（无符号整数）
0 Management (MGMT) Message [IUA/M2UA/M3UA/SUA]
1 Transfer Messages [M3UA]
2 SS7 Signalling Network Management (SSNM) Messages [M3UA/SUA]
3 ASP State Maintenance (ASPSM) Messages [IUA/M2UA/M3UA/SUA]
4 ASP Traffic Maintenance (ASPTM) Messages [IUA/M2UA/M3UA/SUA]
5 Q.921/Q.931 Boundary Primitives Transport (QPTM)
Messages [IUA]
6 MTP2 User Adaptation (MAUP) Messages [M2UA]
7 Connectionless Messages [SUA]
8 Connection-Oriented Messages [SUA]
9 Routing Key Management (RKM) Messages (M3UA)
10 Interface Identifier Management (IIM) Messages (M2UA)
11 to 127 Reserved by the IETF
128 to 255 Reserved for IETF-Defined Message Class extensions
0 Management (MGMT) Message [IUA/M2UA/M3UA/SUA]
1 Transfer Messages [M3UA]
2 SS7 Signalling Network Management (SSNM) Messages [M3UA/SUA]
3 ASP State Maintenance (ASPSM) Messages [IUA/M2UA/M3UA/SUA]
4 ASP Traffic Maintenance (ASPTM) Messages [IUA/M2UA/M3UA/SUA]
5 Q.921/Q.931 Boundary Primitives Transport (QPTM)
Messages [IUA]
6 MTP2 User Adaptation (MAUP) Messages [M2UA]
7 Connectionless Messages [SUA]
8 Connection-Oriented Messages [SUA]
9 Routing Key Management (RKM) Messages (M3UA)
10 Interface Identifier Management (IIM) Messages (M2UA)
11 to 127 Reserved by the IETF
128 to 255 Reserved for IETF-Defined Message Class extensions
The following List contains the Message Types for the valid Message Classes:
以下列表包含有效消息类的消息类型：
MTP2 User Adaptation (MAUP) Messages
MTP2用户自适应（MAUP）消息
0 Reserved 1 Data 2 Establish Request 3 Establish Confirm 4 Release Request 5 Release Confirm 6 Release Indication 7 State Request 8 State Confirm 9 State Indication 10 Data Retrieval Request 11 Data Retrieval Confirm 12 Data Retrieval Indication 13 Data Retrieval Complete Indication 14 Congestion Indication 15 Data Acknowledge 16 to 127 Reserved by the IETF 128 to 255 Reserved for IETF-Defined MAUP extensions
0保留1数据2建立请求3建立确认4释放请求5释放确认6释放指示7状态请求8状态确认9状态指示10数据检索请求11数据检索确认12数据检索指示13数据检索完成指示14拥塞指示15数据确认16至127保留由IETF 128到255为IETF定义的MAUP扩展保留
Application Server Process State Maintenance (ASPSM) messages
应用程序服务器进程状态维护（ASPSM）消息
0 Reserved 1 ASP Up (UP) 2 ASP Down (DOWN) 3 Heartbeat (BEAT) 4 ASP Up Ack (UP ACK) 5 ASP Down Ack (DOWN ACK) 6 Heartbeat Ack (BEAT ACK) 7 to 127 Reserved by the IETF 128 to 255 Reserved for IETF-Defined ASPSM extensions
0保留1 ASP向上（向上）2 ASP向下（向下）3心跳（节拍）4 ASP向上确认（向上确认）5 ASP向下确认（向下确认）6心跳确认（节拍确认）7到127由IETF保留128到255为IETF定义的ASPSM扩展保留
Application Server Process Traffic Maintenance (ASPTM) messages
应用程序服务器进程流量维护（ASPTM）消息
0 Reserved 1 ASP Active (ACTIVE) 2 ASP Inactive (INACTIVE) 3 ASP Active Ack (ACTIVE ACK) 4 ASP Inactive Ack (INACTIVE ACK) 5 to 127 Reserved by the IETF 128 to 255 Reserved for IETF-Defined ASPTM extensions
0保留1 ASP活动（活动）2 ASP非活动（非活动）3 ASP活动确认（活动确认）4 ASP非活动确认（非活动确认）5到127由IETF保留128到255为IETF定义的ASPTM扩展保留
Management (MGMT) Messages
管理（MGMT）消息
0 Error (ERR) 1 Notify (NTFY) 2 to 127 Reserved by the IETF 128 to 255 Reserved for IETF-Defined MGMT extensions
0错误（ERR）1通知（NTFY）2到127由IETF保留128到255为IETF定义的管理扩展保留
Interface Identifier Management (IIM) Messages
接口标识符管理（IIM）消息
0 Reserved 1 Registration Request (REG REQ) 2 Registration Response (REG RSP) 3 Deregistration Request (DEREG REQ) 4 Deregistration Response (DEREG RSP) 5 to 127 Reserved by the IETF 128 to 255 Reserved for IETF-Defined IIM extensions
0保留1注册请求（REG REQ）2注册响应（REG RSP）3注销请求（DEREG REQ）4注销响应（DEREG RSP）5到127由IETF保留128到255为IETF定义的IIM扩展保留
The Message Length defines the length of the message in octets, including the header. The Message Length MUST include parameter padding bytes, if any. The Message Length MUST NOT be longer than a MTP3 message [2,3,4,5] plus the length of the common and M2UA message headers.
消息长度以八位字节定义消息的长度，包括消息头。消息长度必须包括参数填充字节（如果有）。消息长度不得超过MTP3消息[2,3,4,5]加上公共和M2UA消息头的长度。
M2UA messages consist of a Common Header followed by zero or more variable-length parameters, as defined by the message type. The variable-length parameters contained in a message are defined in a Tag-Length-Value format as shown below.
M2UA消息由一个公共头和零个或多个可变长度参数组成，这些参数由消息类型定义。消息中包含的可变长度参数以标记长度值格式定义，如下所示。
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Parameter Tag | Parameter Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ Parameter 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Parameter Tag | Parameter Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ Parameter Value /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Mandatory parameters MUST be placed before optional parameters in a message.
在消息中，必须将强制参数置于可选参数之前。
Parameter Tag: 16 bits (unsigned integer)
参数标记：16位（无符号整数）
The Type field is a 16 bit identifier of the type of parameter. It takes a value of 0 to 65534. The common parameters used by the adaptation layers are in the range of 0x00 to 0xff. The M2UA specific parameters have Tags in the range 0x300 to 0x3ff.
类型字段是参数类型的16位标识符。它的值为0到65534。自适应层使用的公共参数在0x00到0xff的范围内。M2UA特定参数的标记范围为0x300至0x3ff。
The common parameter tags (used by all User Adaptation layers) that M2UA uses are defined below:
M2UA使用的通用参数标签（由所有用户适配层使用）定义如下：
Parameter Value Parameter Name
--------------- --------------
0 (0x00) Reserved
1 (0x01) Interface Identifier (Integer)
2 (0x02) Unused
3 (0x03) Interface Identifier (Text)
4 (0x04) Info String
5 (0x05) Unused
6 (0x06) Unused
7 (0x07) Diagnostic Information
8 (0x08) Interface Identifier (Integer Range)
9 (0x09) Heartbeat Data
10 (0x0a) Unused
11 (0x0b) Traffic Mode Type
12 (0x0c) Error Code
13 (0x0d) Status Type/Information
14 (0x0e) Unused
15 (0x0f) Unused
16 (0x10) Unused
17 (0x11) ASP Identifier
18 (0x12) Unused
19 (0x13) Correlation Id
18-255 Reserved
Parameter Value Parameter Name
--------------- --------------
0 (0x00) Reserved
1 (0x01) Interface Identifier (Integer)
2 (0x02) Unused
3 (0x03) Interface Identifier (Text)
4 (0x04) Info String
5 (0x05) Unused
6 (0x06) Unused
7 (0x07) Diagnostic Information
8 (0x08) Interface Identifier (Integer Range)
9 (0x09) Heartbeat Data
10 (0x0a) Unused
11 (0x0b) Traffic Mode Type
12 (0x0c) Error Code
13 (0x0d) Status Type/Information
14 (0x0e) Unused
15 (0x0f) Unused
16 (0x10) Unused
17 (0x11) ASP Identifier
18 (0x12) Unused
19 (0x13) Correlation Id
18-255 Reserved
The M2UA specific parameter Tags defined are as follows:
定义的M2UA特定参数标记如下：
Parameter Value Parameter Name
--------------- --------------
768 (0x0300) Protocol Data 1
769 (0x0301) Protocol Data 2 (TTC)
770 (0x0302) State Request
771 (0x0303) State Event
772 (0x0304) Congestion Status
773 (0x0305) Discard Status
774 (0x0306) Action
775 (0x0307) Sequence Number
776 (0x0308) Retrieval Result
777 (0x0309) Link Key
778 (0x030a) Local-LK-Identifier
779 (0x030b) Signalling Data Terminal (SDT) Identifier
780 (0x030c) Signalling Data Link (SDL) Identifier
781 (0x030d) Registration Result
782 (0x030e) Registration Status
783 (0x030f) De-Registration Result
784 (0x0310) De-Registration Status
Parameter Value Parameter Name
--------------- --------------
768 (0x0300) Protocol Data 1
769 (0x0301) Protocol Data 2 (TTC)
770 (0x0302) State Request
771 (0x0303) State Event
772 (0x0304) Congestion Status
773 (0x0305) Discard Status
774 (0x0306) Action
775 (0x0307) Sequence Number
776 (0x0308) Retrieval Result
777 (0x0309) Link Key
778 (0x030a) Local-LK-Identifier
779 (0x030b) Signalling Data Terminal (SDT) Identifier
780 (0x030c) Signalling Data Link (SDL) Identifier
781 (0x030d) Registration Result
782 (0x030e) Registration Status
783 (0x030f) De-Registration Result
784 (0x0310) De-Registration Status
Parameter Length: 16 bits (unsigned integer)
参数长度：16位（无符号整数）
The Parameter Length field contains the size of the parameter in bytes, including the Parameter Tag, Parameter Length, and Parameter Value fields. Thus, a parameter with a zero-length Parameter Value field would have a Length field of 4. The Parameter Length does not include any padding bytes.
参数长度字段包含以字节为单位的参数大小，包括参数标记、参数长度和参数值字段。因此，具有零长度参数值字段的参数的长度字段为4。参数长度不包括任何填充字节。
Parameter Value: variable-length.
参数值：可变长度。
The Parameter Value field contains the actual information to be transferred in the parameter.
参数值字段包含要在参数中传输的实际信息。
The total length of a parameter (including Tag, Parameter Length and Value fields) MUST be a multiple of 4 bytes. If the length of the parameter is not a multiple of 4 bytes, the sender pads the Parameter at the end (i.e., after the Parameter Value field) with all zero bytes. The length of the padding is NOT included in the parameter length field. A sender MUST NOT pad with more than 3 bytes. The receiver MUST ignore the padding bytes.
参数的总长度（包括标记、参数长度和值字段）必须是4字节的倍数。如果参数的长度不是4字节的倍数，则发送方在参数末尾（即参数值字段之后）填充所有零字节。填充的长度不包括在参数长度字段中。发送方的填充长度不得超过3个字节。接收器必须忽略填充字节。
In addition to the common message header, there will be a M2UA specific message header. The M2UA specific message header will immediately follow the common message header, but will only be used with MAUP messages.
除了公共消息头之外，还将有一个M2UA特定的消息头。M2UA特定消息头将紧跟在公共消息头之后，但仅用于MAUP消息。
This message header will contain the Interface Identifier. The Interface Identifier identifies the physical interface at the SG for which the signalling messages are sent/received. The format of the Interface Identifier parameter can be text or integer, the values of which are assigned according to network operator policy. The values used are of local significance only, coordinated between the SG and ASP.
此消息头将包含接口标识符。接口标识符标识SG上发送/接收信令消息的物理接口。接口标识符参数的格式可以是文本或整数，其值根据网络运营商策略分配。使用的值仅具有局部意义，在SG和ASP之间进行协调。
The integer formatted Interface Identifier MUST be supported. The text formatted Interface Identifier MAY optionally be supported.
必须支持整数格式的接口标识符。可以选择支持文本格式的接口标识符。
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x1) | Length=8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier (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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x1) | Length=8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier (integer) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3 M2UA Message Header (Integer-based Interface Identifier)
图3 M2UA消息头（基于整数的接口标识符）
The Tag value for the Integer-based Interface Identifier is 0x1. The length is always set to a value of 8.
基于整数的接口标识符的标记值为0x1。长度始终设置为8的值。
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x3) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Interface Identifier (text) /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x3) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Interface Identifier (text) /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4 M2UA Message Header (Text-based Interface Identifier)
图4 M2UA消息头（基于文本的接口标识符）
The Tag value for the Text-based Interface Identifier is 0x3. The encoding of the Identifier is ANSI X3.4-1986 [7]. The maximum string length of the text-based Interface Identifier is 255 octets. The tag length is equal to the string length of the Interface Identifier name plus four bytes for the Tag and Length fields.
基于文本的接口标识符的标记值为0x3。标识符的编码为ANSI X3.4-1986[7]。基于文本的接口标识符的最大字符串长度为255个八位字节。标记长度等于接口标识符名称的字符串长度加上标记和长度字段的四个字节。
The following section defines the messages and parameter contents. The M2UA messages will use the common message header (Figure 2) and the M2UA message header (Figure 3 and Figure 4).
以下部分定义了消息和参数内容。M2UA消息将使用公共消息头（图2）和M2UA消息头（图3和图4）。
The Data message contains an SS7 MTP2-User Protocol Data Unit (PDU). The Data message contains the following parameter:
数据消息包含一个SS7 MTP2用户协议数据单元（PDU）。数据消息包含以下参数：
Protocol Data (mandatory) Correlation Id (optional)
协议数据（必需）关联Id（可选）
The format for the Data Message parameters 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x300) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Protocol Data /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x13) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Correlation 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x300) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Protocol Data /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x13) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Correlation Id |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Protocol Data field contains the MTP2-User application message in network byte order starting with the Signalling Information Octet (SIO). The Correlation Id parameter uniquely identifies the MSU carried in the Protocol Data within an AS. This Correlation Id parameter is assigned by the sending M2UA. The purpose of the Correlation Id is to permit the newly active ASP to synchronize its processing of the traffic in each ordered stream with other ASPs in the broadcast group.
协议数据字段以网络字节顺序包含MTP2用户应用程序消息，从信令信息八位字节（SIO）开始。Correlation Id参数唯一标识AS中协议数据中携带的MSU。此相关Id参数由发送M2UA分配。相关Id的目的是允许新激活的ASP将其对每个有序流中的流量的处理与广播组中的其他ASP同步。
The format for a Data Message with TTC PDU parameters is as follows:
带有TTC PDU参数的数据报文格式如下：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x301) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ TTC Protocol Data /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x13) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Correlation 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x301) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ TTC Protocol Data /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x13) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Correlation Id |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Protocol Data field contains the MTP2-User application message in network byte order starting with the Length Indicator (LI) octet. The Japanese TTC variant uses the spare bits of the LI octet for priority.
协议数据字段以网络字节顺序包含MTP2用户应用程序消息，从长度指示器（LI）八位字节开始。日本TTC变体使用LI八位字节的备用位作为优先级。
The length of the Protocol Data and TTC Protocol Data MUST NOT exceed the length of a MTP2-User application message [2,3,5].
协议数据和TTC协议数据的长度不得超过MTP2用户应用程序消息的长度[2,3,5]。
The Data Acknowledge message contains the Correlation Id of the Data message that the sending M2UA is acknowledging as successfully processed to the peer M2UA.
数据确认消息包含发送M2UA向对等M2UA确认已成功处理的数据消息的相关Id。
The Data Acknowledge message contains the following parameter:
数据确认消息包含以下参数：
Correlation Id Mandatory
相关Id是必需的
The following format MUST be used for the Data Ack 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x13) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Correlation 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x13) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Correlation Id |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Correlation Id parameter of the Data message and the Data Ack message provide a mechanism, for those SG implementations capable of taking advantage of them, to obtain an acknowledgment that the MSU has been transferred to the M2UA peer before acknowledging the MSU to
数据消息和数据确认消息的相关Id参数为那些能够利用它们的SG实现提供了一种机制，以在将MSU确认为已被传输到M2UA对等方之前获得MSU已被传输到M2UA对等方的确认
the SS7 peer, removing the risk of losing messages due to association failure or SCTP congestion.
SS7对等，消除了由于关联失败或SCTP拥塞而丢失消息的风险。
The Data Ack message MUST be sent if a Correlation Id parameter is received from the peer. Otherwise, the Data Ack message MUST NOT be sent.
如果从对等方接收到相关Id参数，则必须发送数据确认消息。否则，不得发送数据确认消息。
If the Data Acknowledge is not sent for Correlation Id(s) or is sent with Invalid Correlation Id(s), the SS7 link will eventually fail due to lack of MTP Level 2 acknowledgments of the SS7 peer's MSUs.
如果数据确认未针对相关Id发送，或发送时相关Id无效，则SS7链路最终将因缺少SS7对等方MSU的MTP 2级确认而失败。
The Establish Request message is used to establish the SS7 link or to indicate that the channel has been established. The MGC controls the state of the SS7 link. When the MGC desires the SS7 link to be in-service, it will send the Establish Request message. Note that the SGP MAY already have the SS7 link established at its layer. If so, upon receipt of an Establish Request, the SGP takes no action except to send an Establish Confirm.
建立请求消息用于建立SS7链路或指示信道已建立。MGC控制SS7链路的状态。当MGC希望SS7链路处于服务状态时，它将发送建立请求消息。注意，SGP可能已经在其层建立了SS7链路。如果是，在收到建立请求后，SGP不采取任何行动，只发送建立确认。
When the MGC sends an M2UA Establish Request message, the MGC MAY start a timer. This timer would be stopped upon receipt of an M2UA Establish Confirm. If the timer expires, the MGC would resend the M2UA Establish Request message and restart the timer. In other words, the MGC MAY continue to request the establishment of the data link on a periodic basis until the desired state is achieved or some other action is taken (notify the Management Layer).
当MGC发送M2UA建立请求消息时，MGC可以启动计时器。收到M2UA建立确认后，该计时器将停止。如果计时器过期，MGC将重新发送M2UA建立请求消息并重新启动计时器。换言之，MGC可继续定期请求建立数据链路，直到达到所需状态或采取某种其他行动（通知管理层）。
The mode (Normal or Emergency) for bringing the SS7 link in service is defaulted to Normal. The State Request (described in Section 3.3.1.5 below) can be used to change the mode to Emergency.
使SS7链路投入服务的模式（正常或紧急）默认为正常。状态请求（如下文第3.3.1.5节所述）可用于将模式更改为紧急模式。
This Release Request message is used to release the channel. The Release Confirm and Indication messages are used to indicate that the channel has been released.
此释放请求消息用于释放通道。释放确认和指示消息用于指示通道已释放。
The State Request message can be sent from a MGC to cause an action on a particular SS7 link supported by the Signalling Gateway Process. The SGP sends a State Confirm to the MGC if the action has been successfully completed. The State Confirm reflects that state value received in the State Request message.
可以从MGC发送状态请求消息，以便在信令网关进程支持的特定SS7链路上执行操作。如果操作已成功完成，SGP将向MGC发送状态确认。状态确认反映在状态请求消息中接收到的状态值。
The State Request message contains the following parameter:
状态请求消息包含以下参数：
State (mandatory)
国家（强制性）
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x302) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| State |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x302) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| State |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The valid values for State are shown in the following table.
状态的有效值如下表所示。
Define Value Description STATUS_LPO_SET 0x0 Request local processor outage STATUS_LPO_CLEAR 0x1 Request local processor outage recovered STATUS_EMER_SET 0x2 Request emergency alignment STATUS_EMER_CLEAR 0x3 Request normal alignment (cancel emergency) STATUS_FLUSH_BUFFERS 0x4 Flush or clear receive, transmit and retransmit queues STATUS_CONTINUE 0x5 Continue or Resume STATUS_CLEAR_RTB 0x6 Clear the retransmit queue STATUS_AUDIT 0x7 Audit state of link STATUS_CONG_CLEAR 0x8 Congestion cleared STATUS_CONG_ACCEPT 0x9 Congestion accept STATUS_CONG_DISCARD 0xa Congestion discard
定义值描述状态\u LPO\u集合0x0请求本地处理器中断状态\u LPO\u清除0x1请求本地处理器中断恢复状态\u紧急\u集合0x2请求紧急对齐状态\u紧急清除0x3请求正常对齐（取消紧急）状态\u刷新\u缓冲区0x4刷新或清除接收，传输和重传队列状态\u继续0x5继续或恢复状态\u清除\u RTB 0x6清除重传队列状态\u审核0x7审核链路状态\u通信\u清除0x8拥塞清除状态\u通信\u接受0x9拥塞接受状态\u通信\u丢弃0xa拥塞丢弃
The State Confirm message will be sent by the SGP in response to a State Request from the MGC. The State Confirm reflects that state value received in the State Request message.
SGP将发送状态确认消息，以响应MGC的状态请求。状态确认反映在状态请求消息中接收到的状态值。
The State Confirm message contains the following parameter:
状态确认消息包含以下参数：
State (mandatory)
国家（强制性）
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x302) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| State |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x302) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| State |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The valid values for State are shown in the following table. The value of the State field SHOULD reflect the value received in the State Request message.
状态的有效值如下表所示。状态字段的值应反映在状态请求消息中接收到的值。
Define Value Description STATUS_LPO_SET 0x0 Request local processor outage STATUS_LPO_CLEAR 0x1 Request local processor outage recovered STATUS_EMER_SET 0x2 Request emergency alignment STATUS_EMER_CLEAR 0x3 Request normal alignment (cancel emergency) STATUS_FLUSH_BUFFERS 0x4 Flush or clear receive, transmit and retransmit queues STATUS_CONTINUE 0x5 Continue or Resume STATUS_CLEAR_RTB 0x6 Clear the retransmit queue STATUS_AUDIT 0x7 Audit state of link STATUS_CONG_CLEAR 0x8 Congestion cleared STATUS_CONG_ACCEPT 0x9 Congestion accept STATUS_CONG_DISCARD 0xa Congestion discard
定义值描述状态\u LPO\u集合0x0请求本地处理器中断状态\u LPO\u清除0x1请求本地处理器中断恢复状态\u紧急\u集合0x2请求紧急对齐状态\u紧急清除0x3请求正常对齐（取消紧急）状态\u刷新\u缓冲区0x4刷新或清除接收，传输和重传队列状态\u继续0x5继续或恢复状态\u清除\u RTB 0x6清除重传队列状态\u审核0x7审核链路状态\u通信\u清除0x8拥塞清除状态\u通信\u接受0x9拥塞接受状态\u通信\u丢弃0xa拥塞丢弃
The MTP2 State Indication message can be sent from a SGP to an ASP to indicate a condition on a SS7 link.
MTP2状态指示消息可以从SGP发送到ASP，以指示SS7链路上的状态。
The State Indication message contains the following parameter:
状态指示消息包含以下参数：
Event (mandatory)
事件（强制性）
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x303) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Event |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x303) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Event |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The valid values for Event are shown in the following table.
事件的有效值如下表所示。
Define Value Description EVENT_RPO_ENTER 0x1 Remote entered processor outage EVENT_RPO_EXIT 0x2 Remote exited processor outage EVENT_LPO_ENTER 0x3 Link entered processor outage EVENT_LPO_EXIT 0x4 Link exited processor outage
定义值描述事件\u RPO\u输入0x1远程输入的处理器中断事件\u RPO\u退出0x2远程退出的处理器中断事件\u LPO\u输入0x3链接输入的处理器中断事件\u LPO\u退出0x4链接退出的处理器中断
The Congestion Indication message can be sent from a Signalling Gateway Process to an ASP to indicate the congestion status and discard status of a SS7 link. When the MSU buffer fill increases above an Onset threshold or decreases below an Abatement threshold or crosses a Discard threshold in either direction, the SGP SHALL send a congestion indication message when it supports SS7 MTP2 variants that support multiple congestion levels.
拥塞指示消息可以从信令网关进程发送到ASP，以指示SS7链路的拥塞状态和丢弃状态。当MSU缓冲区填充增加到起始阈值以上，或减少到缓解阈值以下，或在任一方向超过丢弃阈值时，SGP应在其支持支持多个拥塞级别的SS7 MTP2变体时发送拥塞指示消息。
The SGP SHALL send the message only when there is actually a change in either the discard level or the congestion level to report, meaning it is different from the previously sent message. In addition, the SGP SHALL use an implementation dependent algorithm to limit the frequency of congestion indication messages.
只有当要报告的丢弃级别或拥塞级别实际发生变化时，SGP才应发送消息，这意味着它与之前发送的消息不同。此外，SGP应使用依赖于实现的算法来限制拥塞指示消息的频率。
An implementation may optionally send Congestion Indication messages on a "high priority" stream in order to potentially reduce delay.
实现可以可选地在“高优先级”流上发送拥塞指示消息，以便潜在地减少延迟。
The Congestion Indication message contains the following parameters:
拥塞指示消息包含以下参数：
Congestion Status (mandatory) Discard Status (optional)
拥塞状态（强制）放弃状态（可选）
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x304) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Congestion Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x305) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Discard Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x304) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Congestion Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x305) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Discard Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The valid values for Congestion Status and Discard Status are shown in the following table.
拥塞状态和丢弃状态的有效值如下表所示。
Define Value Description LEVEL_NONE 0x0 No congestion LEVEL_1 0x1 Congestion Level 1 LEVEL_2 0x2 Congestion Level 2 LEVEL_3 0x3 Congestion Level 3
定义值描述级别\u无0x0无拥塞级别\u 1 0x1拥塞级别1级别\u 2 0x2拥塞级别2级别\u 3 0x3拥塞级别3
For SS7 networks that do not support multiple levels of congestion, only the LEVEL_NONE and LEVEL_3 values will be used. For SS7 networks that support multiple levels of congestion, it is possible for all values to be used. Refer to [2], [3] and [12] for more details on the Congestion and Discard Status of SS7 signalling links.
对于不支持多个拥塞级别的SS7网络，将仅使用级别_NONE和级别_3的值。对于支持多级拥塞的SS7网络，可以使用所有值。有关SS7信令链路的拥塞和丢弃状态的更多详细信息，请参阅[2]、[3]和[12]。
The MTP2 Retrieval Request message is used during the MTP Level 3 changeover procedure to request the BSN, to retrieve PDUs from the transmit and retransmit queues or to flush PDUs from the retransmit queue. Examples of the use of Retrieval Request for SS7 Link Changeover are provided in Section 5.3.6.
MTP2检索请求消息在MTP级别3转换过程中用于请求BSN、从传输和重传队列检索PDU或从重传队列刷新PDU。第5.3.6节提供了SS7链路转换检索请求的使用示例。
The Retrieval Request message contains the following parameters:
检索请求消息包含以下参数：
Action (mandatory) Sequence Number (optional)
操作（强制）序列号（可选）
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x306) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Action |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x307) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x306) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Action |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x307) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The valid values for Action are shown in the following table.
下表显示了操作的有效值。
Define Value Description ACTION_RTRV_BSN 0x1 Retrieve the backward sequence number ACTION_RTRV_MSGS 0x2 Retrieve the PDUs from the transmit and retransmit queues
定义值描述操作\u RTRV\u BSN 0x1检索向后序列号操作\u RTRV\u MSGS 0x2从传输和重新传输队列检索PDU
In the Retrieval Request message, the Sequence Number field SHOULD NOT be present if the Action field is ACTION_RTRV_BSN. The Sequence Number field contains the Forward Sequence Number (FSN) of the far end if the Action is ACTION_RTRV_MSGS.
在检索请求消息中，如果操作字段为Action\u RTRV\u BSN，则序列号字段不应出现。如果操作为Action_RTRV_MSGS，则序列号字段包含远端的前向序列号（FSN）。
The MTP2 Retrieval Confirm message is sent by the Signalling Gateway in response to a Retrieval Request message. Examples of the use of the Retrieval Confirm for SS7 Link Changeover are provided in Section 5.3.6.
MTP2检索确认消息由信令网关发送，以响应检索请求消息。第5.3.6节提供了SS7链路转换使用检索确认的示例。
The Retrieval Confirm message contains the following parameters:
检索确认消息包含以下参数：
Action (mandatory) Result (mandatory) Sequence Number (optional)
操作（强制）结果（强制）序列号（可选）
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x306) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Action |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x308) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Result |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x307) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x306) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Action |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x308) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Result |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x307) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The valid values for Action are the same as in Retrieval Request.
操作的有效值与检索请求中的值相同。
The values for Result are shown below:
结果值如下所示：
Define Value Description RESULT_SUCCESS 0x0 Action successful RESULT_FAILURE 0x1 Action failed
定义值说明结果\u成功0x0操作成功结果\u失败0x1操作失败
When the Signalling Gateway Process sends a Retrieval Confirm to a Retrieval Request, it echos the Action field. If the Action was ACTION_RTRV_BSN and the SGP successfully retrieved the BSN, the SGP will put the Backward Sequence Number (BSN) in the Sequence Number field and will indicate a success in the Result field. If the BSN could not be retrieved, the Sequence Number field will not be included and the Result field will indicate failure.
当信令网关进程向检索请求发送检索确认时，它会回显操作字段。如果操作为Action_RTRV_BSN，且SGP成功检索BSN，则SGP将在序列号字段中放置反向序列号（BSN），并在结果字段中指示成功。如果无法检索BSN，则不包括序列号字段，结果字段将指示失败。
For a Retrieval Confirm with Action of ACTION_RTRV_MSGS, the value of the Result field will indicate success or failure. A failure means that the buffers could not be retrieved. The Sequence Number field is not used with ACTION_RTRV_MSGS.
对于带有Action_RTRV_MSGS操作的检索确认，结果字段的值将指示成功或失败。失败意味着无法检索缓冲区。序列号字段不与操作\u RTRV\u MSGS一起使用。
The Retrieval Indication message is sent by the Signalling Gateway with a PDU from the transmit or retransmit queue. The Retrieval Indication message does not contain the Action or Sequence Number fields, just a MTP3 Protocol Data Unit (PDU) from the transmit or retransmit queue. Examples of the use of the Retrieval Indication for SS7 Link Changeover are provided in Section 5.3.6.
检索指示消息由信令网关通过PDU从传输或重传队列发送。检索指示消息不包含操作或序列号字段，仅包含来自传输或重传队列的MTP3协议数据单元（PDU）。第5.3.6节提供了SS7链路转换检索指示的使用示例。
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x300) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Protocol Data /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x300) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Protocol Data /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
For TTC Data messages, the following parameter will be used to indicate a TTC PDU which starts at LI.
对于TTC数据消息，以下参数将用于指示从LI开始的TTC PDU。
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x301) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ TTC Protocol Data /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x301) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ TTC Protocol Data /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The M2UA implementation MAY consider the use of the bundling feature of SCTP for Retrieval Indication messages.
M2UA实现可以考虑使用SCTP的捆绑特征来检索指示消息。
The MTP2 Retrieval Complete Indication message is exactly the same as the MTP2 Retrieval Indication message except that it also indicates that retrieval is complete. In addition, it MAY contain a PDU (which MUST be the last PDU) from the transmit or retransmit queue.
MTP2检索完成指示消息与MTP2检索指示消息完全相同，只是它也指示检索完成。此外，它可能包含来自传输或重传队列的PDU（必须是最后一个PDU）。
The ASPM messages will only use the common message header.
ASPM消息将仅使用公共消息头。
The ASP Up (ASPUP) message is used to indicate to a remote M2UA peer that the Adaptation layer is ready to receive traffic or maintenance messages.
ASP Up（ASUP）消息用于向远程M2UA对等方指示适配层已准备好接收流量或维护消息。
The ASPUP message contains the following parameters
ASPUP消息包含以下参数
ASP Identifier (optional) Info String (optional)
ASP标识符（可选）信息字符串（可选）
Note: The ASP Identifier MUST be used where the SGP cannot identify the ASP by pre-configured address/port number information (e.g., where an ASP is resident on a Host using dynamic address/port number assignment).
注意：如果SGP无法通过预配置的地址/端口号信息识别ASP，则必须使用ASP标识符（例如，ASP驻留在使用动态地址/端口号分配的主机上）。
The format for ASPUP Message parameters is as follows:
ASPUP消息参数的格式如下所示：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x11) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ASP Identifier* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ INFO String* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x11) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ASP Identifier* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ INFO String* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The optional ASP Identifier parameter would contain a unique value that is locally significant among the ASPs that support an AS. The SGP should save the ASP Identifier to be used, if necessary, with the Notify message (see Section 3.3.3.2).
可选的ASP标识符参数将包含一个唯一的值，该值在支持AS的ASP中具有本地意义。SGP应保存ASP标识符，以便在必要时与Notify消息一起使用（见第3.3.3.2节）。
The optional INFO String parameter can carry any meaningful UTF-8 [6] character string along with the message. Length of the INFO String parameter is from 0 to 255 octets. No procedures are presently identified for its use but the INFO String MAY be used for debugging purposes.
可选信息字符串参数可以携带任何有意义的UTF-8[6]字符串以及消息。信息字符串参数的长度为0到255个八位字节。目前还没有确定其使用的过程，但信息字符串可用于调试目的。
The ASP Up Ack message is used to acknowledge an ASP Up message received from a remote M2UA peer.
ASP Up Ack消息用于确认从远程M2UA对等方接收到的ASP Up消息。
The ASPUP Ack message contains the following parameters:
ASUP Ack消息包含以下参数：
INFO String (optional)
信息字符串（可选）
The format for ASPUP Ack Message parameters is as follows:
ASPUP Ack消息参数的格式如下：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ INFO String* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ INFO String* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format and description of the optional Info String parameter is the same as for the ASP UP message (See Section 3.3.2.1).
可选信息字符串参数的格式和说明与ASP UP消息的格式和说明相同（见第3.3.2.1节）。
The ASP Down (ASPDN) message is used to indicate to a remote M2UA peer that the adaptation layer is not ready to receive traffic or maintenance messages.
ASP Down（ASPDN）消息用于向远程M2UA对等方指示适配层尚未准备好接收流量或维护消息。
The ASPDN message contains the following parameters
ASPDN消息包含以下参数
INFO String (optional)
信息字符串（可选）
The format for the ASPDN message parameters is as follows:
ASPDN消息参数的格式如下所示：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ INFO String* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ INFO String* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format and description of the optional Info String parameter is the same as for the ASP Up message (See Section 3.3.2.1).
可选信息字符串参数的格式和说明与ASP Up消息的格式和说明相同（见第3.3.2.1节）。
The ASP Down Ack message is used to acknowledge an ASP Down message received from a remote M2UA peer.
ASP Down Ack消息用于确认从远程M2UA对等方接收到的ASP Down消息。
The ASP Down Ack message contains the following parameters:
ASP Down Ack消息包含以下参数：
INFO String (optional)
信息字符串（可选）
The format for the ASPDN Ack message parameters is as follows:
ASPDN Ack消息参数的格式如下：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ INFO String* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ INFO String* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format and description of the optional Info String parameter is the same as for the ASP UP message (See Section 3.3.2.1).
可选信息字符串参数的格式和说明与ASP UP消息的格式和说明相同（见第3.3.2.1节）。
The Heartbeat message is optionally used to ensure that the M2UA peers are still available to each other.
心跳消息可选择性地用于确保M2UA对等点彼此仍然可用。
The BEAT message contains the following parameter:
节拍消息包含以下参数：
Heartbeat Data Optional
心跳数据可选
The format for the BEAT message 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0009 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Heartbeat Data /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0009 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Heartbeat Data /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The sending node defines the Heartbeat Data field contents. It may include a Heartbeat Sequence Number and/or time stamp, or other implementation specific details.
发送节点定义心跳数据字段内容。它可能包括心跳序列号和/或时间戳，或其他特定于实现的细节。
The receiver of a Heartbeat message does not process this field as it is only of significance to the sender. The receiver echoes the content of the Heartbeat Data in a BEAT ACK message.
心跳消息的接收者不处理此字段，因为它仅对发送者重要。接收器在拍确认消息中回显心跳数据的内容。
The Heartbeat ACK message is sent in response to a BEAT message. A peer MUST send a BEAT ACK in response to a BEAT message. It includes all the parameters of the received Heartbeat message, without any change.
心跳确认消息是响应节拍消息而发送的。对等方必须发送节拍确认以响应节拍消息。它包括接收到的心跳消息的所有参数，没有任何更改。
The BEAT ACK message contains the following parameter:
节拍确认消息包含以下参数：
Heartbeat Data Optional
心跳数据可选
The format for the BEAT ACK message 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0009 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Heartbeat Data /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0009 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Heartbeat Data /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The sending node defines the Heartbeat Data field contents. It may include a Heartbeat Sequence Number and/or time stamp, or other implementation specific details.
发送节点定义心跳数据字段内容。它可能包括心跳序列号和/或时间戳，或其他特定于实现的细节。
The receiver of a Heartbeat message does not process this field as it is only of significance to the sender. The receiver echoes the content of the Heartbeat Data in a BEAT ACK message.
心跳消息的接收者不处理此字段，因为它仅对发送者重要。接收器在拍确认消息中回显心跳数据的内容。
The ASPAC message is sent by an ASP to indicate to an SGP that it is Active and ready to be used.
ASPAC消息由ASP发送，以向SGP指示其处于活动状态并准备好使用。
The ASPAC message contains the following parameters:
ASPAC消息包含以下参数：
Traffic Mode Type (optional) Interface Identifier (optional) - Combination of integer and integer ranges, OR - string (text formatted) INFO String (optional)
交通模式类型（可选）接口标识符（可选）-整数和整数范围的组合，或-字符串（文本格式）信息字符串（可选）
The format for the ASPAC message using integer formatted Interface Identifiers is as follows:
使用整数格式接口标识符的ASPAC消息格式如下：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0xb) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Traffic Mode Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x1=integer) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Interface Identifiers* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x8=integer range) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Start1* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Stop1* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Start2* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Stop2* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. .
. .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier StartN* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier StopN* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Additional Interface Identifiers /
/ of Tag Type 0x1 or 0x8 \
\ /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ INFO String* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0xb) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Traffic Mode Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x1=integer) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Interface Identifiers* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x8=integer range) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Start1* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Stop1* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Start2* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Stop2* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. .
. .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier StartN* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier StopN* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Additional Interface Identifiers /
/ of Tag Type 0x1 or 0x8 \
\ /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ INFO String* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format for the ASPAC message using text formatted (string) Interface Identifiers is as follows:
使用文本格式（字符串）接口标识符的ASPAC消息格式如下：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0xb) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Traffic Mode Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x3=string) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Interface Identifier* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Additional Interface Identifiers /
/ of Tag Type 0x3 \
\ /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ INFO String* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0xb) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Traffic Mode Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x3=string) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Interface Identifier* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Additional Interface Identifiers /
/ of Tag Type 0x3 \
\ /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ INFO String* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Traffic Mode Type parameter identifies the traffic mode of operation of the ASP within an AS. The valid values for Type are shown in the following table:
Traffic Mode Type参数标识AS中ASP的运行流量模式。类型的有效值如下表所示：
Value Description 0x1 Override 0x2 Load-share 0x3 Broadcast
值说明0x1覆盖0x2加载共享0x3广播
Within a particular AS, only one Traffic Mode Type can be used. The Override value indicates that the ASP is operating in Override mode, where the ASP takes over all traffic in an Application Server (i.e., primary/backup operation), over-riding any currently active ASPs in the AS. In Load-share mode, the ASP will share in the traffic distribution with any other currently active ASPs. In Broadcast mode, all of the Active ASPs receive all message traffic in the Application Server.
在特定AS中，只能使用一种交通模式类型。Override值表示ASP正在Override模式下运行，在此模式下，ASP接管应用程序服务器中的所有流量（即主/备份操作），超过AS中任何当前活动的ASP。在负载共享模式下，ASP将与任何其他当前活动的ASP共享流量分布。在广播模式下，所有活动的ASP接收应用服务器中的所有消息流量。
The optional Interface Identifiers parameter contains a list of Interface Identifier integers (Type 0x1 or Type 0x8) or text strings (Type 0x3)indexing the Application Server traffic that the sending ASP is configured/registered to receive. If integer formatted Interface Identifiers are being used, the ASP can also send ranges of Interface Identifiers (Type 0x8). Interface Identifier types Integer (0x1) and Integer Range (0x8) are allowed in the same message. Text formatted Interface Identifiers (0x3) cannot be used with either Integer (0x1) or Integer Range (0x8) types.
可选的Interface Identifiers参数包含接口标识符整数（类型0x1或类型0x8）或文本字符串（类型0x3）列表，用于索引发送ASP配置/注册为接收的应用程序服务器流量。如果使用整数格式的接口标识符，ASP还可以发送接口标识符的范围（类型0x8）。同一消息中允许使用Integer（0x1）和Integer Range（0x8）接口标识符类型。文本格式的接口标识符（0x3）不能与整数（0x1）或整数范围（0x8）类型一起使用。
If no Interface Identifiers are included, the message is for all provisioned Interface Identifiers within the AS(s) in which the ASP is provisioned. If only a subset of Interface Identifiers for an AS are included, the ASP is noted as Active for all the Interface Identifiers provisioned for that AS.
如果未包括任何接口标识符，则该消息适用于配置ASP的AS中的所有已配置接口标识符。如果仅包括AS的接口标识符子集，则对于为该AS提供的所有接口标识符，ASP将被视为活动的。
Note: If the optional Interface Identifier parameter is present, the integer formatted Interface Identifier MUST be supported, while the text formatted Interface Identifier MAY be supported.
注意：如果存在可选接口标识符参数，则必须支持整数格式的接口标识符，而可能支持文本格式的接口标识符。
An SGP that receives an ASPAC with an incorrect or unsupported Traffic Mode Type for a particular Interface Identifier will respond with an Error Message (Cause: Unsupported Traffic Handling Mode).
接收特定接口标识符的ASPAC具有不正确或不受支持的流量模式类型的SGP将以错误消息（原因：不受支持的流量处理模式）进行响应。
The format and description of the optional Info String parameter is the same as for the ASP UP message (See Section 3.3.2.1).
可选信息字符串参数的格式和说明与ASP UP消息的格式和说明相同（见第3.3.2.1节）。
The ASP Active (ASPAC) Ack message is used to acknowledge an ASP Active message received from a remote M2UA peer.
ASP Active（ASPAC）Ack消息用于确认从远程M2UA对等方接收到的ASP Active消息。
The ASPAC Ack message contains the following parameters:
ASPAC Ack消息包含以下参数：
Traffic Mode Type (optional) Interface Identifier (optional) - Combination of integer and integer ranges, OR - string (text formatted) INFO String (optional)
交通模式类型（可选）接口标识符（可选）-整数和整数范围的组合，或-字符串（文本格式）信息字符串（可选）
The format for the ASPAC Ack message with Integer-formatted Interface Identifiers is as follows:
带有整数格式接口标识符的ASPAC Ack消息格式如下：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0xb) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Traffic Mode Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x1=integer) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Interface Identifiers* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x8=integer range) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Start1* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Stop1* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Start2* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Stop2* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. .
. .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier StartN* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier StopN* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Additional Interface Identifiers /
/ of Tag Type 0x1 or 0x8 \
\ /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ INFO String* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0xb) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Traffic Mode Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x1=integer) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Interface Identifiers* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x8=integer range) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Start1* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Stop1* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Start2* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Stop2* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. .
. .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier StartN* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier StopN* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Additional Interface Identifiers /
/ of Tag Type 0x1 or 0x8 \
\ /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ INFO String* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format for the ASP Active Ack message using text formatted (string) Interface Identifiers is as follows:
使用文本格式（字符串）接口标识符的ASP活动确认消息的格式如下：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0xb) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Traffic Mode Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x3=string) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Interface Identifier* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Additional Interface Identifiers /
/ of Tag Type 0x3 \
\ /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ INFO String* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0xb) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Traffic Mode Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x3=string) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Interface Identifier* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Additional Interface Identifiers /
/ of Tag Type 0x3 \
\ /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ INFO String* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format and description of the optional Info String parameter is the same as for the ASP Up message (See Section 3.3.2.1).
可选信息字符串参数的格式和说明与ASP Up消息的格式和说明相同（见第3.3.2.1节）。
The format of the optional Interface Identifier parameter is the same as for the ASP Active message (See Section 3.3.2.7).
可选接口标识符参数的格式与ASP活动消息的格式相同（见第3.3.2.7节）。
The format and description of the optional Info String parameter is the same as for the ASP Up message (See Section 3.3.2.1).
可选信息字符串参数的格式和说明与ASP Up消息的格式和说明相同（见第3.3.2.1节）。
The ASP Inactive (ASPIA) message is sent by an ASP to indicate to an SGP that it is no longer an active ASP to be used from within a list of ASPs. The SGP will respond with an ASPIA Ack message and either discard incoming messages or buffer for a timed period and then discard.
ASP非活动（ASPIA）消息由ASP发送，以向SGP指示它不再是要从ASP列表中使用的活动ASP。SGP将使用ASPIA Ack消息进行响应，并在一段时间内丢弃传入消息或缓冲区，然后丢弃。
The ASPIA message contains the following parameters:
ASPIA消息包含以下参数：
Interface Identifiers (optional) - Combination of integer and integer ranges, OR - string (text formatted) INFO String (optional)
接口标识符（可选）-整数和整数范围的组合，或-字符串（文本格式）信息字符串（可选）
The format for the ASP Inactive message parameters using Integer formatted Interface Identifiers is as follows:
使用整数格式接口标识符的ASP非活动消息参数的格式如下：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x1=integer) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Interface Identifiers* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x8=integer range) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Start1* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Stop1* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Start2* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Stop2* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. .
. .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier StartN* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier StopN* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Additional Interface Identifiers /
/ of Tag Type 0x1 or 0x8 \
\ /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ INFO String* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x1=integer) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Interface Identifiers* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x8=integer range) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Start1* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Stop1* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Start2* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Stop2* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. .
. .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier StartN* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier StopN* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Additional Interface Identifiers /
/ of Tag Type 0x1 or 0x8 \
\ /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ INFO String* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format for the ASP Inactive message using text formatted (string) Interface Identifiers is as follows:
使用文本格式（字符串）接口标识符的ASP非活动消息的格式如下：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x3=string) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Interface Identifier* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Additional Interface Identifiers /
/ of Tag Type 0x3 \
\ /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ INFO String* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x3=string) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Interface Identifier* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Additional Interface Identifiers /
/ of Tag Type 0x3 \
\ /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ INFO String* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format of the optional Interface Identifier parameter is the same as for the ASP Active message (See Section 3.3.2.7).
可选接口标识符参数的格式与ASP活动消息的格式相同（见第3.3.2.7节）。
The format and description of the optional Info String parameter is the same as for the ASP Up message (See Section 3.3.2.1).
可选信息字符串参数的格式和说明与ASP Up消息的格式和说明相同（见第3.3.2.1节）。
The optional Interface Identifiers parameter contains a list of Interface Identifier integers indexing the Application Server traffic that the sending ASP is configured/registered to receive, but does not want to receive at this time.
可选接口标识符参数包含一个接口标识符整数列表，用于索引发送ASP配置/注册为接收但此时不希望接收的应用程序服务器流量。
The ASP Inactive (ASPIA) Ack message is used to acknowledge an ASP Inactive message received from a remote M2UA peer.
ASP Inactive（ASPIA）Ack消息用于确认从远程M2UA对等方接收到的ASP Inactive消息。
The ASPIA Ack message contains the following parameters:
ASPIA Ack消息包含以下参数：
Interface Identifiers (optional) - Combination of integer and integer ranges, OR - string (text formatted) INFO String (optional)
接口标识符（可选）-整数和整数范围的组合，或-字符串（文本格式）信息字符串（可选）
The format for the ASPIA Ack message is as follows:
ASPIA Ack消息的格式如下：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x1=integer) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Interface Identifiers* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x8=integer range) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Start1* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Stop1* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Start2* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Stop2* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. .
. .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier StartN* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier StopN* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Additional Interface Identifiers /
/ of Tag Type 0x1 or 0x8 \
\ /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ INFO String* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x1=integer) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Interface Identifiers* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x8=integer range) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Start1* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Stop1* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Start2* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Stop2* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. .
. .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier StartN* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier StopN* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Additional Interface Identifiers /
/ of Tag Type 0x1 or 0x8 \
\ /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ INFO String* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format for the ASP Inactive Ack message using text formatted (string) Interface Identifiers is as follows:
使用文本格式（字符串）接口标识符的ASP非活动确认消息的格式如下：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x3=string) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Interface Identifier* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Additional Interface Identifiers /
/ of Tag Type 0x3 \
\ /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ INFO String* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x3=string) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Interface Identifier* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Additional Interface Identifiers /
/ of Tag Type 0x3 \
\ /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ INFO String* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format of the optional Interface Identifier parameter is the same as for the ASP Active message (See Section 3.3.2.7).
可选接口标识符参数的格式与ASP活动消息的格式相同（见第3.3.2.7节）。
The format and description of the optional Info String parameter is the same as for the ASP Up message (See Section 3.3.2.1).
可选信息字符串参数的格式和说明与ASP Up消息的格式和说明相同（见第3.3.2.1节）。
The Error (ERR) message is used to notify a peer of an error event associated with an incoming message. For example, the message type might be unexpected given the current state, or a parameter value might be invalid.
错误（ERR）消息用于通知对等方与传入消息关联的错误事件。例如，给定当前状态，消息类型可能是意外的，或者参数值可能无效。
An Error message MUST not be generated in response to other Error messages.
不得生成错误消息以响应其他错误消息。
The ERR message contains the following parameters:
ERR消息包含以下参数：
Error Code (mandatory) Interface Identifier (optional) Diagnostic Information (optional)
错误代码（必需）接口标识符（可选）诊断信息（可选）
The format for the ERR message is as follows:
ERR消息的格式如下所示：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0xc) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Error Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x1, 0x3, or 0x8) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Interface Identifier(s)* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x7) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Diagnostic Information* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0xc) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Error Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x1, 0x3, or 0x8) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Interface Identifier(s)* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x7) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Diagnostic Information* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Error Code parameter indicates the reason for the Error Message. The Error parameter value can be one of the following values:
Error Code参数指示错误消息的原因。错误参数值可以是以下值之一：
Invalid Version 0x1 Invalid Interface Identifier 0x2 Unsupported Message Class 0x3 Unsupported Message Type 0x4 Unsupported Traffic Handling Mode 0x5 Unexpected Message 0x6 Protocol Error 0x7 Unsupported Interface Identifier Type 0x8 Invalid Stream Identifier 0x9 Not Used in M2UA 0xa Not Used in M2UA 0xb Not Used in M2UA 0xc Refused - Management Blocking 0xd ASP Identifier Required 0xe Invalid ASP Identifier 0xf ASP Active for Interface Identifier(s) 0x10 Invalid Parameter Value 0x11 Parameter Field Error 0x12 Unexpected Parameter 0x13 Not Used in M2UA 0x14 Not Used in M2UA 0x15 Missing Parameter 0x16
无效版本0x1无效接口标识符0x2不支持的消息类0x3不支持的消息类型0x4不支持的流量处理模式0x5意外消息0x6协议错误0x7不支持的接口标识符类型0x8无效流标识符0x9未在M2UA中使用0xa未在M2UA中使用0xb未在M2UA中使用0xc拒绝-管理阻塞0xd ASP标识符必需0xe无效ASP标识符0xf ASP活动接口标识符0x10无效参数值0x11参数字段错误0x12意外参数0x13未在M2UA中使用0x14未在M2UA中使用0x15缺少参数0x16
The "Invalid Version" error would be sent if a message was received with an invalid or unsupported version. The Error message would contain the supported version in the Common header. The Error message could optionally provide the supported version in the Diagnostic Information area.
如果收到的消息版本无效或不受支持，则会发送“无效版本”错误。错误消息将在公共标头中包含受支持的版本。错误消息可以在诊断信息区域提供支持的版本。
The "Invalid Interface Identifier" error would be sent by a SGP if an ASP sends a message (i.e. an ASP Active message) with an invalid (not configured) Interface Identifier value. One of the optional Interface Identifier parameters (Integer-based, text-based or integer range) MUST be used with this error code to identify the invalid Interface Identifier(s) received.
如果ASP发送带有无效（未配置）接口标识符值的消息（即ASP活动消息），则SGP将发送“无效接口标识符”错误。此错误代码必须使用一个可选接口标识符参数（基于整数、基于文本或整数范围）来标识接收到的无效接口标识符。
The "Unsupported Traffic Handling Mode" error would be sent by a SGP if an ASP sends an ASP Active with an unsupported Traffic Handling Mode. An example would be a case in which the SGP did not support load-sharing. One of the optional Interface Identifier parameters (Integer-based, text-based or integer range) MAY be used with this error code to identify the Interface Identifier(s).
如果ASP以不支持的流量处理模式发送ASP活动，则SGP将发送“不支持的流量处理模式”错误。例如，SGP不支持负载共享。可选接口标识符参数之一（基于整数、基于文本或整数范围）可与此错误代码一起使用，以标识接口标识符。
The "Unexpected Message" error would be sent by an ASP if it received a MAUP message from an SGP while it was in the Inactive state.
如果ASP在非活动状态下收到来自SGP的MAUP消息，则ASP将发送“意外消息”错误。
The "Protocol Error" error would be sent for any protocol anomaly (i.e. a bogus message).
任何协议异常（即虚假消息）都会发送“协议错误”错误。
The "Invalid Stream Identifier" error would be sent if a message was received on an unexpected SCTP stream (i.e. a MGMT message was received on a stream other than "0").
如果在意外的SCTP流上接收到消息（即，在“0”以外的流上接收到管理消息），则将发送“无效流标识符”错误。
The "Unsupported Interface Identifier Type" error would be sent by a SGP if an ASP sends a Text formatted Interface Identifier and the SGP only supports Integer formatted Interface Identifiers. When the ASP receives this error, it will need to resend its message with an Integer formatted Interface Identifier.
如果ASP发送文本格式的接口标识符，且SGP仅支持整数格式的接口标识符，则SGP将发送“不支持的接口标识符类型”错误。当ASP收到此错误时，需要使用整数格式的接口标识符重新发送其消息。
The "Unsupported Message Class" error would be sent if a message with an unexpected or unsupported Message Class is received.
如果收到包含意外或不支持的消息类的消息，则会发送“不支持的消息类”错误。
The "Refused - Management Blocking" error is sent when an ASP Up or ASP Active message is received and the request is refused for management reasons (e.g., management lock-out").
当收到ASP Up或ASP Active消息并且由于管理原因（例如，管理锁定）拒绝请求时，将发送“拒绝-管理阻止”错误。
The "ASP Identifier Required" is sent by a SGP in response to an ASPUP message which does not contain an ASP Identifier parameter when the SGP requires one. The ASP SHOULD resend the ASPUP message with an ASP Identifier.
当SGP需要ASP标识符参数时，“需要ASP标识符”由SGP发送，以响应不包含ASP标识符参数的ASPUP消息。ASP应使用ASP标识符重新发送ASPUP消息。
The "Invalid ASP Identifier" is sent by a SGP in response to an ASPUP message with an invalid (i.e. non-unique) ASP Identifier.
“无效ASP标识符”由SGP发送，以响应带有无效（即非唯一）ASP标识符的ASPUP消息。
The "ASP Currently Active for Interface Identifier(s)" error is sent by a SGP when a Deregistration request is received from an ASP that is active for Interface Identifier(s) specified in the Deregistration request. One of the optional Interface Identifier parameters (Integer-based, text-based or integer range) MAY be used with this error code to identify the Interface Identifier(s).
当从针对撤销注册请求中指定的接口标识符处于活动状态的ASP收到撤销注册请求时，SGP会发送“ASP当前针对接口标识符处于活动状态”错误。可选接口标识符参数之一（基于整数、基于文本或整数范围）可与此错误代码一起使用，以标识接口标识符。
The "Invalid Parameter Value " error is sent if a message is received with an invalid parameter value (e.g., a State Request with an an undefined State).
如果收到具有无效参数值的消息（例如，具有未定义状态的状态请求），则会发送“无效参数值”错误。
The "Parameter Field Error" would be sent if a message with a parameter has a wrong length field.
如果带有参数的消息的字段长度错误，则会发送“参数字段错误”。
The "Unexpected Parameter" error would be sent if a message contains an invalid parameter.
如果消息包含无效参数，将发送“意外参数”错误。
The "Missing Parameter" error would be sent if a mandatory parameter was not included in a message.
如果消息中未包含强制参数，则会发送“缺少参数”错误。
The optional Diagnostic information can be any information germane to the error condition, to assist in the identification of the error condition. In the case of an Invalid Version Error Code the Diagnostic information includes the supported Version parameter. In the other cases, the Diagnostic information SHOULD be the first 40 bytes of the offending message.
可选诊断信息可以是与错误状况相关的任何信息，以帮助识别错误状况。在版本错误代码无效的情况下，诊断信息包括支持的版本参数。在其他情况下，诊断信息应为违规消息的前40个字节。
The Notify message is used to provide an autonomous indication of M2UA events to an M2UA peer.
Notify消息用于向M2UA对等方提供M2UA事件的自主指示。
The NTFY message contains the following parameters:
NTFY消息包含以下参数：
Status Type (mandatory) Status Information (mandatory) ASP Identifier (optional) Interface Identifiers (optional) INFO String (optional)
状态类型（必需）状态信息（必需）ASP标识符（可选）接口标识符（可选）信息字符串（可选）
The format for the Notify message with Integer-formatted Interface Identifiers is as follows:
带有整数格式接口标识符的Notify消息的格式如下：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0xd) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Status Type | Status Information |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x11) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ASP Identifier* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x1=integer) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Interface Identifiers* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x8=integer range) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Start1* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Stop1* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Start2* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Stop2* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. .
. .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier StartN* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier StopN* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Additional Interface Identifiers /
/ of Tag Type 0x1 or 0x8 \
\ /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ INFO String* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0xd) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Status Type | Status Information |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x11) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ASP Identifier* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x1=integer) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Interface Identifiers* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x8=integer range) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Start1* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Stop1* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Start2* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Stop2* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. .
. .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier StartN* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier StopN* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Additional Interface Identifiers /
/ of Tag Type 0x1 or 0x8 \
\ /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ INFO String* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format for the Notify message with Text-formatted Interface Identifiers is as follows:
带有文本格式接口标识符的Notify消息的格式如下：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0xd) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Status Type | Status Information |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x11) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ASP Identifier* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x3=string) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Interface Identifier* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Additional Interface Identifiers /
/ of Tag Type 0x3 \
\ /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ INFO String* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0xd) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Status Type | Status Information |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x11) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ASP Identifier* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x3=string) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Interface Identifier* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ Additional Interface Identifiers /
/ of Tag Type 0x3 \
\ /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ INFO String* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Status Type parameter identifies the type of the Notify message. The following are the valid Status Type values:
Status Type参数标识通知消息的类型。以下是有效的状态类型值：
Value Description 0x1 Application Server state change (AS_State_Change) 0x2 Other
值说明0x1应用程序服务器状态更改（作为状态更改）0x2其他
The Status Information parameter contains more detailed information for the notification, based on the value of the Status Type. If the Status Type is AS_State_Change the following Status Information values are used:
Status Information参数根据状态类型的值包含通知的更详细信息。如果状态类型为AS_State_Change，则使用以下状态信息值：
Value Description 1 reserved 2 Application Server Inactive (AS_Inactive) 3 Application Server Active (AS_Active) 4 Application Server Pending (AS_Pending)
值说明1保留2应用程序服务器不活动（AS_不活动）3应用程序服务器活动（AS_活动）4应用程序服务器挂起（AS_挂起）
These notifications are sent from an SGP to an ASP upon a change in status of a particular Application Server. The value reflects the new state of the Application Server. The Interface Identifiers of the AS MAY be placed in the message if desired.
这些通知在特定应用程序服务器的状态发生变化时从SGP发送到ASP。该值反映应用程序服务器的新状态。如果需要，可以将AS的接口标识符放置在消息中。
If the Status Type is Other, then the following Status Information values are defined:
如果状态类型为“其他”，则定义以下状态信息值：
Value Description 1 Insufficient ASP resources active in AS 2 Alternate ASP Active 3 ASP Failure
值说明1活动的ASP资源不足，如2备用ASP活动3 ASP失败
In the Insufficient ASP Resources case, the SGP is indicating to an ASP-INACTIVE ASP(s) in the AS that another ASP is required in order to handle the load of the AS (Load-sharing mode). For the Alternate ASP Active case, the formerly Active ASP is informed when an alternate ASP transitions to the ASP Active state in Override mode. The ASP Identifier (if available) of the Alternate ASP MUST be placed in the message. For the ASP Failure case, the SGP is indicating to ASP(s) in the AS that one of the ASPs has transitioned to ASP-DOWN. The ASP Identifier (if available) of the failed ASP MUST be placed in the message.
在ASP资源不足的情况下，SGP向AS中的ASP-非活动ASP指示需要另一个ASP来处理AS的负载（负载共享模式）。对于备用ASP活动情况，当备用ASP在覆盖模式下转换为ASP活动状态时，会通知以前处于活动状态的ASP。备用ASP的ASP标识符（如果可用）必须放在消息中。对于ASP失败案例，SGP向AS中的ASP指示其中一个ASP已转换为ASP-DOWN。失败ASP的ASP标识符（如果可用）必须放在消息中。
For each of the Status Information values in Status Type Other, the Interface Identifiers of the affected AS MAY be placed in the message if desired.
对于Status Type Other中的每个状态信息值，如果需要，可以将受影响AS的接口标识符放置在消息中。
The format of the optional Interface Identifier parameter is the same as for the ASP Active message (See Section 3.3.2.7).
可选接口标识符参数的格式与ASP活动消息的格式相同（见第3.3.2.7节）。
The format and description of the optional Info String parameter is the same as for the ASP Up message (See Section 3.3.2.1).
可选信息字符串参数的格式和说明与ASP Up消息的格式和说明相同（见第3.3.2.1节）。
The Interface Identifier Management messages are optional. They are used to support the automatic allocation of Signalling Terminals or Signalling Data Links [2][3].
接口标识符管理消息是可选的。它们用于支持自动分配信令终端或信令数据链路[2][3]。
The REG REQ message is sent by an ASP to indicate to a remote M2UA peer that it wishes to register one or more given Link Keys with the remote peer. Typically, an ASP would send this message to an SGP, and expect to receive a REG RSP in return with an associated Interface Identifier value.
REG REQ消息由ASP发送，以指示远程M2UA对等方它希望向远程对等方注册一个或多个给定链接密钥。通常，ASP会将此消息发送给SGP，并期望收到REG RSP以及相关接口标识符值。
The REG REQ message contains the following parameter:
REG REQ消息包含以下参数：
Link Key (mandatory)
链接键（强制）
The format for the REG REQ message is as follows
REG REQ消息的格式如下
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0309 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ Link Key 1 /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ ... /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0309 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ Link Key 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0309 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ Link Key 1 /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ ... /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0309 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ Link Key n /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Link Key: fixed length
链接键：固定长度
The Link Key parameter is mandatory. The sender of this message expects that the receiver of this message will create a Link Key entry and assign a unique Interface Identifier value to it, if the Link Key entry does not yet exist.
Link Key参数是必需的。如果链接密钥条目尚不存在，则此消息的发送方希望此消息的接收方创建链接密钥条目并为其分配唯一的接口标识符值。
The Link Key parameter may be present multiple times in the same message. This is used to allow the registration of multiple Link Keys in a single message.
链路键参数可能在同一消息中出现多次。这用于允许在单个消息中注册多个链接密钥。
The format of the Link Key parameter is as follows:
Link Key参数的格式如下：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local-LK-Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Signalling Data Terminal Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Signalling Data Link Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local-LK-Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Signalling Data Terminal Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Signalling Data Link Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Local-LK-Identifier: 32-bit integer
本地LK标识符：32位整数
The mandatory Local-LK-Identifier field is used to uniquely (between ASP and SGP) identify the registration request. The Identifier value is assigned by the ASP, and is used to correlate the response in a REG RSP message with the original registration request. The Identifier value MUST remain unique until the REG RSP is received.
强制本地LK标识符字段用于唯一地（在ASP和SGP之间）标识注册请求。标识符值由ASP分配，用于将REG RSP消息中的响应与原始注册请求关联。在收到REG RSP之前，标识符值必须保持唯一。
The format of the Local-LK-Identifier field is as follows:
本地LK标识符字段的格式如下：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x030a | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local-LK-Identifier 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x030a | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local-LK-Identifier value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Signalling Data Terminal Identifier
信令数据终端标识符
The Signalling Data Terminal Identifier parameter is mandatory. It identifies the Signalling Data Terminal associated with the SS7 link for which the ASP is registering. The format is as follows:
信令数据终端标识符参数是必需的。它标识与ASP正在注册的SS7链路相关联的信令数据终端。格式如下:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x030b | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | SDT Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x030b | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | SDT Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The SDT Identifier is a 32-bit unsigned value which may only be significant to 12 or 14 bits depending on the SS7 variant which is supported by the MTP Level 3 at the ASP. Insignificant SDT Identifier bits are coded 0.
SDT标识符是一个32位无符号值，根据ASP的MTP级别3支持的SS7变量，该值可能仅对12位或14位有效。不重要的SDT标识符位编码为0。
Signalling Data Link Identifier
信令数据链路标识符
The Signalling Data Link Identifier parameter is mandatory. It identifies the Signalling Data Link Identifier associated with the SS7 link for which the ASP is registering. The format is as follows:
信令数据链路标识符参数是必需的。它标识与ASP正在注册的SS7链路相关联的信令数据链路标识符。格式如下:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x030c | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | SDL Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x030c | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | SDL Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The SDL Identifier is a 32-bit unsigned value which may only be significant to 12 or 14 bits depending on the SS7 variant which is supported by the MTP Level 3 at the ASP. Insignificant SDLI bits are coded 0.
SDL标识符是一个32位无符号值，根据ASP的MTP级别3支持的SS7变量，该值可能仅对12位或14位有效。不重要的SDLI位编码为0。
The REG RSP message is used as a response to the REG REQ message from a remote M2UA peer. It contains indications of success/failure for registration requests and returns a unique Interface Identifier value for successful registration requests, to be used in subsequent M2UA Traffic Management protocol.
REG RSP消息用作远程M2UA对等方对REG REQ消息的响应。它包含注册请求成功/失败的指示，并返回成功注册请求的唯一接口标识符值，用于后续M2UA流量管理协议。
The REG RSP message contains the following parameter:
REG RSP消息包含以下参数：
Registration Results (mandatory)
注册结果（强制性）
The format for the REG RSP message is as follows:
REG RSP报文格式如下：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x030d | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ Registration Result 1 /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ ... /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x030d | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ Registration Result 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x030d | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ Registration Result 1 /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ ... /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x030d | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ Registration Result n /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Registration Results: fixed length
注册结果：固定长度
The Registration Results parameter contains one or more results, each containing the registration status for a single Link Key in the REG REQ message. The number of results in a single REG RSP message MAY match the number of Link Key parameters found in the corresponding REG REQ message. The format of each result is as follows:
Registration Results参数包含一个或多个结果，每个结果都包含REG REQ消息中单个链接密钥的注册状态。单个REG RSP消息中的结果数量可能与相应REG REQ消息中的链路密钥参数数量相匹配。每个结果的格式如下：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local-LK-Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Registration Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local-LK-Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Registration Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Local-LK-Identifier: 32-bit integer
本地LK标识符：32位整数
The Local-LK-Identifier contains the same value as found in the matching Link Key parameter found in the REG REQ message. The format of the Local-LK-Identifier is shown in Section 3.3.4.1.
本地LK标识符包含与REG REQ消息中的匹配链路密钥参数相同的值。本地LK标识符的格式如第3.3.4.1节所示。
Registration Status: 32-bit integer
注册状态：32位整数
The Registration Result Status field indicates the success or the reason for failure of a registration request.
注册结果状态字段指示注册请求成功或失败的原因。
Its values may be one of the following:
其值可以是以下值之一：
0 Successfully Registered 1 Error - Unknown 2 Error - Invalid SDLI 3 Error - Invalid SDTI 4 Error - Invalid Link Key 5 Error - Permission Denied 6 Error - Overlapping (Non-unique) Link Key 7 Error - Link Key not Provisioned 8 Error - Insufficient Resources
0成功注册1错误-未知2错误-无效SDLI 3错误-无效SDTI 4错误-无效链接密钥5错误-权限被拒绝6错误-重叠（非唯一）链接密钥7错误-未设置链接密钥8错误-资源不足
The format of the Registration Status field 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x030e | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Registration Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x030e | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Registration Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Interface Identifier: 32-bit integer
接口标识符：32位整数
The Interface Identifier field contains the Interface Identifier for the associated Link Key if the registration is successful. It is set to "0" if the registration was not successful. The format of integer-based and text-based Interface Identifier parameters are shown in Section 3.2.
如果注册成功，接口标识符字段包含关联链接密钥的接口标识符。如果注册未成功，则将其设置为“0”。基于整数和基于文本的接口标识符参数的格式见第3.2节。
The DEREG REQ message is sent by an ASP to indicate to a remote M2UA peer that it wishes to de-register a given Interface Identifier. Typically, an ASP would send this message to an SGP, and expects to receive a DEREG RSP in return reflecting the Interface Identifier and containing a de-registration status.
DEREG REQ消息由ASP发送，以指示远程M2UA对等方希望取消注册给定接口标识符。通常，ASP会将此消息发送给SGP，并期望收到一个反映接口标识符并包含取消注册状态的撤销RSP作为回报。
The DEREG REQ message contains the following parameter:
DEREG REQ消息包含以下参数：
Interface Identifier (mandatory)
接口标识符（必需）
The format for the DEREG REQ message is as follows:
DEREG REQ消息的格式如下：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x1 or 0x3 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ Interface Identifier 1 /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ ... /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x1 or 0x3 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ Interface Identifier 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x1 or 0x3 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ Interface Identifier 1 /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ ... /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x1 or 0x3 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ Interface Identifier n /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Interface Identifier
接口标识符
The Interface Identifier parameter contains a Interface Identifier indexing the Application Server traffic that the sending ASP is currently registered to receive from the SGP but now wishes to de-register. The format of integer-based and text-based Interface Identifier parameters are shown in Section 3.2.
Interface Identifier参数包含一个接口标识符，用于索引发送ASP当前注册为从SGP接收但现在希望取消注册的应用程序服务器通信量。基于整数和基于文本的接口标识符参数的格式见第3.2节。
The DEREG RSP message is used as a response to the DEREG REQ message from a remote M2UA peer.
DEREG RSP消息用作远程M2UA对等方对DEREG REQ消息的响应。
The DEREG RSP message contains the following parameter:
DEREG RSP消息包含以下参数：
De-Registration Results (mandatory)
注销结果（强制）
The format for the DEREG RSP message is as follows:
DEREG RSP报文格式如下：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x030f | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ De-Registration Result 1 /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ ... /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x030f | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ De-Registration Result 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x030f | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ De-Registration Result 1 /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ ... /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x030f | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ De-Registration Result n /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
De-Registration Results: fixed length
取消注册结果：固定长度
The De-Registration Results parameter contains one or more results, each containing the de-registration status for a single Interface Identifier in the DEREG REQ message. The number of results in a single DEREG RSP message MAY match the number of Interface Identifier parameters found in the corresponding DEREG REQ message. The format of each result is as follows:
“取消注册结果”参数包含一个或多个结果，每个结果都包含DEREG REQ消息中单个接口标识符的取消注册状态。单个DEREG RSP消息中的结果数量可能与相应DEREG REQ消息中的接口标识符参数数量相匹配。每个结果的格式如下：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| De-Registration Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| De-Registration Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Interface Identifier: 32-bit integer
接口标识符：32位整数
The Interface Identifier field contains the Interface Identifier value of the matching Link Key to de-register, as found in the DEREG REQ. The format of integer-based and text-based Interface Identifier parameters are shown in Section 3.2.
Interface Identifier（接口标识符）字段包含要注销的匹配链接密钥的接口标识符值，如DEREG REQ中所示。基于整数和基于文本的接口标识符参数的格式见第3.2节。
De-Registration Status: 32-bit integer
取消注册状态：32位整数
The De-Registration Result Status field indicates the success or the reason for failure of the de-registration.
注销结果状态字段指示注销成功或失败的原因。
Its values may be one of the following:
其值可以是以下值之一：
0 Successfully De-registered 1 Error - Unknown 2 Error - Invalid Interface Identifier 3 Error - Permission Denied 4 Error - Not Registered
0已成功取消注册1错误-未知2错误-无效接口标识符3错误-权限被拒绝4错误-未注册
The format of the De-Registration Status field 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0310 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| De-Registration Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0310 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| De-Registration Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The M2UA layer needs to respond to various primitives it receives from other layers as well as messages it receives from the peer-to-peer messages. This section describes various procedures involved in response to these events.
M2UA层需要响应从其他层接收的各种原语以及从对等消息接收的消息。本节描述了应对这些事件所涉及的各种程序。
These procedures achieve the M2UA layer "Transport of MTP Level 2 / MTP Level 3 boundary" service.
这些程序实现M2UA层“MTP 2级/MTP 3级边界传输”服务。
On receiving a primitive from the local upper layer, the M2UA layer will send the corresponding MAUP message (see Section 3) to its peer. The M2UA layer MUST fill in various fields of the common and specific headers correctly. In addition the message SHOULD be sent on the SCTP stream that corresponds to the SS7 link.
从本地上层接收到原语后，M2UA层将向其对等方发送相应的MAUP消息（参见第3节）。M2UA层必须正确填写公共和特定标头的各个字段。此外，应在对应于SS7链路的SCTP流上发送消息。
On receiving MAUP messages from a peer M2UA layer, the M2UA layer on an SG or MGC needs to invoke the corresponding layer primitives to the local MTP Level 2 or MTP Level 3 layer.
从对等M2UA层接收MAUP消息时，SG或MGC上的M2UA层需要调用本地MTP级别2或MTP级别3层的相应层原语。
On receiving primitives from the local Layer Management, the M2UA layer will take the requested action and provide an appropriate response primitive to Layer Management.
从本地层管理接收原语后，M2UA层将采取请求的操作，并向层管理提供适当的响应原语。
An M-SCTP_ESTABLISH request primitive from Layer Management at an ASP will initiate the establishment of an SCTP association. The M2UA layer will attempt to establish an SCTP association with the remote M2UA peer by sending an SCTP-ASSOCIATE primitive to the local SCTP layer.
来自ASP层管理的M-SCTP_建立请求原语将启动SCTP关联的建立。M2UA层将通过向本地SCTP层发送SCTP-ASSOCIATE原语，尝试与远程M2UA对等方建立SCTP关联。
When an SCTP association has been successfully established, the SCTP will send an SCTP-COMMUNICATION_UP notification primitive to the local M2UA layer. At the SGP that initiated the request, the M2UA layer will send an M-SCTP_ESTABLISH confirm primitive to Layer Management when the association setup is complete. At the peer M2UA layer, an M-SCTP_ESTABLISH indication primitive is sent to Layer Management upon successful completion of an incoming SCTP association setup.
成功建立SCTP关联后，SCTP将向本地M2UA层发送SCTP-COMMUNICATION_UP通知原语。在发起请求的SGP处，当关联设置完成时，M2UA层将向层管理发送一个M-SCTP_建立确认原语。在对等M2UA层，成功完成传入SCTP关联设置后，M-SCTP_建立指示原语被发送到层管理。
An M-SCTP_RELEASE request primitive from Layer Management initiates the shutdown of an SCTP association. The M2UA layer accomplishes a graceful shutdown of the SCTP association by sending an SCTP-SHUTDOWN primitive to the SCTP layer.
来自层管理的M-SCTP_释放请求原语启动SCTP关联的关闭。M2UA层通过向SCTP层发送SCTP-shutdown原语来完成SCTP关联的正常关闭。
When the graceful shutdown of the SCTP association has been accomplished, the SCTP layer returns an SCTP-SHUTDOWN_COMPLETE notification primitive to the local M2UA layer. At the M2UA Layer that initiated the request, the M2UA layer will send an M-SCTP_RELEASE confirm primitive to Layer Management when the association shutdown is complete. At the peer M2UA Layer, an M-SCTP_RELEASE indication primitive is sent to Layer Management upon abort or successful shutdown of an SCTP association.
当SCTP关联的正常关闭完成后，SCTP层向本地M2UA层返回SCTP-shutdown_COMPLETE通知原语。在发起请求的M2UA层，当关联关闭完成时，M2UA层将向层管理发送一个M-SCTP_RELEASE confirm原语。在对等M2UA层，当SCTP关联中止或成功关闭时，M-SCTP_释放指示原语被发送到层管理。
An M-SCTP_STATUS request primitive supports a Layer Management query of the local status of a particular SCTP association. The M2UA layer simply maps the M-SCTP_STATUS request primitive to an SCTP-STATUS primitive to the SCTP layer. When the SCTP responds, the M2UA layer maps the association status information to an M-SCTP_STATUS confirm primitive. No peer protocol is invoked.
M-SCTP_状态请求原语支持对特定SCTP关联的本地状态的层管理查询。M2UA层只是将M-SCTP_状态请求原语映射到SCTP层的SCTP-STATUS原语。当SCTP响应时，M2UA层将关联状态信息映射到M-SCTP_状态确认原语。没有调用对等协议。
Similar LM-to-M2UA-to-SCTP and/or SCTP-to-M2UA-to-LM primitive mappings can be described for the various other SCTP Upper Layer primitives in RFC 2960 [8] such as INITIALIZE, SET PRIMARY, CHANGE HEARTBEAT, REQUEST HEARTBEAT, GET SRTT REPORT, SET FAILURE THRESHOLD, SET PROTOCOL PARAMETERS, DESTROY SCTP INSTANCE, SEND FAILURE, AND NETWORK STATUS CHANGE. Alternatively, these SCTP Upper Layer
对于RFC 2960[8]中的各种其他SCTP上层原语，可以描述类似的LM-to-M2UA-to-SCTP和/或SCTP-to-M2UA-to-LM原语映射，例如初始化、设置主要、更改心跳、请求心跳、获取SRTT报告、设置故障阈值、设置协议参数、销毁SCTP实例、发送故障、，以及网络状态的变化。或者，这些SCTP位于上层
primitives (and Status as well) can be considered for modeling purposes as a Layer Management interaction directly with the SCTP Layer.
原语（以及状态）可以考虑作为直接与SCTP层的层管理交互进行建模。
M-NOTIFY indication and M-ERROR indication primitives indicate to Layer Management the notification or error information contained in a received M2UA Notify or Error message respectively. These indications can also be generated based on local M2UA events.
M-NOTIFY指示和M-ERROR指示原语分别向层管理层指示接收到的M2UA NOTIFY或ERROR消息中包含的通知或错误信息。也可以根据本地M2UA事件生成这些指示。
An M-ASP_STATUS request primitive supports a Layer Management query of the status of a particular local or remote ASP. The M2UA layer responds with the status in an M-ASP_STATUS confirm primitive. No M2UA peer protocol is invoked.
M-ASP_状态请求原语支持对特定本地或远程ASP的状态进行层管理查询。M2UA层以M-ASP_状态确认原语中的状态进行响应。未调用M2UA对等协议。
An M-AS_STATUS request supports a Layer Management query of the status of a particular AS. The M2UA responds with an M-AS_STATUS confirm primitive. No M2UA peer protocol is invoked.
M-AS_状态请求支持对特定AS状态的层管理查询。M2UA使用M-AS_状态确认原语进行响应。未调用M2UA对等协议。
M-ASP_UP request, M-ASP_DOWN request, M-ASP_ACTIVE request and M-ASP_INACTIVE request primitives allow Layer Management at an ASP to initiate state changes. Upon successful completion, a corresponding confirm primitive is provided by the M2UA layer to Layer Management. If an invocation is unsuccessful, an Error indication primitive is provided in the primitive. These requests result in outgoing ASP Up, ASP Down, ASP Active and ASP Inactive messages to the remote M2UA peer at an SGP.
M-ASP_向上请求、M-ASP_向下请求、M-ASP_活动请求和M-ASP_非活动请求原语允许ASP的层管理启动状态更改。成功完成后，M2UA层对层管理提供相应的确认原语。如果调用失败，则在原语中提供错误指示原语。这些请求会将ASP Up、ASP Down、ASP Active和ASP Inactive消息发送到SGP上的远程M2UA对等方。
Upon successful state changes resulting from reception of ASP Up, ASP Down, ASP Active and ASP Inactive messages from a peer M2UA, the M2UA layer SHOULD invoke corresponding M-ASP_UP, M-ASP_DOWN, M-ASP_ACTIVE and M-ASP_INACTIVE, M-AS_ACTIVE, M-AS_INACTIVE, and M-AS_DOWN indication primitives to the local Layer Management.
在从对等M2UA接收到ASP Up、ASP Down、ASP Active和ASP Inactive消息后，M2UA层应向本地层管理调用相应的M-ASP_Up、M-ASP_Down、M-ASP_Active和M-ASP_Inactive、M-AS_Active和M-AS_Down指示原语。
M-NOTIFY indication and M-ERROR indication primitives indicate to Layer Management the notification or error information contained in a received M2UA Notify or Error message. These indications can also be generated based on local M2UA events.
M-NOTIFY指示和M-ERROR指示原语向层管理层指示接收到的M2UA NOTIFY或ERROR消息中包含的通知或错误信息。也可以根据本地M2UA事件生成这些指示。
All MGMT messages, except BEAT and BEAT Ack, SHOULD be sent with sequenced delivery to ensure ordering. All MGMT messages, with the exception of ASPTM, BEAT and BEAT Ack messages, SHOULD be sent on SCTP stream '0'. All ASPTM messages SHOULD be sent on the stream which normally carries the data traffic to which the message applies. BEAT and BEAT Ack messages MAY be sent using out-of-order delivery, and MAY be sent on any stream.
除BEAT和BEAT Ack外，所有管理信息均应按顺序发送，以确保订购。除ASPTM、BEAT和BEAT Ack消息外，所有管理消息都应在SCTP流“0”上发送。所有ASPTM消息应在通常承载消息所适用的数据流量的流上发送。BEAT和BEAT Ack消息可以使用无序交付发送，并且可以在任何流上发送。
The M2UA layer on the SGP maintains the state of each remote ASP, in each Application Server that the ASP is configured to receive traffic, as input to the M2UA message distribution function.
SGP上的M2UA层维护每个远程ASP的状态，在每个应用服务器中，ASP被配置为接收流量，作为M2UA消息分发功能的输入。
The state of each remote ASP, in each AS that it is configured to operate, is maintained in the M2UA layer in the SGP. The state of a particular ASP in a particular AS changes due to events. The events include:
在SGP的M2UA层中维护每个远程ASP在其配置为运行的每个AS中的状态。由于事件而改变的特定ASP在特定ASP中的状态。这些活动包括：
* Reception of messages from the peer M2UA layer at the ASP; * Reception of some messages from the peer M2UA layer at other ASPs in the AS (e.g., ASP Active message indicating "Override"); * Reception of indications from the SCTP layer; or * Local Management intervention.
* 从ASP的对等M2UA层接收消息；*在AS中的其他ASP接收来自对等M2UA层的一些消息（例如，ASP活动消息指示“覆盖”）；*接收来自SCTP层的指示；或*地方管理干预。
The ASP state transition diagram is shown in Figure 5. The possible states of an ASP are:
ASP状态转换图如图5所示。ASP的可能状态为：
ASP-DOWN: The remote M2UA peer at the ASP is unavailable and/or the related SCTP association is down. Initially all ASPs will be in this state. An ASP in this state SHOULD NOT be sent any M2UA messages, with the exception of Heartbeat, ASP Down Ack and Error messages.
ASP-DOWN：ASP上的远程M2UA对等机不可用和/或相关SCTP关联已关闭。最初，所有ASP都将处于此状态。处于此状态的ASP不应发送任何M2UA消息，心跳、ASP停机确认和错误消息除外。
ASP-INACTIVE: The remote M2UA peer at the ASP is available (and the related SCTP association is up) but application traffic is stopped. In this state the ASP MAY be sent any non-MAUP M2UA messages.
ASP-INACTIVE：ASP上的远程M2UA对等机可用（且相关SCTP关联已启动），但应用程序通信已停止。在此状态下，ASP可发送任何非MAUP M2UA消息。
ASP-ACTIVE: The remote M2UA peer at the ASP is available and application traffic is active (for a particular Interface Identifier or set of Interface Identifiers).
ASP-ACTIVE：ASP上的远程M2UA对等点可用，并且应用程序流量处于活动状态（对于特定接口标识符或一组接口标识符）。
Figure 5: ASP State Transition Diagram
图5:ASP状态转换图
+--------------+
| ASP-ACTIVE |
+----------------------| |
| Other +-------| |
| ASP in AS | +--------------+
| Overrides | ^ |
| | ASP | | ASP
| | Active | | Inactive
| | | v
| | +--------------+
| | | |
| +------>| ASP-INACTIVE |
| +--------------+
| ^ |
ASP Down/ | ASP | | ASP Down /
SCTP CDI/ | Up | | SCTP CDI/
SCTP RI | | v SCTP RI
| +--------------+
| | |
+--------------------->| ASP-DOWN |
| |
+--------------+
+--------------+
| ASP-ACTIVE |
+----------------------| |
| Other +-------| |
| ASP in AS | +--------------+
| Overrides | ^ |
| | ASP | | ASP
| | Active | | Inactive
| | | v
| | +--------------+
| | | |
| +------>| ASP-INACTIVE |
| +--------------+
| ^ |
ASP Down/ | ASP | | ASP Down /
SCTP CDI/ | Up | | SCTP CDI/
SCTP RI | | v SCTP RI
| +--------------+
| | |
+--------------------->| ASP-DOWN |
| |
+--------------+
SCTP CDI: The SCTP CDI denotes the local SCTP layer's Communication Down Indication to the Upper Layer Protocol (M2UA) on an SGP. The local SCTP layer will send this indication when it detects the loss of connectivity to the ASP's peer SCTP layer. SCTP CDI is understood as either a SHUTDOWN_COMPLETE notification or COMMUNICATION_LOST notification from the SCTP layer.
SCTP CDI：SCTP CDI表示本地SCTP层与SGP上的上层协议（M2UA）的通信下行指示。当本地SCTP层检测到与ASP对等SCTP层的连接丢失时，将发送此指示。SCTP CDI被理解为来自SCTP层的关机完成通知或通信丢失通知。
SCTP RI: The local SCTP layer's Restart indication to the upper layer protocol (M2UA) on an SG. The local SCTP will send this indication when it detects a restart from the ASP's peer SCTP layer.
SCTP RI：本地SCTP层对SG上上层协议（M2UA）的重启指示。当本地SCTP检测到来自ASP对等SCTP层的重启时，将发送此指示。
The state of the AS is maintained in the M2UA layer on the SGP. The state of an AS changes due to events. These events include:
AS的状态保持在SGP上的M2UA层中。AS的状态因事件而更改。这些活动包括：
* ASP state transitions * Recovery timer triggers
* ASP状态转换*恢复计时器触发器
The possible states of an AS are:
AS的可能状态为：
AS-DOWN: The Application Server is unavailable. This state implies that all related ASPs are in the ASP-DOWN state for this AS. Initially the AS will be in this state. An Application Server MUST be in the AS-DOWN state before it can be removed from a configuration.
AS-DOWN：应用程序服务器不可用。此状态表示此AS的所有相关ASP都处于ASP-DOWN状态。最初，AS将处于此状态。应用程序服务器必须处于AS-DOWN状态才能从配置中删除。
AS-INACTIVE: The Application Server is available but no application traffic is active (i.e., one or more related ASPs are in the ASP-INACTIVE state, but none in the ASP-ACTIVE state). The recovery timer T(r) is not running or has expired.
AS-INACTIVE：应用程序服务器可用，但没有活动的应用程序流量（即，一个或多个相关的ASP处于ASP-INACTIVE状态，但没有处于ASP-active状态）。恢复计时器T（r）未运行或已过期。
AS-ACTIVE: The Application Server is available and application traffic is active. This state implies that at least one ASP is in the ASP-ACTIVE state.
AS-ACTIVE：应用程序服务器可用，且应用程序流量处于活动状态。此状态表示至少有一个ASP处于ASP-ACTIVE状态。
AS-PENDING: An active ASP has transitioned to ASP-INACTIVE or ASP-DOWN and it was the last remaining active ASP in the AS. A recovery timer T(r) SHOULD be started and all incoming signalling messages SHOULD be queued by the SGP. If an ASP becomes ASP-ACTIVE before T(r) expires, the AS is moved to the AS-ACTIVE state and all the queued messages will be sent to the ASP.
AS-PENDING：活动ASP已转换为ASP-INACTIVE或ASP-DOWN，并且它是AS中最后一个剩余的活动ASP。恢复计时器T（r）应启动，所有传入的信令消息应由SGP排队。如果ASP在T（r）到期之前变为ASP-ACTIVE，则AS将移动到AS-ACTIVE状态，并且所有排队的消息都将发送到ASP。
If T(r) expires before an ASP becomes ASP-ACTIVE, the SGP stops queuing messages and discards all previously queued messages. The AS will move to the AS-INACTIVE state if at least one ASP is in the ASP-INACTIVE state, otherwise it will move to the AS-DOWN state.
如果在ASP变为ASP-ACTIVE之前T（r）过期，SGP将停止对消息进行排队，并丢弃所有先前排队的消息。如果至少有一个ASP处于ASP-INACTIVE状态，AS将移到AS-INACTIVE状态，否则它将移到AS-DOWN状态。
Figure 6 shows an example AS state machine for the case where the AS/ASP data is pre-configured. For other cases where the AS/ASP configuration data is created dynamically, there would be differences in the state machine, especially at the creation of the AS.
图6显示了预配置AS/ASP数据情况下的AS状态机示例。对于动态创建AS/ASP配置数据的其他情况，状态机中会存在差异，尤其是在创建AS时。
For example, where the AS/ASP configuration data is not created until Registration of the first ASP, the AS-INACTIVE state is entered directly upon the first successful REG REQ from an ASP. Another example is where the AS/ASP configuration data is not created until the first ASP successfully enters the ASP-ACTIVE state. In this case the AS-ACTIVE state is entered directly.
例如，如果在注册第一个ASP之前不创建AS/ASP配置数据，则在ASP的第一次成功REG REQ时直接进入AS-INACTIVE状态。另一个示例是，在第一个ASP成功进入ASP-ACTIVE状态之前，不会创建AS/ASP配置数据。在这种情况下，直接进入AS-ACTIVE状态。
Figure 6: AS State Transition Diagram
图6:AS状态转换图
+----------+ one ASP trans to ACTIVE +-------------+
| AS- |---------------------------->| AS- |
| INACTIVE | | ACTIVE |
| |<--- | |
+----------+ \ +-------------+
^ | \ Tr Expiry, ^ |
| | \ at least one | |
| | \ ASP in ASP-INACTIVE | |
| | \ | |
| | \ | |
| | \ | |
one ASP | | all ASP \ one ASP | | Last ACTIVE
trans | | trans to \ trans to | | ASP trans to
to | | ASP-DOWN -------\ ASP- | | ASP-INACTIVE
ASP- | | \ ACTIVE | | or ASP-DOWN
INACTIVE| | \ | | (start Tr)
| | \ | |
| | \ | |
| v \ | v
+----------+ \ +-------------+
| | --| |
| AS-DOWN | | AS-PENDING |
| | | (queuing) |
| |<----------------------------| |
+----------+ Tr Expiry and no ASP +-------------+
in ASP-INACTIVE state
+----------+ one ASP trans to ACTIVE +-------------+
| AS- |---------------------------->| AS- |
| INACTIVE | | ACTIVE |
| |<--- | |
+----------+ \ +-------------+
^ | \ Tr Expiry, ^ |
| | \ at least one | |
| | \ ASP in ASP-INACTIVE | |
| | \ | |
| | \ | |
| | \ | |
one ASP | | all ASP \ one ASP | | Last ACTIVE
trans | | trans to \ trans to | | ASP trans to
to | | ASP-DOWN -------\ ASP- | | ASP-INACTIVE
ASP- | | \ ACTIVE | | or ASP-DOWN
INACTIVE| | \ | | (start Tr)
| | \ | |
| | \ | |
| v \ | v
+----------+ \ +-------------+
| | --| |
| AS-DOWN | | AS-PENDING |
| | | (queuing) |
| |<----------------------------| |
+----------+ Tr Expiry and no ASP +-------------+
in ASP-INACTIVE state
Tr = Recovery Timer
Tr = Recovery Timer
Before the establishment of an SCTP association the ASP state at both the SGP and ASP is assumed to be in the state ASP-DOWN.
在建立SCTP关联之前，假定SGP和ASP的ASP状态都处于ASP-DOWN状态。
Once the SCTP association is established (see Section 4.2.1) and assuming that the local M2UA-User is ready, the local M2UA ASP Maintenance (ASPM) function will initiate the relevant procedures, using the ASP Up/ASP Down/ASP Active/ASP Inactive messages to convey the ASP state to the SGP (see Section 4.3.4).
一旦建立SCTP关联（见第4.2.1节），并假设本地M2UA用户已准备就绪，本地M2UA ASP维护（ASPM）功能将启动相关程序，使用ASP Up/ASP Down/ASP Active/ASP Inactive消息将ASP状态传递给SGP（见第4.3.4节）。
If the M2UA layer subsequently receives an SCTP-COMMUNICATION_DOWN or SCTP-RESTART indication primitive from the underlying SCTP layer, it will inform the Layer Management by invoking the M-SCTP_STATUS indication primitive. The state of the ASP will be moved to ASP-DOWN.
如果M2UA层随后从底层SCTP层接收到SCTP-COMMUNICATION_DOWN或SCTP-RESTART指示原语，它将通过调用M-SCTP_状态指示原语通知层管理。ASP的状态将移动到ASP-DOWN。
In the case of SCTP-COMMUNICATION_DOWN, the SCTP client MAY try to re-establish the SCTP association. This MAY be done by the M2UA layer automatically, or Layer Management MAY re-establish using the M-SCTP_ESTABLISH request primitive.
在SCTP通信中断的情况下，SCTP客户端可以尝试重新建立SCTP关联。这可以由M2UA层自动完成，或者层管理可以使用M-SCTP_建立请求原语重新建立。
In the case of an SCTP-RESTART indication at an ASP, the ASP is now considered by its M2UA peer to be in the ASP-DOWN state. The ASP, if it is to recover, must begin any recovery with the ASP-Up procedure.
在ASP处出现SCTP重启指示的情况下，其M2UA对等方现在认为ASP处于ASP-DOWN状态。如果要恢复，ASP必须使用ASP Up过程开始任何恢复。
After an ASP has successfully established an SCTP association to an SGP, the SGP waits for the ASP to send an ASP Up message, indicating that the ASP M2UA peer is available. The ASP is always the initiator of the ASP Up message. This action MAY be initiated at the ASP by an M-ASP_UP request primitive from Layer Management or MAY be initiated automatically by an M2UA management function.
ASP成功建立与SGP的SCTP关联后，SGP等待ASP发送ASP Up消息，指示ASP M2UA对等机可用。ASP始终是ASP Up消息的发起方。此操作可以由层管理的M-ASP_UP request原语在ASP处启动，也可以由M2UA管理功能自动启动。
When an ASP Up message is received at an SGP and internally the remote ASP is in the ASP-DOWN state and not considered locked-out for local management reasons, the SGP marks the remote ASP in the state ASP-INACTIVE and informs Layer Management with an M-ASP_Up indication primitive. If the SGP is aware, via current configuration data, which Application Servers the ASP is configured to operate in, the SGP updates the ASP state to ASP-INACTIVE in each AS that it is a member.
当SGP收到ASP Up消息且远程ASP在内部处于ASP-DOWN状态且由于本地管理原因未被视为锁定时，SGP将远程ASP标记为ASP-INACTIVE状态，并使用M-ASP\U Up指示原语通知层管理。如果SGP通过当前配置数据知道ASP配置为在哪些应用服务器中运行，则SGP会将每个应用服务器中的ASP状态更新为ASP-INACTIVE，因为它是一个成员。
Alternatively, the SGP may move the ASP into a pool of Inactive ASPs available for future configuration within Application Server(s), determined in a subsequent Registration Request or ASP Active procedure. If the ASP Up message contains an ASP Identifier, the SGP should save the ASP Identifier for that ASP. The SGP MUST send an ASP Up Ack message in response to a received ASP Up message even if the ASP is already marked as ASP-INACTIVE at the SGP.
或者，SGP可以将ASP移动到一个非活动ASP池中，该非活动ASP池可用于在随后的注册请求或ASP活动过程中确定的应用服务器内的未来配置。如果ASP Up消息包含ASP标识符，则SGP应保存该ASP的ASP标识符。SGP必须发送ASP Up Ack消息以响应收到的ASP Up消息，即使该ASP已在SGP上标记为ASP-INACTIVE。
If for any local reason (e.g., management lock-out) the SGP cannot respond with an ASP Up Ack message, the SGP responds to an ASP Up message with an Error message with Reason "Refused - Management Blocking".
如果由于任何本地原因（例如，管理锁定），SGP无法响应ASP Up Ack消息，则SGP会响应ASP Up消息，并返回错误消息，原因为“拒绝-管理阻塞”。
At the ASP, the ASP Up Ack message received is not acknowledged. Layer Management is informed with an M-ASP_UP confirm primitive.
在ASP上，接收到的ASP Up Ack消息未得到确认。层管理由M-ASP\U UP确认原语通知。
When the ASP sends an ASP Up message it starts timer T(ack). If the ASP does not receive a response to an ASP Up message within T(ack), the ASP MAY restart T(ack) and resend ASP Up messages until it
当ASP发送ASP Up消息时，它启动计时器T（确认）。如果ASP在T（ack）内未收到对ASP Up消息的响应，则ASP可重新启动T（ack）并重新发送ASP Up消息，直到收到响应为止
receives an ASP Up Ack message. T(ack) is provisionable, with a default of 2 seconds. Alternatively, retransmission of ASP Up messages MAY be put under control of Layer Management. In this method, expiry of T(ack) results in an M-ASP_UP confirm primitive carrying a negative indication.
接收ASP Up Ack消息。T（ack）是可设置的，默认值为2秒。或者，ASP Up消息的重新传输可以置于层管理的控制之下。在这种方法中，T（ack）的到期将导致带有否定指示的M-ASP_UP confirm原语。
The ASP MUST wait for the ASP Up Ack message before sending any other M2UA messages (e.g., ASP Active or REG REQ). If the SGP receives any other M2UA messages before an ASP Up message is received (other than ASP Down - see Section 4.3.4.2), the SGP MAY discard them.
ASP必须等待ASP Up Ack消息，然后才能发送任何其他M2UA消息（例如ASP Active或REG REQ）。如果SGP在收到ASP Up消息（ASP Down除外-参见第4.3.4.2节）之前收到任何其他M2UA消息，SGP可能会丢弃这些消息。
If an ASP Up message is received and internally the remote ASP is in the ASP-ACTIVE state, an ASP Up Ack message is returned, as well as an Error message ("Unexpected Message), and the remote ASP state is changed to ASP-INACTIVE in all relevant Application Servers.
如果收到ASP Up消息且远程ASP在内部处于ASP-ACTIVE状态，将返回ASP Up Ack消息以及错误消息（“意外消息”），并且所有相关应用程序服务器中的远程ASP状态将更改为ASP-INACTIVE。
If an ASP Up message is received and internally the remote ASP is already in the ASP-INACTIVE state, an ASP Up Ack message is returned and no further action is taken.
如果收到ASP Up消息，并且远程ASP在内部已处于ASP-INACTIVE状态，则返回ASP Up Ack消息，并且不采取进一步的操作。
If an ASP Up message with an unsupported version is received, the receiving end responds with an Error message, indicating the version the receiving node supports and notifies Layer Management.
如果接收到版本不受支持的ASP Up消息，接收端将以错误消息响应，指示接收节点支持的版本，并通知层管理。
This is useful when protocol version upgrades are being performed in a network. A node upgraded to a newer version SHOULD support the older versions used on other nodes it is communicating with. Because ASPs initiate the ASP Up procedure it is assumed that the Error message would normally come from the SGP.
这在网络中执行协议版本升级时非常有用。升级到较新版本的节点应支持与之通信的其他节点上使用的较旧版本。由于ASP启动ASP Up过程，因此假定错误消息通常来自SGP。
The ASP will send an ASP Down message to an SGP when the ASP wishes to be removed from service in all Application Servers that it is a member and no longer receive any MAUP or ASPTM messages. This action MAY be initiated at the ASP by an M-ASP_DOWN request primitive from Layer Management or MAY be initiated automatically by an M2UA management function.
当ASP希望从其作为成员的所有应用程序服务器的服务中删除并且不再接收任何MAUP或ASPTM消息时，ASP将向SGP发送ASP Down消息。此操作可以由层管理的M-ASP_DOWN request原语在ASP处启动，也可以由M2UA管理功能自动启动。
Whether the ASP is permanently removed from any AS is a function of configuration management. In the case where the ASP previously used the Registration procedures (see Section 4.4) to register within Application Servers but has not unregistered from all of them prior to sending the ASP Down message, the SGP MUST consider the ASP as unregistered in all Application Servers that it is still a member.
ASP是否从任何AS中永久删除是配置管理的一项功能。在ASP以前使用注册程序（见第4.4节）在应用服务器中注册但尚未在发送ASP向下消息之前对它们进行登记时，SGP必须考虑ASP在所有应用服务器中未注册的情况，因为它仍然是成员。
The SGP marks the ASP as ASP-DOWN, informs Layer Management with an M-ASP_Down indication primitive, and returns an ASP Down Ack message to the ASP.
SGP将ASP标记为ASP-DOWN，使用M-ASP\U DOWN指示原语通知层管理，并向ASP返回ASP-DOWN确认消息。
The SGP MUST send an ASP Down Ack message in response to a received ASP Down message from the ASP even if the ASP is already marked as ASP-DOWN at the SGP.
即使ASP已在SGP上标记为ASP-Down，SGP也必须发送ASP Down Ack消息以响应从ASP接收到的ASP Down消息。
At the ASP, the ASP Down Ack message received is not acknowledged. Layer Management is informed with an M-ASP_DOWN confirm primitive. If the ASP receives an ASP Down Ack without having sent an ASP Down message, the ASP SHOULD now consider itself as in the ASP-DOWN state. If the ASP was previously in the ASP-ACTIVE or ASP_INACTIVE state, the ASP SHOULD then initiate procedures to return itself to its previous state.
在ASP上，接收到的ASP Down Ack消息未得到确认。通过M-ASP_DOWN confirm原语通知层管理。如果ASP在没有发送ASP向下消息的情况下接收到ASP Unk ACK，那么ASP现在应该将其视为ASP-DOWN状态。如果ASP以前处于ASP-ACTIVE或ASP\U INACTIVE状态，则ASP应启动过程以将自身恢复到以前的状态。
When the ASP sends an ASP Down message it starts timer T(ack). If the ASP does not receive a response to an ASP Down message within T(ack), the ASP MAY restart T(ack) and resend ASP Down messages until it receives an ASP Down Ack message. T(ack) is provisionable, with a default of 2 seconds. Alternatively, retransmission of ASP Down messages MAY be put under control of Layer Management. In this method, expiry of T(ack) results in an M-ASP_DOWN confirm primitive carrying a negative indication.
当ASP发送ASP Down消息时，它启动定时器T（ack）。如果ASP在T（ack）内未收到对ASP Down消息的响应，则ASP可重新启动T（ack）并重新发送ASP Down消息，直到收到ASP Down ack消息。T（ack）是可设置的，默认值为2秒。或者，ASP Down消息的重传可以置于层管理的控制之下。在这种方法中，T（ack）的到期会导致M-ASP_DOWN confirm原语带有否定指示。
Anytime after the ASP has received an ASP Up Ack message from the SGP, the ASP MAY send an ASP Active message to the SGP indicating that the ASP is ready to start processing traffic. This action MAY be initiated at the ASP by an M-ASP_ACTIVE request primitive from Layer Management or MAY be initiated automatically by a M2UA management function. In the case where an ASP wishes to process the traffic for more than one Application Server across a common SCTP association, the ASP Active message(s) SHOULD contain a list of one or more Interface Identifiers to indicate for which Application Servers the ASP Active message applies. It is not necessary for the ASP to include any Interface Identifiers of interest in a single ASP Active message, thus requesting to become active in all Interface Identifiers at the same time. Multiple ASP Active messages MAY be used to activate within the Application Servers independently, or in sets. In the case where an ASP Active message does not contain a Interface Identifier parameter, the receiver must know, via configuration data, of which Application Server(s) the ASP is a member.
在ASP从SGP接收到ASP Up Ack消息后的任何时候，ASP都可以向SGP发送ASP活动消息，指示ASP已准备好开始处理流量。此操作可以由层管理的M-ASP_活动请求原语在ASP处启动，也可以由M2UA管理功能自动启动。如果ASP希望跨公共SCTP关联处理多个应用程序服务器的流量，则ASP活动消息应包含一个或多个接口标识符的列表，以指示ASP活动消息适用于哪些应用程序服务器。ASP不需要在单个ASP活动消息中包含任何感兴趣的接口标识符，因此请求同时在所有接口标识符中变为活动。多个ASP活动消息可用于在应用程序服务器内单独激活，或以集合形式激活。如果ASP活动消息不包含接口标识符参数，则接收方必须通过配置数据知道ASP是哪个应用程序服务器的成员。
For the Application Servers that the ASP can successfully activate, the SGP responds with one or more ASP Active Ack messages, including
对于ASP可以成功激活的应用程序服务器，SGP用一条或多条ASP活动确认消息进行响应，包括
the associated Interface Identifier(s) and reflecting any Traffic Mode Type value present in the related ASP Active message. The Interface Identifier parameter MUST be included in the ASP Active Ack message(s) if the received ASP Active message contained any Interface Identifiers. Depending on any Traffic Mode Type request in the ASP Active message or local configuration data if there is no request, the SGP moves the ASP to the correct ASP traffic state within the associated Application Server(s). Layer Management is informed with an M-ASP_Active indication. If the SGP receives any Data messages before an ASP Active message is received, the SGP MAY discard them. By sending an ASP Active Ack message, the SGP is now ready to receive and send traffic for the related Interface Identifier(s). The ASP SHOULD NOT send MAUP messages for the related Interface Identifier(s) before receiving an ASP Active Ack message, or it will risk message loss.
关联的接口标识符，并反映相关ASP活动消息中存在的任何通信模式类型值。如果收到的ASP活动消息包含任何接口标识符，则ASP活动确认消息中必须包含接口标识符参数。根据ASP活动消息中的任何流量模式类型请求或本地配置数据（如果没有请求），SGP将ASP移动到相关应用程序服务器内的正确ASP流量状态。通过M-ASP\U活动指示通知图层管理。如果SGP在收到ASP活动消息之前收到任何数据消息，则SGP可能会丢弃这些数据消息。通过发送ASP活动Ack消息，SGP现在可以接收和发送相关接口标识符的通信量。在收到ASP活动Ack消息之前，ASP不应发送相关接口标识符的MAUP消息，否则将有消息丢失的风险。
Multiple ASP Active Ack messages MAY be used in response to an ASP Active message containing multiple Interface Identifiers, allowing the SGP to independently acknowledge the ASP Active message for different (sets of) Interface Identifiers. The SGP MUST send an Error message ("Invalid Interface Identifier") for each Interface Identifier value that cannot be successfully activated.
多个ASP活动Ack消息可用于响应包含多个接口标识符的ASP活动消息，从而允许SGP针对不同（组）接口标识符独立地确认ASP活动消息。SGP必须为无法成功激活的每个接口标识符值发送错误消息（“无效接口标识符”）。
In the case where an "out-of-the-blue" ASP Active message is received (i.e., the ASP has not registered with the SG or the SG has no static configuration data for the ASP), the message MAY be silently discarded.
在接收到“出乎意料的”ASP活动消息的情况下（即，ASP没有向SG注册，或者SG没有ASP的静态配置数据），该消息可以被静默地丢弃。
The SGP MUST send an ASP Active Ack message in response to a received ASP Active message from the ASP, if the ASP is already marked in the ASP-ACTIVE state at the SGP.
如果ASP已在SGP上标记为ASP-Active状态，则SGP必须发送ASP-Active Ack消息以响应从ASP接收到的ASP-Active消息。
At the ASP, the ASP Active Ack message received is not acknowledged. Layer Management is informed with an M-ASP_ACTIVE confirm primitive. It is possible for the ASP to receive Data message(s) before the ASP Active Ack message as the ASP Active Ack and Data messages from an SG may be sent on different SCTP streams. Message loss is possible as the ASP does not consider itself in the ASP-ACTIVE state until reception of the ASP Active Ack message.
在ASP上，接收到的ASP活动确认消息未得到确认。层管理由M-ASP_活动确认原语通知。ASP可以在ASP活动Ack消息之前接收数据消息，因为ASP活动Ack和来自SG的数据消息可以在不同的SCTP流上发送。消息丢失是可能的，因为ASP在接收ASP活动ACK消息之前不考虑自身处于ASP-Active状态。
When the ASP sends an ASP Active message it starts timer T(ack). If the ASP does not receive a response to an ASP Active message within T(ack), the ASP MAY restart T(ack) and resend ASP Active message(s) until it receives an ASP Active Ack message. T(ack) is provisionable, with a default of 2 seconds. Alternatively, retransmission of ASP Active messages MAY be put under the control of Layer Management. In this method, expiry of T(ack) results in an M-ASP_ACTIVE confirm primitive carrying a negative indication.
当ASP发送ASP活动消息时，它启动计时器T（确认）。如果ASP在T（确认）内未收到对ASP活动消息的响应，则ASP可重新启动T（确认）并重新发送ASP活动消息，直到收到ASP活动确认消息。T（ack）是可设置的，默认值为2秒。或者，ASP活动消息的重传可以置于层管理的控制之下。在这种方法中，T（ack）的到期会导致带有否定指示的M-ASP_活动确认原语。
There are three modes of Application Server traffic handling in the SGP M2UA layer: Override, Load share and Broadcast. When included, the Traffic Mode Type parameter in the ASP Active message indicates the traffic handling mode to be used in a particular Application Server. If the SGP determines that the mode indicated in an ASP Active message is unsupported or incompatible with the mode currently configured for the AS, the SGP responds with an Error message ("Unsupported / Invalid Traffic Handling Mode"). If the traffic handling mode of the Application Server is not already known via configuration data, the traffic handling mode indicated in the first ASP Active message causing the transition of the Application Server state to AS-ACTIVE MAY be used to set the mode.
SGP M2UA层中有三种应用服务器流量处理模式：覆盖、负载共享和广播。包含时，ASP Active message中的Traffic Mode Type参数表示要在特定应用程序服务器中使用的流量处理模式。如果SGP确定ASP活动消息中指示的模式不受支持或与当前为AS配置的模式不兼容，SGP将以错误消息（“不支持/无效流量处理模式”）进行响应。如果通过配置数据还不知道应用服务器的流量处理模式，则可以使用导致应用服务器状态转换为AS-Active的第一个ASP-Active消息中指示的流量处理模式来设置该模式。
In the case of an Override mode AS, reception of an ASP Active message at an SGP causes the (re)direction of all traffic for the AS to the ASP that sent the ASP Active message. Any previously active ASP in the AS is now considered to be in the state ASP-INACTIVE and SHOULD no longer receive traffic from the SGP within the AS. The SGP then MUST send a Notify message ("Alternate ASP Active") to the previously active ASP in the AS, and SHOULD stop traffic to/from that ASP. The ASP receiving this Notify MUST consider itself now in the ASP-INACTIVE state, if it is not already aware of this via inter-ASP communication with the Overriding ASP.
在覆盖模式AS的情况下，在SGP处接收ASP活动消息将导致AS的所有通信量（重新）定向到发送ASP活动消息的ASP。AS中任何以前处于活动状态的ASP现在被视为处于ASP-INACTIVE状态，并且不应再从AS中的SGP接收流量。然后，SGP必须向AS中以前处于活动状态的ASP发送通知消息（“备用ASP活动”），并应停止与该ASP之间的通信。接收到此通知的ASP现在必须在ASP非活动状态下考虑自身，如果它还没有通过与ASP的ASP间通信来意识到这一点的话。
In the case of a Load-share mode AS, reception of an ASP Active message at an SGP causes the direction of traffic to the ASP sending the ASP Active message, in addition to all the other ASPs that are currently active in the AS. The algorithm at the SGP for load-sharing traffic within an AS to all the active ASPs is implementation dependent. The algorithm could, for example be round-robin or based on information in the Data message (e.g., such as the SLS in the Routing Label).
在负载共享模式AS的情况下，除了AS中当前处于活动状态的所有其他ASP外，在SGP处接收ASP活动消息会导致发送ASP活动消息的ASP的流量方向。SGP中用于AS内所有活动ASP的负载共享流量的算法取决于实现。例如，该算法可以是循环或基于数据消息中的信息（例如，例如路由标签中的SLS）。
An SGP, upon reception of an ASP Active message for the first ASP in a Load share AS, MAY choose not to direct traffic to a newly active ASP until it determines that there are sufficient resources to handle the expected load (e.g., until there are "n" ASPs in state ASP-ACTIVE in the AS).
SGP在接收到负载共享AS中第一个ASP的ASP活动消息后，可以选择不将流量定向到新活动的ASP，直到它确定有足够的资源来处理预期负载（例如，直到AS中有处于ASP-Active状态的“n”个ASP）。
All ASPs within a load-sharing mode AS must be able to process any Data message received for the AS, to accommodate any potential fail-over or balancing of the offered load.
负载共享模式AS中的所有ASP必须能够处理AS接收到的任何数据消息，以适应所提供负载的任何潜在故障转移或平衡。
In the case of a Broadcast mode AS, reception of an ASP Active message at an SGP causes the direction of traffic to the ASP sending the ASP Active message, in addition to all the other ASPs that are currently active in the AS. The algorithm at the SGP for
在广播模式AS的情况下，除了AS中当前处于活动状态的所有其他ASP外，在SGP处接收ASP活动消息会导致发送ASP活动消息的ASP的流量方向。在SGP上的算法
broadcasting traffic within an AS to all the active ASPs is a simple broadcast algorithm, where every message is sent to each of the active ASPs.
将AS内的通信量广播到所有活动ASP是一种简单的广播算法，其中每个消息都发送到每个活动ASP。
An SGP, upon reception of an ASP Active message for the first ASP in a Broadcast AS, MAY choose not to direct traffic to a newly active ASP until it determines that there are sufficient resources to handle the expected load (e.g., until there are "n" ASPs in state ASP-ACTIVE in the AS).
SGP在接收到广播AS中第一个ASP的ASP活动消息时，可以选择不将流量定向到新活动的ASP，直到它确定有足够的资源来处理预期负载（例如，直到AS中有处于ASP-Active状态的“n”个ASP）。
Whenever an ASP in a Broadcast mode AS becomes ASP-ACTIVE, the SGP MUST tag the first DATA message broadcast in each SCTP stream with a unique Correlation Id parameter. The purpose of this Correlation Id is to permit the newly active ASP to synchronize its processing of traffic in each ordered stream with the other ASPs in the broadcast group.
每当处于广播模式AS的ASP变为ASP-ACTIVE时，SGP必须使用唯一的相关Id参数标记每个SCTP流中广播的第一条数据消息。此关联Id的目的是允许新激活的ASP将其对每个有序流中的流量的处理与广播组中的其他ASP同步。
When an ASP wishes to withdraw from receiving traffic within an AS, the ASP sends an ASP Inactive message to the SGP. This action MAY be initiated at the ASP by an M-ASP_INACTIVE request primitive from Layer Management or MAY be initiated automatically by an M2UA management function. In the case where an ASP is processing the traffic for more than one Application Server across a common SCTP association, the ASP Inactive message contains one or more Interface Identifiers to indicate for which Application Servers the ASP Inactive message applies. In the case where an ASP Inactive message does not contain a Interface Identifier parameter, the receiver must know, via configuration data, of which Application Servers the ASP is a member and move the ASP to the ASP-INACTIVE state in all Application Servers. In the case of an Override mode AS, where another ASP has already taken over the traffic within the AS with an ASP Active ("Override") message, the ASP that sends the ASP Inactive message is already considered by the SGP to be in the state ASP-INACTIVE. An ASP Inactive Ack message is sent to the ASP, after ensuring that all traffic is stopped to the ASP.
当ASP希望退出AS内的接收流量时，ASP会向SGP发送一条ASP非活动消息。此操作可以由层管理的M-ASP_非活动请求原语在ASP处启动，也可以由M2UA管理功能自动启动。如果ASP正在处理公共SCTP关联中多个应用程序服务器的通信量，则ASP非活动消息包含一个或多个接口标识符，以指示ASP非活动消息适用于哪些应用程序服务器。如果ASP非活动消息不包含接口标识符参数，则接收方必须通过配置数据知道ASP是哪个应用程序服务器的成员，并在所有应用程序服务器中将ASP移动到ASP-Inactive状态。在覆盖模式AS的情况下，如果另一个ASP已通过ASP Active（“覆盖”）消息接管AS内的流量，则发送ASP Inactive消息的ASP已被SGP视为处于ASP-Inactive状态。在确保所有到ASP的通信都已停止后，ASP Inactive Ack消息将发送到ASP。
In the case of a Load-share mode AS, the SGP moves the ASP to the ASP-INACTIVE state and the AS traffic is re-allocated across the remaining ASPs in the state ASP-ACTIVE, as per the load-sharing algorithm currently used within the AS. A Notify message ("Insufficient ASP resources active in AS") MAY be sent to all inactive ASPs, if required. An ASP Inactive Ack message is sent to the ASP after all traffic is halted and Layer Management is informed with an M-ASP_INACTIVE indication primitive.
在负载共享模式AS的情况下，SGP将ASP移动到ASP-INACTIVE状态，并根据AS中当前使用的负载共享算法，在ASP-ACTIVE状态的其余ASP之间重新分配AS流量。如果需要，可以向所有非活动的ASP发送通知消息（“AS中活动的ASP资源不足”）。在所有通信停止后，ASP Inactive Ack消息被发送到ASP，并使用M-ASP_Inactive指示原语通知层管理。
In the case of a Broadcast mode AS, the SGP moves the ASP to the ASP-INACTIVE state and the AS traffic is broadcast only to the remaining ASPs in the state ASP-ACTIVE. A Notify message ("Insufficient ASP resources active in AS") MAY be sent to all inactive ASPs, if required. An ASP Inactive Ack message is sent to the ASP after all traffic is halted and Layer Management is informed with an M-ASP_INACTIVE indication primitive.
在广播模式AS的情况下，SGP将ASP移动到ASP-INACTIVE状态，AS通信量仅广播到ASP-ACTIVE状态下的其余ASP。如果需要，可以向所有非活动的ASP发送通知消息（“AS中活动的ASP资源不足”）。在所有通信停止后，ASP Inactive Ack消息被发送到ASP，并使用M-ASP_Inactive指示原语通知层管理。
Multiple ASP Inactive Ack messages MAY be used in response to an ASP Inactive message containing multiple Interface Identifiers, allowing the SGP to independently acknowledge for different (sets of) Interface Identifiers. The SGP sends an Error message ("Invalid Interface Identifier") for each invalid or not configured Interface Identifier value in a received ASP Inactive message.
多个ASP非活动Ack消息可用于响应包含多个接口标识符的ASP非活动消息，从而允许SGP独立地确认不同（组）接口标识符。SGP为接收到的ASP非活动消息中的每个无效或未配置的接口标识符值发送错误消息（“无效接口标识符”）。
The SGP MUST send an ASP Inactive Ack message in response to a received ASP Inactive message from the ASP and the ASP is already marked as ASP-INACTIVE at the SGP.
SGP必须发送ASP非活动确认消息，以响应从ASP接收到的ASP非活动消息，并且ASP已在SGP标记为ASP-Inactive。
At the ASP, the ASP Inactive Ack message received is not acknowledged. Layer Management is informed with an M-ASP_INACTIVE confirm primitive. If the ASP receives an ASP Inactive Ack without having sent an ASP Inactive message, the ASP SHOULD now consider itself as in the ASP-INACTIVE state. If the ASP was previously in the ASP-ACTIVE state, the ASP SHOULD then initiate procedures to return itself to its previous state.
在ASP上，接收到的ASP非活动确认消息未得到确认。使用M-ASP\U非活动确认原语通知图层管理。如果ASP接收到ASP非活动ACK而不发送ASP非激活消息，那么ASP现在应该认为自己处于ASP非活动状态。如果ASP以前处于ASP-ACTIVE状态，则ASP应启动过程以将自身恢复到以前的状态。
When the ASP sends an ASP Inactive message it starts timer T(ack). If the ASP does not receive a response to an ASP Inactive message within T(ack), the ASP MAY restart T(ack) and resend ASP Inactive messages until it receives an ASP Inactive Ack message. T(ack) is provisionable, with a default of 2 seconds. Alternatively, retransmission of ASP Inactive messages MAY be put under the control of Layer Management. In this method, expiry of T(ack) results in a M-ASP_Inactive confirm primitive carrying a negative indication.
当ASP发送ASP非活动消息时，它启动计时器T（确认）。如果ASP在T（确认）内未收到对ASP非活动消息的响应，则ASP可重新启动T（确认）并重新发送ASP非活动消息，直到收到ASP非活动确认消息。T（ack）是可设置的，默认值为2秒。或者，ASP非活动消息的重新传输可以置于层管理的控制之下。在这种方法中，T（ack）的到期导致M-ASP_非活动确认原语携带负指示。
If no other ASPs in the Application Server are in the state ASP-ACTIVE, the SGP MUST send a Notify message ("AS-Pending") to all of the ASPs in the AS which are in the state ASP-INACTIVE. The SGP SHOULD start buffering the incoming messages for T(r)seconds, after which messages MAY be discarded. T(r) is configurable by the network operator. If the SGP receives an ASP Active message from an ASP in the AS before expiry of T(r), the buffered traffic is directed to that ASP and the timer is canceled. If T(r) expires, the AS is moved to the AS-INACTIVE state.
如果应用程序服务器中没有其他ASP处于ASP-ACTIVE状态，则SGP必须向AS中处于ASP-ACTIVE状态的所有ASP发送通知消息（“AS Pending”）。SGP应开始将传入消息缓冲T（r）秒，之后可能会丢弃消息。T（r）可由网络运营商配置。如果SGP在T（r）到期之前从AS中的ASP接收到ASP活动消息，则缓冲的通信量被定向到该ASP，并且定时器被取消。如果T（r）过期，AS将移至AS-INACTIVE状态。
A Notify message reflecting a change in the AS state MUST be sent to all ASPs in the AS, except those in the ASP-DOWN state, with appropriate Status Information and any ASP Identifier of the failed ASP. At the ASP, Layer Management is informed with an M-NOTIFY indication primitive. The Notify message MUST be sent whether the AS state change was a result of an ASP failure or reception of an ASP State Management (ASPSM) / ASP Traffic Management (ASPTM) message. In the second case, the Notify message MUST be sent after any related acknowledgment messages (e.g., ASP Up Ack, ASP Down Ack, ASP Active Ack, or ASP Inactive Ack).
必须向AS中的所有ASP发送反映AS状态更改的Notify消息（ASP-DOWN状态的ASP除外），其中包含相应的状态信息和失败ASP的任何ASP标识符。在ASP中，层管理通过M-NOTIFY指示原语通知。无论AS状态更改是由于ASP故障还是由于接收到ASP状态管理（ASPSM）/ASP流量管理（ASPTM）消息而导致，都必须发送Notify消息。在第二种情况下，通知消息必须在任何相关确认消息（例如，ASP Up Ack、ASP Down Ack、ASP Active Ack或ASP Inactive Ack）之后发送。
In the case where a Notify ("AS-PENDING") message is sent by an SGP that now has no ASPs active to service the traffic, or where a Notify ("Insufficient ASP resources active in AS") message MUST be sent in the Load share or Broadcast mode, the Notify message does not explicitly compel the ASP(s) receiving the message to become active. The ASPs remain in control of what (and when) traffic action is taken.
如果通知（“AS-PENDING”）消息由SGP发送，而该SGP现在没有活动的ASP来为流量提供服务，或者如果通知（“AS中活动的ASP资源不足”）消息必须以负载共享或广播模式发送，则通知消息不会显式强制接收该消息的ASP变为活动。ASP仍然控制采取什么（以及何时）交通行动。
In the case where a Notify message does not contain a Interface Identifier parameter, the receiver must know, via configuration data, of which Application Servers the ASP is a member and take the appropriate action in each AS.
在Notify消息不包含接口标识符参数的情况下，接收方必须通过配置数据知道ASP是哪个应用程序服务器的成员，并在每个AS中采取适当的操作。
The optional Heartbeat procedures MAY be used when operating over transport layers that do not have their own heartbeat mechanism for detecting loss of the transport association (i.e., other than SCTP).
可选的心跳程序可用于在没有自己的心跳机制来检测传输关联丢失（即，除了SCTP）的传输层上操作。
Either M2UA peer may optionally send Heartbeat messages periodically, subject to a provisionable timer T(beat). Upon receiving a Heartbeat message, the M2UA peer MUST respond with a Heartbeat Ack message.
任一M2UA对等方可选择性地根据可设置的定时器T（节拍）周期性地发送心跳消息。接收到心跳消息后，M2UA对等方必须使用心跳确认消息进行响应。
If no Heartbeat Ack message (or any other M2UA message) is received from the M2UA peer within 2*T(beat), the remote M2UA peer is considered unavailable. Transmission of Heartbeat messages is stopped and the signalling process SHOULD attempt to re-establish communication if it is configured as the client for the disconnected M2UA peer.
如果在2*T（beat）内没有从M2UA对等方接收到心跳确认消息（或任何其他M2UA消息），则认为远程M2UA对等方不可用。心跳消息的传输已停止，如果将信令进程配置为断开连接的M2UA对等方的客户端，则应尝试重新建立通信。
The Heartbeat message may optionally contain an opaque Heartbeat Data parameter that MUST be echoed back unchanged in the related Heartbeat Ack message. The sender, upon examining the contents of the returned Heartbeat Ack message, MAY choose to consider the remote M2UA peer as unavailable. The contents/format of the Heartbeat Data parameter is
Heartbeat消息可以选择性地包含不透明的Heartbeat数据参数，该参数必须在相关Heartbeat Ack消息中原封不动地回显。发送者在检查返回的心跳ACK消息的内容时，可以选择考虑远程M2UA对等体不可用。Heartbeat数据参数的内容/格式为
implementation-dependent and only of local interest to the original sender. The contents may be used, for example, to support a Heartbeat sequence algorithm (to detect missing Heartbeats), and/or a time stamp mechanism (to evaluate delays).
依赖于实现，且仅与原始发送方的本地利益相关。例如，内容可用于支持心跳序列算法（检测丢失的心跳）和/或时间戳机制（评估延迟）。
Note: Heartbeat related events are not shown in Figure 5 "ASP state transition diagram".
注意：图5“ASP状态转换图”中未显示心跳相关事件。
The Interface Identifier Management procedures are optional. They can be used to support automatic allocation of Signalling Terminals or Signalling Data Links [2][3].
接口标识符管理过程是可选的。它们可用于支持信令终端或信令数据链路的自动分配[2][3]。
An ASP MAY dynamically register with an SGP as an ASP within an Application Server for individual Interface Identifier(s) using the REG REQ message. A Link Key parameter in the REG REQ specifies the parameters associated with the Link Key.
ASP可以使用REG REQ消息在应用程序服务器中动态地向SGP注册为单个接口标识符的ASP。REG REQ中的链接键参数指定与链接键关联的参数。
The SGP examines the contents of the received Link Key parameters (SDLI and SDTI) and compares them with the currently provisioned Interface Identifiers. If the received Link Key matches an existing SGP Link Key entry, and the ASP is not currently included in the list of ASPs for the related Application Server, the SGP MAY authorize the ASP to be added to the AS. Or, if the Link Key does not currently exist and the received Link Key data is valid and unique, an SGP supporting dynamic configuration MAY authorize the creation of a new Interface Identifier and related Application Server and add the ASP to the new AS. In either case, the SGP returns a Registration Response message to the ASP, containing the same Local-LK-Identifier as provided in the initial request, a Registration Result "Successfully Registered" and the Interface Identifier. A unique method of Interface Identifier valid assignment at the SG/SGP is implementation dependent but MUST be guaranteed to be unique for each Application server or Link Key served by SGP.
SGP检查接收到的链路密钥参数（SDLI和SDTI）的内容，并将其与当前配置的接口标识符进行比较。如果收到的链接密钥与现有SGP链接密钥条目匹配，并且ASP当前未包括在相关应用程序服务器的ASP列表中，则SGP可以授权将ASP添加到AS。或者，如果链路密钥当前不存在且接收到的链路密钥数据有效且唯一，则支持动态配置的SGP可授权创建新的接口标识符和相关应用服务器，并将ASP添加到新AS。在任何一种情况下，SGP都将注册响应消息返回给ASP，其中包含与初始请求中提供的相同的本地LK标识符、注册结果“成功注册”和接口标识符。SG/SGP上接口标识符有效分配的唯一方法取决于实现，但必须保证对于SGP服务的每个应用服务器或链路密钥是唯一的。
If the SGP determines that the received Link Key data is invalid, or contains invalid parameter values, the SGP returns a Registration Response message to the ASP, containing a Registration Result "Error - Invalid Link Key", "Error - Invalid SDTI", "Error - Invalid SDLI" as appropriate.
如果SGP确定接收到的链路密钥数据无效，或包含无效参数值，则SGP将向ASP返回注册响应消息，其中包含注册结果“错误-无效链路密钥”、“错误-无效SDTI”、“错误-无效SDLI”（视情况而定）。
If the SGP determines that the Link Key parameter overlaps with an existing Link Key entry, the SGP returns a Registration Response message to the ASP, with a Registration Status of "Error - Overlapping (Non-Unique) Link Key". An incoming signalling message received at an SGP cannot match against more than one Link Key.
如果SGP确定链路密钥参数与现有链路密钥条目重叠，则SGP将向ASP返回注册响应消息，注册状态为“错误-重叠（非唯一）链路密钥”。在SGP接收的传入信令消息不能与多个链路密钥匹配。
If the SGP does not authorize the registration request, the SGP returns a REG RSP message to the ASP containing the Registration Result "Error - Permission Denied".
如果SGP未授权注册请求，SGP将向ASP返回REG RSP消息，其中包含注册结果“错误-权限被拒绝”。
If an SGP determines that a received Link Key does not currently exist and the SGP does not support dynamic configuration, the SGP returns a Registration Response message to the ASP, containing a Registration Result "Error - Link Key not Provisioned".
如果SGP确定接收到的链接密钥当前不存在，并且SGP不支持动态配置，则SGP将向ASP返回注册响应消息，其中包含注册结果“错误-未设置链接密钥”。
If an SGP determines that a received Link Key does not currently exist and the SGP supports dynamic reconfiguration but does not have the capacity to add new Link Key and Application Server entries, the SGP returns a Registration Response message to the ASP, containing a Registration Result "Error - Insufficient Resources".
如果SGP确定接收到的链接密钥当前不存在，SGP支持动态重新配置，但没有能力添加新的链接密钥和应用程序服务器条目，则SGP将向ASP返回注册响应消息，其中包含注册结果“错误-资源不足”。
An ASP MAY register multiple Link Keys at once by including a number of Link Key parameters in a single REG REQ message. The SGP MAY respond to each registration request in a single REG RSP message, indicating the success or failure result for each Link Key in a separate Registration Result parameter. Alternatively, the SGP MAY respond with multiple REG RSP messages, each with one or more Registration Result parameters. The ASP uses the Local-LK-Identifier parameter to correlate the requests with the responses.
ASP可以通过在单个REG REQ消息中包含多个链接键参数，一次注册多个链接键。SGP可以在单个REG RSP消息中响应每个注册请求，在单独的注册结果参数中指示每个链路密钥的成功或失败结果。或者，SGP可以使用多个REG RSP消息进行响应，每个消息具有一个或多个注册结果参数。ASP使用本地LK标识符参数将请求与响应关联起来。
An ASP MAY dynamically de-register with an SGP as an ASP within an Application Server for individual Interface Identifier(s) using the DEREG REQ message. A Interface Identifier parameter in the DEREG REQ specifies which Interface Identifier to de-register.
ASP可以使用DEREG REQ消息，在应用服务器内动态地向SGP注销单个接口标识符的ASP。DEREG REQ中的接口标识符参数指定要取消注册的接口标识符。
The SGP examines the contents of the received Interface Identifier parameter and validates that the ASP is currently registered in the Application Server(s) related to the included Interface Identifier(s). If validated, the ASP is de-registered as an ASP in the related Application Server.
SGP检查收到的接口标识符参数的内容，并验证ASP当前是否已在与包含的接口标识符相关的应用程序服务器中注册。如果已验证，则ASP将在相关应用程序服务器中取消注册为ASP。
The deregistration procedure does not necessarily imply the deletion of Link Key and Application Server configuration data at the SGP. Other ASPs may continue to be associated with the Application Server,
注销过程不一定意味着在SGP上删除链路密钥和应用程序服务器配置数据。其他ASP可能会继续与应用程序服务器关联，
in which case the Link Key data CANNOT be deleted. If a Deregistration results in no more ASPs in an Application Server, an SGP MAY delete the Link Key data.
在这种情况下，无法删除链接密钥数据。如果取消注册导致应用服务器中没有更多的ASP，则SGP可以删除链接密钥数据。
The SGP acknowledges the de-registration required by returning a DEREG RSP to the requesting ASP. The result of the de-registration is found in the Deregistration Result parameter, indicating success or failure with cause.
SGP通过向请求的ASP返回撤销注册RSP来确认所需的撤销注册。取消注册的结果可在“注销结果”参数中找到，表示成功或失败的原因。
An ASP MAY de-register multiple Interface Identifiers at once by including a number of Interface Identifiers in a single DEREG REQ message. The SGP MUST respond to each deregistration request in a single DEREG RSP message, indicating the success or failure result for each Interface Identifier in a separate Deregistration Result parameter.
ASP可通过在单个DEREG REQ消息中包括多个接口标识符，一次注销多个接口标识符。SGP必须在单个撤销RSP消息中响应每个撤销注册请求，在单独的撤销注册结果参数中指示每个接口标识符的成功或失败结果。
This scenario shows the example M2UA message flows for the establishment of traffic between an SGP and an ASP, where only one ASP is configured within an AS (no backup). It is assumed that the SCTP association is already set-up.
此场景显示了用于在SGP和ASP之间建立流量的示例M2UA消息流，其中AS中仅配置了一个ASP（无备份）。假设SCTP关联已经建立。
SGP ASP1
|
|<---------ASP Up----------|
|--------ASP Up Ack------->|
| |
|<-------ASP Active--------|
|------ASP Active Ack----->|
| |
|------NTFY(AS-ACTIVE)---->|
SGP ASP1
|
|<---------ASP Up----------|
|--------ASP Up Ack------->|
| |
|<-------ASP Active--------|
|------ASP Active Ack----->|
| |
|------NTFY(AS-ACTIVE)---->|
5.1.2 Single ASP in an Application Server (1+0 sparing) with Dynamic Registration
5.1.2 应用服务器中的单个ASP（1+0备用），具有动态注册
This scenario is the same as the one shown in Section 5.1.1 except with a dynamic registration (automatic allocation) of an Interface Identifier(s).
该场景与第5.1.1节中所示的场景相同，只是动态注册（自动分配）接口标识符。
SGP ASP1
|
|<---------ASP Up----------|
|--------ASP Up Ack------->|
| |
|<--------REG REQ----------|
|------REG REQ RESP------->|
| |
|<-------ASP Active--------|
|------ASP Active Ack----->|
| |
|------NTFY(AS-ACTIVE)---->|
SGP ASP1
|
|<---------ASP Up----------|
|--------ASP Up Ack------->|
| |
|<--------REG REQ----------|
|------REG REQ RESP------->|
| |
|<-------ASP Active--------|
|------ASP Active Ack----->|
| |
|------NTFY(AS-ACTIVE)---->|
This scenario shows the example M2UA message flows for the establishment of traffic between an SGP and two ASPs in the same Application Server, where ASP1 is configured to be active and ASP2 to be standby in the event of communication failure or the withdrawal from service of ASP1. ASP2 MAY act as a hot, warm, or cold standby depending on the extent to which ASP1 and ASP2 share call/transaction state or can communicate call state under failure/withdrawal events.
此场景显示了用于在同一应用服务器中的一个SGP和两个ASP之间建立流量的示例M2UA消息流，其中ASP1配置为活动，ASP2配置为备用，以防通信故障或ASP1退出服务。根据ASP1和ASP2在多大程度上共享呼叫/事务状态，或者在故障/退出事件下可以通信呼叫状态，ASP2可以作为热备、热备或冷备。
SGP ASP1 ASP2
| | |
|<--------ASP Up----------| |
|-------ASP Up Ack------->| |
| | |
|<-----------------------------ASP Up----------------|
|----------------------------ASP Up Ack------------->|
| | |
| | |
|<-------ASP Active-------| |
|-----ASP Active Ack----->| |
| | |
| | |
|-----NTFY(AS-ACTIVE)---->| |
| | |
|------------------NTFY(AS-ACTIVE)------------------>|
SGP ASP1 ASP2
| | |
|<--------ASP Up----------| |
|-------ASP Up Ack------->| |
| | |
|<-----------------------------ASP Up----------------|
|----------------------------ASP Up Ack------------->|
| | |
| | |
|<-------ASP Active-------| |
|-----ASP Active Ack----->| |
| | |
| | |
|-----NTFY(AS-ACTIVE)---->| |
| | |
|------------------NTFY(AS-ACTIVE)------------------>|
Following on from the example in Section 5.1.2, and ASP withdraws from service:
根据第5.1.2节中的示例，ASP退出服务：
SGP ASP1 ASP2
| | |
|<-----ASP Inactive-------| |
|----ASP Inactive Ack---->| |
| | |
|----NTFY(AS-PENDING)---->| |
|------------------NTFY(AS-PENDING)----------------->|
| | |
|<------------------------------ ASP Active----------|
|-----------------------------ASP Active Ack-------->|
| | |
|-----NTFY(AS-ACTIVE)---->| |
|------------------NTFY(AS-ACTIVE)------------------>|
| | |
SGP ASP1 ASP2
| | |
|<-----ASP Inactive-------| |
|----ASP Inactive Ack---->| |
| | |
|----NTFY(AS-PENDING)---->| |
|------------------NTFY(AS-PENDING)----------------->|
| | |
|<------------------------------ ASP Active----------|
|-----------------------------ASP Active Ack-------->|
| | |
|-----NTFY(AS-ACTIVE)---->| |
|------------------NTFY(AS-ACTIVE)------------------>|
| | |
In this case, the SGP notifies ASP2 that the AS has moved to the AS-PENDING state. ASP2 sends ASP Active to bring the AS back to the AS-ACTIVE state. If ASP2 did not send the ASP Active message before T(r) expired, the SGP would send a NOTIFY (AS-DOWN).
在这种情况下，SGP通知ASP2 AS已移动到AS-PENDING状态。ASP2发送ASP Active以使AS返回AS-Active状态。如果ASP2在T（r）过期之前未发送ASP活动消息，则SGP将发送通知（AS-DOWN）。
Note: If the SGP detects loss of the M2UA peer (through a detection of SCTP failure), the initial SGP-ASP1 ASP Inactive message exchange would not occur.
注意：如果SGP检测到M2UA对等机丢失（通过检测SCTP故障），则不会发生初始SGP-ASP1 ASP非活动消息交换。
SGP ASP1 ASP2
| | |
(detects SCTP failure)
|------------------NTFY(AS-PENDING)----------------->|
| | |
|<------------------------------ ASP Active----------|
|-----------------------------ASP Active Ack-------->|
| | |
|------------------NTFY(AS-ACTIVE)------------------>|
| | |
SGP ASP1 ASP2
| | |
(detects SCTP failure)
|------------------NTFY(AS-PENDING)----------------->|
| | |
|<------------------------------ ASP Active----------|
|-----------------------------ASP Active Ack-------->|
| | |
|------------------NTFY(AS-ACTIVE)------------------>|
| | |
Following on from the example in Section 5.1.2, and ASP2 wishes to override ASP1 and take over the traffic:
根据第5.1.2节中的示例，ASP2希望覆盖ASP1并接管流量：
SGP ASP1 ASP2
| | |
|<-------------------------------ASP Active----------|
|-----------------------------ASP Active Ack-------->|
|----NTFY(Alt ASP-Act)--->| |
| | |
SGP ASP1 ASP2
| | |
|<-------------------------------ASP Active----------|
|-----------------------------ASP Active Ack-------->|
|----NTFY(Alt ASP-Act)--->| |
| | |
In this case, the SGP notifies ASP1 that an alternative ASP has overridden it.
在这种情况下，SGP通知ASP1替代ASP已覆盖它。
When the M2UA layer on the ASP has a MAUP message to send to the SGP, it will do the following:
当ASP上的M2UA层向SGP发送MAUP消息时，它将执行以下操作：
- Determine the correct SGP
- 确定正确的SGP
- Find the SCTP association to the chosen SGP
- 查找与所选SGP的SCTP关联
- Determine the correct stream in the SCTP association based on the SS7 link
- 根据SS7链路确定SCTP关联中的正确流
- Fill in the MAUP message, fill in M2UA Message Header, fill in Common Header
- 填写MAUP报文，填写M2UA报文头，填写公共报文头
- Send the MAUP message to the remote M2UA peer in the SGP, over the SCTP association
- 通过SCTP关联向SGP中的远程M2UA对等方发送MAUP消息
When the M2UA layer on the SGP has a MAUP message to send to the ASP, it will do the following:
当SGP上的M2UA层向ASP发送MAUP消息时，它将执行以下操作：
- Determine the AS for the Interface Identifier
- 确定接口标识符的AS
- Determine the Active ASP (SCTP association) within the AS
- 确定AS中的活动ASP（SCTP关联）
- Determine the correct stream in the SCTP association based on the SS7 link
- 根据SS7链路确定SCTP关联中的正确流
- Fill in the MAUP message, fill in M2UA Message Header, fill in Common Header
- 填写MAUP报文，填写M2UA报文头，填写公共报文头
- Send the MAUP message to the remote M2UA peer in the ASP, over the SCTP association
- 通过SCTP关联向ASP中的远程M2UA对等方发送MAUP消息
The MGC can request that a SS7 link be brought into alignment using the normal or emergency procedure [2][3]. An example of the message flow to bring a SS7 link in-service using the normal alignment procedure is shown below.
MGC可以使用正常或紧急程序[2][3]请求对准SS7链路。使用正常校准程序使SS7链路投入使用的消息流示例如下所示。
MTP2 M2UA M2UA MTP3 SGP SGP ASP ASP
MTP2 M2UA M2UA MTP3 SGP SGP ASP
<----Start Req---|<---Establish Req----|<----Start Req------
<----Start Req---|<---Establish Req----|<----Start Req------
---In Serv Ind-->|----Establish Cfm--->|----In Serv Ind---->
---In Serv Ind-->|----Establish Cfm--->|----In Serv Ind---->
An example of the message flow to bring a SS7 link in-service using the emergency alignment procedure.
使用紧急校准程序使SS7链路投入使用的消息流示例。
MTP2 M2UA M2UA MTP3 SGP SGP ASP ASP
MTP2 M2UA M2UA MTP3 SGP SGP ASP
<----Emer Req----|<--State Req (STATUS_EMER_SET)----|<----Emer Req---
<----Emer Req----|<--State Req (STATUS_EMER_SET)----|<----Emer Req---
-----Emer Cfm--->|---State Cfm (STATUS_EMER_SET)--->|----Emer Cfm---->
-----Emer Cfm--->|---State Cfm (STATUS_EMER_SET)--->|----Emer Cfm---->
<---Start Req----|<-------Establish Req-------------|<---Start Req----
<---Start Req----|<-------Establish Req-------------|<---Start Req----
---In Serv Ind-->|--------Establish Cfm------------>|---In Serv Ind-->
---In Serv Ind-->|--------Establish Cfm------------>|---In Serv Ind-->
The MGC can request that a SS7 link be taken out-of-service. It uses the Release Request message as shown below.
MGC可以请求SS7链路停止服务。它使用释放请求消息，如下所示。
MTP2 M2UA M2UA MTP3 SGP SGP ASP ASP
MTP2 M2UA M2UA MTP3 SGP SGP ASP
<-----Stop Req-----|<---Release Req------|<-----Stop Req------
<-----Stop Req-----|<---Release Req------|<-----Stop Req------
--Out of Serv Ind->|----Release Cfm----->|--Out of Serv Ind-->
--Out of Serv Ind->|----Release Cfm----->|--Out of Serv Ind-->
The SGP can autonomously indicate that a SS7 link has gone out-of-service as shown below.
SGP可以自动指示SS7链路已停止服务，如下所示。
MTP2 M2UA M2UA MTP3 SGP SGP ASP ASP
MTP2 M2UA M2UA MTP3 SGP SGP ASP
--Out of Serv->|----Release Ind----->|--Out of Serv-->
--Out of Serv->|----Release Ind----->|--Out of Serv-->
The MGC can set a Local Processor Outage condition. It uses the State Request message as shown below.
MGC可以设置本地处理器中断条件。它使用状态请求消息，如下所示。
MTP2 M2UA M2UA MTP3 SGP SGP ASP ASP
MTP2 M2UA M2UA MTP3 SGP SGP ASP
<----LPO Req----|<---State Req (STATUS_LPO_SET)----|<----LPO Req---
<----LPO Req----|<---State Req (STATUS_LPO_SET)----|<----LPO Req---
-----LPO Cfm--->|----State Cfm (STATUS_LPO_SET)--->|----LPO Cfm---->
-----LPO Cfm--->|----State Cfm (STATUS_LPO_SET)--->|----LPO Cfm---->
The MGC can clear a Local Processor Outage condition. It uses the State Request message as shown below.
MGC可以清除本地处理器中断情况。它使用状态请求消息，如下所示。
MTP2 M2UA M2UA MTP3 SGP SGP ASP ASP
MTP2 M2UA M2UA MTP3 SGP SGP ASP
<---LPO Req---|<---State Req (STATUS_LPO_CLEAR)----|<----LPO Req---
<---LPO Req---|<---State Req (STATUS_LPO_CLEAR)----|<----LPO Req---
----LPO Cfm-->|----State Cfm (STATUS_LPO_CLEAR)--->|----LPO Cfm---->
----LPO Cfm-->|----State Cfm (STATUS_LPO_CLEAR)--->|----LPO Cfm---->
The SGP can indicate that Remote has entered or exited the Processor Outage condition for a SS7 link. It uses the State Indication message as shown below.
SGP可以指示Remote已进入或退出SS7链路的处理器中断条件。它使用如下所示的状态指示消息。
MTP2 M2UA M2UA MTP3 SGP SGP ASP ASP
MTP2 M2UA M2UA MTP3 SGP SGP ASP
----RPO Ind---->|----State Ind (EVENT_RPO_ENTER)-->|-----RPO Ind---->
----RPO Ind---->|----State Ind (EVENT_RPO_ENTER)-->|-----RPO Ind---->
-RPO Rcvr Ind-->|----State Ind (EVENT_RPO_EXIT)--->|--RPO Rcvr Ind-->
-RPO Rcvr Ind-->|----State Ind (EVENT_RPO_EXIT)--->|--RPO Rcvr Ind-->
The SGP can indicate that a SS7 link has become congested. It uses the Congestion Indication message as shown below.
SGP可以指示SS7链路已变得拥挤。它使用拥塞指示消息，如下所示。
MTP2 M2UA M2UA MTP3 SGP SGP ASP ASP
MTP2 M2UA M2UA MTP3 SGP SGP ASP
----Cong Ind---->|--------Cong Ind (STATUS)------->|----Cong Ind---->
----Cong Ind---->|--------Cong Ind (STATUS)------->|----Cong Ind---->
-Cong Cease Ind->|--------Cong Ind (STATUS)------->|-Cong Cease Ind->
-Cong Cease Ind->|--------Cong Ind (STATUS)------->|-Cong Cease Ind->
An example of the message flow for an error free changeover is shown below. In this example, there were three messages in the retransmission queue that needed to be retrieved.
下面显示了无错误转换的消息流示例。在本例中，重传队列中有三条消息需要检索。
MTP2 M2UA M2UA MTP3 SGP SGP ASP ASP
MTP2 M2UA M2UA MTP3 SGP SGP ASP
<-Rtrv BSN Req-|<--Rtrv Req (ACTION_RTRV_BSN)--|<--Rtrv BSN Req---
(seq_num = 0)
<-Rtrv BSN Req-|<--Rtrv Req (ACTION_RTRV_BSN)--|<--Rtrv BSN Req---
(seq_num = 0)
-Rtrv BSN Cfm->|---Rtrv Cfm (ACTION_RTRV_BSN)->|---Rtrv BSN Cfm-->
(seq_num = BSN)
-Rtrv BSN Cfm->|---Rtrv Cfm (ACTION_RTRV_BSN)->|---Rtrv BSN Cfm-->
(seq_num = BSN)
<-Rtrv Msg Req-|<-Rtrv Req (ACTION_RTRV_MSGS)--|<--Rtrv Msg Req---
(seq_num = FSN)
<-Rtrv Msg Req-|<-Rtrv Req (ACTION_RTRV_MSGS)--|<--Rtrv Msg Req---
(seq_num = FSN)
-Rtrv Msg Cfm->|--Rtrv Cfm (ACTION_RTRV_MSGS)->|---Rtrv Msg Cfm-->
(seq_num = 0)
-Rtrv Msg Cfm->|--Rtrv Cfm (ACTION_RTRV_MSGS)->|---Rtrv Msg Cfm-->
(seq_num = 0)
-Rtrv Msg Ind->|---------Retrieval Ind ------->|---Rtrv Msg Ind-->
-Rtrv Msg Ind->|---------Retrieval Ind ------->|---Rtrv Msg Ind-->
-Rtrv Msg Ind->|---------Retrieval Ind ------->|---Rtrv Msg Ind-->
-Rtrv Msg Ind->|---------Retrieval Ind ------->|---Rtrv Msg Ind-->
-Rtrv Msg Ind->|---------Retrieval Ind ------->|---Rtrv Msg Ind-->
-Rtrv Msg Ind->|---------Retrieval Ind ------->|---Rtrv Msg Ind-->
-Rtrv Compl Ind->|----Retrieval Compl Ind ---->|-Rtrv Compl Ind-->
-Rtrv Compl Ind->|----Retrieval Compl Ind ---->|-Rtrv Compl Ind-->
Note: The number of Retrieval Indication is dependent on the number of messages in the retransmit queue that have been requested. Only one Retrieval Complete Indication SHOULD be sent.
注意：检索指示的数量取决于重传队列中已请求的消息数量。只应发送一个检索完整指示。
An example of a message flow with an error retrieving the BSN is shown below.
下面显示了检索BSN时出错的消息流示例。
MTP2 M2UA M2UA MTP3 SGP SGP ASP ASP
MTP2 M2UA M2UA MTP3 SGP SGP ASP
<-Rtrv BSN Req-|<--Rtrv Req (ACTION_RTRV_BSN)--|<--Rtrv BSN Req---
<-Rtrv BSN Req-|<--Rtrv Req (ACTION_RTRV_BSN)--|<--Rtrv BSN Req---
-BSN Not Rtrv->|---Rtrv Cfm (ACTION_RTRV_BSN)->|---BSN Not Rtrv-->
(seq_num = -1)
-BSN Not Rtrv->|---Rtrv Cfm (ACTION_RTRV_BSN)->|---BSN Not Rtrv-->
(seq_num = -1)
An example of a message flow with an error retrieving the messages is shown below.
下面显示了检索消息时出错的消息流示例。
<-Rtrv BSN Req-|<--Rtrv Req (ACTION_RTRV_BSN)--|<--Rtrv BSN Req---
<-Rtrv BSN Req-|<--Rtrv Req (ACTION_RTRV_BSN)--|<--Rtrv BSN Req---
-Rtrv BSN Cfm->|---Rtrv Cfm (ACTION_RTRV_BSN)->|---Rtrv BSN Cfm-->
(seq_num = BSN)
-Rtrv BSN Cfm->|---Rtrv Cfm (ACTION_RTRV_BSN)->|---Rtrv BSN Cfm-->
(seq_num = BSN)
<-Rtrv Msg Req-|<-Rtrv Req (ACTION_RTRV_MSGS)--|<--Rtrv Msg Req---
(seq_num = FSN)
<-Rtrv Msg Req-|<-Rtrv Req (ACTION_RTRV_MSGS)--|<--Rtrv Msg Req---
(seq_num = FSN)
-Rtrv Msg Cfm->|--Rtrv Cfm (ACTION_RTRV_MSGS)->|---Rtrv Msg Cfm-->
(seq_num = -1)
-Rtrv Msg Cfm->|--Rtrv Cfm (ACTION_RTRV_MSGS)->|---Rtrv Msg Cfm-->
(seq_num = -1)
An example of a message flow for a request to drop messages (clear retransmission buffers) is shown below.
请求丢弃消息（清除重传缓冲区）的消息流示例如下所示。
MTP2 M2UA M2UA MTP3 SGP SGP ASP ASP
MTP2 M2UA M2UA MTP3 SGP SGP ASP
-Clr RTB Req----|<-StateReq (STATUS_CLEAR_RTB)--|<--Clr RTB Req-----
-Clr RTB Req----|<-StateReq (STATUS_CLEAR_RTB)--|<--Clr RTB Req-----
-Clr RTB Req--->|-StateCfm (STATUS_CLEAR_RTB)-->|---Clr RTB Req---->
-Clr RTB Req--->|-StateCfm (STATUS_CLEAR_RTB)-->|---Clr RTB Req---->
The following message flow shows a request to flush buffers.
下面的消息流显示刷新缓冲区的请求。
MTP2 M2UA M2UA MTP3 SGP SGP ASP ASP
MTP2 M2UA M2UA MTP3 SGP SGP ASP
<--Flush Req----|<-State Req (STATUS_FLUSH_BUFS)--|<---Flush Req--
<--Flush Req----|<-State Req (STATUS_FLUSH_BUFS)--|<---Flush Req--
---Flush Cfm--->|--State Cfm (STATUS_FLUSH_BUFS)->|---Flush Cfm-->
---Flush Cfm--->|--State Cfm (STATUS_FLUSH_BUFS)->|---Flush Cfm-->
The following message flow shows a request to continue.
下面的消息流显示了继续的请求。
MTP2 M2UA M2UA MTP3 SGP SGP ASP ASP
MTP2 M2UA M2UA MTP3 SGP SGP ASP
<---Cont Req----|<--State Req (STATUS_CONTINUE)---|<---Cont Req---
<---Cont Req----|<--State Req (STATUS_CONTINUE)---|<---Cont Req---
----Cont Cfm--->|---State Cfm (STATUS_CONTINUE)-->|----Cont Cfm-->
----Cont Cfm--->|---State Cfm (STATUS_CONTINUE)-->|----Cont Cfm-->
It may be necessary for the ASP to audit the current state of a SS7 link. The flows below show an example of the request and all the potential responses.
ASP可能需要审核SS7链路的当前状态。下面的流程显示了请求和所有潜在响应的示例。
Below is an example in which the SS7 link is out-of-service.
下面是SS7链路停止服务的示例。
MTP2 M2UA M2UA MGMT SGP SGP ASP ASP
MTP2 M2UA M2UA管理SGP SGP ASP
|<----State Req (STATUS_AUDIT)----|<----Audit-------
|<----State Req (STATUS_AUDIT)----|<----Audit-------
MTP3 ASP
MTP3 ASP
|-----------Release Ind---------->|-Out of Serv Ind->
|-----------Release Ind---------->|-Out of Serv Ind->
MGMT ASP
管理ASP
|-----State Cfm (STATUS_AUDIT)--->|----Audit Cfm--->
|-----State Cfm (STATUS_AUDIT)--->|----Audit Cfm--->
Below is an example in which the SS7 link is in-service.
下面是SS7链路正在使用的示例。
MTP2 M2UA M2UA MGMT SGP SGP ASP ASP
MTP2 M2UA M2UA管理SGP SGP ASP
|<----State Req (STATUS_AUDIT)----|<----Audit-------
|<----State Req (STATUS_AUDIT)----|<----Audit-------
MTP3 ASP
MTP3 ASP
|-----------Establish Cfm-------->|---In Serv Ind-->
|-----------Establish Cfm-------->|---In Serv Ind-->
MGMT ASP
管理ASP
|-----State Cfm (STATUS_AUDIT)--->|----Audit Cfm--->
|-----State Cfm (STATUS_AUDIT)--->|----Audit Cfm--->
Below is an example in which the SS7 link is in-service, but congested.
下面是一个示例，其中SS7链路在使用中，但拥塞。
MTP2 M2UA M2UA MGMT SGP SGP ASP ASP
MTP2 M2UA M2UA管理SGP SGP ASP
|<----State Req (STATUS_AUDIT)----|<----Audit-------
|<----State Req (STATUS_AUDIT)----|<----Audit-------
MTP3 ASP
MTP3 ASP
|-----------Establish Cfm-------->|---In Serv Ind-->
|-----------Establish Cfm-------->|---In Serv Ind-->
|----------Congestion Ind-------->|---Cong Ind----->
|----------Congestion Ind-------->|---Cong Ind----->
MGMT ASP
管理ASP
|-----State Cfm (STATUS_AUDIT)--->|----Audit Cfm--->
|-----State Cfm (STATUS_AUDIT)--->|----Audit Cfm--->
Below is an example in which the SS7 link is in-service, but in Remote Processor Outage.
下面是一个示例，其中SS7链路正在使用中，但处于远程处理器中断状态。
MTP2 M2UA M2UA MGMT SGP SGP ASP ASP
MTP2 M2UA M2UA管理SGP SGP ASP
|<----State Req (STATUS_AUDIT)----|<---Audit Req----
|<----State Req (STATUS_AUDIT)----|<---Audit Req----
MTP3 ASP
MTP3 ASP
|-----------Establish Ind-------->|---In Serv Ind-->
|-----------Establish Ind-------->|---In Serv Ind-->
|---State Ind (EVENT_RPO_ENTER)-->|----RPO Enter--->
|---State Ind (EVENT_RPO_ENTER)-->|----RPO Enter--->
MGMT ASP
管理ASP
|-----State Cfm (STATUS_AUDIT)--->|----Audit Cfm--->
|-----State Cfm (STATUS_AUDIT)--->|----Audit Cfm--->
The recommended default values for M2UA timers are:
M2UA定时器的推荐默认值为：
T(r) 2 seconds T(ack) 2 seconds T(beat) Heartbeat Timer 30 seconds
T（r）2秒T（确认）2秒T（节拍）心跳计时器30秒
M2UA is designed to carry signalling messages for telephony services. As such, M2UA MUST involve the security needs of several parties: the end users of the services; the network providers and the applications involved. Additional requirements MAY come from local regulation. While having some overlapping security needs, any security solution SHOULD fulfill all of the different parties' needs.
M2UA设计用于承载电话服务的信令消息。因此，M2UA必须涉及多方的安全需求：服务的最终用户；网络提供商和涉及的应用程序。其他要求可能来自当地法规。尽管存在一些重叠的安全需求，但任何安全解决方案都应该满足不同各方的所有需求。
There is no quick fix, one-size-fits-all solution for security. As a transport protocol, M2UA has the following security objectives:
没有快速修复、一刀切的安全解决方案。作为一种传输协议，M2UA具有以下安全目标：
* Availability of reliable and timely user data transport. * Integrity of user data transport. * Confidentiality of user data.
* 提供可靠、及时的用户数据传输。*用户数据传输的完整性。*用户数据的保密性。
M2UA runs on top of SCTP. SCTP [8] provides certain transport related security features, such as:
M2UA运行在SCTP之上。SCTP[8]提供了某些与传输相关的安全功能，例如：
* Blind Denial of Service Attacks * Flooding * Masquerade * Improper Monopolization of Services
* 盲目拒绝服务攻击*泛滥*伪装*不正当的服务垄断
When M2UA is running in a professionally managed corporate or service provider network, it is reasonable to expect that this network includes an appropriate security policy framework. The "Site Security Handbook" [13] SHOULD be consulted for guidance.
当M2UA在专业管理的公司或服务提供商网络中运行时，可以合理预期该网络包含适当的安全策略框架。应参考“现场安全手册”[13]以获取指导。
When the network in which M2UA runs in involves more than one party, it MAY NOT be reasonable to expect that all parties have implemented security in a sufficient manner. In such a case, it is recommended that IPSEC is used to ensure confidentiality of user payload. Consult [14] for more information on configuring IPSEC services.
当M2UA运行的网络涉及多个参与方时，期望所有参与方都以充分的方式实施了安全性可能是不合理的。在这种情况下，建议使用IPSEC来确保用户负载的机密性。有关配置IPSEC服务的更多信息，请参阅[14]。
Particularly for mobile users, the requirement for confidentiality MAY include the masking of IP addresses and ports. In this case application level encryption is not sufficient; IPSEC ESP SHOULD be used instead. Regardless of which level performs the encryption, the IPSEC ISAKMP service SHOULD be used for key management.
特别是对于移动用户，保密性要求可能包括屏蔽IP地址和端口。在这种情况下，应用程序级加密是不够的；应改用IPSEC ESP。无论哪个级别执行加密，都应使用IPSEC ISAKMP服务进行密钥管理。
A request will be made to IANA to assign an M2UA value for the Payload Protocol Identifier in SCTP Payload Data chunk. The following SCTP Payload Protocol Identifier has been registered:
将向IANA发出请求，为SCTP有效负载数据块中的有效负载协议标识符分配M2UA值。已注册以下SCTP有效负载协议标识符：
M2UA "2"
M2UA“2”
The SCTP Payload Protocol Identifier is included in each SCTP Data chunk, to indicate which protocol the SCTP is carrying. This Payload Protocol Identifier is not directly used by SCTP but MAY be used by certain network entities to identify the type of information being carried in a Data chunk.
SCTP有效负载协议标识符包含在每个SCTP数据块中，以指示SCTP承载的协议。此有效负载协议标识符不直接由SCTP使用，但可由某些网络实体用于标识数据块中承载的信息类型。
The User Adaptation peer MAY use the Payload Protocol Identifier as a way of determining additional information about the data being presented to it by SCTP.
用户适配对等方可以使用有效负载协议标识符作为确定关于由SCTP呈现给它的数据的附加信息的方式。
This protocol may also be extended through IANA in three ways:
本协议也可通过IANA以三种方式扩展：
-- through definition of additional message classes,
-- through definition of additional message types, and
-- through definition of additional message parameters.
-- through definition of additional message classes,
-- through definition of additional message types, and
-- through definition of additional message parameters.
The definition and use of new message classes, types and parameters is an integral part of SIGTRAN adaptation layers. Thus, these extensions are assigned by IANA through an IETF Consensus action as defined in [RFC2434].
新消息类、类型和参数的定义和使用是SIGTRAN适配层不可分割的一部分。因此，IANA通过[RFC2434]中定义的IETF共识行动分配这些扩展。
The proposed extension must in no way adversely affect the general working of the protocol.
拟议的延期决不能对议定书的一般工作产生不利影响。
The documentation for a new message class MUST include the following information:
新消息类的文档必须包括以下信息：
(a) A long and short name for the message class. (b) A detailed description of the purpose of the message class.
(a) 消息类的长名称和短名称。（b） 消息类用途的详细说明。
Documentation of the message type MUST contain the following information:
消息类型的文档必须包含以下信息：
(a) A long and short name for the new message type. (b) A detailed description of the structure of the message. (c) A detailed definition and description of intended use of each field within the message. (d) A detailed procedural description of the use of the new message type within the operation of the protocol. (e) A detailed description of error conditions when receiving this message type.
(a) 新消息类型的长名称和短名称。（b） 对消息结构的详细描述。（c） 对消息中每个字段的预期用途的详细定义和说明。（d） 协议操作中使用新消息类型的详细过程描述。（e） 接收此消息类型时错误情况的详细说明。
When an implementation receives a message type which it does not support, it MUST respond with an Error (ERR) message with an Error Code of Unsupported Message Type.
当实现接收到不支持的消息类型时，它必须以错误（ERR）消息响应，错误代码为不支持的消息类型。
Documentation of the message parameter MUST contain the following information:
消息参数的文档必须包含以下信息：
(a) Name of the parameter type. (b) Detailed description of the structure of the parameter field. This structure MUST conform to the general type-length-value format described in Section 3.1.5. (c) Detailed definition of each component of the parameter value. (d) Detailed description of the intended use of this parameter type, and an indication of whether and under what circumstances multiple instances of this parameter type may be found within the same message type.
(a) 参数类型的名称。（b） 参数字段结构的详细说明。该结构必须符合第3.1.5节所述的通用类型长度值格式。（c） 参数值的每个组件的详细定义。（d） 此参数类型的预期用途的详细说明，以及是否以及在何种情况下可在同一消息类型中找到此参数类型的多个实例的指示。
The authors would like to thank Tom George (Alcatel) for contribution of text and effort on the specification.
作者要感谢Tom George（Alcatel）对规范的文本贡献和努力。
The authors would like to thank John Loughney, Neil Olson, Michael Tuexen, Nikhil Jain, Steve Lorusso, Dan Brendes, Joe Keller, Heinz Prantner, Barry Nagelberg, Naoto Makinae, Joyce Archibald, Mark Kobine, Nitin Tomar, Harsh Bhondwe and Karen King for their valuable comments and suggestions.
作者要感谢约翰·拉夫尼、尼尔·奥尔森、迈克尔·图克森、尼希尔·杰恩、史蒂夫·洛鲁索、丹·布伦德斯、乔·凯勒、海因茨·普兰特纳、巴里·纳格尔伯格、纳奥托·马金奈、乔伊斯·阿奇博尔德、马克·科宾、尼廷·托马斯、哈什·邦德和卡伦·金，感谢他们提出的宝贵意见和建议。
[1] ITU-T Recommendation Q.700, 'Introduction To ITU-T Signalling System No. 7 (SS7)'
[1] ITU-T建议Q.700，“第7号ITU-T信令系统（SS7）简介”
[2] ITU-T Recommendation Q.701-Q.705, 'Signalling System No. 7 (SS7) - Message Transfer Part (MTP)'
[2] ITU-T建议Q.701-Q.705，“第7号信令系统（SS7）-消息传输部分（MTP）”
[3] ANSI T1.111 'Signalling System Number 7 - Message Transfer Part'
[3] ANSI T1.111“7号信号系统-信息传输部分”
[4] Bellcore GR-246-CORE 'Bell Communications Research Specification of Signalling System Number 7', Volume 1, December 1995
[4] Bellcore GR-246-CORE“信号系统7号贝尔通信研究规范”，第1卷，1995年12月
[5] Telecommunication Technology Committee (TTC) Standard JT-Q704, Message Transfer Part Signaling Network Functions, April 28, 1992.
[5] 电信技术委员会（TTC）标准JT-Q704，信息传输部分信令网络功能，1992年4月28日。
[6] Yergeau, F., "UTF-8, a transformation format of ISO 10646", RFC 2279, January 1998.
[6] “UTF-8，ISO 10646的转换格式”，RFC 2279，1998年1月。
[7] Coded Character Set--7-Bit American Standard Code for Information Interchange, ANSI X3.4-1986.
[7] 编码字符集——信息交换用7位美国标准代码，ANSI X3.4-1986。
[8] Stewart, R., Xie, Q., Morneault, K., Sharp, C., Schwarzbauer, H., Taylor, T., Rytina, I., Kalla, M., Zhang, L. and V. Paxson, "Stream Control Transmission Protocol", RFC 2960, October 2000.
[8] Stewart，R.，Xie，Q.，Morneault，K.，Sharp，C.，Schwarzbauer，H.，Taylor，T.，Rytina，I.，Kalla，M.，Zhang，L.和V.Paxson，“流控制传输协议”，RFC 29602000年10月。
[9] Ong, L., Rytina, I., Garcia, M., Schwarzbauer, H., Coene, L., Lin, H., Juhasz, I., Holdrege, M. and C. Sharp, "Architectural Framework for Signalling Transport", RFC 2719, October 1999.
[9] Ong，L.，Rytina，I.，Garcia，M.，Schwarzbauer，H.，Coene，L.，Lin，H.，Juhasz，I.，Holdrege，M.和C.Sharp，“信号传输的架构框架”，RFC 2719，1999年10月。
[10] ITU-T Recommendation Q.2140, 'B-ISDN ATM Adaptation Layer', February 1995
[10] ITU-T建议Q.2140，“B-ISDN ATM适配层”，1995年2月
[11] ITU-T Recommendation Q.2210, 'Message transfer part level 3 functions and messages using the services of ITU-T Recommendation Q.2140', August 1995
[11] ITU-T建议Q.2210，“使用ITU-T建议Q.2140服务的信息传输部分3级功能和信息”，1995年8月
[12] ITU-T Recommendation Q.751.1, 'Network Element Management Information Model for the Message Transfer Part', October 1995
[12] ITU-T建议Q.751.1，“报文传输部分的网元管理信息模型”，1995年10月
[13] Fraser, B., "Site Security Handbook", FYI 8, RFC 2196, September 1997.
[13] Fraser，B.，《现场安全手册》，第8期，RFC 2196，1997年9月。
[14] Kent, S. and R. Atkinson, "Security Architecture for the Internet Protocol", RFC 2401, November 1998.
[14] Kent，S.和R.Atkinson，“互联网协议的安全架构”，RFC 2401，1998年11月。
Appendix A: Signalling Network Architecture
附录A：信令网络架构
A Signalling Gateway will support the transport of MTP2-User signalling traffic received from the SS7 network to one or more distributed ASPs (e.g., MGCs). Clearly, the M2UA protocol description cannot in itself meet any performance and reliability requirements for such transport. A physical network architecture is required, with data on the availability and transfer performance of the physical nodes involved in any particular exchange of information. However, the M2UA protocol is flexible enough to allow its operation and management in a variety of physical configurations that will enable Network Operators to meet their performance and reliability requirements.
信令网关将支持将从SS7网络接收的MTP2用户信令业务传输到一个或多个分布式ASP（例如MGC）。显然，M2UA协议描述本身无法满足此类传输的任何性能和可靠性要求。需要一个物理网络体系结构，其中包含与任何特定信息交换所涉及的物理节点的可用性和传输性能相关的数据。然而，M2UA协议具有足够的灵活性，允许其在各种物理配置中运行和管理，从而使网络运营商能够满足其性能和可靠性要求。
To meet the stringent SS7 signalling reliability and performance requirements for carrier grade networks, these Network Operators should ensure that there is no single point of failure provisioned in the end-to-end network architecture between an SS7 node and an IP ASP.
为了满足运营商级网络严格的SS7信令可靠性和性能要求，这些网络运营商应确保在SS7节点和IP ASP之间的端到端网络体系结构中不存在单点故障。
Depending of course on the reliability of the SGP and ASP functional elements, this can typically be met by spreading SS7 links in a SS7 linkset [1] across SGPs or SGs, the provision of redundant QoS-bounded IP network paths for SCTP Associations between SCTP End Points, and redundant Hosts. The distribution of ASPs within the available Hosts is also important. For a particular Application Server, the related ASPs MAY be distributed over at least two Hosts.
当然，这取决于SGP和ASP功能元件的可靠性，通常可以通过将SS7链路集[1]中的SS7链路分布在SGP或SGs上、为SCTP端点和冗余主机之间的SCTP关联提供冗余QoS受限IP网络路径来实现。ASP在可用主机中的分布也很重要。对于特定的应用服务器，相关的ASPs可以分布在至少两台主机上。
An example of logical network architecture relevant to carrier-grade operation in the IP network domain is shown in Figure 7 below:
与IP网络域中的运营商级操作相关的逻辑网络架构示例如下图7所示：
************** **************
* ********__*______________________________*__******** * Host1
SG1 * * SGP1 *__*________________ _______*__* ASP1 * *
* ******** * | | * ******** *
* . * | | * *
* . * | | **************
************** | |
| |
************** | |
* ********__*______________________|
SG2 * * SGP2 *__*________ |
* ******** * | |
* . * | |
* . * | |
************** | | **************
| |_____________*__******** * Host2
|_____________________*__* ASP2 * *
. * ******** *
. SCTP Associations * *
. **************
.
.
.
************** **************
* ********__*______________________________*__******** * Host1
SG1 * * SGP1 *__*________________ _______*__* ASP1 * *
* ******** * | | * ******** *
* . * | | * *
* . * | | **************
************** | |
| |
************** | |
* ********__*______________________|
SG2 * * SGP2 *__*________ |
* ******** * | |
* . * | |
* . * | |
************** | | **************
| |_____________*__******** * Host2
|_____________________*__* ASP2 * *
. * ******** *
. SCTP Associations * *
. **************
.
.
.
Figure 7: Logical Model Example
图7：逻辑模型示例
To avoid a single point of failure, it is recommended that a minimum of two ASPs be configured in an AS list, resident in separate hosts and, therefore, available over different SCTP associations. For example, in the network shown in Figure 7, all messages for the Interface Identifiers could be sent to ASP1 in Host1 or ASP2 in Host2. The AS list at SGP1 might look like the following:
为了避免单点故障，建议在AS列表中至少配置两个ASP，它们驻留在不同的主机中，因此可通过不同的SCTP关联使用。例如，在图7所示的网络中，接口标识符的所有消息都可以发送到Host1中的ASP1或Host2中的ASP2。SGP1上的AS列表可能如下所示：
Interface Identifiers - Application Server #1
ASP1/Host1 - State = Active
ASP2/Host2 - State = Inactive
Interface Identifiers - Application Server #1
ASP1/Host1 - State = Active
ASP2/Host2 - State = Inactive
In this 1+1 redundancy case, ASP1 in Host1 would be sent any incoming message for the Interface Identifiers registered. ASP2 in Host2 would normally be brought to the active state upon failure of ASP1/Host1. In this example, both ASPs are Inactive or Active, meaning that the related SCTP association and far-end M2UA peer is ready.
在这种1+1冗余的情况下，Host1中的ASP1将被发送注册的接口标识符的任何传入消息。当ASP1/Host1发生故障时，Host2中的ASP2通常会变为活动状态。在本例中，两个ASP都处于非活动或活动状态，这意味着相关SCTP关联和远端M2UA对等已准备就绪。
For carrier grade networks, Operators should ensure that under failure or isolation of a particular ASP, stable calls or transactions are not lost. This implies that ASPs need, in some cases, to share the call/-transaction state or be able to pass the call/transaction state between each other. Also, in the case of ASPs performing call processing, coordination MAY be required with the related Media Gateway to transfer the MGC control for a particular trunk termination. However, this sharing or communication is outside the scope of this document.
对于运营商级网络，运营商应确保在特定ASP出现故障或隔离的情况下，稳定的呼叫或事务不会丢失。这意味着在某些情况下，ASP需要共享调用/事务状态，或者能够在彼此之间传递调用/事务状态。此外，在ASPs执行呼叫处理的情况下，可能需要与相关媒体网关进行协调，以转移用于特定中继终端的MGC控制。但是，这种分享或交流不在本文件的范围之内。
Ken Morneault Cisco Systems Inc. 13615 Dulles Technology Drive Herndon, VA. 20171 USA
Ken Morneault Cisco Systems Inc.美国弗吉尼亚州赫恩登市杜勒斯技术大道13615号，邮编：20171
Phone: +1-703-484-3323
EMail: kmorneau@cisco.com
Phone: +1-703-484-3323
EMail: kmorneau@cisco.com
Ram Dantu, Ph.D. NetRake Corporation 3000 Technology Drive Plano, TX 75074 USA
拉姆·丹图博士。美国德克萨斯州普莱诺市NetRake公司3000技术大道75074号
Phone: +1-214-291-1111
EMail: rdantu@netrake.com
Phone: +1-214-291-1111
EMail: rdantu@netrake.com
Greg Sidebottom Signatus Technologies Kanata, Ontario, Canada
Greg Sidebottom Signatus Technologies加拿大安大略省卡纳塔市
EMail: greg@signatustechnologies.com
EMail: greg@signatustechnologies.com
Brian Bidulock OpenSS7 Corporation 1469 Jeffreys Crescent Edmonton, AB T6L 6T1 Canada
Brian Bidulock OpenSS7 Corporation 1469 Jeffreys Crescent Edmonton，AB T6L 6T1加拿大
Phone: +1-780-490-1141
EMail: bidulock@openss7.org
Phone: +1-780-490-1141
EMail: bidulock@openss7.org
Jacob Heitz Lucent Technologies 1701 Harbor Bay Parkway Alameda, CA, 94502 USA
Jacob Heitz-Lucent Technologies美国加利福尼亚州阿拉米达港湾公园路1701号，邮编94502
Phone: +1-510-747-2917
EMail: jheitz@lucent.com
Phone: +1-510-747-2917
EMail: jheitz@lucent.com
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编辑功能的资金目前由互联网协会提供。