Network Working Group J. Loughney, Ed.
Request for Comments: 3868 Nokia
Category: Standards Track G. Sidebottom
Signatus Technologies
L. Coene
G. Verwimp
Siemens n.v.
J. Keller
Tekelec
B. Bidulock
OpenSS7 Corporation
October 2004
Network Working Group J. Loughney, Ed.
Request for Comments: 3868 Nokia
Category: Standards Track G. Sidebottom
Signatus Technologies
L. Coene
G. Verwimp
Siemens n.v.
J. Keller
Tekelec
B. Bidulock
OpenSS7 Corporation
October 2004
Signalling Connection Control Part User Adaptation Layer (SUA)
信令连接控制部分用户适配层（SUA）
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 (2004).
版权所有（C）互联网协会（2004年）。
Abstract
摘要
This document defines a protocol for the transport of any Signalling Connection Control Part-User signalling over IP using the Stream Control Transmission Protocol. The protocol is designed to be modular and symmetric, to allow it to work in diverse architectures, such as a Signalling Gateway to IP Signalling Endpoint architecture as well as a peer-to-peer IP Signalling Endpoint architecture.
本文件定义了使用流控制传输协议通过IP传输任何信令连接控制部分用户信令的协议。该协议被设计为模块化和对称的，以允许它在不同的体系结构中工作，例如信令网关到IP信令端点体系结构以及对等IP信令端点体系结构。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Scope. . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2. Abbreviations and Terminology. . . . . . . . . . . . . . 4
1.3. Signalling Transport Architecture. . . . . . . . . . . . 6
1.4. Services Provided by the SUA Layer . . . . . . . . . . . 9
1.5. Internal Functions Provided in the SUA Layer . . . . . . 11
1.6. Definition of SUA Boundaries . . . . . . . . . . . . . . 14
2. Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . 19
3. Protocol Elements. . . . . . . . . . . . . . . . . . . . . . . 19
3.1. Common Message Header. . . . . . . . . . . . . . . . . . 20
3.2. SUA Connectionless Messages. . . . . . . . . . . . . . . 24
3.3. Connection Oriented Messages . . . . . . . . . . . . . . 27
3.4. Signalling Network Management (SNM) Messages . . . . . . 42
3.5. Application Server Process State Maintenance Messages. . 49
3.6. ASP Traffic Maintenance Messages . . . . . . . . . . . . 53
3.7. SUA Management Messages. . . . . . . . . . . . . . . . . 56
3.8. Routing Key Management (RKM) Messages. . . . . . . . . . 58
3.9. Common Parameters. . . . . . . . . . . . . . . . . . . . 61
3.10. SUA-Specific parameters. . . . . . . . . . . . . . . . . 74
4. Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . 92
4.1. Procedures to Support the SUA-User Layer . . . . . . . . 92
4.2. Receipt of Primitives from the Layer Management. . . . . 93
4.3. AS and ASP State Maintenance . . . . . . . . . . . . . . 95
4.4. Routing Key Management Procedures. . . . . . . . . . . .109
4.5. Availability and/or Congestion Status of SS7
Destination Support101 . . . . . . . . . . . . . . . . .112
4.6. MTP3 Restart . . . . . . . . . . . . . . . . . . . . . .115
4.7. SCCP - SUA Interworking at the SG. . . . . . . . . . . .115
5. Examples of SUA Procedures . . . . . . . . . . . . . . . . . .117
5.1. SG Architecture. . . . . . . . . . . . . . . . . . . . .117
5.2 IPSP Examples. . . . . . . . . . . . . . . . . . . . . .119
6. Security Considerations. . . . . . . . . . . . . . . . . . . .121
7. IANA Considerations. . . . . . . . . . . . . . . . . . . . . .121
7.1. SCTP Payload Protocol ID . . . . . . . . . . . . . . . .121
7.2. Port Number. . . . . . . . . . . . . . . . . . . . . . .121
7.3. Protocol Extensions. . . . . . . . . . . . . . . . . . .121
8. Timer Values . . . . . . . . . . . . . . . . . . . . . . . . .123
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . .123
10. References . . . . . . . . . . . . . . . . . . . . . . . . . .123
10.1. Normative References . . . . . . . . . . . . . . . . . .123
10.2. Informative References . . . . . . . . . . . . . . . . .124
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Scope. . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2. Abbreviations and Terminology. . . . . . . . . . . . . . 4
1.3. Signalling Transport Architecture. . . . . . . . . . . . 6
1.4. Services Provided by the SUA Layer . . . . . . . . . . . 9
1.5. Internal Functions Provided in the SUA Layer . . . . . . 11
1.6. Definition of SUA Boundaries . . . . . . . . . . . . . . 14
2. Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . 19
3. Protocol Elements. . . . . . . . . . . . . . . . . . . . . . . 19
3.1. Common Message Header. . . . . . . . . . . . . . . . . . 20
3.2. SUA Connectionless Messages. . . . . . . . . . . . . . . 24
3.3. Connection Oriented Messages . . . . . . . . . . . . . . 27
3.4. Signalling Network Management (SNM) Messages . . . . . . 42
3.5. Application Server Process State Maintenance Messages. . 49
3.6. ASP Traffic Maintenance Messages . . . . . . . . . . . . 53
3.7. SUA Management Messages. . . . . . . . . . . . . . . . . 56
3.8. Routing Key Management (RKM) Messages. . . . . . . . . . 58
3.9. Common Parameters. . . . . . . . . . . . . . . . . . . . 61
3.10. SUA-Specific parameters. . . . . . . . . . . . . . . . . 74
4. Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . 92
4.1. Procedures to Support the SUA-User Layer . . . . . . . . 92
4.2. Receipt of Primitives from the Layer Management. . . . . 93
4.3. AS and ASP State Maintenance . . . . . . . . . . . . . . 95
4.4. Routing Key Management Procedures. . . . . . . . . . . .109
4.5. Availability and/or Congestion Status of SS7
Destination Support101 . . . . . . . . . . . . . . . . .112
4.6. MTP3 Restart . . . . . . . . . . . . . . . . . . . . . .115
4.7. SCCP - SUA Interworking at the SG. . . . . . . . . . . .115
5. Examples of SUA Procedures . . . . . . . . . . . . . . . . . .117
5.1. SG Architecture. . . . . . . . . . . . . . . . . . . . .117
5.2 IPSP Examples. . . . . . . . . . . . . . . . . . . . . .119
6. Security Considerations. . . . . . . . . . . . . . . . . . . .121
7. IANA Considerations. . . . . . . . . . . . . . . . . . . . . .121
7.1. SCTP Payload Protocol ID . . . . . . . . . . . . . . . .121
7.2. Port Number. . . . . . . . . . . . . . . . . . . . . . .121
7.3. Protocol Extensions. . . . . . . . . . . . . . . . . . .121
8. Timer Values . . . . . . . . . . . . . . . . . . . . . . . . .123
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . .123
10. References . . . . . . . . . . . . . . . . . . . . . . . . . .123
10.1. Normative References . . . . . . . . . . . . . . . . . .123
10.2. Informative References . . . . . . . . . . . . . . . . .124
Appendix A. Signalling Network Architecture . . . . . . . . . . .125
A.1. Generalized Peer-to-Peer Network Architecture. . . . . .125
A.2. Signalling Gateway Network Architecture. . . . . . . . .126
A.3. Signalling Gateway Message Distribution
Recommendations. . . . . . . . . . . . . . . . . . . . .128
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . .129
Full Copyright Statement . . . . . . . . . . . . . . . . . . . . .131
Appendix A. Signalling Network Architecture . . . . . . . . . . .125
A.1. Generalized Peer-to-Peer Network Architecture. . . . . .125
A.2. Signalling Gateway Network Architecture. . . . . . . . .126
A.3. Signalling Gateway Message Distribution
Recommendations. . . . . . . . . . . . . . . . . . . . .128
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . .129
Full Copyright Statement . . . . . . . . . . . . . . . . . . . . .131
There is ongoing integration of switched circuit networks and IP networks. Network service providers are designing IP-based signalling architectures that need support for SS7 and SS7-like signalling protocols. IP provides an effective way to transport user data and for operators to expand their networks and build new services. In these networks, there is need for interworking between the SS7 and IP domains [2719].
交换电路网络和IP网络正在进行集成。网络服务提供商正在设计基于IP的信令架构，这些架构需要支持SS7和类似SS7的信令协议。IP为传输用户数据和运营商扩展网络和构建新服务提供了一种有效的方式。在这些网络中，SS7和IP域之间需要互通[2719]。
This document defines a protocol for the transport SS7 SCCP-User protocols [ANSI SCCP] [ITU SCCP], such as TCAP and RANAP, over IP using the Stream Control Transmission Protocol (SCTP) [2960].
本文件定义了使用流控制传输协议（SCTP）[2960]通过IP传输SS7 SCCP用户协议[ANSI SCCP][ITU SCCP]的协议，如TCAP和RANAP。
This document details the delivery of SCCP-user messages (MAP & CAP over TCAP [ANSI TCAP] [ITU TCAP], RANAP [RANAP], etc.) messages over IP between two signalling endpoints. Consideration is given for the transport from a signalling gateway to an IP signalling node (such as an IP-resident Database) as described in the Framework Architecture for Signalling Transport [2719]. This protocol can also support transport of SCCP-user messages between two endpoints wholly contained within an IP network.
本文档详细介绍了通过IP在两个信令端点之间传递SCCP用户消息（TCAP[ANSI TCAP][ITU TCAP]、RANAP[RANAP]等上的MAP和CAP）消息。如信令传输框架架构[2719]所述，考虑从信令网关到IP信令节点（如IP驻留数据库）的传输。该协议还可以支持在完全包含在IP网络中的两个端点之间传输SCCP用户消息。
The delivery mechanism addresses the following criteria:
交付机制满足以下标准：
* Support for transfer of SCCP-User Part messages * Support for SCCP connectionless service. * Support for SCCP connection oriented service. * Support for the operation of SCCP-User protocol peers. * Support for the management of SCTP transport associations between signalling gateways and IP-based signalling nodes. * Support for distributed IP-based signalling nodes. * Support for the asynchronous reporting of status changes to management functions.
* 支持传输SCCP用户部件消息*支持SCCP无连接服务。*支持面向SCCP连接的服务。*支持SCCP用户协议对等方的操作。*支持信令网关和基于IP的信令节点之间SCTP传输关联的管理。*支持基于IP的分布式信令节点。*支持向管理功能异步报告状态更改。
CAP - CAMEL Application Protocol.
CAP-CAMEL应用协议。
GTT - Global Title Translation.
全球标题翻译。
MAP - Mobile Application Protocol.
地图-移动应用程序协议。
PC - Signalling System no. 7 Point Code.
PC-信号系统7号点代码。
RANAP - Radio Access Network Application Protocol.
无线接入网应用协议。
SCTP - Stream Control Transmission Protocol.
流控制传输协议。
SS7 - Signalling System no. 7.
SS7-7号信号系统。
TCAP - Transaction Capabilities Application Protocol.
TCAP-事务处理能力应用程序协议。
Signalling Gateway (SG) - Network element that terminates switched circuit networks and transports SCCP-User signalling over IP to an IP signalling endpoint. A Signalling Gateway could be modeled as one or more Signalling Gateway Processes, which are located at the border of the SS7 and IP networks. Where an SG contains more than one SGP, the SG is a logical entity and the contained SGPs are assumed to be coordinated into a single management view to the SS7 network and to the supported Application Servers.
信令网关（SG）-终止交换电路网络并通过IP将SCCP用户信令传输至IP信令端点的网元。信令网关可以建模为一个或多个信令网关进程，它们位于SS7和IP网络的边界。如果一个SG包含多个SGP，则SG是一个逻辑实体，并且所包含的SGP被假定为协调到SS7网络和支持的应用服务器的单个管理视图中。
Application Server (AS) - A logical entity serving a specific Routing Key. An example of an Application Server is a virtual IP database element handling all requests for an SCCP-user. The AS contains a set of one or more unique Application Server Processes, of which one or more is normally actively processing traffic.
应用服务器（AS）-为特定路由密钥提供服务的逻辑实体。应用服务器的一个示例是虚拟IP数据库元素，它处理SCCP用户的所有请求。AS包含一组一个或多个唯一的应用程序服务器进程，其中一个或多个进程通常正在积极处理流量。
Application Server Process (ASP) - An Application Server Process serves as an active or backup process of an Application Server (e.g., part of a distributed signalling node or database element). Examples of ASPs are MGCs, IP SCPs, or IP-based HLRs. An ASP contains an SCTP endpoint and may be configured to process traffic within more than one Application Server.
应用服务器进程（ASP）-应用服务器进程用作应用服务器的活动或备份进程（例如，分布式信令节点或数据库元素的一部分）。ASP的示例包括MGC、IP SCP或基于IP的HLR。ASP包含一个SCTP端点，可以配置为在多个应用服务器中处理流量。
IP Server Process (IPSP) - A process instance of an IP-based application. An IPSP is essentially the same as an ASP, except that it uses SUA in a peer-to-peer fashion. Conceptually, an IPSP does not use the services of a Signalling Gateway.
IP服务器进程（IPSP）-基于IP的应用程序的进程实例。IPSP本质上与ASP相同，只是它以点对点的方式使用SUA。从概念上讲，IPSP不使用信令网关的服务。
Signalling Gateway Process (SGP) - A process instance of a Signalling Gateway. It serves as an active, load-sharing or broadcast process of a Signalling Gateway.
信令网关进程（SGP）-信令网关的进程实例。它充当信令网关的主动、负载共享或广播过程。
Signalling Process - A process instance that uses SUA to communicate with other signalling process. An ASP, a SGP and an IPSP are all signalling processes.
信令进程-使用SUA与其他信令进程通信的进程实例。ASP、SGP和IPSP都是信令过程。
Association - An association refers to an SCTP association. The association provides the transport for the delivery of SCCP-User protocol data units and SUA layer peer messages.
关联-关联是指SCTP关联。该关联为SCCP用户协议数据单元和SUA层对等消息的传递提供传输。
Routing Key - The Routing Key describes a set of SS7 parameters and/or parameter ranges that uniquely defines the range of signalling traffic configured to be handled by a particular Application Server. An example would be where a Routing Key consists of a particular SS7 SCCP SSN plus an identifier to uniquely mark the network that the SSN belongs to, for which all traffic would be directed to a particular Application Server. Routing Keys are mutually exclusive in the sense that a received SS7 signalling message cannot be directed to more than one Routing Key. Routing Keys can be provisioned, for example, by a MIB or registered using SUA's dynamic registration procedures. Routing keys MUST NOT span multiple network appearances.
路由密钥-路由密钥描述了一组SS7参数和/或参数范围，这些参数和/或参数范围唯一地定义了配置为由特定应用服务器处理的信令通信量的范围。例如，路由密钥由特定的SS7 SCCP SSN加上唯一标记SSN所属网络的标识符组成，对于该SSN，所有流量都将定向到特定的应用服务器。在接收到的SS7信令消息不能定向到多个路由密钥的意义上，路由密钥是互斥的。例如，可以通过MIB提供路由密钥，或者使用SUA的动态注册过程进行注册。路由密钥不得跨越多个网络外观。
Routing Context - An Application Server Process may be configured to process traffic within more than one Application Server. In this case, the Routing Context parameter is exchanged between the SGP and the ASP (or between two ASPs), identifying the relevant Application Server. From the perspective of an SGP/ASP, the Routing Context uniquely identifies the range of traffic associated with a particular Application Server, which the ASP is configured to receive. There is a 1:1 relationship between a Routing Context value and a Routing Key within an AS. Therefore the Routing Context can be viewed as an index into an AS Table containing the AS Routing Keys.
路由上下文-可以将应用程序服务器进程配置为处理多个应用程序服务器内的流量。在这种情况下，路由上下文参数在SGP和ASP（或两个ASP）之间交换，以标识相关的应用程序服务器。从SGP/ASP的角度来看，路由上下文唯一地标识与特定应用程序服务器相关联的流量范围，ASP配置为接收该范围。AS中的路由上下文值和路由键之间存在1:1的关系。因此，可以将路由上下文视为包含as路由键的as表的索引。
Address Mapping Function (AMF) - The AMF is an implementation dependent function that is responsible for resolving the address presented in the incoming SCCP/SUA message to correct SCTP association for the desired endpoint. The AMF MAY use routing context / routing key information as selection criteria for the appropriate SCTP association.
地址映射函数（AMF）-AMF是一个依赖于实现的函数，负责解析传入SCCP/SUA消息中显示的地址，以更正所需端点的SCTP关联。AMF可以使用路由上下文/路由密钥信息作为适当SCTP关联的选择标准。
Fail-over - The capability to reroute signalling traffic as required to an alternate Application Server Process, or group of ASPs, within an Application Server in the event of failure or unavailability of a currently used Application Server Process. Fail-over may apply upon the return to service of a previously unavailable Application Server Process.
故障转移—在当前使用的应用程序服务器进程出现故障或不可用时，根据需要将信令流量重新路由到应用程序服务器内的备用应用程序服务器进程或一组ASP的能力。故障转移可在以前不可用的应用程序服务器进程恢复服务时应用。
Host - The computing platform that the SGP or ASP process is running on.
主机-运行SGP或ASP进程的计算平台。
Layer Management - Layer Management is a nodal function that handles the inputs and outputs between the SUA layer and a local management entity.
层管理-层管理是处理SUA层和本地管理实体之间的输入和输出的节点功能。
Network Appearance - The Network Appearance is an SUA local reference (typically an integer) shared by SG and AS that together with a Signalling Point Code uniquely identifies an SS7 node by indicating the specific SS7 network it belongs to.
网络外观-网络外观是由SG共享的SUA本地参考（通常为整数），与信令点代码一起，通过指示其所属的特定SS7网络来唯一标识SS7节点。
Network Byte Order - Most significant byte first, a.k.a. Big Endian.
网络字节顺序-最高有效字节优先，也称为大端字节。
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 sequenced except for those submitted to the unordered delivery service.
流-流指SCTP流；从一个SCTP端点到另一个相关SCTP端点建立的单向逻辑通道，在该通道内，除提交给无序传递服务的用户消息外，所有用户消息都按顺序传递。
Transport address - an address that serves as a source or destination for the unreliable packet transport service used by SCTP. In IP networks, a transport address is defined by the combination of an IP address and an SCTP port number. Note, only one SCTP port may be defined for each endpoint, but each SCTP endpoint may have multiple IP addresses.
传输地址-用作SCTP使用的不可靠数据包传输服务的源或目的地的地址。在IP网络中，传输地址由IP地址和SCTP端口号的组合定义。注意，每个端点只能定义一个SCTP端口，但每个SCTP端点可能有多个IP地址。
The framework architecture that has been defined for switched circuit networks signalling transport over IP [2719] uses multiple components, including an IP transport protocol, a signalling common transport protocol and an adaptation module to support the services expected by a particular switched circuit networks signalling protocol from its underlying protocol layer.
为交换电路网络定义的框架架构（IP传输信令）[2719]使用多个组件，包括IP传输协议，一种信令通用传输协议和适配模块，用于支持特定交换电路网络信令协议从其底层协议层期望的服务。
In general terms, the SUA architecture can be modeled as a peer-to-peer architecture. The first section considers the SS7 to IP interworking architectures for connectionless and connection-oriented transport. For this case, it is assumed that the ASP initiates the establishment of the SCTP association with SG.
一般来说，SUA体系结构可以建模为对等体系结构。第一部分考虑用于无连接和面向连接传输的SS7到IP互通体系结构。在这种情况下，假设ASP启动了与SG的SCTP关联的建立。
In this architecture, the SCCP and SUA layers interface in the SG. Interworking between the SCCP and SUA layers is needed to provide for the transfer of the user messages as well as the management messages.
在此体系结构中，SCCP和SUA层在SG中接口。SCCP和SUA层之间需要互通，以提供用户消息和管理消息的传输。
******** SS7 *************** IP ********
* SEP *---------* *--------* *
* or * * SG * * ASP *
* STP * * * * *
******** *************** ********
******** SS7 *************** IP ********
* SEP *---------* *--------* *
* or * * SG * * ASP *
* STP * * * * *
******** *************** ********
+------+ +------+
| SUAP | | SUAP |
+------+ +------+------+ +------+
| SCCP | | SCCP | SUA | | SUA |
+------+ +------+------+ +------+
| MTP3 | | MTP3 | | | |
+------+ +------+ SCTP | | SCTP |
| MTP2 | | MTP2 | | | |
+------+ +------+------+ +------+
| L1 | | L1 | IP | | IP |
+------+ +------+------+ +------+
| | | |
+---------------+ +------------+
+------+ +------+
| SUAP | | SUAP |
+------+ +------+------+ +------+
| SCCP | | SCCP | SUA | | SUA |
+------+ +------+------+ +------+
| MTP3 | | MTP3 | | | |
+------+ +------+ SCTP | | SCTP |
| MTP2 | | MTP2 | | | |
+------+ +------+------+ +------+
| L1 | | L1 | IP | | IP |
+------+ +------+------+ +------+
| | | |
+---------------+ +------------+
SUAP - SCCP/SUA User Protocol (TCAP, for example) STP - SS7 Signalling Transfer Point
SUAP-SCCP/SUA用户协议（例如TCAP）STP-SS7信令传输点
See Appendix A.3.1 for operation recommendations.
操作建议见附录A.3.1。
In this case, the connectionless SCCP messages are routed on point code (PC) and subsystem number (SSN). The subsystem identified by SSN and Routing Context is regarded as local to the SG. This means from SS7 point of view, the SCCP-user is located at the SG.
在这种情况下，无连接SCCP消息通过点代码（PC）和子系统编号（SSN）进行路由。由SSN和路由上下文标识的子系统被视为SG的本地子系统。这意味着从SS7的角度来看，SCCP用户位于SG。
A Global Title translation is executed at the signalling gateway, before the destination of the message can be determined. The actual location of the SCCP-user is irrelevant to the SS7 network. GT Translation yields an "SCCP entity set", from which an Application Server can be derived. Selection of the Application Server is based on the SCCP called party address (and possibly other SS7 parameters depending on the implementation).
在确定消息的目的地之前，在信令网关处执行全局标题转换。SCCP用户的实际位置与SS7网络无关。GT转换生成一个“SCCP实体集”，可以从中派生应用程序服务器。应用服务器的选择基于SCCP被叫方地址（以及可能的其他SS7参数，具体取决于实现）。
In this architecture, the SCCP and SUA layers share an interface in the signalling gateway process to associate the two connection sections needed for the connection-oriented data transfer between SEP and ASP. Both connection sections are setup when routing the Connect Request messages from the signalling end point via signalling gateway process to ASP and visa versa. The routing of the Connect Request message is performed in the same way as described in 1.3.1.
在此体系结构中，SCCP和SUA层在信令网关过程中共享一个接口，以关联SEP和ASP之间面向连接的数据传输所需的两个连接部分。当通过信令网关进程将连接请求消息从信令端点路由到ASP时，将设置两个连接部分，反之亦然。连接请求消息的路由按照1.3.1中所述的相同方式执行。
******** SS7 *************** IP ********
* SEP/ *---------* SG *--------* ASP *
* STP * * * * *
******** *************** ********
******** SS7 *************** IP ********
* SEP/ *---------* SG *--------* ASP *
* STP * * * * *
******** *************** ********
+------+ +------+
| SUAP | | SUAP |
+------+ +------+------+ +------+
| SCCP | | SCCP | SUA | | SUA |
+------+ +------+------+ +------+
| MTP3 | | MTP3 | | | |
+------| +------+ SCTP | | SCTP |
| MTP2 | | MTP2 | | | |
+------+ +------+------+ +------+
| L1 | | L1 | IP | | IP |
+------+ +------+------+ +------+
| | | |
+---------------+ +------------+
+------+ +------+
| SUAP | | SUAP |
+------+ +------+------+ +------+
| SCCP | | SCCP | SUA | | SUA |
+------+ +------+------+ +------+
| MTP3 | | MTP3 | | | |
+------| +------+ SCTP | | SCTP |
| MTP2 | | MTP2 | | | |
+------+ +------+------+ +------+
| L1 | | L1 | IP | | IP |
+------+ +------+------+ +------+
| | | |
+---------------+ +------------+
SUAP - SCCP/SUA Application Protocol (e.g., - RANAP/RNSAP)
STP - SS7 Signalling Transfer Point
SUAP - SCCP/SUA Application Protocol (e.g., - RANAP/RNSAP)
STP - SS7 Signalling Transfer Point
See Appendix A.3.2 for operation recommendations.
操作建议见附录A.3.2。
This architecture can be used to carry a protocol that uses the transport services of SCCP within an IP network. This allows flexibility in developing networks, especially when interaction between legacy signalling is not needed. The architecture removes the need for signalling gateway functionality.
该体系结构可用于承载在IP网络中使用SCCP传输服务的协议。这允许在开发网络时具有灵活性，特别是在不需要传统信令之间的交互时。该体系结构消除了对信令网关功能的需要。
******** IP ********
* IPSP *--------* IPSP *
******** ********
******** IP ********
* IPSP *--------* IPSP *
******** ********
+------+ +------+
| SUAP | | SUAP |
+------+ +------+
| SUA | | SUA |
+------+ +------+
| SCTP | | SCTP |
+------+ +------+
| IP | | IP |
+------+ +------+
| |
+----------------+
+------+ +------+
| SUAP | | SUAP |
+------+ +------+
| SUA | | SUA |
+------+ +------+
| SCTP | | SCTP |
+------+ +------+
| IP | | IP |
+------+ +------+
| |
+----------------+
SUAP - SCCP/SUA Application Protocol (e.g., - RANAP/RNSAP)
SUAP - SCCP/SUA Application Protocol (e.g., - RANAP/RNSAP)
The SUA protocol supports ASP fail-over functions to support a high availability of transaction processing capability.
SUA协议支持ASP故障转移功能，以支持事务处理能力的高可用性。
An Application Server can be considered as a list of all ASPs configured/registered to handle SCCP-user messages within a certain range of routing information, known as a Routing Key. One or more ASPs in the list may normally be active to handle traffic, while others may be inactive but available in the event of failure or unavailability of the active ASP(s).
可以将应用程序服务器视为所有配置/注册的ASP的列表，以处理特定路由信息范围（称为路由密钥）内的SCCP用户消息。列表中的一个或多个ASP通常处于活动状态以处理流量，而其他ASP可能处于非活动状态，但在活动ASP出现故障或不可用时可用。
For operation recommendations, see Appendix A.
有关操作建议，请参见附录A。
The SUA supports the transfer of SCCP-user messages. The SUA layer at the signalling gateway and at the ASP support the seamless transport of user messages between the signalling gateway and the ASP.
SUA支持SCCP用户消息的传输。信令网关和ASP的SUA层支持在信令网关和ASP之间无缝传输用户消息。
Depending upon the SCCP-users supported, the SUA supports the 4 possible SCCP protocol classes transparently. The SCCP protocol classes are defined as follows:
根据支持的SCCP用户，SUA透明地支持4种可能的SCCP协议类。SCCP协议类别定义如下：
* Protocol class 0 provides unordered transfer of SCCP-user messages in a connectionless manner.
* 协议类0以无连接的方式提供SCCP用户消息的无序传输。
* Protocol class 1 allows the SCCP-user to select the sequenced delivery of SCCP-user messages in a connectionless manner.
* 协议类别1允许SCCP用户以无连接方式选择SCCP用户消息的顺序传递。
* Protocol class 2 allows the bidirectional transfer of SCCP-user messages by setting up a temporary or permanent signalling connection.
* 协议类别2允许通过建立临时或永久信令连接来双向传输SCCP用户消息。
* Protocol class 3 allows the features of protocol class 2 with the inclusion of flow control. Detection of message loss or mis-sequencing is included.
* 协议类3允许协议类2的功能，包括流量控制。包括对消息丢失或错误排序的检测。
Protocol classes 0 and 1 make up the SCCP connectionless service. Protocol classes 2 and 3 make up the SCCP connection-oriented service.
协议类0和1构成SCCP无连接服务。协议类2和3构成了面向SCCP连接的服务。
The SUA layer provides the capability to indicate errors associated with the SUA-protocol messages and to provide notification to local management and the remote peer as is necessary.
SUA层提供指示与SUA协议消息相关的错误的能力，并在必要时向本地管理层和远程对等方提供通知。
SUA uses the existing ASP management messages for ASP status handling. The interworking with SCCP management messages consists of DUNA, DAVA, DAUD, DRST, DUPU or SCON messages (defined in section 3) on receipt of SSP, SSA, SST or SSC (defined by SCCP) to the appropriate ASPs. See also chapter 1.4.5. The primitives below are sent between the SCCP and SUA management functions in the SG to trigger events in the IP and SS7 domain.
SUA使用现有的ASP管理消息来处理ASP状态。收到SSP、SSA、SST或SSC（由SCCP定义）后，与SCCP管理信息的互通包括DUNA、DAVA、DAUD、DRST、DUPU或SCON信息（定义见第3节）。另见第1.4.5章。以下原语在SG中的SCCP和SUA管理功能之间发送，以触发IP和SS7域中的事件。
Generic |Specific |
Name |Name |ANSI/ITU Reference
----------+-----------+---------------------------------------------
N-State |Request |ITU-Q.711 Chap 6.3.2.3.2 (Tab 16/Q.711)
|Indication |ANSI-T1.112 Chap 2.3.2.3.2 (Tab 8E/T1.112.1)
----------+-----------+---------------------------------------------
N-PCstate |Indication |ITU-Q.711 Chap 6.3.2.3.3 (Tab 1/Q.711)
| |ANSI-T1.112 Chap 2.3.2.3.4 (Tab 8G/T1.112.1)
----------+-----------+---------------------------------------------
N-Coord |Request |ITU-Q.711 Chap 6.3.2.3.1 (Tab 15/Q.711)
|Indication |ANSI-T1.112 Chap 2.3.2.3.3 (Tab 8F/T1.112.1)
|Response |
|Confirm |
Generic |Specific |
Name |Name |ANSI/ITU Reference
----------+-----------+---------------------------------------------
N-State |Request |ITU-Q.711 Chap 6.3.2.3.2 (Tab 16/Q.711)
|Indication |ANSI-T1.112 Chap 2.3.2.3.2 (Tab 8E/T1.112.1)
----------+-----------+---------------------------------------------
N-PCstate |Indication |ITU-Q.711 Chap 6.3.2.3.3 (Tab 1/Q.711)
| |ANSI-T1.112 Chap 2.3.2.3.4 (Tab 8G/T1.112.1)
----------+-----------+---------------------------------------------
N-Coord |Request |ITU-Q.711 Chap 6.3.2.3.1 (Tab 15/Q.711)
|Indication |ANSI-T1.112 Chap 2.3.2.3.3 (Tab 8F/T1.112.1)
|Response |
|Confirm |
1.4.5. Support for the management between the SGP and ASP.
1.4.5. 支持SGP和ASP之间的管理。
The SUA layer provides interworking with SCCP management functions at the SG for operation between the switched circuit networks and the IP network. It should:
SUA层在SG处提供与SCCP管理功能的互通，以便在交换电路网络和IP网络之间进行操作。它应当：
* Provide an indication to the SCCP-user at an ASP that a SS7 endpoint/peer is unreachable. * Provide an indication to the SCCP-user at an ASP that a SS7 endpoint/peer is reachable. * Provide congestion indication to SCCP-user at an ASP. * Provide the initiation of an audit of SS7 endpoints at the SG.
* 向ASP上的SCCP用户提供无法访问SS7端点/对等点的指示。*向ASP上的SCCP用户提供SS7端点/对等点可访问的指示。*在ASP向SCCP用户提供拥塞指示。*在SG处提供SS7端点审计的启动。
For network scalability purposes, the SUA may be enhanced with a relay functionality to determine the next hop SCTP association toward the destination SUA endpoint.
出于网络可伸缩性目的，可以使用中继功能来增强SUA，以确定朝向目的地SUA端点的下一跳SCTP关联。
The determination of the next hop may be based on Global Title information (e.g., E.164 number), in analogy with SCCP GTT in SS7 networks, modeled in [ITU-T Q.714]. It may also be based on Hostname information, IP address or pointcode contained in the called party address.
下一跳的确定可基于全局标题信息（例如，164号），类似于[ITU-T Q.714]中建模的SS7网络中的SCCP GTT。它也可能基于主机名信息、IP地址或被叫方地址中包含的点代码。
This allows for greater scalability, reliability and flexibility in wide-scale deployments of SUA. The usage of a relay function is a deployment decision.
这使得SUA的大规模部署具有更大的可扩展性、可靠性和灵活性。中继功能的使用是一项部署决策。
To perform its addressing and relaying capabilities, the SUA makes use of an Address Mapping Function (AMF). This function is considered part of SUA, but the way it is realized is left implementation / deployment dependent (local tables, DNS [3761], LDAP, etc.)
为了执行寻址和中继功能，SUA使用地址映射功能（AMF）。此功能被视为SUA的一部分，但其实现方式取决于实现/部署（本地表、DNS[3761]、LDAP等）
The AMF is invoked when a message is received at the incoming interface. The AMF is responsible for resolving the address presented in the incoming SCCP/SUA message to SCTP associations to destinations within the IP network. The AMF will select the appropriate SCTP association based upon routing context / routing key information available. The destination might be the end SUA node or a SUA relay node. The Routing Keys reference an Application Server, which will have one or more ASPs processing traffic for the AS. The availability and status of the ASPs is handled by SUA ASP management messages.
当传入接口接收到消息时，将调用AMF。AMF负责将传入SCCP/SUA消息中显示的地址解析为IP网络中的SCTP关联目的地。AMF将根据可用的路由上下文/路由密钥信息选择适当的SCTP关联。目标可能是终端SUA节点或SUA中继节点。路由密钥引用一个应用服务器，该应用服务器将有一个或多个ASP处理AS的流量。ASP的可用性和状态由SUA ASP管理消息处理。
Possible SS7 address/routing information that comprise a Routing Key entry includes, for example, OPC, DPC, SIO found in the MTP3 routing label, SCCP subsystem number, or Transaction ID. IP addresses and hostnames can also be used as Routing Key Information.
可能包含路由密钥条目的SS7地址/路由信息包括，例如，MTP3路由标签中的OPC、DPC、SIO、SCCP子系统号或事务ID。IP地址和主机名也可用作路由密钥信息。
It is expected that the routing keys be provisioned via a MIB, dynamic registration or external process, such as a database.
期望通过MIB、动态注册或外部进程（如数据库）提供路由密钥。
Normally, one or more ASPs are active in the AS (i.e., currently processing traffic) but in certain failure and transition cases it is possible that there may not be an active ASP available. The SGP will buffer the message destined for this AS for a time T(r) or until an ASP becomes available. When no ASP becomes available before expiry of T(r), the SGP will flush the buffered messages and initiate the appropriate return or refusal procedures.
通常，一个或多个ASP在AS中处于活动状态（即，当前正在处理流量），但在某些故障和转换情况下，可能没有可用的活动ASP。SGP将在时间T（r）内或直到ASP可用时缓冲发送给此目的地的消息。当在T（r）到期之前没有ASP可用时，SGP将刷新缓冲消息并启动适当的返回或拒绝程序。
If there is no address mapping match for an incoming message, a default treatment MAY be specified. Possible solutions are to provide a default Application Server to direct all unallocated traffic to a (set of) default ASP(s), or to drop the messages and provide a notification to management. The treatment of unallocated traffic is implementation dependent.
如果传入消息没有地址映射匹配，则可以指定默认处理方式。可能的解决方案是提供一个默认应用程序服务器，将所有未分配的流量定向到（一组）默认ASP，或者删除消息并向管理层提供通知。未分配流量的处理取决于实现。
To direct messages to the SS7 network, the ASP MAY perform an address mapping to choose the proper SGP for a given message. This is accomplished by observing the Destination Point Code and other elements of the outgoing message, SS7 network status, SGP availability, and Routing Context configuration tables.
为了将消息定向到SS7网络，ASP可以执行地址映射，为给定消息选择适当的SGP。这是通过观察目标点代码和传出消息的其他元素、SS7网络状态、SGP可用性和路由上下文配置表来实现的。
A Signalling Gateway may be composed of one or more SGPs. There is, however, no SUA messaging to manage the status of an SGP. Whenever an SCTP association to an SGP exists, it is assumed to be available. Also, every SGP of one SG communicating with one ASP regarding one AS provides identical SS7 connectivity to this ASP.
信令网关可以由一个或多个sgp组成。但是，没有用于管理SGP状态的SUA消息。只要存在与SGP的SCTP关联，就假定该关联可用。此外，一个SG的每个SGP与一个ASP（关于一个AS）通信，提供与该ASP相同的SS7连接。
An ASP routes responses to the SGP that it received messages from; within the routing context which it is currently active and receiving traffic.
ASP将响应路由到它从中接收消息的SGP；在当前处于活动状态并接收流量的路由上下文中。
The relay function is invoked when:
继电器功能在以下情况下调用：
- Routing is on Global Title
- 路由在全局标题上
- Routing is on Hostname - Routing is on SSN and PC or SSN and IP Address and the address presented is not the one of the relay node
- 路由基于主机名-路由基于SSN和PC或SSN和IP地址，并且显示的地址不是中继节点的地址
Translation/resolution of the above address information yields one of the following:
翻译/解析上述地址信息会产生以下结果之一：
- Route on SSN: SCTP association ID toward the destination node, SSN and optionally Routing Context and/or IP address. - Route on GT: SCTP association ID toward next relay node, (new) GT and optionally SSN and/or Routing Context. - Routing on Hostname: SCTP association ID toward next relay node, (new) Hostname and optionally SSN and/or Routing Context. - A local SUA-user (combined relay/end node)
- SSN上的路由：指向目标节点、SSN和可选路由上下文和/或IP地址的SCTP关联ID。-在GT:SCTP关联ID上路由到下一个中继节点，（新）GT和可选的SSN和/或路由上下文。-主机名上的路由：指向下一个中继节点的SCTP关联ID，（新）主机名以及可选的SSN和/或路由上下文。-本地SUA用户（组合中继/终端节点）
To prevent looping, an SS7 hop counter is used. The originating end node (be it an SS7 or an IP node) sets the value of the SS7 hop counter to the maximum value (15 or less). Each time the relay function is invoked within an intermediate (relay) node, the SS7 hop counter is decremented. When the value reaches zero, the return or refusal procedures are invoked with reason "Hop counter violation".
为防止循环，使用SS7跳计数器。发起端节点（无论是SS7还是IP节点）将SS7跃点计数器的值设置为最大值（15或更小）。每次在中间（中继）节点内调用中继功能时，SS7跃点计数器将递减。当值达到零时，将调用返回或拒绝过程，原因是“跃点计数器冲突”。
The SUA supports SCTP streams. Signalling Gateway SG and Application Servers need to maintain a list of SCTP and SUA-users for mapping purposes. SCCP-users requiring sequenced message transfer need to be sent over a stream with sequenced delivery.
SUA支持SCTP流。信令网关SG和应用服务器需要维护SCTP和SUA用户的列表，以便进行映射。需要顺序消息传输的SCCP用户需要通过具有顺序传递的流发送。
SUA uses stream 0 for SUA management messages. It is OPTIONAL that sequenced delivery be used to preserve the order of management message delivery.
SUA将流0用于SUA管理消息。可以选择使用顺序传递来保留管理消息传递的顺序。
Stream selection based on protocol class:
基于协议类的流选择：
- Protocol class 0: SUA MAY select unordered delivery. The stream selected is based on traffic information available to the SGP or ASP.
- 协议类别0:SUA可以选择无序交付。选择的流基于SGP或ASP可用的流量信息。
- Protocol class 1: SUA MUST select ordered delivery. The stream selected is based upon the sequence parameter given by the upper layer over the primitive interface and other traffic information available to the SGP or ASP
- 协议类别1：SUA必须选择订单交付。选择的流基于上层在基本接口上给出的序列参数和SGP或ASP可用的其他流量信息
- Protocol classes 2 and 3: SUA MUST select ordered delivery. The stream selected is based upon the source local reference of the connection and other traffic information available to the SGP or ASP.
- 协议类别2和3：SUA必须选择订单交付。选择的流基于连接的源本地引用和SGP或ASP可用的其他流量信息。
Local Management at an ASP may wish to stop traffic across an SCTP association to temporarily remove the association from service or to perform testing and maintenance activity. The function could optionally be used to control the start of traffic on to a newly available SCTP association.
ASP的本地管理层可能希望停止通过SCTP关联的通信，以临时将该关联从服务中删除，或执行测试和维护活动。该功能可选择性地用于控制新可用SCTP关联上的流量开始。
The SUA layer is informed of local and IP network congestion by means of an implementation-dependent function (e.g., an implementation-dependent indication from the SCTP of IP network congestion).
通过依赖于实现的功能（例如，来自于SCTP的IP网络拥塞的依赖于实现的指示），向SUA层通知本地和IP网络拥塞。
At an ASP or IPSP, the SUA layer indicates congestion to local SCCP-Users by means of an appropriate SCCP primitive (e.g., N-INFORM, N-NOTICE), as per current SCCP procedures, to invoke appropriate upper layer responses. When an SG determines that the transport of SS7 messages is encountering congestion, the SG MAY trigger SS7 SCCP Congestion messages to originating SS7 nodes, per the congestion procedures of the relevant SCCP standard. The triggering of SS7 SCCP Management messages from an SG is an implementation-dependent function.
在ASP或IPSP中，根据当前SCCP程序，SUA层通过适当的SCCP原语（例如，N-INFORT、N-NOTINCE）向本地SCCP用户指示拥塞，以调用适当的上层响应。当SG确定SS7消息的传输遇到拥塞时，SG可以根据相关SCCP标准的拥塞过程，向发起SS7节点触发SS7 SCCP拥塞消息。从SG触发SS7 SCCP管理消息是一项依赖于实现的功能。
The SUA layer at an ASP or IPSP MAY indicate local congestion to an SUA peer with an SCON message. When an SG receives a congestion message (SCON) from an ASP, and the SG determines that an endpoint is now encountering congestion, it MAY trigger congestion procedures of the relevant SCCP standard.
ASP或IPSP上的SUA层可通过SCON消息向SUA对等方指示本地拥塞。当SG从ASP接收到拥塞消息（SCON），并且SG确定某个端点现在遇到拥塞时，它可能会触发相关SCCP标准的拥塞过程。
The following primitives are supported between the SUA and an SCCP-user (a reference to ITU and ANSI sections where these primitives and corresponding parameters are described, is also given):
SUA和SCCP用户之间支持以下原语（还提供了对ITU和ANSI章节的参考，其中描述了这些原语和相应参数）：
Generic |Specific |
Name |Name |ANSI/ITU Reference
------------+----------+-------------------------------------------
N-CONNECT |Request |ITU-Q.711 Chap 6.1.1.2.2 (Tab 2/Q.711)
|Indication|ANSI-T1.112 Chap 2.1.1.2.2 (Tab 2/T1.112.1)
|Response |
|Confirm |
------------+----------+-------------------------------------------
N-DATA |Request |ITU-Q.711 Chap 6.1.1.2.3 (Tab 3/Q.711)
|Indication|ANSI-T1.112 Chap 2.1.1.2.3 (Tab 3/T1.112.1)
Generic |Specific |
Name |Name |ANSI/ITU Reference
------------+----------+-------------------------------------------
N-CONNECT |Request |ITU-Q.711 Chap 6.1.1.2.2 (Tab 2/Q.711)
|Indication|ANSI-T1.112 Chap 2.1.1.2.2 (Tab 2/T1.112.1)
|Response |
|Confirm |
------------+----------+-------------------------------------------
N-DATA |Request |ITU-Q.711 Chap 6.1.1.2.3 (Tab 3/Q.711)
|Indication|ANSI-T1.112 Chap 2.1.1.2.3 (Tab 3/T1.112.1)
------------+----------+-------------------------------------------
N-EXPEDITED |Request |ITU-Q.711 Chap 6.1.1.2.3 (Tab 4/Q.711)
DATA |Indication|ANSI-T1.112 Chap 2.1.1.2.3 (Tab 4/T1.112.1)
------------+----------+-------------------------------------------
N-RESET |Request |ITU-Q.711 Chap 6.1.1.2.3 (Tab 5/Q.711)
|Indication|ANSI-T1.112 Chap 2.1.1.2.3 (Tab 5/T1.112.1)
|Response |
|Confirm |
------------+----------+-------------------------------------------
N-DISCONNECT|Request |ITU-Q.711 Chap 6.1.1.2.4 (Tab 6/Q.711)
|Indication|ANSI-T1.112 Chap 2.1.1.2.4 (Tab 6/T1.112.1)
------------+----------+-------------------------------------------
N-INFORM |Request |ITU-Q.711 Chap 6.1.1.3.2 (Tab 8/Q.711)
|Indication|ANSI-T1.112 Chap 2.1.1.2.5 (Tab 6A/T1.112.1)
------------+----------+-------------------------------------------
N-UNITDATA |Request |ITU-Q.711 Chap 6.2.2.3.1 (Tab 12/Q.711)
|Indication|ANSI-T1.112 Chap 2.2.2.3.1 (Tab 8A/T1.112.1)
------------+----------+-------------------------------------------
N-NOTICE |Indication|ITU-Q.711 Chap 6.2.2.3.2 (Tab 13/Q.711)
| |ANSI-T1.112 Chap 2.2.2.3.2 (Tab 8B/T1.112.1)
------------+----------+--------------------------------------------
N-STATE |Request |ITU-Q.711 Chap 6.3.2.3.2 (Tab 16/Q.711)
|Indication|ANSI-T1.112 Chap 2.3.2.3.2 (Tab 8E/T1.112.1)
------------+----------+--------------------------------------------
N-PCSTATE |Indication|ITU-Q.711 Chap 6.3.2.3.3 (Tab 17/Q.711)
| |ANSI-T1.112 Chap 2.3.2.3.4 (Tab 8G/T1.112.1)
------------+----------+--------------------------------------------
N-COORD |Request |ITU-Q.711 Chap 6.3.2.3.1 (Tab 15/Q.711)
|Indication|ANSI-T1.112 Chap 2.3.2.3.3 (Tab 8F/T1.112.1)
|Response |
|Confirm |
------------+----------+-------------------------------------------
N-EXPEDITED |Request |ITU-Q.711 Chap 6.1.1.2.3 (Tab 4/Q.711)
DATA |Indication|ANSI-T1.112 Chap 2.1.1.2.3 (Tab 4/T1.112.1)
------------+----------+-------------------------------------------
N-RESET |Request |ITU-Q.711 Chap 6.1.1.2.3 (Tab 5/Q.711)
|Indication|ANSI-T1.112 Chap 2.1.1.2.3 (Tab 5/T1.112.1)
|Response |
|Confirm |
------------+----------+-------------------------------------------
N-DISCONNECT|Request |ITU-Q.711 Chap 6.1.1.2.4 (Tab 6/Q.711)
|Indication|ANSI-T1.112 Chap 2.1.1.2.4 (Tab 6/T1.112.1)
------------+----------+-------------------------------------------
N-INFORM |Request |ITU-Q.711 Chap 6.1.1.3.2 (Tab 8/Q.711)
|Indication|ANSI-T1.112 Chap 2.1.1.2.5 (Tab 6A/T1.112.1)
------------+----------+-------------------------------------------
N-UNITDATA |Request |ITU-Q.711 Chap 6.2.2.3.1 (Tab 12/Q.711)
|Indication|ANSI-T1.112 Chap 2.2.2.3.1 (Tab 8A/T1.112.1)
------------+----------+-------------------------------------------
N-NOTICE |Indication|ITU-Q.711 Chap 6.2.2.3.2 (Tab 13/Q.711)
| |ANSI-T1.112 Chap 2.2.2.3.2 (Tab 8B/T1.112.1)
------------+----------+--------------------------------------------
N-STATE |Request |ITU-Q.711 Chap 6.3.2.3.2 (Tab 16/Q.711)
|Indication|ANSI-T1.112 Chap 2.3.2.3.2 (Tab 8E/T1.112.1)
------------+----------+--------------------------------------------
N-PCSTATE |Indication|ITU-Q.711 Chap 6.3.2.3.3 (Tab 17/Q.711)
| |ANSI-T1.112 Chap 2.3.2.3.4 (Tab 8G/T1.112.1)
------------+----------+--------------------------------------------
N-COORD |Request |ITU-Q.711 Chap 6.3.2.3.1 (Tab 15/Q.711)
|Indication|ANSI-T1.112 Chap 2.3.2.3.3 (Tab 8F/T1.112.1)
|Response |
|Confirm |
The upper layer primitives provided by the SCTP are provided in [SCTP].
SCTP提供的上层原语见[SCTP]。
M-SCTP_ESTABLISH request Direction: LM -> SUA Purpose: LM requests ASP to establish an SCTP association with its peer.
M-SCTP_建立请求方向：LM->SUA目的：LM请求ASP与其对等方建立SCTP关联。
M-SCTP_ESTABLISH confirm Direction: SUA -> LM Purpose: ASP confirms to LM that it has established an SCTP association with its peer.
M-SCTP_建立确认方向：SUA->LM目的：ASP向LM确认其已与其对等方建立SCTP关联。
M-SCTP_ESTABLISH indication Direction: SUA -> LM Purpose: SUA informs LM that a remote ASP has established an SCTP association.
M-SCTP_建立指示方向：SUA->LM目的：SUA通知LM远程ASP已建立SCTP关联。
M-SCTP_RELEASE request Direction: LM -> SUA Purpose: LM requests ASP to release an SCTP association with its peer.
M-SCTP_释放请求方向：LM->SUA目的：LM请求ASP释放与其对等方的SCTP关联。
M-SCTP_RELEASE confirm Direction: SUA -> LM Purpose: ASP confirms to LM that it has released SCTP association with its peer.
M-SCTP_发布确认方向：SUA->LM目的：ASP向LM确认其已发布与其对等方的SCTP关联。
M-SCTP_RELEASE indication Direction: SUA -> LM Purpose: SUA informs LM that a remote ASP has released an SCTP Association or the SCTP association has failed.
M-SCTP_释放指示方向：SUA->LM目的：SUA通知LM远程ASP已释放SCTP关联或SCTP关联已失败。
M-SCTP RESTART indication Direction: SUA -> LM Purpose: SUA informs LM that an SCTP restart indication has been received.
M-SCTP重启指示方向：SUA->LM目的：SUA通知LM已收到SCTP重启指示。
M-SCTP_STATUS request Direction: LM -> SUA Purpose: LM requests SUA to report the status of an SCTP association.
M-SCTP_状态请求方向：LM->SUA目的：LM请求SUA报告SCTP关联的状态。
M-SCTP_STATUS confirm Direction: SUA -> LM Purpose: SUA responds with the status of an SCTP association.
M-SCTP_状态确认方向：SUA->LM目的：SUA以SCTP关联的状态进行响应。
M-SCTP STATUS indication Direction: SUA -> LM Purpose: SUA reports the status of an SCTP association.
M-SCTP状态指示方向：SUA->LM目的：SUA报告SCTP关联的状态。
M-ASP_STATUS request Direction: LM -> SUA Purpose: LM requests SUA to report the status of a local or remote ASP.
M-ASP_状态请求方向：LM->SUA目的：LM请求SUA报告本地或远程ASP的状态。
M-ASP_STATUS confirm Direction: SUA -> LM Purpose: SUA reports status of local or remote ASP.
M-ASP_状态确认方向：SUA->LM目的：SUA报告本地或远程ASP的状态。
M-AS_STATUS request Direction: LM -> SUA Purpose: LM requests SUA to report the status of an AS.
M-AS_状态请求方向：LM->SUA目的：LM请求SUA报告AS的状态。
M-AS_STATUS confirm Direction: SUA -> LM Purpose: SUA reports the status of an AS.
M-AS_状态确认方向：SUA->LM目的：SUA报告AS的状态。
M-NOTIFY indication Direction: SUA -> LM Purpose: SUA reports that it has received a Notify message from its peer.
M-NOTIFY指示方向：SUA->LM目的：SUA报告已收到来自其对等方的NOTIFY消息。
M-ERROR indication Direction: SUA -> LM Purpose: SUA reports that it has received an Error message from its peer or that a local operation has been unsuccessful.
M-错误指示方向：SUA->LM目的：SUA报告它已收到来自其对等方的错误消息或本地操作已失败。
M-ASP_UP request Direction: LM -> SUA Purpose: LM requests ASP to start its operation and send an ASP Up message to its peer.
M-ASP_UP请求方向：LM->SUA目的：LM请求ASP启动其操作并向其对等方发送ASP UP消息。
M-ASP_UP confirm Direction: SUA -> LM Purpose: ASP reports that is has received an ASP UP Ack message from its peer.
M-ASP_UP confirm Direction:SUA->LM Purpose:ASP报告已从其对等方接收到ASP UP Ack消息。
M-ASP_UP indication Direction: SUA -> LM Purpose: SUA reports it has successfully processed an incoming ASP Up message from its peer.
M-ASP_UP指示方向：SUA->LM目的：SUA报告已成功处理来自其对等方的传入ASP UP消息。
M-ASP_DOWN request Direction: LM -> SUA Purpose: LM requests ASP to stop its operation and send an ASP Down message to its peer.
M-ASP_DOWN请求方向：LM->SUA目的：LM请求ASP停止其操作并向其对等方发送ASP DOWN消息。
M-ASP_DOWN confirm Direction: SUA -> LM Purpose: ASP reports that is has received an ASP Down Ack message from its peer.
M-ASP\U向下确认方向：SUA->LM目的：已从对等方接收到ASP向下确认消息的ASP报告。
M-ASP_DOWN indication Direction: SUA -> LM Purpose: SUA reports it has successfully processed an incoming ASP Down message from its peer, or the SCTP association has been lost/reset.
M-ASP_停机指示方向：SUA->LM目的：SUA报告已成功处理来自其对等方的传入ASP停机消息，或者SCTP关联已丢失/重置。
M-ASP_ACTIVE request Direction: LM -> SUA Purpose: LM requests ASP to send an ASP Active message to its peer.
M-ASP_活动请求方向：LM->SUA目的：LM请求ASP向其对等方发送ASP活动消息。
M-ASP_ACTIVE confirm Direction: SUA -> LM Purpose: ASP reports that is has received an ASP Active Ack message from its peer.
M-ASP_活动确认方向：SUA->LM目的：已从对等方收到ASP活动确认消息的ASP报告。
M-ASP_ACTIVE indication Direction: SUA -> LM Purpose: SUA reports it has successfully processed an incoming ASP Active message from its peer.
M-ASP_活动指示方向：SUA->LM目的：SUA报告已成功处理来自其对等方的传入ASP活动消息。
M-ASP_INACTIVE request Direction: LM -> SUA Purpose: LM requests ASP to send an ASP Inactive message to its peer.
M-ASP_非活动请求方向：LM->SUA目的：LM请求ASP向其对等方发送ASP非活动消息。
M-ASP_INACTIVE confirm Direction: LM -> SUA Purpose: ASP reports that is has received an ASP Inactive Ack message from its peer.
M-ASP_非活动确认方向：LM->SUA目的：从对等方接收到ASP非活动确认消息的ASP报告。
M-ASP_INACTIVE indication Direction: SUA -> LM Purpose: SUA reports it has successfully processed an incoming ASP Inactive message from its peer.
M-ASP_非活动指示方向：SUA->LM目的：SUA报告已成功处理来自其对等方的传入ASP非活动消息。
M-AS_ACTIVE indication Direction: SUA -> LM Purpose: SUA reports that an AS has moved to the AS-ACTIVE state.
M-AS_活动指示方向：SUA->LM目的：SUA报告AS已移动到活动状态。
M-AS_INACTIVE indication Direction: SUA -> LM Purpose: SUA reports that an AS has moved to the AS-INACTIVE state.
M-AS_非活动指示方向：SUA->LM目的：SUA报告AS已移动到AS-INACTIVE状态。
M-AS_DOWN indication Direction: SUA -> LM Purpose: SUA reports that an AS has moved to the AS-DOWN state.
M-AS_下降指示方向：SUA->LM目的：SUA报告AS已移动到AS下降状态。
If the SUA layer supports dynamic registration of Routing Key, the layer MAY support the following additional primitives:
如果SUA层支持路由密钥的动态注册，则该层可能支持以下附加原语：
M-RK_REG request Direction: LM -> SUA Purpose: LM requests ASP to register RK(s) with its peer by sending REG REQ message.
M-RK_REG请求方向：LM->SUA目的：LM通过发送REG REQ消息请求ASP向其对等方注册RK。
M-RK_REG confirm Direction: SUA -> LM Purpose: ASP reports that it has received REG RSP message with registration status as successful from its peer.
M-RK_REG confirm Direction:SUA->LM Purpose:ASP报告已从其对等方收到注册状态为成功的REG RSP消息。
M-RK_REG indication Direction: SUA -> LM Purpose: SUA informs LM that it has successfully processed an incoming REG REQ message.
M-RK_REG指示方向：SUA->LM目的：SUA通知LM已成功处理传入REG REQ消息。
M-RK_DEREG request Direction: LM -> SUA Purpose: LM requests ASP to deregister RK(s) with its peer by sending DEREG REQ message.
M-RK_DEREG请求方向：LM->SUA目的：LM通过发送DEREG REQ消息请求ASP与对等方注销RK。
M-RK_DEREG confirm Direction: SUA -> LM Purpose: ASP reports that it has received DEREG RESP message with deregistration status as successful from its peer.
M-RK_DEREG confirm Direction:SUA->LM Purpose:ASP报告已从其对等方收到注销状态为successful的DEREG RESP消息。
M-RK_DEREG indication Direction: SUA -> LM Purpose: SUA informs LM that it has successfully processed an incoming DEREG REQ from its peer.
M-RK_DEREG指示方向：SUA->LM目的：SUA通知LM已成功处理来自其对等方的传入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 BCP 14, RFC 2119 [2119].
本文件中出现的关键词必须、不得、必需、应、不应、应、不应、推荐、不推荐、可和可选时，应按照BCP 14、RFC 2119[2119]中的说明进行解释。
The general message format includes a Common Message Header together with a list of zero or more parameters as defined by the Message Type.
通用消息格式包括一个公共消息头以及由消息类型定义的零个或多个参数的列表。
For forward compatibility, all Message Types may have attached parameters even if none are specified in this version.
为了向前兼容，即使在此版本中未指定任何参数，所有消息类型都可能具有附加参数。
The Reserved field is set to 0 in messages sent and is not to be examined in messages received.
在已发送的邮件中，保留字段设置为0，在已接收的邮件中不进行检查。
The protocol messages for the SCCP-User Adaptation Protocol requires a message structure which contains a version, message class, message type, message length and message contents. This message header is common among all signalling protocol adaptation layers:
SCCP用户自适应协议的协议消息需要包含版本、消息类、消息类型、消息长度和消息内容的消息结构。此消息头在所有信令协议适配层中是通用的：
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 | Reserved | Message Class | Message Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Reserved | Message Class | Message Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Data |
Note that the 'data' portion of SUA messages SHALL contain SCCP-User data, not the encapsulated SCCP message.
请注意，SUA消息的“数据”部分应包含SCCP用户数据，而不是封装的SCCP消息。
Optional parameters can only occur at most once in an SUA message.
可选参数在SUA消息中最多只能出现一次。
The version field (ver) contains the version of the SUA adaptation layer. The supported versions are:
版本字段（ver）包含SUA适配层的版本。受支持的版本包括：
1 SUA version 1.0
1 SUA版本1.0
Message Classes
消息类
0 SUA Management (MGMT) Message 1 Reserved 2 Signalling Network Management (SNM) Messages 3 ASP State Maintenance (ASPSM) Messages 4 ASP Traffic Maintenance (ASPTM) Messages 5 Reserved 6 Reserved 7 Connectionless Messages 8 Connection-Oriented Messages 9 Routing Key Management (RKM) Messages. 10 - 127 Reserved by the IETF 128 - 255 Reserved for IETF-Defined Message Class Extensions
0 SUA管理（MGMT）消息1保留2信令网络管理（SNM）消息3 ASP状态维护（ASPSM）消息4 ASP流量维护（ASPTM）消息5保留6保留7无连接消息8面向连接的消息9路由密钥管理（RKM）消息。10-127由IETF保留128-255为IETF定义的消息类扩展保留
SUA Management Messages
SUA管理消息
0 Error (ERR) 1 Notify (NTFY) 2 - 127 Reserved by the IETF 128- 255 Reserved for IETF-Defined Message Class Extensions
0错误（ERR）1通知（NTFY）2-127由IETF保留128-255为IETF定义的消息类扩展保留
Signalling Network Management (SNM) Messages
信令网络管理（SNM）消息
0 Reserved 1 Destination Unavailable (DUNA) 2 Destination Available (DAVA) 3 Destination State Audit (DAUD) 4 Signalling Congestion (SCON) 5 Destination User Part Unavailable (DUPU) 6 Destination Restricted (DRST) 7 - 127 Reserved by the IETF 128 - 255 Reserved for IETF-Defined Message Class Extensions
0保留1目的地不可用（DUNA）2目的地可用（DAVA）3目的地状态审核（DAUD）4信令拥塞（SCON）5目的地用户部分不可用（DUPU）6目的地受限（DRST）7-127由IETF 128保留-255为IETF定义的消息类扩展保留
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 - 127 Reserved by the IETF 128 - 255 Reserved for IETF-Defined Message Class Extensions
0保留1 ASP向上（向上）2 ASP向下（向下）3心跳（节拍）4 ASP向上确认（向上确认）5 ASP向下确认（向下确认）6心跳确认（节拍确认）7-127由IETF保留128-255为IETF定义的消息类扩展保留
ASP Traffic Maintenance (ASPTM) Messages
ASP流量维护（ASPTM）消息
0 Reserved 1 ASP Active (ACTIVE) 2 ASP Inactive (INACTIVE) 3 ASP Active Ack (ACTIVE ACK) 4 ASP Inactive Ack (INACTIVE ACK) 5 - 127 Reserved by the IETF 128 - 255 Reserved for IETF-Defined Message Class Extensions
0保留1 ASP活动（活动）2 ASP非活动（非活动）3 ASP活动确认（活动确认）4 ASP非活动确认（非活动确认）5-127由IETF 128保留-255为IETF定义的消息类扩展保留
Routing Key Management (RKM) Messages
路由密钥管理（RKM）消息
0 Reserved 1 Registration Request (REG REQ) 2 Registration Response (REG RSP) 3 Deregistration Request (DEREG REQ) 4 Deregistration Response (DEREG RSP) 5 - 127 Reserved by the IETF 128 - 255 Reserved for IETF-Defined Message Class Extensions
0保留1注册请求（REG REQ）2注册响应（REG RSP）3注销请求（DEREG REQ）4注销响应（DEREG RSP）5-127由IETF保留128-255为IETF定义的消息类扩展保留
Connectionless (CL) Messages
无连接（CL）消息
0 Reserved 1 Connectionless Data Transfer (CLDT) 2 Connectionless Data Response (CLDR) 3 - 127 Reserved by the IETF 128 - 255 Reserved for IETF-Defined Message Class Extensions
0保留1无连接数据传输（CLDT）2无连接数据响应（CLDR）3-127由IETF保留128-255为IETF定义的消息类扩展保留
Connection-Oriented (CO) Messages
面向连接（CO）消息
0 Reserved 1 Connection Request (CORE) 2 Connection Acknowledge (COAK) 3 Connection Refused (COREF) 4 Release Request (RELRE) 5 Release Complete (RELCO) 6 Reset Confirm (RESCO) 7 Reset Request (RESRE) 8 Connection Oriented Data Transfer (CODT) 9 Connection Oriented Data Acknowledge (CODA) 10 Connection Oriented Error (COERR) 11 Inactivity Test (COIT) 12 - 127 Reserved by the IETF 128 - 255 Reserved for IETF-Defined Message Class Extensions
0保留1连接请求（核心）2连接确认（COAK）3连接拒绝（COREF）4释放请求（RELR）5释放完成（RELCO）6重置确认（RESCO）7重置请求（RESRE）8面向连接的数据传输（CODT）9面向连接的数据确认（CODA）10面向连接的错误（COERR）11不活动测试（COIT）12-127由IETF保留128-255为IETF定义的消息类扩展保留
The Message Length defines the length of the message in octets, including the header and including all padding bytes. Message Length is a 32-bit identifier.
消息长度以八位字节定义消息的长度，包括头和所有填充字节。消息长度是32位标识符。
SUA messages consist of a Common Header followed by zero or more parameters, as defined by the message type. The Tag-Length-Value (TLV) parameters contained in a message are defined in a Tag-Length-Value format as shown below.
根据消息类型的定义，SUA消息由一个公共头和零个或多个参数组成。消息中包含的标记长度值（TLV）参数以标记长度值格式定义，如下所示。
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 /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameter Tag: 16 bits (unsigned integer)
参数标记：16位（无符号整数）
Tag field is a 16-bit identifier of the type of parameter. It takes a value of 0 to 65535.
标记字段是参数类型的16位标识符。它的值为0到65535。
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. The Parameter Length does not include any padding bytes. However, composite parameters will contain all padding bytes, since all parameters contained within this composite parameter will be considered multiples of 4 bytes.
参数长度字段包含以字节为单位的参数大小，包括参数标记、参数长度和参数值字段。参数长度不包括任何填充字节。但是，复合参数将包含所有填充字节，因为此复合参数中包含的所有参数都将被视为4字节的倍数。
Parameter Value: variable-length.
参数值：可变长度。
The Parameter Value field contains the actual information to be transfered 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 SHOULD NOT pad with more than 3 bytes. The receiver MUST ignore the padding bytes.
参数的总长度（包括标记、参数长度和值字段）必须是4字节的倍数。如果参数的长度不是4字节的倍数，则发送方在参数末尾（即参数值字段之后）填充所有零字节。填充的长度不包括在参数长度字段中。发送方的填充不应超过3个字节。接收器必须忽略填充字节。
Implementation note: The use of TLV in principle allows the parameters to be placed in a random order in the message. However, some guidelines should be considered for easy processing in the following order:
实现说明：原则上使用TLV允许在消息中以随机顺序放置参数。但是，应考虑一些指南，以便按照以下顺序进行处理：
- Parameters needed to correctly process other message parameters, preferably should precede these parameters (such as Routing Context). - Mandatory parameters preferably SHOULD precede any optional parameters. - The data parameter will normally be the final one in the message.
- 正确处理其他消息参数所需的参数最好位于这些参数之前（如路由上下文）。-强制性参数优先于任何可选参数。-数据参数通常是消息中的最后一个参数。
- The receiver SHOULD accept parameters in any order, except where explicitly mandated.
- 接收方应接受任何顺序的参数，除非明确要求。
The following section describes the SUA Connectionless transfer messages and parameter contents. The general message format includes a Common Message Header together with a list of zero or more parameters as defined by the Message Type. All Message Types can have attached parameters.
以下部分介绍了SUA无连接传输消息和参数内容。通用消息格式包括一个公共消息头以及由消息类型定义的零个或多个参数的列表。所有消息类型都可以附加参数。
This message transfers data between one SUA to another.
此消息在一个SUA与另一个SUA之间传输数据。
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 = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0115 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Protocol Class |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0102 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Source Address /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0103 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Destination Address /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0116 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Control |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0101 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SS7 Hop Count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0113 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Importance |
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 = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0115 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Protocol Class |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0102 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Source Address /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0103 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Destination Address /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0116 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Control |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0101 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SS7 Hop Count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0113 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Importance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0114 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Priority |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0013 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Correlation ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0117 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Segmentation |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x010B | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Data /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0114 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Priority |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0013 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Correlation ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0117 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Segmentation |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x010B | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Data /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters Routing Context Mandatory Protocol Class Mandatory Source Address Mandatory Destination Address Mandatory Sequence Control Mandatory SS7 Hop Count Optional Importance Optional Message Priority Optional Correlation ID Optional Segmentation Optional Data Mandatory
参数路由上下文强制协议类强制源地址强制目标地址强制序列控制强制SS7跳数可选重要性可选消息优先级可选相关ID可选分段可选数据强制
Implementation note: This message covers the following SCCP messages: unitdata (UDT), extended unitdata (XUDT), long unitdata (LUDT).
实现说明：此消息包含以下SCCP消息：unitdata（UDT）、ExtendedUnitData（XUDT）、LongUnitData（LUDT）。
This message is used as a response message by the peer to report errors in the received CLDT message, when the return on error option is set.
当设置了return on error（返回错误）选项时，对等机将此消息用作响应消息，以报告收到的CLDT消息中的错误。
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 = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0106 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SCCP Cause |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0102 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Source Address /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0103 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Destination Address /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0101 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SS7 Hop Count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0113 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Importance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0114 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Priority |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0013 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Correlation ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0117 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Segmentation |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x010b | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
/ 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 = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0106 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SCCP Cause |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0102 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Source Address /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0103 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Destination Address /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0101 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SS7 Hop Count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0113 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Importance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0114 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Priority |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0013 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Correlation ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0117 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Segmentation |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x010b | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
/ Data /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters Routing Context Mandatory SCCP Cause Mandatory Source Address Mandatory Destination Address Mandatory SS7 Hop Count Optional Importance Optional Message Priority Optional Correlation ID Optional Segmentation Optional Data Optional
参数路由上下文强制SCCP导致强制源地址强制目标地址强制SS7跃点计数可选重要性可选消息优先级可选相关性ID可选分段可选数据可选
Implementation note: This message covers the following SCCP messages: unitdata service (UDTS), extended unitdata service (XUDTS) and long unitdata service (LUDTS).
实施说明：此消息涵盖以下SCCP消息：unitdata服务（UDTS）、扩展unitdata服务（XUDTS）和长unitdata服务（LUDTS）。
This message transfers data between one SUA to another for connection-oriented service.
此消息在一个SUA和另一个SUA之间传输数据，以实现面向连接的服务。
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 = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0107 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0105 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination Reference Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0114 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Priority |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0013 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Correlation ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x010b | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ 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 = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0107 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0105 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination Reference Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0114 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Priority |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0013 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Correlation ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x010b | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Data /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters Routing Context Mandatory Sequence Number Optional *1 Destination Reference Number Mandatory Message Priority Optional Correlation ID Optional Data Mandatory
参数路由上下文必需序列号可选*1目标参考号必需消息优先级可选相关性ID可选数据必需
NOTE *1: This parameter is not present in case of Expedited Data (ED).
注*1：对于加急数据（ED），此参数不存在。
Implementation note: For the CODT to represent DT1, DT2 and ED messages, the following conditions MUST be met:
实施说明：CODT要表示DT1、DT2和ED消息，必须满足以下条件：
DT1 is represented by a CODT when: Sequence Number parameter is present (contains "more" indicator).
当：序列号参数存在时（包含“更多”指示符），DT1由CODT表示。
DT2 is represented by a CODT when: Sequence Number parameter is present (contains P(S), P(R) and more indicator)
当序列号参数存在时（包含P（S）、P（R）和更多指示符），DT2由CODT表示
ED is represented by a CODT with: Sequence Number parameter is not present
ED由CODT表示，其中：序列号参数不存在
The peer uses this message to acknowledge receipt of data. This message is used only with protocol class 3.
对等方使用此消息确认收到数据。此消息仅用于协议类别3。
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 = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0105 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination Reference Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0108 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Receive Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x010A | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Credit |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0105 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination Reference Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0108 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Receive Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x010A | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Credit |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters Routing Context Mandatory Destination Reference Number Mandatory Receive Sequence Number Optional *1 Credit Mandatory *1
参数路由上下文强制目标参考号强制接收序列号可选*1信用强制*1
NOTE *1: Mandatory when representing Data Acknowledgement (AK).
注*1：表示数据确认（AK）时为必填项。
Implementation note: For the CODA to represent DA and EA messages, the following conditions MUST be met:
实施说明：要使尾码表示DA和EA消息，必须满足以下条件：
DA is represented by a CODA when: Receive Sequence Number parameter is present (contains P(S), P(R) and more indicator)
当：接收序列号参数存在时（包含P（S）、P（R）和更多指示器），DA由尾码表示
EA is represented by a CODA when: Receive Sequence Number parameter is not present
当：接收序列号参数不存在时，EA由尾码表示
This message is used for establishing a signalling connection between two peer endpoints.
此消息用于在两个对等端点之间建立信令连接。
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 = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0115 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Protocol Class |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0104 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source Reference Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0103 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Destination Address /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0116 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Control |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0107 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0102 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Source Address /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0101 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SS7 Hop Count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0113 | 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0115 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Protocol Class |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0104 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source Reference Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0103 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Destination Address /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0116 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Control |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0107 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0102 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Source Address /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0101 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SS7 Hop Count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0113 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Importance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0114 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Priority |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x010A | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Credit |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x010b | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Data /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Importance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0114 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Priority |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x010A | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Credit |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x010b | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Data /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters Routing Context Mandatory Protocol Class Mandatory Source Reference Number Mandatory Destination Address Mandatory Sequence Control Mandatory Sequence Number Optional *1 Source Address Optional SS7 Hop Count Optional Importance Optional Message Priority Optional Credit Optional *1 Data Optional
参数路由上下文强制协议类强制源参考号强制目标地址强制序列控制强制序列号可选*1源地址可选SS7跳数可选重要性可选消息优先级可选信用可选*1数据可选
NOTE *1: Mandatory for protocol class 3 only.
注*1：仅3级协议为强制性。
Implementation note: This message covers the following SCCP message: Connection Request (CR).
实施说明：此消息包含以下SCCP消息：连接请求（CR）。
This message is used to acknowledge a connection request from the peer endpoint.
此消息用于确认来自对等端点的连接请求。
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 = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0115 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Protocol Class |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0105 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination Reference Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0104 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source Reference Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x01116 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Control |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x010A | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Credit |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0102 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Source Address /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0113 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Importance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0114 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Priority |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0103 | 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0115 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Protocol Class |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0105 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination Reference Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0104 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source Reference Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x01116 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Control |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x010A | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Credit |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0102 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Source Address /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0113 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Importance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0114 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Priority |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0103 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Destination Address /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x010b | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Data /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Destination Address /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x010b | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Data /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters Routing Context Mandatory Protocol Class Mandatory Destination Reference Number Mandatory Source Reference Number Mandatory Sequence Control Mandatory Credit Mandatory *2 Source Address Optional Importance Optional Message Priority Optional Destination Address Optional *1 Data Optional
参数路由上下文强制协议类强制目标参考号强制源参考号强制顺序控制强制信用强制*2源地址可选重要性可选消息优先级可选目标地址可选*1数据可选
NOTE *1: Destination Address parameter will be present in case that the received CORE message conveys the Source Address parameter.
注*1：如果接收到的核心消息传递源地址参数，则会出现目标地址参数。
NOTE *2: Only applicable for protocol class 3.
注*2：仅适用于协议类别3。
Implementation note: This message covers the following SCCP message: Connection Confirm (CC).
实施说明：此消息包含以下SCCP消息：连接确认（CC）。
This message is used to refuse a connection request between two peer endpoints.
此消息用于拒绝两个对等端点之间的连接请求。
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 = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0105 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination Reference Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0106 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SCCP Cause |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0102 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Source Address /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0103 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Destination Address /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0113 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Importance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x010B | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ 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 = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0105 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination Reference Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0106 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SCCP Cause |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0102 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Source Address /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0103 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Destination Address /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0113 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Importance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x010B | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Data /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters Routing Context Mandatory Destination Reference Number Mandatory SCCP Cause Mandatory Source Address Optional Destination Address Optional *1 Importance Optional Data Optional
参数路由上下文强制目标参考号强制SCCP原因强制源地址可选目标地址可选*1重要性可选数据可选
Note *1: Destination Address parameter will be present in case that the received CORE message conveys the Source Address parameter.
注*1：如果接收到的核心消息传递源地址参数，则会出现目标地址参数。
Implementation note: This message covers the following SCCP message: Connection REFused (CREF).
实施说明：此消息包含以下SCCP消息：连接被拒绝（CREF）。
This message is used to request a signalling connection between two peer endpoints be released. All associated resources can then be released.
此消息用于请求释放两个对等端点之间的信令连接。然后可以释放所有相关资源。
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 = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0105 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination Reference Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0104 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source Reference Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0106 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SCCP Cause |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0113 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Importance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x010b | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ 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 = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0105 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination Reference Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0104 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source Reference Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0106 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SCCP Cause |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0113 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Importance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x010b | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Data /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters Routing Context Mandatory Destination Reference Number Mandatory Source Reference Number Mandatory SCCP Cause Mandatory Importance Optional Data Optional
参数路由上下文强制目标参考号强制源参考号强制SCCP原因强制重要性可选数据可选
Implementation note: This message covers the following SCCP message: connection ReLeaSeD (RLSD).
实施说明：此消息包含以下SCCP消息：已释放连接（RLSD）。
This message is used to acknowledge the release of a signalling connection between two peer endpoints. All associated resources should be released.
此消息用于确认两个对等端点之间信令连接的释放。应释放所有相关资源。
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 = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0105 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination Reference Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0104 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source Reference Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0113 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Importance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0105 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination Reference Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0104 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source Reference Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0113 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Importance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters Routing Context Mandatory Destination Reference Number Mandatory Source Reference Number Mandatory Importance Optional
参数路由上下文强制目标参考号强制源参考号强制重要性可选
Implementation note: This message covers the following SCCP message: ReLease Complete (RLC).
实施说明：此消息涵盖以下SCCP消息：发布完成（RLC）。
This message is used to indicate that the sending SCCP/SUA wants to initiate a reset procedure (reinitialization of sequence numbers) to the peer endpoint.
此消息用于指示发送SCCP/SUA希望启动对等端点的重置过程（序列号的重新初始化）。
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 = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0105 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination Reference Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0104 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source Reference Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0106 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SCCP Cause |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0105 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination Reference Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0104 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source Reference Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0106 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SCCP Cause |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters Routing Context Mandatory Destination Reference Number Mandatory Source Reference Number Mandatory SCCP Cause Mandatory
参数路由上下文强制目标参考号强制源参考号强制SCCP原因强制
Implementation note: This message covers the following SCCP message: ReSet Request (RSR).
实施说明：此消息包含以下SCCP消息：重置请求（RSR）。
This message is used to confirm the Reset Request.
此消息用于确认重置请求。
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 = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0105 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination Reference Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0104 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source Reference 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 = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0105 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination Reference Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0104 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source Reference Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters Routing Context Mandatory Destination Reference Number Mandatory Source Reference Number Mandatory
参数路由上下文强制目标参考号强制源参考号强制
Implementation note: This message covers the following SCCP message: ReSet Confirmation (RSC).
实施说明：此消息包含以下SCCP消息：重置确认（RSC）。
The COERR message is sent to indicate a protocol data unit error.
发送COERR消息以指示协议数据单元错误。
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 = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0105 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination Reference Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0106 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SCCP Cause |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0105 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination Reference Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0106 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SCCP Cause |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters Routing Context Mandatory Destination Reference Number Mandatory SCCP Cause Mandatory
参数路由上下文强制目标参考号强制SCCP原因强制
Implementation note: This message covers the following SCCP message: Protocol Data Unit ERRor (ERR).
实施说明：此消息包含以下SCCP消息：协议数据单元错误（ERR）。
This message is used for auditing the signalling connection state and the consistency of connection data at both ends of the signalling connection.
此消息用于审核信令连接状态和信令连接两端连接数据的一致性。
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 = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0115 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Protocol Class |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0104 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source Reference Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0105 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination Reference number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0107 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x010A | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Credit |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0115 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Protocol Class |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0104 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source Reference Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0105 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination Reference number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0107 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x010A | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Credit |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters Routing Context Mandatory Protocol Class Mandatory Source Reference Number Mandatory Destination Reference number Mandatory Sequence Number Mandatory *1 Credit Mandatory *1
参数路由上下文强制协议类强制源参考号强制目标参考号强制序列号强制*1信用强制*1
NOTE *1: Information in these parameter fields reflects those values sent in the last data form 2 or data acknowledgement message. They are ignored if the protocol class indicates class 2.
注*1：这些参数字段中的信息反映了上次数据表2或数据确认消息中发送的值。如果协议类指示类别2，则忽略它们。
Implementation note: This message covers the following SCCP message: Inactivity Test (IT).
实施说明：此消息包含以下SCCP消息：不活动测试（IT）。
In the scope of SUA, this message is covered by the PC- or N-state indication passed between SCCP and local SCCP-user. The DUNA message is sent from the SG or relay node to all concerned ASPs (servicing SCCP-users considered local to the SG or relay node, see chapter 1.3.1.1), when a destination or SCCP-user has become unreachable. The SUA-User at the ASP is expected to stop traffic to the affected destination or SCCP-user through the SG or relay node initiating the DUNA.
在SUA范围内，SCCP和本地SCCP用户之间传递的PC或N状态指示涵盖了该消息。当无法到达目的地或SCCP用户时，从SG或中继节点将DUNA消息发送至所有相关的ASP（为SG或中继节点认为本地的SCCP用户提供服务，见第1.3.1.1章）。ASP处的SUA用户预计将通过SG或中继节点停止到受影响目的地或SCCP用户的流量，从而启动DUNA。
The format for DUNA Message parameters is as follows:
DUNA消息参数的格式如下所示：
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 = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0012 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Affected Point Code /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x8003 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSN |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0112 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SMI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | 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 = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0012 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Affected Point Code /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x8003 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSN |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0112 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SMI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Info String /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters Routing Context Optional Affected Point Code Mandatory *1 SSN Optional *1 SMI Optional Info String Optional
参数路由上下文可选受影响点代码必需*1 SSN可选*1 SMI可选信息字符串可选
Note 1: When the SSN is included, the DUNA message corresponds to the SCCP N-STATE primitive. When SSN is not, the DUNA message corresponds to the SCCP N-PCSTATE primitive. The Affected Point Code parameter can only contain one point code when SSN is present.
注1：当包含SSN时，DUNA消息对应于SCCP N-STATE原语。如果未指定SSN，则DUNA消息对应于SCCP N-PCSTATE原语。当存在SSN时，受影响的点代码参数只能包含一个点代码。
In the scope of SUA, this message is covered by the PC- and N-state indication passed between SCCP and local SCCP-user. The DAVA message is sent from the SG or relay node to all concerned ASPs (servicing SCCP-users considered local to the SG or relay node, see chapter 1.3.1.1) to indicate that a destination (PC or SCCP-user) is now reachable. The ASP SUA-User protocol is expected to resume traffic to the affected destination through the SG or relay node initiating the DAVA.
在SUA范围内，SCCP和本地SCCP用户之间传递的PC和N状态指示涵盖了该消息。DAVA消息从SG或中继节点发送到所有相关的ASP（为SG或中继节点本地的SCCP用户提供服务，请参见第1.3.1.1章），以指示现在可以到达目的地（PC或SCCP用户）。ASP SUA用户协议预计将通过启动DAVA的SG或中继节点恢复到受影响目的地的通信量。
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 = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0012 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Affected Point Code /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x8003 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSN |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0112 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SMI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | 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 = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0012 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Affected Point Code /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x8003 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSN |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0112 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SMI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Info String /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters Routing Context Optional Affected Point Code Mandatory *1 SSN Optional *1 SMI Optional Info String Optional
参数路由上下文可选受影响点代码必需*1 SSN可选*1 SMI可选信息字符串可选
Note 1: When the SSN is included, the DAVA message corresponds to the SCCP N-STATE primitive. When SSN is not included, the DAVA message corresponds to the SCCP N-PCSTATE primitive. The Affected Point Code can only contain one point code when SSN is present.
注1：当包含SSN时，DAVA消息对应于SCCP N-STATE原语。当不包括SSN时，DAVA消息对应于SCCP N-PCSTATE原语。存在SSN时，受影响的点代码只能包含一个点代码。
The DAUD message can be sent from the ASP to the SG (or relay node) to query the availability state of the routes to an affected destination. A DAUD may be sent periodically after the ASP has received a DUNA, until a DAVA is received. The DAUD can also be sent when an ASP recovers from isolation from the SG (or relay node).
DAUD消息可以从ASP发送到SG（或中继节点），以查询到受影响目的地的路由的可用性状态。在ASP收到DUNA后，可以定期发送DAUD，直到收到DAVA为止。当ASP从SG（或中继节点）的隔离恢复时，也可以发送DAUD。
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 = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0012 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Affected Point Code /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x8003 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSN |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x010C | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| User/Cause |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | 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 = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0012 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Affected Point Code /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x8003 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSN |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x010C | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| User/Cause |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Info String /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters Routing Context Optional Affected Point Code Mandatory *1 SSN Optional *1 User / Cause Optional Info String Optional
参数路由上下文可选受影响点代码必需*1 SSN可选*1用户/原因可选信息字符串可选
Note 1: If the SSN is present, the DAUD is "soliciting" N-STATE primitives, otherwise it is "soliciting" N-PCSTATE primitives.
注1：如果存在SSN，则DAUD是“请求”N状态原语，否则它是“请求”N状态原语。
The SCON message can be sent from the SG or relay node to all concerned ASPs to indicate that the congestion level in the SS7 network to a specified destination has changed.
SCON消息可以从SG或中继节点发送到所有相关的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 = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0012 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Affected Point Code /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x8003 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSN |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0118 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Congestion Level |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0112 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SMI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | 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 = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0012 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Affected Point Code /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x8003 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSN |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0118 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Congestion Level |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0112 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SMI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Info String /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters Routing Context Optional Affected Point Code Mandatory *1 SSN Optional *1 Congestion Level Mandatory SMI Optional Info String Optional
参数路由上下文可选受影响点代码必需*1 SSN可选*1拥塞级别必需SMI可选信息字符串可选
Note 1: When the SSN is included, the SCON message corresponds to the SCCP N-STATE primitive. When the SSN is not included, the SCON message corresponds to the SCCP
注1：当包含SSN时，SCON消息对应于SCCP N-STATE原语。当不包括SSN时，SCON消息对应于SCCP
N-PCSTATE primitive reporting signalling point or network congestion status.
N-PCSTATE原语报告信令点或网络拥塞状态。
The DUPU message is used by an SG to inform an ASP that a remote peer at an SS7 node is unavailable.
SG使用DUPU消息通知ASP SS7节点上的远程对等点不可用。
The format for DUPU message parameters is as follows:
DUPU消息参数的格式如下所示：
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 = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0012 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Affected Point Code /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x010C | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| User/Cause |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | 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 = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0012 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Affected Point Code /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x010C | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| User/Cause |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ INFO String /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters Routing Context Optional Affected Point Code Mandatory *1 User/Cause Mandatory Info String Optional
参数路由上下文可选受影响点代码必填*1用户/原因必填信息字符串可选
Note 1: The DUPU corresponds to the SCCP N-PCSTATE primitive.
注1：DUPU对应于SCCP N-PCSTATE原语。
The DRST message is optionally sent from the SG to all concerned ASPs to indicate that the SG has determined that one or more destinations are now restricted from the point of view of the SG, or in response to a DAUD message if appropriate. The SUA layer at the ASP is
DRST消息可选择地从SG发送到所有相关的asp，以指示SG已确定一个或多个目的地现在从SG的角度受到限制，或在适当时响应DAUD消息。ASP的SUA层是
expected to send traffic to the affected destination via an alternate SG of equal priority, but only if such an alternate route exists and is available. If the ASP currently considers the affected destination unavailable, the peer should be informed that traffic to the affected destination could be resumed. In this case, the SUA layer should route the traffic through the SG initiating the DRST message.
预期通过同等优先级的备用SG向受影响的目的地发送流量，但前提是该备用路由存在且可用。如果ASP当前认为受影响的目的地不可用，则应通知对等方可以恢复到受影响目的地的通信。在这种情况下，SUA层应通过发起DRST消息的SG路由流量。
This message is optional for the SG to send and it is optional for the ASP to act on any information received in the message.
此消息可供SG发送，也可供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 = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0012 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Affected Point Code /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x8003 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSN |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0112 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | SMI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | 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 = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0012 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Affected Point Code /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x8003 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSN |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0112 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | SMI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Info String /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters Routing Context Optional Affected Point Code Mandatory *1 SSN Optional *1 SMI Optional *1 Info String Optional
参数路由上下文可选受影响点代码必需*1 SSN可选*1 SMI可选*1信息字符串可选
Note 1: The Affected Point Code refers to the node to which become restricted or which has requested coordinated service outage. When SSN is included in the message
注1：受影响点代码是指受到限制或请求协调服务中断的节点。当SSN包含在消息中时
parameter, the DRST message corresponds to the SCCP N-COORD primitive. If the SMI parameter is also included in the message, the DRST message corresponds to the N-COORD Request and N-COORD Indication primitives, otherwise, the DRST message correspondence to the N-COORD Response and N-COORD Confirm primitives. The Affected Point Code can only contain one point code when SSN is present. When SSN is not present, DRST corresponds to N-PCSTATE primitive.
参数，DRST消息对应于SCCP N-COORD原语。如果消息中还包含SMI参数，则DRST消息对应于N-COORD请求和N-COORD指示原语，否则，DRST消息对应于N-COORD响应和N-COORD确认原语。存在SSN时，受影响的点代码只能包含一个点代码。当SSN不存在时，DRST对应于N-PCSTATE原语。
The ASP UP (UP) message is used to indicate to a remote SUA peer that the Adaptation layer is up and running.
ASP UP（UP）消息用于向远程SUA对等方指示适配层已启动并正在运行。
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 = 0x0011 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ASP Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | 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 = 0x0011 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ASP Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Info String /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters ASP Identifier Optional *1 Info String Optional
参数ASP标识符可选*1信息字符串可选
Note 1: ASP Identifier MUST be used where the IPSP/SGP cannot identify the ASP by provisioned address/port number information (e.g., where an ASP is resident on a Host using dynamic address/port number assignment).
注1：如果IPSP/SGP无法通过提供的地址/端口号信息识别ASP（例如，ASP驻留在使用动态地址/端口号分配的主机上），则必须使用ASP标识符。
The ASP UP Ack message is used to acknowledge an ASP-Up message received from a remote SUA peer.
ASP UP Ack消息用于确认从远程SUA对等方收到的ASP UP消息。
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 = 0x0004 | 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 = 0x0004 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Info String /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters Info String Optional
参数信息字符串可选
The ASP Down (DOWN) message is used to indicate to a remote SUA peer that the adaptation layer is not running.
ASP Down（向下）消息用于向远程SUA对等方指示适配层未运行。
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 = 0x0004 | 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 = 0x0004 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Info String /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters Info String Optional
参数信息字符串可选
The ASP DOWN Ack message is used to acknowledge an ASP-Down message received from a remote SUA peer.
ASP DOWN Ack消息用于确认从远程SUA对等方接收到的ASP DOWN消息。
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 = 0x0004 | 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 = 0x0004 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Info String /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters Info String Optional
参数信息字符串可选
Note: ASP DOWN ACK will always be sent to acknowledge an ASP DOWN.
注意：ASP DOWN ACK将始终被发送以确认ASP DOWN。
The Heartbeat message is optionally used to ensure that the SUA peers are still available to each other.
Heartbeat消息可选择性地用于确保SUA对等点彼此仍然可用。
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 /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters Heartbeat Data Optional
参数心跳数据可选
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 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 /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters Heartbeat Data Optional
参数心跳数据可选
The ASPAC message is sent by an ASP to indicate to a remote SUA peer that it is Active and ready to process signalling traffic for a particular Application Server.
ASPAC消息由ASP发送，以向远程SUA对等方表明其处于活动状态并准备处理特定应用程序服务器的信令通信。
The format for the ACTIVE 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 = 0x000B | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Traffic Mode Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0110 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TID Label |
+-------------------------------+-------------------------------+
| Tag = 0x010F | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| DRN Label |
+-------------------------------+-------------------------------+
| Tag = 0x0004 | 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 = 0x000B | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Traffic Mode Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0110 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TID Label |
+-------------------------------+-------------------------------+
| Tag = 0x010F | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| DRN Label |
+-------------------------------+-------------------------------+
| Tag = 0x0004 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Info String /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters Traffic Mode Type Optional Routing Context Optional TID Label Optional DRN Label Optional Info String Optional
参数流量模式类型可选路由上下文可选TID标签可选DRN标签可选信息字符串可选
The ASPAC Ack message is used to acknowledge an ASP-Active message received from a remote SUA peer.
ASPAC Ack消息用于确认从远程SUA对等方收到的ASP活动消息。
The format for the ACTIVE Ack message is as follows:
活动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 = 0x000B | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Traffic Mode Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | 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 = 0x000B | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Traffic Mode Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Info String /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters Traffic Mode Type Optional Routing Context Mandatory Info String Optional
参数流量模式类型可选路由上下文必需信息字符串可选
The INACTIVE message is sent by an ASP to indicate to a remote SUA peer that it is no longer processing signalling traffic within a particular Application Server.
非活动消息由ASP发送，以向远程SUA对等方指示它不再处理特定应用程序服务器内的信令流量。
The format for the ASPIA message parameters is as follows:
ASPIA消息参数的格式如下：
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 = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | 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 = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ INFO String /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters Routing Context Optional INFO String Optional
参数路由上下文可选信息字符串可选
The INACTIVE Ack message is used to acknowledge an ASP-Inactive message received from a remote SUA peer.
非活动Ack消息用于确认从远程SUA对等方接收到的ASP非活动消息。
The format for the INACTIVE Ack message is as follows:
非活动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 = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | 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 = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ INFO String /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters Routing Context Optional INFO String Optional
参数路由上下文可选信息字符串可选
These messages are used for managing SUA and the representations of the SCCP subsystems in the SUA layer.
这些消息用于管理SUA和SUA层中SCCP子系统的表示。
The ERR message is sent between two SUA peers to indicate an error situation. The Diagnostic Information parameter is optional, possibly used for error logging and/or debugging.
ERR消息在两个SUA对等方之间发送，以指示错误情况。诊断信息参数是可选的，可能用于错误记录和/或调试。
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 = 0x000C | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Error Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0012 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mask | Affected PC 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ ... /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mask | Affected PC n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x010D | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Network Appearance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0007 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Diagnostic Info /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 = 0x000C | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Error Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0012 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mask | Affected PC 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ ... /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mask | Affected PC n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x010D | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Network Appearance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0007 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Diagnostic Info /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameters Error Code Mandatory Routing Context Mandatory *1 Network Appearance Mandatory *1 Affected Point Code Mandatory *1 Diagnostic Information Optional
参数错误代码强制路由上下文强制*1网络外观强制*1受影响点代码强制*1诊断信息可选
Note 1: Only mandatory for specific error codes.
注1：仅对特定错误代码是强制性的。
The Notify message used to provide an autonomous indication of SUA events to an SUA peer.
用于向SUA对等方提供SUA事件的自主指示的通知消息。
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 = 0x000D | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0011 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ASP Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
| Tag = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | 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 = 0x000D | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0011 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ASP Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
| Tag = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Info String /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The NTFY message contains the following parameters:
NTFY消息包含以下参数：
Parameters Status Mandatory ASP Identifier Optional *1 Routing Context Optional Info String Optional
参数状态强制ASP标识符可选*1路由上下文可选信息字符串可选
Note 1: ASP Identifier MUST be used where the IPSP/SGP cannot identify the ASP by provisioned address/port number information (e.g., where an ASP is resident on a Host using dynamic address/port number assignment).
注1：如果IPSP/SGP无法通过提供的地址/端口号信息识别ASP（例如，ASP驻留在使用动态地址/端口号分配的主机上），则必须使用ASP标识符。
The REG REQ message is sent by an ASP to indicate to a remote SUA peer that it wishes to register one or more given Routing Keys with the remote peer. Typically, an ASP would send this message to an SGP, and expects to receive a REG RSP message in return with an associated Routing Context value.
REG REQ消息由ASP发送，以指示远程SUA对等方它希望向远程对等方注册一个或多个给定路由密钥。通常，ASP会将此消息发送给SGP，并期望收到一条REG RSP消息以及相关的路由上下文值。
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 = 0x010E | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Key 1 /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ ... /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x010E | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Key n /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0109 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ASP Capabilities |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 = 0x010E | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Key 1 /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ ... /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x010E | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Key n /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0109 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ASP Capabilities |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The REG REQ message contains the following parameters:
REG REQ消息包含以下参数：
Parameters Routing Key Mandatory *1 ASP Capabilities Optional
参数路由密钥必需*1 ASP功能可选
Note 1: One or more Routing Key parameters MAY be included in a single REG REQ message.
注1：单个REG REQ消息中可能包含一个或多个路由密钥参数。
The REG RSP message is sent by an SG to an ASP indicate the result of a previous REG REQ from an ASP. It contains indications of success/failure for registration requests and returns a unique Routing Context value for successful registration requests, to be used in subsequent SUA Traffic Management protocol messages.
SG向ASP发送REG RSP消息，指示ASP先前REG REQ的结果。它包含注册请求成功/失败的指示，并返回成功注册请求的唯一路由上下文值，用于后续SUA流量管理协议消息。
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 = 0x0014 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Registration Result 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ ... /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0014 | 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 = 0x0014 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Registration Result 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ ... /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0014 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Registration Result n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The REG RSP message contains the following parameters:
REG RSP消息包含以下参数：
Parameters Registration Result Mandatory *1
参数注册结果必填*1
Note 1: One or more Registration Result parameters MAY be included in a single REG RSP message. The number of results in a single REG RSP message can be anywhere from one to the total number of Routing Key parameters found in the corresponding REG REQ message.
注1：单个REG RSP消息中可能包含一个或多个注册结果参数。单个REG RSP消息中的结果数可以是从1到相应REG REQ消息中找到的路由密钥参数总数的任意值。
The DEREG REQ message is sent by an ASP to indicate to a remote SUA peer that it wishes to deregister a given Routing Key. Typically, an ASP would send this message to an SGP, and expects to receive a DEREG RSP message in return with the associated Routing Context value.
DEREG REQ消息由ASP发送，以指示远程SUA对等方它希望取消注册给定的路由密钥。通常，ASP会将此消息发送给SGP，并期望收到一条带相关路由上下文值的DEREG RSP消息。
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 = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The DEREG REQ message contains the following parameters:
DEREG REQ消息包含以下参数：
Parameters Routing Context Mandatory
参数路由上下文是必需的
The DEREG RSP message is used as a response to the DEREG REQ message from a remote SUA peer.
DEREG RSP消息用作对来自远程SUA对等方的DEREG REQ消息的响应。
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 = 0x0015 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Deregistration Result 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ ... /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0015 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Deregistration 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 = 0x0015 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Deregistration Result 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ ... /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0015 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Deregistration Result n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The DEREG RSP message contains the following parameters:
DEREG RSP消息包含以下参数：
Parameters Deregistration Result Mandatory *1
参数注销结果必填*1
Note 1: One or more Deregistration Result parameters MAY be included in one DEREG RSP message. The number of results in a single DEREG RSP message can be anywhere from one to the total number of Routing Context parameters found in the corresponding DEREG REQ message.
注1：一条注销RSP消息中可能包含一个或多个注销结果参数。单个DEREG RSP消息中的结果数可以是从1到相应DEREG REQ消息中找到的路由上下文参数总数的任意值。
These TLV parameters are common across the different adaptation layers.
这些TLV参数在不同的适应层中是通用的。
Parameter Name Parameter ID
============== ============
Reserved 0x0000
Not used in SUA 0x0001
Not used in SUA 0x0002
Not used in SUA 0x0003
Info String 0x0004
Not used in SUA 0x0005
Routing Context 0x0006
Diagnostic Info 0x0007
Not used in SUA 0x0008
Heartbeat Data 0x0009
Not Used in SUA 0x000A
Traffic Mode Type 0x000B
Error Code 0x000C
Status 0x000D
Not used in SUA 0x000E
Not used in SUA 0x000F
Not used in SUA 0x0010
ASP Identifier 0x0011
Affected Point Code 0x0012
Correlation ID 0x0013
Registration Result 0x0014
Deregistration Result 0x0015
Registration Status 0x0016
Deregistration Status 0x0017
Local Routing Key Identifier 0x0018
Parameter Name Parameter ID
============== ============
Reserved 0x0000
Not used in SUA 0x0001
Not used in SUA 0x0002
Not used in SUA 0x0003
Info String 0x0004
Not used in SUA 0x0005
Routing Context 0x0006
Diagnostic Info 0x0007
Not used in SUA 0x0008
Heartbeat Data 0x0009
Not Used in SUA 0x000A
Traffic Mode Type 0x000B
Error Code 0x000C
Status 0x000D
Not used in SUA 0x000E
Not used in SUA 0x000F
Not used in SUA 0x0010
ASP Identifier 0x0011
Affected Point Code 0x0012
Correlation ID 0x0013
Registration Result 0x0014
Deregistration Result 0x0015
Registration Status 0x0016
Deregistration Status 0x0017
Local Routing Key Identifier 0x0018
Use of Parameter ID 0x0001 in SUA messages is not supported.
不支持在SUA消息中使用参数ID 0x0001。
Use of Parameter ID 0x0002 in SUA messages is not supported.
不支持在SUA消息中使用参数ID 0x0002。
Use of Parameter ID 0x0003 in SUA messages is not supported.
不支持在SUA消息中使用参数ID 0x0003。
The optional INFO String parameter can carry any meaningful UTF-8 [3629] 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 service providers may use the INFO String for debugging purposes.
可选信息字符串参数可以携带任何有意义的UTF-8[3629]字符串以及消息。信息字符串参数的长度为0到255个八位字节。目前还没有为其使用标识任何过程，但服务提供商可以出于调试目的使用信息字符串。
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 = 0x0004 | 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 = 0x0004 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Info String /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Use of Parameter ID 0x0005 in SUA messages is not supported.
不支持在SUA消息中使用参数ID 0x0005。
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 = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Routing Context parameter contains (a list of) 4-byte unsigned integers indexing the Application Server traffic that the sending ASP is configured/registered to receive. There is a one-to-one relationship between an index entry and a Routing Key or AS Name.
路由上下文参数包含（一组）4字节无符号整数，用于索引发送ASP配置/注册为接收的应用程序服务器流量。索引项和路由键或AS名称之间存在一对一的关系。
An Application Server Process may be configured to process traffic for more than one logical Application Server. From the perspective of an ASP, a Routing Context defines a range of signalling traffic that the ASP is currently configured to receive from the SG.
应用服务器进程可以配置为处理多个逻辑应用服务器的流量。从ASP的角度来看，路由上下文定义了ASP当前配置为从SG接收的信令通信量的范围。
Additionally, the Routing Context parameter identifies the SS7 network context for the message, for the purposes of logically separating the signalling traffic between the SGP and the Application Server Process over a common SCTP Association, when needed. An example is where an SGP is logically partitioned to appear as an
此外，路由上下文参数标识消息的SS7网络上下文，以便在需要时通过公共SCTP关联在逻辑上分离SGP和应用服务器进程之间的信令通信量。例如，SGP在逻辑上被划分为
element in several different national SS7 networks. It implicitly defines the SS7 Point Code format used, the SS7 Network Indicator value and SCCP protocol type/variant/version used within a separate SS7 network. It also defines the network context for the PC and SSN values. Where an SGP operates in the context of a single SS7 network, or individual SCTP associations are dedicated to each SS7 network context, this functionality is not needed.
多个不同的国家SS7网络中的元素。它隐式定义了所使用的SS7点代码格式、SS7网络指示符值以及在单独的SS7网络中使用的SCCP协议类型/变量/版本。它还定义了PC和SSN值的网络上下文。如果SGP在单个SS7网络的上下文中运行，或者单个SCTP关联专用于每个SS7网络上下文，则不需要此功能。
If the Routing Context parameter is present, it SHOULD be the first parameter in the message as it defines the format and/or interpretation of the parameters containing a PC or SSN value.
如果存在路由上下文参数，它应该是消息中的第一个参数，因为它定义了包含PC或SSN值的参数的格式和/或解释。
The Diagnostic Information can be used to convey any information relevant to an error condition, to assist in the identification of the error condition. In the case of an Adaptation Layer Identifier or Traffic Handling Mode, the Diagnostic Information includes the received parameter. In the other cases, the Diagnostic information may be the first 40 bytes of the offending message.
诊断信息可用于传达与错误状况相关的任何信息，以帮助识别错误状况。在适配层标识符或业务处理模式的情况下，诊断信息包括接收到的参数。在其他情况下，诊断信息可能是违规消息的前40个字节。
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 = 0x0007 | 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 = 0x0007 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Diagnostic Information /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Parameter ID 0x0008 is not used in SUA.
SUA中未使用参数ID 0x0008。
The sending node defines the Heartbeat Data field contents. It may include a Heartbeat Sequence Number and/or Timestamp, 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.
心跳消息的接收者不处理此字段，因为它仅对发送者重要。接收器在拍确认消息中回显心跳数据的内容。
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 data field can be used to store information in the heartbeat message useful to the sending node (e.g., the data field can contain a time stamp, a sequence number, etc.).
数据字段可用于在发送节点有用的心跳消息中存储信息（例如，数据字段可包含时间戳、序列号等）。
Parameter ID 0x000A is not used in SUA.
SUA中未使用参数ID 0x000A。
The Traffic Mode Type parameter identifies the traffic mode of operation of the ASP within an AS.
Traffic Mode Type参数标识AS中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 = 0x000B | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Traffic Mode Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 = 0x000B | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Traffic Mode Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The valid values for Type are shown in the following table.
类型的有效值如下表所示。
1 Override 2 Loadshare 3 Broadcast
1覆盖2负载共享3广播
Within a Routing Context, Override, Loadshare Types and Broadcast cannot be mixed. The Override value indicates that the ASP is operating in Override mode, and the ASP wishes to take over all traffic for an Application Server (i.e., primary/backup operation), overriding any currently active ASP in the AS. In Loadshare mode, the ASP wishes to share in the traffic distribution with any other currently active ASPs. In Broadcast mode, the ASP wishes to receive the same traffic as any other currently active ASPs. When there are insufficient ASPs, the sender may immediately move the ASP to Active.
在路由上下文中，覆盖、负载共享类型和广播不能混合使用。Override值表示ASP正在Override模式下运行，并且ASP希望接管应用程序服务器的所有通信（即主/备份操作），从而覆盖AS中任何当前活动的ASP。在Loadshare模式下，ASP希望与任何其他当前活动的ASP共享流量分布。在广播模式下，ASP希望接收与任何其他当前活动的ASP相同的流量。当ASP不足时，发送方可立即将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 =0x000C | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Error Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 =0x000C | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Error Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Error Code parameter indicates the reason for the Error Message. The Error parameter value can be one of the following values:
Error Code参数指示错误消息的原因。错误参数值可以是以下值之一：
0x01 Invalid Version 0x02 Not Used in SUA 0x03 Unsupported Message Class 0x04 Unsupported Message Type 0x05 Unsupported Traffic Handling Mode 0x06 Unexpected Message 0x07 Protocol Error 0x08 Not used in SUA 0x09 Invalid Stream Identifier 0x0a Not used in SUA 0x0b Not used in SUA 0x0c Not used in SUA 0x0d Refused - Management Blocking 0x0e ASP Identifier Required 0x0f Invalid ASP Identifier 0x10 Not Used in SUA 0x11 Invalid Parameter Value 0x12 Parameter Field Error 0x13 Unexpected Parameter 0x14 Destination Status Unknown 0x15 Invalid Network Appearance 0x16 Missing Parameter 0x17 Not Used in SUA 0x18 Not Used in SUA 0x19 Invalid Routing Context 0x1a No Configured AS for ASP 0x1b Subsystem Status Unknown 0x1c Invalid loadsharing label
0x01无效版本0x02未在SUA中使用0x03不支持的消息类0x04不支持的消息类型0x05不支持的流量处理模式0x06意外消息0x07协议错误0x08未在SUA中使用0x09无效流标识符0x0a未在SUA中使用0x0b未在SUA中使用0x0c未在SUA中使用0x0d被拒绝-管理阻止0x0e ASP所需标识符0x0f无效ASP标识符0x10未在SUA中使用0x11无效参数值0x12参数字段错误0x13意外参数0x14目标状态未知0x15无效网络外观0x16缺少参数0x17未在SUA中使用0x18未在SUA中使用0x19无效路由上下文0x1a未为ASP 0x1b配置子系统状态未知0x1c加载共享标签无效
The "Invalid Version" error is sent if a message was received with an invalid or unsupported version. The Error message contains the supported version in the Common header. The Error message could optionally provide the unsupported version in the Diagnostic information area.
如果收到的消息版本无效或不受支持，则会发送“无效版本”错误。错误消息在公用标头中包含受支持的版本。错误消息可以在诊断信息区域提供不支持的版本。
The "Unsupported Message Class" error is sent if a message with an unexpected or unsupported Message Class is received.
如果收到包含意外或不支持的消息类的消息，则会发送“不支持的消息类”错误。
The "Unsupported Message Type" error is sent if a message with an unexpected or unsupported Message Type is received.
如果收到具有意外或不支持的消息类型的消息，则会发送“不支持的消息类型”错误。
The "Unsupported Traffic Handling Mode" error is sent by a SGP if an ASP sends an ASP Active message with an unsupported Traffic Mode Type or a Traffic Mode Type that is inconsistent with the presently configured mode for the Application Server. An example would be a case in which the SGP did not support loadsharing.
如果ASP发送的ASP活动消息具有不受支持的流量模式类型或与应用服务器当前配置的模式不一致的流量模式类型，则SGP将发送“不受支持的流量处理模式”错误。例如，SGP不支持负载共享。
The "Unexpected Message" error MAY be sent if a defined and recognized message is received that is not expected in the current state (in some cases the ASP may optionally silently discard the message and not send an Error message). For example, silent discard is used by an ASP if it received a DATA message from an SGP while it was in the ASP-INACTIVE state. If the Unexpected message contained Routing Context(s), the Routing Context(s) SHOULD be included in the Error message.
如果接收到当前状态下不期望的已定义和已识别的消息，则可能会发送“意外消息”错误（在某些情况下，ASP可能会选择以静默方式放弃该消息，而不发送错误消息）。例如，如果ASP在ASP-INACTIVE状态下收到来自SGP的数据消息，则ASP将使用静默丢弃。如果意外消息包含路由上下文，则错误消息中应包含路由上下文。
The "Protocol Error" error is sent for any protocol anomaly (i.e., reception of a parameter that is syntactically correct but unexpected in the current situation.
针对任何协议异常发送“协议错误”错误（即，接收到语法正确但在当前情况下意外的参数）。
The "Invalid Stream Identifier" error is sent if a message is received on an unexpected SCTP stream.
如果在意外的SCTP流上接收到消息，则会发送“无效流标识符”错误。
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 lockout"). If this error is in response to an ASP Active message, the Routing Context(s) in the ASP Active message SHOULD be included in the Error message.
“拒绝-管理阻止”错误在收到ASP Up或ASP Active message且请求因管理原因（例如，管理锁定）而被拒绝时发送。如果此错误是对ASP Active message的响应，则ASP Active message中的路由上下文应包含在错误消息中。
The "ASP Identifier Required" is sent by a SGP in response to an ASP Up message that does not contain an ASP Identifier parameter when the SGP requires one. The ASP SHOULD resend the ASP Up message with an ASP Identifier.
当SGP需要ASP标识符参数时，“需要ASP标识符”由SGP发送，以响应不包含ASP标识符参数的ASP Up消息。ASP应使用ASP标识符重新发送ASP Up消息。
The "Invalid ASP Identifier" is send by a SGP in response to an ASP Up message with an invalid ASP Identifier.
“无效ASP标识符”由SGP发送，以响应带有无效ASP标识符的ASP Up消息。
The "Invalid Parameter Value" error is sent if a message is received with an invalid parameter value (e.g., a DUPU message was received with a Mask value other than "0".
如果接收到具有无效参数值的消息（例如，接收到的DUPU消息的掩码值不是“0”），则会发送“无效参数值”错误。
The "Parameter Field Error" would be sent if a message is received with a parameter having a wrong length field.
如果接收到带有错误长度字段的参数的消息，将发送“参数字段错误”。
The "Unexpected Parameter" error would be sent if a message contains an invalid parameter.
如果消息包含无效参数，将发送“意外参数”错误。
The "Invalid Network Appearance" error is sent by a SGP if an ASP sends a message with an invalid (not configured) Network Appearance value. For this error, the invalid (not configured) Network Appearance MUST be included in the Network Appearance parameter.
如果ASP发送具有无效（未配置）网络外观值的消息，则SGP将发送“无效网络外观”错误。对于此错误，网络外观参数中必须包含无效（未配置）的网络外观。
The "Missing Parameter" error would be sent if a mandatory parameter were not included in a message.
如果消息中未包含强制参数，则会发送“缺少参数”错误。
The "Invalid Routing Context" error would be sent by a SG if an ASP sends a message with an invalid (not configured) Routing Context value. For this error, the invalid (not configured) Routing Context(s) MUST be included in the Routing Context parameter.
如果ASP发送带有无效（未配置）路由上下文值的消息，则SG将发送“无效路由上下文”错误。对于此错误，路由上下文参数中必须包含无效（未配置）路由上下文。
The "No Configured AS for ASP" error is sent if a message is received from a peer without a Routing Context parameter and it is not known by configuration data, which Application Servers are referenced.
如果从没有路由上下文参数的对等方接收到消息，并且配置数据不知道该消息，则会发送“No Configured AS for ASP”错误，引用的应用程序服务器。
The "Destination Status Unknown" Error MAY be sent if a DAUD is received at an SG inquiring of the availability or congestion status of a destination, and the SG does not wish to provide the status (e.g., the sender is not authorized to know the status). For this error, the invalid or unauthorized Point Code(s) MUST be included along with the Network Appearance and Routing Context associated with the Point Code(s).
如果SG收到DAUD询问目的地的可用性或拥塞状态，并且SG不希望提供该状态（例如，发送方无权知道该状态），则可能会发送“目的地状态未知”错误。对于此错误，必须包括无效或未经授权的点代码以及与点代码关联的网络外观和路由上下文。
The "Subsystem Status Unknown" Error MAY be sent if a DAUD is received at an SG inquiring of the availability or congestion status of a subsystem, and the SG does not wish to provide the status (e.g., the sender is not authorized to know the status). For this error, the invalid or unauthorized Point Code and Subsystem Number MUST be included along with the Network Appearance and Routing Context associated with the Point Code and Subsystem Number.
如果SG收到询问子系统可用性或拥塞状态的DAUD，且SG不希望提供该状态（例如，发送方无权知道该状态），则可能会发送“子系统状态未知”错误。对于此错误，必须包括无效或未经授权的点代码和子系统编号，以及与点代码和子系统编号关联的网络外观和路由上下文。
The Status parameter identifies the type of the status that is being notified and the Status ID.
Status参数标识正在通知的状态类型和状态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 = 0x000D | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Status Type | Status 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 = 0x000D | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Status Type | Status ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The valid values for Status Type (16 bit unsigned integer) are:
状态类型（16位无符号整数）的有效值为：
1 Application Server state change (AS_State_Change) 2 Other
1应用程序服务器状态更改（作为状态更改）2其他
The Status ID parameter contains more detailed information for the notification, based on the value of the Status Type.
Status ID参数根据状态类型的值包含通知的更详细信息。
If the Status Type is AS_STATE_CHANGE, then the Status ID (16 bit unsigned integer) values are:
如果状态类型为AS_STATE_CHANGE，则状态ID（16位无符号整数）值为：
1 reserved 2 Application Server Inactive (AS-Inactive) 3 Application Server Active (AS-Active) 4 Application Server Pending (AS-Pending)
1保留2应用程序服务器不活动（作为不活动）3应用程序服务器活动（作为活动）4应用程序服务器挂起（作为挂起）
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.
这些通知在特定应用程序服务器的状态发生变化时从SGP发送到ASP。该值反映应用程序服务器的新状态。
If the Status Type is "Other", then the following Status Information values are defined:
如果状态类型为“其他”，则定义以下状态信息值：
1 Insufficient ASP resources active in AS 2 Alternate ASP Active 3 ASP failure
1活动的ASP资源不足，如2备用ASP活动3 ASP失败
These notifications are not based on the SGP reporting the state change of an ASP or AS. In the Insufficient ASP Resources case, the SGP is indicating to an "Inactive" ASP(s) in the AS that another ASP is required to handle the load of the AS (Loadsharing mode or Broadcast mode). For the Alternate ASP Active case, an ASP is informed when an alternate ASP transitions to the ASP-Active state in Override mode.
这些通知不是基于报告ASP或AS状态更改的SGP。在ASP资源不足的情况下，SGP向AS中的“非活动”ASP指示需要另一个ASP来处理AS的负载（负载共享模式或广播模式）。对于备用ASP活动情况，当备用ASP在覆盖模式下转换为ASP活动状态时，会通知ASP。
Parameter ID 0x000E is not used in SUA.
SUA中未使用参数ID 0x000E。
Parameter ID 0x000F is not used in SUA.
SUA中未使用参数ID 0x000F。
Parameter ID 0x0010 is not used in SUA.
参数ID 0x0010未在SUA中使用。
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 = 0x0011 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ASP 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 = 0x0011 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ASP Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
ASP Identifier field: 32-bits (unsigned integer)
ASP标识符字段：32位（无符号整数）
The ASP Identifier field contains 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.7.2).
ASP标识符字段包含一个唯一值，该值在支持AS的ASP中具有本地意义。SGP应保存ASP标识符，以便在必要时与Notify消息一起使用（参见第3.7.2节）。
The Affected Point Code Destinations parameter contains a list of Affected Point Code fields, each a three-octet parameter to allow for 14-, 16- and 24-bit binary formatted SS7 Point Codes. Affected Point Codes that are less than 24-bits are padded on the left to the 24-bit boundary.
“受影响点代码目的地”参数包含受影响点代码字段的列表，每个字段都有一个三个八位组的参数，以允许使用14、16和24位二进制格式的SS7点代码。小于24位的受影响点代码填充在24位边界的左侧。
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 = 0x0012 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mask | Affected PC 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ . . . /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 = 0x0012 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mask | Affected PC 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ . . . /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The encoding is shown below for ANSI and ITU Point Code examples.
ANSI和ITU点代码示例的编码如下所示。
ANSI 24-bit Point Code:
ANSI 24位点代码：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mask | Network | Cluster | Member |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|MSB-----------------------------------------LSB|
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mask | Network | Cluster | Member |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|MSB-----------------------------------------LSB|
ITU 14-bit Point Code:
ITU 14位点代码：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mask |0 0 0 0 0 0 0 0 0 0|Zone | Region | SP |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|MSB--------------------LSB|
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mask |0 0 0 0 0 0 0 0 0 0|Zone | Region | SP |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|MSB--------------------LSB|
It is OPTIONAL for an implementation to generate an Affected Point Code parameter with more than on Affected PC but the implementation MUST accept and process an Affected Point Code parameter with more than one Affected PC.
实现可以选择在受影响的PC上生成多个受影响的点代码参数，但实现必须在多个受影响的PC上接受并处理受影响的点代码参数。
Mask: 8-bits
掩码：8位
The Mask parameter can be used to identify a contiguous range of Affected Destination Point Codes, independent of the point code format. Identifying a contiguous range of Affected PCs may be useful when reception of an MTP3 management message or a linkset event simultaneously affects the availability status of a series of destinations at an SG.
掩码参数可用于识别受影响的目标点代码的连续范围，与点代码格式无关。当接收MTP3管理消息或链路集事件同时影响SG处一系列目的地的可用性状态时，识别受影响PC的连续范围可能有用。
The Mask parameter is an integer representing a bit mask that can be applied to the related Affected PC field. The bit mask identifies how many bits of the Affected PC field are significant and which are effectively "wild-carded". For example, a mask of "8" indicates that the last eight bits of the PC is "wild-carded". For an ANSI 24-bit Affected PC, this is equivalent to signalling that all PCs in an ANSI Cluster are unavailable. A mask of "3" indicates that the last three bits of the PC is "wild-carded". For a 14-bit ITU Affected PC, this is equivalent to signalling that an ITU Region is unavailable.
掩码参数是一个整数，表示可应用于相关受影响PC字段的位掩码。位掩码标识受影响PC字段中有多少位是有效的，哪些位是有效的“通配符”。例如，掩码为“8”表示PC的最后八位为“通配符”。对于受ANSI 24位影响的PC，这相当于发出ANSI集群中所有PC均不可用的信号。掩码为“3”表示电脑的最后三位为“通配符”。对于受ITU影响的14位PC，这相当于发出ITU区域不可用的信号。
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 = 0x0013 | 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 = 0x0013 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Correlation ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Correlation ID is a 32-bit identifier that is attached to CLDT messages to indicate to a newly entering ASP in a Broadcast AS where in the traffic flow of CLDT messages the ASP is joining. It is attached to the first CLDT message sent to an ASP by an SG after sending an ASP Active Ack or otherwise starting traffic to an ASP. The Correlation ID is only significant within a Routing Context.
相关ID是附加到CLDT消息的32位标识符，用于向广播中新进入的ASP指示ASP在CLDT消息的通信流中加入的位置。在向ASP发送ASP活动Ack或以其他方式启动流量后，它附加到SG发送给ASP的第一条CLDT消息。相关性ID仅在路由上下文中有效。
Implementation note: Correlation ID parameter can be used for features like Synchronisation of ASPs/SGPs in a Broadcast Mode AS/SG; avoid message duplication and mis-sequencing in case of failover of association from one ASP/SGP to other ASP/SGP etc.
实施说明：相关ID参数可用于诸如在广播模式AS/SG中同步ASP/SGP等功能；避免在关联从一个ASP/SGP故障切换到另一个ASP/SGP等时出现消息重复和错误排序。
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 = 0x0018 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Routing Key Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0016 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Registration Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Routing Context |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 = 0x0018 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Routing Key Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0016 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Registration Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Routing Context |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Routing Key Identifier contains the same TLV formatted parameter value as found in the matching Routing Key parameter in the REG REQ message.
路由密钥标识符包含与REG REQ消息中匹配的路由密钥参数相同的TLV格式参数值。
Routing Context contains the same TLV formatted Routing Context parameter for the associated Routing Key if the registration was successful. It is set to "0" if the registration was not successful.
如果注册成功，则路由上下文包含关联路由密钥的相同TLV格式的路由上下文参数。如果注册未成功，则将其设置为“0”。
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 = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Routing Context |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0017 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Deregistration 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 = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Routing Context |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0017 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Deregistration Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Routing Context: 32-bit integer
路由上下文：32位整数
Routing Context contains the Routing Context value of the matching Routing key to deregister, as found in the DEREG REQ message.
路由上下文包含要注销的匹配路由密钥的路由上下文值，如在DEREG REQ消息中找到的。
Deregistration Status: 32-bit integer
注销状态：32位整数
Deregistration Status parameter indicates the success or the reason for failure of the deregistration.
注销状态参数表示注销成功或失败的原因。
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 = 0x0016 | 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 = 0x0016 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Registration Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Registration Status: 32-bits (unsigned integer)
注册状态：32位（无符号整数）
The Registration Status field indicates the success or the reason for failure of a registration request.
注册状态字段表示注册请求成功或失败的原因。
Its values may be: 0 Successfully Registered 1 Error - Unknown 2 Error - Invalid Destination Address 3 Error - Invalid Network Appearance 4 Error - Invalid Routing Key 5 Error - Permission Denied 6 Error - Cannot Support Unique Routing 7 Error - Routing Key not Currently Provisioned
其值可能为：0成功注册1错误-未知2错误-无效目标地址3错误-无效网络外观4错误-无效路由密钥5错误-权限被拒绝6错误-无法支持唯一路由7错误-当前未设置路由密钥
8 Error - Insufficient Resources 9 Error - Unsupported RK parameter Field 10 Error - Unsupported/Invalid Traffic Mode Type 11 Error - Routing Key Change Refused
8错误-资源不足9错误-不支持的RK参数字段10错误-不支持/无效的通信模式类型11错误-路由密钥更改被拒绝
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 = 0x0017 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Deregistration 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 = 0x0017 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Deregistration Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Deregistration Status: 32-bit integer
注销状态：32位整数
The Deregistration Result Status field indicates the success or the reason for failure of the deregistration.
注销结果状态字段指示注销成功或失败的原因。
Its values may be:
其值可能是：
0 Successfully Deregistered 1 Error - Unknown 2 Error - Invalid Routing Context 3 Error - Permission Denied 4 Error - Not Registered 5 Error - ASP Currently Active for Routing Context
0已成功取消注册1错误-未知2错误-路由上下文无效3错误-权限被拒绝4错误-未注册5错误-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 = 0x0018 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local Routing Key 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 = 0x0018 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local Routing Key Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Local Routing Key Identifier field is a 32-bits unsigned integer. 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 message is received.
本地路由密钥标识符字段是32位无符号整数。标识符值由ASP分配，用于将REG RSP消息中的响应与原始注册请求关联。在收到REG RSP消息之前，标识符值必须保持唯一。
These TLV parameters are specific to the SUA protocol.
这些TLV参数特定于SUA协议。
Parameter Name Parameter ID
============== ============
SS7 Hop Counter 0x0101
Source Address 0x0102
Destination Address 0x0103
Source Reference Number 0x0104
Destination Reference Number 0x0105
SCCP Cause 0x0106
Sequence Number 0x0107
Receive Sequence Number 0x0108
ASP Capabilities 0x0109
Credit 0x010A
Data 0x010B
User/Cause 0x010C
Network Appearance 0x010D
Routing Key 0x010E
DRN Label 0x010F
TID Label 0x0110
Address Range 0x0111
SMI 0x0112
Importance 0x0113
Message Priority 0x0114
Protocol Class 0x0115
Sequence Control 0x0116
Segmentation 0x0117
Congestion Level 0x0118
Parameter Name Parameter ID
============== ============
SS7 Hop Counter 0x0101
Source Address 0x0102
Destination Address 0x0103
Source Reference Number 0x0104
Destination Reference Number 0x0105
SCCP Cause 0x0106
Sequence Number 0x0107
Receive Sequence Number 0x0108
ASP Capabilities 0x0109
Credit 0x010A
Data 0x010B
User/Cause 0x010C
Network Appearance 0x010D
Routing Key 0x010E
DRN Label 0x010F
TID Label 0x0110
Address Range 0x0111
SMI 0x0112
Importance 0x0113
Message Priority 0x0114
Protocol Class 0x0115
Sequence Control 0x0116
Segmentation 0x0117
Congestion Level 0x0118
Destination/Source Address Sub-Parameters
===========================================
Global Title 0x8001
Point Code 0x8002
Subsystem Number 0x8003
IPv4 Address 0x8004
Hostname 0x8005
IPv6 Addresses 0x8006
Destination/Source Address Sub-Parameters
===========================================
Global Title 0x8001
Point Code 0x8002
Subsystem Number 0x8003
IPv4 Address 0x8004
Hostname 0x8005
IPv6 Addresses 0x8006
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 = 0x0101 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | SS7 Hop Count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0101 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | SS7 Hop Count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
SS7 Hop Counter (3.18/Q.713)
SS7跃点计数器（3.18/Q.713）
The value of the SS7 Hop Counter is decremented with each global title translation and is in the range 15 to 1.
SS7跃点计数器的值随着每次全局标题转换而递减，并且在15到1的范围内。
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 = 0x0102 | Parameter Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Routing Indicator | Address Indicator |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Address parameter(s) /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0102 | Parameter Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Routing Indicator | Address Indicator |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Address parameter(s) /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The following combinations of address parameters are valid:
以下地址参数组合有效：
- Global Title (e.g., E.164 number) + optional PC and/or SSN, SSN may be zero, when routing is done on Global Title
- 全局标题（例如，e.164编号）+可选PC和/或SSN，当路由在全局标题上完成时，SSN可能为零
- SSN (non-zero) + optional PC and/or Global Title, when routing is done on PC + SSN. The PC is mandatory in the source address when sending from SGP to ASP, and in the destination address when sending from ASP to SGP to reach the SS7 SEP.
- 在PC+SSN上完成路由时，SSN（非零）+可选PC和/或全局标题。从SGP发送到ASP时，PC必须位于源地址，从ASP发送到SGP时，PC必须位于目标地址，才能到达SS7 SEP。
- Hostname + optional SSN, when routing is done by Hostname
- 当路由由主机名完成时，主机名+可选SSN
- SSN (non-zero) and optional IP address (IPv4 or IPv6) when routing is done on IP address + SSN
- 在IP地址+SSN上进行路由时，SSN（非零）和可选IP地址（IPv4或IPv6）
The following values are valid for the routing indicator:
以下值对路由指示符有效：
Reserved 0 Route on Global Title 1 Route on SSN + PC 2 Route on Hostname 3 Route on SSN + IP Address 4
全局标题上保留的0路由SSN+PC上的1路由主机名上的2路由SSN+IP地址上的3路由4
The routing indicator determines which address parameters need to be present in the address parameters field.
路由指示符确定哪些地址参数需要出现在地址参数字段中。
This parameter is needed for interworking with SS7 networks. The address indicator specifies what address parameters are actually received in the SCCP address from the SS7 network, or are to be populated in the SCCP address when the message is sent into the SS7 network. The value of the routing indicator needs to be taken into account. It is used in the ASP to SG direction. For example, the PC parameter is present in the destination address of the CLDT sent from ASP->SG, but bit 2 is set to "0" meaning "do not populate this in the SCCP called party address". The effect is that the SG only uses the PC to populate the MTP routing label DPC field, but does not include it in the SCCP called party address.
与SS7网络互通需要此参数。地址指示符指定从SS7网络的SCCP地址中实际接收到的地址参数，或在将消息发送到SS7网络时将在SCCP地址中填充的地址参数。需要考虑路由指示符的值。它用于ASP到SG方向。例如，PC参数存在于从ASP->SG发送的CLDT的目标地址中，但位2被设置为“0”，表示“不要将其填充到SCCP的被叫方地址中”。其效果是，SG仅使用PC填充MTP路由标签DPC字段，但不将其包含在SCCP中，称为参与方地址。
In the SG->ASP direction, the source address PC parameter is present (PC of SS7 SEP). However, this may have been populated from the OPC in the received MTP routing label, not from the PC field in the SCCP calling party address. In this case, bit 2 = "0" denotes that. The AI gives further instructions to the SG how and when to populate the SCCP addresses; in the SG->ASP direction, the AI gives information to the ASP as to what was actually present in the received SCCP addresses.
在SG->ASP方向，源地址PC参数存在（SS7 SEP的PC）。但是，这可能是从接收到的MTP路由标签中的OPC填充的，而不是从SCCP呼叫方地址中的PC字段填充的。在这种情况下，位2=“0”表示。AI向SG进一步指示如何以及何时填充SCCP地址；在SG->ASP方向，AI向ASP提供有关接收到的SCCP地址中实际存在的内容的信息。
The address indicator is coded as follows:
地址指示器编码如下：
Bit 1 is used to indicate inclusion of the SSN
位1用于指示包含SSN
0 Do not include SSN when optional 1 Include SSN
当可选1包含SSN时，0不包含SSN
Bit 2 is used to indicate inclusion of the PC
位2用于指示包含PC
0 Do not include PC, regardless of the routing indicator value 1 Include PC
0不包括PC，无论路由指示符值为多少1包括PC
Bit 3 is used to indicate inclusion of the Global Title
位3用于表示包含全局标题
0 Do not include GT when optional (routing indicator /= 1) 1 Include GT
可选时0不包括GT（路由指示符/=1）1包括GT
The remaining bits are spare and SHOULD be coded zero, and MUST be ignored by the receiver.
剩余的位是备用位，应编码为零，并且必须被接收器忽略。
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 = 0x8001 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | GTI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| No. Digits | Trans. type | Num. Plan | Nature of Add |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Global Title Digits /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 = 0x8001 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | GTI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| No. Digits | Trans. type | Num. Plan | Nature of Add |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Global Title Digits /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Number of Digits:
位数：
This is the number of digits contained in the Global Title.
这是全局标题中包含的位数。
GTI (Global Title Indicator, defined in chapter 3.4.2.3 of Q.713).
GTI（全球所有权指标，定义见Q.713第3.4.2.3章）。
0000 Invalid 0001 Nature of Address is taken over. It is implicitly assumed that the Translation Type = Unknown and Numbering Plan = E.164 (value 1). 0010 This is most commonly used in North American networks. The Translation Type implicitly determines Nature of Address and Numbering Plan. This data can be configured in the SG. The number of digits is always even and determined by the SCCP address length. 0011 Numbering Plan and Translation Type are taken over. It is implicitly assumed that the Nature of Address = Unknown. 0100 This format is used in international networks and most commonly in networks outside North America. All information to populate the source address is present in the SCCP Address.
0000无效0001地址的性质已被接管。隐式假设翻译类型=未知，编号计划=E.164（值1）。0010这是北美网络中最常用的。翻译类型隐式决定地址和编号计划的性质。该数据可在SG中配置。位数始终为偶数，并由SCCP地址长度决定。0011接管编号计划和翻译类型。隐式假设地址的性质=未知。0100此格式用于国际网络，最常用于北美以外的网络。用于填充源地址的所有信息都存在于SCCP地址中。
Translation type:
翻译类型：
0 Unknown 1 - 63 International services 64 - 127 Spare 128 - 254 National network specific 255 Reserved
0未知1-63国际服务64-127备用128-254国家网络特定255保留
Numbering Plan:
编号计划：
0 unknown 1 ISDN/telephony numbering plan (Recommendations E.163 and E.164) 2 generic numbering plan 3 data numbering plan (Recommendation X.121) 4 telex numbering plan (Recommendation F.69) 5 maritime mobile numbering plan (Recommendations E.210, E.211) 6 land mobile numbering plan (Recommendation E.212) 7 ISDN/mobile numbering plan (Recommendation E.214) 8 - 13 spare 14 private network or network-specific numbering plan 15 - 126 spare 127 reserved.
0未知1 ISDN/电话编号计划（建议E.163和E.164）2通用编号计划3数据编号计划（建议X.121）4电传编号计划（建议F.69）5海上移动编号计划（建议E.210和E.211）6陆地移动编号计划（建议E.212）7 ISDN/移动编号计划（建议E.214）8-13备用14专用网络或网络特定编号计划15-126备用127保留。
Nature of Address:
地址的性质：
0 unknown 1 subscriber number 2 reserved for national use 3 national significant number 4 international number 5 - 255 Spare
0未知1用户号码2保留供国家使用3国家有效号码4国际号码5-255备用
Global Title:
全球标题：
Octets contain a number of address signals and possibly filler as shown:
八位字节包含许多地址信号，可能还有填充符，如图所示：
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|2 addr.|1 addr.|4 addr.|3 addr.|6 addr.|5 addr.|8 addr.|7 addr.|
| sig. | sig. | sig. | sig. | sig. | sig. | sig. | sig. |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ............. |filler |N addr.| filler |
| |if req | sig. | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|2 addr.|1 addr.|4 addr.|3 addr.|6 addr.|5 addr.|8 addr.|7 addr.|
| sig. | sig. | sig. | sig. | sig. | sig. | sig. | sig. |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ............. |filler |N addr.| filler |
| |if req | sig. | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
All filler bits SHOULD be set to 0.
所有填充位应设置为0。
Address signals to be coded as defined in ITU-T Q.713 Section 3.4.2.3.1.
按照ITU-T Q.713第3.4.2.3.1节的规定对地址信号进行编码。
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 = 0x8002 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Point Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 = 0x8002 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Point Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
See chapter 3.9.18 Affected Point Code for the layout of the Point Code field.
有关点代码字段的布局，请参见第3.9.18章受影响点代码。
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 = 0x8003 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | SSN 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 = 0x8003 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | SSN value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The internationally standardized SSN values are described in chapter 3.4.2.2 of Q.713.
Q.713第3.4.2.2章描述了国际标准化SSN值。
The IP address formats can use different tags. It should be noted that if the source address is in a certain IP version, the destination address should also be in the same IP version.
IP地址格式可以使用不同的标记。应该注意的是，如果源地址在某个IP版本中，那么目标地址也应该在同一个IP版本中。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x8004/0x8006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ IPv4 or IPv6 Address /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 = 0x8004/0x8006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ IPv4 or IPv6 Address /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Note: The tag value 0x8004 is for an IPv4 address and 0x8006 is for IPv6.
注意：标记值0x8004表示IPv4地址，0x8006表示IPv6地址。
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 = 0x8005 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Host Name /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x8005 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Host Name /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Host Name: variable length
主机名：可变长度
This field contains a host name in "host name syntax" per RFC 1123 Section 2.1 [1123]. The method for resolving the host name is out of scope for this document.
根据RFC 1123第2.1节[1123]，此字段包含“主机名语法”中的主机名。解析主机名的方法超出了此文档的范围。
Note: At least one null terminator is included in the Host Name string and must be included in the 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0103 | Parameter Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Routing Indicator | Address Indicator |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Address Parameter(s) /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0103 | Parameter Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Routing Indicator | Address Indicator |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Address Parameter(s) /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format of this parameter is identical to the Source Address parameter.
此参数的格式与源地址参数相同。
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 = 0x0104 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source Reference 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 = 0x0104 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source Reference Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The source reference number is a 4 octet long integer. This is allocated by the source SUA instance.
源参考号是一个4个八位组长的整数。这是由源SUA实例分配的。
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 = 0x0105 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination Reference 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 = 0x0105 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination Reference Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The destination reference number is a 4 octet long integer. This is allocated by the destination SUA instance.
目标参考号是一个4个八位字节长的整数。这是由目标SUA实例分配的。
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 = 0x0106 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | Cause Type | Cause 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 = 0x0106 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | Cause Type | Cause Value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
This parameter bundles the SCCP parameters Release cause, Return cause, Reset cause, Error cause and Refusal cause.
此参数捆绑SCCP参数释放原因、返回原因、重置原因、错误原因和拒绝原因。
Cause Type can have the following values:
原因类型可以具有以下值：
Return Cause 0x1 Refusal Cause 0x2 Release Cause 0x3 Reset Cause 0x4 Error Cause 0x5
返回原因0x1拒绝原因0x2释放原因0x3重置原因0x4错误原因0x5
Cause Value contains the specific cause value. Below gives examples for ITU SCCP values. ANSI references can be found in ANSI T1.112.3
原因值包含特定的原因值。下面给出了ITU SCCP值的示例。ANSI参考可在ANSI T1.112.3中找到
Cause value in Correspondence with Reference
SUA message SCCP parameter
------------------ ----------------- ---------
CLDR Return Cause ITU-T Q.713 Chap 3.12
COREF Refusal Cause ITU-T Q.713 Chap 3.15
RELRE Release Cause ITU-T Q.713 Chap 3.11
RESRE Reset Cause ITU-T Q.713 Chap 3.13
ERR Error Cause ITU-T Q.713 Chap 3.14
Cause value in Correspondence with Reference
SUA message SCCP parameter
------------------ ----------------- ---------
CLDR Return Cause ITU-T Q.713 Chap 3.12
COREF Refusal Cause ITU-T Q.713 Chap 3.15
RELRE Release Cause ITU-T Q.713 Chap 3.11
RESRE Reset Cause ITU-T Q.713 Chap 3.13
ERR Error Cause ITU-T Q.713 Chap 3.14
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 = 0x0107 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | Rec Seq Num|M| Sent Seq Num |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 = 0x0107 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | Rec Seq Num|M| Sent Seq Num |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
This parameter is used to indicate whether "more" data will follow in subsequent CODT messages, and/or to number each CODT message sequentially for the purpose of flow control. It contains the received as well as the sent sequence number, P(R) and P(S) in Q.713, chapters 3.7 and 3.9.
该参数用于指示后续CODT消息中是否会出现“更多”数据，和/或为流量控制目的，按顺序对每个CODT消息进行编号。它包含Q.713第3.7和3.9章中的接收和发送序列号P（R）和P（S）。
As such it can also be used to acknowledge the receipt of data transfers from the peer in case of protocol class 3.
因此，在协议类别3的情况下，它还可用于确认从对等方接收数据传输。
Sent Sequence Number is one octet and is coded as follows:
发送序列号为一个八位字节，编码如下：
Bits 2-8 are used to indicate the Send Sequence Number P(S). Bit 1 (LSB) of octet 1 is spare.
位2-8用于指示发送序列号P（S）。八位组1的第1位（LSB）是备用的。
Received Sequence Number is one octet, and is coded as follows:
接收序列号为一个八位字节，编码如下：
Bits 2-8 are used to indicate the Received Sequence Number P(R). Bit 1 (LSB) is used for the more data indication, as follows:
位2-8用于指示接收序列号P（R）。位1（LSB）用于更多数据指示，如下所示：
0 no more data 1 more data
0没有更多数据1更多数据
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 = 0x0108 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | Rec Seq Num |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 = 0x0108 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | Rec Seq Num |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
This parameter is used exclusively for protocol class 3 in the data acknowledgement message to indicate the lower edge of the receiving window. See Q.713, chapter 3.9.
此参数专门用于数据确认消息中的协议类别3，以指示接收窗口的下边缘。见Q.713，第3.9章。
It is a 1 octet long integer coded as follows:
它是一个1个八位组长的整数，编码如下：
Bits 8-2 are used to indicate the Received Sequence Number P(R).
位8-2用于指示接收序列号P（R）。
Bit 1 is spare.
第1位是备用的。
This parameter is used so that the ASP can report its capabilities regarding SUA for supporting different protocol classes and interworking scenarios.
使用此参数，ASP可以报告其有关SUA的功能，以支持不同的协议类和互通场景。
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 = 0x0109 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved |0 0 0 0|a|b|c|d| Interworking |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 = 0x0109 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved |0 0 0 0|a|b|c|d| Interworking |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Flags
旗帜
a - Protocol Class 3 b - Protocol Class 2 c - Protocol Class 1 d - Protocol Class 0
a-协议类别3 b-协议类别2 c-协议类别1 d-协议类别0
It is mandatory to support at least Protocol Class 0.
必须至少支持协议类0。
Interworking
互通
Values
价值观
0x0 indicates no interworking with SS7 Networks. 0x1 indicates IP Signalling Endpoint (ASP), interworking with SS7 networks. 0x2 indicates Signalling Gateway. 0x3 indicates relay node support.
0x0表示不与SS7网络互通。0x1表示IP信令端点（ASP），与SS7网络互通。0x2表示信令网关。0x3表示中继节点支持。
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 = 0x010A | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | Credit |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 = 0x010A | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | Credit |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The length of the credit field is one octet. See ITU-T Q.713 Chapter 3.10. The parameter is used for protocol class 3 exclusively.
信用字段的长度为一个八位字节。参见ITU-T Q.713第3.10章。该参数专门用于协议类3。
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 = 0x010b | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ 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 = 0x010b | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Data /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Data parameter field contains the SS7 SCCP-User application message, for example an INAP/TCAP message.
数据参数字段包含SS7 SCCP用户应用程序消息，例如INAP/TCAP消息。
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 = 0x010c | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Cause | User |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 = 0x010c | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Cause | User |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
"User" is coded to that SCCP's SI value. There may be several SCCP's at a given point code, each with different SI values, although normally there is only one with SI = 3.
“用户”编码为该SCCP的SI值。在给定点代码处可能有多个SCCP，每个SCCP具有不同的SI值，尽管通常只有一个SCCP的SI=3。
Cause may take the following values
原因可能采用以下值
0 remote SCCP unavailable, reason unknown;
1 remote SCCP unequipped;
2 remote SCCP inaccessible;
0 remote SCCP unavailable, reason unknown;
1 remote SCCP unequipped;
2 remote SCCP inaccessible;
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 = 0x010D | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Network Appearance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 = 0x010D | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Network Appearance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Network Appearance field: 32-bits (unsigned integer)
网络外观字段：32位（无符号整数）
The Network Appearance field identifies the SS7 network context for the Routing Key. The Network Appearance value is of local significance only, coordinated between the SG and ASP. Therefore, in the case where the ASP is connected to more than one SG, the same SS7 Network context may be identified by different Network Appearance values depending upon to which SG the ASP is registering.
网络外观字段标识路由密钥的SS7网络上下文。网络外观值仅具有本地意义，由SG和ASP协调。因此，在ASP连接到多个SG的情况下，根据ASP注册到哪个SG，相同的SS7网络上下文可以通过不同的网络外观值来识别。
In the Routing Key, the Network Appearance identifies the SS7 Point Code and Global Title Translation Type format used, and the SCCP and possibly the SCCP-User protocol (type, variant and version) used within the specific SS7 network.
在路由密钥中，网络外观标识使用的SS7点代码和全局标题转换类型格式，以及特定SS7网络中使用的SCCP和可能的SCCP用户协议（类型、变体和版本）。
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 = 0x010E | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0018 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local Routing Key Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ Key parameter(s) \
/ /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x010E | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0018 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local Routing Key Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ Key parameter(s) \
/ /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Local Routing Key Identifier field: 32-bits (unsigned integer)
本地路由密钥标识符字段：32位（无符号整数）
Key field: variable
关键字字段：变量
The Key field contains the following parameters:
“键”字段包含以下参数：
Parameter Traffic Mode Type Optional Network Appearance Optional *1 Source Address Optional Destination Address Optional Address Range Optional
参数流量模式类型可选网络外观可选*1源地址可选目标地址可选地址范围可选
Note 1: The Network Appearance parameter must be included in the Routing Key when the ASP is able to register in multiple SS7 Network contexts.
注1：当ASP能够在多个SS7网络上下文中注册时，网络外观参数必须包含在路由密钥中。
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 = 0x010F | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| start | end | label value |
+---------------+---------------+-------------------------------+
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 = 0x010F | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| start | end | label value |
+---------------+---------------+-------------------------------+
The Start parameter is the start position of label, between 0 (LSB) and 23 (MSB).
Start参数是标签的起始位置，介于0（LSB）和23（MSB）之间。
The End parameter is the end position of label, between 0 (LSB) and 23 (MSB).
End参数是标签的结束位置，介于0（LSB）和23（MSB）之间。
Label value is a 16-bit integer, which is unique across an AS.
标签值是16位整数，在AS中是唯一的。
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 = 0x0110 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| start | end | label value |
+---------------+---------------+-------------------------------+
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 = 0x0110 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| start | end | label value |
+---------------+---------------+-------------------------------+
The Start parameter is the start position of label, between 0 (LSB) and 31 (MSB).
Start参数是标签的起始位置，介于0（LSB）和31（MSB）之间。
The End parameter is the end position of label, between 0 (LSB) and 31 (MSB).
End参数是标签的结束位置，介于0（LSB）和31（MSB）之间。
Label value is a 16-bit integer, which is unique across an AS.
标签值是16位整数，在AS中是唯一的。
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 = 0x0111 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ Address parameter(s) \
/ /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0111 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ Address parameter(s) \
/ /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Address field:
地址字段：
The Address field the following parameters:
地址字段包含以下参数：
Parameter Source Address Optional *1 Destination Address Optional *1
参数源地址可选*1目标地址可选*1
Note 1: The Address field must contain pairs of Source Addresses or pairs of Destination Addresses but MUST NOT mix Source Addresses with Destination Addresses in the same Address field.
注1：地址字段必须包含源地址对或目标地址对，但不得在同一地址字段中混合源地址和目标地址。
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 = 0x0112 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | SMI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 = 0x0112 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | SMI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Subsystem Multiplicity Indicator (SMI) can have the following values:
子系统多重性指示器（SMI）可以具有以下值：
0x00 Reserved/Unknown 0x01 Solitary 0x02 Duplicated 0x03 Triplicated 0x04 Quadruplicated 0xff Unspecified
0x00保留/未知0x01单独0x02重复0x03三份0x04四份0xff未指定
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 = 0x0113 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | Importance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 = 0x0113 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | Importance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Importance (3.19/Q.713)
重要性（3.19/Q.713）
Possible values of the Importance Parameter are between 0 and 7, where the value of 0 indicates the least important and 7 indicates the most important.
重要性参数的可能值介于0和7之间，其中0表示最不重要，7表示最重要。
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 = 0x0114 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | Msg Priority |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 = 0x0114 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | Msg Priority |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Priority
优先事项
Priority value ranges from 0 to 3. If the Priority value has not been specified by the SCCP user, it should be set to 0xFF. The SG MAY take the priority into account for determining the MTP message priority. In the all-IP case, this parameter MAY be used.
优先级值的范围为0到3。如果SCCP用户未指定优先级值，则应将其设置为0xFF。SG可以考虑优先级以确定MTP消息优先级。在全IP情况下，可以使用此参数。
The Message Priority parameter is optional in the CLDT, CLDR, CORE, COAK and CODT messages. However, for networks, which support Message Priority (e.g., ANSI), this parameter MUST be included but it is not required for those which don't (e.g., International).
在CLDT、CLDR、CORE、COAK和CODT消息中，消息优先级参数是可选的。但是，对于支持消息优先级（例如ANSI）的网络，必须包含此参数，但不支持此参数的网络（例如国际网络）不需要此参数。
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 = 0x0115 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | Protocol Cl. |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 = 0x0115 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | Protocol Cl. |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Protocol class (3.6/Q.713)
协议等级（3.6/Q.713）
Bits 1-2 indicate the protocol class.
位1-2表示协议类别。
Value Description 0 Class 0 (connectionless service) 1 Class 1 (connectionless service) 2 Class 2 (connection-oriented service) 3 Class 3 (connection-oriented service)
值说明0类0（无连接服务）1类1（无连接服务）2类2（面向连接服务）3类3（面向连接服务）
Bit 8 indicates the use of the return on error procedure.
位8表示错误返回程序的使用。
Value Description 0x0 No special options 0x1 Return message on error
值说明0x0无特殊选项0x1错误时返回消息
Bits 3-7 are spare and SHOULD be coded zero, and MUST be ignored by the receiver.
位3-7是备用的，应编码为零，并且必须被接收器忽略。
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 = 0x0116 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Control |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 = 0x0116 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Control |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Sequence Control (6.2.2.2.2/Q.711)
顺序控制（6.2.2.2.2/Q.711）
The field is coded with the value of the sequence control parameter associated with a group of messages and are chosen so as to ensure proper loadsharing of message groups over SLS values while ensuring that sequence control values within message groups have the sequence control value coded with the same value as the initial message of the message group.
该字段用与一组消息相关联的顺序控制参数的值进行编码，并进行选择，以确保消息组在SLS值上的正确负载共享，同时确保消息组内的顺序控制值的编码值与消息的初始消息的值相同组
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 = 0x0117 | Length = 32 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| first/remain | Segmentation Reference |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 = 0x0117 | Length = 32 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| first/remain | Segmentation Reference |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The first/remaining segments field is formatted as follows: bit 8
(MSB): indicates whether this is the first segment (1) or not (0)
The first/remaining segments field is formatted as follows: bit 8
(MSB): indicates whether this is the first segment (1) or not (0)
bits 1-7: indicate the number of remaining segments, value between 0 and 15
位1-7：表示剩余段的数量，值介于0和15之间
The field would thus be coded 1000 0000 (first, no remaining segments) for a unsegmented CLDT.
因此，对于未分段的CLDT，该字段将被编码为1000 0000（首先，没有剩余的段）。
The segmentation reference field is a 3 byte integer, assigned by the ASP.
分段参考字段是一个3字节的整数，由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 = 0x0118 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Congestion Level |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 = 0x0118 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Congestion Level |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Congestion Level field: 8-bits (unsigned integer)
拥塞级别字段：8位（无符号整数）
The Congestion Level field contains the level at which congestion has occurred.
拥塞级别字段包含发生拥塞的级别。
When the Congestion Level parameter is included in a SCON message that corresponds to an N-PCSTATE primitive, the Congestion Level field indicates the MTP congestion level experienced by the local or affected signalling point as indicated by the Affected Point Code(s) also in the SCON message. In this case, valid values for the Congestion Level field are as follows:
当拥塞级别参数包含在对应于N-PCSTATE原语的SCON消息中时，拥塞级别字段表示本地或受影响信令点经历的MTP拥塞级别，如SCON消息中受影响点代码所示。在这种情况下，拥塞级别字段的有效值如下所示：
0 No Congestion or Undefined 1 Congestion Level 1 2 Congestion Level 2 3 Congestion Level 3
0无拥塞或未定义1拥塞级别1 2拥塞级别2 3拥塞级别3
When the Congestion Level parameter is included in a SCON message that corresponds to an N-STATE primitive, the Congestion Level field indicates the SCCP restricted importance level experienced by the local or affected subsystem as indicated by the Affected Point Code and Subsystem Number also in the SCON message. In this case, valid values for the Congestion Level field range from 0 to 7, where 0 indicates the least congested and 7 indicates the most congested subsystem.
当拥塞级别参数包含在对应于N状态原语的SCON消息中时，拥塞级别字段表示本地或受影响子系统经历的SCCP受限重要性级别，如SCON消息中受影响的点代码和子系统编号所示。在这种情况下，拥塞级别字段的有效值范围为0到7，其中0表示最小拥塞，7表示最拥塞的子系统。
The SUA layer needs to respond to various local primitives it receives from other layers as well as the messages that it receives from the peer SUA layer. This section describes the SUA procedures in response to these events.
SUA层需要响应从其他层接收的各种本地原语以及从对等SUA层接收的消息。本节描述了针对这些事件的SUA程序。
When an SCCP Subsystem Management (SCMG) message is received from the SS7 network, the SGP needs to determine whether there are concerned Application Servers interested in subsystem status changes. The SUA management function is informed with the N-State or N-Coord primitive upon which it formats and transfers the applicable SNMM message to the list of concerned ASPs using stream ID "0".
当从SS7网络接收到SCCP子系统管理（SCMG）消息时，SGP需要确定是否有相关的应用服务器对子系统状态更改感兴趣。SUA管理功能通过N-State或N-Coord原语得到通知，根据该原语，它使用流ID“0”格式化适用的SNMM消息并将其传输到相关的ASP列表。
When MTP-3 Management indications are received (MTP-PAUSE, MTP-RESUME, MTP-STATUS), SCCP Subsystem Management determines whether there are concerned local SCCP-users. When these local SCCP-users are in fact Application Servers, serviced by ASPs, SUA management is informed with the N-PCSTATE indication primitive upon which it formats and transfers the applicable SNM message (DUNA, DAVA, DRST or SCON) to the list of concerned ASPs using stream ID "0".
当收到MTP-3管理指示（MTP-PAUSE、MTP-RESUME、MTP-STATUS）时，SCCP子系统管理确定是否有相关的本地SCCP用户。当这些本地SCCP用户实际上是由ASP提供服务的应用服务器时，SUA管理层会收到N-PCSTATE指示原语的通知，根据该原语，SUA管理层使用流ID“0”将适用的SNM消息（DUNA、DAVA、DRST或SCON）格式化并传输到相关ASP的列表中。
The SUA message distribution function determines the Application Server (AS) based on comparing the information in the N-UNITDATA request primitive with a provisioned Routing Key.
SUA消息分发功能基于将N-UNITDATA请求原语中的信息与配置的路由密钥进行比较来确定应用程序服务器（AS）。
From the list of ASPs within the AS table, an ASP in the ASP-ACTIVE state is selected and a DATA message is constructed and issued on the corresponding SCTP association. If more than one ASP is in the ASP-ACTIVE state (i.e., traffic is to be load-shared across more than one ASP), one of the ASPs in the ASP_ACTIVE state is selected from the list. If the ASPs are in Broadcast Mode, all active ASPs will be selected and the message sent to each of the active ASPs. The selection algorithm is implementation dependent but could, for example, be round robin or based on the SLS. The appropriate
从AS表中的ASP列表中，选择处于ASP-ACTIVE状态的ASP，并在相应的SCTP关联上构造和发布数据消息。如果多个ASP处于ASP-ACTIVE状态（即，流量将在多个ASP之间进行负载共享），则会从列表中选择一个处于ASP\U ACTIVE状态的ASP。如果ASP处于广播模式，将选择所有活动的ASP，并将消息发送到每个活动的ASP。选择算法取决于实现，但例如可以是循环或基于SLS。适当的
selection algorithm must be chosen carefully as it is dependent on application assumptions and understanding of the degree of state coordination between the ASP_ACTIVE ASPs in the AS.
必须仔细选择选择算法，因为它取决于应用程序假设和对as中ASP_活动ASP之间状态协调程度的理解。
In addition, the message needs to be sent on the appropriate SCTP stream, again taking care to meet the message sequencing needs of the signalling application. DATA messages MUST be sent on an SCTP stream other than stream '0' when there is more than one stream.
此外，需要在适当的SCTP流上发送消息，再次注意满足信令应用程序的消息排序需求。当存在多个流时，必须在流“0”以外的SCTP流上发送数据消息。
When there is no Routing Key match, or only a partial match, for an incoming SS7 message, a default treatment MAY be specified. Possible solutions are to provide a default Application Server at the SGP that directs all unallocated traffic to a (set of) default ASP(s), or to drop the message and provide a notification to Layer Management in an M-ERROR indication primitive. The treatment of unallocated traffic is implementation dependent.
当传入SS7消息没有路由密钥匹配或只有部分匹配时，可以指定默认处理。可能的解决方案是在SGP上提供一个默认应用程序服务器，将所有未分配的流量定向到（一组）默认ASP，或者删除消息并在M错误指示原语中向层管理提供通知。未分配流量的处理取决于实现。
On receiving primitives from the local Layer Management, the SUA layer will take the requested action and provide an appropriate response primitive to Layer Management.
从本地层管理接收原语后，SUA层将采取请求的操作，并向层管理提供适当的响应原语。
An M-SCTP_ESTABLISH request primitive from Layer Management at an ASP or IPSP will initiate the establishment of an SCTP association. The SUA layer will attempt to establish an SCTP association with the remote SUA peer by sending an SCTP-ASSOCIATE primitive to the local SCTP layer.
来自ASP或IPSP层管理的M-SCTP_建立请求原语将启动SCTP关联的建立。SUA层将通过向本地SCTP层发送SCTP-ASSOCIATE原语，尝试与远程SUA对等方建立SCTP关联。
When an SCTP association has been successfully established, the SCTP will send an SCTP-COMMUNICATION_UP notification primitive to the local SUA layer. At the ASP or IPSP that initiated the request, the SUA layer will send an M-SCTP_ESTABLISH confirm primitive to Layer Management when the association setup is complete. At the peer SUA layer, an M-SCTP_ESTABLISH indication primitive is sent to Layer Management upon successful completion of an incoming SCTP association setup.
成功建立SCTP关联后，SCTP将向本地SUA层发送SCTP-COMMUNICATION_UP通知原语。在发起请求的ASP或IPSP处，当关联设置完成时，SUA层将向层管理发送一个M-SCTP_建立确认原语。在对等SUA层，成功完成传入SCTP关联设置后，M-SCTP_建立指示原语被发送到层管理。
An M-SCTP_RELEASE request primitive from Layer Management initiates the shutdown of an SCTP association. The SUA layer accomplishes a graceful shutdown of the SCTP association by sending an SCTP-SHUTDOWN primitive to the SCTP layer.
来自层管理的M-SCTP_释放请求原语启动SCTP关联的关闭。SUA层通过向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 SUA layer. At the SUA Layer that initiated the request, the SUA layer will send an M-SCTP_RELEASE confirm primitive to Layer Management when the association shutdown
当SCTP关联的正常关闭完成后，SCTP层向本地SUA层返回SCTP-shutdown_COMPLETE通知原语。在发起请求的SUA层，当关联关闭时，SUA层将向层管理发送一个M-SCTP_RELEASE confirm原语
is complete. At the peer SUA Layer, an M-SCTP_RELEASE indication primitive is sent to Layer Management upon abort or successful shutdown of an SCTP association.
完成了。在对等SUA层，在SCTP关联中止或成功关闭时，M-SCTP_释放指示原语被发送到层管理。
An M-SCTP_STATUS request primitive supports a Layer Management query of the local status of a particular SCTP association. The SUA layer simply maps the M-SCTP_STATUS request primitive to an SCTP-STATUS primitive to the SCTP layer. When the SCTP responds, the SUA layer maps the association status information to an M-SCTP_STATUS confirm primitive. No peer protocol is invoked.
M-SCTP_状态请求原语支持对特定SCTP关联的本地状态的层管理查询。SUA层只是将M-SCTP_状态请求原语映射到SCTP层的SCTP-STATUS原语。当SCTP响应时，SUA层将关联状态信息映射到M-SCTP_状态确认原语。没有调用对等协议。
Similar LM-to-SUA-to-SCTP and/or SCTP-to-SUA-to-LM primitive mappings can be described for the various other SCTP Upper Layer primitives in RFC 2960 [2960] 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 primitives (and Status as well) can be considered for modeling purposes as a Layer Management interaction directly with the SCTP Layer.
对于RFC 2960[2960]中的各种其他SCTP上层原语，例如初始化、设置主、更改心跳、请求心跳、获取SRTT报告、设置故障阈值、设置协议参数、销毁SCTP实例、发送故障、，以及网络状态的变化。或者，出于建模目的，这些SCTP上层原语（以及状态）可以被视为直接与SCTP层进行的层管理交互。
M-NOTIFY indication and M-ERROR indication primitives indicate to Layer Management the notification or error information contained in a received SUA Notify or Error message respectively. These indications can also be generated based on local SUA events.
M-NOTIFY指示和M-ERROR指示原语分别向层管理层指示接收到的SUA NOTIFY或ERROR消息中包含的通知或错误信息。也可以根据本地SUA事件生成这些指示。
An M-ASP_STATUS request primitive supports a Layer Management query of the status of a particular local or remote ASP. The SUA layer responds with the status in an M-ASP_STATUS confirm primitive. No SUA peer protocol is invoked. An M-AS_STATUS request supports a Layer Management query of the status of a particular AS. The SUA responds with an M-AS_STATUS confirm primitive. No SUA peer protocol is invoked.
M-ASP_状态请求原语支持对特定本地或远程ASP的状态进行层管理查询。SUA层以M-ASP_状态确认原语中的状态进行响应。未调用任何SUA对等协议。M-AS_状态请求支持对特定AS状态的层管理查询。SUA以M-AS_状态确认原语进行响应。未调用任何SUA对等协议。
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 SUA 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 SUA peer at an SGP or IPSP.
M-ASP_向上请求、M-ASP_向下请求、M-ASP_活动请求和M-ASP_非活动请求原语允许ASP的层管理启动状态更改。成功完成后，SUA逐层管理将提供相应的确认原语。如果调用失败，则在原语中提供错误指示原语。这些请求会将ASP Up、ASP Down、ASP Active和ASP Inactive消息发送到SGP或IPSP上的远程SUA对等方。
Upon successful state changes resulting from reception of ASP Up, ASP Down, ASP Active and ASP Inactive messages from a peer SUA, the SUA layer MAY 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.
当从对等SUA接收到ASP Up、ASP Down、ASP Active和ASP Inactive消息而导致状态成功更改时，SUA层可将相应的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 SUA Notify or Error message. These indications can also be generated based on local SUA events.
M-NOTIFY指示和M-ERROR指示原语向层管理层指示接收到的SUA NOTIFY或ERROR消息中包含的通知或错误信息。也可以根据本地SUA事件生成这些指示。
All non-Transfer and non-SSNM messages, except BEAT and BEAT Ack, SHOULD be sent with sequenced delivery to ensure ordering. All non-Transfer messages, with the exception of ASPTM, BEAT and BEAT Ack messages SHOULD be sent on SCTP stream '0'. ASPTM messages MAY be sent on one of the streams used to carry data traffic related to the Routing Context(s), to minimize possible message loss. BEAT and BEAT Ack messages MAY be sent using out-of-order delivery, and MAY be sent on any stream.
除BEAT和BEAT Ack外，所有非传输和非SSNM消息应按顺序发送，以确保订购。除ASPTM外，所有非传输消息、BEAT和BEAT Ack消息均应在SCTP流“0”上发送。可以在用于承载与路由上下文相关的数据通信的流之一上发送ASPTM消息，以最小化可能的消息丢失。BEAT和BEAT Ack消息可以使用无序交付发送，并且可以在任何流上发送。
The SUA 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 SUA message distribution function. Similarly, where IPSPs use SUA in a point-to-point fashion, the SUA layer in an IPSP maintains the state of remote IPSPs.
SGP上的SUA层维护每个应用程序服务器中每个远程ASP的状态，将ASP配置为接收流量，作为SUA消息分发功能的输入。类似地，当IPSP以点对点的方式使用SUA时，IPSP中的SUA层维护远程IPSP的状态。
Two IPSP models are defined with regards to the number of messages that are needed to a IPSP state change. They are defined as follows:
根据IPSP状态更改所需的消息数量定义了两个IPSP模型。它们的定义如下：
1. IPSP Single Exchange (SE) model. Only a single exchange of ASPTM or ASPSM messages is needed to change the IPSP state. This means that a set of request from one end and acknowledge from the other will be enough.
1. IPSP单一交换（SE）模型。更改IPSP状态只需交换一次ASPTM或ASPSM消息。这意味着一组来自一端的请求和来自另一端的确认就足够了。
2. IPSP Double Exchange (DE) model. Both IPSPs have to send request messages and both IPSPs have to acknowledge the request messages from the other end. This results in a double exchange of ASPTM and ASPSM message, one from each end. This configuration supports dynamic routing key configuration by using RKM messages in the same way as ASP-SGP scenario.
2. IPSP双交换（DE）模型。两个IPSP都必须发送请求消息，并且两个IPSP都必须确认来自另一端的请求消息。这导致ASPTM和ASPSM消息的双重交换，每端一个。此配置通过使用RKM消息支持动态路由密钥配置，方式与ASP-SGP场景相同。
To ensure interoperability, an SUA implementation supporting IPSP communication MUST support IPSP SE model and MAY implement IPSP DE model.
为确保互操作性，支持IPSP通信的SUA实现必须支持IPSP SE模型，并可能实现IPSP DE模型。
In section 4.3.1: ASP/IPSP States, only the SGP-ASP and the IPSP SE scenarios are described. For the IPSP DE model, both IPSPs MUST follow the SGP side of the SGP-ASP procedures.
在第4.3.1节：ASP/IPSP状态中，仅描述了SGP-ASP和IPSP SE场景。对于IPSP DE模型，两个IPSP必须遵循SGP-ASP程序的SGP端。
In section 4.3.2, only the SGP-ASP scenario is described. All of the procedures referring to an AS served by ASPs are also applicable to ASs served by IPSPs.
在第4.3.2节中，仅描述了SGP-ASP场景。所有涉及ASP提供的AS的程序也适用于IPSP提供的ASs。
In section 4.3.3, only the Management procedures for the SGP-ASP scenario are described. The corresponding Management procedures for IPSPs are directly inferred.
在第4.3.3节中，仅描述了SGP-ASP场景的管理程序。直接推断出IPSP的相应管理程序。
The remaining sections contain specific IPSP Considerations subsections.
其余部分包含特定的IPSP注意事项小节。
The state of each remote ASP/IPSP, in each AS that it is configured to operate, is maintained in the peer SUA layer (i.e., in the SGP or peer IPSP, respectively). The state of a particular ASP/IPSP in a particular AS changes due to events. The events include:
每个远程ASP/IPSP在其配置为运行的每个AS中的状态都在对等SUA层（即，分别在SGP或对等IPSP中）中维护。特定ASP/IPSP在特定环境中的状态，由于事件而发生更改。这些活动包括：
* Reception of messages from the peer SUA layer at the ASP/IPSP; * Reception of some messages from the peer SUA layer at other ASPs/IPSPs in the AS (e.g., ASP Active message indicating "Override"); * Reception of indications from the SCTP layer; or * Local Management intervention.
* 从ASP/IPSP的对等SUA层接收消息；*在AS中的其他ASP/IPSP接收来自对等SUA层的一些消息（例如，ASP活动消息指示“覆盖”）；*接收来自SCTP层的指示；或*地方管理干预。
The ASP/IPSP state transition diagram is shown in Figure 1. The possible states of an ASP/IPSP are:
ASP/IPSP状态转换图如图1所示。ASP/IPSP的可能状态为：
ASP-DOWN: The remote SUA peer at the ASP/IPSP is unavailable and/or the related SCTP association is down. Initially all ASPs/IPSPs will be in this state. An ASP/IPSP in this state SHOULD NOT be sent any SUA messages, with the exception of Heartbeat, ASP Down Ack and Error messages.
ASP-DOWN：ASP/IPSP上的远程SUA对等点不可用和/或相关SCTP关联已关闭。最初，所有ASP/IPSP都将处于此状态。处于此状态的ASP/IPSP不应发送任何SUA消息，但心跳、ASP停机确认和错误消息除外。
ASP-INACTIVE: The remote SUA peer at the ASP/IPSP is available (and the related SCTP association is up) but application traffic is stopped. In this state the ASP/IPSP SHOULD NOT be sent any DATA or SSNM messages for the AS for which the ASP/IPSP is inactive.
ASP-INACTIVE：ASP/IPSP上的远程SUA对等方可用（且相关SCTP关联已启动），但应用程序流量已停止。在此状态下，对于ASP/IPSP处于非活动状态的AS，不应向ASP/IPSP发送任何数据或SSNM消息。
ASP-ACTIVE: The remote SUA peer at the ASP/IPSP is available and application traffic is active (for a particular Routing Context or set of Routing Contexts).
ASP-ACTIVE：ASP/IPSP上的远程SUA对等点可用，并且应用程序流量处于活动状态（对于特定路由上下文或一组路由上下文）。
Figure 1: ASP/IPSP State Transition Diagram, per AS
图1:ASP/IPSP状态转换图，根据AS
+--------------+
| |
+----------------------| ASP-ACTIVE |
| Other ASP/ +-------| |
| IPSP in AS | +--------------+
| Overrides | ^ |
| | ASPAC/ | | ASPIA/
| |[ASPAC-Ack]| | [ASPIA-Ack]
| | | v
| | +--------------+
| | | |
| +------>| ASP-INACTIVE |
| | |
| +--------------+
| ^ |
ASPDN/ | | | ASPDN /
[ASPDN-Ack/]| ASPUP/ | | [ASPDN-Ack /]
SCTP CDI/ | [ASPUP-Ack] | | SCTP CDI/
SCTP RI | | | SCTP RI
| | v
| +--------------+
| | |
+--------------------->| ASP-DOWN |
| |
+--------------+
+--------------+
| |
+----------------------| ASP-ACTIVE |
| Other ASP/ +-------| |
| IPSP in AS | +--------------+
| Overrides | ^ |
| | ASPAC/ | | ASPIA/
| |[ASPAC-Ack]| | [ASPIA-Ack]
| | | v
| | +--------------+
| | | |
| +------>| ASP-INACTIVE |
| | |
| +--------------+
| ^ |
ASPDN/ | | | ASPDN /
[ASPDN-Ack/]| ASPUP/ | | [ASPDN-Ack /]
SCTP CDI/ | [ASPUP-Ack] | | SCTP CDI/
SCTP RI | | | SCTP RI
| | v
| +--------------+
| | |
+--------------------->| ASP-DOWN |
| |
+--------------+
The transitions in brackets are just valid for the IPSP SE model communication while the rest are valid for both ASPs and IPSPs.
括号中的转换仅对IPSP SE模型通信有效，而其余转换对ASP和IPSP都有效。
SCTP CDI: The SCTP CDI denotes the local SCTP layer's Communication Down Indication to the Upper Layer Protocol (SUA) 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上的上层协议（SUA）的通信下行指示。当本地SCTP层检测到与ASP对等SCTP层的连接丢失时，将发送此指示。SCTP CDI被理解为来自SCTP层的关机完成通知或通信丢失通知。
SCTP RI: The local SCTP layer's Restart indication to the upper layer protocol (SUA) 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上上层协议（SUA）的重启指示。当本地SCTP检测到来自ASP对等SCTP层的重启时，将发送此指示。
The state of the AS is maintained in the SUA layer on the SGP. The state of an AS changes due to events. These events include:
AS的状态保持在SGP上的SUA层中。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 is 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, and the SGP has no alternative, the SGP may stop queueing messages and discard all previously queued messages. The AS will move to the AS-INACTIVE state if at least one ASP is in ASP-INACTIVE state, otherwise it will move to AS-DOWN state.
如果T（r）在ASP变为ASP-ACTIVE之前过期，并且SGP没有其他选择，则SGP可能会停止对消息进行排队，并丢弃所有先前排队的消息。如果至少有一个ASP处于ASP-INACTIVE状态，AS将移到AS-INACTIVE状态，否则它将移到AS-DOWN状态。
Figure 2 shows an example AS state machine for the case where the AS/ASP data is provisioned. For other cases where the AS/ASP configuration data is created dynamically, there would be differences in the state machine, especially at creation of the AS.
图2显示了设置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 2: AS State Transition Diagram
图2: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 |
| | | (queueing) |
| |<----------------------------| |
+----------+ 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 |
| | | (queueing) |
| |<----------------------------| |
+----------+ Tr Expiry and no ASP +-------------+
in ASP-INACTIVE state
Tr = Recovery Timer
Tr = Recovery Timer
The AS state diagram for the AS-SG case is applicable for IPSP communication.
AS-SG案例的AS状态图适用于IPSP通信。
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 SUA-User is ready, the local SUA 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节），并假设本地SUA用户已准备就绪，本地SUA ASP维护（ASPM）功能将启动相关程序，使用ASP Up/ASP Down/ASP Active/ASP Inactive消息将ASP状态传递给SGP（见第4.3.4节）。
If the SUA 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.
如果SUA层随后从底层SCTP层接收到SCTP-COMMUNICATION_DOWN或SCTP-RESTART指示原语，它将通过调用M-SCTP_状态指示原语通知层管理。ASP的状态将移动到ASP-DOWN。
In the case of SCTP-COMMUNICATION_DOWN, the SCTP client MAY try to reestablish the SCTP association. This MAY be done by the SUA layer automatically, or Layer Management MAY reestablish using the M-SCTP_ESTABLISH request primitive.
在SCTP通信中断的情况下，SCTP客户端可以尝试重新建立SCTP关联。这可以由SUA层自动完成，或者层管理可以使用M-SCTP_建立请求原语重新建立。
In the case of an SCTP-RESTART indication at an ASP, the ASP is now considered by its SUA 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重启指示的情况下，其SUA对等方现在认为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 SUA 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 SUA management function.
ASP成功建立与SGP的SCTP关联后，SGP将等待ASP发送ASP Up消息，指示ASP SUA对等方可用。ASP始终是ASP Up消息的发起方。此操作可以由层管理的M-ASP_UP request原语在ASP处启动，也可以由SUA管理功能自动启动。
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 receives an ASP Up Ack message. T(ack) is provisioned, 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发送ASP Up消息时，它启动计时器T（确认）。如果ASP在T（确认）内未收到对ASP Up消息的响应，则ASP可重新启动T（确认）并重新发送ASP Up消息，直到收到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 SUA messages (e.g., ASP Active or REG REQ). If the SGP receives any other SUA messages before ASPUP message is received (other than ASPDN - see section 4.3.4.2), the SGP SHOULD discard them.
ASP必须等待ASP Up Ack消息，然后才能发送任何其他SUA消息（例如ASP Active或REG REQ）。如果SGP在收到ASPUP消息之前收到任何其他SUA消息（ASPDN除外-参见第4.3.4.2节），则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。
An IPSP may be considered in the ASP-INACTIVE state after and ASPUP or ASPUP Ack has been received from it. An IPSP can be considered in the ASP-DOWN state after an ASPDN or ASPDN Ack has been received from it. The IPSP may inform Layer Management of the change in state of the remote IPSP using M-ASP_UP or M-ASP_DN indication or confirmation primitives.
在接收到来自IPSP的ASUP或ASUP Ack后，可以认为IPSP处于ASP-INACTIVE状态。从IPSP接收到ASPDN或ASPDN Ack后，可以认为IPSP处于ASP-DOWN状态。IPSP可以使用M-ASP\U UP或M-ASP\U DN指示或确认原语将远程IPSP的状态变化通知给层管理。
Alternatively, when using IPSP DE model, an interchange of ASP Up messages from each end MUST be performed. Four messages are needed for completion.
或者，当使用IPSP DE模型时，必须执行来自每一端的ASP Up消息交换。完成需要四条消息。
If for any local reason (e.g., management lock-out) and IPSP cannot respond to an ASP Up message with an ASP Up Ack message, it responds to an ASP Up message with an Error message with Reason "Refused - Management Blocking" and leaves the remote IPSP in the ASP-DOWN state.
如果由于任何本地原因（例如，管理锁定），IPSP无法使用ASP Up Ack消息响应ASP Up消息，则它会使用错误消息响应ASP Up消息，原因为“拒绝-管理阻塞”，并使远程IPSP处于ASP-DOWN状态。
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 Connectionless or Connection - Oriented, SSNM 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 SUA management function.
当ASP希望从其作为成员的所有应用程序服务器的服务中删除并且不再接收任何无连接或面向连接的SSNM或ASPTM消息时，ASP将向SGP发送ASP关闭消息。此操作可以由层管理的M-ASP_DOWN request原语在ASP处启动，也可以由SUA管理功能自动启动。
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.1) to register within Application Servers but has not deregistered from all of them prior to sending the ASP Down message, the SGP MUST consider the ASP as deregistered in all Application Servers that it is still a member.
ASP是否从任何AS中永久删除是配置管理的一项功能。在ASP以前使用登记程序（见4.4.1节）在应用服务器中注册但尚未在发送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 provisioned, with a default of 2 seconds. Alternatively, retransmission of ASP Down
当ASP发送ASP Down消息时，它启动定时器T（ack）。如果ASP在T（ack）内未收到对ASP Down消息的响应，则ASP可重新启动T（ack）并重新发送ASP Down消息，直到收到ASP Down ack消息。设置了T（ack），默认值为2秒。或者，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.
消息可以置于层管理的控制之下。在这种方法中，T（ack）的到期会导致M-ASP_DOWN confirm原语带有否定指示。
Anytime after the ASP has received an ASP Up Ack message from the SGP or IPSP, 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 an SUA 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 Routing Contexts to indicate for which Application Servers the ASP Active message applies. It is not necessary for the ASP to include all Routing Contexts of interest in a single ASP Active message, thus requesting to become active in all Routing Contexts 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 Routing Context parameter, the receiver must know, via configuration data, which Application Server(s) the ASP is a member.
在ASP从SGP或IPSP收到ASP Up Ack消息后的任何时候，ASP都可以向SGP发送ASP活动消息，指示ASP已准备好开始处理流量。此操作可以由层管理的M-ASP_活动请求原语在ASP处启动，也可以由SUA管理功能自动启动。如果ASP希望通过公共SCTP关联处理多个应用程序服务器的流量，则ASP活动消息应包含一个或多个路由上下文的列表，以指示ASP活动消息适用于哪些应用程序服务器。ASP不必在单个ASP活动消息中包含所有感兴趣的路由上下文，因此请求同时在所有路由上下文中变为活动。多个ASP活动消息可用于在应用程序服务器内单独激活，或以集合形式激活。如果ASP活动消息不包含路由上下文参数，则接收方必须通过配置数据知道ASP是哪个应用程序服务器的成员。
For the Application Servers that the ASP can be successfully activated, the SGP or IPSP responds with one or more ASP Active Ack messages, including the associated Routing Context(s) and reflecting any Traffic Mode Type value present in the related ASP Active message. The Routing Context parameter MUST be included in the ASP Active Ack message(s) if the received ASP Active message contained any Routing Contexts. 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 or IPSP receives any Data messages before an ASP Active message is received, the SGP or IPSP MAY discard them. By sending an ASP Active Ack message, the SGP or IPSP is now ready to receive and send traffic for the related Routing Context(s). The ASP SHOULD NOT send Data or SSNM messages for the related Routing Context(s) before receiving an ASP Active Ack message, or it will risk message loss.
对于能够成功激活ASP的应用程序服务器，SGP或IPSP使用一条或多条ASP活动Ack消息进行响应，包括关联的路由上下文，并反映相关ASP活动消息中存在的任何流量模式类型值。如果收到的ASP活动消息包含任何路由上下文，则必须在ASP活动确认消息中包含路由上下文参数。根据ASP活动消息中的任何流量模式类型请求，或者如果没有请求，则根据本地配置数据，SGP将ASP移动到相关应用程序服务器内的正确ASP流量状态。通过M-ASP\U活动指示通知图层管理。如果SGP或IPSP在收到ASP活动消息之前收到任何数据消息，则SGP或IPSP可能会丢弃这些数据消息。通过发送ASP活动Ack消息，SGP或IPSP现在可以接收和发送相关路由上下文的通信量。在收到ASP活动Ack消息之前，ASP不应发送相关路由上下文的数据或SSNM消息，否则将有消息丢失的风险。
Multiple ASP Active Ack messages MAY be used in response to an ASP Active message containing multiple Routing Contexts, allowing the SGP or IPSP to independently acknowledge the ASP Active message for different (sets of) Routing Contexts. The SGP or IPSP MUST send an Error message ("Invalid Routing Context") for each Routing Context value that cannot be successfully activated.
多个ASP活动Ack消息可用于响应包含多个路由上下文的ASP活动消息，从而允许SGP或IPSP针对不同（组）路由上下文独立地确认ASP活动消息。SGP或IPSP必须为无法成功激活的每个路由上下文值发送错误消息（“无效路由上下文”）。
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 or IPSP 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或IPSP的数据消息可以在不同的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 messages until it receives an ASP Active Ack message. T(ack) is provisioned, with a default of 2 seconds. Alternatively, retransmission of ASP Active messages MAY be put under 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 SUA layer: Override, Loadshare 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, then 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 SUA层中有三种应用程序服务器流量处理模式：覆盖、负载共享和广播。包含时，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 state ASP-INACTIVE and SHOULD no longer receive traffic from the SGP within the AS. The SGP or IPSP then MUST send a Notify message ("Alternate ASP Active") to the previously active ASP in the AS, and SHOULD stop traffic to/from
在覆盖模式AS的情况下，在SGP处接收ASP活动消息将导致AS的所有通信量（重新）定向到发送ASP活动消息的ASP。AS中任何以前处于活动状态的ASP现在被视为处于ASP-INACTIVE状态，并且不应再从AS中的SGP接收流量。然后，SGP或IPSP必须向AS中先前处于活动状态的ASP发送通知消息（“备用ASP活动”），并应停止来往的通信
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.
那个ASP。接收到此通知的ASP现在必须在ASP非活动状态下考虑自身，如果它还没有通过与ASP的ASP间通信来意识到这一点的话。
In the case of a Loadshare mode AS, reception of an ASP Active message at an SGP or IPSP 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 loadsharing 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., the SLS or SSN).
在Loadshare模式AS的情况下，除了AS中当前处于活动状态的所有其他ASP外，在SGP或IPSP处接收ASP活动消息会导致发送ASP活动消息的ASP的流量方向。SGP中用于AS内所有活动ASP的负载共享流量的算法取决于实现。例如，该算法可以是循环的或基于数据消息中的信息（例如，SLS或SSN）。
An SGP or IPSP, upon reception of an ASP Active message for the first ASP in a Loadshare 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或IPSP在接收到负载共享AS中第一个ASP的ASP活动消息后，可以选择不将流量定向到新活动的ASP，直到它确定有足够的资源来处理预期负载（例如，直到AS中有“n”个ASP处于ASP-Active状态）。
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 rebalancing of the offered load.
负载共享模式AS中的所有ASP必须能够处理为AS接收的任何数据消息，以适应所提供负载的任何潜在故障转移或重新平衡。
In the case of a Broadcast mode AS, reception of an ASP Active message at an SGP or IPSP 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 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. An SGP or IPSP, 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).
在广播模式AS的情况下，除了AS中当前处于活动状态的所有其他ASP外，在SGP或IPSP处接收ASP活动消息会导致发送ASP活动消息的ASP的流量方向。SGP中用于将AS内的业务广播到所有活动ASP的算法是一种简单的广播算法，其中每个消息都发送到每个活动ASP。SGP或IPSP在接收到广播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 traffic flow 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 traffic flow with the other ASPs in the broadcast group.
每当处于广播模式AS的ASP变为ASP-ACTIVE时，SGP必须使用唯一的相关Id参数标记每个交通流中广播的第一条数据消息。此关联Id的目的是允许新激活的ASP将其对每个流量中的流量的处理与广播组中的其他ASP同步。
Either of the IPSPs can initiate communication. When an IPSP receives an ASP Active, it should mark the peer as ASP-ACTIVE and return an ASP Active Ack message. An ASP receiving an ASP Active Ack message may mark the peer as ASP-Active, if it is not already in the ASP-ACTIVE state.
任何一个IPSP都可以启动通信。当IPSP接收到ASP-Active时，它应将对等方标记为ASP-Active并返回ASP-Active Ack消息。如果对等方尚未处于ASP-Active状态，则接收ASP-Active Ack消息的ASP可能会将其标记为ASP-Active。
Alternatively, when using IPSP DE model, an interchange of ASP Active messages from each end MUST be performed. Four messages are needed for completion.
或者，当使用IPSP DE模型时，必须执行来自每一端的ASP活动消息交换。完成需要四条消息。
When an ASP wishes to withdraw from receiving traffic within an AS, or the ASP wants to initiate the process of deactivation, the ASP sends an ASP Inactive message to the SGP or IPSP.
当ASP希望从AS内的接收流量中退出，或者ASP希望启动停用过程时，ASP将向SGP或IPSP发送ASP Inactive消息。
An ASP Inactive message MUST be always responded by the peer (although other messages may be sent in the middle):
ASP非活动消息必须始终由对等方响应（尽管其他消息可能在中间发送）：
- If the corresponding RK is registered (statically or dynamically), the peer should respond with an ASP Inactive Ack message.
- 如果相应的RK已注册（静态或动态），则对等方应使用ASP Inactive Ack消息进行响应。
- If the RK is not registered, or the RC information is not valid, the peer must respond with an ERROR message with Error Code = "Invalid Routing Context".
- 如果RK未注册，或者RC信息无效，对等方必须以错误代码=“无效路由上下文”的错误消息进行响应。
- If the RC is missing and its specification is needed according to the used configuration, the peer must respond with an ERROR message with Error Code = "No Configured AS for ASP".
- 如果RC缺失，并且根据所使用的配置需要其规范，则对等方必须以错误代码“No Configured AS for ASP”的错误消息进行响应。
The action of sending the ASP Inactive message MAY be initiated at the ASP by an M-ASP_INACTIVE request primitive from Layer Management or MAY be initiated automatically by an SUA 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 Routing Contexts to indicate for which Application Servers the ASP Inactive message applies.
发送ASP非活动消息的操作可以由来自层管理的M-ASP_非活动请求原语在ASP处启动，也可以由SUA管理功能自动启动。如果ASP正在处理公共SCTP关联中多个应用程序服务器的流量，则ASP非活动消息包含一个或多个路由上下文，以指示ASP非活动消息适用于哪些应用程序服务器。
In the case where an ASP Inactive message does not contain a Routing Context parameter, the receiver must know, via configuration data, which Application Servers the ASP is a member and move the ASP to the ASP-INACTIVE state in each all Application Servers.
如果ASP非活动消息不包含路由上下文参数，则接收方必须通过配置数据知道ASP是哪个应用程序服务器的成员，并在每个应用程序服务器中将ASP移动到ASP-Inactive状态。
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
在覆盖模式AS的情况下，如果另一个ASP已通过ASP Active（“覆盖”）消息接管AS内的通信量，则发送ASP Inactive消息的ASP已被删除
considered by the SGP to be in state ASP-INACTIVE. An ASP Inactive Ack message is sent to the ASP, after ensuring that all traffic is stopped to the ASP.
SGP认为处于ASP-INACTIVE状态。在确保所有到ASP的通信都已停止后，ASP Inactive Ack消息将发送到ASP。
In the case of a Loadshare mode AS, the SGP moves the ASP to the ASP-INACTIVE state and the AS traffic is reallocated across the remaining ASPs in the state ASP-ACTIVE, as per the loadsharing 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流量将根据AS中当前使用的负载共享算法在ASP-ACTIVE状态下的其余ASP之间重新分配。如果需要，可以向所有非活动的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 Routing Contexts, allowing the SGP or IPSP to independently acknowledge for different (sets of) Routing Contexts. The SGP or IPSP sends an Error message ("Invalid Routing Context") message for each invalid or not configured Routing Context value in a received ASP Inactive message.
多个ASP非活动Ack消息可用于响应包含多个路由上下文的ASP非活动消息，从而允许SGP或IPSP独立地确认不同（组）路由上下文。SGP或IPSP为接收到的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. 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 provisioned, with a default of 2 seconds. Alternatively, retransmission of ASP Inactive messages MAY be put under 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非活动确认消息未得到确认。使用M-ASP\U非活动确认原语通知图层管理。如果ASP接收到ASP非活动ACK而不发送ASP非激活消息，那么ASP现在应该认为自己处于ASP非活动状态。如果ASP以前处于ASP-ACTIVE状态，则ASP应启动过程以将自身恢复到以前的状态。当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 cancelled. 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状态。
An IPSP may be considered in the ASP-INACTIVE state by a remote IPSP after an ASP Inactive or ASP Inactive Ack message has been received from it.
在从远程IPSP接收到ASP INACTIVE或ASP INACTIVE Ack消息后，远程IPSP可能认为IPSP处于ASP-INACTIVE状态。
Alternatively, when using IPSP DE model, an interchange of ASP Inactive messages from each end MUST be performed. Four messages are needed for completion.
或者，当使用IPSP DE模型时，必须从每一端交换ASP非活动消息。完成需要四条消息。
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 ASP State or Traffic Management related acknowledgement 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消息。在第二种情况下，Notify消息必须在任何ASP状态或与流量管理相关的确认消息（例如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 Loadshare 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.
如果SGP发送的Notify（“AS-PENDING”）消息现在没有活动的ASP来服务流量，或者Notify（“AS中活动的ASP资源不足”）消息必须以Loadshare或广播模式发送，则Notify消息不会显式强制接收消息的ASP变为活动。ASP仍然控制采取什么（以及何时）交通行动。
In the case where a Notify message does not contain a Routing Context 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中采取适当的操作。
Notify works in the same manner as in the SG-AS case. One of the IPSPs can send this message to any remote IPSP that is not in the ASP-DOWN state.
以与SG-as案例相同的方式通知工程。其中一个IPSP可以将此消息发送到任何未处于ASP-DOWN状态的远程IPSP。
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 SUA peer may optionally send Heartbeat messages periodically, subject to a provisioned timer T(beat). Upon receiving a Heartbeat message, the SUA peer MUST respond with a Heartbeat Ack message.
任一SUA对等方可选择性地根据所设置的定时器T（节拍）周期性地发送心跳消息。收到心跳消息后，SUA对等方必须使用心跳确认消息进行响应。
If no Heartbeat Ack message (or any other SUA message) is received from the SUA peer within 2*T(beat), the remote SUA peer is considered unavailable. Transmission of Heartbeat messages is stopped and the signalling process SHOULD attempt to reestablish communication if it is configured as the client for the disconnected SUA peer.
如果在2*T（beat）内未从SUA对等方接收到心跳确认消息（或任何其他SUA消息），则认为远程SUA对等方不可用。心跳消息的传输已停止，如果信令进程配置为断开连接的SUA对等方的客户端，则应尝试重新建立通信。
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 SUA peer as unavailable. The contents/format of the Heartbeat Data parameter is 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 timestamp mechanism (to evaluate delays).
Heartbeat消息可以选择性地包含不透明的Heartbeat数据参数，该参数必须在相关Heartbeat Ack消息中原封不动地回显。发送者在检查返回的心跳ACK消息的内容时，可以选择考虑不可用的远程SUA对等体。Heartbeat数据参数的内容/格式取决于实现，仅与原始发送方的本地兴趣相关。例如，内容可用于支持心跳序列算法（检测丢失的心跳）和/或时间戳机制（评估延迟）。
Note: Heartbeat related events are not shown in Figure 2 "ASP state transition diagram".
注意：图2“ASP状态转换图”中未显示心跳相关事件。
An ASP MAY dynamically register with an SGP as an ASP within an Application Server using the REG REQ message. A Routing Key parameter in the REG REQ message specifies the parameters associated with the Routing Key.
ASP可以使用REG REQ消息在应用服务器内动态地向SGP注册为ASP。REG REQ消息中的路由密钥参数指定与路由密钥相关的参数。
The SGP examines the contents of the received Routing Key parameter and compares it with the currently provisioned Routing Keys. If the received Routing Key matches an existing SGP Routing Key entry, and the ASP is not currently included in the list of ASPs for the related
SGP检查接收到的路由密钥参数的内容，并将其与当前配置的路由密钥进行比较。如果收到的路由密钥与现有的SGP路由密钥条目匹配，并且ASP当前未包含在相关应用程序的ASP列表中
Application Server, the SGP MAY authorize the ASP to be added to the AS. Or, if the Routing Key does not currently exist and the received Routing Key data is valid and unique, an SGP supporting dynamic configuration MAY authorize the creation of a new Routing Key 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-RK-Identifier as provided in the initial request, and a Registration Result "Successfully Registered". A unique Routing Context value assigned to the SGP Routing Key is included. The method of Routing Context value assignment at the SGP is implementation dependent but must be guaranteed to be unique for each Application Server or Routing Key supported by the SGP. If the SGP determines that the received Routing 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 Routing Key", "Error - Invalid DPC", "Error - Invalid Network Appearance" as appropriate.
应用服务器，SGP可以授权ASP添加到AS。或者，如果路由密钥当前不存在且接收到的路由密钥数据有效且唯一，则支持动态配置的SGP可授权创建新路由密钥和相关应用程序服务器，并将ASP添加到新AS。在任何一种情况下，SGP都会向ASP返回注册响应消息，其中包含与初始请求中提供的相同的本地RK标识符，以及“成功注册”的注册结果。包括分配给SGP路由密钥的唯一路由上下文值。SGP上的路由上下文值分配方法取决于实现，但必须保证对于SGP支持的每个应用服务器或路由密钥是唯一的。如果SGP确定接收到的路由密钥数据无效，或包含无效参数值，则SGP将向ASP返回注册响应消息，其中包含注册结果“错误-无效路由密钥”、“错误-无效DPC”、“错误-无效网络外观”（视情况而定）。
If the SGP does not support the registration procedure, the SGP returns an Error message to the ASP, with an error code of "Unsupported Message Type".
如果SGP不支持注册过程，SGP将向ASP返回错误消息，错误代码为“不支持的消息类型”。
If the SGP determines that a unique Routing Key cannot be created, the SGP returns a Registration Response message to the ASP, with a Registration Status of "Error - Cannot Support Unique Routing". An incoming signalling message received at an SGP should not match against more than one Routing 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 Routing 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 - Routing Key not Currently Provisioned".
如果SGP确定当前不存在收到的路由密钥，并且SGP不支持动态配置，则SGP将向ASP返回注册响应消息，其中包含注册结果“错误-当前未设置路由密钥”。
If an SGP determines that a received Routing Key does not currently exist and the SGP supports dynamic configuration but does not have the capacity to add new Routing 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返回注册响应消息，其中包含注册结果“错误-资源不足”。
If an SGP determines that one or more of the Routing Key parameters are not supported for the purpose of creating new Routing Key entries, the SGP returns a Registration Response message to the ASP,
如果SGP确定不支持一个或多个路由密钥参数来创建新的路由密钥条目，SGP将向ASP返回注册响应消息，
containing a Registration Result "Error - Unsupported RK parameter field". This result MAY be used if, for example, the SGP does not support RK Address parameter.
包含注册结果“错误-不支持的RK参数字段”。例如，如果SGP不支持RK地址参数，则可以使用该结果。
A Registration Response "Error - Unsupported Traffic Handling Mode" is returned if the Routing Key in the REG REQ contains a Traffic Handling Mode that is inconsistent with the presently configured mode for the matching Application Server.
如果REG REQ中的路由密钥包含与匹配应用程序服务器当前配置的模式不一致的流量处理模式，则返回注册响应“错误-不支持的流量处理模式”。
An ASP MAY register multiple Routing Keys at once by including a number of Routing 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 Routing 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-RK-Identifier parameter to correlate the requests with the responses.
ASP可以通过在单个REG REQ消息中包含多个路由密钥参数，一次注册多个路由密钥。SGP可以在单个REG RSP消息中响应每个注册请求，在单独的注册结果参数中指示每个路由密钥的成功或失败结果。或者，SGP可以使用多个REG-RSP消息进行响应，每个消息具有一个或多个注册结果参数。ASP使用本地RK标识符参数将请求与响应关联起来。
An ASP MAY modify an existing Routing Key by including a Routing Context parameter in the REG REQ. If the SGP determines that the Routing Context applies to an existing Routing Key, the SG MAY adjust the existing Routing Key to match the new information provided in the Routing Key parameter. A Registration Response "Routing Key Change Refused" is returned if the SGP does not accept the modification of the Routing Key.
ASP可以通过在REG REQ中包含路由上下文参数来修改现有路由密钥。如果SGP确定路由上下文应用于现有路由密钥，则SG可以调整现有路由密钥以匹配路由密钥参数中提供的新信息。如果SGP不接受路由密钥的修改，则返回注册响应“路由密钥更改被拒绝”。
Upon successful registration of an ASP in an AS, the SGP can now send related SS7 Signalling Network Management messaging, if this did not previously start upon the ASP transitioning to state ASP-INACTIVE.
在AS中成功注册ASP后，SGP现在可以发送相关的SS7信令网络管理消息，前提是该消息在ASP转换为ASP-INACTIVE状态时未启动。
An ASP MAY dynamically deregister with an SGP as an ASP within an Application Server using the DEREG REQ message. A Routing Context parameter in the DEREG REQ message specifies which Routing Keys to deregister. An ASP SHOULD move to the ASP-INACTIVE state for an Application Server before attempting to deregister the Routing Key (i.e., deregister after receiving an ASP Inactive Ack). Also, an ASP SHOULD deregister from all Application Servers that it is a member before attempting to move to the ASP-Down state.
ASP可以使用DEREG REQ消息在应用程序服务器内以ASP的形式动态地向SGP注销。DEREG REQ消息中的路由上下文参数指定要取消注册的路由密钥。ASP应在尝试取消注册路由密钥（即，在收到ASP非活动Ack后取消注册）之前，将应用程序服务器移动到ASP非活动状态。此外，在尝试移动到ASP关闭状态之前，ASP应该从其作为成员的所有应用程序服务器注销。
The SGP examines the contents of the received Routing Context parameter and validates that the ASP is currently registered in the Application Server(s) related to the included Routing Context(s). If validated, the ASP is deregistered as an ASP in the related Application Server.
SGP检查接收到的路由上下文参数的内容，并验证ASP当前是否已在与包含的路由上下文相关的应用程序服务器中注册。如果已验证，则ASP将在相关应用程序服务器中注销为ASP。
The deregistration procedure does not necessarily imply the deletion of Routing Key and Application Server configuration data at the SGP. Other ASPs may continue to be associated with the Application Server, in which case the Routing Key data SHOULD NOT be deleted. If a Deregistration results in no more ASPs in an Application Server, an SGP MAY delete the Routing Key data.
注销过程不一定意味着在SGP上删除路由密钥和应用程序服务器配置数据。其他ASP可能会继续与应用服务器关联，在这种情况下，不应删除路由密钥数据。如果取消注册导致应用服务器中没有更多的ASP，SGP可能会删除路由密钥数据。
The SGP acknowledges the deregistration request by returning a DEREG RSP message to the requesting ASP. The result of the deregistration is found in the Deregistration Result parameter, indicating success or failure with cause.
SGP通过向请求ASP返回撤销RSP消息来确认撤销注册请求。注销结果可在“注销结果”参数中找到，表示成功或失败的原因。
An ASP MAY deregister multiple Routing Contexts at once by including a number of Routing Contexts in a single DEREG REQ message. The SGP MAY respond to each deregistration request in a single DEREG RSP message, indicating the success or failure result for each Routing Context in a separate Deregistration Result parameter.
ASP可以通过在单个DEREG REQ消息中包含多个路由上下文，一次取消注册多个路由上下文。SGP可以在单个撤销RSP消息中响应每个撤销注册请求，在单独的撤销注册结果参数中指示每个路由上下文的成功或失败结果。
The Registration/Deregistration procedures work in the IPSP cases in the same way as in AS-SG cases. An IPSP may register an RK in the remote IPSP. An IPSP is responsible for deregistering the RKs that it has registered.
注册/注销程序在IPSP案例中的工作方式与as-SG案例中的工作方式相同。IPSP可以在远程IPSP中注册RK。IPSP负责注销其已注册的RK。
On receiving a N-STATE, N-PCSTATE and N-INFORM indication primitive from the nodal interworking function at an SGP, the SGP SUA layer will send a corresponding SS7 Signalling Network Management (SNM) DUNA, DAVA, SCON, or DUPU message (see Section 3.4) to the SUA peers at concerned ASPs. The SUA layer must fill in various fields of the SNM messages consistently with the information received in the primitives.
从SGP的节点互通功能接收到N-STATE、N-PCSTATE和N-INFORM指示原语后，SGP SUA层将向相关ASP的SUA对等方发送相应的SS7信令网络管理（SNM）DUNA、DAVA、SCON或DUPU消息（见第3.4节）。SUA层必须与原语中接收到的信息一致地填写SNM消息的各个字段。
The SGP SUA layer determines the set of concerned ASPs to be informed based on the specific SS7 network for which the primitive indication is relevant. In this way, all ASPs configured to send/receive traffic within a particular network appearance are informed. If the SGP operates within a single SS7 network appearance, then all ASPs are informed.
SGP SUA层根据与原始指示相关的特定SS7网络确定要通知的相关ASP集。这样，所有配置为在特定网络外观内发送/接收流量的ASP都会得到通知。如果SGP在单个SS7网络外观内运行，则通知所有ASP。
DUNA, DAVA, SCON, and DRST messages are sent sequentially and processed at the receiver in the order sent. SCTP stream 0 SHOULD NOT be used. The Unordered bit in the SCTP DATA chunk MAY be used for the SCON message.
DUNA、DAVA、SCON和DRST消息按顺序发送，并在接收方按发送顺序进行处理。不应使用SCTP流0。SCTP数据块中的无序位可用于SCON消息。
Sequencing is not required for the DUPU or DAUD messages, which MAY be sent unordered. SCTP stream 0 is used, with optional use of the Unordered bit in the SCTP DATA chunk.
DUPU或DAUD消息不需要排序，可能会无序发送。使用SCTP流0，可选择使用SCTP数据块中的无序位。
At an ASP, upon receiving an SS7 Signalling Network Management (SSNM) message from the remote SUA Peer, the SUA layer invokes the appropriate primitive indications to the resident SUA-Users. Local management is informed.
在ASP上，在从远程SUA对等方接收到SS7信令网络管理（SSNM）消息时，SUA层向常驻SUA用户调用适当的原语指示。通知当地管理层。
In the case where a local event has caused the unavailability or congestion status of SS7 destinations, the SUA layer at the ASP SHOULD pass up appropriate indications in the primitives to the SUA User, as though equivalent SSNM messages were received. For example, the loss of an SCTP association to an SGP may cause the unavailability of a set of SS7 destinations. N-PCSTATE indication primitives to the SUA User are appropriate.
在本地事件导致SS7目的地不可用或拥塞状态的情况下，ASP处的SUA层应将原语中的适当指示传递给SUA用户，就像接收到等效的SSNM消息一样。例如，丢失与SGP的SCTP关联可能导致一组SS7目的地不可用。适用于SUA用户的N-PCSTATE指示原语。
Implementation Note: To accomplish this, the SUA layer at an ASP maintains the status of routes via the SG.
实现说明：为了实现这一点，ASP上的SUA层通过SG维护路由状态。
At an ASP, upon receiving a Signalling Network Management message from the remote SUA Peer, the SUA layer updates the status of the affected route(s) via the originating SG and determines, whether or not the overall availability or congestion status of the effected destination(s) has changed. If so, the SUA layer invokes the appropriate primitive indications to the resident SUA-Users. Local management is informed.
在ASP处，当从远程SUA对等方接收到信令网络管理消息时，SUA层通过发起SG更新受影响路由的状态，并确定受影响目的地的总体可用性或拥塞状态是否已改变。如果是这样，SUA层将向常驻SUA用户调用适当的原语指示。通知当地管理层。
An ASP may optionally initiate an audit procedure to inquire of an SGP the availability and, if the national congestion method with multiple congestion levels and message priorities is used, congestion status of an SS7 destination or set of destinations. A Destination Audit (DAUD) message is sent from the ASP to the SGP requesting the current availability and congestion status of one or more SS7 destinations or subsystems.
ASP可以选择性地启动审计过程，以询问SGP的可用性，并且如果使用具有多个拥塞级别和消息优先级的国家拥塞方法，则询问SS7目的地或目的地集的拥塞状态。目标审核（DAUD）消息从ASP发送到SGP，请求一个或多个SS7目标或子系统的当前可用性和拥塞状态。
The DAUD message MAY be sent unordered. The ASP MAY send the DAUD in the following cases:
DAUD消息可能会无序发送。在以下情况下，ASP可能会发送DAUD：
- Periodic. A Timer originally set upon reception of a DUNA, SCON or DRST message has expired without a subsequent DAVA, DUNA, SCON or DRST message updating the availability/congestion status of the affected Destination Point Code. The Timer is reset upon issuing a DAUD. In this case the DAUD is sent to the SGP that originally sent the SSNM message.
- 周期性最初在接收到DUNA、SCON或DRST消息时设置的计时器已过期，没有后续的DAVA、DUNA、SCON或DRST消息更新受影响目的地代码的可用性/拥塞状态。发出DAUD后，定时器复位。在这种情况下，DAUD被发送到最初发送SSNM消息的SGP。
- Isolation. The ASP is newly ASP-ACTIVE or has been isolated from an SGP for an extended period. The ASP MAY request the availability/congestion status of one or more SS7 destinations to which it expects to communicate.
- 隔离ASP是新的ASP-ACTIVE或已与SGP隔离较长时间。ASP可请求其预期与之通信的一个或多个SS7目的地的可用性/拥塞状态。
Implementation Note:
实施说明：
In the first of the cases above, the auditing procedure must not be invoked for the case of a received SCON message containing a congestion level value of "no congestion" or undefined" (i.e., congestion Level = "0"). This is because the value indicates either congestion abatement or that the ITU MTP3 international congestion method is being used. In the international congestion method, the MTP3 layer at the SGP does not maintain the congestion status of any destinations and therefore the SGP cannot provide any congestion information in response to the DAUD. For the same reason, in the second of the cases above a DAUD message cannot reveal any congested destination(s).
在上述第一种情况下，如果收到的SCON消息包含“无拥塞”或未定义的拥塞级别值（即拥塞级别=“0”），则不得调用审核过程。这是因为该值表示拥塞缓解或正在使用ITU MTP3国际拥塞方法。在国际拥塞方法中，SGP的MTP3层不保持任何目的地的拥塞状态，因此SGP无法提供任何拥塞信息以响应DAUD。出于同样的原因，在上述第二种情况下，DAUD消息无法显示任何拥挤的目的地。
The SGP SHOULD respond to a DAUD message with the availability and congestion status of the subsystem. The status of each SS7 destination or subsystem requested is indicated in a DUNA message (if unavailable), a DAVA message (if available), or a DRST (if restricted and the SGP supports this feature). If the SS7 destination or subsystem is available and congested, the SGP responds with an SCON message in addition to the DAVA message. If the SS7 destination or subsystem is restricted and congested, the SGP responds with an SCON message in addition to the DRST. If the SGP has no information on the availability / congestion status of the SS7 destination or subsystem, the SGP responds with a DUNA message, as it has no routing information to allow it to route traffic to this destination or subsystem.
SGP应响应带有子系统可用性和拥塞状态的DAUD消息。请求的每个SS7目的地或子系统的状态在DUNA消息（如果不可用）、DAVA消息（如果可用）或DRST（如果受限且SGP支持此功能）中指示。如果SS7目的地或子系统可用且拥挤，则SGP除了DAVA消息外，还会以SCON消息作出响应。如果SS7目的地或子系统受到限制和拥塞，则SGP除了DRST外，还将使用SCON消息进行响应。如果SGP没有关于SS7目的地或子系统的可用性/拥塞状态的信息，则SGP将使用DUNA消息进行响应，因为它没有路由信息以允许它将流量路由到此目的地或子系统。
An SG MAY refuse to provide the availability or congestion status of a destination or subsystem if, for example, the ASP is not authorized to know the status of the destination or subsystem. The SG MAY respond with an Error Message (Error Code = "Destination Status Unknown") or Error Message (Error Code = "Subsystem Status Unknown").
例如，如果ASP无权了解目的地或子系统的状态，则SG可能拒绝提供目的地或子系统的可用性或拥塞状态。SG可能会响应错误消息（错误代码=“目的地状态未知”）或错误消息（错误代码=“子系统状态未知”）。
In the case where the MTP3 in the SG undergoes an MTP restart, event communication SHOULD be handled as follows:
如果SG中的MTP3经历MTP重启，事件通信应按如下方式处理：
When the SG discovers SS7 network isolation, the SGPs send an indication to all concerned available ASPs (i.e., ASPs in the ASP-ACTIVE state) using DUNA messages for the concerned destinations. When the SG has completed the MTP Restart procedure, the SUA layer at the SGPs inform all concerned ASPs in the ASP-ACTIVE state of any available/restricted SS7 destinations using the DAVA/DRST message. No message is necessary for those destinations still unavailable after the restart procedure.
当SG发现SS7网络隔离时，SGP使用相关目的地的DUNA消息向所有相关可用的ASP（即处于ASP-ACTIVE状态的ASP）发送指示。当SG完成MTP重启程序时，SGP的SUA层使用DAVA/DRST消息通知处于ASP-ACTIVE状态的所有相关ASP任何可用/受限的SS7目的地。对于重新启动过程后仍不可用的目标，不需要任何消息。
When the SUA layer at an ASP receives a DUNA message indicating SS7 destination unavailability at an SG, SCCP Users will receive an N-PCSTATE indication and will stop any affected traffic to this destination. When the SUA receives a DAVA/DRST message, SCCP Users will receive an N-PCSTATE indication and can resume traffic to the newly available SS7 destination via this SGP, provided the ASP is in the ASP-ACTIVE state toward this SGP.
当ASP处的SUA层接收到指示SG处SS7目的地不可用的DUNA消息时，SCCP用户将接收到N-PCSTATE指示，并将停止到此目的地的任何受影响流量。当SUA接收到DAVA/DRST消息时，SCCP用户将收到N-PCSTATE指示，并且可以通过该SGP恢复到新可用SS7目的地的通信量，前提是该SGP的ASP处于ASP-ACTIVE状态。
The ASP MAY choose to audit the availability of unavailable destinations by sending DAUD messages. This would be for example the case when an AS becomes active at an ASP and does not have current destination statuses. If MTP restart is in progress at the SG, the SGP returns a DUNA message for that destination, even if it received an indication that the destination became available or restricted.
ASP可以选择通过发送DAUD消息来审核不可用目的地的可用性。例如，当AS在ASP处变为活动状态且没有当前目标状态时，就是这种情况。如果SG处正在进行MTP重启，则SGP将返回该目的地的DUNA消息，即使它收到目的地可用或受限的指示。
When it is expected that signalling messages will not fit into a PDU of the most restrictive transport technology used (e.g., 272-SIF of MTP3), then segmenting/reassembly could be performed at the SG, ASP or IPSP. If the SG, ASP or IPSP is incapable of performing a necessary segmentation/reassembly, it can inform the peer of the failure using the appropriate error in a CLDR or RESRE/COERR message.
当预计信令消息将不适合所使用的最严格传输技术的PDU（例如，MTP3的272-SIF）时，可在SG、ASP或IPSP处执行分段/重新组装。如果SG、ASP或IPSP无法执行必要的分段/重新组装，则可以使用CLDR或RESRE/COERR消息中的适当错误通知对等方故障。
Within an AS (identified by RK/RC parameters) several loadsharing ASPs may be active.
在AS（由RK/RC参数标识）内，多个负载共享ASP可能处于活动状态。
However, to assure the correct processing of TCAP transactions or SCCP connections, the loadsharing scheme used at the SG must make sure that messages continuing or ending the transactions/connections arrive at the same ASP where the initial message (TC_Query, TC_Begin, CR) was sent to/received from.
但是，为确保正确处理TCAP事务或SCCP连接，SG使用的负载共享方案必须确保继续或结束事务/连接的消息到达发送/接收初始消息（TC_查询、TC_开始、CR）的同一ASP。
When the ASP can be identified uniquely based on RK parameters (e.g., unique DPC or GT), loadsharing is not required. When the ASPs in the AS share state or use an internal distribution mechanism, the SG must only take into account the in-sequence-delivery requirement. In case of SCCP CO traffic, when the coupled approach is used, loadsharing of messages other than CR is not required.
如果可以根据RK参数（例如，唯一DPC或GT）唯一地识别ASP，则不需要负载共享。当ASP处于AS共享状态或使用内部分配机制时，SG必须只考虑顺序交付要求。在SCCP协同通信的情况下，当使用耦合方法时，不需要对CR以外的消息进行负载共享。
If these assumptions cannot be made, both SG and ASP should support the following general procedure in a loadsharing environment.
如果无法做出这些假设，SG和ASP应在负载共享环境中支持以下一般过程。
After association setup and registration, an ASP normally goes active for each AS it registered for. In the ASPAC message, the ASP includes a TID and/or DRN Label Parameter, if applicable for the AS in question. All the ASPs within the AS must specify a unique label at a fixed position in the TID or DRN parameter. The same ASPAC message is sent to each SG used for interworking with the SS7 network.
在关联设置和注册之后，ASP通常会在注册时激活。在ASPAC消息中，ASP包括TID和/或DRN标签参数（如果适用于所述AS）。AS中的所有ASP必须在TID或DRN参数中的固定位置指定唯一标签。将相同的ASPAC消息发送到每个用于与SS7网络互通的SG。
The SG builds, per RK, a list of ASPs that have registered for it. The SG can now build up and update a distribution table for a certain Routing Context, any time the association is (re-)established and the ASP goes active. The SG has to perform some trivial plausibility checks on the parameters:
SG根据RK建立已注册的ASP列表。现在，只要关联（重新）建立且ASP处于活动状态，SG就可以为特定路由上下文建立和更新分发表。SG必须对参数进行一些无关紧要的合理性检查：
- Start and End parameters values are between 0 and 31 for TID. - Start and End parameters values are between 0 and 23 for DRN - 0 < (Start - End + 1) <= 16 (label length maximum 16-bit) - Start values are the same for each ASP within a RC - End values are the same for each ASP within a RC - TID and DRN Label values must be unique across the RC
- TID的开始和结束参数值介于0和31之间。-对于DRN-0<（开始-结束+1）<=16（标签长度最大为16位），开始和结束参数值介于0和23之间-对于RC中的每个ASP，开始值相同-对于RC中的每个ASP，结束值相同-TID，DRN标签值在RC中必须是唯一的
If any of these checks fail, the SG refuses the ASPAC request, with an error, "Invalid loadsharing label."
如果这些检查中的任何一项失败，SG将拒绝ASPAC请求，并显示一个错误“无效的负载共享标签”
Messages not containing a destination (or "responding") TID, i.e., Query, Begin, Unidirectional, are loadshared among the available ASPs. Any scheme permitting a fair load distribution among the ASPs is allowed (e.g., round robin).
不包含目标（或“响应”）TID（即查询、开始、单向）的消息在可用的ASP之间进行负载共享。允许任何允许在ASP之间公平分配负载的方案（例如，循环）。
When a destination TID is present, the SG extracts the label and selects the ASP that corresponds with it.
当存在目标TID时，SG提取标签并选择与其对应的ASP。
If an ASP is not available, the SG may generate (X)UDTS "routing failure", if the return option is used.
如果ASP不可用，则如果使用返回选项，SG可能会生成（X）个UDT“路由失败”。
Messages not containing a destination reference number (DRN), i.e., a Connection Request, MAY be loadshared among the available ASPs. The load distribution mechanism is an implementation issue. When a DRN is present, the SG extracts the label and selects the ASP that corresponds with it. If an ASP is not available, the SG discards the message.
不包含目的地参考号（DRN）的消息，即连接请求，可以在可用的ASP之间进行负载共享。负载分配机制是一个实现问题。当存在DRN时，SG提取标签并选择与其对应的ASP。如果ASP不可用，SG将丢弃该消息。
It is important that each ASP send its unique label (within the AS) to each SGP. For a better robustness against association failures, the SGs MAY cooperate to provide alternative routes toward an ASP. Mechanisms for SG cooperation/coordination are outside of the scope of this document.
重要的是，每个ASP向每个SGP发送其唯一的标签（在AS内）。为了更好地抵抗关联失败，SGs可以合作提供通向ASP的替代路由。SG合作/协调机制不在本文件范围内。
The following sequence charts overview the procedures of SUA. These are meant as examples, they do not, in and of themselves, impose additional requirements upon an instance of SUA.
以下序列图概述了SUA的程序。这些只是示例，它们本身不会对SUA实例施加额外的要求。
The sequences below outline logical steps for a variety of scenarios within a SG architecture. Please note that these scenarios cover a Primary/Backup configuration. Where there is a load-sharing configuration then the SGP can declare availability when 1 ASP issues ASPAC but can only declare unavailability when all ASPs have issued ASPIA.
下面的顺序概述了SG体系结构中各种场景的逻辑步骤。请注意，这些场景包括主/备份配置。如果存在负载共享配置，则SGP可以在1个ASP发布ASPAC时声明可用性，但只能在所有ASP发布ASPIA时声明不可用。
The following is established before traffic can flow.
在交通能够流动之前，建立以下条件。
Each node is configured (via MIB, for example) with the connections that need to be setup.
每个节点都配置了（例如，通过MIB）需要设置的连接。
ASP-a1 ASP-a2 SG SEP
(Primary) (Backup)
|------Establish SCTP Association------|
|--Estab. SCTP Ass--|
|--Align SS7 link---|
+----------------ASP Up---------------->
<--------------ASP Up Ack--------------+
+------ASP Up------->
<---ASP Up Ack------+
+-------------ASP Active--------------->
<----------ASP Active Ack--------------+
<----------NTFY (ASP Active)-----------+
<-NTFY (ASP Active)-+
+--------SSA-------->
<--------SSA--------+
<-----------------DAVA-----------------+
+-----------------CLDT----------------->
+--------UDT-------->
ASP-a1 ASP-a2 SG SEP
(Primary) (Backup)
|------Establish SCTP Association------|
|--Estab. SCTP Ass--|
|--Align SS7 link---|
+----------------ASP Up---------------->
<--------------ASP Up Ack--------------+
+------ASP Up------->
<---ASP Up Ack------+
+-------------ASP Active--------------->
<----------ASP Active Ack--------------+
<----------NTFY (ASP Active)-----------+
<-NTFY (ASP Active)-+
+--------SSA-------->
<--------SSA--------+
<-----------------DAVA-----------------+
+-----------------CLDT----------------->
+--------UDT-------->
The following sequences address fail-over of SEP and ASP.
以下序列说明SEP和ASP的故障转移。
The SEP knows that the SGP is 'concerned' about its availability. Similarly, the SGP knows that ASP-a1 is concerned about the SEPs availability.
SEP知道SGP“关注”其可用性。同样，SGP知道ASP-a1关心SEPs的可用性。
ASP-a1 ASP-a2 SG SEP
(Primary) (Backup)
<--------SSP--------+
<-----------------DUNA-----------------+
+-----------------DAUD----------------->
+--------SST-------->
ASP-a1 ASP-a2 SG SEP
(Primary) (Backup)
<--------SSP--------+
<-----------------DUNA-----------------+
+-----------------DAUD----------------->
+--------SST-------->
The following is an example of a successful fail-over scenario, where there is a fail-over from ASP-a1 to ASP-a2, i.e., Primary to Backup. During the fail-over, the SGP buffers any incoming data messages from the SEP, forwarding them when the Backup becomes available.
下面是一个成功的故障切换场景示例，其中存在从ASP-a1到ASP-a2的故障切换，即从主服务器到备份服务器的故障切换。在故障转移期间，SGP缓冲来自SEP的任何传入数据消息，并在备份可用时转发这些消息。
ASP-a1 ASP-a2 SG SEP
(Primary) (Backup)
+-------------ASP Inactive------------->
<-----------ASP Inactive ACK-----------+
<--------------------NTFY (AS Pending)-+
<-NTFY (AS Pending)-+
+----ASP Active----->
<--ASP Active Ack---+
<-NTFY (AS Active)--+
<----------NTFY (AS Active)------------+
ASP-a1 ASP-a2 SG SEP
(Primary) (Backup)
+-------------ASP Inactive------------->
<-----------ASP Inactive ACK-----------+
<--------------------NTFY (AS Pending)-+
<-NTFY (AS Pending)-+
+----ASP Active----->
<--ASP Active Ack---+
<-NTFY (AS Active)--+
<----------NTFY (AS Active)------------+
ASP-a1 ASP-a2 SG SEP
(Primary) (Backup)
+-------------ASP Inactive------------->
<-----------ASP Inactive ACK-----------+
<--------------------NTFY (AS Pending)-+
<--NTFY (AS Pending)-+
After some time elapses (i.e., timeout).
+--------SSP-------->
<--------SST--------+
<-------------------NTFY (AS Inactive)-+
<-NTFY (AS Inactive)-+
ASP-a1 ASP-a2 SG SEP
(Primary) (Backup)
+-------------ASP Inactive------------->
<-----------ASP Inactive ACK-----------+
<--------------------NTFY (AS Pending)-+
<--NTFY (AS Pending)-+
After some time elapses (i.e., timeout).
+--------SSP-------->
<--------SST--------+
<-------------------NTFY (AS Inactive)-+
<-NTFY (AS Inactive)-+
The sequences below outline logical steps for a variety of scenarios within an IP-IP architecture. Please note that these scenarios cover a Primary/Backup configuration. Where there is a load-sharing configuration then the AS can declare availability when 1 ASP issues ASPAC but can only declare unavailability when all ASPs have issued ASPIA.
下面的顺序概述了IP-IP体系结构中各种场景的逻辑步骤。请注意，这些场景包括主/备份配置。如果存在负载共享配置，则AS可以在1个ASP发布ASPAC时声明可用性，但只能在所有ASP发布ASPIA时声明不可用。
The following shows an example establishment of SUA connectivity. In this example, each IPSP consists of an Application Server and two ASPs. The following is established before SUA traffic can flow. A connectionless flow is shown for simplicity.
以下显示了建立SUA连接的示例。在本例中，每个IPSP由一个应用程序服务器和两个ASP组成。在SUA流量可以流动之前，建立以下条件。为了简单起见，显示了无连接流。
Establish SCTP Connectivity - as per RFC 2960. Note that SCTP connections are bidirectional. The endpoint that establishes SCTP connectivity MUST also establish UA connectivity (see RFC 2960, section 5.2.1 for handling collisions) [2960].
根据RFC 2960建立SCTP连接。请注意，SCTP连接是双向的。建立SCTP连接的端点还必须建立UA连接（关于冲突处理，请参见RFC 2960第5.2.1节）[2960]。
IP SEP A IP SEP B AS A AS B ASP-a1 ASP-a2 ASP-b2 ASP-b1
IP SEP A IP SEP B AS A AS B ASP-a1 ASP-a2 ASP-b2 ASP-b1
[All ASPs are in the ASP-DOWN state]
[所有ASP都处于ASP-DOWN状态]
+-------------------------------ASP Up-------------------------->
<-----------------------------ASP Up Ack------------------------+
+-------------------------------ASP Up-------------------------->
<-----------------------------ASP Up Ack------------------------+
+--------------ASP Up--------------->
<------------ASP Up Ack-------------+
+--------------ASP Up--------------->
<------------ASP Up Ack-------------+
+---------------------------ACTIVE------------------------------->
<-------------------------ACTIVE Ack-----------------------------+
+---------------------------ACTIVE------------------------------->
<-------------------------ACTIVE Ack-----------------------------+
[Traffic can now flow directly between ASPs]
[流量现在可以直接在ASP之间流动]
+-----------------------------CLDT------------------------------->
+-----------------------------CLDT------------------------------->
The following sequences address fail-over of ASP.
以下序列用于解决ASP的故障转移。
The following is an example of a successful fail-over scenario, where there is a fail-over from ASP-a1 to ASP-a2, i.e., Primary to Backup. Since data transfer passes directly between peer ASPs, ASP-b1 is notified of the fail-over of ASP-a1 and buffers outgoing data messages until ASP-a2 becomes available.
下面是一个成功的故障切换场景示例，其中存在从ASP-a1到ASP-a2的故障切换，即从主服务器到备份服务器的故障切换。由于数据传输直接在对等ASP之间进行，ASP-b1将收到ASP-a1故障转移的通知，并缓冲传出的数据消息，直到ASP-a2可用为止。
IP SEP A IP SEP B ASP-a1 ASP-a2 ASP-b2 ASP-b1
IP SEP A IP SEP B ASP-a1 ASP-a2 ASP-b2 ASP-b1
+-----------------------------ASP Inact------------------------>
<---------------------------ASP Inact Ack----------------------+
<---------------NTFY (ASP-a1 Inactive)--------------+
+---------------------ASP Act----------------------->
<-------------------ASP Act Ack---------------------+
+-----------------------------ASP Inact------------------------>
<---------------------------ASP Inact Ack----------------------+
<---------------NTFY (ASP-a1 Inactive)--------------+
+---------------------ASP Act----------------------->
<-------------------ASP Act Ack---------------------+
The sequence is the same as 5.2.2.1 except that, since the backup fails to come in then, the Notify messages declaring the availability of the backup are not sent.
该顺序与5.2.2.1相同，不同之处在于，由于备份未能进入，因此不会发送声明备份可用性的通知消息。
The security considerations discussed for the 'Security Considerations for SIGTRAN Protocols' [3788] document apply to this document.
“SIGTRAN协议的安全注意事项”[3788]文件中讨论的安全注意事项适用于本文件。
IANA has assigned a SUA value for the Payload Protocol Identifier in the SCTP DATA chunk. The following SCTP Payload Protocol Identifier is registered:
IANA已为SCTP数据块中的有效负载协议标识符分配了一个SUA值。已注册以下SCTP有效负载协议标识符：
SUA "4"
SUA“4”
The SCTP Payload Protocol Identifier value "4" SHOULD be included in each SCTP DATA chunk, to indicate that the SCTP is carrying the SUA protocol. The value "0" (unspecified) is also allowed but any other values MUST not be used. 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有效负载协议标识符值“4”应包含在每个SCTP数据块中，以指示SCTP正在承载SUA协议。也允许使用值“0”（未指定），但不得使用任何其他值。此有效负载协议标识符不直接由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呈现给它的数据的附加信息的方式。
IANA has registered SCTP Port Number 14001 for SUA. It is recommended that SGPs use this SCTP port number for listening for new connections. SGPs MAY also use statically configured SCTP port numbers instead.
IANA已为SUA注册了SCTP端口号14001。建议SGP使用此SCTP端口号侦听新连接。SGP也可以使用静态配置的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. - 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 [2434].
新消息类、类型和参数的定义和使用是SIGTRAN适配层不可分割的一部分。因此，IANA通过[2434]中定义的IETF共识行动分配这些扩展。
The proposed extension MUST in no way adversely affect the general working of the protocol.
拟议的延期决不能对议定书的一般工作产生不利影响。
A new registry has been created by IANA to allow the protocol to be extended.
IANA已经创建了一个新的注册表，以允许扩展协议。
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 = 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 earlier in the document. (c) Detailed definition of each component of the parameter value.
(a) 参数类型的名称。（b） 参数字段结构的详细说明。此结构必须符合文档前面描述的常规类型长度值格式。（c） 参数值的每个组件的详细定义。
(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.
(d) 此参数类型的预期用途的详细说明，以及是否以及在何种情况下可在同一消息类型中找到此参数类型的多个实例的指示。
Ta 2 seconds Tr 2 seconds T(ack) 2 seconds T(ias) Inactivity Send timer 7 minutes T(iar) Inactivity Receive timer 15 minutes T(beat) Heartbeat Timer 30 seconds
Ta 2秒Tr 2秒T（确认）2秒T（ias）不活动发送计时器7分钟T（iar）不活动接收计时器15分钟T（节拍）心跳计时器30秒
The authors would like to thank (in alphabetical order) Richard Adams, Javier Pastor-Balbas, Andrew Booth, Martin Booyens, F. Escobar, S. Furniss Klaus Gradischnig, Miguel A. Garcia, Marja-Liisa Hamalainen, Sherry Karl, S. Lorusso, Markus Maanoja, Sandeep Mahajan, Ken Morneault, Guy Mousseau, Chirayu Patel, Michael Purcell, W. Sully, Michael Tuexen, Al Varney, Tim Vetter, Antonio Villena, Ben Wilson, Michael Wright and James Yu for their insightful comments and suggestions.
作者要感谢（按字母顺序排列）理查德·亚当斯、哈维尔·帕斯托尔·巴尔巴斯、安德鲁·布斯、马丁·布扬斯、F.埃斯科瓦尔、S.弗尼斯·克劳斯·格拉迪施尼格、米格尔·加西亚、玛莉·莉莎·哈马莱宁、雪莉·卡尔、S.洛鲁索、马库斯·马诺亚、桑德普·马哈扬、肯·摩诺、盖·穆索、奇拉尤·帕特尔、迈克尔·普赛尔、W.萨利、，Michael Tuexen、Al Varney、Tim Vetter、Antonio Villena、Ben Wilson、Michael Wright和James Yu，感谢他们富有洞察力的评论和建议。
[1123] Braden, R., Ed., "Requirements for Internet Hosts - Application and Support", STD 3, RFC 1123, October 1989.
[1123]Braden，R.，Ed.“互联网主机的要求-应用和支持”，STD 3，RFC 1123，1989年10月。
[2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[2960] 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.
[2960]Stewart，R.，Xie，Q.，Morneault，K.，Sharp，C.，Schwarzbauer，H.，Taylor，T.，Rytina，I.，Kalla，M.，Zhang，L.，和V.Paxson，“流控制传输协议”，RFC 29602000年10月。
[3629] Yergeau, F., "UTF-8, a transformation format of ISO 10646", STD 63, RFC 3629, November 2003.
[3629]Yergeau，F.，“UTF-8，ISO 10646的转换格式”，STD 63，RFC 3629，2003年11月。
[3788] Loughney, J., Tuexen, M., Ed., and J. Pastor-Balbas, "Security Considerations for Signaling Transport (SIGTRAN) Protocols", RFC 3788, June 2004.
[3788]Loughney，J.，Tuexen，M.，Ed.，和J.Pastor Balbas，“信号传输（SIGTRAN）协议的安全考虑”，RFC 3788，2004年6月。
[ANSI SCCP] ANSI T1.112 "Signalling System Number 7 - Signalling Connection Control Part".
[ANSI SCCP]ANSI T1.112“7号信号系统-信号连接控制部分”。
[ITU SCCP] ITU-T Recommendations Q.711-714, "Signalling System No. 7 (SS7) - Signalling Connection Control Part (SCCP)." ITU-T Telecommunication Standardization Sector of ITU, formerly CCITT, Geneva (July 1996).
[ITU SCCP]ITU-T建议Q.711-714，“第7号信令系统（SS7）-信令连接控制部分（SCCP）”，ITU-T电信标准化部门，前身为CCITT，日内瓦（1996年7月）。
[2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998.
[2434]Narten，T.和H.Alvestrand，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 2434，1998年10月。
[2719] Ong, L., Rytina, I., Garcia, M., Schwarzbauer, H., Coene, L., Lin, H., Juhasz, I., Holdrege, M., and C. Sharp, "Framework Architecture for Signalling Transport", RFC 2719, October 1999.
[2719]Ong，L.，Rytina，I.，Garcia，M.，Schwarzbauer，H.，Coene，L.，Lin，H.，Juhasz，I.，Holdrege，M.，和C.Sharp，“信号传输的框架架构”，RFC 2719，1999年10月。
[3761] Falstrom, P. and M. Mealling, "The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)", RFC 3761, April 2004.
[3761]Falstrom，P.和M.Mealling，“E.164到统一资源标识符（URI）动态委托发现系统（DDDS）应用程序（ENUM）”，RFC 3761，2004年4月。
[ANSI TCAP] ANSI T1.114 'Signalling System Number 7 - Transaction Capabilities Application Part'
[ANSI TCAP]ANSI T1.114“7号信令系统-事务处理能力应用部分”
[ITU TCAP] ITU-T Recommendation Q.771-775 'Signalling System No. 7 SS7) - Transaction Capabilities (TCAP).'
[ITU TCAP]ITU-T建议Q.771-775“第7号信令系统SS7）-事务处理能力（TCAP）。”
[RANAP] 3G TS 25.413 V3.5.0 (2001-03) 'Technical Specification 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN Iu Interface RANAP Signalling'
[RANAP]3G TS 25.413 V3.5.0（2001-03）“第三代合作伙伴项目技术规范”；无线接入网技术规范；UTRAN Iu接口RANAP信令'
Figure 3 shows an example network architecture that can support robust operation and fail-over. There needs to be some management resources at the AS to manage traffic.
图3显示了一个可以支持健壮操作和故障转移的示例网络体系结构。AS需要一些管理资源来管理流量。
***********
* AS1 *
* +-----+ * SCTP Associations
* |ASP1 +-------------------+
* +-----+ * | ***********
* * | * AS3 *
* +-----+ * | * +-----+ *
* |ASP2 +-----------------------------------------+ASP1 | *
* +-----+ * | * +-----+ *
* * | * *
* +-----+ * | * +-----+ *
* |ASP3 | * +--------------------------+ASP2 | *
* +-----+ * | | * +-----+ *
*********** | | ***********
| |
*********** | | ***********
* AS2 * | | * AS4 *
* +-----+ * | | * +-----+ *
* |ASP1 +--------------+ +---------------------+ASP1 | *
* +-----+ * * +-----+ *
* * * *
* +-----+ * * +-----+ *
* |ASP2 +-----------------------------------------+ASP1 | *
* +-----+ * * +-----+ *
* * ***********
* +-----+ *
* |ASP3 | *
* +-----+ *
* *
***********
***********
* AS1 *
* +-----+ * SCTP Associations
* |ASP1 +-------------------+
* +-----+ * | ***********
* * | * AS3 *
* +-----+ * | * +-----+ *
* |ASP2 +-----------------------------------------+ASP1 | *
* +-----+ * | * +-----+ *
* * | * *
* +-----+ * | * +-----+ *
* |ASP3 | * +--------------------------+ASP2 | *
* +-----+ * | | * +-----+ *
*********** | | ***********
| |
*********** | | ***********
* AS2 * | | * AS4 *
* +-----+ * | | * +-----+ *
* |ASP1 +--------------+ +---------------------+ASP1 | *
* +-----+ * * +-----+ *
* * * *
* +-----+ * * +-----+ *
* |ASP2 +-----------------------------------------+ASP1 | *
* +-----+ * * +-----+ *
* * ***********
* +-----+ *
* |ASP3 | *
* +-----+ *
* *
***********
Figure 3: Generalized Architecture
图3：通用架构
In this example, the Application Servers are shown residing within one logical box, with ASPs located inside. In fact, an AS could be distributed among several hosts. In such a scenario, the host should share state as protection in the case of a failure. This is out of scope of this protocol. Additionally, in a distributed system, one ASP could be registered to more than one AS. This document should not restrict such systems - though such a case in not specified.
在本例中，应用程序服务器位于一个逻辑框内，而ASP位于逻辑框内。事实上，AS可以分布在多个主机之间。在这种情况下，主机应在发生故障时共享状态作为保护。这超出了本协议的范围。此外，在分布式系统中，一个ASP可以注册到多个AS。本文件不应限制此类系统-尽管未规定此类情况。
When interworking between SS7 and IP domains is needed, the SGP acts as the gateway node between the SS7 network and the IP network. The SGP will transport SCCP-user signalling traffic from the SS7 network to the IP-based signalling nodes (for example IP-resident Databases). The Signalling Gateway can be considered as a group of Application Servers with additional functionality to interface toward an SS7 network.
当SS7和IP域之间需要互通时，SGP充当SS7网络和IP网络之间的网关节点。SGP将SCCP用户信令业务从SS7网络传输到基于IP的信令节点（例如，IP驻留数据库）。信令网关可被视为一组应用服务器，具有额外的功能以连接到SS7网络。
The SUA protocol should be flexible enough to allow different configurations and transport technology to allow the network operators to meet their operation, management and performance requirements.
SUA协议应足够灵活，允许不同的配置和传输技术，以允许网络运营商满足其运营、管理和性能要求。
An ASP may be connected to multiple SGPs (see figure 4). In such a case, a particular SS7 destination may be reachable via more than SG, therefore, more than one route. Given that proper SLS selection, loadsharing, and SG selection based on point code availability is performed at the ASP, it will be necessary for the ASP to maintain the status of each distant SGPs to which it communicates on the basis of the SG through which it may route.
一个ASP可以连接到多个SGP（见图4）。在这种情况下，特定的SS7目的地可经由多个SG到达，因此可经由多个路由到达。鉴于在ASP上执行了基于点代码可用性的适当SLS选择、负载共享和SG选择，ASP有必要根据其可能路由的SG保持其通信到的每个远程SGP的状态。
Signalling Gateway
SCTP Associations
+----------+ **************
| SG1 | * AS3 *
| ******** | * ******** *
| * SGP11+--------------------------------------------+ ASP1 * *
| ******** | / * ******** *
| ******** | | * ******** *
| * SGP12+--------------------------------------------+ ASP2 * *
| ******** | \ / | * ******** *
+----------+ \ | | * . *
\ | | * . *
+---------- \ | | * . *
| SG2 | \ | | * . *
| ******** | \ | | * ******** *
| * SGP21+---------------------------------+-+ * * ASPN * *
| ******** | \ * ******** *
| ******** | \ **************
| * SGP22+---+--+ \
| ******** | | | \ **************
+----------+ | | \ * AS4 *
| | \ * ******** *
| +-------------------------------------+ ASP1 * *
| * ******** *
| * . *
| * . *
| * *
| * ******** *
+----------------------------------------+ ASPn * *
* ******** *
**************
Signalling Gateway
SCTP Associations
+----------+ **************
| SG1 | * AS3 *
| ******** | * ******** *
| * SGP11+--------------------------------------------+ ASP1 * *
| ******** | / * ******** *
| ******** | | * ******** *
| * SGP12+--------------------------------------------+ ASP2 * *
| ******** | \ / | * ******** *
+----------+ \ | | * . *
\ | | * . *
+---------- \ | | * . *
| SG2 | \ | | * . *
| ******** | \ | | * ******** *
| * SGP21+---------------------------------+-+ * * ASPN * *
| ******** | \ * ******** *
| ******** | \ **************
| * SGP22+---+--+ \
| ******** | | | \ **************
+----------+ | | \ * AS4 *
| | \ * ******** *
| +-------------------------------------+ ASP1 * *
| * ******** *
| * . *
| * . *
| * *
| * ******** *
+----------------------------------------+ ASPn * *
* ******** *
**************
Figure 4: Signalling Gateway Architecture
图4：信令网关体系结构
The pair of SGs can either operate as replicated endpoints or as replicated relay points from the SS7 network point of view.
从SS7网络的角度来看，这对SGs既可以作为复制端点运行，也可以作为复制中继点运行。
Replicated endpoints: the coupling between the SGs and the ASPs when the SGs act as replicated endpoints is an implementation issue.
复制端点：当SGs充当复制端点时，SGs和ASP之间的耦合是一个实现问题。
Replicated relay points: in normal circumstances, the path from SEP to ASP will always go via the same SGP when in-sequence-delivery is requested. However, linkset failures may cause MTP to reroute to the other SG.
复制中继点：在正常情况下，当请求按顺序传递时，从SEP到ASP的路径将始终通过相同的SGP。但是，链路集故障可能会导致MTP重新路由到另一个SG。
By means of configuration, the SG knows the local SCCP-user is actually represented by an AS, and serviced by a set of ASPs working in n+k redundancy mode. An ASP is selected and a CLDT message is sent on the appropriate SCTP association/stream.
通过配置，SG知道本地SCCP用户实际上由AS表示，并由在n+k冗余模式下工作的一组asp服务。选择ASP，并在适当的SCTP关联/流上发送CLDT消息。
The selection criterion can be based on a round robin mechanism, or any other method that guarantees a balanced loadsharing over the active ASPs. However, when TCAP messages are transported, load sharing is only possible for the first message in a TCAP dialogue (TC_Begin, TC_Query, TC_Unidirectional). All other TCAP messages in the same dialogue are sent to the same ASP that was selected for the first message, unless the ASPs are able to share state and maintain sequenced delivery. To this end, the SGP needs to know the TID allocation policy of the ASPs in a single AS:
选择标准可以基于循环机制，也可以基于任何其他方法，以确保在活动的ASP上平衡负载共享。但是，当传输TCAP消息时，负载共享仅适用于TCAP对话中的第一条消息（TC_Begin、TC_Query、TC_单向）。同一对话中的所有其他TCAP消息将发送到为第一条消息选择的同一ASP，除非ASP能够共享状态并保持顺序传递。为此，SGP需要了解ASP的TID分配政策，具体如下：
- State sharing - Fixed range of TIDs per ASP in the AS
- 状态共享-AS中每个ASP的固定TID范围
This information may be provisioned in the SG, or may be dynamically exchanged via the ASP_Active message.
该信息可以在SG中提供，或者可以通过ASP_活动消息动态交换。
An example for an INAP/TCAP message exchange between SEP and ASP is given below.
下面给出了SEP和ASP之间的INAP/TCAP消息交换示例。
Address information in CLDT message (e.g., TC_Query) from SGP to ASP, with association ID = SG-ASP, Stream ID based on sequence control and possibly other parameters, e.g., OPC:
从SGP到ASP的CLDT消息（例如，TC_查询）中的地址信息，关联ID=SG-ASP，流ID基于顺序控制和可能的其他参数，例如OPC：
- Routing Context: based on SS7 Network ID and AS membership, so that the message can be transported to the correct ASP. - Source address: valid combination of SSN, PC and GT, as needed for back routing to the SEP. - Destination address: at least SSN, to select the SCCP/SUA-user at the ASP.
- 路由上下文：基于SS7网络ID和AS成员身份，以便将消息传输到正确的ASP源地址：根据需要，SSN、PC和GT的有效组合，用于返回到SEP的路由。目标地址：至少SSN，用于在ASP上选择SCCP/SUA用户。
Address information in CLDT message (e.g., TC_Response) from ASP to SG, with association ID = ASP-SG, stream ID selected by implementation dependent means with regards to in-sequence-delivery:
从ASP到SG的CLDT消息（例如，TC_响应）中的地址信息，关联ID=ASP-SG，流ID通过实现相关方式选择，与顺序交付有关：
- Routing Context: as received in previous message. - Source address: unique address provided so that when used as the SCCP called party address in the SEP, it must yield the same AS, the SSN might be sufficient.
- 路由上下文：在上一条消息中收到。-源地址：提供的唯一地址，当在SEP中用作SCCP被叫方地址时，它必须产生与相同的地址，SSN可能就足够了。
- Destination address: copied from source address in received CLDT message.
- 目标地址：从收到的CLDT消息中的源地址复制。
Further messages from the SEP belonging to the same TCAP transaction will now reach the same ASP.
来自SEP的属于同一TCAP事务的更多消息现在将到达同一ASP。
Further messages for this connection are routed on DPC in the SS7 connection section (MTP routing label), and on IP address in the IP connection section (SCTP header). No other routing information is present in the SCCP or SUA messages themselves. Resources are kept within the SG to forward messages from one section to another and to populate the MTP routing label or SCTP header, based on the destination local reference of these messages (Connect Confirm, Data Transfer, etc.)
此连接的其他消息在SS7连接部分（MTP路由标签）的DPC上路由，并在IP连接部分（SCTP头）的IP地址上路由。SCCP或SUA消息本身中不存在其他路由信息。资源保存在SG内，用于将消息从一个区段转发到另一个区段，并根据这些消息的目标本地引用（连接确认、数据传输等）填充MTP路由标签或SCTP标头
This means that in the SG, two local references are allocated, one 3-byte value used for the SS7 section and one 4-byte value for the IP section. Also a resource containing the connection data for both sections is allocated, and either of the two local references can be used to retrieve this data e.g., for an incoming DT1 or CODT, for example.
这意味着在SG中，分配了两个本地引用，一个3字节的值用于SS7部分，一个4字节的值用于IP部分。此外，还分配了包含两个部分的连接数据的资源，并且两个本地引用中的任何一个都可用于检索该数据，例如，对于传入的DT1或CODT。
Authors' Addresses
作者地址
John Loughney Nokia Research Center PO Box 407 FIN-00045 Nokia Group Finland
John Loughney诺基亚研究中心邮政信箱407 FIN-00045诺基亚集团芬兰
EMail: john.Loughney@nokia.com
EMail: john.Loughney@nokia.com
Greg Sidebottom Signatus Technologies Kanata, Ontario Canada
Greg Sidebottom Signatus Technologies加拿大安大略省卡纳塔市
EMail: greg@signatustechnologies.com
EMail: greg@signatustechnologies.com
Lode Coene Siemens n.v. Atealaan 34 B-2200 Herentals Belgium
Lode Coene Siemens n.v.Atalaan 34 B-2200 Herentals比利时
Phone: +32-14-252081
EMail: lode.coene@siemens.com
Phone: +32-14-252081
EMail: lode.coene@siemens.com
Gery Verwimp Siemens n.v. 34 Atealaan PO 2200 Herentals Belgium
Gery Verwimp Siemens n.v.34 Atalaan PO 2200比利时海伦塔斯
Phone: +32 14 25 3424
EMail: gery.verwimp@siemens.com
Phone: +32 14 25 3424
EMail: gery.verwimp@siemens.com
Joe Keller Tekelec 5200 Paramount Parkway Morrisville, NC 27560 USA
美国北卡罗来纳州莫里斯维尔派拉蒙公园路5200号，邮编27560
EMail: joe.keller@tekelec.com
EMail: joe.keller@tekelec.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
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2004). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
版权所有（C）互联网协会（2004年）。本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM 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.
本文件及其包含的信息是按“原样”提供的，贡献者、他/她所代表或赞助的组织（如有）、互联网协会和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。