draft-ietf-sigtran-m2ua-15.txt   rfc3331.txt 
Network Working Group Ken Morneault
INTERNET-DRAFT Cisco Systems
Ram Dantu
NetRake
Greg Sidebottom
gregside consulting
Tom George
Alcatel
Brian Bidulock
OpenSS7
Jacob Heitz
Lucent
Expires in June 2002 Feb 2002
Signaling System 7 (SS7) Message Transfer Part (MTP) 2 -
User Adaptation Layer
<draft-ietf-sigtran-m2ua-15.txt>
Status of This Memo Network Working Group K. Morneault
Request for Comments: 3331 Cisco Systems
Category: Standards Track R. Dantu
NetRake
G. Sidebottom
Signatus Technologies
B. Bidulock
OpenSS7
J. Heitz
Lucent
September 2002
This document is an Internet-Draft and is in full conformance with all Signaling System 7 (SS7) Message Transfer Part 2 (MTP2) -
provisions of Section 10 of RFC 2026. Internet-Drafts are working User Adaptation Layer
documents of the Internet Engineering Task Force (IETF), its areas,
and its working groups. Note that other groups MAY also distribute
working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Status of this Memo
and MAY be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as 'work in progress'.
The list of current Internet-Drafts can be accessed at This document specifies an Internet standards track protocol for the
http://www.ietf.org/ietf/1id-abstracts.txt 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.
The list of Internet-Draft Shadow Directories can be accessed at Copyright Notice
http://www.ietf.org/shadow.html.
To learn the current status of any Internet-Draft, please check the Copyright (C) The Internet Society (2002). All Rights Reserved.
'1id-abstracts.txt' listing contained in the Internet- Drafts Shadow
Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe),
munnari.oz.au (Pacific Rim), ftp.ietf.org (US East Coast), or
ftp.isi.edu (US West Coast).
Abstract Abstract
This Internet Draft defines a protocol for backhauling of SS7 MTP2 This document defines a protocol for the backhauling of Signaling
User signalling messages over IP using the Stream Control System 7 Message Transfer Part 2 (SS7 MTP2) User signalling messages
Transmission Protocol (SCTP). This protocol would be used between a over IP using the Stream Control Transmission Protocol (SCTP). This
Signalling Gateway (SG) and Media Gateway Controller (MGC). It is protocol would be used between a Signalling Gateway (SG) and Media
assumed that the SG receives SS7 signalling over a standard SS7 Gateway Controller (MGC). It is assumed that the SG receives SS7
interface using the SS7 Message Transfer Part (MTP) to provide signalling over a standard SS7 interface using the SS7 Message
transport. The Signalling Gateway would act as a Signalling Link Transfer Part (MTP) to provide transport. The Signalling Gateway
Terminal. would act as a Signalling Link Terminal.
TABLE OF CONTENTS Table of Contents
1. Introduction.............................................. 2
1.1 Scope.................................................. 3
1.2 Terminology............................................ 3
1.3 M2UA Overview.......................................... 5
1.4 Services Provided by the M2UA Adaptation Layer......... 7
1.5 Functions Provided by the M2UA Layer................... 9
1.6 Definition of the M2UA Boundaries..................... 12
2. Conventions.............................................. 16
3. Protocol Elements........................................ 16
3.1 Common Message Header................................. 16
3.2 M2UA Message Header................................... 22
3.3 M2UA Messages......................................... 23
4. Procedures............................................... 58
4.1 Procedures to Support the M2UA-User Layer............. 58
4.2 Receipt of Primitives from the Layer Management....... 59
4.3 AS and ASP State Maintenance.......................... 61
4.4 Link Key Management Procedures........................ 73
5. Examples of MTP2 User Adaptation (M2UA) Procedures....... 75
5.1 Establishment of associations between SGP and MGC..... 75
examples
5.2 ASP Traffic Fail-over Examples........................ 77
5.3 SGP to MGC, MTP Level 2 to MTP Level 3 Boundary
Procedures............................................ 78
6. Timer Values............................................. 85
7. Security Considerations.................................. 85
7.1 Threats................................................ 85
7.2 Protecting Confidentiality............................. 86
8. IANA Considerations...................................... 86
8.1 SCTP Payload Protocol Identifier....................... 86
8.2 M2UA Protocol Extensions............................... 86
9. Acknowledgements......................................... 87
10. References............................................... 88
Appendix A: Signalling Network Architecture.................. 90
Authors' Addresses........................................... 92
Full Copyright Statement..................................... 94
1. Introduction..............................................3
1.1 Scope..................................................3
1.2 Terminology............................................3
1.3 Signalling Transport Architecture......................5
1.4 Services Provide by the M2UA Adaptation Layer..........7
1.5 Function Provided by the M2UA Layer....................9
1.6 Definition of the M2UA Boundaries.....................11
2. Conventions..............................................13
3. Protocol Elements........................................13
3.1 Common Message Header.................................13
3.2 M2UA Message Header...................................17
3.3 M2UA Messages.........................................18
4. Procedures...............................................48
4.1 Procedures to Support the M2UA-User Layer.............49
4.2 Receipt of Primitives from the Layer Management.......49
4.3 AS and ASP State Maintenance..........................51
4.4 Link Key Management Procedures........................62
5. Examples of MTP2 User Adaptation (M2UA) Procedures.......63
5.1 Establishment of associations between SG and MGC......63
examples
5.2 MTP Level 2 / MTP Level 3 Boundary Examples...........66
5.3 Layer Management Communication Examples...............66
6. Timers...................................................71
7. Security Considerations..................................71
7.1 Threats................................................71
7.2 Protecting Confidentiality.............................72
8. IANA Considerations......................................72
8.1 SCTP Payload Protocol Identifier.......................72
8.2 IUA Protocol Extensions................................72
9. Acknowledgements.........................................74
10. References...............................................74
11. Author's Addresses.......................................75
1. Introduction 1. Introduction
This draft defines a protocol for the backhauling of SS7 [1] MTP2 User This document defines a protocol for the backhauling of SS7 [1] MTP2
[2] [3] [4] (i.e. MTP3) signalling messages over IP using the Stream Control User [2] [3] [4] (i.e. MTP3) signalling messages over IP using the
Transmission Protocol (SCTP) [8]. This protocol would be used between Stream Control Transmission Protocol (SCTP) [8]. This protocol would
a Signalling Gateway (SG) and Media Gateway Controller (MGC). be used between a Signalling Gateway (SG) and Media Gateway
Controller (MGC).
1.1 Scope 1.1 Scope
There is a need for Switched Circuit Network (SCN) signalling protocol There is a need for Switched Circuit Network (SCN) signalling
delivery from an Signalling Gateway (SG) to a Media Gateway protocol delivery from a Signalling Gateway (SG) to a Media Gateway
Controller (MGC) [9]. The delivery mechanism addresses the following Controller (MGC) [9]. The delivery mechanism addresses the following
objectives: objectives:
* Support for MTP Level 2 / MTP Level 3 interface boundary * Support for MTP Level 2 / MTP Level 3 interface boundary
* Support for communication between Layer Management modules on SG * Support for communication between Layer Management modules on SG
and MGC and MGC
* Support for management of SCTP active associations between the SG and * Support for management of SCTP active associations between the SG
MGC and MGC
The SG will terminate up to MTP Level 2 and the MGC will terminate The SG will terminate up to MTP Level 2 and the MGC will terminate
MTP Level 3 and above. In other words, the SG will transport MTP MTP Level 3 and above. In other words, the SG will transport MTP
Level 3 messages over an IP network to a MGC. Level 3 messages over an IP network to a MGC.
1.2 Terminology 1.2 Terminology
Application Server (AS) - A logical entity serving a specific application Application Server (AS) - A logical entity serving a specific
instance. An example of an Application Server is a MGC handling the application instance. An example of an Application Server is a MGC
MTP Level 3 and call processing for SS7 links terminated by the handling the MTP Level 3 and call processing for SS7 links terminated
Signalling Gateways. Practically speaking, an AS is modeled at the SG by the Signalling Gateways. Practically speaking, an AS is modeled
as an ordered list of one or more related Application Server Processes at the SG as an ordered list of one or more related Application
(e.g., primary, secondary, tertiary, ...). Server Processes (e.g., primary, secondary, tertiary, ...).
Application Server Process (ASP) - A process instance of an Application Application Server Process (ASP) - A process instance of an
Server. Examples of Application Server Processes are active or standby Application Server. Examples of Application Server Processes are
MGC instances. active or standby MGC instances.
Association - An association refers to a SCTP association. The Association - An association refers to a SCTP association. The
association will provide the transport for the delivery of protocol association will provide the transport for the delivery of protocol
data units for one or more interfaces. data units for one or more interfaces.
Backhaul - Refers to the transport of signalling from the point of Backhaul - Refers to the transport of signalling from the point of
interface for the associated data stream (i.e., SG function in the MGU) interface for the associated data stream (i.e., SG function in the
back to the point of call processing (i.e., the MGCU), if this is not MGU) back to the point of call processing (i.e., the MGCU), if this
local [9]. is not local [9].
Fail-over - The capability to reroute signalling traffic as required Fail-over - The capability to reroute signalling traffic as required
to an alternate Application Server Process within an Application Server to an alternate Application Server Process within an Application
in the event of failure or unavailability of a currently used Application Server in the event of failure or unavailability of a currently used
Server Process. Fail-back MAY apply upon the return to service of a Application Server Process. Fail-back MAY apply upon the return to
previously unavailable Application Server Process. service of a previously unavailable Application Server Process.
Host - The computing platform that the ASP process is running on. Host - The computing platform that the ASP process is running on.
Interface - For the purposes of this document, an interface is a SS7 Interface - For the purposes of this document, an interface is a SS7
signalling link. signalling link.
Interface Identifier - The Interface Identifier identifies the physical Interface Identifier - The Interface Identifier identifies the
interface at the SG for which the signalling messages are sent/received. physical interface at the SG for which the signalling messages are
The format of the Interface Identifier parameter can be text or integer, sent/received. The format of the Interface Identifier parameter can
the values of which are assigned according to network operator policy. be text or integer, the values of which are assigned according to
The values used are of local significance only, coordinated between the network operator policy. The values used are of local significance
SG and ASP. only, coordinated between the SG and ASP.
Layer Management - Layer Management is a nodal function in an SG or Layer Management - Layer Management is a nodal function in an SG or
ASP that handles the inputs and outputs between the M2UA layer and a ASP that handles the inputs and outputs between the M2UA layer and a
local management entity. local management entity.
Link Key - The link key is a locally unique (between ASP and SG) Link Key - The link key is a locally unique (between ASP and SG)
value that identifies a registration request for a particular value that identifies a registration request for a particular
Signalling Data Link and Signalling Terminal pair. Signalling Data Link and Signalling Terminal pair.
MTP - The Message Transfer Part of the SS7 protocol MTP - The Message Transfer Part of the SS7 protocol
MTP2 - MTP Level 2, the signalling datalink layer of SS7 MTP2 - MTP Level 2, the signalling data link layer of SS7
MTP3 - MTP Level 3, the signalling network layer of SS7 MTP3 - MTP Level 3, the signalling network layer of SS7
MTP2-User - A protocol that uses the services of MTP Level 2 MTP2-User - A protocol that uses the services of MTP Level 2 (i.e.
(i.e. MTP3). MTP3).
Network Byte Order: Most significant byte first, a.k.a Big Endian. Network Byte Order: Most significant byte first, a.k.a Big Endian.
Signalling Data Link - An SDL refers to a specific communications Signalling Data Link - An SDL refers to a specific communications
facility that connects two Signalling Link Terminals. facility that connects two Signalling Link Terminals.
Signalling Gateway (SG) - An SG is a signalling agent at the edge of Signalling Gateway (SG) - An SG is a signalling agent at the edge of
the IP network. An SG appears to the SS7 as one or more Signalling the IP network. An SG appears to the SS7 as one or more Signalling
Link Terminals that are connected to one or more Signalling Data Links Link Terminals that are connected to one or more Signalling Data
in the SS7 network. An SG contains a set of one or more unique Links in the SS7 network. An SG contains a set of one or more unique
Signalling Gateway Processes, on which one or more is normally Signalling Gateway Processes, on which one or more is normally
actively processing traffic. Where an SG contains more than one SGP, actively processing traffic. Where an SG contains more than one SGP,
the SG is a logical entity. the SG is a logical entity.
Signalling Gateway Process (SGP) - A process instance that uses M2UA to Signalling Gateway Process (SGP) - A process instance that uses M2UA
communicate to and from a Signalling Link Terminal. It serves as an to communicate to and from a Signalling Link Terminal. It serves as
active, backup or load-sharing proces of a Signalling Gateway. an active, backup or load-sharing process of a Signalling Gateway.
Signalling Link Terminal (SLT) - Refers to the means of performing all Signalling Link Terminal (SLT) - Refers to the means of performing
of the functions defined at MTP level 2 regardless of their all of the functions defined at MTP level 2 regardless of their
implementation [2]. implementation [2,3].
Stream - A stream refers to an SCTP stream; a unidirectional logical Stream - A stream refers to an SCTP stream; a unidirectional logical
channel established from one SCTP endpoint to another associated SCTP channel established from one SCTP endpoint to another associated SCTP
endpoint, within which all user messages are delivered in-sequence endpoint, within which all user messages are delivered in-sequence
except for those submitted to the unordered delivery service. except for those submitted to the unordered delivery service.
1.3 M2UA Overview 1.3 M2UA Overview
The framework architecture that has been defined for SCN signalling The framework architecture that has been defined for SCN signalling
transport over IP [9] uses two components: a signalling common transport over IP [9] uses two components: a signalling common
transport protocol and an adaptation module to support the services transport protocol and an adaptation module to support the services
expected by a particular SCN signalling protocol from its underlying expected by a particular SCN signalling protocol from its underlying
protocol layer. protocol layer.
Within this framework architecture, this document defines a SCN Within this framework architecture, this document defines a SCN
adaptation module that is suitable for the transport of SS7 MTP2 User adaptation module that is suitable for the transport of SS7 MTP2 User
messages. The only SS7 MTP2 User is MTP3. The M2UA uses the services messages. The only SS7 MTP2 User is MTP3. The M2UA uses the
of the Stream Control Transmission Protocol [8] as the underlying services of the Stream Control Transmission Protocol [8] as the
reliable signalling common transport protocol. underlying reliable signalling common transport protocol.
In a Signalling Gateway, it is expected that the SS7 MTP2-User signalling In a Signalling Gateway, it is expected that the SS7 MTP2-User
is transmitted and received from the PSTN over a standard SS7 network signalling is transmitted and received from the PSTN over a standard
interface, using the SS7 Message Transfer Part Level 1 and Level 2 [3,4] SS7 network interface, using the SS7 Message Transfer Part Level 1
to provide reliable transport of the MTP3-User signalling messages to and and Level 2 [2,3,4] to provide reliable transport of the MTP3-User
from an SS7 Signalling End Point (SEP) or Signalling Transfer Point (STP). signalling messages to and from an SS7 Signalling End Point (SEP) or
The SG then provides a interworking of transport functions Signalling Transfer Point (STP). The SG then provides an
with the IP transport, in order to transfer the MTP2-User signalling interworking of transport functions with the IP transport, in order
messages to and from an Application Server Process where the peer MTP2- to transfer the MTP2-User signalling messages to and from an
User protocol layer exists. Application Server Process where the peer MTP2-User protocol layer
exists.
1.3.1 Example - SG to MGC 1.3.1 Example - SG to MGC
In a Signalling Gateway, it is expected that the SS7 signalling is In a Signalling Gateway, it is expected that the SS7 signalling is
received over a standard SS7 network termination, using the SS7 Message received over a standard SS7 network termination, using the SS7
Transfer Part (MTP) to provide transport of SS7 signalling messages to Message Transfer Part (MTP) to provide transport of SS7 signalling
and from an SS7 Signalling End Point (SEP) or SS7 Signalling Transfer messages to and from an SS7 Signalling End Point (SEP) or SS7
Point (STP). In other words, the SG acts as a Signalling Link Terminal Signalling Transfer Point (STP). In other words, the SG acts as a
(SLT) [2]. The SG then provides interworking of transport functions Signalling Link Terminal (SLT) [2,3]. The SG then provides an
with IP Signalling Transport, in order to transport the MTP3 signalling interworking of transport functions with IP Signalling Transport, in
messages to the MGC where the peer MTP3 protocol layer exists, as shown order to transport the MTP3 signalling messages to the MGC where the
below: peer MTP3 protocol layer exists, as shown below:
****** SS7 ****** IP ******* ****** SS7 ****** IP *******
*SEP *-----------* SG *-------------* MGC * *SEP *-----------* SG *-------------* MGC *
****** ****** ******* ****** ****** *******
+----+ +----+ +----+ +----+
|S7UP| |S7UP| |S7UP| |S7UP|
+----+ +----+ +----+ +----+
|MTP + |MTP | |MTP + |MTP |
| L3 | (NIF) |L3 | | L3 | (NIF) |L3 |
+----+ +----+----+ +----+ +----+ +----+----+ +----+
|MTP | |MTP |M2UA| |M2UA| |MTP | |MTP |M2UA| |M2UA|
| | | +----+ +----+ | | | +----+ +----+
|L2 | |L2 |SCTP| |SCTP| |L2 | |L2 |SCTP| |SCTP|
|L1 | |L1 +----+ +----+ |L1 | |L1 +----+ +----+
| | | |IP | |IP | | | | |IP | |IP |
+----+ +---------+ +----+ +----+ +---------+ +----+
NIF - Nodal Interworking Function NIF - Nodal Interworking Function
SEP - SS7 Signalling Endpoint SEP - SS7 Signalling Endpoint
IP - Internet Protocol IP - Internet Protocol
SCTP - Stream Control Transmission Protocol (Reference [8]) SCTP - Stream Control Transmission Protocol (Reference [8])
Figure 1 M2UA in the SG to MGC Application Figure 1 M2UA in the SG to MGC Application
Note: STPs MAY be present in the SS7 path between the SEP and the SG. Note: STPs MAY be present in the SS7 path between the SEP and the SG.
It is recommended that the M2UA use the services of the Stream It is recommended that the M2UA use the services of the Stream
Control Transmission Protocol (SCTP) as the underlying reliable Control Transmission Protocol (SCTP) [8] as the underlying reliable
common signalling transport protocol. The use of SCTP provides common signalling transport protocol. The use of SCTP provides the
the following features: following features:
- explicit packet-oriented delivery (not stream-oriented) - explicit packet-oriented delivery (not stream-oriented)
- sequenced delivery of user messages within multiple streams, - sequenced delivery of user messages within multiple streams, with
with an option for order-of-arrival delivery of individual an option for order-of-arrival delivery of individual user
user messages, messages,
- optional multiplexing of user messages into SCTP datagrams, - optional multiplexing of user messages into SCTP datagrams,
- network-level fault tolerance through support of multi-homing - network-level fault tolerance through the support of multi-homing
at either or both ends of an association, at either or both ends of an association,
- resistance to flooding and masquerade attacks, and - resistance to flooding and masquerade attacks, and
- data segmentation to conform to discovered path MTU size - data segmentation to conform to discovered path MTU size
There are scenarios without redundancy requirements and There are scenarios without redundancy requirements and scenarios in
scenarios in which redundancy is supported below the transport which redundancy is supported below the transport layer. In these
layer. In these cases, the SCTP functions above MAY NOT be a cases, the SCTP functions above MAY NOT be a requirement and TCP can
requirement and TCP can be used as the underlying common be used as the underlying common transport protocol.
transport protocol.
1.3.2 ASP Fail-over Model and Terminology 1.3.2 ASP Fail-over Model and Terminology
The M2UA layer supports ASP fail-over functions in order to support a The M2UA layer supports ASP fail-over functions in order to support a
high availability of call and transaction processing capability. All high availability of call and transaction processing capability. All
MTP2-User messages incoming to a SGP from the SS7 network are assigned MTP2-User messages incoming to a SGP from the SS7 network are
to the unique Application Server, based on the Interface Identifier of assigned to the unique Application Server, based on the Interface
the message. Identifier of the message.
The M2UA layer supports a n+k redundancy model (active-standby, The M2UA layer supports a n+k redundancy model (active-standby, load
loadsharing, broadcast) where n is the minimum number of redundant sharing, broadcast) where n is the minimum number of redundant ASPs
ASPs required to handle traffic and k ASPs are available to take over required to handle traffic and k ASPs are available to take over for
for a failed or unavailable ASP. Note that 1+1 active/standby a failed or unavailable ASP. Note that 1+1 active/standby redundancy
redundancy is a subset of this model. A simplex 1+0 model is also is a subset of this model. A simplex 1+0 model is also supported as
supported as a subset, with no ASP redundancy. a subset, with no ASP redundancy.
1.3.3 Client/Server Model 1.3.3 Client/Server Model
It is recommended that the SGP and ASP be able to support both client It is recommended that the SGP and ASP be able to support both client
and server operation. The peer endpoints using M2UA SHOULD be and server operation. The peer endpoints using M2UA SHOULD be
configured so that one always takes on the role of client and the configured so that one always takes on the role of client and the
other the role of server for initiating SCTP associations. The other the role of server for initiating SCTP associations. The
default orientation would be for the SGP to take on the role of server default orientation would be for the SGP to take on the role of
while the ASP is the client. In this case, ASPs SHOULD initiate the server while the ASP is the client. In this case, ASPs SHOULD
SCTP association to the SGP. initiate the SCTP association to the SGP.
The SCTP and TCP Registered User Port Number Assignment for M2UA The SCTP and TCP Registered User Port Number Assignment for M2UA is
is 2904. 2904.
1.4 Services Provided by the M2UA Adaptation Layer 1.4 Services Provided by the M2UA Adaptation Layer
The SS7 MTP3/MTP2(MTP2-User) interface is retained at the termination The SS7 MTP3/MTP2(MTP2-User) interface is retained at the termination
point in the IP network, so that the M2UA protocol layer is required to point in the IP network, so that the M2UA protocol layer is required
provide the equivalent set of services to its users as provided by the to provide the equivalent set of services to its users as provided by
MTP Level 2 to MTP Level 3. the MTP Level 2 to MTP Level 3.
1.4.1 Support for MTP Level 2 / MTP Level 3 interface boundary 1.4.1 Support for MTP Level 2 / MTP Level 3 interface boundary
M2UA supports a MTP Level 2 / MTP Level 3 interface boundary that enables M2UA supports a MTP Level 2 / MTP Level 3 interface boundary that
a seamless, or as seamless as possible, operation of the MTP2-User peers enables a seamless, or as seamless as possible, operation of the
in the SS7 and IP domains. An example of the primitives that need to be MTP2-User peers in the SS7 and IP domains. An example of the
supported can be found in [10]. primitives that need to be supported can be found in [10].
1.4.2 Support for communication between Layer Management modules
on SG and MGC
The M2UA layer needs to provide some messages that will facilitate 1.4.2 Support for communication between Layer Management modules on SG
communication between Layer Management modules on the SG and MGC. and MGC
To facilitate reporting of errors that arise because of backhauling MTP The M2UA layer needs to provide some messages that will facilitate
Level 3 scenario, the following primitive is defined: communication between Layer Management modules on the SG and MGC. To
facilitate reporting of errors that arise because of the backhauling
MTP Level 3 scenario, the following primitive is defined:
M-ERROR M-ERROR
The M-ERROR message is used to indicate an error with a received The M-ERROR message is used to indicate an error with a received M2UA
M2UA message (e.g., an interface identifier value is not known to the message (e.g., an interface identifier value is not known to the SG).
SG).
1.4.3 Support for management of active associations between SG and MGC 1.4.3 Support for management of active associations between SG and MGC
The M2UA layer on the SG keeps the state of the configured ASPs. A set The M2UA layer on the SG keeps the state of the configured ASPs. A
of primitives between M2UA layer and the Layer Management are defined set of primitives between M2UA layer and the Layer Management are
below to help the Layer Management manage the association(s) between defined below to help the Layer Management manage the association(s)
the SG and the MGC. The M2UA layer can be instructed by the Layer between the SG and the MGC. The M2UA layer can be instructed by the
Management to establish a SCTP association to a peer M2UA node. This Layer Management to establish a SCTP association to a peer M2UA node.
procedure can be achieved using the M-SCTP ESTABLISH primitive. This procedure can be achieved using the M-SCTP ESTABLISH primitive.
M-SCTP_ESTABLISH M-SCTP_ESTABLISH
The M-SCTP_ESTABLISH primitive is used to request, indicate and confirm The M-SCTP_ESTABLISH primitive is used to request, indicate and
the establishment of a SCTP association to a peer M2UA node. confirm the establishment of a SCTP association to a peer M2UA node.
M-SCTP_RELEASE M-SCTP_RELEASE
The M-SCTP_RELEASE primitives are used to request, indicate, and The M-SCTP_RELEASE primitives are used to request, indicate, and
confirm the release of a SCTP association to a peer M2UA node. confirm the release of a SCTP association to a peer M2UA node.
The M2UA layer MAY also need to inform the status of the SCTP The M2UA layer MAY also need to inform the status of the SCTP
association(s) to the Layer Management. This can be achieved using association(s) to the Layer Management. This can be achieved using
the following primitive. the following primitive.
M-SCTP_STATUS M-SCTP_STATUS
The M-SCTP_STATUS primitive is used to request and indicate the status The M-SCTP_STATUS primitive is used to request and indicate the
of underlying SCTP association(s). status of underlying SCTP association(s).
The Layer Management MAY need to inform the M2UA layer of an AS/ASP The Layer Management MAY need to inform the M2UA layer of an AS/ASP
status (i.e., failure, active, etc.), so that messages can be exchanged status (i.e., failure, active, etc.), so that messages can be
between M2UA layer peers to stop traffic to the local M2UA user. This exchanged between M2UA layer peers to stop traffic to the local M2UA
can be achieved using the following primitive. user. This can be achieved using the following primitive.
M-ASP_STATUS M-ASP_STATUS
The ASP status is stored inside M2UA layer on both the SG and MGC The ASP status is stored inside the M2UA layer on both the SG and MGC
sides. The M-ASP_STATUS primitive can be used by Layer Management to sides. The M-ASP_STATUS primitive can be used by Layer Management to
request the status of the Application Server Process from the M2UA request the status of the Application Server Process from the M2UA
layer. This primitive can also be used to indicate the status of the layer. This primitive can also be used to indicate the status of the
Application Server Process. Application Server Process.
M-ASP_MODIFY M-ASP_MODIFY
The M-ASP_MODIFY primitive can be used by Layer Management to modify The M-ASP_MODIFY primitive can be used by Layer Management to modify
the status of the Application Server Process. In other words, the the status of the Application Server Process. In other words, the
Layer Management on the ASP side uses this primitive to initiate Layer Management on the ASP side uses this primitive to initiate the
the ASPM procedures. ASPM procedures.
M-AS_STATUS M-AS_STATUS
The M-AS_STATUS primitive can be used by Layer Management to request The M-AS_STATUS primitive can be used by Layer Management to request
the status of the Application Server. This primitive can also be the status of the Application Server. This primitive can also be
used to indicate the status of the Application Server. used to indicate the status of the Application Server.
1.5 Functions Provided by the M2UA Layer 1.5 Functions Provided by the M2UA Layer
1.5.1 Mapping 1.5.1 Mapping
The M2UA layer MUST maintain a map of a Interface ID to a physical The M2UA layer MUST maintain a map of an Interface ID to a physical
interface on the Signalling Gateway. A physical interface would be a interface on the Signalling Gateway. A physical interface would be a
V.35 line, T1 line/timeslot, E1 line/timeslot, etc. The M2UA layer V.35 line, T1 line/time slot, E1 line/time slot, etc. The M2UA layer
MUST also maintain a map of Interface Identifier to SCTP association MUST also maintain a map of the Interface Identifier to SCTP
and to the related stream within the association. association and to the related stream within the association.
The SGP maps an Interface Identifier to an SCTP association/stream The SGP maps an Interface Identifier to an SCTP association/stream
only when an ASP sends an ASP Active message for a particular Interface only when an ASP sends an ASP Active message for a particular
Identifier. It must be noted, however, that this mapping is dynamic Interface Identifier. It must be noted, however, that this mapping
and could change at any time due to a change of ASP state. This mapping is dynamic and could change at any time due to a change of ASP state.
could even temporarily be invalid, for example during failover of one This mapping could even temporarily be invalid, for example during
ASP to another. Therefore, the SGP MUST maintain the states of AS/ASP fail-over of one ASP to another. Therefore, the SGP MUST maintain
and reference them during the routing of an messages to an AS/ASP. the states of AS/ASP and reference them during the routing of any
messages to an AS/ASP.
Note that only one SGP SHOULD provide Signalling Link Terminal Note that only one SGP SHOULD provide Signalling Link Terminal
services to an SS7 link. Therefore, within an SG, an Application services to an SS7 link. Therefore, within an SG, an Application
Server SHOULD be active for only one SGP at any given point in time. Server SHOULD be active for only one SGP at any given point in time.
An example of the logical view of relationship between SS7 link, An example of the logical view of the relationship between an SS7
Interface Identifier, AS and ASP in an SGP is shown below: link, Interface Identifier, AS and ASP in an SGP is shown below:
/-------------------------------------------------+ /-------------------------------------------------+
/ /----------------------------------------------|--+ / /----------------------------------------------|--+
/ / v | / / v |
/ / +----+ act+-----+ +-------+ -+--+|-+- / / +----+ act+-----+ +-------+ -+--+|-+-
SS7 link1-------->|IID |-+ +-->| ASP |-->| Assoc | v SS7 link1-------->|IID |-+ +-->| ASP |-->| Assoc | v
/ +----+ | +----+ | +-----+ +-------+ -+--+--+- / +----+ | +----+ | +-----+ +-------+ -+--+--+-
/ +->| AS |--+ Streams / +->| AS |--+ Streams
/ +----+ | +----+ stb+-----+ / +----+ | +----+ stb+-----+
SS7 link2-------->|IID |-+ | ASP | SS7 link2-------->|IID |-+ | ASP |
+----+ +-----+ +----+ +-----+
where IID = Interface Identifier where IID = Interface Identifier
A SGP MAY support more than one AS. An AS MAY support more than A SGP MAY support more than one AS. An AS MAY support more than one
one Interface Identifier. Interface Identifier.
1.5.2 Support for the management of SCTP associations between the 1.5.2 Support for the management of SCTP associations between the SGPs
SGPs and ASPs and ASPs
The M2UA layer at the SG maintains the availability state of all The M2UA layer at the SG maintains the availability state of all
configured ASPs, in order to manage the SCTP associations and the configured ASPs, in order to manage the SCTP associations and the
traffic between the SG and ASPs. As well, the active/inactive state traffic between the SG and ASPs. As well, the active/inactive state
of remote ASP(s) are also maintained. The Active ASP(s) are the of remote ASP(s) are also maintained. The Active ASP(s) are the
one(s) currently receiving traffic from the SG. one(s) currently receiving traffic from the SG.
The M2UA layer MAY be instructed by local management to establish an The M2UA layer MAY be instructed by local management to establish an
SCTP association to a peer M2UA node. This can be achieved using the SCTP association to a peer M2UA node. This can be achieved using the
M-SCTP_ESTABLISH primitive to request, indicate and confirm the M-SCTP_ESTABLISH primitive to request, indicate and confirm the
establishment of an SCTP association with a peer M2UA node. establishment of an SCTP association with a peer M2UA node.
The M2UA layer MAY also need to inform local management of the status of The M2UA layer MAY also need to inform local management of the status
the underlying SCTP associations using the M-SCTP_STATUS request and of the underlying SCTP associations using the M-SCTP_STATUS request
indication primitive. For example, the M2UA MAY inform local management and the indication primitive. For example, the M2UA MAY inform local
of the reason for the release of an SCTP association, determined either management of the reason for the release of an SCTP association,
locally within the M2UA layer or by a primitive from the SCTP. determined either locally within the M2UA layer or by a primitive
from the SCTP.
Also the M2UA layer may need to inform the local management of the Also the M2UA layer may need to inform the local management of the
change in status of an ASP or AS. This may be achieved using the M-ASP change in status of an ASP or AS. This may be achieved using the M-
STATUS request or M-AS_STATUS request primitives. ASP STATUS request or M-AS_STATUS request primitives.
1.5.3 Status of ASPs 1.5.3 Status of ASPs
The M2UA layer on the SG MUST maintain the state of the ASPs it is The M2UA layer on the SG MUST maintain the state of the ASPs it is
supporting. The state of an ASP changes because of reception of supporting. The state of an ASP changes because of the reception of
peer-to-peer messages (ASPM messages as described in Section 3.3.2) peer-to-peer messages (ASPM messages as described in Section 3.3.2)
or reception of indications from the local SCTP association. ASP or the reception of indications from the local SCTP association. The
state transition procedures are described in Section 4.3.1. ASP state transition procedures are described in Section 4.3.1.
At a SGP, an Application Server list MAY contain active and inactive At a SGP, an Application Server list MAY contain active and inactive
ASPs to support ASP fail-over procedures. When, for example, both ASPs to support ASP fail-over procedures. When, for example, both a
a primary and a backup ASP are available, M2UA peer protocol is primary and a backup ASP are available, the M2UA peer protocol is
required to control which ASP is currently active. The ordered required to control which ASP is currently active. The ordered list
list of ASPs within a logical Application Server is kept updated in of ASPs within a logical Application Server is kept updated in the
the SGP to reflect the active Application Server Process. SGP to reflect the active Application Server Process.
Also the M2UA layer MAY need to inform the local management of the Also the M2UA layer MAY need to inform the local management of the
change in status of an ASP or AS. This can be achieved using the M-ASP change in status of an ASP or AS. This can be achieved using the M-
STATUS or M-AS_STATUS primitives. ASP_STATUS or M-AS_STATUS primitives.
1.5.4 SCTP Specifics 1.5.4 SCTP Specifics
1.5.4.1 SCTP Stream Management 1.5.4.1 SCTP Stream Management
SCTP allows a user specified number of streams to be opened during SCTP allows a user specified number of streams to be opened during
initialization of the association. It is the responsibility of the initialization of the association. It is the responsibility of the
M2UA layer to ensure proper management of these streams. Because of M2UA layer to ensure proper management of these streams. Because of
the unidirectional nature of streams, a M2UA layer is not aware of the the unidirectional nature of streams, a M2UA layer is not aware of
stream information from its peer M2UA layer. Instead, the Interface the stream information from its peer M2UA layer. For this reason,
Identifier is in the M2UA message header. the Interface Identifier is in the M2UA message header.
The use of SCTP streams within M2UA is recommended in order to minimize The use of SCTP streams within M2UA is recommended in order to
transmission and buffering delay, therefore improving the overall minimize transmission and buffering delay, thereby, improving the
performance and reliability of the signalling elements. A separate overall performance and reliability of the signalling elements. A
SCTP stream can be used for each SS7 link. Or, an implementation may separate SCTP stream can be used for each SS7 link. Or, an
choose to split the SS7 link across several streams based on SLS. implementation may choose to split the SS7 link across several
This method may be of particular interest for high speed SS7 links streams based on SLS. This method may be of particular interest for
(MTP3b) since high speed links have a 24-bit sequence number and the high speed SS7 links (MTP3b) since high speed links have a 24-bit
stream sequence number is 16-bits. sequence number and the stream sequence number is 16-bits.
SCTP Stream '0' SHOULD NOT be used for MTP2 User Adaptation (MAUP) SCTP Stream '0' SHOULD NOT be used for MTP2 User Adaptation (MAUP)
messages (see Section 3) since stream '0' SHOULD only be used for ASP messages (see Section 3) since stream '0' SHOULD only be used for ASP
Management (ASPM) messages (see Section 4.3.3). Management (ASPM) messages (see Section 4.3.3).
1.5.5 Seamless SS7 Network Management Interworking 1.5.5 Seamless SS7 Network Management Interworking
The M2UA layer on the SGP SHOULD pass an indication of unavailability The M2UA layer on the SGP SHOULD pass an indication of unavailability
of the M2UA-User (MTP3) to the local Layer Management, if the of the M2UA-User (MTP3) to the local Layer Management, if the
currently active ASP moves from the ACTIVE state. The actions taken by currently active ASP moves from the ACTIVE state. The actions taken
M2UAon the SGP with regards to MTP Level 2 should be in accordance by M2UA on the SGP with regards to MTP Level 2 should be in
with the appropriate MTP specifications. accordance with the appropriate MTP specifications.
1.5.6 Flow Control / Congestion 1.5.6 Flow Control / Congestion
It is possible for the M2UA layer to be informed of IP network It is possible for the M2UA layer to be informed of the IP network
congestion onset and abatement by means of an implementation dependent congestion onset and abatement by means of an implementation
function (i.e. an indication from the SCTP). The handling of dependent function (i.e. an indication from the SCTP). The handling
this congestion indication by M2UA is implementation dependent. of this congestion indication by M2UA is implementation dependent.
However, the actions taken by the SG should be accordance with the However, the actions taken by the SG should be in accordance with the
appropriate MTP specification and should enable SS7 functionality appropriate MTP specification and should enable SS7 functionality
(e.g. flow control) to be correctly maintained. (e.g. flow control) to be correctly maintained.
1.5.7 Audit of SS7 Link State 1.5.7 Audit of SS7 Link State
After a failover of one ASP to another ASP, it may be necessary for the After a fail-over of one ASP to another ASP, it may be necessary for
M2UA on the ASP to audit the current SS7 link state to ensure consistency. the M2UA on the ASP to audit the current SS7 link state to ensure
The M2UA on the SGP would respond to the audit request with information consistency. The M2UA on the SGP would respond to the audit request
regarding the current state of the SS7 link (i.e. in-service, with information regarding the current state of the SS7 link (i.e.
out-of-service, congestion state, LPO/RPO state). in-service, out-of-service, congestion state, LPO/RPO state).
1.6 Definition of the M2UA Boundaries 1.6 Definition of the M2UA Boundaries
1.6.1 Definition of the M2UA / MTP Level 3 boundary 1.6.1 Definition of the M2UA / MTP Level 3 boundary
DATA DATA
ESTABLISH ESTABLISH
RELEASE RELEASE
STATE STATE
DATA RETRIEVAL DATA RETRIEVAL
DATA RETRIEVAL COMPLETE DATA RETRIEVAL COMPLETE
1.6.2 Definition of the M2UA / MTP Level 2 boundary 1.6.2 Definition of the M2UA / MTP Level 2 boundary
DATA DATA
ESTABLISH ESTABLISH
RELEASE RELEASE
STATE STATE
DATA RETRIEVAL DATA RETRIEVAL
DATA RETRIEVAL COMPLETE DATA RETRIEVAL COMPLETE
1.6.3 Definition of the Lower Layer Boundary between M2UA and SCTP 1.6.3 Definition of the Lower Layer Boundary between M2UA and SCTP
The upper layer and layer management primitives provided by SCTP are The upper layer and layer management primitives provided by SCTP are
provided in Reference [8] Section 9. provided in Reference [8] Section 10.
1.6.4 Definition of Layer Management / M2UA Boundary 1.6.4 Definition of Layer Management / M2UA Boundary
M-SCTP_ESTABLISH request M-SCTP_ESTABLISH request
Direction: LM -> M2UA Direction: LM -> M2UA
Purpose: LM requests ASP to establish an SCTP association with an Purpose: LM requests ASP to establish an SCTP association with an
SGP. SGP.
M-SCTP_ESTABLISH confirm M-SCTP_ESTABLISH confirm
Direction: M2UA -> LM Direction: M2UA -> LM
Purpose: ASP confirms to LM that it has established an SCTP Purpose: ASP confirms to LM that it has established an
association with an SGP. SCTP association with an SGP.
M-SCTP_ESTABLISH indication M-SCTP_ESTABLISH indication
Direction: M2UA -> LM Direction: M2UA -> LM
Purpose: SGP informs LM that an ASP has established an SCTP Purpose: SGP informs LM that an ASP has established an SCTP
association. association.
M-SCTP_RELEASE request M-SCTP_RELEASE request
Direction: LM -> M2UA Direction: LM -> M2UA
Purpose: LM requests ASP to release an SCTP association with SGP. Purpose: LM requests ASP to release an SCTP association with SGP.
skipping to change at page 12, line 81 skipping to change at page 14, line 38
Purpose: ASP or SGP reports that it has received an ERROR Purpose: ASP or SGP reports that it has received an ERROR
message from its peer. message from its peer.
M-ASP_UP request M-ASP_UP request
Direction: LM -> M2UA Direction: LM -> M2UA
Purpose: LM requests ASP to start its operation and send an ASP UP Purpose: LM requests ASP to start its operation and send an ASP UP
message to the SGP. message to the SGP.
M-ASP_UP confirm M-ASP_UP confirm
Direction: M2UA -> LM Direction: M2UA -> LM
Purpose: ASP reports that it has received an ASP UP Acknowledgement Purpose: ASP reports that it has received an ASP UP Acknowledgment
message from the SGP. message from the SGP.
M-ASP_DOWN request M-ASP_DOWN request
Direction: LM -> M2UA Direction: LM -> M2UA
Purpose: LM requests ASP to stop its operation and send an ASP DOWN Purpose: LM requests ASP to stop its operation and send an ASP DOWN
message to the SGP. message to the SGP.
M-ASP_DOWN confirm M-ASP_DOWN confirm
Direction: M2UA -> LM Direction: M2UA -> LM
Purpose: ASP reports that is has received an ASP DOWN Acknowledgement Purpose: ASP reports that is has received an ASP DOWN Acknowledgment
message from the SGP. message from the SGP.
M-ASP_ACTIVE request M-ASP_ACTIVE request
Direction: LM -> M2UA Direction: LM -> M2UA
Purpose: LM requests ASP to send an ASP ACTIVE message to the SGP. Purpose: LM requests ASP to send an ASP ACTIVE message to the SGP.
M-ASP_ACTIVE confirm M-ASP_ACTIVE confirm
Direction: M2UA -> LM Direction: M2UA -> LM
Purpose: ASP reports that is has received an ASP ACTIVE Acknowledgement Purpose: ASP reports that is has received an ASP ACTIVE
message from the SGP. Acknowledgment message from the SGP.
M-ASP_INACTIVE request M-ASP_INACTIVE request
Direction: LM -> M2UA Direction: LM -> M2UA
Purpose: LM requests ASP to send an ASP INACTIVE message to the SGP. Purpose: LM requests ASP to send an ASP INACTIVE message to the SGP.
M-ASP_INACTIVE confirm M-ASP_INACTIVE confirm
Direction: M2UA -> LM Direction: M2UA -> LM
Purpose: ASP reports that is has received an ASP INACTIVE Purpose: ASP reports that is has received an ASP INACTIVE
Acknowledgement message from the SGP. Acknowledgment message from the SGP.
M-LINK_KEY_REG Request M-LINK_KEY_REG Request
Direction: LM -> M2UA Direction: LM -> M2UA
Purpose: LM requests ASP to register Link Key with SG by sending REG Purpose: LM requests ASP to register Link Key with SG by sending REG
REQ message. REQ message.
M-LINK_KEY_REG Confirm M-LINK_KEY_REG Confirm
Direction: M2UA -> LM Direction: M2UA -> LM
Purpose: ASP reports to LM that it has successfully received a REG Purpose: ASP reports to LM that it has successfully received a REG
RSP message from SG. RSP message from SG.
skipping to change at page 13, line 32 skipping to change at page 16, line 7
Purpose: ASP reports to LM that it has successfully received a Purpose: ASP reports to LM that it has successfully received a
DEREG RSP message from SG. DEREG RSP message from SG.
M-LINK_KEY_DEREG Indication M-LINK_KEY_DEREG Indication
Direction: M2UA -> LM Direction: M2UA -> LM
Purpose: SG reports to LM that it has successfully processed an Purpose: SG reports to LM that it has successfully processed an
incoming DEREG REQ message from ASP. incoming DEREG REQ message from ASP.
2.0 Conventions 2.0 Conventions
The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,
NOT, RECOMMENDED, NOT RECOMMENDED, MAY, and OPTIONAL, when they appear SHOULD NOT, RECOMMENDED, NOT RECOMMENDED, MAY, and OPTIONAL, when
in this document, are to be interpreted as described in [RFC2119]. they appear in this document, are to be interpreted as described in
[RFC2119].
3.0 Protocol Elements 3.0 Protocol Elements
This section describes the format of various messages used in this This section describes the format of various messages used in this
protocol. protocol.
3.1 Common Message Header 3.1 Common Message Header
The protocol messages for MTP2-User Adaptation require a message The protocol messages for MTP2-User Adaptation require a message
structure which contains a version, message class, message type, message structure that contains a version, message class, message type,
length, and message contents. This message header is common among all message length, and message contents. This message header is common
signalling protocol adaptation layers: among all signalling protocol adaptation layers:
0 1 2 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 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Spare | Message Class | Message Type | | Version | Spare | Message Class | Message Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Length | | Message Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2 Common Message Header Figure 2 Common Message Header
All fields in an M2UA message MUST be transmitted in the network byte All fields in an M2UA message MUST be transmitted in the network byte
order, unless otherwise stated. order, unless otherwise stated.
3.1.1 Version 3.1.1 Version
The version field (vers) contains the version of the M2UA adaptation The version field contains the version of the M2UA adaptation layer.
layer. The supported versions are: The supported versions are:
Value Version Value Version
----- ------- ----- -------
1 Release 1.0 1 Release 1.0
3.1.2 Spare 3.1.2 Spare
The Spare field is 8-bits. It SHOULD be set to all '0's by the sender The Spare field is 8-bits. It SHOULD be set to all '0's by the
and ignored by the receiver. sender and ignored by the receiver.
3.1.3 Message Class 3.1.3 Message Class
The following List contains the valid Message Classes: The following List contains the valid Message Classes:
Message Class: 8 bits (unsigned integer) Message Class: 8 bits (unsigned integer)
0 Management (MGMT) Message [IUA/M2UA/M3UA/SUA] 0 Management (MGMT) Message [IUA/M2UA/M3UA/SUA]
1 Transfer Messages [M3UA] 1 Transfer Messages [M3UA]
2 SS7 Signalling Network Management (SSNM) Messages [M3UA/SUA] 2 SS7 Signalling Network Management (SSNM) Messages [M3UA/SUA]
3 ASP State Maintenance (ASPSM) Messages [IUA/M2UA/M3UA/SUA] 3 ASP State Maintenance (ASPSM) Messages [IUA/M2UA/M3UA/SUA]
4 ASP Traffic Maintenance (ASPTM) Messages [IUA/M2UA/M3UA/SUA] 4 ASP Traffic Maintenance (ASPTM) Messages [IUA/M2UA/M3UA/SUA]
5 Q.921/Q.931 Boundary Primitives Transport (QPTM) 5 Q.921/Q.931 Boundary Primitives Transport (QPTM)
Messages [IUA] Messages [IUA]
6 MTP2 User Adaptation (MAUP) Messages [M2UA] 6 MTP2 User Adaptation (MAUP) Messages [M2UA]
7 Connectionless Messages [SUA] 7 Connectionless Messages [SUA]
8 Connection-Oriented Messages [SUA] 8 Connection-Oriented Messages [SUA]
9 Routing Key Management (RKM) Messages (M3UA) 9 Routing Key Management (RKM) Messages (M3UA)
10 Interface Identifier Management (IIM) Messages (M2UA) 10 Interface Identifier Management (IIM) Messages (M2UA)
11 to 127 Reserved by the IETF 11 to 127 Reserved by the IETF
128 to 255 Reserved for IETF-Defined Message Class extensions 128 to 255 Reserved for IETF-Defined Message Class extensions
3.1.4 Message Type 3.1.4 Message Type
The following List contains the Message Types for the valid Message The following List contains the Message Types for the valid Message
Classes: Classes:
MTP2 User Adaptatation (MAUP) Messages MTP2 User Adaptation (MAUP) Messages
0 Reserved 0 Reserved
1 Data 1 Data
2 Establish Request 2 Establish Request
3 Establish Confirm 3 Establish Confirm
4 Release Request 4 Release Request
5 Release Confirm 5 Release Confirm
6 Release Indication 6 Release Indication
7 State Request 7 State Request
8 State Confirm 8 State Confirm
9 State Indication 9 State Indication
10 Data Retrieval Request 10 Data Retrieval Request
11 Data Retrieval Confirm 11 Data Retrieval Confirm
12 Data Retrieval Indication 12 Data Retrieval Indication
13 Data Retrieval Complete Indication 13 Data Retrieval Complete Indication
14 Congestion Indication 14 Congestion Indication
15 Data Acknowledge 15 Data Acknowledge
16 to 127 Reserved by the IETF 16 to 127 Reserved by the IETF
128 to 255 Reserved for IETF-Defined MAUP extensions 128 to 255 Reserved for IETF-Defined MAUP extensions
Application Server Process State Maintenance (ASPSM) messages Application Server Process State Maintenance (ASPSM) messages
0 Reserved 0 Reserved
1 ASP Up (UP) 1 ASP Up (UP)
2 ASP Down (DOWN) 2 ASP Down (DOWN)
3 Heartbeat (BEAT) 3 Heartbeat (BEAT)
4 ASP Up Ack (UP ACK) 4 ASP Up Ack (UP ACK)
5 ASP Down Ack (DOWN ACK) 5 ASP Down Ack (DOWN ACK)
6 Heartbeat Ack (BEAT ACK) 6 Heartbeat Ack (BEAT ACK)
7 to 127 Reserved by the IETF 7 to 127 Reserved by the IETF
128 to 255 Reserved for IETF-Defined ASPSM extensions 128 to 255 Reserved for IETF-Defined ASPSM extensions
Application Server Process Traffic Maintenance (ASPTM) messages Application Server Process Traffic Maintenance (ASPTM) messages
0 Reserved 0 Reserved
1 ASP Active (ACTIVE) 1 ASP Active (ACTIVE)
2 ASP Inactive (INACTIVE) 2 ASP Inactive (INACTIVE)
3 ASP Active Ack (ACTIVE ACK) 3 ASP Active Ack (ACTIVE ACK)
4 ASP Inactive Ack (INACTIVE ACK) 4 ASP Inactive Ack (INACTIVE ACK)
5 to 127 Reserved by the IETF 5 to 127 Reserved by the IETF
128 to 255 Reserved for IETF-Defined ASPTM extensions 128 to 255 Reserved for IETF-Defined ASPTM extensions
Management (MGMT) Messages Management (MGMT) Messages
0 Error (ERR) 0 Error (ERR)
1 Notify (NTFY) 1 Notify (NTFY)
2 to 127 Reserved by the IETF 2 to 127 Reserved by the IETF
128 to 255 Reserved for IETF-Defined MGMT extensions 128 to 255 Reserved for IETF-Defined MGMT extensions
Interface Identifier Management (IIM) Messages Interface Identifier Management (IIM) Messages
0 Reserved 0 Reserved
1 Registration Request (REG REQ) 1 Registration Request (REG REQ)
2 Registration Response (REG RSP) 2 Registration Response (REG RSP)
3 Deregistration Request (DEREG REQ) 3 Deregistration Request (DEREG REQ)
4 Deregistration Response (DEREG RSP) 4 Deregistration Response (DEREG RSP)
5 to 127 Reserved by the IETF 5 to 127 Reserved by the IETF
128 to 255 Reserved for IETF-Defined IIM extensions 128 to 255 Reserved for IETF-Defined IIM extensions
3.1.5 Message Length 3.1.5 Message Length
The Message Length defines the length of the message in octets, The Message Length defines the length of the message in octets,
including the header. The Message Length MUST include parameter including the header. The Message Length MUST include parameter
padding bytes, if any. The Message Length MUST NOT be longer padding bytes, if any. The Message Length MUST NOT be longer than a
than a MTP3 message [2] [3] [5] plus the length of the common and MTP3 message [2,3,4,5] plus the length of the common and M2UA message
M2UA message headers. headers.
3.1.6 Variable-Length Parameter Format 3.1.6 Variable-Length Parameter Format
M2UA messages consist of a Common Header followed by zero or more M2UA messages consist of a Common Header followed by zero or more
variable-length parameters, as defined by the message type. The variable-length parameters, as defined by the message type. The
variable-length parameters contained in a message are defined in a variable-length parameters contained in a message are defined in a
Tag-Length-Value format as shown below. Tag-Length-Value format as shown below.
0 1 2 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 0 1 2 3 4 5 6 7 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 Tag | Parameter Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ Parameter Value / / Parameter Value /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Mandatory parameters MUST be placed before optional parameters in a Mandatory parameters MUST be placed before optional parameters in a
message. message.
Parameter Tag: 16 bits (unsigned integer) Parameter Tag: 16 bits (unsigned integer)
The Type field is a 16 bit identifier of the type of parameter. It The Type field is a 16 bit identifier of the type of parameter. It
takes a value of 0 to 65534. The common parameters used by adaptation takes a value of 0 to 65534. The common parameters used by the
layers are in the range of 0x00 to 0xff. The M2UA specific parameters adaptation layers are in the range of 0x00 to 0xff. The M2UA
have Tags in the range 0x300 to 0x3ff. specific parameters have Tags in the range 0x300 to 0x3ff.
The common parameter tags (used by all User Adaptation layers) that The common parameter tags (used by all User Adaptation layers) that
M2UA uses are defined below: M2UA uses are defined below:
Parameter Value Parameter Name Parameter Value Parameter Name
--------------- -------------- --------------- --------------
0 (0x00) Reserved 0 (0x00) Reserved
1 (0x01) Interface Identifier (Integer) 1 (0x01) Interface Identifier (Integer)
2 (0x02) Unused 2 (0x02) Unused
3 (0x03) Interface Identifier (Text) 3 (0x03) Interface Identifier (Text)
4 (0x04) Info String 4 (0x04) Info String
5 (0x05) Unused 5 (0x05) Unused
6 (0x06) Unused 6 (0x06) Unused
7 (0x07) Diagnostic Information 7 (0x07) Diagnostic Information
8 (0x08) Interface Identifier (Integer Range) 8 (0x08) Interface Identifier (Integer Range)
9 (0x09) Heartbeat Data 9 (0x09) Heartbeat Data
10 (0x0a) Unused 10 (0x0a) Unused
11 (0x0b) Traffic Mode Type 11 (0x0b) Traffic Mode Type
12 (0x0c) Error Code 12 (0x0c) Error Code
13 (0x0d) Status Type/Information 13 (0x0d) Status Type/Information
14 (0x0e) Unused 14 (0x0e) Unused
15 (0x0f) Unused 15 (0x0f) Unused
16 (0x10) Unused 16 (0x10) Unused
17 (0x11) ASP Identifier 17 (0x11) ASP Identifier
18 (0x12) Unused 18 (0x12) Unused
19 (0x13) Correlation Id 19 (0x13) Correlation Id
18-255 Reserved 18-255 Reserved
The M2UA specific parameter Tags defined are as follows: The M2UA specific parameter Tags defined are as follows:
Parameter Value Parameter Name Parameter Value Parameter Name
--------------- -------------- --------------- --------------
768 (0x0300) Protocol Data 1 768 (0x0300) Protocol Data 1
769 (0x0301) Protocol Data 2 (TTC) 769 (0x0301) Protocol Data 2 (TTC)
770 (0x0302) State Request 770 (0x0302) State Request
771 (0x0303) State Event 771 (0x0303) State Event
772 (0x0304) Congestion Status 772 (0x0304) Congestion Status
773 (0x0305) Discard Status 773 (0x0305) Discard Status
774 (0x0306) Action 774 (0x0306) Action
775 (0x0307) Sequence Number 775 (0x0307) Sequence Number
776 (0x0308) Retrieval Result 776 (0x0308) Retrieval Result
777 (0x0309) Link Key 777 (0x0309) Link Key
778 (0x030a) Local-LK-Identifier 778 (0x030a) Local-LK-Identifier
779 (0x030b) Signalling Data Terminal (SDT) Identifier 779 (0x030b) Signalling Data Terminal (SDT) Identifier
780 (0x030c) Signailng Data Link (SDL) Identifier 780 (0x030c) Signalling Data Link (SDL) Identifier
781 (0x030d) Registration Result 781 (0x030d) Registration Result
782 (0x030e) Registration Status 782 (0x030e) Registration Status
783 (0x030f) De-Registration Result 783 (0x030f) De-Registration Result
784 (0x0310) De-Registration Status 784 (0x0310) De-Registration Status
Parameter Length: 16 bits (unsigned integer) Parameter Length: 16 bits (unsigned integer)
The Parameter Length field contains the size of the parameter in The Parameter Length field contains the size of the parameter in
bytes, including the Parameter Tag, Parameter Length, and Parameter bytes, including the Parameter Tag, Parameter Length, and Parameter
Value fields. Thus, a parameter with a zero-length Parameter Value Value fields. Thus, a parameter with a zero-length Parameter Value
field would have a Length field of 4. The Parameter Length does not field would have a Length field of 4. The Parameter Length does not
include any padding bytes. include any padding bytes.
Parameter Value: variable-length. Parameter Value: variable-length.
The Parameter Value field contains the actual information to be The Parameter Value field contains the actual information to be
transferred in the parameter. transferred in the parameter.
The total length of a parameter (including Tag, Parameter Length and 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 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 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 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 bytes. The length of the padding is NOT included in the parameter
length field. A sender MUST NOT pad with more than 3 bytes. The length field. A sender MUST NOT pad with more than 3 bytes. The
receiver MUST ignore the padding bytes. receiver MUST ignore the padding bytes.
3.2 M2UA Message Header 3.2 M2UA Message Header
In addition to the common message header, there will be a M2UA In addition to the common message header, there will be a M2UA
specific message header. The M2UA specific message header will specific message header. The M2UA specific message header will
immediately follow the common message header, but will only be used immediately follow the common message header, but will only be used
with MAUP messages. with MAUP messages.
This message header will contain the Interface Identifier. The This message header will contain the Interface Identifier. The
Interface Identifier identifies the physical interface at the SG for Interface Identifier identifies the physical interface at the SG for
which the signalling messages are sent/received. The format of the which the signalling messages are sent/received. The format of the
Interface Identifier parameter can be text or integer, the values of Interface Identifier parameter can be text or integer, the values of
which are assigned according to network operator policy. The values which are assigned according to network operator policy. The values
used are of local significance only, coordinated between the SG and used are of local significance only, coordinated between the SG and
ASP. ASP.
The integer formatted Interface Identifier MUST be supported. The The integer formatted Interface Identifier MUST be supported. The
text formatted Interface Identifier MAY optionally be supported. text formatted Interface Identifier MAY optionally be supported.
0 1 2 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 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x1) | Length=8 | | Tag (0x1) | Length=8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier (integer) | | Interface Identifier (integer) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3 M2UA Message Header (Integer-based Interface Identifier) Figure 3 M2UA Message Header (Integer-based Interface Identifier)
The Tag value for Integer-based Interface Identifier is 0x1. The The Tag value for the Integer-based Interface Identifier is 0x1. The
length is always set to a value of 8. length is always set to a value of 8.
0 1 2 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 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x3) | Length | | Tag (0x3) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \ / \
\ Interface Identifier (text) / \ Interface Identifier (text) /
/ \ / \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4 M2UA Message Header (Text-based Interface Identifier) Figure 4 M2UA Message Header (Text-based Interface Identifier)
The Tag value for the Text-based Interface Identifier is 0x3. The The Tag value for the Text-based Interface Identifier is 0x3. The
encoding of the Identifier is ANSI X3.4-1986 [7]. The maximum encoding of the Identifier is ANSI X3.4-1986 [7]. The maximum string
string length of the text-based Interface Identifier is 255 octets. length of the text-based Interface Identifier is 255 octets. The tag
The tag length is equal to the string length of the Interface length is equal to the string length of the Interface Identifier name
Identifier name plus four bytes for the Tag and Length fields. plus four bytes for the Tag and Length fields.
3.3 M2UA Messages 3.3 M2UA Messages
The following section defines the messages and parameter contents. The following section defines the messages and parameter contents.
The M2UA messages will use the common message header (Figure 2) and The M2UA messages will use the common message header (Figure 2) and
the M2UA message header (Figure 3). the M2UA message header (Figure 3 and Figure 4).
3.3.1 MTP2 User Adaptation Messages 3.3.1 MTP2 User Adaptation Messages
3.3.1.1 Data 3.3.1.1 Data
The Data message contains an SS7 MTP2-User Protocol Data Unit (PDU). The Data message contains an SS7 MTP2-User Protocol Data Unit (PDU).
The Data message contains the following parameter: The Data message contains the following parameter:
Protocol Data (mandatory) Protocol Data (mandatory)
Correlation Id (optional) Correlation Id (optional)
The format for the Data Message parameters is as follows: The format for the Data Message parameters is as follows:
0 1 2 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 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x300) | Length | | Tag (0x300) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \ / \
\ Protocol Data / \ Protocol Data /
/ \ / \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x311) | Length = 8 | | Tag (0x13) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Correlation Id | | Correlation Id |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Protocol Data field contains the MTP2-User application message in The Protocol Data field contains the MTP2-User application message in
network byte order starting with the Signalling Information Octet (SIO). network byte order starting with the Signalling Information Octet
The Correlation Id parameter uniquely identifies the MSU carried in the (SIO). The Correlation Id parameter uniquely identifies the MSU
Protocol Data within an AS. This Correlation Id parameter is assigned carried in the Protocol Data within an AS. This Correlation Id
by the sending M2UA. The purpose of the Correlation Id is to permit parameter is assigned by the sending M2UA. The purpose of the
the newly active ASP to synchronize its processing of the traffic in Correlation Id is to permit the newly active ASP to synchronize its
each ordered stream with other ASPs in the broadcast group. processing of the traffic in each ordered stream with other ASPs in
the broadcast group.
The format for a Data Message with TTC PDU parameters is as follows: The format for a Data Message with TTC PDU parameters is as follows:
0 1 2 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 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x301) | Length | | Tag (0x301) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \ / \
\ Protocol Data / \ TTC Protocol Data /
/ \ / \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x13) | Length = 8 | | Tag (0x13) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Correlation Id | | Correlation Id |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Protocol Data field contains the MTP2-User application message in The Protocol Data field contains the MTP2-User application message in
network byte order starting with the Length Indicator (LI) octet. network byte order starting with the Length Indicator (LI) octet.
The Japanese TTC variant uses the spare bits of the LI octet for The Japanese TTC variant uses the spare bits of the LI octet for
priority. The length of the Protocol Data MUST NOT exceed the length priority.
of a MTP2-User application message [2] [3].
The length of the Protocol Data and TTC Protocol Data MUST NOT exceed
the length of a MTP2-User application message [2,3,5].
3.3.1.2 Data Acknowledge Message 3.3.1.2 Data Acknowledge Message
The Data Acknowledge message contains the Correlation Id of the Data The Data Acknowledge message contains the Correlation Id of the Data
message which the sending M2UA is acknowledging as successfully message that the sending M2UA is acknowledging as successfully
processed to the peer M2UA. processed to the peer M2UA.
The Data Acknowledge message contains the following parameter: The Data Acknowledge message contains the following parameter:
Correlation Id Mandatory Correlation Id Mandatory
The following format MUST be used for the Data Ack Message: The following format MUST be used for the Data Ack Message:
0 1 2 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 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x13) | Length = 8 | | Tag (0x13) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Correlation Id | | Correlation Id |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Correlation Id parameter of the Data message and the Data Ack The Correlation Id parameter of the Data message and the Data Ack
message provide a mechanism, for those SG implementations capable for message provide a mechanism, for those SG implementations capable of
taking advantage of them, to obtain an acknowledgement that the MSU taking advantage of them, to obtain an acknowledgment that the MSU
has been transferred to the M2UA peer before acknowleding the MSU to has been transferred to the M2UA peer before acknowledging the MSU to
the SS7 peer, removing the risk of losing messages due to association the SS7 peer, removing the risk of losing messages due to association
failure or SCTP congestion. failure or SCTP congestion.
The Data Ack message MUST be sent if a Correlation Id parameter is The Data Ack message MUST be sent if a Correlation Id parameter is
received from the peer. Otherwise, the Data Ack message MUST NOT be received from the peer. Otherwise, the Data Ack message MUST NOT be
sent. sent.
If the Data Acknowledge is not sent for Correlation Id(s) or is sent If the Data Acknowledge is not sent for Correlation Id(s) or is sent
with Invalid Correlation Id(s), the SS7 link will eventually fail with Invalid Correlation Id(s), the SS7 link will eventually fail due
dueto lack of MTP Level 2 acknowledgements of the SS7 peer's MSUs. to lack of MTP Level 2 acknowledgments of the SS7 peer's MSUs.
3.3.1.3 Establish (Request, Confirmation) 3.3.1.3 Establish (Request, Confirmation)
The Establish Request message is used to establish the SS7 link or to The Establish Request message is used to establish the SS7 link or to
indicate that the channel has been established. The MGC controls the indicate that the channel has been established. The MGC controls the
state of the SS7 link. When the MGC desires the SS7 link to be state of the SS7 link. When the MGC desires the SS7 link to be in-
in-service, it will send the Establish Request message. Note that service, it will send the Establish Request message. Note that the
the SGP MAY already have the SS7 link established at its layer. SGP MAY already have the SS7 link established at its layer. If so,
If so, upon receipt of an Establish Request, the SGP takes no action upon receipt of an Establish Request, the SGP takes no action except
except to send an Establish Confirm. to send an Establish Confirm.
When the MGC sends an M2UA Establish Request message, the MGC MAY When the MGC sends an M2UA Establish Request message, the MGC MAY
start a timer. This timer would be stopped upon receipt of an M2UA start a timer. This timer would be stopped upon receipt of an M2UA
Establish Confirm. If the timer expires, the MGC would resend the Establish Confirm. If the timer expires, the MGC would resend the
M2UA Establish Request message and restart the timer. In other words, M2UA Establish Request message and restart the timer. In other
the MGC MAY continue to request the establishment of the datalink words, the MGC MAY continue to request the establishment of the data
on periodic basis until the desired state is achieved or take some link on a periodic basis until the desired state is achieved or some
other action (notify the Management Layer). other action is taken (notify the Management Layer).
The mode (Normal or Emergency) for bringing the SS7 link in service is The mode (Normal or Emergency) for bringing the SS7 link in service
defaulted to Normal. The State Request (described in Section 3.3.1.5 is defaulted to Normal. The State Request (described in Section
below) can be used to change the mode to Emergency. 3.3.1.5 below) can be used to change the mode to Emergency.
3.3.1.4 Release (Request, Indication, Confirmation) 3.3.1.4 Release (Request, Indication, Confirmation)
This Release Request message is used to release the channel. The This Release Request message is used to release the channel. The
Release Confirm and Indication messages are used to indicate that the Release Confirm and Indication messages are used to indicate that the
channel has been released. channel has been released.
3.3.1.5 State Request 3.3.1.5 State Request
The State Request message can be sent from a MGC to cause an action The State Request message can be sent from a MGC to cause an action
on a particular SS7 link supported by the Signalling Gateway Process. on a particular SS7 link supported by the Signalling Gateway Process.
The SGP sends a State Confirm to the MGC if the action has been The SGP sends a State Confirm to the MGC if the action has been
successfully completed. The State Confirm reflects that state value successfully completed. The State Confirm reflects that state value
received in the State Request message. received in the State Request message.
The State Request message contains the following parameter: The State Request message contains the following parameter:
State (mandatory) State (mandatory)
0 1 2 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 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x302) | Length = 8 | | Tag (0x302) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| State | | State |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The valid values for State are shown in the following table. The valid values for State are shown in the following table.
Define Value Description Define Value Description
STATUS_LPO_SET 0x0 Request local processor outage STATUS_LPO_SET 0x0 Request local processor outage
STATUS_LPO_CLEAR 0x1 Request local processor outage STATUS_LPO_CLEAR 0x1 Request local processor outage
recovered recovered
STATUS_EMER_SET 0x2 Request emergency alignment STATUS_EMER_SET 0x2 Request emergency alignment
STATUS_EMER_CLEAR 0x3 Request normal alignment (cancel STATUS_EMER_CLEAR 0x3 Request normal alignment (cancel
emergency) emergency)
STATUS_FLUSH_BUFFERS 0x4 Flush or clear receive, transmit STATUS_FLUSH_BUFFERS 0x4 Flush or clear receive, transmit
and retransmit queues and retransmit queues
STATUS_CONTINUE 0x5 Continue or Resume STATUS_CONTINUE 0x5 Continue or Resume
STATUS_CLEAR_RTB 0x6 Clear the retransmit queue STATUS_CLEAR_RTB 0x6 Clear the retransmit queue
STATUS_AUDIT 0x7 Audit state of link STATUS_AUDIT 0x7 Audit state of link
STATUS_CONG_CLEAR 0x8 Congestion cleared STATUS_CONG_CLEAR 0x8 Congestion cleared
STATUS_CONG_ACCEPT 0x9 Congestion accept STATUS_CONG_ACCEPT 0x9 Congestion accept
STATUS_CONG_DISCARD 0xa Congestion discard STATUS_CONG_DISCARD 0xa Congestion discard
3.3.1.6 State Confirm 3.3.1.6 State Confirm
The State Confirm message will be sent by the SGP in response to a State The State Confirm message will be sent by the SGP in response to a
Request from the MGC. The State Confirm reflects that state value State Request from the MGC. The State Confirm reflects that state
received in the State Request message. value received in the State Request message.
The State Confirm message contains the following parameter: The State Confirm message contains the following parameter:
State (mandatory) State (mandatory)
0 1 2 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 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x302) | Length = 8 | | Tag (0x302) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| State | | State |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The valid values for State are shown in the following table. The
value of the State field SHOULD reflect the value received in the
State Request message.
The valid values for State are shown in the following table. The value Define Value Description
of the State field SHOULD reflect the value received in the State STATUS_LPO_SET 0x0 Request local processor outage
Request message. STATUS_LPO_CLEAR 0x1 Request local processor outage
recovered
Define Value Description STATUS_EMER_SET 0x2 Request emergency alignment
STATUS_LPO_SET 0x0 Request local processor outage STATUS_EMER_CLEAR 0x3 Request normal alignment (cancel
STATUS_LPO_CLEAR 0x1 Request local processor outage emergency)
recovered STATUS_FLUSH_BUFFERS 0x4 Flush or clear receive, transmit
STATUS_EMER_SET 0x2 Request emergency alignment and retransmit queues
STATUS_EMER_CLEAR 0x3 Request normal alignment (cancel STATUS_CONTINUE 0x5 Continue or Resume
emergency) STATUS_CLEAR_RTB 0x6 Clear the retransmit queue
STATUS_FLUSH_BUFFERS 0x4 Flush or clear receive, transmit STATUS_AUDIT 0x7 Audit state of link
and retransmit queues STATUS_CONG_CLEAR 0x8 Congestion cleared
STATUS_CONTINUE 0x5 Continue or Resume STATUS_CONG_ACCEPT 0x9 Congestion accept
STATUS_CLEAR_RTB 0x6 Clear the retransmit queue STATUS_CONG_DISCARD 0xa Congestion discard
STATUS_AUDIT 0x7 Audit state of link
STATUS_CONG_CLEAR 0x8 Congestion cleared
STATUS_CONG_ACCEPT 0x9 Congestion accept
STATUS_CONG_DISCARD 0xa Congestion discard
3.3.1.7 State Indication 3.3.1.7 State Indication
The MTP2 State Indication message can be sent from a SGP to an ASP to The MTP2 State Indication message can be sent from a SGP to an ASP to
indicate a condition on a SS7 link. indicate a condition on a SS7 link.
The State Indication message contains the following parameter: The State Indication message contains the following parameter:
Event (mandatory) Event (mandatory)
0 1 2 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 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x303) | Length = 8 | | Tag (0x303) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Event | | Event |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The valid values for Event are shown in the following table. The valid values for Event are shown in the following table.
Define Value Description Define Value Description
EVENT_RPO_ENTER 0x1 Remote entered processor outage EVENT_RPO_ENTER 0x1 Remote entered processor outage
EVENT_RPO_EXIT 0x2 Remote exited processor outage EVENT_RPO_EXIT 0x2 Remote exited processor outage
EVENT_LPO_ENTER 0x3 Link entered processor outage EVENT_LPO_ENTER 0x3 Link entered processor outage
EVENT_LPO_EXIT 0x4 Link exited processor outage EVENT_LPO_EXIT 0x4 Link exited processor outage
3.3.1.8 Congestion Indication 3.3.1.8 Congestion Indication
The Congestion Indication message can be sent from a Signalling Gateway The Congestion Indication message can be sent from a Signalling
Process to an ASP to indicate the congestion status and discard status Gateway Process to an ASP to indicate the congestion status and
of a SS7 link. When the MSU buffer fill increases above an Onset discard status of a SS7 link. When the MSU buffer fill increases
threshold or decreases below an Abatement threshold or crosses a Discard above an Onset threshold or decreases below an Abatement threshold or
threshold in either direction, the SGP SHALL send a congestion indication crosses a Discard threshold in either direction, the SGP SHALL send a
message when it supports SS7 MTP2 variants that support multiple congestion congestion indication message when it supports SS7 MTP2 variants that
levels. support multiple congestion levels.
The SGP SHALL send the message only when there is actually a change The SGP SHALL send the message only when there is actually a change
in either the discard level or the congestion level to report, in either the discard level or the congestion level to report,
meaning it is different from the previously sent message. In addition, meaning it is different from the previously sent message. In
the SGP SHALL use an implementation dependent algorithm to limit the addition, the SGP SHALL use an implementation dependent algorithm to
frequency of congestion indication messages. limit the frequency of congestion indication messages.
An implementation may optionally send Congestion Indication messages on An implementation may optionally send Congestion Indication messages
a "high priority" stream in order to potentially reduce delay. on a "high priority" stream in order to potentially reduce delay.
The Congestion Indication message contains the following parameters: The Congestion Indication message contains the following parameters:
Congestion Status (mandatory) Congestion Status (mandatory)
Discard Status (optional) Discard Status (optional)
0 1 2 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 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x304) | Length = 8 | | Tag (0x304) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Congestion Status | | Congestion Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x305) | Length = 8 | | Tag (0x305) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Discard Status | | Discard Status |
skipping to change at page 23, line 16 skipping to change at page 28, line 41
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x304) | Length = 8 | | Tag (0x304) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Congestion Status | | Congestion Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x305) | Length = 8 | | Tag (0x305) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Discard Status | | Discard Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The valid values for Congestion Status and Discard Status are shown in The valid values for Congestion Status and Discard Status are shown
the following table. in the following table.
Define Value Description Define Value Description
LEVEL_NONE 0x0 No congestion LEVEL_NONE 0x0 No congestion
LEVEL_1 0x1 Congestion Level 1 LEVEL_1 0x1 Congestion Level 1
LEVEL_2 0x2 Congestion Level 2 LEVEL_2 0x2 Congestion Level 2
LEVEL_3 0x3 Congestion Level 3 LEVEL_3 0x3 Congestion Level 3
For SS7 networks that do not support multiple levels of congestion, only For SS7 networks that do not support multiple levels of congestion,
the LEVEL_NONE and LEVEL_3 values will be used. For SS7 networks that only the LEVEL_NONE and LEVEL_3 values will be used. For SS7
support multiple levels of congestion, it is possible for all values to networks that support multiple levels of congestion, it is possible
be used. Refer to [2], [3] and [12] for more details on the Congestion for all values to be used. Refer to [2], [3] and [12] for more
and Discard Status of SS7 signalling links. details on the Congestion and Discard Status of SS7 signalling links.
3.3.1.9 Retrieval Request 3.3.1.9 Retrieval Request
The MTP2 Retrieval Request message is used during the MTP Level 3 The MTP2 Retrieval Request message is used during the MTP Level 3
changeover procedure to request the BSN, to retrieve PDUs from the changeover procedure to request the BSN, to retrieve PDUs from the
transmit and retransmit queues or to flush PDUs from the retransmit transmit and retransmit queues or to flush PDUs from the retransmit
queue. Examples of the use of Retrieval Request for SS7 Link queue. Examples of the use of Retrieval Request for SS7 Link
Changeover are provided in Section 5.3.6. Changeover are provided in Section 5.3.6.
The Retrieval Request message contains the following parameters: The Retrieval Request message contains the following parameters:
Action (mandatory) Action (mandatory)
Sequence Number (optional) Sequence Number (optional)
0 1 2 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 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x306) | Length = 8 | | Tag (0x306) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Action | | Action |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x307) | Length = 8 | | Tag (0x307) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number | | Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The valid values for Action are shown in the following table. The valid values for Action are shown in the following table.
Define Value Description Define Value Description
ACTION_RTRV_BSN 0x1 Retrieve the backward sequence number ACTION_RTRV_BSN 0x1 Retrieve the backward sequence number
ACTION_RTRV_MSGS 0x2 Retrieve the PDUs from the transmit ACTION_RTRV_MSGS 0x2 Retrieve the PDUs from the transmit
and retransmit queues and retransmit queues
In the Retrieval Request message, the Sequence Number field SHOULD NOT In the Retrieval Request message, the Sequence Number field SHOULD
be present if the Action field is ACTION_RTRV_BSN. The Sequence Number NOT be present if the Action field is ACTION_RTRV_BSN. The Sequence
field contains the Forward Sequence Number (FSN) of the far end if the Number field contains the Forward Sequence Number (FSN) of the far
Action is ACTION_RTRV_MSGS. end if the Action is ACTION_RTRV_MSGS.
3.3.1.10 Retrieval Confirm 3.3.1.10 Retrieval Confirm
The MTP2 Retrieval Confirm message is sent by the Signalling Gateway The MTP2 Retrieval Confirm message is sent by the Signalling Gateway
in response to a Retrieval Request message. Examples of the use of in response to a Retrieval Request message. Examples of the use of
Retrieval Confirm for SS7 Link Changeover are provided in Section the Retrieval Confirm for SS7 Link Changeover are provided in Section
5.3.6. 5.3.6.
The Retrieval Confirm message contains the following parameters: The Retrieval Confirm message contains the following parameters:
Action (mandatory) Action (mandatory)
Result (mandatory) Result (mandatory)
Sequence Number (optional) Sequence Number (optional)
0 1 2 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 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x306) | Length = 8 | | Tag (0x306) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 24, line 46 skipping to change at page 30, line 34
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x308) | Length = 8 | | Tag (0x308) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Result | | Result |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x307) | Length = 8 | | Tag (0x307) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number | | Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The valid values for Action are the same as in Retrieval Request. The valid values for Action are the same as in Retrieval Request.
The values for Result are shown below: in the following table. The values for Result are shown below:
Define Value Description Define Value Description
RESULT_SUCCESS 0x0 Action successful RESULT_SUCCESS 0x0 Action successful
RESULT_FAILURE 0x1 Action failed RESULT_FAILURE 0x1 Action failed
When the Signalling Gateway Process sends a Retrieval Confirm to a When the Signalling Gateway Process sends a Retrieval Confirm to a
Retrieval Request, it echos the Action field. If the Action was Retrieval Request, it echos the Action field. If the Action was
ACTION_RTRV_BSN and the SGP successfully retrieved the BSN, the SGP ACTION_RTRV_BSN and the SGP successfully retrieved the BSN, the SGP
will put the Backward Sequence Number (BSN) in the Sequence Number will put the Backward Sequence Number (BSN) in the Sequence Number
field and will indicate a success in the Result field. If the BSN field and will indicate a success in the Result field. If the BSN
could not be retrieved, the Sequence Number field will not be included could not be retrieved, the Sequence Number field will not be
and the Result field will indicate failure. included and the Result field will indicate failure.
For a Retrieval Confirm with Action of ACTION_RTRV_MSGS, the value of For a Retrieval Confirm with Action of ACTION_RTRV_MSGS, the value of
the Result field will indicate success or failure. A failure means the Result field will indicate success or failure. A failure means
that the buffers could not be retrieved. The Sequence Number field is that the buffers could not be retrieved. The Sequence Number field
not used with ACTION_RTRV_MSGS. is not used with ACTION_RTRV_MSGS.
3.3.1.11 Retrieval Indication 3.3.1.11 Retrieval Indication
The Retrieval Indication message is sent by the Signalling Gateway with The Retrieval Indication message is sent by the Signalling Gateway
a PDU from the transmit or retransmit queue. The Retrieval Indication with a PDU from the transmit or retransmit queue. The Retrieval
message does not contain the Action or seq_num fields, just a MTP3 Indication message does not contain the Action or Sequence Number
Protocol Data Unit (PDU) from the transmit or retransmit queue. fields, just a MTP3 Protocol Data Unit (PDU) from the transmit or
Examples of the use of Retrieval Indication for SS7 Link Changeover are retransmit queue. Examples of the use of the Retrieval Indication
provided in Section 5.3.6. for SS7 Link Changeover are provided in Section 5.3.6.
0 1 2 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 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x300) | Length | | Tag (0x300) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \ / \
\ Protocol Data / \ Protocol Data /
/ \ / \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
For TTC Data messages, the following parameter will be used to indicate For TTC Data messages, the following parameter will be used to
a TTC PDU which starts at LI. indicate a TTC PDU which starts at LI.
0 1 2 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 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x301) | Length | | Tag (0x301) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \ / \
\ TTC Protocol Data / \ TTC Protocol Data /
/ \ / \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The M2UA implementation MAY consider the use of the bundling feature The M2UA implementation MAY consider the use of the bundling feature
of SCTP for Retrieval Indication messages. of SCTP for Retrieval Indication messages.
3.3.1.12 Retrieval Complete Indication 3.3.1.12 Retrieval Complete Indication
The MTP2 Retrieval Complete Indication message is exactly the same as The MTP2 Retrieval Complete Indication message is exactly the same as
the MTP2 Retrieval Indication message except that it also indicates the MTP2 Retrieval Indication message except that it also indicates
that retrieval is complete. In addition, it MAY contain a PDU (which that retrieval is complete. In addition, it MAY contain a PDU (which
MUST be the last PDU) from the transmit or retransmit queue. MUST be the last PDU) from the transmit or retransmit queue.
3.3.2 Application Server Process Maintenance (ASPM) Messages 3.3.2 Application Server Process Maintenance (ASPM) Messages
The ASPM messages will only use the common message header. The ASPM messages will only use the common message header.
3.3.2.1 ASP Up (ASPUP) 3.3.2.1 ASP Up (ASPUP)
The ASP Up (ASPUP) message is used to indicate to a remote M2UA peer The ASP Up (ASPUP) message is used to indicate to a remote M2UA peer
that the Adaptation layer is ready to receive traffic or maintenance that the Adaptation layer is ready to receive traffic or maintenance
messages. messages.
The ASPUP message contains the following parameters The ASPUP message contains the following parameters
ASP Identifier (optional) ASP Identifier (optional)
Info String (optional) Info String (optional)
Note: The ASP Identifier MUST be used where the SGP cannot Note: The ASP Identifier MUST be used where the SGP cannot
identify the ASP by pre-configured address/port number identify the ASP by pre-configured address/port number
information (e.g., where an ASP is resident on a Host using information (e.g., where an ASP is resident on a Host using
dynamic address/port number assignment). dynamic address/port number assignment).
The format for ASPUP Message parameters is as follows: The format for ASPUP Message parameters is as follows:
0 1 2 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 0 1 2 3 4 5 6 7 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 (0xe) | Length | | Tag (0x11) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ASP Identifier* | | ASP Identifier* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length | | Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \ / \
\ INFO String* / \ INFO String* /
/ \ / \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The optional ASP Identifier parameter would contain a unique value The optional ASP Identifier parameter would contain a unique value
that is locally significant among the ASPs that support an AS. The 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 SGP should save the ASP Identifier to be used, if necessary, with the
Notify message (see Section 3.3.3.2). Notify message (see Section 3.3.3.2).
The optional INFO String parameter can carry any meaningful UTF-8 [6] The optional INFO String parameter can carry any meaningful UTF-8 [6]
character string along with the message. Length of the INFO String character string along with the message. Length of the INFO String
parameter is from 0 to 255 octets. No procedures are presently parameter is from 0 to 255 octets. No procedures are presently
identified for its use but the INFO String MAY be used for debugging identified for its use but the INFO String MAY be used for debugging
purposes. purposes.
3.3.2.2 ASP Up Ack 3.3.2.2 ASP Up Ack
The ASP Up Ack message is used to acknowledge an ASP Up message The ASP Up Ack message is used to acknowledge an ASP Up message
received from a remote M2UA peer. received from a remote M2UA peer.
The ASPUP Ack message contains the following parameters: The ASPUP Ack message contains the following parameters:
INFO String (optional) INFO String (optional)
The format for ASPUP Ack Message parameters is as follows: The format for ASPUP Ack Message parameters is as follows:
0 1 2 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 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length | | Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \ / \
\ INFO String* / \ INFO String* /
/ \ / \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format and description of the optional Info String parameter is the The format and description of the optional Info String parameter is
same as for the ASP UP message (See Section 3.3.2.1). the same as for the ASP UP message (See Section 3.3.2.1).
3.3.2.3 ASP Down (ASPDN) 3.3.2.3 ASP Down (ASPDN)
The ASP Down (ASPDN) message is used to indicate to a remote M2UA peer The ASP Down (ASPDN) message is used to indicate to a remote M2UA
that the adaptation layer is not ready to receive traffic or peer that the adaptation layer is not ready to receive traffic or
maintenance messages. maintenance messages.
The ASPDN message contains the following parameters The ASPDN message contains the following parameters
INFO String (optional) INFO String (optional)
The format for the ASPDN message parameters is as follows: The format for the ASPDN message parameters is as follows:
0 1 2 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 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length | | Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \ / \
\ INFO String* / \ INFO String* /
/ \ / \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format and description of the optional Info String parameter is the The format and description of the optional Info String parameter is
same as for the ASP Up message (See Section 3.3.2.1). the same as for the ASP Up message (See Section 3.3.2.1).
3.3.2.4 ASP Down Ack 3.3.2.4 ASP Down Ack
The ASP Down Ack message is used to acknowledge an ASP Down message The ASP Down Ack message is used to acknowledge an ASP Down message
received from a remote M2UA peer. received from a remote M2UA peer.
The ASP Down Ack message contains the following parameters: The ASP Down Ack message contains the following parameters:
INFO String (optional) INFO String (optional)
The format for the ASPDN Ack message parameters is as follows: The format for the ASPDN Ack message parameters is as follows:
0 1 2 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 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length | | Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \ / \
\ INFO String* / \ INFO String* /
/ \ / \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format and description of the optional Info String parameter is the The format and description of the optional Info String parameter is
same as for the ASP UP message (See Section 3.3.2.1). the same as for the ASP UP message (See Section 3.3.2.1).
3.3.2.5 Heartbeat (BEAT) 3.3.2.5 Heartbeat (BEAT)
The Heartbeat message is optionally used to ensure that the M2UA The Heartbeat message is optionally used to ensure that the M2UA
peers are still available to each other. peers are still available to each other.
The BEAT message contains the following parameter: The BEAT message contains the following parameter:
Heartbeat Data Optional Heartbeat Data Optional
The format for the BEAT message is as follows: The format for the BEAT message is as follows:
0 1 2 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 0 1 2 3 4 5 6 7 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 | | Tag = 0x0009 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Heartbeat Data / / Heartbeat Data /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The sending node defines the Heartbeat Data field contents. It may The sending node defines the Heartbeat Data field contents. It may
include a Heartbeat Sequence Number and/or Timestamp, or other include a Heartbeat Sequence Number and/or time stamp, or other
implementation specific details. implementation specific details.
The receiver of a Heartbeat message does not process this field as The receiver of a Heartbeat message does not process this field as it
it is only of significance to the sender. The receiver echoes the is only of significance to the sender. The receiver echoes the
content of the Heartbeat Data in a BEAT ACK message. content of the Heartbeat Data in a BEAT ACK message.
3.3.2.6 Heartbeat Ack (BEAT ACK) 3.3.2.6 Heartbeat Ack (BEAT ACK)
The Heartbeat ACK message is sent in response to a BEAT message. A 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 peer MUST send a BEAT ACK in response to a BEAT message. It includes
all the parameters of the received Heartbeat message, without any all the parameters of the received Heartbeat message, without any
change. change.
The BEAT ACK message contains the following parameter: The BEAT ACK message contains the following parameter:
Heartbeat Data Optional Heartbeat Data Optional
The format for the BEAT ACK message is as follows: The format for the BEAT ACK message is as follows:
0 1 2 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 0 1 2 3 4 5 6 7 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 | | Tag = 0x0009 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Heartbeat Data / / Heartbeat Data /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The sending node defines the Heartbeat Data field contents. It may The sending node defines the Heartbeat Data field contents. It may
include a Heartbeat Sequence Number and/or Timestamp, or other include a Heartbeat Sequence Number and/or time stamp, or other
implementation specific details. implementation specific details.
The receiver of a Heartbeat message does not process this field as The receiver of a Heartbeat message does not process this field as it
it is only of significance to the sender. The receiver echoes the is only of significance to the sender. The receiver echoes the
content of the Heartbeat Data in a BEAT ACK message. content of the Heartbeat Data in a BEAT ACK message.
3.3.2.7 ASP Active (ASPAC) 3.3.2.7 ASP Active (ASPAC)
The ASPAC message is sent by an ASP to indicate to an SGP that it is The ASPAC message is sent by an ASP to indicate to an SGP that it is
Active and ready to be used. Active and ready to be used.
The ASPAC message contains the following parameters: The ASPAC message contains the following parameters:
Traffic Mode Type (optional) Traffic Mode Type (optional)
Interface Identifier (optional) Interface Identifier (optional)
- Combination of integer and integer ranges, OR - Combination of integer and integer ranges, OR
- string (text formatted) - string (text formatted)
INFO String (optional) INFO String (optional)
The format for the ASPAC message using integer formatted Interface The format for the ASPAC message using integer formatted Interface
Identifiers is as follows: Identifiers is as follows:
0 1 2 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 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0xb) | Length | | Tag (0xb) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Traffic Mode Type | | Traffic Mode Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x1=integer) | Length | | Tag (0x1=integer) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \ / \
\ Interface Identifiers* / \ Interface Identifiers* /
/ \ / \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x8=integer range) | Length | | Tag (0x8=integer range) | Length |
skipping to change at page 30, line 47 skipping to change at page 37, line 4
\ Additional Interface Identifiers / \ Additional Interface Identifiers /
/ of Tag Type 0x1 or 0x8 \ / of Tag Type 0x1 or 0x8 \
\ / \ /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length | | Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \ / \
\ INFO String* / \ INFO String* /
/ \ / \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format for the ASPAC message using text formatted (string)
The format for the ASPAC message using text formatted (string) Interface Identifiers is as follows:
Interface Identifiers is as follows:
0 1 2 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 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0xb) | Length | | Tag (0xb) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Traffic Mode Type | | Traffic Mode Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x3=string) | Length | | Tag (0x3=string) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 31, line 30 skipping to change at page 37, line 32
/ of Tag Type 0x3 \ / of Tag Type 0x3 \
\ / \ /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length | | Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \ / \
\ INFO String* / \ INFO String* /
/ \ / \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Traffic Mode Type parameter identifies the traffic mode of The Traffic Mode Type parameter identifies the traffic mode of
operation of the ASP within an AS. The valid values for Type are operation of the ASP within an AS. The valid values for Type are
shown in the following table: shown in the following table:
Value Description Value Description
0x1 Override 0x1 Override
0x2 Load-share 0x2 Load-share
0x3 Broadcast 0x3 Broadcast
Within a particular AS, only one Traffic Mode Type can be used. Within a particular AS, only one Traffic Mode Type can be used. The
The Override value indicates that the ASP is operating in Override Override value indicates that the ASP is operating in Override mode,
mode, where the ASP takes over all traffic in an Application Server where the ASP takes over all traffic in an Application Server (i.e.,
(i.e., primary/backup operation), over-riding any currently active primary/backup operation), over-riding any currently active ASPs in
ASPs in the AS. In Load-share mode, the ASP will share in the traffic the AS. In Load-share mode, the ASP will share in the traffic
distribution with any other currently active ASPs. In Broadcast mode, distribution with any other currently active ASPs. In Broadcast
all of the Active ASPs receive all message traffic in the Application mode, all of the Active ASPs receive all message traffic in the
Server. Application Server.
The optional Interface Identifiers parameter contains a list of The optional Interface Identifiers parameter contains a list of
Interface Identifier integers (Type 0x1 or Type 0x8) or text strings Interface Identifier integers (Type 0x1 or Type 0x8) or text strings
(Type 0x3)indexing the Application Server traffic that the sending (Type 0x3)indexing the Application Server traffic that the sending
ASP is configured/registered to receive. If integer formatted ASP is configured/registered to receive. If integer formatted
Interface Identifiers are being used, the ASP can also send ranges of Interface Identifiers are being used, the ASP can also send ranges of
Interface Identifiers (Type 0x8). Interface Identifier types Integer Interface Identifiers (Type 0x8). Interface Identifier types Integer
(0x1) and Integer Range (0x8) are allowed in the same message. Text (0x1) and Integer Range (0x8) are allowed in the same message. Text
formatted Interface Identifiers (0x3) cannot be used with either formatted Interface Identifiers (0x3) cannot be used with either
Integer (0x1) or Integer Range (0x8) types. Integer (0x1) or Integer Range (0x8) types.
If no Interface Identifiers are included, the message is for all If no Interface Identifiers are included, the message is for all
provisioned Interface Identifiers within the AS(s) in which the provisioned Interface Identifiers within the AS(s) in which the ASP
ASP is provisioned. If only a subset of Interface Identifiers for an is provisioned. If only a subset of Interface Identifiers for an AS
AS are included, the ASP is noted as Active for all the Interface are included, the ASP is noted as Active for all the Interface
Identifiers provisioned for that AS. Identifiers provisioned for that AS.
Note: If the optional Interface Identifier parameter is present, the Note: If the optional Interface Identifier parameter is present, the
integer formatted Interface Identifier MUST be supported, while the integer formatted Interface Identifier MUST be supported, while
text formatted Interface Identifier MAY be supported. the text formatted Interface Identifier MAY be supported.
An SGP that receives an ASPAC with an incorrect or unsupported Traffic An SGP that receives an ASPAC with an incorrect or unsupported
Mode Type for a particular Interface Identifier will respond with an Traffic Mode Type for a particular Interface Identifier will respond
Error Message (Cause: Unsupported Traffic Handling Mode). with an Error Message (Cause: Unsupported Traffic Handling Mode).
The format and description of the optional Info String parameter is the The format and description of the optional Info String parameter is
same as for the ASP UP message (See Section 3.3.2.1). the same as for the ASP UP message (See Section 3.3.2.1).
3.3.2.8 ASP Active Ack 3.3.2.8 ASP Active Ack
The ASP Active (ASPAC) Ack message is used to acknowledge an ASP Active The ASP Active (ASPAC) Ack message is used to acknowledge an ASP
message received from a remote M2UA peer. Active message received from a remote M2UA peer.
The ASPAC Ack message contains the following parameters: The ASPAC Ack message contains the following parameters:
Traffic Mode Type (optional) Traffic Mode Type (optional)
Interface Identifier (optional) Interface Identifier (optional)
- Combination of integer and integer ranges, OR - Combination of integer and integer ranges, OR
- string (text formatted) - string (text formatted)
INFO String (optional) INFO String (optional)
The format for the ASPAC Ack message with Integer-formatted Interface The format for the ASPAC Ack message with Integer-formatted Interface
Identifiers is as follows: Identifiers is as follows:
0 1 2 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 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0xb) | Length | | Tag (0xb) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Traffic Mode Type | | Traffic Mode Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x1=integer) | Length | | Tag (0x1=integer) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \ / \
\ Interface Identifiers* / \ Interface Identifiers* /
/ \ / \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x8=integer range) | Length | | Tag (0x8=integer range) | Length |
skipping to change at page 34, line 4 skipping to change at page 40, line 4
\ Additional Interface Identifiers / \ Additional Interface Identifiers /
/ of Tag Type 0x1 or 0x8 \ / of Tag Type 0x1 or 0x8 \
\ / \ /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length | | Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \ / \
\ INFO String* / \ INFO String* /
/ \ / \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format for the ASP Active Ack message using text formatted
The format for the ASP Active Ack message using text formatted (string) (string) Interface Identifiers is as follows:
Interface Identifiers is as follows:
0 1 2 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 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0xb) | Length | | Tag (0xb) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Traffic Mode Type | | Traffic Mode Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x3=string) | Length | | Tag (0x3=string) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 34, line 33 skipping to change at page 40, line 32
/ of Tag Type 0x3 \ / of Tag Type 0x3 \
\ / \ /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length | | Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \ / \
\ INFO String* / \ INFO String* /
/ \ / \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format and description of the optional Info String parameter is the The format and description of the optional Info String parameter is
same as for the ASP Up message (See Section 3.3.2.1). the same as for the ASP Up message (See Section 3.3.2.1).
The format of the Traffic Mode Type and Interface Identifier parameters The format of the optional Interface Identifier parameter is the same
is the same as for the ASP Active message (See Section 3.3.2.5). as for the ASP Active message (See Section 3.3.2.7).
The format and description of the optional Info String parameter is
the same as for the ASP Up message (See Section 3.3.2.1).
3.3.2.9 ASP Inactive (ASPIA) 3.3.2.9 ASP Inactive (ASPIA)
The ASP Inactive (ASPIA) message is sent by an ASP to indicate to an The ASP Inactive (ASPIA) message is sent by an ASP to indicate to an
SGP that it is no longer an active ASP to be used from within a list SGP that it is no longer an active ASP to be used from within a list
of ASPs. The SGP will respond with an ASPIA Ack message and either of ASPs. The SGP will respond with an ASPIA Ack message and either
discard incoming messages or buffer for a timed period and then discard incoming messages or buffer for a timed period and then
discard. discard.
The ASPIA message contains the following parameters: The ASPIA message contains the following parameters:
Interface Identifiers (optional) Interface Identifiers (optional)
- Combination of integer and integer ranges, OR - Combination of integer and integer ranges, OR
- string (text formatted) - string (text formatted)
INFO String (optional) INFO String (optional)
The format for the ASP Inactive message parameters using Integer The format for the ASP Inactive message parameters using Integer
formatted Interface Identifiers is as follows: formatted Interface Identifiers is as follows:
0 1 2 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 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x1=integer) | Length | | Tag (0x1=integer) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \ / \
\ Interface Identifiers* / \ Interface Identifiers* /
/ \ / \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 35, line 43 skipping to change at page 42, line 4
\ Additional Interface Identifiers / \ Additional Interface Identifiers /
/ of Tag Type 0x1 or 0x8 \ / of Tag Type 0x1 or 0x8 \
\ / \ /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length | | Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \ / \
\ INFO String* / \ INFO String* /
/ \ / \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format for the ASP Inactive message using text formatted (string)
The format for the ASP Inactive message using text formatted (string) Interface Identifiers is as follows:
Interface Identifiers is as follows:
0 1 2 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 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x3=string) | Length | | Tag (0x3=string) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \ / \
\ Interface Identifier* / \ Interface Identifier* /
/ \ / \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 36, line 5 skipping to change at page 42, line 28
/ of Tag Type 0x3 \ / of Tag Type 0x3 \
\ / \ /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length | | Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \ / \
\ INFO String* / \ INFO String* /
/ \ / \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format and description of the optional Interface Identifiers and The format of the optional Interface Identifier parameter is the same
Info String parameters is the same as for the ASP Active message (See as for the ASP Active message (See Section 3.3.2.7).
Section 3.3.2.3).
The optional Interface Identifiers parameter contains a list of The format and description of the optional Info String parameter is
Interface Identifier integers indexing the Application Server traffic the same as for the ASP Up message (See Section 3.3.2.1).
that the sending ASP is configured/registered to receive, but does not
want to receive at this time. The optional Interface Identifiers parameter contains a list of
Interface Identifier integers indexing the Application Server traffic
that the sending ASP is configured/registered to receive, but does
not want to receive at this time.
3.3.2.10 ASP Inactive Ack 3.3.2.10 ASP Inactive Ack
The ASP Inactive (ASPIA) Ack message is used to acknowledge an ASP The ASP Inactive (ASPIA) Ack message is used to acknowledge an ASP
Inactive message received from a remote M2UA peer. Inactive message received from a remote M2UA peer.
The ASPIA Ack message contains the following parameters: The ASPIA Ack message contains the following parameters:
Interface Identifiers (optional) Interface Identifiers (optional)
- Combination of integer and integer ranges, OR - Combination of integer and integer ranges, OR
- string (text formatted) - string (text formatted)
INFO String (optional) INFO String (optional)
The format for the ASPIA Ack message is as follows: The format for the ASPIA Ack message is as follows:
0 1 2 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 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x1=integer) | Length | | Tag (0x1=integer) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \ / \
\ Interface Identifiers* / \ Interface Identifiers* /
/ \ / \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 37, line 4 skipping to change at page 44, line 4
\ Additional Interface Identifiers / \ Additional Interface Identifiers /
/ of Tag Type 0x1 or 0x8 \ / of Tag Type 0x1 or 0x8 \
\ / \ /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length | | Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \ / \
\ INFO String* / \ INFO String* /
/ \ / \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format for the ASP Inactive Ack message using text formatted
The format for the ASP Inactive Ack message using text formatted (string) Interface Identifiers is as follows:
(string) Interface Identifiers is as follows:
0 1 2 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 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x3=string) | Length | | Tag (0x3=string) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \ / \
\ Interface Identifier* / \ Interface Identifier* /
/ \ / \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 37, line 29 skipping to change at page 44, line 28
/ of Tag Type 0x3 \ / of Tag Type 0x3 \
\ / \ /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length | | Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \ / \
\ INFO String* / \ INFO String* /
/ \ / \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format of the Interface Identifier parameter is the same as for The format of the optional Interface Identifier parameter is the same
the ASP Inactive message (See Section 3.3.2.7). as for the ASP Active message (See Section 3.3.2.7).
The format and description of the optional Info String parameter is The format and description of the optional Info String parameter is
the same as for the ASP Up message (See Section 3.3.2.1). the same as for the ASP Up message (See Section 3.3.2.1).
3.3.3 Layer Management (MGMT) Messages 3.3.3 Layer Management (MGMT) Messages
3.3.3.1 Error (ERR) 3.3.3.1 Error (ERR)
The Error (ERR) message is used to notify a peer of an error event The Error (ERR) message is used to notify a peer of an error event
associated with an incoming message. For example, the message type associated with an incoming message. For example, the message type
might be unexpected given the current state, or a parameter value might might be unexpected given the current state, or a parameter value
be invalid. might be invalid.
The ERR message contains the following parameters: An Error message MUST not be generated in response to other Error
messages.
Error Code (mandatory) The ERR message contains the following parameters:
Interface Identifier (optional)
Diagnostic Information (optional)
The format for the ERR message is as follows: Error Code (mandatory)
Interface Identifier (optional)
Diagnostic Information (optional)
The format for the ERR message is as follows:
0 1 2 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 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0xc) | Length | | Tag (0xc) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Error Code | | Error Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x1, 0x3, or 0x8) | Length | | Tag (0x1, 0x3, or 0x8) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \ / \
\ Interface Identifier(s)* / \ Interface Identifier(s)* /
/ \ / \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x7) | Length | | Tag (0x7) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \ / \
\ Diagnostic Information* / \ Diagnostic Information* /
/ \ / \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Error Code parameter indicates the reason for the Error Message. The Error Code parameter indicates the reason for the Error Message.
The Error parameter value can be one of the following values: The Error parameter value can be one of the following values:
Invalid Version 0x1 Invalid Version 0x1
Invalid Interface Identifier 0x2 Invalid Interface Identifier 0x2
Unsupported Message Class 0x3 Unsupported Message Class 0x3
Unsupported Message Type 0x4 Unsupported Message Type 0x4
Unsupported Traffic Handling Mode 0x5 Unsupported Traffic Handling Mode 0x5
Unexpected Message 0x6 Unexpected Message 0x6
Protocol Error 0x7 Protocol Error 0x7
Unsupported Interface Identifier Type 0x8 Unsupported Interface Identifier Type 0x8
Invalid Stream Identifier 0x9 Invalid Stream Identifier 0x9
Not Used in M2UA 0xa Not Used in M2UA 0xa
Not Used in M2UA 0xb Not Used in M2UA 0xb
Not Used in M2UA 0xc Not Used in M2UA 0xc
Refused - Management Blocking 0xd Refused - Management Blocking 0xd
ASP Identifier Required 0xe ASP Identifier Required 0xe
Invalid ASP Identifier 0xf Invalid ASP Identifier 0xf
ASP Active for Interface Identifier(s) 0x10 ASP Active for Interface Identifier(s) 0x10
Invalid Parameter Value 0x11 Invalid Parameter Value 0x11
Parameter Field Error 0x12 Parameter Field Error 0x12
Unexpected Parameter 0x13 Unexpected Parameter 0x13
Not Used in M2UA 0x14 Not Used in M2UA 0x14
Not Used in M2UA 0x15 Not Used in M2UA 0x15
Missing Parameter 0x16 Missing Parameter 0x16
The "Invalid Version" error would be sent if a message was The "Invalid Version" error would be sent if a message was received
received with an invalid or unsupported version. The Error message with an invalid or unsupported version. The Error message would
would contain the supported version in the Common header. The contain the supported version in the Common header. The Error
Error message could optionally provide the supported version in message could optionally provide the supported version in the
the Diagnostic Information area. Diagnostic Information area.
The "Invalid Interface Identifier" error would be sent by a SGP if The "Invalid Interface Identifier" error would be sent by a SGP if an
an ASP sends a message (i.e. an ASP Active message) with an invalid ASP sends a message (i.e. an ASP Active message) with an invalid (not
(unconfigured) Interface Identifier value. One of the optional configured) Interface Identifier value. One of the optional
Interface Identifier parameters (Integer-based, text-based or integer Interface Identifier parameters (Integer-based, text-based or integer
range) MUST be used with this error code to identify the invalid range) MUST be used with this error code to identify the invalid
Interface Identifier(s) received. Interface Identifier(s) received.
The "Unsupported Traffic Handling Mode" error would be sent by a SGP The "Unsupported Traffic Handling Mode" error would be sent by a SGP
if an ASP sends an ASP Active with an unsupported Traffic Handling if an ASP sends an ASP Active with an unsupported Traffic Handling
Mode. An example would be a case in which the SGP did not support Mode. An example would be a case in which the SGP did not support
load-sharing. One of the optional Interface Identifier parameters load-sharing. One of the optional Interface Identifier parameters
(Integer-based, text-based or integer range) MAY be used with this (Integer-based, text-based or integer range) MAY be used with this
error code to identify the Interface Identifier(s). error code to identify the Interface Identifier(s).
The "Unexpected Message" error would be sent by an ASP if it received The "Unexpected Message" error would be sent by an ASP if it received
a MAUP message from an SGP while it was in the Inactive state. a MAUP message from an SGP while it was in the Inactive state.
The "Protocol Error" error would be sent for any protocol anomaly The "Protocol Error" error would be sent for any protocol anomaly
(i.e. a bogus message). (i.e. a bogus message).
The "Invalid Stream Identifier" error would be sent if a message The "Invalid Stream Identifier" error would be sent if a message was
was received on an unexpected SCTP stream (i.e. a MGMT message received on an unexpected SCTP stream (i.e. a MGMT message was
was received on a stream other than "0"). received on a stream other than "0").
The "Unsupported Interface Identifier Type" error would be sent by The "Unsupported Interface Identifier Type" error would be sent by a
a SGP if an ASP sends a Text formatted Interface Identifier and the SGP if an ASP sends a Text formatted Interface Identifier and the SGP
SGP only supports Integer formatted Interface Identifiers. When only supports Integer formatted Interface Identifiers. When the ASP
the ASP receives this error, it will need to resend its message with receives this error, it will need to resend its message with an
an Integer formatted Interface Identifier. Integer formatted Interface Identifier.
The "Unsupported Message Class" error would be sent if a message with The "Unsupported Message Class" error would be sent if a message with
an unexpected or unsupported Message Class is received. an unexpected or unsupported Message Class is received.
The "Refused - Management Blocking" error is sent when an ASP Up or The "Refused - Management Blocking" error is sent when an ASP Up or
ASP Active message is received and the request is refused for ASP Active message is received and the request is refused for
management reasons (e.g., management lock-out"). management reasons (e.g., management lock-out").
The "ASP Identifier Required" is sent by a SGP in response The "ASP Identifier Required" is sent by a SGP in response to an
to an ASPUP message which does not contain an ASP Identifier ASPUP message which does not contain an ASP Identifier parameter when
parameter when the SGP requires one. The ASP SHOULD resend the the SGP requires one. The ASP SHOULD resend the ASPUP message with
ASPUP message with an ASP Identifier. an ASP Identifier.
The "Invalid ASP Identifier" is send by a SGP in response to an The "Invalid ASP Identifier" is sent by a SGP in response to an ASPUP
ASPUP message with an invalid (i.e. non-unique) ASP Identifier. message with an invalid (i.e. non-unique) ASP Identifier.
The "ASP Currently Active for Interface Identifier(s)" error is The "ASP Currently Active for Interface Identifier(s)" error is sent
sent by a SGP when a Deregistration request is received from an ASP by a SGP when a Deregistration request is received from an ASP that
that is active for Interface Identifier(s) specified in the is active for Interface Identifier(s) specified in the Deregistration
Deregistration request. One of the optional Interface Identifier request. One of the optional Interface Identifier parameters
parameters (Integer-based, text-based or integer range) MAY be used (Integer-based, text-based or integer range) MAY be used with this
with this error code to identify the Interface Identifier(s). error code to identify the Interface Identifier(s).
The "Invalid Parameter Value " error is sent if a message is received The "Invalid Parameter Value " error is sent if a message is received
with an invalid parameter value (e.g., a State Request with an with an invalid parameter value (e.g., a State Request with an an
an undefined State). undefined State).
The "Parameter Field Error" would be sent if a message with a The "Parameter Field Error" would be sent if a message with a
parameter that has a wrong length field. parameter has a wrong length field.
The "Unexpected Parameter" error would be sent if a message contains The "Unexpected Parameter" error would be sent if a message contains
an invalid parameter. an invalid parameter.
The "Missing Parameter" error would be sent if a mandatory parameter The "Missing Parameter" error would be sent if a mandatory parameter
were not included in a message. was not included in a message.
The optional Diagnostic information can be any information germane to The optional Diagnostic information can be any information germane to
the error condition, to assist in identification of the error condition. the error condition, to assist in the identification of the error
In the case of an Invalid Version Error Code the Diagnostic information condition. In the case of an Invalid Version Error Code the
includes the supported Version parameter. In the other cases, the Diagnostic information includes the supported Version parameter. In
Diagnostic information SHOULD be the first 40 bytes of the offending the other cases, the Diagnostic information SHOULD be the first 40
message. bytes of the offending message.
3.3.3.2 Notify (NTFY) 3.3.3.2 Notify (NTFY)
The Notify message is used to provide an autonomous indication of M2UA The Notify message is used to provide an autonomous indication of
events to an M2UA peer. M2UA events to an M2UA peer.
The NTFY message contains the following parameters: The NTFY message contains the following parameters:
Status Type (mandatory) Status Type (mandatory)
Status Information (mandatory) Status Information (mandatory)
ASP Identifier (optional) ASP Identifier (optional)
Interface Identifiers (optional) Interface Identifiers (optional)
INFO String (optional) INFO String (optional)
The format for the Notify message with Integer-formatted Interface The format for the Notify message with Integer-formatted Interface
Identifiers is as follows: Identifiers is as follows:
0 1 2 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 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0xd) | Length | | Tag (0xd) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Status Type | Status Information | | Status Type | Status Information |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0xe) | Length | | Tag (0x11) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ASP Identifier* | | ASP Identifier* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x1=integer) | Length | | Tag (0x1=integer) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \ / \
\ Interface Identifiers* / \ Interface Identifiers* /
/ \ / \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x8=integer range) | Length | | Tag (0x8=integer range) | Length |
skipping to change at page 41, line 4 skipping to change at page 49, line 4
\ Additional Interface Identifiers / \ Additional Interface Identifiers /
/ of Tag Type 0x1 or 0x8 \ / of Tag Type 0x1 or 0x8 \
\ / \ /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length | | Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \ / \
\ INFO String* / \ INFO String* /
/ \ / \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format for the Notify message with Text-formatted Interface
The format for the Notify message with Text-formatted Interface Identifiers is as follows:
Identifiers is as follows:
0 1 2 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 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0xd) | Length | | Tag (0xd) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Status Type | Status Information | | Status Type | Status Information |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0xe) | Length | | Tag (0x11) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ASP Identifier* | | ASP Identifier* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x3=string) | Length | | Tag (0x3=string) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \ / \
\ Interface Identifier* / \ Interface Identifier* /
/ \ / \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \ / \
skipping to change at page 41, line 37 skipping to change at page 49, line 36
/ of Tag Type 0x3 \ / of Tag Type 0x3 \
\ / \ /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length | | Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \ / \
\ INFO String* / \ INFO String* /
/ \ / \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Status Type parameter identifies the type of the Notify message. The Status Type parameter identifies the type of the Notify message.
The following are the valid Status Type values: The following are the valid Status Type values:
Value Description Value Description
0x1 Application Server state change (AS_State_Change) 0x1 Application Server state change (AS_State_Change)
0x2 Other 0x2 Other
The Status Information parameter contains more detailed information The Status Information parameter contains more detailed information
for the notification, based on the value of the Status Type. If the for the notification, based on the value of the Status Type. If the
Status Type is AS_State_Change the following Status Information values Status Type is AS_State_Change the following Status Information
are used: values are used:
Value Description Value Description
1 reserved 1 reserved
2 Application Server Inactive (AS_Inactive) 2 Application Server Inactive (AS_Inactive)
3 Application Server Active (AS_Active) 3 Application Server Active (AS_Active)
4 Application Server Pending (AS_Pending) 4 Application Server Pending (AS_Pending)
These notifications are sent from an SGP to an ASP upon a change in These notifications are sent from an SGP to an ASP upon a change in
status of a particular Application Server. The value reflects the status of a particular Application Server. The value reflects the
new state of the Application Server. The Interface Identifiers of new state of the Application Server. The Interface Identifiers of
the AS MAY be placed in the message if desired. the AS MAY be placed in the message if desired.
If the Status Type is Other, then the following Status Information If the Status Type is Other, then the following Status Information
values are defined: values are defined:
Value Description Value Description
1 Insufficient ASP resources active in AS 1 Insufficient ASP resources active in AS
2 Alternate ASP Active 2 Alternate ASP Active
3 ASP Failure 3 ASP Failure
In the Insufficient ASP Resources case, the SGP is indicating to an In the Insufficient ASP Resources case, the SGP is indicating to an
ASP-INACTIVE ASP(s) in the AS that another ASP is required in order to ASP-INACTIVE ASP(s) in the AS that another ASP is required in order
handle the load of the AS (Load-sharing mode). For the Alternate ASP to handle the load of the AS (Load-sharing mode). For the Alternate
Active case, the formerly Active ASP is informed when an alternate ASP Active case, the formerly Active ASP is informed when an
ASP transitions to the ASP Active state in Override mode. The ASP alternate ASP transitions to the ASP Active state in Override mode.
Identifier (if available) of the Alternate ASP MUST be placed in the The ASP Identifier (if available) of the Alternate ASP MUST be placed
message. For the ASP Failure case, the SGP is indicating to ASP(s) in the message. For the ASP Failure case, the SGP is indicating to
in the AS that one of the ASPs has transitioned to ASP-DOWN. The ASP ASP(s) in the AS that one of the ASPs has transitioned to ASP-DOWN.
Identifier (if available) of the failed ASP MUST be placed in the The ASP Identifier (if available) of the failed ASP MUST be placed in
message. the message.
For each of the Status Information values in Status Type Other, the For each of the Status Information values in Status Type Other, the
Interface Identifiers of the affected AS MAY be placed in the message Interface Identifiers of the affected AS MAY be placed in the message
if desired. if desired.
The format and description of the optional Interface Identifiers and The format of the optional Interface Identifier parameter is the same
Info String parameters is the same as for the ASP Active message as for the ASP Active message (See Section 3.3.2.7).
(See Section 3.3.2.3).
The format and description of the optional Info String parameter is
the same as for the ASP Up message (See Section 3.3.2.1).
3.3.4 Interface Identifier Management (IIM) Messages 3.3.4 Interface Identifier Management (IIM) Messages
The Interface Identifier Management messages are optional. They are The Interface Identifier Management messages are optional. They are
used to support automatic allocation of Signalling Terminals or used to support the automatic allocation of Signalling Terminals or
Signalling Data Links [2][3]. Signalling Data Links [2][3].
3.3.4.1 Registration Request (REG REQ) 3.3.4.1 Registration Request (REG REQ)
The REG REQ message is sent by an ASP to indicate to a remote M2UA The REG REQ message is sent by an ASP to indicate to a remote M2UA
peer that it wishes to register one or more given Link Keys with the peer that it wishes to register one or more given Link Keys with the
remote peer. Typically, an ASP would send this message to an SGP, remote peer. Typically, an ASP would send this message to an SGP,
and expect to receive a REG RSP in return with an associated and expect to receive a REG RSP in return with an associated
Interface Identifier value. Interface Identifier value.
The REG REQ message contains the following parameter: The REG REQ message contains the following parameter:
Link Key (mandatory) Link Key (mandatory)
The format for the REG REQ message is as follows
The format for the REG REQ message is as follows
0 1 2 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 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0309 | Length | | Tag = 0x0309 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ Link Key 1 / / Link Key 1 /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ ... / / ... /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0309 | Length | | Tag = 0x0309 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ Link Key n / / Link Key n /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Link Key: fixed length Link Key: fixed length
The Link Key parameter is mandatory. The sender of this message The Link Key parameter is mandatory. The sender of this message
expects the receiver of this message will create a Link Key entry expects that the receiver of this message will create a Link Key
and assign a unique Interface Identifier value to it, if the Link entry and assign a unique Interface Identifier value to it, if the
Key entry does not yet exist. Link Key entry does not yet exist.
The Link Key parameter may be present multiple times in the same The Link Key parameter may be present multiple times in the same
message. This is used to allow the registration of multiple Link message. This is used to allow the registration of multiple Link
Keys in a single message. Keys in a single message.
The format of the Link Key parameter is as follows: The format of the Link Key parameter is as follows:
0 1 2 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 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local-LK-Identifier | | Local-LK-Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Signalling Data Terminal Identifier | | Signalling Data Terminal Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Signalling Data Link Identifier | | Signalling Data Link Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Local-LK-Identifier: 32-bit integer Local-LK-Identifier: 32-bit integer
The mandatory Local-LK-Identifier field is used to uniquely The mandatory Local-LK-Identifier field is used to uniquely
(between ASP and SGP) identify the registration request. The (between ASP and SGP) identify the registration request. The
Identifier value is assigned by the ASP, and is used to correlate Identifier value is assigned by the ASP, and is used to correlate
the response in a REG RSP message with the original registration the response in a REG RSP message with the original registration
request. The Identifier value MUST remain unique until the REG request. The Identifier value MUST remain unique until the REG
RSP is received. RSP is received.
The format of the Local-LK-Identifier field is as follows: The format of the Local-LK-Identifier field is as follows:
0 1 2 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 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x030a | Length = 8 | | Tag = 0x030a | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local-LK-Identifier value | | Local-LK-Identifier value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Signalling Data Terminal Identifier
Signalling Data Terminal Identifier The Signalling Data Terminal Identifier parameter is mandatory.
It identifies the Signalling Data Terminal associated with the SS7
The Signalling Data Terminal Identifier parameter is mandatory. link for which the ASP is registering. The format is as follows:
It identifies the Signalling Data Terminal associated with the
SS7 link for which the ASP is registering. The format is as
follows:
0 1 2 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 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x030b | Length = 8 | | Tag = 0x030b | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | SDT Identifier | | Reserved | SDT Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The SDT Identifier is a 32-bit unsigned value which may only be The SDT Identifier is a 32-bit unsigned value which may only be
significant to 12 or 14 bits depending on the SS7 variant which significant to 12 or 14 bits depending on the SS7 variant which is
is supported by the MTP Level 3 at the ASP. Insignificant SDTI supported by the MTP Level 3 at the ASP. Insignificant SDT
bits are coded 0. Identifier bits are coded 0.
Signalling Data Link Identifier Signalling Data Link Identifier
The Signalling Data Link Identifier parameter is mandatory. It The Signalling Data Link Identifier parameter is mandatory. It
identifies the Signalling Data Link Identifier associated with identifies the Signalling Data Link Identifier associated with the
the SS7 link for which the ASP is registering. The format is as SS7 link for which the ASP is registering. The format is as
follows: follows:
0 1 2 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 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x030c | Length = 8 | | Tag = 0x030c | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | SDL Identifier | | Reserved | SDL Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The SDL Identifier is a 32-bit unsigned value which may only be The SDL Identifier is a 32-bit unsigned value which may only be
significant to 12 or 14 bits depending on the SS7 variant which significant to 12 or 14 bits depending on the SS7 variant which
is supported by the MTP Level 3 at the ASP. Insignificant SDLI is supported by the MTP Level 3 at the ASP. Insignificant SDLI
bits are coded 0. bits are coded 0.
3.3.4.2 Registration Response (REG RSP) 3.3.4.2 Registration Response (REG RSP)
The REG RSP message is used as a response to the REG REQ message The REG RSP message is used as a response to the REG REQ message
from a remote M2UA peer. It contains indications of success/failure from a remote M2UA peer. It contains indications of success/failure
for registration requests and returns a unique Interface Identifier for registration requests and returns a unique Interface Identifier
value for successful registration requests, to be used in subsequent value for successful registration requests, to be used in subsequent
M2UA Traffic Management protocol. M2UA Traffic Management protocol.
The REG RSP message contains the following parameter: The REG RSP message contains the following parameter:
Registration Results (mandatory) Registration Results (mandatory)
The format for the REG RSP message is as follows: The format for the REG RSP message is as follows:
0 1 2 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 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x030d | Length | | Tag = 0x030d | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ Registration Result 1 / / Registration Result 1 /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 45, line 31 skipping to change at page 54, line 31
/ ... / / ... /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x030d | Length | | Tag = 0x030d | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ Registration Result n / / Registration Result n /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Registration Results: fixed length Registration Results: fixed length
The Registration Results parameter contains one or more results, The Registration Results parameter contains one or more results,
each containing the registration status for a single Link Key in each containing the registration status for a single Link Key in
the REG REQ message. The number of results in a single REG RSP the REG REQ message. The number of results in a single REG RSP
message MAY match the number of Link Key parameters found in the message MAY match the number of Link Key parameters found in the
corresponding REG REQ message. The format of each result is as corresponding REG REQ message. The format of each result is as
follows: follows:
0 1 2 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 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local-LK-Identifier | | Local-LK-Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Registration Status | | Registration Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier | | Interface Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Local-LK-Identifier: 32-bit integer
Local-LK-Identifier: 32-bit integer The Local-LK-Identifier contains the same value as found in the
matching Link Key parameter found in the REG REQ message. The
The Local-LK-Identifier contains the same value as found in the format of the Local-LK-Identifier is shown in Section 3.3.4.1.
matching Link Key parameter found in the REG REQ message. The
format of the Local-LK-Identifier is shown in Section 3.3.4.1.
Registration Status: 32-bit integer Registration Status: 32-bit integer
The Registration Result Status field indicates the success or the The Registration Result Status field indicates the success or the
reason for failure of a registration request. reason for failure of a registration request.
Its values may be one of the following: Its values may be one of the following:
0 Successfully Registered 0 Successfully Registered
1 Error - Unknown 1 Error - Unknown
2 Error - Invalid SDLI 2 Error - Invalid SDLI
3 Error - Invalid SDTI 3 Error - Invalid SDTI
4 Error - Invalid Link Key 4 Error - Invalid Link Key
5 Error - Permission Denied 5 Error - Permission Denied
6 Error - Overlapping (Non-unique) Link Key 6 Error - Overlapping (Non-unique) Link Key
7 Error - Link Key not Provisioned 7 Error - Link Key not Provisioned
8 Error - Insufficient Resources 8 Error - Insufficient Resources
The format of the Registration Status field is as follows: The format of the Registration Status field is as follows:
0 1 2 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 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x030e | Length = 8 | | Tag = 0x030e | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Registration Status | | Registration Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Interface Identifier: 32-bit integer Interface Identifier: 32-bit integer
The Interface Identifier field contains the Interface Identifier The Interface Identifier field contains the Interface Identifier
for the associated Link Key if the registration is successful. for the associated Link Key if the registration is successful. It
It is set to "0" if the registration was not successful. The is set to "0" if the registration was not successful. The format
format of integer-based and text-based Interface Identifier of integer-based and text-based Interface Identifier parameters
parameters are shown in Section 3.2. are shown in Section 3.2.
3.3.4.3 De-Registration Request (DEREG REQ) 3.3.4.3 De-Registration Request (DEREG REQ)
The DEREG REQ message is sent by an ASP to indicate to a remote M2UA The DEREG REQ message is sent by an ASP to indicate to a remote M2UA
peer that it wishes to de-register a given Interface Identifier. peer that it wishes to de-register a given Interface Identifier.
Typically, an ASP would send this message to an SGP, and expects to Typically, an ASP would send this message to an SGP, and expects to
receive a DEREG RSP in return reflecting the Interface Identifier receive a DEREG RSP in return reflecting the Interface Identifier and
and containing a de-registration status. containing a de-registration status.
The DEREG REQ message contains the following parameter: The DEREG REQ message contains the following parameter:
Interface Identifier (mandatory) Interface Identifier (mandatory)
The format for the DEREG REQ message is as follows: The format for the DEREG REQ message is as follows:
0 1 2 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 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x1 or 0x3 | Length | | Tag = 0x1 or 0x3 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ Interface Identifier 1 / / Interface Identifier 1 /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 47, line 25 skipping to change at page 56, line 31
/ ... / / ... /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x1 or 0x3 | Length | | Tag = 0x1 or 0x3 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ Interface Identifier n / / Interface Identifier n /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Interface Identifier Interface Identifier
The Interface Identifier parameter contains a Interface Identifier The Interface Identifier parameter contains a Interface Identifier
indexing the Application Server traffic that the sending ASP is indexing the Application Server traffic that the sending ASP is
currently registered to receive from the SGP but now wishes to currently registered to receive from the SGP but now wishes to
de-register. The format of integer-based and text-based Interface de-register. The format of integer-based and text-based Interface
Identifier parameters are shown in Section 3.2. Identifier parameters are shown in Section 3.2.
3.3.4.4 De-Registration Response (DEREG RSP) 3.3.4.4 De-Registration Response (DEREG RSP)
The DEREG RSP message is used as a response to the DEREG REQ message The DEREG RSP message is used as a response to the DEREG REQ message
from a remote M2UA peer. from a remote M2UA peer.
The DEREG RSP message contains the following parameter: The DEREG RSP message contains the following parameter:
De-Registration Results (mandatory) De-Registration Results (mandatory)
The format for the DEREG RSP message is as follows: The format for the DEREG RSP message is as follows:
0 1 2 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 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x030f | Length | | Tag = 0x030f | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ De-Registration Result 1 / / De-Registration Result 1 /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 48, line 5 skipping to change at page 57, line 27
/ ... / / ... /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x030f | Length | | Tag = 0x030f | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ De-Registration Result n / / De-Registration Result n /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
De-Registration Results: fixed length De-Registration Results: fixed length
The De-Registration Results parameter contains one or more results, The De-Registration Results parameter contains one or more
each containing the de-registration status for a single Interface results, each containing the de-registration status for a single
Identifier in the DEREG REQ message. The number of results in a Interface Identifier in the DEREG REQ message. The number of
single DEREG RSP message MAY match the number of Interface Identifier results in a single DEREG RSP message MAY match the number of
parameters found in the corresponding DEREG REQ message. The format Interface Identifier parameters found in the corresponding DEREG
of each result is as follows: REQ message. The format of each result is as follows:
0 1 2 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 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier | | Interface Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| De-Registration Status | | De-Registration Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Interface Identifier: 32-bit integer Interface Identifier: 32-bit integer
The Interface Identifier field contains the Interface Identifier The Interface Identifier field contains the Interface Identifier
value of the matching Link Key to de-register, as found in the value of the matching Link Key to de-register, as found in the
DEREG REQ. The format of integer-based and text-based Interface DEREG REQ. The format of integer-based and text-based Interface
Identifier parameters are shown in Section 3.2. Identifier parameters are shown in Section 3.2.
De-Registration Status: 32-bit integer De-Registration Status: 32-bit integer
The De-Registration Result Status field indicates the success or The De-Registration Result Status field indicates the success or
the reason for failure of the de-registration. the reason for failure of the de-registration.
Its values may be one of the following: Its values may be one of the following:
0 Successfully De-registered 0 Successfully De-registered
1 Error - Unknown 1 Error - Unknown
2 Error - Invalid Interface Identifier 2 Error - Invalid Interface Identifier
3 Error - Permission Denied 3 Error - Permission Denied
4 Error - Not Registered 4 Error - Not Registered
The format of the De-Registration Status field is as follows: The format of the De-Registration Status field is as follows:
0 1 2 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 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0310 | Length = 8 | | Tag = 0x0310 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| De-Registration Status | | De-Registration Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
4.0 Procedures 4.0 Procedures
The M2UA layer needs to respond to various primitives it receives from The M2UA layer needs to respond to various primitives it receives
other layers as well as messages it receives from the peer-to-peer from other layers as well as messages it receives from the peer-to-
messages. This section describes various procedures involved in peer messages. This section describes various procedures involved in
response to these events. response to these events.
4.1 Procedures to Support the M2UA-User Layer 4.1 Procedures to Support the M2UA-User Layer
These procedures achieve the M2UA layer "Transport of MTP Level 2 / These procedures achieve the M2UA layer "Transport of MTP Level 2 /
MTP Level 3 boundary" service. MTP Level 3 boundary" service.
4.1.1 MTP Level 2 / MTP Level 3 Boundary Procedures 4.1.1 MTP Level 2 / MTP Level 3 Boundary Procedures
On receiving a primitive from the local upper layer, the M2UA layer On receiving a primitive from the local upper layer, the M2UA layer
will send the corresponding MAUP message (see Section 3) to its peer. will send the corresponding MAUP message (see Section 3) to its peer.
The M2UA layer MUST fill in various fields of the common and specific The M2UA layer MUST fill in various fields of the common and specific
headers correctly. In addition the message SHOULD be sent on the SCTP headers correctly. In addition the message SHOULD be sent on the
stream that corresponds to the SS7 link. SCTP stream that corresponds to the SS7 link.
4.1.2 MAUP Message Procedures 4.1.2 MAUP Message Procedures
On receiving MAUP messages from a peer M2UA layer, the M2UA layer on an On receiving MAUP messages from a peer M2UA layer, the M2UA layer on
SG or MGC needs to invoke the corresponding layer primitives to the an SG or MGC needs to invoke the corresponding layer primitives to
local MTP Level 2 or MTP Level 3 layer. the local MTP Level 2 or MTP Level 3 layer.
4.2 Receipt of Primitives from the Layer Management 4.2 Receipt of Primitives from the Layer Management
On receiving primitives from the local Layer Management, the M2UA layer On receiving primitives from the local Layer Management, the M2UA
will take the requested action and provide an appropriate response layer will take the requested action and provide an appropriate
primitive to Layer Management. response primitive to Layer Management.
An M-SCTP_ESTABLISH request primitive from Layer Management at an ASP An M-SCTP_ESTABLISH request primitive from Layer Management at an ASP
will initiate the establishment of an SCTP association. The M2UA will initiate the establishment of an SCTP association. The M2UA
layer will attempt to establish an SCTP association with the remote layer will attempt to establish an SCTP association with the remote
M2UA peer by sending an SCTP-ASSOCIATE primitive to the local SCTP M2UA peer by sending an SCTP-ASSOCIATE primitive to the local SCTP
layer. layer.
When an SCTP association has been successfully established, the SCTP When an SCTP association has been successfully established, the SCTP
will send an SCTP-COMMUNICATION_UP notification primitive to the local will send an SCTP-COMMUNICATION_UP notification primitive to the
M2UA layer. At the SGP that initiated the request, the M2UA layer will local M2UA layer. At the SGP that initiated the request, the M2UA
send an M-SCTP_ESTABLISH confirm primitive to Layer Management when layer will send an M-SCTP_ESTABLISH confirm primitive to Layer
the association setup is complete. At the peer M2UA layer, an Management when the association setup is complete. At the peer M2UA
M-SCTP_ESTABLISH indication primitive is sent to Layer Management layer, an M-SCTP_ESTABLISH indication primitive is sent to Layer
upon successful completion of an incoming SCTP association setup. Management upon successful completion of an incoming SCTP association
setup.
An M-SCTP_RELEASE request primitive from Layer Management initates the An M-SCTP_RELEASE request primitive from Layer Management initiates
shutdown of an SCTP association. The M2UA layer accomplishes a the shutdown of an SCTP association. The M2UA layer accomplishes a
graceful shutdown of the SCTP association by sending an SCTP-SHUTDOWN graceful shutdown of the SCTP association by sending an SCTP-SHUTDOWN
primitive to the SCTP layer. primitive to the SCTP layer.
When the graceful shutdown of the SCTP association has been When the graceful shutdown of the SCTP association has been
accomplished, the SCTP layer returns an SCTP-SHUTDOWN_COMPLETE accomplished, the SCTP layer returns an SCTP-SHUTDOWN_COMPLETE
notification primitive to the local M2UA layer. At the M2UA Layer that notification primitive to the local M2UA layer. At the M2UA Layer
initiated the request, the M2UA layer will send an M-SCTP_RELEASE that initiated the request, the M2UA layer will send an M-
confirm primitive to Layer Management when the association shutdown is SCTP_RELEASE confirm primitive to Layer Management when the
complete. At the peer M2UA Layer, an M-SCTP_RELEASE indication association shutdown is complete. At the peer M2UA Layer, an M-
primitive is sent to Layer Management upon abort or successful SCTP_RELEASE indication primitive is sent to Layer Management upon
shutdown of an SCTP association. abort or successful shutdown of an SCTP association.
An M-SCTP_STATUS request primitive supports a Layer Management query An M-SCTP_STATUS request primitive supports a Layer Management query
of the local status of a particular SCTP association. The M2UA layer of the local status of a particular SCTP association. The M2UA layer
simply maps the M-SCTP_STATUS request primitive to an SCTP-STATUS simply maps the M-SCTP_STATUS request primitive to an SCTP-STATUS
primitive to the SCTP layer. When the SCTP responds, the M2UA layer primitive to the SCTP layer. When the SCTP responds, the M2UA layer
maps the association status information to an M-SCTP_STATUS confirm maps the association status information to an M-SCTP_STATUS confirm
primitive. No peer protocol is invoked. primitive. No peer protocol is invoked.
Similar LM-to-M2UA-to-SCTP and/or SCTP-to-M2UA-to-LM primitive mappings Similar LM-to-M2UA-to-SCTP and/or SCTP-to-M2UA-to-LM primitive
can be described for the various other SCTP Upper Layer primitives in mappings can be described for the various other SCTP Upper Layer
RFC2960 [8] such as INITIALIZE, SET PRIMARY, CHANGE HEARTBEAT, primitives in RFC 2960 [8] such as INITIALIZE, SET PRIMARY, CHANGE
REQUEST HEARTBEAT, GET SRTT REPORT, SET FAILURE THRESHOLD, SET PROTOCOL HEARTBEAT, REQUEST HEARTBEAT, GET SRTT REPORT, SET FAILURE THRESHOLD,
PARAMETERS, DESTROY SCTP INSTANCE, SEND FAILURE, AND NETWORK STATUS SET PROTOCOL PARAMETERS, DESTROY SCTP INSTANCE, SEND FAILURE, AND
CHANGE. Alternatively, these SCTP Upper Layer primitives (and Status NETWORK STATUS CHANGE. Alternatively, these SCTP Upper Layer
as well) can be considered for modeling purposes as a Layer Management primitives (and Status as well) can be considered for modeling
interaction directly with the SCTP Layer. purposes as a Layer Management interaction directly with the SCTP
Layer.
M-NOTIFY indication and M-ERROR indication primitives indicate to Layer M-NOTIFY indication and M-ERROR indication primitives indicate to
Management the notification or error information contained in a Layer Management the notification or error information contained in a
received M2UA Notify or Error message respectively. These indications received M2UA Notify or Error message respectively. These
can also be generated based on local M2UA events. indications can also be generated based on local M2UA events.
An M-ASP_STATUS request primitive supports a Layer Management query of An M-ASP_STATUS request primitive supports a Layer Management query
the status of a particular local or remote ASP. The M2UA layer of the status of a particular local or remote ASP. The M2UA layer
responds with the status in an M-ASP_STATUS confirm primitive. No M2UA responds with the status in an M-ASP_STATUS confirm primitive. No
peer protocol is invoked. M2UA peer protocol is invoked.
An M-AS_STATUS request supports a Layer Management query of the status An M-AS_STATUS request supports a Layer Management query of the
of a particular AS. The M2UA responds with an M-AS_STATUS confirm status of a particular AS. The M2UA responds with an M-AS_STATUS
primitive. No M2UA peer protocol is invoked. confirm primitive. No M2UA peer protocol is invoked.
M-ASP_UP request, M-ASP_DOWN request, M-ASP_ACTIVE request and M-ASP_ M-ASP_UP request, M-ASP_DOWN request, M-ASP_ACTIVE request and M-
INACTIVE request primitives allow Layer Management at an ASP to ASP_INACTIVE request primitives allow Layer Management at an ASP to
initiate state changes. Upon successful completion, a corresponding initiate state changes. Upon successful completion, a corresponding
confirm primitive is provided by the M2UA layer to Layer Management. confirm primitive is provided by the M2UA layer to Layer Management.
If an invocation is unsuccessful, an Error indication primitive is If an invocation is unsuccessful, an Error indication primitive is
provided in the primitive. These requests result in outgoing ASP Up, provided in the primitive. These requests result in outgoing ASP Up,
ASP Down, ASP Active and ASP Inactive messages to the remote M2UA peer ASP Down, ASP Active and ASP Inactive messages to the remote M2UA
at an SGP. peer at an SGP.
4.2.1 Receipt of M2UA Peer Management Messages 4.2.1 Receipt of M2UA Peer Management Messages
Upon successful state changes resulting from reception of ASP Up, Upon successful state changes resulting from reception of ASP Up, ASP
ASP Down, ASP Active and ASP Inactive messages from a peer M2UA, the Down, ASP Active and ASP Inactive messages from a peer M2UA, the M2UA
M2UA layer SHOULD invoke corresponding M-ASP_UP, M-ASP_DOWN, M- layer SHOULD invoke corresponding M-ASP_UP, M-ASP_DOWN, M-ASP_ACTIVE
ASP_ACTIVE and M-ASP_INACTIVE, M-AS_ACTIVE, M-AS_INACTIVE, and M- and M-ASP_INACTIVE, M-AS_ACTIVE, M-AS_INACTIVE, and M-AS_DOWN
AS_DOWN indication primitives to the local Layer Management. indication primitives to the local Layer Management.
M-NOTIFY indication and M-ERROR indication primitives indicate to Layer M-NOTIFY indication and M-ERROR indication primitives indicate to
Management the notification or error information contained in a Layer Management the notification or error information contained in a
received M2UA Notify or Error message. These indications can also be received M2UA Notify or Error message. These indications can also be
generated based on local M2UA events. generated based on local M2UA events.
All MGMT messages, except BEAT and BEAT Ack, SHOULD be sent with All MGMT messages, except BEAT and BEAT Ack, SHOULD be sent with
sequenced delivery to ensure ordering. All MGMT messages, with the sequenced delivery to ensure ordering. All MGMT messages, with the
exception of ASPTM, BEAT and BEAT Ack messages, SHOULD be sent on SCTP exception of ASPTM, BEAT and BEAT Ack messages, SHOULD be sent on
stream '0'. All ASPTM messages SHOULD be sent on the stream which SCTP stream '0'. All ASPTM messages SHOULD be sent on the stream
normally carries the data traffic to which the message applies. BEAT which normally carries the data traffic to which the message applies.
and BEAT Ack messages MAY be sent using out-of-order delivery, and BEAT and BEAT Ack messages MAY be sent using out-of-order delivery,
MAY be sent on any stream. and MAY be sent on any stream.
4.3 AS and ASP State Maintenance 4.3 AS and ASP State Maintenance
The M2UA layer on the SGP maintains the state of each remote ASP, in The M2UA layer on the SGP maintains the state of each remote ASP, in
each Application Server that the ASP is configured to receive traffic, each Application Server that the ASP is configured to receive
as input to the M2UA message distribution function. traffic, as input to the M2UA message distribution function.
4.3.1 ASP States 4.3.1 ASP States
The state of each remote ASP, in each AS that it is configured to The state of each remote ASP, in each AS that it is configured to
operate, is maintained in the M2UA layer in the SGP. The state of a operate, is maintained in the M2UA layer in the SGP. The state of a
particular ASP in a particular AS changes due to events. The events particular ASP in a particular AS changes due to events. The events
include: include:
* Reception of messages from the peer M2UA layer at the ASP; * Reception of messages from the peer M2UA layer at the ASP;
* Reception of some messages from the peer M2UA layer at other ASPs * Reception of some messages from the peer M2UA layer at other ASPs
in the AS (e.g., ASP Active message indicating "Override"); in the AS (e.g., ASP Active message indicating "Override");
* Reception of indications from the SCTP layer; or * Reception of indications from the SCTP layer; or
* Local Management intervention. * Local Management intervention.
The ASP state transition diagram is shown in Figure 5. The possible The ASP state transition diagram is shown in Figure 5. The possible
states of an ASP are: states of an ASP are:
ASP-DOWN: The remote M2UA peer at the ASP is unavailable and/or the ASP-DOWN: The remote M2UA peer at the ASP is unavailable and/or the
related SCTP association is down. Initially all ASPs will be in this related SCTP association is down. Initially all ASPs will be in this
state. An ASP in this state SHOULD NOT be sent any M2UA messages, with state. An ASP in this state SHOULD NOT be sent any M2UA messages,
the exception of Heartbeat, ASP Down Ack and Error messages. with the exception of Heartbeat, ASP Down Ack and Error messages.
ASP-INACTIVE: The remote M2UA peer at the ASP is available (and the ASP-INACTIVE: The remote M2UA peer at the ASP is available (and the
related SCTP association is up) but application traffic is stopped. related SCTP association is up) but application traffic is stopped.
In this state the ASP MAY be sent any non-MAUP M2UA messages. In this state the ASP MAY be sent any non-MAUP M2UA messages.
ASP-ACTIVE: The remote M2UA peer at the ASP is available and ASP-ACTIVE: The remote M2UA peer at the ASP is available and
application traffic is active (for a particular Interface Identifier application traffic is active (for a particular Interface Identifier
or set of Interface Identifiers). or set of Interface Identifiers).
Figure 5: ASP State Transition Diagram Figure 5: ASP State Transition Diagram
+--------------+ +--------------+
| ASP-ACTIVE | | ASP-ACTIVE |
+----------------------| | +----------------------| |
| Other +-------| | | Other +-------| |
| ASP in AS | +--------------+ | ASP in AS | +--------------+
| Overrides | ^ | | Overrides | ^ |
| | ASP | | ASP | | ASP | | ASP
| | Active | | Inactive | | Active | | Inactive
| | | v | | | v
| | +--------------+ | | +--------------+
| | | | | | | |
| +------>| ASP-INACTIVE | | +------>| ASP-INACTIVE |
| +--------------+ | +--------------+
| ^ | | ^ |
ASP Down/ | ASP | | ASP Down / ASP Down/ | ASP | | ASP Down /
SCTP CDI/ | Up | | SCTP CDI/ SCTP CDI/ | Up | | SCTP CDI/
SCTP RI | | v SCTP RI SCTP RI | | v SCTP RI
| +--------------+ | +--------------+
| | | | | |
+--------------------->| ASP-DOWN | +--------------------->| ASP-DOWN |
| | | |
+--------------+ +--------------+
SCTP CDI: The SCTP CDI denotes the local SCTP layer's Communication SCTP CDI: The SCTP CDI denotes the local SCTP layer's Communication
Down Indication to the Upper Layer Protocol (M2UA) on an SGP. The local Down Indication to the Upper Layer Protocol (M2UA) on an SGP. The
SCTP layer will send this indication when it detects the loss of local SCTP layer will send this indication when it detects the loss
connectivity to the ASP's peer SCTP layer. SCTP CDI is understood as of connectivity to the ASP's peer SCTP layer. SCTP CDI is understood
either a SHUTDOWN_COMPLETE notification or COMMUNICATION_LOST as either a SHUTDOWN_COMPLETE notification or COMMUNICATION_LOST
notification from the SCTP layer. notification from the SCTP layer.
SCTP RI: The local SCTP layer's Restart indication to the upper layer SCTP RI: The local SCTP layer's Restart indication to the upper layer
protocol (M2UA) on an SG. The local SCTP will send this indication when protocol (M2UA) on an SG. The local SCTP will send this indication
it detects a restart from the ASP's peer SCTP layer. when it detects a restart from the ASP's peer SCTP layer.
4.3.2 AS States 4.3.2 AS States
The state of the AS is maintained in the M2UA layer on the SGP. The The state of the AS is maintained in the M2UA layer on the SGP. The
state of an AS changes due to events. These events include: state of an AS changes due to events. These events include:
* ASP state transitions * ASP state transitions
* Recovery timer triggers * Recovery timer triggers
The possible states of an AS are: The possible states of an AS are:
AS-DOWN: The Application Server is unavailable. This state implies AS-DOWN: The Application Server is unavailable. This state implies
that all related ASPs are in the ASP-DOWN state for this AS. Initially that all related ASPs are in the ASP-DOWN state for this AS.
the AS will be in this state. An Application Server MUST be in the AS- Initially the AS will be in this state. An Application Server MUST
DOWN state before it can be removed from a configuration. be in the AS-DOWN state before it can be removed from a
configuration.
AS-INACTIVE: The Application Server is available but no application AS-INACTIVE: The Application Server is available but no application
traffic is active (i.e., one or more related ASPs are in the ASP- 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 INACTIVE state, but none in the ASP-ACTIVE state). The recovery
T(r) is not running or has expired. timer T(r) is not running or has expired.
AS-ACTIVE: The Application Server is available and application traffic AS-ACTIVE: The Application Server is available and application
is active. This state implies that at least one ASP is in the ASP- traffic is active. This state implies that at least one ASP is in
ACTIVE state. the ASP-ACTIVE state.
AS-PENDING: An active ASP has transitioned to ASP-INACTIVE or ASP-DOWN AS-PENDING: An active ASP has transitioned to ASP-INACTIVE or ASP-
and it was the last remaining active ASP in the AS. A recovery timer DOWN and it was the last remaining active ASP in the AS. A recovery
T(r) SHOULD be started and all incoming signalling messages SHOULD be timer T(r) SHOULD be started and all incoming signalling messages
queued by the SGP. If an ASP becomes ASP-ACTIVE before T(r) expires, SHOULD be queued by the SGP. If an ASP becomes ASP-ACTIVE before
the AS is moved to the AS-ACTIVE state and all the queued messages will T(r) expires, the AS is moved to the AS-ACTIVE state and all the
be sent to the ASP. queued messages will be sent to the ASP.
If T(r) expires before an ASP becomes ASP-ACTIVE, the SGP stops queuing If T(r) expires before an ASP becomes ASP-ACTIVE, the SGP stops
messages and discards all previously queued messages. The AS will move queuing messages and discards all previously queued messages. The AS
to the AS-INACTIVE state if at least one ASP is in ASP-INACTIVE state, will move to the AS-INACTIVE state if at least one ASP is in the
otherwise it will move to AS-DOWN state. ASP-INACTIVE state, otherwise it will move to the AS-DOWN state.
Figure 6 shows an example AS state machine for the case where the Figure 6 shows an example AS state machine for the case where the
AS/ASP data is pre-configured. For other cases where the AS/ASP AS/ASP data is pre-configured. For other cases where the AS/ASP
configuration data is created dynamically, there would be differences configuration data is created dynamically, there would be differences
in the state machine, especially at creation of the AS. in the state machine, especially at the creation of the AS.
For example, where the AS/ASP configuration data is not created until For example, where the AS/ASP configuration data is not created until
Registration of the first ASP, the AS-INACTIVE state is entered Registration of the first ASP, the AS-INACTIVE state is entered
directly upon the first successful REG REQ from an ASP. Another directly upon the first successful REG REQ from an ASP. Another
example is where the AS/ASP configuration data is not created until the example is where the AS/ASP configuration data is not created until
first ASP successfully enters the ASP-ACTIVE state. In this case the the first ASP successfully enters the ASP-ACTIVE state. In this case
AS-ACTIVE state is entered directly. the AS-ACTIVE state is entered directly.
Figure 6: AS State Transition Diagram Figure 6: AS State Transition Diagram
+----------+ one ASP trans to ACTIVE +-------------+ +----------+ one ASP trans to ACTIVE +-------------+
| AS- |---------------------------->| AS- | | AS- |---------------------------->| AS- |
| INACTIVE | | ACTIVE | | INACTIVE | | ACTIVE |
| |<--- | | | |<--- | |
+----------+ \ +-------------+ +----------+ \ +-------------+
^ | \ Tr Expiry, ^ | ^ | \ Tr Expiry, ^ |
| | \ at least one | | | | \ at least one | |
| | \ ASP in ASP-INACTIVE | | | | \ ASP in ASP-INACTIVE | |
| | \ | | | | \ | |
| | \ | | | | \ | |
| | \ | | | | \ | |
one ASP | | all ASP \ one ASP | | Last ACTIVE one ASP | | all ASP \ one ASP | | Last ACTIVE
trans | | trans to \ trans to | | ASP trans to trans | | trans to \ trans to | | ASP trans to
to | | ASP-DOWN -------\ ASP- | | ASP-INACTIVE to | | ASP-DOWN -------\ ASP- | | ASP-INACTIVE
ASP- | | \ ACTIVE | | or ASP-DOWN ASP- | | \ ACTIVE | | or ASP-DOWN
INACTIVE| | \ | | (start Tr) INACTIVE| | \ | | (start Tr)
| | \ | | | | \ | |
| | \ | | | | \ | |
| v \ | v | v \ | v
+----------+ \ +-------------+ +----------+ \ +-------------+
| | --| | | | --| |
| AS-DOWN | | AS-PENDING | | AS-DOWN | | AS-PENDING |
| | | (queueing) | | | | (queuing) |
| |<----------------------------| | | |<----------------------------| |
+----------+ Tr Expiry and no ASP +-------------+ +----------+ Tr Expiry and no ASP +-------------+
in ASP-INACTIVE state in ASP-INACTIVE state
Tr = Recovery Timer Tr = Recovery Timer
4.3.3 M2UA Management Procedures for Primitives 4.3.3 M2UA Management Procedures for Primitives
Before the establishment of an SCTP association the ASP state at both 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. the SGP and ASP is assumed to be in the state ASP-DOWN.
Once the SCTP association is established (see Section 4.2.1) and Once the SCTP association is established (see Section 4.2.1) and
assuming that the local M2UA-User is ready, the local M2UA ASP assuming that the local M2UA-User is ready, the local M2UA ASP
Maintenance (ASPM) function will initiate the relevant procedures, Maintenance (ASPM) function will initiate the relevant procedures,
using the ASP Up/ASP Down/ASP Active/ASP Inactive messages to convey using the ASP Up/ASP Down/ASP Active/ASP Inactive messages to convey
the ASP state to the SGP (see Section 4.3.4). the ASP state to the SGP (see Section 4.3.4).
If the M2UA layer subsequently receives an SCTP-COMMUNICATION_DOWN If the M2UA layer subsequently receives an SCTP-COMMUNICATION_DOWN or
or SCTP-RESTART indication primitive from the underlying SCTP layer, SCTP-RESTART indication primitive from the underlying SCTP layer, it
it will inform the Layer Management by invoking the M-SCTP_STATUS will inform the Layer Management by invoking the M-SCTP_STATUS
indication primitive. The state of the ASP will be moved to ASP-DOWN. indication primitive. The state of the ASP will be moved to ASP-
DOWN.
In the case of SCTP-COMMUNICATION_DOWN, the SCTP client MAY try to re- In the case of SCTP-COMMUNICATION_DOWN, the SCTP client MAY try to
establish the SCTP association. This MAY be done by the M2UA layer re-establish the SCTP association. This MAY be done by the M2UA
automatically, or Layer Management MAY re-establish using the layer automatically, or Layer Management MAY re-establish using the
M-SCTP_ESTABLISH request primitive. M-SCTP_ESTABLISH request primitive.
In the case of an SCTP-RESTART indication at an ASP, the ASP is now In the case of an SCTP-RESTART indication at an ASP, the ASP is now
considered by its M2UA peer to be in the ASP-DOWN state. The ASP, if considered by its M2UA peer to be in the ASP-DOWN state. The ASP, if
it is to recover, must begin any recovery with the ASP-Up procedure. it is to recover, must begin any recovery with the ASP-Up procedure.
4.3.4 ASPM Procedures for Peer-to-Peer Messages 4.3.4 ASPM Procedures for Peer-to-Peer Messages
4.3.4.1 ASP Up Procedures 4.3.4.1 ASP Up Procedures
After an ASP has successfully established an SCTP association to an 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 SGP, the SGP waits for the ASP to send an ASP Up message, indicating
that the ASP M2UA peer is available. The ASP is always the initiator that the ASP M2UA peer is available. The ASP is always the initiator
of the ASP Up message. This action MAY be initiated at the ASP by an 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 M-ASP_UP request primitive from Layer Management or MAY be initiated
automatically by an M2UA management function. automatically by an M2UA management function.
When an ASP Up message is received at an SGP and internally the remote When an ASP Up message is received at an SGP and internally the
ASP is in the ASP-DOWN state and not considered locked-out for local remote ASP is in the ASP-DOWN state and not considered locked-out for
management reasons, the SGP marks the remote ASP in the state ASP- local management reasons, the SGP marks the remote ASP in the state
INACTIVE and informs Layer Management with an M-ASP_Up indication ASP-INACTIVE and informs Layer Management with an M-ASP_Up indication
primitive. If the SGP is aware, via current configuration data, which primitive. If the SGP is aware, via current configuration data,
Application Servers the ASP is configured to operate in, the SGP which Application Servers the ASP is configured to operate in, the
updates the ASP state to ASP-INACTIVE in each AS that it is a member. SGP updates the ASP state to ASP-INACTIVE in each AS that it is a
member.
Alternatively, the SGP may move the ASP into a pool of Inactive ASPs Alternatively, the SGP may move the ASP into a pool of Inactive ASPs
available for future configuration within Application Server(s), available for future configuration within Application Server(s),
determined in a subsequent Registration Request or ASP Active determined in a subsequent Registration Request or ASP Active
procedure. If the ASP Up message contains an ASP Identifier, the SGP 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 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 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. the ASP is already marked as ASP-INACTIVE at the SGP.
If for any local reason (e.g., management lock-out) the SGP cannot 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 respond with an ASP Up Ack message, the SGP responds to an ASP Up
message with an Error message with Reason "Refused - Management message with an Error message with Reason "Refused - Management
Blocking". Blocking".
At the ASP, the ASP Up Ack message received is not acknowledged. Layer At the ASP, the ASP Up Ack message received is not acknowledged.
Management is informed with an M-ASP_UP confirm primitive. Layer Management is informed with an M-ASP_UP confirm primitive.
When the ASP sends an ASP Up message it starts timer T(ack). If the 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 does not receive a response to an ASP Up message within T(ack),
ASP MAY restart T(ack) and resend ASP Up messages until it receives an the ASP MAY restart T(ack) and resend ASP Up messages until it
ASP Up Ack message. T(ack) is provisionable, with a default of 2 receives an ASP Up Ack message. T(ack) is provisionable, with a
seconds. Alternatively, retransmission of ASP Up messages MAY be put default of 2 seconds. Alternatively, retransmission of ASP Up
under control of Layer Management. In this method, expiry of T(ack) messages MAY be put under control of Layer Management. In this
results in an M-ASP_UP confirm primitive carrying a negative method, expiry of T(ack) results in an M-ASP_UP confirm primitive
indication. carrying a negative indication.
The ASP MUST wait for the ASP Up Ack message before sending any other The ASP MUST wait for the ASP Up Ack message before sending any other
M2UA messages (e.g., ASP Active or REG REQ). If the SGP receives any M2UA messages (e.g., ASP Active or REG REQ). If the SGP receives any
other M2UA messages before an ASP Up message is received (other than other M2UA messages before an ASP Up message is received (other than
ASP Down - see Section 4.3.4.2), the SGP MAY discard them. ASP Down - see Section 4.3.4.2), the SGP MAY discard them.
If an ASP Up message is received and internally the remote ASP is in 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 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 an Error message ("Unexpected Message), and the remote ASP state is
changed to ASP-INACTIVE in all relevant Application Servers. changed to ASP-INACTIVE in all relevant Application Servers.
If an ASP Up message is received and internally the remote ASP is 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 already in the ASP-INACTIVE state, an ASP Up Ack message is returned
and no further action is taken. and no further action is taken.
4.3.4.1.1 M2UA Version Control 4.3.4.1.1 M2UA Version Control
If an ASP Up message with an unsupported version is received, the If an ASP Up message with an unsupported version is received, the
receiving end responds with an Error message, indicating the version receiving end responds with an Error message, indicating the version
the receiving node supports and notifies Layer Management. the receiving node supports and notifies Layer Management.
This is useful when protocol version upgrades are being performed in a This is useful when protocol version upgrades are being performed in
network. A node upgraded to a newer version SHOULD support the older a network. A node upgraded to a newer version SHOULD support the
versions used on other nodes it is communicating with. Because ASPs older versions used on other nodes it is communicating with. Because
initiate the ASP Up procedure it is assumed that the Error message ASPs initiate the ASP Up procedure it is assumed that the Error
would normally come from the SGP. message would normally come from the SGP.
4.3.4.2 ASP Down Procedures 4.3.4.2 ASP Down Procedures
The ASP will send an ASP Down message to an SGP when the ASP wishes to The ASP will send an ASP Down message to an SGP when the ASP wishes
be removed from service in all Application Servers that it is a member to be removed from service in all Application Servers that it is a
and no longer receive any MAUP or ASPTM messages. This action MAY be member and no longer receive any MAUP or ASPTM messages. This action
initiated at the ASP by an M-ASP_DOWN request primitive from Layer MAY be initiated at the ASP by an M-ASP_DOWN request primitive from
Management or MAY be initiated automatically by an M2UA management Layer Management or MAY be initiated automatically by an M2UA
function. management function.
Whether the ASP is permanently removed from any AS is a function of Whether the ASP is permanently removed from any AS is a function of
configuration management. In the case where the ASP previously used configuration management. In the case where the ASP previously used
the Registration procedures (see Section 4.4) to register within the Registration procedures (see Section 4.4) to register within
Application Servers but has not deregistered from all of them prior to Application Servers but has not unregistered from all of them prior
sending the ASP Down message, the SGP MUST consider the ASP as to sending the ASP Down message, the SGP MUST consider the ASP as
Deregistered in all Application Servers that it is still a member. unregistered in all Application Servers that it is still a member.
The SGP marks the ASP as ASP-DOWN, informs Layer Management with an 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 M-ASP_Down indication primitive, and returns an ASP Down Ack message
to the ASP. to the ASP.
The SGP MUST send an ASP Down Ack message in response to a received ASP The SGP MUST send an ASP Down Ack message in response to a received
Down message from the ASP even if the ASP is already marked as ASP-DOWN ASP Down message from the ASP even if the ASP is already marked as
at the SGP. ASP-DOWN at the SGP.
At the ASP, the ASP Down Ack message received is not acknowledged. At the ASP, the ASP Down Ack message received is not acknowledged.
Layer Management is informed with an M-ASP_DOWN confirm primitive. If Layer Management is informed with an M-ASP_DOWN confirm primitive.
the ASP receives an ASP Down Ack without having sent an ASP Down 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. 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 If the ASP was previously in the ASP-ACTIVE or ASP_INACTIVE state,
ASP SHOULD then initiate procedures to return itself to its previous the ASP SHOULD then initiate procedures to return itself to its
state. previous state.
When the ASP sends an ASP Down message it starts timer T(ack). If the When the ASP sends an ASP Down message it starts timer T(ack). If
ASP does not receive a response to an ASP Down message within T(ack), the ASP does not receive a response to an ASP Down message within
the ASP MAY restart T(ack) and resend ASP Down messages until it T(ack), the ASP MAY restart T(ack) and resend ASP Down messages until
receives an ASP Down Ack message. T(ack) is provisionable, with a it receives an ASP Down Ack message. T(ack) is provisionable, with a
default of 2 seconds. Alternatively, retransmission of ASP Down default of 2 seconds. Alternatively, retransmission of ASP Down
messages MAY be put under control of Layer Management. In this method, messages MAY be put under control of Layer Management. In this
expiry of T(ack) results in an M-ASP_DOWN confirm primitive carrying a method, expiry of T(ack) results in an M-ASP_DOWN confirm primitive
negative indication. carrying a negative indication.
4.3.4.4 ASP Active Procedures 4.3.4.3 ASP Active Procedures
Anytime after the ASP has received an ASP Up Ack message from the SGP, Anytime after the ASP has received an ASP Up Ack message from the
the ASP MAY send an ASP Active message to the SGP indicating that SGP, the ASP MAY send an ASP Active message to the SGP indicating
the ASP is ready to start processing traffic. This action MAY be that the ASP is ready to start processing traffic. This action MAY
initiated at the ASP by an M-ASP_ACTIVE request primitive from Layer be initiated at the ASP by an M-ASP_ACTIVE request primitive from
Management or MAY be initiated automatically by a M2UA management Layer Management or MAY be initiated automatically by a M2UA
function. In the case where an ASP wishes to process the traffic for management function. In the case where an ASP wishes to process the
more than one Application Server across a common SCTP association, the traffic for more than one Application Server across a common SCTP
ASP Active message(s) SHOULD contain a list of one or more Interface association, the ASP Active message(s) SHOULD contain a list of one
Identifiers to indicate for which Application Servers the ASP Active or more Interface Identifiers to indicate for which Application
message applies. It is not necessary for the ASP to include any Servers the ASP Active message applies. It is not necessary for the
Interface Identifiers of interest in a single ASP Active message, ASP to include any Interface Identifiers of interest in a single ASP
thus requesting to become active in all Interface Identifiers at the Active message, thus requesting to become active in all Interface
same time. Multiple ASP Active messages MAY be used to activate Identifiers at the same time. Multiple ASP Active messages MAY be
within the Application Servers independently, or in sets. In the used to activate within the Application Servers independently, or in
case where an ASP Active message does not contain a Interface sets. In the case where an ASP Active message does not contain a
Identifier parameter, the receiver must know, via configuration data, Interface Identifier parameter, the receiver must know, via
which Application Server(s) the ASP is a member. configuration data, of which Application Server(s) the ASP is a
member.
For the Application Servers that the ASP can successfully activate, For the Application Servers that the ASP can successfully activate,
the SGP responds with one or more ASP Active Ack messages, including the SGP responds with one or more ASP Active Ack messages, including
the associated Interface Identifier(s) and reflecting any Traffic Mode the associated Interface Identifier(s) and reflecting any Traffic
Type value present in the related ASP Active message. The Interface Mode Type value present in the related ASP Active message. The
Identifier parameter MUST be included in the ASP Active Ack message(s) Interface Identifier parameter MUST be included in the ASP Active Ack
if the received ASP Active message contained any Interface Identifiers. message(s) if the received ASP Active message contained any Interface
Depending on any Traffic Mode Type request in the ASP Active message Identifiers. Depending on any Traffic Mode Type request in the ASP
or local configuration data if there is no request, the SGP moves the Active message or local configuration data if there is no request,
ASP to the correct ASP traffic state within the associated Application the SGP moves the ASP to the correct ASP traffic state within the
Server(s). Layer Management is informed with an M-ASP_Active associated Application Server(s). Layer Management is informed with
indication. If the SGP receives any Data messages before an ASP Active an M-ASP_Active indication. If the SGP receives any Data messages
message is received, the SGP MAY discard them. By sending an ASP before an ASP Active message is received, the SGP MAY discard them.
Active Ack message, the SGP is now ready to receive and send traffic By sending an ASP Active Ack message, the SGP is now ready to receive
for the related Interface Identifier(s). The ASP SHOULD NOT send MAUP and send traffic for the related Interface Identifier(s). The ASP
messages for the related Interface Identifier(s) before receiving an SHOULD NOT send MAUP messages for the related Interface Identifier(s)
ASP Active Ack message, or it will risk message loss. before receiving an ASP Active Ack message, or it will risk message
loss.
Multiple ASP Active Ack messages MAY be used in response to an ASP Multiple ASP Active Ack messages MAY be used in response to an ASP
Active message containing multiple Interface Identifiers, allowing Active message containing multiple Interface Identifiers, allowing
the SGP to independently acknowledge the ASP Active message for the SGP to independently acknowledge the ASP Active message for
different (sets of) Interface Identifiers. The SGP MUST send different (sets of) Interface Identifiers. The SGP MUST send an
an Error message ("Invalid Interface Identifier") for each Interface Error message ("Invalid Interface Identifier") for each Interface
Identifier value that cannot be successfully activated. Identifier value that cannot be successfully activated.
In the case where an "out-of-the-blue" ASP Active message is received 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 (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. configuration data for the ASP), the message MAY be silently
discarded.
The SGP MUST send an ASP Active Ack message in response to a received 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 message from the ASP, if the ASP is already marked in the
ASP-ACTIVE state at the SGP. ASP-ACTIVE state at the SGP.
At the ASP, the ASP Active Ack message received is not acknowledged. At the ASP, the ASP Active Ack message received is not acknowledged.
Layer Management is informed with an M-ASP_ACTIVE confirm primitive. 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 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 Active Ack message as the ASP Active Ack and Data messages from an SG
may be sent on different SCTP streams. Message loss is possible as may be sent on different SCTP streams. Message loss is possible as
the ASP does not consider itself in the ASP-ACTIVE state until the ASP does not consider itself in the ASP-ACTIVE state until
reception of the ASP Active Ack message. reception of the ASP Active Ack message.
When the ASP sends an ASP Active message it starts timer T(ack). If 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 the ASP does not receive a response to an ASP Active message within
T(ack), the ASP MAY restart T(ack) and resend ASP Active message(s) T(ack), the ASP MAY restart T(ack) and resend ASP Active message(s)
until it receives an ASP Active Ack message. T(ack) is provisionable, until it receives an ASP Active Ack message. T(ack) is
with a default of 2 seconds. Alternatively, retransmission of ASP provisionable, with a default of 2 seconds. Alternatively,
Active messages MAY be put under control of Layer Management. In retransmission of ASP Active messages MAY be put under the control of
this method, expiry of T(ack) results in an M-ASP_ACTIVE confirm Layer Management. In this method, expiry of T(ack) results in an M-
primitive carrying a negative indication. ASP_ACTIVE confirm primitive carrying a negative indication.
There are three modes of Application Server traffic handling in the SGP There are three modes of Application Server traffic handling in the
M2UA layer: Override, Loadshare and Broadcast. When included, the SGP M2UA layer: Override, Load share and Broadcast. When included,
Traffic Mode Type parameter in the ASP Active message indicates the the Traffic Mode Type parameter in the ASP Active message indicates
traffic handling mode to be used in a particular Application Server. the traffic handling mode to be used in a particular Application
If the SGP determines that the mode indicated in an ASP Active message Server. If the SGP determines that the mode indicated in an ASP
is unsupported or incompatible with the mode currently configured for Active message is unsupported or incompatible with the mode currently
the AS, the SGP responds with an Error message ("Unsupported / Invalid configured for the AS, the SGP responds with an Error message
Traffic Handling Mode"). If the traffic handling mode of the ("Unsupported / Invalid Traffic Handling Mode"). If the traffic
Application Server is not already known via configuration data, then handling mode of the Application Server is not already known via
the traffic handling mode indicated in the first ASP Active message configuration data, the traffic handling mode indicated in the first
causing the transition of the Application Server state to AS-ACTIVE MAY ASP Active message causing the transition of the Application Server
be used to set the mode. state to AS-ACTIVE MAY be used to set the mode.
In the case of an 0verride mode AS, reception of an ASP Active message In the case of an Override mode AS, reception of an ASP Active
at an SGP causes the (re)direction of all traffic for the AS to the ASP message at an SGP causes the (re)direction of all traffic for the AS
that sent the ASP Active message. Any previously active ASP in the AS to the ASP that sent the ASP Active message. Any previously active
is now considered to be in state ASP-INACTIVE and SHOULD no longer ASP in the AS is now considered to be in the state ASP-INACTIVE and
receive traffic from the SGP within the AS. The SGP then MUST send a SHOULD no longer receive traffic from the SGP within the AS. The SGP
Notify message ("Alternate ASP Active") to the previously active ASP then MUST send a Notify message ("Alternate ASP Active") to the
in the AS, and SHOULD stop traffic to/from that ASP. The ASP receiving previously active ASP in the AS, and SHOULD stop traffic to/from that
this Notify MUST consider itself now in the ASP-INACTIVE state, if it ASP. The ASP receiving this Notify MUST consider itself now in the
is not already aware of this via inter-ASP communication with the ASP-INACTIVE state, if it is not already aware of this via inter-ASP
Overriding ASP. communication with the Overriding ASP.
In the case of a Load-share mode AS, reception of an ASP Active In the case of a Load-share mode AS, reception of an ASP Active
message at an SGP causes the direction of traffic to the ASP sending message at an SGP causes the direction of traffic to the ASP sending
the ASP Active message, in addition to all the other ASPs that are the ASP Active message, in addition to all the other ASPs that are
currently active in the AS. The algorithm at the SGP for load-sharing currently active in the AS. The algorithm at the SGP for load-
traffic within an AS to all the active ASPs is implementation sharing traffic within an AS to all the active ASPs is implementation
dependent. The algorithm could, for example be round-robin or based dependent. The algorithm could, for example be round-robin or based
on information in the Data message (e.g., such as the SLS in the on information in the Data message (e.g., such as the SLS in the
Routing Label). Routing Label).
An SGP, upon reception of an ASP Active message for the first ASP in An SGP, 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 a Load share AS, MAY choose not to direct traffic to a newly active
until it determines that there are sufficient resources to handle the ASP until it determines that there are sufficient resources to handle
expected load (e.g., until there are "n" ASPs in state ASP-ACTIVE in the expected load (e.g., until there are "n" ASPs in state ASP-ACTIVE
the AS). in the AS).
All ASPs within a load-sharing mode AS must be able to process any All ASPs within a load-sharing mode AS must be able to process any
Data message received for the AS, to accommodate any potential Data message received for the AS, to accommodate any potential fail-
fail-over or rebalancing of the offered load. over or balancing of the offered load.
In the case of a Broadcast mode AS, reception of an ASP Active message In the case of a Broadcast mode AS, reception of an ASP Active
at an SGP causes the direction of traffic to the ASP sending the ASP message at an SGP causes the direction of traffic to the ASP sending
Active message, in addition to all the other ASPs that are currently the ASP Active message, in addition to all the other ASPs that are
active in the AS. The algorithm at the SGP for broadcasting currently active in the AS. The algorithm at the SGP for
traffic within an AS to all the active ASPs is a simple broadcast broadcasting traffic within an AS to all the active ASPs is a simple
algorithm, where every message is sent to each of the active ASPs. broadcast algorithm, where every message is sent to each of the
active ASPs.
An SGP, upon reception of an ASP Active message for the first An SGP, upon reception of an ASP Active message for the first ASP in
ASP in a Broadcast AS, MAY choose not to direct traffic to a newly a Broadcast AS, MAY choose not to direct traffic to a newly active
active ASP until it determines that there are sufficient resources to ASP until it determines that there are sufficient resources to handle
handle the expected load (e.g., until there are "n" ASPs in state the expected load (e.g., until there are "n" ASPs in state ASP-ACTIVE
ASP-ACTIVE in the AS). in the AS).
Whenever an ASP in a Broadcast mode AS becomes ASP-ACTIVE, the SGP Whenever an ASP in a Broadcast mode AS becomes ASP-ACTIVE, the SGP
MUST tag the first DATA message broadcast in each SCTP stream with a MUST tag the first DATA message broadcast in each SCTP stream with a
unique Correlation Id parameter. The purpose of this Correlation Id unique Correlation Id parameter. The purpose of this Correlation Id
is to permit the newly active ASP to synchronize its processing of is to permit the newly active ASP to synchronize its processing of
traffic in each ordered stream with the other ASPs in the broadcast traffic in each ordered stream with the other ASPs in the broadcast
group. group.
4.3.4.5 ASP Inactive Procedures 4.3.4.4 ASP Inactive Procedures
When an ASP wishes to withdraw from receiving traffic within an AS, the When an ASP wishes to withdraw from receiving traffic within an AS,
ASP sends an ASP Inactive message to the SGP. This action MAY be the ASP sends an ASP Inactive message to the SGP. This action MAY be
initiated at the ASP by an M-ASP_INACTIVE request primitive from initiated at the ASP by an M-ASP_INACTIVE request primitive from
Layer Management or MAY be initiated automatically by an M2UA Layer Management or MAY be initiated automatically by an M2UA
management function. In the case where an ASP is processing the management function. In the case where an ASP is processing the
traffic for more than one Application Server across a common SCTP traffic for more than one Application Server across a common SCTP
association, the ASP Inactive message contains one or more Interface association, the ASP Inactive message contains one or more Interface
Identifiers to indicate for which Application Servers the ASP Inactive Identifiers to indicate for which Application Servers the ASP
message applies. In the case where an ASP Inactive message does not Inactive message applies. In the case where an ASP Inactive message
contain a Interface Identifier parameter, the receiver must know, via does not contain a Interface Identifier parameter, the receiver must
configuration data, which Application Servers the ASP is a member and know, via configuration data, of which Application Servers the ASP is
move the ASP to the ASP-INACTIVE state in all Application Servers. a member and move the ASP to the ASP-INACTIVE state in all
In the case of an Override mode AS, where another ASP has already Application Servers. In the case of an Override mode AS, where
taken over the traffic within the AS with an ASP Active ("Override") another ASP has already taken over the traffic within the AS with an
message, the ASP that sends the ASP Inactive message is already ASP Active ("Override") message, the ASP that sends the ASP Inactive
considered by the SGP to be in state ASP-INACTIVE. An ASP Inactive message is already considered by the SGP to be in the state ASP-
Ack message is sent to the ASP, after ensuring that all traffic is INACTIVE. An ASP Inactive Ack message is sent to the ASP, after
stopped to the ASP. ensuring that all traffic is stopped to the ASP.
In the case of a Load-share mode AS, the SGP moves the ASP to the ASP- In the case of a Load-share mode AS, the SGP moves the ASP to the
INACTIVE state and the AS traffic is re-allocated across the remaining ASP-INACTIVE state and the AS traffic is re-allocated across the
ASPs in the state ASP-ACTIVE, as per the load-sharing algorithm remaining ASPs in the state ASP-ACTIVE, as per the load-sharing
currently used within the AS. A Notify message ("Insufficient ASP algorithm currently used within the AS. A Notify message
resources active in AS") MAY be sent to all inactive ASPs, if required. ("Insufficient ASP resources active in AS") MAY be sent to all
An ASP Inactive Ack message is sent to the ASP after all traffic inactive ASPs, if required. An ASP Inactive Ack message is sent to
is halted and Layer Management is informed with an M-ASP_INACTIVE the ASP after all traffic is halted and Layer Management is informed
indication primitive. with an M-ASP_INACTIVE indication primitive.
In the case of a Broadcast mode AS, the SGP moves the ASP to the 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 ASP-INACTIVE state and the AS traffic is broadcast only to the
remaining ASPs in the state ASP-ACTIVE. A Notify message remaining ASPs in the state ASP-ACTIVE. A Notify message
("Insufficient ASP resources active in AS") MAY be sent to all ("Insufficient ASP resources active in AS") MAY be sent to all
inactive ASPs, if required. An ASP Inactive Ack message is sent to inactive ASPs, if required. An ASP Inactive Ack message is sent to
the ASP after all traffic is halted and Layer Management is informed the ASP after all traffic is halted and Layer Management is informed
with an M-ASP_INACTIVE indication primitive. with an M-ASP_INACTIVE indication primitive.
Multiple ASP Inactive Ack messages MAY be used in response to an Multiple ASP Inactive Ack messages MAY be used in response to an ASP
ASP Inactive message containing multiple Interface Identifers, Inactive message containing multiple Interface Identifiers, allowing
allowing the SGP to independently acknowledge for different (sets the SGP to independently acknowledge for different (sets of)
of) Interface Identifiers. The SGP sends an Error message ("Invalid Interface Identifiers. The SGP sends an Error message ("Invalid
Interface Identifier") message for each invalid or unconfigured Interface Identifier") for each invalid or not configured Interface
Interface Identifer value in a received ASP Inactive message. Identifier value in a received ASP Inactive message.
The SGP MUST send an ASP Inactive Ack message in response to a received The SGP MUST send an ASP Inactive Ack message in response to a
ASP Inactive message from the ASP and the ASP is already marked as ASP- received ASP Inactive message from the ASP and the ASP is already
INACTIVE at the SGP. marked as ASP-INACTIVE at the SGP.
At the ASP, the ASP Inactive Ack message received is not acknowledged. At the ASP, the ASP Inactive Ack message received is not
Layer Management is informed with an M-ASP_INACTIVE confirm primitive. acknowledged. Layer Management is informed with an M-ASP_INACTIVE
If the ASP receives an ASP Inactive Ack without having sent an ASP confirm primitive. If the ASP receives an ASP Inactive Ack without
Inactive message, the ASP SHOULD now consider itself as in the having sent an ASP Inactive message, the ASP SHOULD now consider
ASP-INACTIVE state. If the ASP was previously in the ASP-ACTIVE itself as in the ASP-INACTIVE state. If the ASP was previously in
state, the ASP SHOULD then initiate procedures to return itself to the ASP-ACTIVE state, the ASP SHOULD then initiate procedures to
its previous state. return itself to its previous state.
When the ASP sends an ASP Inactive message it starts timer T(ack). When the ASP sends an ASP Inactive message it starts timer
If the ASP does not receive a response to an ASP Inactive message T(ack). If the ASP does not receive a response to an ASP Inactive
within T(ack), the ASP MAY restart T(ack) and resend ASP Inactive message within T(ack), the ASP MAY restart T(ack) and resend ASP
messages until it receives an ASP Inactive Ack message. T(ack) is Inactive messages until it receives an ASP Inactive Ack message.
provisionable, with a default of 2 seconds. Alternatively, T(ack) is provisionable, with a default of 2 seconds. Alternatively,
retransmission of ASP Inactive messages MAY be put under control of retransmission of ASP Inactive messages MAY be put under the control
Layer Management. In this method, expiry of T(ack) results in a M- of Layer Management. In this method, expiry of T(ack) results in a
ASP_Inactive confirm primitive carrying a negative indication. M-ASP_Inactive confirm primitive carrying a negative indication.
If no other ASPs in the Application Server are in the state ASP-ACTIVE, If no other ASPs in the Application Server are in the state ASP-
the SGP MUST send a Notify message ("AS-Pending") to all of the ASPs ACTIVE, the SGP MUST send a Notify message ("AS-Pending") to all of
in the AS which are in the state ASP-INACTIVE. The SGP SHOULD start the ASPs in the AS which are in the state ASP-INACTIVE. The SGP
buffering the incoming messages for T(r)seconds, after which messages SHOULD start buffering the incoming messages for T(r)seconds, after
MAY be discarded. T(r) is configurable by the network operator. If which messages MAY be discarded. T(r) is configurable by the network
the SGP receives an ASP Active message from an ASP in the AS before operator. If the SGP receives an ASP Active message from an ASP in
expiry of T(r), the buffered traffic is directed to that ASP and the the AS before expiry of T(r), the buffered traffic is directed to
timer is cancelled. If T(r) expires, the AS is moved to the that ASP and the timer is canceled. If T(r) expires, the AS is moved
AS-INACTIVE state. to the AS-INACTIVE state.
4.3.4.6 Notify Procedures 4.3.4.5 Notify Procedures
A Notify message reflecting a change in the AS state MUST be sent to 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 all ASPs in the AS, except those in the ASP-DOWN state, with
appropriate Status Information and any ASP Identifier of the failed appropriate Status Information and any ASP Identifier of the failed
ASP. At the ASP, Layer Management is informed with an M-NOTIFY ASP. At the ASP, Layer Management is informed with an M-NOTIFY
indication primitive. The Notify message MUST be sent whether the indication primitive. The Notify message MUST be sent whether the AS
AS state change was a result of an ASP failure or reception of an state change was a result of an ASP failure or reception of an ASP
ASP State Management (ASPSM) / ASP Traffic Management (ASPTM) message. State Management (ASPSM) / ASP Traffic Management (ASPTM) message.
In the second case, the Notify message MUST be sent after any related In the second case, the Notify message MUST be sent after any related
acknowledgement messages (e.g., ASP Up Ack, ASP Down Ack, ASP Active acknowledgment messages (e.g., ASP Up Ack, ASP Down Ack, ASP Active
Ack, or ASP Inactive Ack). Ack, or ASP Inactive Ack).
In the case where a Notify ("AS-PENDING") message is sent by an In the case where a Notify ("AS-PENDING") message is sent by an SGP
SGP that now has no ASPs active to service the traffic, or where a that now has no ASPs active to service the traffic, or where a Notify
Notify ("Insufficient ASP resources active in AS") message MUST be sent ("Insufficient ASP resources active in AS") message MUST be sent in
in the Loadshare or Broadcast mode, the Notify message does not the Load share or Broadcast mode, the Notify message does not
explicitly compel the ASP(s) receiving the message to become active. explicitly compel the ASP(s) receiving the message to become active.
The ASPs remain in control of what (and when) traffic action is taken. The ASPs remain in control of what (and when) traffic action is
taken.
In the case where a Notify message does not contain a Interface In the case where a Notify message does not contain a Interface
Identifier parameter, the receiver must know, via configuration data, Identifier parameter, the receiver must know, via configuration data,
of which Application Servers the ASP is a member and take the of which Application Servers the ASP is a member and take the
appropriate action in each AS. appropriate action in each AS.
4.3.4.7 Heartbeat Procedures 4.3.4.6 Heartbeat Procedures
The optional Heartbeat procedures MAY be used when operating over The optional Heartbeat procedures MAY be used when operating over
transport layers that do not have their own heartbeat mechanism for transport layers that do not have their own heartbeat mechanism for
detecting loss of the transport association (i.e., other than SCTP). detecting loss of the transport association (i.e., other than SCTP).
Either M2UA peer may optionally send Heartbeat messages periodically, Either M2UA peer may optionally send Heartbeat messages periodically,
subject to a provisionable timer T(beat). Upon receiving a Heartbeat subject to a provisionable timer T(beat). Upon receiving a Heartbeat
message, the M2UA peer MUST respond with a Heartbeat Ack message. message, the M2UA peer MUST respond with a Heartbeat Ack message.
If no Heartbeat Ack message (or any other M2UA message) is received If no Heartbeat Ack message (or any other M2UA message) is received
from the M2UA peer within 2*T(beat), the remote M2UA peer is considered from the M2UA peer within 2*T(beat), the remote M2UA peer is
unavailable. Transmission of Heartbeat messages is stopped and the considered unavailable. Transmission of Heartbeat messages is
signalling process SHOULD attempt to re-establish communication if it stopped and the signalling process SHOULD attempt to re-establish
is configured as the client for the disconnected M2UA peer. communication if it is configured as the client for the disconnected
M2UA peer.
The Heartbeat message may optionally contain an opaque Heartbeat Data The Heartbeat message may optionally contain an opaque Heartbeat Data
parameter that MUST be echoed back unchanged in the related Heartbeat parameter that MUST be echoed back unchanged in the related Heartbeat
Ack message. The sender, upon examining the contents of the returned Ack message. The sender, upon examining the contents of the returned
Heartbeat Ack message, MAY choose to consider the remote M2UA peer as Heartbeat Ack message, MAY choose to consider the remote M2UA peer as
unavailable. The contents/format of the Heartbeat Data parameter is unavailable. The contents/format of the Heartbeat Data parameter is
implementation-dependent and only of local interest to the original implementation-dependent and only of local interest to the original
sender. The contents may be used, for example, to support a Heartbeat sender. The contents may be used, for example, to support a
sequence algorithm (to detect missing Heartbeats), and/or a timestamp Heartbeat sequence algorithm (to detect missing Heartbeats), and/or a
mechanism (to evaluate delays). time stamp mechanism (to evaluate delays).
Note: Heartbeat related events are not shown in Figure 5 "ASP state Note: Heartbeat related events are not shown in Figure 5 "ASP state
transition diagram". transition diagram".
4.4 Link Key Management Procedures 4.4 Link Key Management Procedures
The Interface Identifier Management procedures are optional. They can The Interface Identifier Management procedures are optional. They
be used to support automatic allocation of Signalling Terminals or can be used to support automatic allocation of Signalling Terminals
Signalling Data Links [2][3]. or Signalling Data Links [2][3].
4.4.1 Registration 4.4.1 Registration
An ASP MAY dynamically register with an SGP as an ASP within an An ASP MAY dynamically register with an SGP as an ASP within an
Application Server for individual Interface Identifier(s) using Application Server for individual Interface Identifier(s) using the
the REG REQ message. A Link Key parameter in the REG REQ specifies REG REQ message. A Link Key parameter in the REG REQ specifies the
the parameters associated with the Link Key. parameters associated with the Link Key.
The SGP examines the contents of the received Link Key parameters (SDLI The SGP examines the contents of the received Link Key parameters
and SDTI) and compares them with the currently provisioned Interface (SDLI and SDTI) and compares them with the currently provisioned
Identifiers. If the received Link Key matches an existing SGP Link Key Interface Identifiers. If the received Link Key matches an existing
entry, and the ASP is not currently included in the list of ASPs for SGP Link Key entry, and the ASP is not currently included in the list
the related Application Server, the SGP MAY authorize the ASP to be of ASPs for the related Application Server, the SGP MAY authorize the
added to the AS. Or, if the Link Key does not currently exist and the ASP to be added to the AS. Or, if the Link Key does not currently
received Link Key data is valid and unique, an SGP supporting dynamic exist and the received Link Key data is valid and unique, an SGP
configuration MAY authorize the creation of a new Interface Identifier supporting dynamic configuration MAY authorize the creation of a new
and related Application Server and add the ASP to the new AS. In either Interface Identifier and related Application Server and add the ASP
case, the SGP returns a Registration Response message to the ASP, to the new AS. In either case, the SGP returns a Registration
containing the same Local-LK-Identifier as provided in the initial Response message to the ASP, containing the same Local-LK-Identifier
request, a Registration Result "Successfully Registered" and the as provided in the initial request, a Registration Result
Interface Identifier. A unique method of Interface Identifier valid "Successfully Registered" and the Interface Identifier. A unique
assignment at the SG/SGP is implementation dependent but MUST be method of Interface Identifier valid assignment at the SG/SGP is
guaranteed to be unique for each Application server or Link Key implementation dependent but MUST be guaranteed to be unique for each
served by SGP. Application server or Link Key served by SGP.
If the SGP determines that the received Link Key data is invalid, or If the SGP determines that the received Link Key data is invalid, or
contains invalid parameter values, the SGP returns a Registration contains invalid parameter values, the SGP returns a Registration
Response message to the ASP, containing a Registration Result "Error Response message to the ASP, containing a Registration Result "Error
- Invalid Link Key", "Error - Invalid SDTI", "Error - Invalid SDLI" - Invalid Link Key", "Error - Invalid SDTI", "Error - Invalid SDLI"
as appropriate. as appropriate.
If the SGP determins that the Link Key parameter overlaps with an If the SGP determines that the Link Key parameter overlaps with an
existing Link Key entry, the SGP returns a Registration Response existing Link Key entry, the SGP returns a Registration Response
message to the ASP, with a Registration Status of "Error - message to the ASP, with a Registration Status of "Error -
Overlapping (Non-Unique) Link Key". An incoming signalling message Overlapping (Non-Unique) Link Key". An incoming signalling message
received at an SGP cannot match against more than one Link Key. received at an SGP cannot match against more than one Link Key.
If the SGP does not authorize the registration request, the SGP If the SGP does not authorize the registration request, the SGP
returns a REG RSP message to the ASP containing the Registration returns a REG RSP message to the ASP containing the Registration
Result "Error - Permission Denied". Result "Error - Permission Denied".
If an SGP determines that a received Link Key does not currently If an SGP determines that a received Link Key does not currently
exist and the SGP does not support dynamic configuration, the SGP exist and the SGP does not support dynamic configuration, the SGP
returns a Registration Response message to the ASP, containing a returns a Registration Response message to the ASP, containing a
Registration Result "Error - Link Key not Provisioned". Registration Result "Error - Link Key not Provisioned".
If an SGP determines that a received Link Key does not currently If an SGP determines that a received Link Key does not currently
exist and the SGP supports dynamic reconfiguration but does not have exist and the SGP supports dynamic reconfiguration but does not have
the capacity to add new Link Key and Application Server entries, the the capacity to add new Link Key and Application Server entries, the
SGP returns a Registration Response message to the ASP, containing a SGP returns a Registration Response message to the ASP, containing a
Registration Result "Error - Insufficient Resources". Registration Result "Error - Insufficient Resources".
An ASP MAY register multiple Link Keys at once by including a number An ASP MAY register multiple Link Keys at once by including a number
of Link Key parameters in a single REG REQ message. The SGP MAY of Link Key parameters in a single REG REQ message. The SGP MAY
response to each registration request in a single REG RSP message, respond to each registration request in a single REG RSP message,
indicating the success or failure result for each Link Key in a indicating the success or failure result for each Link Key in a
separate Registration Result parameter. Alternatively, the SGP MAY separate Registration Result parameter. Alternatively, the SGP MAY
respond with multiple REG RSP messages, each with one or more respond with multiple REG RSP messages, each with one or more
Registration Result parameters. The ASP uses the Local-LK-Identifier Registration Result parameters. The ASP uses the Local-LK-Identifier
parameter to correlate the requests with the responses. parameter to correlate the requests with the responses.
4.4.2 Deregistration 4.4.2 Deregistration
An ASP MAY dynamically de-register with an SGP as an ASP within an An ASP MAY dynamically de-register with an SGP as an ASP within an
Application Server for individual Interface Identifier(s) using Application Server for individual Interface Identifier(s) using the
the DEREG REQ message. A Interface Identifier parameter in the DEREG REQ message. A Interface Identifier parameter in the DEREG REQ
DEREG REQ specifies which Interface Identifier to de-register. specifies which Interface Identifier to de-register.
The SGP examines the contents of the received Interface Identifier The SGP examines the contents of the received Interface Identifier
parameter and validates that the ASP is currently registered in the parameter and validates that the ASP is currently registered in the
Application Server(s) related to the included Interface Application Server(s) related to the included Interface
Identifier(s). If validated, the ASP is de-registered as an ASP in Identifier(s). If validated, the ASP is de-registered as an ASP in
the related Application Server. the related Application Server.
The deregistration procedure does not necessarily imply the deletion The deregistration procedure does not necessarily imply the deletion
of Link Key and Application Server configuration data at the SGP. of Link Key and Application Server configuration data at the SGP.
Other ASPs may continue to be associated with the Application Other ASPs may continue to be associated with the Application Server,
Server, in which case the Link Key data CANNOT be deleted. If a in which case the Link Key data CANNOT be deleted. If a
Deregistration results in no more ASPs in an Application Server, an Deregistration results in no more ASPs in an Application Server, an
SGP MAY delete the Link Key data. SGP MAY delete the Link Key data.
The SGP acknowledges the de-registration requires by returning a DEREG The SGP acknowledges the de-registration required by returning a
RSP to the requesting ASP. The result of the de-registration is DEREG RSP to the requesting ASP. The result of the de-registration
found in the Deregistration Result parameter, indicating success or is found in the Deregistration Result parameter, indicating success
failure with cause. or failure with cause.
An ASP MAY de-register multiple Interface Identifiers at once by An ASP MAY de-register multiple Interface Identifiers at once by
including a number of Interface Identifiers in a single DEREG REQ including a number of Interface Identifiers in a single DEREG REQ
message. The SGP MUST response to each deregistration request in a message. The SGP MUST respond to each deregistration request in a
single DEREG RSP message, indicating the success or failure result single DEREG RSP message, indicating the success or failure result
for each Interface Identifier in a separate Deregistration Result for each Interface Identifier in a separate Deregistration Result
parameter. parameter.
5.0 Examples of MTP2 User Adaptation (M2UA) Procedures 5.0 Examples of MTP2 User Adaptation (M2UA) Procedures
5.1 Establishment of associations between SGP and MGC examples 5.1 Establishment of associations between SGP and MGC examples
5.1.1 Single ASP in an Application Server (1+0 sparing) 5.1.1 Single ASP in an Application Server (1+0 sparing)
This scenario shows the example M2UA message flows for the establishment This scenario shows the example M2UA message flows for the
of traffic between an SGP and an ASP, where only one ASP is configured establishment of traffic between an SGP and an ASP, where only one
within an AS (no backup). It is assumed that the SCTP association is ASP is configured within an AS (no backup). It is assumed that the
already set-up. SCTP association is already set-up.
SGP ASP1 SGP ASP1
| |
|<---------ASP Up----------| |<---------ASP Up----------|
|--------ASP Up Ack------->| |--------ASP Up Ack------->|
| | | |
|<-------ASP Active--------| |<-------ASP Active--------|
|------ASP Active Ack----->| |------ASP Active Ack----->|
| | | |
|------NTFY(AS-ACTIVE)---->| |------NTFY(AS-ACTIVE)---->|
5.1.2 Single ASP in an Application Server (1+0 sparing) with Dynamic 5.1.2 Single ASP in an Application Server (1+0 sparing) with Dynamic
Registration Registration
This scenario is the same as the one shown in Section 5.1.1 except This scenario is the same as the one shown in Section 5.1.1 except
with a dynamic registration (automatic allocation) of Interface with a dynamic registration (automatic allocation) of an Interface
Identifier(s). Identifier(s).
SGP ASP1 SGP ASP1
| |
|<---------ASP Up----------| |<---------ASP Up----------|
|--------ASP Up Ack------->| |--------ASP Up Ack------->|
| | | |
|<--------REG REQ----------| |<--------REG REQ----------|
|------REG REQ RESP------->| |------REG REQ RESP------->|
| | | |
|<-------ASP Active--------| |<-------ASP Active--------|
|------ASP Active Ack----->| |------ASP Active Ack----->|
| | | |
|------NTFY(AS-ACTIVE)---->| |------NTFY(AS-ACTIVE)---->|
5.1.3 Two ASPs in Application Server (1+1 sparing) 5.1.3 Two ASPs in Application Server (1+1 sparing)
This scenario shows the example M2UA message flows for the establishment This scenario shows the example M2UA message flows for the
of traffic between an SGP and two ASPs in the same Application Server, establishment of traffic between an SGP and two ASPs in the same
where ASP1 is configured to be active and ASP2 to be standby in the event Application Server, where ASP1 is configured to be active and ASP2 to
of communication failure or the withdrawal from service of ASP1. ASP2 MAY be standby in the event of communication failure or the withdrawal
act as a hot, warm, or cold standby depending on the extent to which ASP1 from service of ASP1. ASP2 MAY act as a hot, warm, or cold standby
and ASP2 share call/transaction state or can communicate call state under depending on the extent to which ASP1 and ASP2 share call/transaction
failure/withdrawal events. state or can communicate call state under failure/withdrawal events.
SGP ASP1 ASP2 SGP ASP1 ASP2
| | | | | |
|<--------ASP Up----------| | |<--------ASP Up----------| |
|-------ASP Up Ack------->| | |-------ASP Up Ack------->| |
| | | | | |
|<-----------------------------ASP Up----------------| |<-----------------------------ASP Up----------------|
|----------------------------ASP Up Ack------------->| |----------------------------ASP Up Ack------------->|
| | | | | |
| | | | | |
|<-------ASP Active-------| | |<-------ASP Active-------| |
|-----ASP Active Ack----->| | |-----ASP Active Ack----->| |
| | | | | |
| | | | | |
|-----NTFY(AS-ACTIVE)---->| | |-----NTFY(AS-ACTIVE)---->| |
| | | | | |
|------------------NTFY(AS-ACTIVE)------------------>| |------------------NTFY(AS-ACTIVE)------------------>|
5.2 ASP Traffic Fail-over Examples 5.2 ASP Traffic Fail-over Examples
5.2.1 (1+1 Sparing, withdrawal of ASP, backup Override) 5.2.1 (1+1 Sparing, withdrawal of ASP, backup Override)
Following on from the example in Section 5.1.2, and ASP withdraws from Following on from the example in Section 5.1.2, and ASP withdraws
service: from service:
SGP ASP1 ASP2 SGP ASP1 ASP2
| | | | | |
|<-----ASP Inactive-------| | |<-----ASP Inactive-------| |
|----ASP Inactive Ack---->| | |----ASP Inactive Ack---->| |
| | | | | |
|------------------NTFY(AS-PENDING)----------------->| |----NTFY(AS-PENDING)---->| |
| | | |------------------NTFY(AS-PENDING)----------------->|
|<------------------------------ ASP Active----------| | | |
|-----------------------------ASP Active Ack-------->| |<------------------------------ ASP Active----------|
| | | |-----------------------------ASP Active Ack-------->|
|------------------NTFY(AS-ACTIVE)------------------>| | | |
| | | |-----NTFY(AS-ACTIVE)---->| |
|------------------NTFY(AS-ACTIVE)------------------>|
| | |
In this case, the SGP notifies ASP2 that the AS has moved to the In this case, the SGP notifies ASP2 that the AS has moved to the AS-
AS-PENDING state. ASP2 sends ASP Active to bring the AS back to PENDING state. ASP2 sends ASP Active to bring the AS back to the
the AS-ACTIVE state. If ASP2 did not send the ASP Active message AS-ACTIVE state. If ASP2 did not send the ASP Active message before
before T(r) expired, the SGP would send a NOTIFY (AS-DOWN). T(r) expired, the SGP would send a NOTIFY (AS-DOWN).
Note: If the SGP detects loss of the M2UA peer (through a detection Note: If the SGP detects loss of the M2UA peer (through a detection
of SCTP failure), the initial SGP-ASP1 ASP Inactive message exchange of SCTP failure), the initial SGP-ASP1 ASP Inactive message
would not occur. exchange would not occur.
SGP ASP1 ASP2 SGP ASP1 ASP2
| | | | | |
(detects SCTP failure) (detects SCTP failure)
|------------------NTFY(AS-PENDING)----------------->| |------------------NTFY(AS-PENDING)----------------->|
| | | | | |
|<------------------------------ ASP Active----------| |<------------------------------ ASP Active----------|
|-----------------------------ASP Active Ack-------->| |-----------------------------ASP Active Ack-------->|
| | | | | |
|------------------NTFY(AS-ACTIVE)------------------>| |------------------NTFY(AS-ACTIVE)------------------>|
| | | | | |
5.2.2 (1+1 Sparing, backup Override) 5.2.2 (1+1 Sparing, backup Override)
Following on from the example in Section 5.1.2, and ASP2 wishes to Following on from the example in Section 5.1.2, and ASP2 wishes to
override ASP1 and take over the traffic: override ASP1 and take over the traffic:
SGP ASP1 ASP2 SGP ASP1 ASP2
| | | | | |
|<-------------------------------ASP Active----------| |<-------------------------------ASP Active----------|
|-----------------------------ASP Active Ack-------->| |-----------------------------ASP Active Ack-------->|
|----NTFY(Alt ASP-Act)--->| | |----NTFY(Alt ASP-Act)--->| |
| | | | | |
In this case, the SGP notifies ASP1 that an alternative ASP has In this case, the SGP notifies ASP1 that an alternative ASP has
overridden it. overridden it.
5.3 SGP to MGC, MTP Level 2 to MTP Level 3 Boundary Procedures 5.3 SGP to MGC, MTP Level 2 to MTP Level 3 Boundary Procedures
When the M2UA layer on the ASP has a MAUP message to send to the SGP, it When the M2UA layer on the ASP has a MAUP message to send to the SGP,
will do the following: it will do the following:
- Determine the correct SGP - Determine the correct SGP
- Find the SCTP association to the chosen SGP - Find the SCTP association to the chosen SGP
- Determine the correct stream in the SCTP association based on - Determine the correct stream in the SCTP association based on
the SS7 link the SS7 link
- Fill in the MAUP message, fill in M2UA Message Header, fill in - Fill in the MAUP message, fill in M2UA Message Header, fill in
Common Header Common Header
- Send the MAUP message to the remote M2UA peer in the SGP, over the - Send the MAUP message to the remote M2UA peer in the SGP, over
SCTP association the SCTP association
When the M2UA layer on the SGP has a MAUP message to send to the ASP, it When the M2UA layer on the SGP has a MAUP message to send to the ASP,
will do the following: it will do the following:
- Determine the AS for the Interface Identifier - Determine the AS for the Interface Identifier
- Determine the Active ASP (SCTP association) within the AS - Determine the Active ASP (SCTP association) within the AS
- Determine the correct stream in the SCTP association based on - Determine the correct stream in the SCTP association based on
the SS7 link the SS7 link
- Fill in the MAUP message, fill in M2UA Message Header, fill in - Fill in the MAUP message, fill in M2UA Message Header, fill in
Common Header Common Header
- Send the MAUP message to the remote M2UA peer in the ASP, over the - Send the MAUP message to the remote M2UA peer in the ASP, over
SCTP association the SCTP association
5.3.1 SS7 Link Alignment 5.3.1 SS7 Link Alignment
The MGC can request that a SS7 link be brought into alignment using the The MGC can request that a SS7 link be brought into alignment using
normal or emergency procedure [2][3]. An example of the message flow the normal or emergency procedure [2][3]. An example of the message
to bring a SS7 link in-service using the normal alignment procedure is flow to bring a SS7 link in-service using the normal alignment
shown below. procedure is shown below.
MTP2 M2UA M2UA MTP3 MTP2 M2UA M2UA MTP3
SGP SGP ASP ASP SGP SGP ASP ASP
<----Start Req---|<---Establish Req----|<----Start Req------ <----Start Req---|<---Establish Req----|<----Start Req------
---In Serv Ind-->|----Establish Cfm--->|----In Serv Ind----> ---In Serv Ind-->|----Establish Cfm--->|----In Serv Ind---->
An example of the message flow to bring a SS7 link in-service using the An example of the message flow to bring a SS7 link in-service using
emergency alignment procedure. the emergency alignment procedure.
MTP2 M2UA M2UA MTP3 MTP2 M2UA M2UA MTP3
SGP SGP ASP ASP SGP SGP ASP ASP
<----Emer Req----|<--State Req (STATUS_EMER_SET)----|<----Emer Req--- <----Emer Req----|<--State Req (STATUS_EMER_SET)----|<----Emer Req---
-----Emer Cfm--->|---State Cfm (STATUS_EMER_SET)--->|----Emer Cfm----> -----Emer Cfm--->|---State Cfm (STATUS_EMER_SET)--->|----Emer Cfm---->
<---Start Req----|<-------Establish Req-------------|<---Start Req---- <---Start Req----|<-------Establish Req-------------|<---Start Req----
---In Serv Ind-->|--------Establish Cfm------------>|---In Serv Ind--> ---In Serv Ind-->|--------Establish Cfm------------>|---In Serv Ind-->
5.3.2 SS7 Link Release 5.3.2 SS7 Link Release
The MGC can request that a SS7 link be taken out-of-service. It uses The MGC can request that a SS7 link be taken out-of-service. It uses
the Release Request message as shown below. the Release Request message as shown below.
MTP2 M2UA M2UA MTP3 MTP2 M2UA M2UA MTP3
SGP SGP ASP ASP SGP SGP ASP ASP
<-----Stop Req-----|<---Release Req------|<-----Stop Req------ <-----Stop Req-----|<---Release Req------|<-----Stop Req------
--Out of Serv Ind->|----Release Cfm----->|--Out of Serv Ind--> --Out of Serv Ind->|----Release Cfm----->|--Out of Serv Ind-->
The SGP can autonomously indicate that a SS7 link has gone out-of- The SGP can autonomously indicate that a SS7 link has gone out-of-
service as shown below. service as shown below.
MTP2 M2UA M2UA MTP3 MTP2 M2UA M2UA MTP3
SGP SGP ASP ASP SGP SGP ASP ASP
--Out of Serv->|----Release Ind----->|--Out of Serv--> --Out of Serv->|----Release Ind----->|--Out of Serv-->
5.3.3 Set and Clear Local Processor Outage 5.3.3 Set and Clear Local Processor Outage
The MGC can set a Local Processor Outage condition. It uses the The MGC can set a Local Processor Outage condition. It uses the
State Request message as shown below. State Request message as shown below.
MTP2 M2UA M2UA MTP3 MTP2 M2UA M2UA MTP3
SGP SGP ASP ASP SGP SGP ASP ASP
<----LPO Req----|<---State Req (STATUS_LPO_SET)----|<----LPO Req--- <----LPO Req----|<---State Req (STATUS_LPO_SET)----|<----LPO Req---
-----LPO Cfm--->|----State Cfm (STATUS_LPO_SET)--->|----LPO Cfm----> -----LPO Cfm--->|----State Cfm (STATUS_LPO_SET)--->|----LPO Cfm---->
The MGC can clear a Local Processor Outage condition. It uses the The MGC can clear a Local Processor Outage condition. It uses the
State Request message as shown below. State Request message as shown below.
MTP2 M2UA M2UA MTP3 MTP2 M2UA M2UA MTP3
SGP SGP ASP ASP SGP SGP ASP ASP
<---LPO Req---|<---State Req (STATUS_LPO_CLEAR)----|<----LPO Req--- <---LPO Req---|<---State Req (STATUS_LPO_CLEAR)----|<----LPO Req---
----LPO Cfm-->|----State Cfm (STATUS_LPO_CLEAR)--->|----LPO Cfm----> ----LPO Cfm-->|----State Cfm (STATUS_LPO_CLEAR)--->|----LPO Cfm---->
5.3.4 Notification of Remote Processor Outage 5.3.4 Notification of Remote Processor Outage
The SGP can indicate Remote has entered or exited the Processor Outage The SGP can indicate that Remote has entered or exited the Processor
condition for a SS7 link. It uses the State Indication message as shown Outage condition for a SS7 link. It uses the State Indication
below. message as shown below.
MTP2 M2UA M2UA MTP3 MTP2 M2UA M2UA MTP3
SGP SGP ASP ASP SGP SGP ASP ASP
----RPO Ind---->|----State Ind (EVENT_RPO_ENTER)-->|-----RPO Ind----> ----RPO Ind---->|----State Ind (EVENT_RPO_ENTER)-->|-----RPO Ind---->
-RPO Rcvr Ind-->|----State Ind (EVENT_RPO_EXIT)--->|--RPO Rcvr Ind--> -RPO Rcvr Ind-->|----State Ind (EVENT_RPO_EXIT)--->|--RPO Rcvr Ind-->
5.3.5 Notification of SS7 Link Congestion 5.3.5 Notification of SS7 Link Congestion
The SGP can indicate that a SS7 link has become congested. It uses the The SGP can indicate that a SS7 link has become congested. It uses
Congestion Indication message as shown below. the Congestion Indication message as shown below.
MTP2 M2UA M2UA MTP3 MTP2 M2UA M2UA MTP3
SGP SGP ASP ASP SGP SGP ASP ASP
----Cong Ind---->|--------Cong Ind (STATUS)------->|----Cong Ind----> ----Cong Ind---->|--------Cong Ind (STATUS)------->|----Cong Ind---->
-Cong Cease Ind->|--------Cong Ind (STATUS)------->|-Cong Cease Ind-> -Cong Cease Ind->|--------Cong Ind (STATUS)------->|-Cong Cease Ind->
5.3.6 SS7 Link Changeover 5.3.6 SS7 Link Changeover
An example of the message flow for an error free changeover is shown An example of the message flow for an error free changeover is shown
below. In this example, there were three messages in the retransmission below. In this example, there were three messages in the
queue that needed to be retrieved. retransmission queue that needed to be retrieved.
MTP2 M2UA M2UA MTP3 MTP2 M2UA M2UA MTP3
SGP SGP ASP ASP SGP SGP ASP ASP
<-Rtrv BSN Req-|<--Rtrv Req (ACTION_RTRV_BSN)--|<--Rtrv BSN Req--- <-Rtrv BSN Req-|<--Rtrv Req (ACTION_RTRV_BSN)--|<--Rtrv BSN Req---
(seq_num = 0) (seq_num = 0)
-Rtrv BSN Cfm->|---Rtrv Cfm (ACTION_RTRV_BSN)->|---Rtrv BSN Cfm--> -Rtrv BSN Cfm->|---Rtrv Cfm (ACTION_RTRV_BSN)->|---Rtrv BSN Cfm-->
(seq_num = BSN) (seq_num = BSN)
skipping to change at page 68, line 67 skipping to change at page 81, line 44
-Rtrv Msg Cfm->|--Rtrv Cfm (ACTION_RTRV_MSGS)->|---Rtrv Msg Cfm--> -Rtrv Msg Cfm->|--Rtrv Cfm (ACTION_RTRV_MSGS)->|---Rtrv Msg Cfm-->
(seq_num = 0) (seq_num = 0)
-Rtrv Msg Ind->|---------Retrieval Ind ------->|---Rtrv Msg Ind--> -Rtrv Msg Ind->|---------Retrieval Ind ------->|---Rtrv Msg Ind-->
-Rtrv Msg Ind->|---------Retrieval Ind ------->|---Rtrv Msg Ind--> -Rtrv Msg Ind->|---------Retrieval Ind ------->|---Rtrv Msg Ind-->
-Rtrv Msg Ind->|---------Retrieval Ind ------->|---Rtrv Msg Ind--> -Rtrv Msg Ind->|---------Retrieval Ind ------->|---Rtrv Msg Ind-->
-Rtrv Compl Ind->|----Retrieval Compl Ind ---->|-Rtrv Compl Ind--> -Rtrv Compl Ind->|----Retrieval Compl Ind ---->|-Rtrv Compl Ind-->
Note: The number of Retrieval Indication is dependent on the number of Note: The number of Retrieval Indication is dependent on the
messages in the retransmit queue that have been requested. Only one number of messages in the retransmit queue that have been
Retrieval Complete Indication SHOULD be sent. requested. Only one Retrieval Complete Indication SHOULD be
sent.
An example of a message flow with an error retrieving the BSN is shown An example of a message flow with an error retrieving the BSN is
below. shown below.
MTP2 M2UA M2UA MTP3 MTP2 M2UA M2UA MTP3
SGP SGP ASP ASP SGP SGP ASP ASP
<-Rtrv BSN Req-|<--Rtrv Req (ACTION_RTRV_BSN)--|<--Rtrv BSN Req--- <-Rtrv BSN Req-|<--Rtrv Req (ACTION_RTRV_BSN)--|<--Rtrv BSN Req---
-BSN Not Rtrv->|---Rtrv Cfm (ACTION_RTRV_BSN)->|---BSN Not Rtrv--> -BSN Not Rtrv->|---Rtrv Cfm (ACTION_RTRV_BSN)->|---BSN Not Rtrv-->
(seq_num = -1) (seq_num = -1)
An example of a message flow with an error retrieving the messages is An example of a message flow with an error retrieving the messages is
shown below. shown below.
<-Rtrv BSN Req-|<--Rtrv Req (ACTION_RTRV_BSN)--|<--Rtrv BSN Req--- <-Rtrv BSN Req-|<--Rtrv Req (ACTION_RTRV_BSN)--|<--Rtrv BSN Req---
-Rtrv BSN Cfm->|---Rtrv Cfm (ACTION_RTRV_BSN)->|---Rtrv BSN Cfm--> -Rtrv BSN Cfm->|---Rtrv Cfm (ACTION_RTRV_BSN)->|---Rtrv BSN Cfm-->
(seq_num = BSN) (seq_num = BSN)
<-Rtrv Msg Req-|<-Rtrv Req (ACTION_RTRV_MSGS)--|<--Rtrv Msg Req--- <-Rtrv Msg Req-|<-Rtrv Req (ACTION_RTRV_MSGS)--|<--Rtrv Msg Req---
(seq_num = FSN) (seq_num = FSN)
-Rtrv Msg Cfm->|--Rtrv Cfm (ACTION_RTRV_MSGS)->|---Rtrv Msg Cfm--> -Rtrv Msg Cfm->|--Rtrv Cfm (ACTION_RTRV_MSGS)->|---Rtrv Msg Cfm-->
(seq_num = -1) (seq_num = -1)
An example of a message flow for a request to drop messages (clear An example of a message flow for a request to drop messages (clear
retransmission buffers) is shown below. retransmission buffers) is shown below.
MTP2 M2UA M2UA MTP3 MTP2 M2UA M2UA MTP3
SGP SGP ASP ASP SGP SGP ASP ASP
-Clr RTB Req----|<-StateReq (STATUS_CLEAR_RTB)--|<--Clr RTB Req----- -Clr RTB Req----|<-StateReq (STATUS_CLEAR_RTB)--|<--Clr RTB Req-----
-Clr RTB Req--->|-StateCfm (STATUS_CLEAR_RTB)-->|---Clr RTB Req----> -Clr RTB Req--->|-StateCfm (STATUS_CLEAR_RTB)-->|---Clr RTB Req---->
5.3.7 Flush and Continue 5.3.7 Flush and Continue
The following message flow shows a request to flush buffers. The following message flow shows a request to flush buffers.
MTP2 M2UA M2UA MTP3 MTP2 M2UA M2UA MTP3
SGP SGP ASP ASP SGP SGP ASP ASP
<--Flush Req----|<-State Req (STATUS_FLUSH_BUFS)--|<---Flush Req-- <--Flush Req----|<-State Req (STATUS_FLUSH_BUFS)--|<---Flush Req--
---Flush Cfm--->|--State Cfm (STATUS_FLUSH_BUFS)->|---Flush Cfm--> ---Flush Cfm--->|--State Cfm (STATUS_FLUSH_BUFS)->|---Flush Cfm-->
The following message flow shows a request to continue.
The following message flow shows a request to continue.
MTP2 M2UA M2UA MTP3 MTP2 M2UA M2UA MTP3
SGP SGP ASP ASP SGP SGP ASP ASP
<---Cont Req----|<--State Req (STATUS_CONTINUE)---|<---Cont Req--- <---Cont Req----|<--State Req (STATUS_CONTINUE)---|<---Cont Req---
----Cont Cfm--->|---State Cfm (STATUS_CONTINUE)-->|----Cont Cfm--> ----Cont Cfm--->|---State Cfm (STATUS_CONTINUE)-->|----Cont Cfm-->
5.3.8 Auditing of SS7 link state 5.3.8 Auditing of SS7 link state
It may be necessary for the ASP to audit the current state of a SS7 link. It may be necessary for the ASP to audit the current state of a SS7
The flows below show an example of the request and all the potential link. The flows below show an example of the request and all the
responses. potential responses.
Below is an example in which the SS7 link is out-of-service. Below is an example in which the SS7 link is out-of-service.
MTP2 M2UA M2UA MGMT MTP2 M2UA M2UA MGMT
SGP SGP ASP ASP SGP SGP ASP ASP
|<----State Req (STATUS_AUDIT)----|<----Audit------- |<----State Req (STATUS_AUDIT)----|<----Audit-------
MTP3 MTP3
ASP ASP
|-----------Release Ind---------->|-Out of Serv Ind-> |-----------Release Ind---------->|-Out of Serv Ind->
MGMT MGMT
ASP ASP
|-----State Cfm (STATUS_AUDIT)--->|----Audit Cfm---> |-----State Cfm (STATUS_AUDIT)--->|----Audit Cfm--->
Below is an example in which the SS7 link is in-service. Below is an example in which the SS7 link is in-service.
MTP2 M2UA M2UA MGMT MTP2 M2UA M2UA MGMT
SGP SGP ASP ASP SGP SGP ASP ASP
|<----State Req (STATUS_AUDIT)----|<----Audit------- |<----State Req (STATUS_AUDIT)----|<----Audit-------
MTP3 MTP3
ASP ASP
|-----------Establish Cfm-------->|---In Serv Ind--> |-----------Establish Cfm-------->|---In Serv Ind-->
MGMT MGMT
ASP ASP
|-----State Cfm (STATUS_AUDIT)--->|----Audit Cfm---> |-----State Cfm (STATUS_AUDIT)--->|----Audit Cfm--->
Below is an example in which the SS7 link is in-service, but congested. Below is an example in which the SS7 link is in-service, but
congested.
MTP2 M2UA M2UA MGMT MTP2 M2UA M2UA MGMT
SGP SGP ASP ASP SGP SGP ASP ASP
|<----State Req (STATUS_AUDIT)----|<----Audit------- |<----State Req (STATUS_AUDIT)----|<----Audit-------
MTP3 MTP3
ASP ASP
|-----------Establish Cfm-------->|---In Serv Ind--> |-----------Establish Cfm-------->|---In Serv Ind-->
|----------Congestion Ind-------->|---Cong Ind-----> |----------Congestion Ind-------->|---Cong Ind----->
MGMT MGMT
ASP ASP
|-----State Cfm (STATUS_AUDIT)--->|----Audit Cfm---> |-----State Cfm (STATUS_AUDIT)--->|----Audit Cfm--->
Below is an example in which the SS7 link is in-service, but in Remote Below is an example in which the SS7 link is in-service, but in
Processor Outage. Remote Processor Outage.
MTP2 M2UA M2UA MGMT MTP2 M2UA M2UA MGMT
SGP SGP ASP ASP SGP SGP ASP ASP
|<----State Req (STATUS_AUDIT)----|<---Audit Req---- |<----State Req (STATUS_AUDIT)----|<---Audit Req----
MTP3 MTP3
ASP ASP
|-----------Establish Ind-------->|---In Serv Ind--> |-----------Establish Ind-------->|---In Serv Ind-->
|---State Ind (EVENT_RPO_ENTER)-->|----RPO Enter---> |---State Ind (EVENT_RPO_ENTER)-->|----RPO Enter--->
MGMT MGMT
ASP ASP
|-----State Cfm (STATUS_AUDIT)--->|----Audit Cfm---> |-----State Cfm (STATUS_AUDIT)--->|----Audit Cfm--->
6.0 Timer Values 6.0 Timer Values
The recommended default values for M2UA timers are: The recommended default values for M2UA timers are:
T(r) 2 seconds T(r) 2 seconds
T(ack) 2 seconds T(ack) 2 seconds
T(beat) Heartbeat Timer 30 seconds T(beat) Heartbeat Timer 30 seconds
7.0 Security Considerations 7.0 Security Considerations
M2UA is designed to carry signalling messages for telephony services. M2UA is designed to carry signalling messages for telephony services.
As such, M2UA MUST involve the security needs of several parties: the As such, M2UA MUST involve the security needs of several parties: the
end users of the services; the network providers and the applications end users of the services; the network providers and the applications
involved. Additional requirements MAY come from local regulation. involved. Additional requirements MAY come from local regulation.
While having some overlapping security needs, any security solution While having some overlapping security needs, any security solution
SHOULD fulfill all of the different parties' needs. SHOULD fulfill all of the different parties' needs.
7.1 Threats 7.1 Threats
There is no quick fix, one-size-fits-all solution for security. As a There is no quick fix, one-size-fits-all solution for security. As a
transport protocol, M2UA has the following security objectives: transport protocol, M2UA has the following security objectives:
* Availability of reliable and timely user data transport. * Availability of reliable and timely user data transport.
* Integrity of user data transport. * Integrity of user data transport.
* Confidentiality of user data. * Confidentiality of user data.
M2UA runs on top of SCTP. SCTP [8] provides certain transport related M2UA runs on top of SCTP. SCTP [8] provides certain transport
security features, such as: related security features, such as:
* Blind Denial of Service Attacks * Blind Denial of Service Attacks
* Flooding * Flooding
* Masquerade * Masquerade
* Improper Monopolization of Services * Improper Monopolization of Services
When M2UA is running in professionally managed corporate or service When M2UA is running in a professionally managed corporate or service
provider network, it is reasonable to expect that this network includes provider network, it is reasonable to expect that this network
an appropriate security policy framework. The "Site Security Handbook" includes an appropriate security policy framework. The "Site
[13] SHOULD be consulted for guidance. Security Handbook" [13] SHOULD be consulted for guidance.
When the network in which M2UA runs in involves more than one party, it When the network in which M2UA runs in involves more than one party,
MAY NOT be reasonable to expect that all parties have implemented it MAY NOT be reasonable to expect that all parties have implemented
security in a sufficient manner. In such a case, it is recommended that security in a sufficient manner. In such a case, it is recommended
IPSEC is used to ensure confidentiality of user payload. Consult [14] that IPSEC is used to ensure confidentiality of user payload.
for more information on configuring IPSEC services. Consult [14] for more information on configuring IPSEC services.
7.2 Protecting Confidentiality 7.2 Protecting Confidentiality
Particularly for mobile users, the requirement for confidentiality MAY Particularly for mobile users, the requirement for confidentiality
include the masking of IP addresses and ports. In this case application MAY include the masking of IP addresses and ports. In this case
level encryption is not sufficient; IPSEC ESP SHOULD be used instead. application level encryption is not sufficient; IPSEC ESP SHOULD be
Regardless of which level performs the encryption, the IPSEC ISAKMP used instead. Regardless of which level performs the encryption, the
service SHOULD be used for key management. IPSEC ISAKMP service SHOULD be used for key management.
8.0 IANA Considerations 8.0 IANA Considerations
8.1 SCTP Payload Protocol Identifier 8.1 SCTP Payload Protocol Identifier
A request will be made to IANA to assign an M2UA value for the Payload A request will be made to IANA to assign an M2UA value for the
Protocol Identifier in SCTP Payload Data chunk. The following SCTP Payload Protocol Identifier in SCTP Payload Data chunk. The
Payload Protocol Identifier has been registered: following SCTP Payload Protocol Identifier has been registered:
M2UA "2" M2UA "2"
The SCTP Payload Protocol Identifier is included in each SCTP Data chunk, The SCTP Payload Protocol Identifier is included in each SCTP Data
to indicate which protocol the SCTP is carrying. This Payload Protocol chunk, to indicate which protocol the SCTP is carrying. This Payload
Identifier is not directly used by SCTP but MAY be used by certain Protocol Identifier is not directly used by SCTP but MAY be used by
network entities to identify the type of information being carried in a certain network entities to identify the type of information being
Data chunk. carried in a Data chunk.
The User Adaptation peer MAY use the Payload Protocol Identifier as a The User Adaptation peer MAY use the Payload Protocol Identifier as a
way of determining additional information about the data being presented way of determining additional information about the data being
to it by SCTP. presented to it by SCTP.
8.2 M2UA Protocol Extensions 8.2 M2UA Protocol Extensions
This protocol may also be extended through IANA in three ways: This protocol may also be extended through IANA in three ways:
-- through definition of additional message classes, -- through definition of additional message classes,
-- through definition of additional message types, and -- through definition of additional message types, and
-- through definition of additional message parameters. -- through definition of additional message parameters.
The definition and use of new message classes, types and parameters is The definition and use of new message classes, types and parameters
an integral part of SIGTRAN adaptation layers. Thus, these extensions is an integral part of SIGTRAN adaptation layers. Thus, these
are assigned by IANA through an IETF Consensus action as defined in extensions are assigned by IANA through an IETF Consensus action as
[RFC2434]. defined in [RFC2434].
The proposed extension must in no way adversely affect the general The proposed extension must in no way adversely affect the general
working of the protocol. working of the protocol.
8.2.1 IETF Defined Message Classes 8.2.1 IETF Defined Message Classes
The documentation for a new message class MUST include the following The documentation for a new message class MUST include the following
information: information:
(a) A long and short name for the message class. (a) A long and short name for the message class.
(b) A detailed description of the purpose of the message class. (b) A detailed description of the purpose of the message class.
8.2.2 IETF Defined Message Types 8.2.2 IETF Defined Message Types
Documentation of the message type MUST contain the following Documentation of the message type MUST contain the following
information: information:
(a) A long and short name for the new message type. (a) A long and short name for the new message type.
(b) A detailed description of the structure of the message. (b) A detailed description of the structure of the message.
(c) A detailed definition and description of intended use of each field (c) A detailed definition and description of intended use of each
within the message. field within the message.
(d) A detailed procedural description of the use of the new message (d) A detailed procedural description of the use of the new message
type within the operation of the protocol. type within the operation of the protocol.
(e) A detailed description of error conditions when receiving this (e) A detailed description of error conditions when receiving this
message type. message type.
When an implementation receives a message type which it does not support, When an implementation receives a message type which it does not
it MUST respond with an Error (ERR) message with an Error Code of support, it MUST respond with an Error (ERR) message with an Error
Unsupported Message Type. Code of Unsupported Message Type.
8.2.3 IETF-defined TLV Parameter Extension 8.2.3 IETF-defined TLV Parameter Extension
Documentation of the message parameter MUST contain the following Documentation of the message parameter MUST contain the following
information: information:
(a) Name of the parameter type. (a) Name of the parameter type.
(b) Detailed description of the structure of the parameter field. This (b) Detailed description of the structure of the parameter field.
structure MUST conform to the general type-length-value format This structure MUST conform to the general type-length-value
described in Section 3.1.5. format described in Section 3.1.5.
(c) Detailed definition of each component of the parameter value. (c) Detailed definition of each component of the parameter value.
(d) Detailed description of the intended use of this parameter type, (d) Detailed description of the intended use of this parameter type,
and an indication of whether and under what circumstances and an indication of whether and under what circumstances
multiple instances of this parameter type may be found within the multiple instances of this parameter type may be found within the
same message type. same message type.
9.0 Acknowledgements 9.0 Acknowledgments
The authors would like to thank John Loughney, Neil Olson, Michael The authors would like to thank Tom George (Alcatel) for contribution
Tuexen, Nikhil Jain, Steve Lorusso, Dan Brendes, Joe Keller, Heinz of text and effort on the specification.
Prantner, Barry Nagelberg, Naoto Makinae, Joyce Archibald, Mark
Kobine, Nitin Tomar, Harsh Bhondwe and Karen King for their valuable The authors would like to thank John Loughney, Neil Olson, Michael
comments and suggestions. Tuexen, Nikhil Jain, Steve Lorusso, Dan Brendes, Joe Keller, Heinz
Prantner, Barry Nagelberg, Naoto Makinae, Joyce Archibald, Mark
Kobine, Nitin Tomar, Harsh Bhondwe and Karen King for their valuable
comments and suggestions.
10.0 References 10.0 References
10.1 Normative 10.1 Normative
[1] ITU-T Recommendation Q.700, 'Introduction To ITU-T Signalling [1] ITU-T Recommendation Q.700, 'Introduction To ITU-T Signalling
System No. 7 (SS7)' System No. 7 (SS7)'
[2] ITU-T Recommendation Q.701-Q.705, 'Signalling System No. 7 (SS7) - [2] ITU-T Recommendation Q.701-Q.705, 'Signalling System No. 7 (SS7)
Message Transfer Part (MTP)' - Message Transfer Part (MTP)'
[3] ANSI T1.111 'Signalling System Number 7 - Message Transfer Part' [3] ANSI T1.111 'Signalling System Number 7 - Message Transfer Part'
[4] Bellcore GR-246-CORE 'Bell Communications Research Specification [4] Bellcore GR-246-CORE 'Bell Communications Research Specification
of Signalling System Number 7', Volume 1, December 1995 of Signalling System Number 7', Volume 1, December 1995
[5] Telecommunication Technology Committee (TTC) Standard JT-Q704, [5] Telecommunication Technology Committee (TTC) Standard JT-Q704,
Message Transfer Part Signaling Network Functions, Message Transfer Part Signaling Network Functions, April 28,
April 28, 1992. 1992.
[6] UTF-8, a transformation format of ISO 10646, RFC 2279, January [6] Yergeau, F., "UTF-8, a transformation format of ISO 10646", RFC
1998 2279, January 1998.
[7] Coded Character Set--7-Bit American Standard Code for [7] Coded Character Set--7-Bit American Standard Code for
Information Interchange, ANSI X3.4-1986. Information Interchange, ANSI X3.4-1986.
10.2 Informative 10.2 Informative
[8] Stream Control Transmission Protocol, RFC 2960, October 2000 [8] Stewart, R., Xie, Q., Morneault, K., Sharp, C., Schwarzbauer,
H., Taylor, T., Rytina, I., Kalla, M., Zhang, L. and V. Paxson,
"Stream Control Transmission Protocol", RFC 2960, October 2000.
[9] Architectural Framework for Signalling Transport, RFC 2719, [9] Ong, L., Rytina, I., Garcia, M., Schwarzbauer, H., Coene, L.,
October 1999 Lin, H., Juhasz, I., Holdrege, M. and C. Sharp, "Architectural
Framework for Signalling Transport", RFC 2719, October 1999.
[10] ITU-T Recommendation Q.2140, 'B-ISDN ATM Adaptation Layer', [10] ITU-T Recommendation Q.2140, 'B-ISDN ATM Adaptation Layer',
February 1995 February 1995
[11] ITU-T Recommendation Q.2210, 'Message transfer part level 3 [11] ITU-T Recommendation Q.2210, 'Message transfer part level 3
functions and messages using the services of ITU-T functions and messages using the services of ITU-T
Recommendation Q.2140', August 1995 Recommendation Q.2140', August 1995
[12] ITU-T Recommendation Q.751.1, 'Network Element Management [12] ITU-T Recommendation Q.751.1, 'Network Element Management
Information Model for the Message Transfer Part', October 1995 Information Model for the Message Transfer Part', October 1995
[13] Site Security Handbook, RFC 2196, September 1997 [13] Fraser, B., "Site Security Handbook", FYI 8, RFC 2196, September
1997.
[14] Security Architecture for the Internet Protocol, RFC 2401 [14] Kent, S. and R. Atkinson, "Security Architecture for the
11.0 Author's Addresses Internet Protocol", RFC 2401, November 1998.
Ken Morneault Tel: +1-703-484-3323 Appendix A: Signalling Network Architecture
Cisco Systems Inc. EMail: kmorneau@cisco.com
13615 Dulles Technology Drive
Herndon, VA. 20171
USA
Ram Dantu, Ph.D. Tel +1-214-291-1111 A Signalling Gateway will support the transport of MTP2-User
NetRake Corporation EMail rdantu@netrake.com signalling traffic received from the SS7 network to one or more
3000 Technology Drive distributed ASPs (e.g., MGCs). Clearly, the M2UA protocol
Plano, TX 75074 description cannot in itself meet any performance and reliability
USA requirements for such transport. A physical network architecture is
required, with data on the availability and transfer performance of
the physical nodes involved in any particular exchange of
information. However, the M2UA protocol is flexible enough to allow
its operation and management in a variety of physical configurations
that will enable Network Operators to meet their performance and
reliability requirements.
Greg Sidebottom EMail: gregside@home.com To meet the stringent SS7 signalling reliability and performance
gregside consulting requirements for carrier grade networks, these Network Operators
Kanata, Ontario should ensure that there is no single point of failure provisioned in
Canada the end-to-end network architecture between an SS7 node and an IP
ASP.
Tom George Tel: +1-972-519-3168 Depending of course on the reliability of the SGP and ASP functional
Alcatel USA EMail: tom.george@usa.alcatel.com elements, this can typically be met by spreading SS7 links in a SS7
1000 Coit Road linkset [1] across SGPs or SGs, the provision of redundant QoS-
Plano, TX 74075 bounded IP network paths for SCTP Associations between SCTP End
USA Points, and redundant Hosts. The distribution of ASPs within the
available Hosts is also important. For a particular Application
Server, the related ASPs MAY be distributed over at least two Hosts.
Brian Bidulock Tel +1-972-839-4489 An example of logical network architecture relevant to carrier-grade
OpenSS7 Project EMail: bidulock@openss7.org operation in the IP network domain is shown in Figure 7 below:
c/o #424, 4701 Preston Park Blvd.
Plano, TX 75093
USA
Jacob Heitz Tek +1-510-747-2917 ************** **************
Lucent Technologies Email: jheitz@lucent.com * ********__*______________________________*__******** * Host1
1701 Harbor Bay Parkway SG1 * * SGP1 *__*________________ _______*__* ASP1 * *
Alameda, CA, 94502 * ******** * | | * ******** *
USA * . * | | * *
Appendix A: Signalling Network Architecture * . * | | **************
************** | |
| |
************** | |
* ********__*______________________|
SG2 * * SGP2 *__*________ |
* ******** * | |
* . * | |
* . * | |
************** | | **************
| |_____________*__******** * Host2
|_____________________*__* ASP2 * *
. * ******** *
. SCTP Associations * *
. **************
.
.
.
A Signalling Gateway will support the transport of MTP2-User signalling Figure 7: Logical Model Example
traffic received from the SS7 network to one or more distributed ASPs
(e.g., MGCs). Clearly, the M2UA protocol description cannot in itself
meet any performance and reliability requirements for such transport.
A physical network architecture is required, with data on the
availability and transfer performance of the physical nodes involved in
any particular exchange of information. However, the M2UA protocol is
flexible enough allow its operation and management in a variety of
physical configurations that will enable Network Operators to meet
their performance and reliability requirements.
To meet the stringent SS7 signalling reliability and performance To avoid a single point of failure, it is recommended that a minimum
requirements for carrier grade networks, these Network Operators should of two ASPs be configured in an AS list, resident in separate hosts
ensure that there is no single point of failure provisioned in the end- and, therefore, available over different SCTP associations. For
to-end network architecture between an SS7 node and an IP ASP. example, in the network shown in Figure 7, all messages for the
Interface Identifiers could be sent to ASP1 in Host1 or ASP2 in
Host2. The AS list at SGP1 might look like the following:
Depending of course on the reliability of the SGP and ASP functional Interface Identifiers - Application Server #1
elements, this can typically be met by the spreading SS7 links in a ASP1/Host1 - State = Active
SS7 linkset [1] across SGPs or SGs, the provision of redundant ASP2/Host2 - State = Inactive
QoS-bounded IP network paths for SCTP Associations between SCTP End
Points, and redundant Hosts. The distribution of ASPs within the
available Hosts is also important. For a particular Application
Server, the related ASPs MAY be distributed over at least two Hosts.
An example logical network architecture relevant to carrier-grade In this 1+1 redundancy case, ASP1 in Host1 would be sent any incoming
operation in the IP network domain is shown in Figure 7 below: message for the Interface Identifiers registered. ASP2 in Host2
would normally be brought to the active state upon failure of
ASP1/Host1. In this example, both ASPs are Inactive or Active,
meaning that the related SCTP association and far-end M2UA peer is
ready.
************** ************** For carrier grade networks, Operators should ensure that under
* ********__*______________________________*__******** * Host1 failure or isolation of a particular ASP, stable calls or
SG1 * * SGP1 *__*________________ _______*__* ASP1 * * transactions are not lost. This implies that ASPs need, in some
* ******** * | | * ******** * cases, to share the call/-transaction state or be able to pass the
* . * | | * * call/transaction state between each other. Also, in the case of ASPs
* . * | | ************** performing call processing, coordination MAY be required with the
************** | | related Media Gateway to transfer the MGC control for a particular
| | trunk termination. However, this sharing or communication is outside
************** | | the scope of this document.
* ********__*______________________|
SG2 * * SGP2 *__*________ |
* ******** * | |
* . * | |
* . * | |
************** | | **************
| |_____________*__******** * Host2
|_____________________*__* ASP2 * *
. * ******** *
. SCTP Associations * *
. **************
.
.
.
Figure 7: Logical Model Example 11.0 Authors' Addresses
To avoid a single point of failure, it is recommended that a minimum Ken Morneault
of two ASPs be configured in an AS list, resident in separate hosts Cisco Systems Inc.
and, therefore, available over different SCTP associations. For 13615 Dulles Technology Drive
example, in the network shown in Figure 7, all messages for the Herndon, VA. 20171
Interface Identifiers could be sent to ASP1 in Host1 or ASP2 in USA
Host2. The AS list at SGP1 might look like the following:
Interface Identifiers - Application Server #1 Phone: +1-703-484-3323
ASP1/Host1 - State = Active EMail: kmorneau@cisco.com
ASP2/Host2 - State = Inactive
In this 1+1 redundancy case, ASP1 in Host1 would be sent any incoming Ram Dantu, Ph.D.
message for the Interface Identifiers registered. ASP2 in Host2 would NetRake Corporation
normally be brought to the active state upon failure of ASP1/Host1. 3000 Technology Drive
In this example, both ASPs are Inactive or Active, meaning that the Plano, TX 75074
related SCTP association and far-end M2UA peer is ready. USA
For carrier grade networks, Operators should ensure that under failure Phone: +1-214-291-1111
or isolation of a particular ASP, stable calls or transactions are not EMail: rdantu@netrake.com
lost. This implies that ASPs need, in some cases, to share the call/-
transaction state or be able to pass the call/transaction state between Greg Sidebottom
each other. Also, in the case of ASPs performing call processing, Signatus Technologies
coordination MAY be required with the related Media Gateway to transfer Kanata, Ontario, Canada
the MGC control for a particular trunk termination. However, this
sharing or communication is outside the scope of this document. EMail: greg@signatustechnologies.com
Brian Bidulock
OpenSS7 Corporation
1469 Jeffreys Crescent
Edmonton, AB T6L 6T1
Canada
Phone: +1-780-490-1141
EMail: bidulock@openss7.org
Jacob Heitz
Lucent Technologies
1701 Harbor Bay Parkway
Alameda, CA, 94502
USA
Phone: +1-510-747-2917
EMail: jheitz@lucent.com
Full Copyright Statement
Copyright (C) The Internet Society (2002). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
 End of changes. 578 change blocks. 
2238 lines changed or deleted 2251 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/