draft-ietf-sigtran-m2ua-09.txt   draft-ietf-sigtran-m2ua-10.txt 
Network Working Group Ken Morneault Network Working Group Ken Morneault
INTERNET-DRAFT Ram Dantu INTERNET-DRAFT Cisco Systems
Cisco Systems Ram Dantu
NetRake
Greg Sidebottom Greg Sidebottom
Nortel Networks Nortel Networks
Tom George Tom George
Alcatel Alcatel
Brian Bidulock Brian Bidulock
OpenSS7 OpenSS7
Jacob Heitz Jacob Heitz
Lucent Lucent
Expires in six months July 2001 Expires in March 2002 Sep 2001
SS7 MTP2-User Adaptation Layer SS7 MTP2-User Adaptation Layer
<draft-ietf-sigtran-m2ua-09.txt> <draft-ietf-sigtran-m2ua-10.txt>
Status of This Memo Status of This Memo
This document is an Internet-Draft and is in full conformance with all This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 of RFC 2026. Internet-Drafts are working provisions of Section 10 of RFC 2026. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, documents of the Internet Engineering Task Force (IETF), its areas,
and its working groups. Note that other groups MAY also distribute and its working groups. Note that other groups MAY also distribute
working documents as Internet-Drafts. working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
skipping to change at page 1, line 47 skipping to change at page 1, line 48
To learn the current status of any Internet-Draft, please check the To learn the current status of any Internet-Draft, please check the
'1id-abstracts.txt' listing contained in the Internet- Drafts Shadow '1id-abstracts.txt' listing contained in the Internet- Drafts Shadow
Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe),
munnari.oz.au (Pacific Rim), ftp.ietf.org (US East Coast), or munnari.oz.au (Pacific Rim), ftp.ietf.org (US East Coast), or
ftp.isi.edu (US West Coast). ftp.isi.edu (US West Coast).
Abstract Abstract
This Internet Draft defines a protocol for backhauling of SS7 MTP2 This Internet Draft defines a protocol for backhauling of SS7 MTP2
User signaling messages over IP using the Stream Control User signalling messages over IP using the Stream Control
Transmission Protocol (SCTP). This protocol would be used between a Transmission Protocol (SCTP). This protocol would be used between a
Signaling Gateway (SG) and Media Gateway Controller (MGC). It is Signalling Gateway (SG) and Media Gateway Controller (MGC). It is
assumed that the SG receives SS7 signaling over a standard SS7 assumed that the SG receives SS7 signalling over a standard SS7
interface using the SS7 Message Transfer Part (MTP) to provide interface using the SS7 Message Transfer Part (MTP) to provide
transport. The Signaling Gateway would act as a Signaling Link transport. The Signalling Gateway would act as a Signalling Link
Terminal. Terminal.
TABLE OF CONTENTS TABLE OF CONTENTS
1. Introduction..............................................2 1. Introduction..............................................3
1.1 Scope..................................................2 1.1 Scope..................................................3
1.2 Terminology............................................3 1.2 Terminology............................................3
1.3 Signaling Transport Architecture.......................3 1.3 Signalling Transport Architecture......................5
1.4 Services Provide by the M2UA Adaptation Layer..........6 1.4 Services Provide by the M2UA Adaptation Layer..........8
1.5 Function Provided by the M2UA Layer....................8 1.5 Function Provided by the M2UA Layer...................10
1.6 Definition of the M2UA Boundaries......................9 1.6 Definition of the M2UA Boundaries.....................12
2. Conventions...............................................9 2. Conventions..............................................15
3. Protocol Elements.........................................9 3. Protocol Elements........................................15
3.1 Common Message Header.................................10 3.1 Common Message Header.................................15
3.2 M2UA Message Header...................................11 3.2 M2UA Message Header...................................19
3.3 M2UA Messages.........................................11 3.3 M2UA Messages.........................................20
4. Procedures...............................................20 4. Procedures...............................................51
4.1 Procedures to Support Service in Section 1.4.1........20 4.1 Procedures to Support the M2UA-User Layer.............52
4.2 Procedures to Support Service in Section 1.4.2........21 4.2 Receipt of Primitives from the Layer Management.......52
4.3 Procedures to Support Service in Section 1.4.3........21 4.3 AS and ASP State Maintenance..........................54
5. Examples of MTP2 User Adaptation (M2UA) Procedures.......26 4.4 Link Key Management Procedures........................65
5.1 Establishment of associations between SG and MGC......26 5. Examples of MTP2 User Adaptation (M2UA) Procedures.......66
5.1 Establishment of associations between SG and MGC......66
examples examples
5.2 MTP Level 2 / MTP Level 3 Boundary Examples...........28 5.2 MTP Level 2 / MTP Level 3 Boundary Examples...........69
5.3 Layer Management Communication Examples...............29 5.3 Layer Management Communication Examples...............69
6. Timers...................................................30 6. Timers...................................................74
7. Security.................................................30 7. Security.................................................74
8. IANA Considerations......................................31 7.1 Threats................................................74
8.1 SCTP Payload Protocol Identifier.......................31 7.2 Protecting Confidentiality.............................75
8.2 IUA Protocol Extensions................................31 8. IANA Considerations......................................75
9. Acknowledgements.........................................31 8.1 SCTP Payload Protocol Identifier.......................75
10. References...............................................32 8.2 IUA Protocol Extensions................................75
11. Author's Addresses.......................................33 9. Acknowledgements.........................................77
10. References...............................................77
11. Author's Addresses.......................................78
1. Introduction 1. Introduction
1.1 Scope 1.1 Scope
There is a need for Switched Circuit Network SCN signaling protocol There is a need for Switched Circuit Network SCN signalling protocol
delivery from an Signaling Gateway (SG) to a Media Gateway delivery from an Signalling Gateway (SG) to a Media Gateway
Controller (MGC) or IP Signaling Point (IPSP). The delivery Controller (MGC). The delivery mechanism addresses the following
mechanism SHOULD meet the following criteria: 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 and
MGC 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 or IPSP. 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 application
instance. An example of an Application Server is a MGC handling the instance. An example of an Application Server is a MGC handling the
MTP Level 3 and call processing for SS7 links terminated by the MTP Level 3 and call processing for SS7 links terminated by the
Signaling Gateways. Practically speaking, an AS is modeled at the SG Signalling Gateways. Practically speaking, an AS is modeled at the SG
as an ordered list of one or more related Application Server Processes as an ordered list of one or more related Application Server Processes
(e.g., primary, secondary, tertiary, ...). (e.g., primary, secondary, tertiary, ...).
Application Server Process (ASP) - A process instance of an Application Application Server Process (ASP) - A process instance of an Application
Server. Examples of Application Server Processes are primary or backup Server. Examples of Application Server Processes are active or standby
MGC instances. 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 signaling 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 MGU)
back to the point of call processing (i.e., the MGCU), if this is not back to the point of call processing (i.e., the MGCU), if this is not
local [4]. local [4].
Fail-over - The capability to re-route signaling 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 Server
in the event of failure or unavailability of a currently used Application in the event of failure or unavailability of a currently used Application
Server Process. Fail-back MAY apply upon the return to service of a Server Process. Fail-back MAY apply upon the return to service of a
previously unavailable Application Server Process. 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
signaling link. signalling link.
Interface Identifier - The Interface Identifier identifies the physical Interface Identifier - The Interface Identifier identifies the physical
interface at the SG for which the signaling messages are sent/received. interface at the SG for which the signalling messages are sent/received.
The format of the Interface Identifier parameter can be text or integer, The format of the Interface Identifier parameter can be text or integer,
the values of which are assigned according to network operator policy. the values of which are assigned according to network operator policy.
The values used are of local significance only, coordinated between the The values used are of local significance only, coordinated between the
SG and ASP. 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 Signaling value that identifies a registration request for a particular
Data Link and Signaling 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 datalink 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. MTP3). (i.e. 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.
Signaling Link Terminal (SLT) - Refers to the means of performing all Signalling Data Link - An SDL refers to a specific communications
facility that connects two Signalling Link Terminals.
Signalling Gateway (SG) - An SG is a signalling agent at the edge of
the IP network. An SG appears to the SS7 as one or more Signalling
Link Terminals that are connected to one or more Signalling Data Links
in the SS7 network. An SG contains a set of one or more unique
Signalling Gateway Processes, on which one or more is normally
actively processing traffic. Where an SG contains more than one SGP,
the SG is a logical entity.
Signalling Gateway Process (SGP) - A process instance that uses M2UA to
communicate to and from a Signalling Link Terminal. It serves as an
active, backup or load-sharing proces of a Signalling Gateway.
Signalling Link Terminal (SLT) - Refers to the means of performing all
of the functions defined at MTP level 2 regardless of their of the functions defined at MTP level 2 regardless of their
implementation [2]. implementation [2].
Stream - A stream refers to an SCTP stream; a uni-directional 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 un-ordered 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 signaling The framework architecture that has been defined for SCN signalling
transport over IP [6] uses two components: a signaling common transport over IP [6] 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 signaling 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 services
of the Stream Control Transmission Protocol [5] as the underlying of the Stream Control Transmission Protocol [5] as the underlying
reliable signaling common transport protocol. reliable signalling common transport protocol.
In a Signaling Gateway, it is expected that the SS7 MTP2-User signaling In a Signalling Gateway, it is expected that the SS7 MTP2-User signalling
is transmitted and received from the PSTN over a standard SS7 network is transmitted and received from the PSTN over a standard SS7 network
interface, using the SS7 Message Transfer Part Level 1 and Level 2 [3,4] interface, using the SS7 Message Transfer Part Level 1 and Level 2 [3,4]
to provide reliable transport of the MTP3-User signaling messages to and to provide reliable transport of the MTP3-User signalling messages to and
from an SS7 Signaling End Point (SEP) or Signaling Transfer Point (STP). from an SS7 Signalling End Point (SEP) or Signalling Transfer Point (STP).
The SG then provides a inter-working of transport functions The SG then provides a interworking of transport functions
with the IP transport, in order to transfer the MTP2-User signaling with the IP transport, in order to transfer the MTP2-User signalling
messages to and from an Application Server Process where the peer MTP2- messages to and from an Application Server Process where the peer MTP2-
User protocol layer exists. User protocol layer exists.
1.3.1 Example - SG to MGC 1.3.1 Example - SG to MGC
In a Signaling Gateway, it is expected that the SS7 signaling 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 Message
Transfer Part (MTP) to provide transport of SS7 signaling messages to Transfer Part (MTP) to provide transport of SS7 signalling messages to
and from an SS7 Signaling End Point (SEP) or SS7 Signaling Transfer and from an SS7 Signalling End Point (SEP) or SS7 Signalling Transfer
Point (STP). In other words, the SG acts as a Signaling Link Terminal Point (STP). In other words, the SG acts as a Signalling Link Terminal
(SLT) [2]. The SG then provides interworking of transport functions (SLT) [2]. The SG then provides interworking of transport functions
with IP Signaling Transport, in order to transport the MTP3 signaling with IP Signalling Transport, in order to transport the MTP3 signalling
messages to the MGC where the peer MTP3 protocol layer exists, as shown messages to the MGC where the peer MTP3 protocol layer exists, as shown
below: below:
****** SS7 ****** IP ******* ****** SS7 ****** IP *******
*SEP *-----------* SG *-------------* MGC * *SEP *-----------* SG *-------------* MGC *
****** ****** ******* ****** ****** *******
+----+ +----+ +----+ +----+
|S7UP| |S7UP| |S7UP| |S7UP|
+----+ +----+ +----+ +----+
skipping to change at page 5, line 23 skipping to change at page 5, line 59
| 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 Signaling Endpoint SEP - SS7 Signalling Endpoint
IP - Internet Protocol IP - Internet Protocol
SCTP - Stream Control Transmission Protocol SCTP - Stream Control Transmission Protocol (Reference [5])
(Refer to Reference [5])
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) as the underlying reliable
common signaling transport protocol. The use of SCTP provides common signalling transport protocol. The use of SCTP provides
the following features: the 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 an option for order-of-arrival delivery of individual with an option for order-of-arrival delivery of individual
user messages, user 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 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 which redundancy is supported below the transport scenarios in which redundancy is supported below the transport
layer. In these cases, the SCTP functions above MAY NOT be a layer. In these cases, the SCTP functions above MAY NOT be a
requirement and TCP can be used as the underlying common requirement and TCP can be used as the underlying common
transport protocol. transport protocol.
1.3.2 Support for the management of SCTP associations between the SG 1.3.2 Support for the management of SCTP associations between the
and ASPs SGPs 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 one(s) of remote ASP(s) are also maintained. The Active ASP(s) are the
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 of
the underlying SCTP associations using the M-SCTP_STATUS request and the underlying SCTP associations using the M-SCTP_STATUS request and
indication primitive. For example, the M2UA MAY inform local management indication primitive. For example, the M2UA MAY inform local management
of the reason for the release of an SCTP association, determined either of the reason for the release of an SCTP association, determined either
locally within the M2UA layer or by a primitive from the SCTP. 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-ASP
STATUS request or M-AS_STATUS request primitives. STATUS request or M-AS_STATUS request primitives.
1.3.3 Signaling Network Architecture 1.3.3 Signalling Network Architecture
A Signaling Gateway will support the transport of MTP2-User signaling A Signalling Gateway will support the transport of MTP2-User signalling
traffic received from the SS7 network to one or more distributed ASPs traffic received from the SS7 network to one or more distributed ASPs
(e.g., MGCs). Clearly, the M2UA protocol description cannot in itself (e.g., MGCs). Clearly, the M2UA protocol description cannot in itself
meet any performance and reliability requirements for such transport. meet any performance and reliability requirements for such transport.
A physical network architecture is required, with data on the A physical network architecture is required, with data on the
availability and transfer performance of the physical nodes involved in availability and transfer performance of the physical nodes involved in
any particular exchange of information. However, the M2UA protocol MUST any particular exchange of information. However, the M2UA protocol MUST
be flexible enough allow its operation and management in a variety of be flexible enough allow its operation and management in a variety of
physical configurations that will enable Network Operators to meet physical configurations that will enable Network Operators to meet
their performance and reliability requirements. their performance and reliability requirements.
To meet the stringent SS7 signaling reliability and performance To meet the stringent SS7 signalling reliability and performance
requirements for carrier grade networks, these Network Operators SHOULD requirements for carrier grade networks, these Network Operators SHOULD
ensure that there is no single point of failure provisioned in the end- ensure that there is no single point of failure provisioned in the end-
to-end network architecture between an SS7 node and an IP ASP. to-end network architecture between an SS7 node and an IP ASP.
Depending of course on the reliability of the SG and ASP functional Depending of course on the reliability of the SGP and ASP functional
elements, this can typically be met by the spreading links in a linkset elements, this can typically be met by the spreading links in a linkset
across SGs, the provision of redundant QoS-bounded IP network paths for across SGPs or SGs, the provision of redundant QoS-bounded IP network
SCTP Associations between SCTP End Points, and redundant Hosts. The paths for SCTP Associations between SCTP End Points, and redundant
distribution of ASPs within the available Hosts is also important. For Hosts. The distribution of ASPs within the available Hosts is also
a particular Application Server, the related ASPs SHOULD be distributed important. For a particular Application Server, the related ASPs MAY
over at least two Hosts. be distributed over at least two Hosts.
An example logical network architecture relevant to carrier-grade An example logical network architecture relevant to carrier-grade
operation in the IP network domain is shown in Figure 2 below: operation in the IP network domain is shown in Figure 2 below:
******** ************** ************** **************
* *_________________________________________* ******** * Host1 * ********__*______________________________*__******** * Host1
* * _________* * ASP1 * * SG1 * * SGP1 *__*________________ _______*__* ASP1 * *
* SG1 * SCTP Associations | * ******** * * ******** * | | * ******** *
* *_______________________ | * * * . * | | * *
******** | | ************** * . * | | **************
************** | |
| | | |
******** | | ************** | |
* *_______________________________| * ********__*______________________|
* * | SG2 * * SGP2 *__*________ |
* SG2 * SCTP Associations | * ******** * | |
* *____________ | * . * | |
* * | | * . * | |
******** | | ************** ************** | | **************
| |_________________* ******** * Host2 | |_____________*__******** * Host2
|____________________________* * ASP2 * * |_____________________*__* ASP2 * *
* ******** * . * ******** *
* * . SCTP Associations * *
************** . **************
. .
. .
. .
Figure 2 - Logical Model Example Figure 2 - Logical Model Example
For carrier grade networks, Operators SHOULD ensure that under failure For carrier grade networks, Operators SHOULD ensure that under failure
or isolation of a particular ASP, stable calls or transactions are not or isolation of a particular ASP, stable calls or transactions are not
lost. This implies that ASPs need, in some cases, to share the call/- 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 transaction state or be able to pass the call/transaction state between
each other. Also, in the case of ASPs performing call processing, each other. Also, in the case of ASPs performing call processing,
coordination MAY be required with the related Media Gateway to transfer coordination MAY be required with the related Media Gateway to transfer
the MGC control for a particular trunk termination. However, this the MGC control for a particular trunk termination. However, this
sharing or communication is outside the scope of this document. sharing or communication is outside the scope of this document.
1.3.4 ASP Fail-over Model and Terminology 1.3.4 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 SG from the SS7 network are assigned MTP2-User messages incoming to a SGP from the SS7 network are assigned
to the unique Application Server, based on the Interface Identifier of to the unique Application Server, based on the Interface Identifier of
the message. the message.
The M2UA layer supports a n+k redundancy model (active-standby, The M2UA layer supports a n+k redundancy model (active-standby,
loadsharing, broadcast) where n ASP is the minimum number of redundant loadsharing, broadcast) where n is the minimum number of redundant
ASPs required to handle traffic and k ASPs are available to take over ASPs required to handle traffic and k ASPs are available to take over
for a failed or unavailable ASP. Note that 1+1 active/standby redundancy for a failed or unavailable ASP. Note that 1+1 active/standby
is a subset of this model. A simplex 1+0 model is also supported as a redundancy is a subset of this model. A simplex 1+0 model is also
subset, with no ASP redundancy. supported as a subset, with no ASP redundancy.
To avoid a single point of failure, it is recommended that a minimum of To avoid a single point of failure, it is recommended that a minimum
two ASPs be configured in an AS list, resident in separate hosts and, oftwo ASPs be configured in an AS list, resident in separate hosts
therefore, available over different SCTP associations. For example, in and, therefore, available over different SCTP associations. For
the network shown in Figure 2, all messages for the Interface Identifiers example, in the network shown in Figure 2, all messages for the
could be sent to ASP1 in Host1 or ASP2 in Host2. The AS list at SG1 Interface Identifiers could be sent to ASP1 in Host1 or ASP2 in
might look like the following: Host2. The AS list at SGP1 might look like the following:
Interface Identiers - Application Server #1 Interface Identifiers - Application Server #1
ASP1/Host1 - State = Active ASP1/Host1 - State = Active
ASP2/Host2 - State = Inactive ASP2/Host2 - State = Inactive
In this 1+1 redundancy case, ASP1 in Host1 would be sent any incoming In this 1+1 redundancy case, ASP1 in Host1 would be sent any incoming
message for the Interface Identifiers registered. ASP2 in Host2 would message for the Interface Identifiers registered. ASP2 in Host2 would
normally be brought to the active state upon failure of ASP1/Host1. normally be brought to the active state upon failure of ASP1/Host1.
In this example, both ASPs are Inactive or Active, meaning that the In this example, both ASPs are Inactive or Active, meaning that the
related SCTP association and far-end M2UA peer is ready. related SCTP association and far-end M2UA peer is ready.
The two ASPs MAY share state information via shared memory, or MAY The two ASPs MAY share state information via shared memory, or MAY
use an ASP to ASP protocol to pass state information. The ASP to ASP use an ASP to ASP protocol to pass state information. The ASP to ASP
protocol is outside the scope of this document. protocol is outside the scope of this document.
1.3.5 Client/Server Model 1.3.5 Client/Server Model
It is recommended that the SG 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 SG to take on the role of server default orientation would be for the SGP to take on the role of server
while the ASP is the client. In this case, ASPs SHOULD initiate the while the ASP is the client. In this case, ASPs SHOULD initiate the
SCTP association to the SG. SCTP association to the SGP.
The SCTP (and UDP/TCP) Registered User Port Number Assignment for M2UA The SCTP (and UDP/TCP) Registered User Port Number Assignment for M2UA
is 2904. is 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 to
provide the equivalent set of services to its users as provided by the provide the equivalent set of services to its users as provided by the
MTP Level 2 to MTP Level 3. MTP Level 2 to MTP Level 3.
skipping to change at page 9, line 41 skipping to change at page 10, line 31
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 a Interface ID to a physical
interface on the Signaling 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/timeslot, E1 line/timeslot, etc. The M2UA layer
MUST also maintain a map of Interface Identifier to SCTP association MUST also maintain a map of Interface Identifier to SCTP association
and to the related stream within the association. and to the related stream within the association.
The SG 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 Interface
Identifier. It MUST be noted, however, that this mapping is dynamic Identifier. It MUST be noted, however, that this mapping is dynamic
and could change at any time due to a change of ASP state. This mapping and could change at any time due to a change of ASP state. This mapping
could even temporarily be invalid, for example during failover of one could even temporarily be invalid, for example during failover of one
ASP to another. Therefore, the SG MUST maintain the states of AS/ASP ASP to another. Therefore, the SGP MUST maintain the states of AS/ASP
and reference them during the routing of an messages to an AS/ASP. and reference them during the routing of an messages to an AS/ASP.
Note that only one SGP SHOULD provide Signalling Link Terminal
services to an SS7 link. Therefore, within an SG, an Application
Server MUST 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 relationship between SS7 link,
Interface Identifier, AS and ASP in the SG is shown below: 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 SG can support more than one AS. An AS can support more than A SGP MAY support more than one AS. An AS MAY support more than
one Interface Identifier. one Interface Identifier.
1.5.2 Status of ASPs 1.5.2 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 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 reception of indications from the local SCTP association. ASP
state transition procedures are described in Section 4.3.1. state transition procedures are described in Section 4.3.1.
At a SG, 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 primary and a back-up ASP are available, M2UA peer protocol is a primary and a backup ASP are available, 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 of ASPs within a logical Application Server is kept updated in list of ASPs within a logical Application Server is kept updated in
the SG to reflect the active Application Server Process. the 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-ASP
STATUS or M-AS_STATUS primitives. STATUS or M-AS_STATUS primitives.
1.5.3 SCTP Specifics 1.5.3 SCTP Specifics
1.5.3.1 SCTP Stream Management 1.5.3.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 the
stream information from its peer M2UA layer. Instead, the Interface stream information from its peer M2UA layer. Instead, the Interface
Identifier is in the M2UA message header. 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 minimize
transmission and buffering delay, therefore improving the overall transmission and buffering delay, therefore improving the overall
performance and reliability of the signaling elements. A separate performance and reliability of the signalling elements. A separate
SCTP stream can be used for each SS7 link. Or, an implementation may SCTP stream can be used for each SS7 link. Or, an implementation may
choose to split the SS7 link across several streams based on SLS. choose to split the SS7 link across several streams based on SLS.
This method may be of particular interest for high speed links (MTP3b) This method may be of particular interest for high speed links (MTP3b)
since high speed links have a 24-bit sequence number and the stream since high speed links have a 24-bit sequence number and the stream
sequence number is 16-bits. 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 onlt 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.4 Seamless SS7 Network Management Interworking 1.5.4 Seamless SS7 Network Management Interworking
The M2UA layer on the SG SHOULD pass an indication of unavailability of The M2UA layer on the SGP SHOULD pass an indication of unavailability
the M2UA-User (MTP3) to the local Layer Management, if the currently of the M2UA-User (MTP3) to the local Layer Management, if the
active ASP moves from the ACTIVE state. The actions taken by M2UA currently active ASP moves from the ACTIVE state. The actions taken by
on the SG with regards to MTP Level 2 should be in accordance with M2UAon the SGP with regards to MTP Level 2 should be in accordance
the appropriate MTP specifications. with the appropriate MTP specifications.
1.5.5 Flow Control / Congestion 1.5.5 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 IP network
congestion onset and abatement by means of an implementation-dependent congestion onset and abatement by means of an implementation dependent
function (i.e. an indication from the SCTP). The handling of function (i.e. an indication from the SCTP). The handling of
this congestion indication by M2UA is implementation dependent. this congestion indication by M2UA is implementation dependent.
However, the actions taken by the SG should be accordance with the
appropriate MTP specification and should enable SS7 functionality
(e.g. flow control) to be correctly maintained.
1.5.6 Audit of Link State 1.5.6 Audit of Link State
After a failover of one ASP to another ASP, it may be necessary for the After a failover of one ASP to another ASP, it may be necessary for the
M2UA on the ASP to audit the current SS7 link state to ensure consistency. M2UA on the ASP to audit the current SS7 link state to ensure consistency.
The M2UA on the SG would respond to the audit request with information The M2UA on the SGP would respond to the audit request with information
regarding the current state of the link (i.e. in-service, out-of-service, regarding the current state of the link (i.e. in-service, out-of-service,
congestion state, LPO/RPO state). 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
skipping to change at page 10, line 34 skipping to change at page 13, line 9
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 [5] Section 9. provided in Reference [5] Section 9.
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 SG. Purpose: LM requests ASP to establish an SCTP association with an
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 SCTP
association with an SG. association with an SGP.
M-SCTP_ESTABLISH indication M-SCTP_ESTABLISH indication
Direction: M2UA -> LM Direction: M2UA -> LM
Purpose: SG 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 SG. Purpose: LM requests ASP to release an SCTP association with SGP.
M-SCTP_RELEASE confirm M-SCTP_RELEASE confirm
Direction: M2UA -> LM Direction: M2UA -> LM
Purpose: ASP confirms to LM that it has released SCTP association Purpose: ASP confirms to LM that it has released SCTP association
with SG. with SGP.
M-SCTP_RELEASE indication M-SCTP_RELEASE indication
Direction: M2UA -> LM Direction: M2UA -> LM
Purpose: SG or IPSP informs LM that ASP has released an SCTP Purpose: SGP informs LM that ASP has released an SCTP association.
association.
M-SCTP_RESTART indication M-SCTP_RESTART indication
Direction: M2UA -> LM Direction: M2UA -> LM
Purpose: SG or IPSP informs LM that a SCTP Restart indication has Purpose: M2UA informs LM that a SCTP Restart indication has
been received been received
M-SCTP_STATUS request M-SCTP_STATUS request
Direction: LM -> M2UA Direction: LM -> M2UA
Purpose: LM requests M2UA to report status of SCTP association. Purpose: LM requests M2UA to report status of SCTP association.
M-SCTP_STATUS indication M-SCTP_STATUS indication
Direction: M2UA -> LM Direction: M2UA -> LM
Purpose: M2UA reports status of SCTP association. Purpose: M2UA reports status of SCTP association.
M-ASP_STATUS request M-ASP_STATUS request
Direction: LM -> M2UA Direction: LM -> M2UA
Purpose: LM requests SG to report status of remote ASP. Purpose: LM requests SGP to report status of remote ASP.
M-ASP_STATUS indication M-ASP_STATUS indication
Direction: M2UA -> LM Direction: M2UA -> LM
Purpose: SG reports status of remote ASP. Purpose: SGP reports status of remote ASP.
M-AS_STATUS request M-AS_STATUS request
Direction: LM -> M2UA Direction: LM -> M2UA
Purpose: LM requests SG to report status of AS. Purpose: LM requests SG to report status of AS.
M-AS_STATUS indication M-AS_STATUS indication
Direction: M2UA -> LM Direction: M2UA -> LM
Purpose: SG reports status of AS. Purpose: SG reports status of AS.
M-NOTIFY indication M-NOTIFY indication
Direction: M2UA -> LM Direction: M2UA -> LM
Purpose: ASP reports that it has received a NOTIFY message Purpose: ASP reports that it has received a NOTIFY message
from its peer. from its peer.
M-ERROR indication M-ERROR indication
Direction: M2UA -> LM Direction: M2UA -> LM
Purpose: ASP or SG 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 SG. 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 Acknowledgement
message from the SG. 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 SG. 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 Acknowledgement
message from the SG. 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 SG. 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 Acknowledgement
message from the SG. 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 SG. 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 Acknowledgement Purpose: ASP reports that is has received an ASP INACTIVE Acknowledgement
message from the SG. message from the SGP.
M-LINK_KEY_REG Request
Direction LM -> M2UA
Purpose LM requests ASP to register Link Key with SG by sending REG REQ
message.
M-LINK_KEY_REG Confirm
Direction M2UA -> LM
Purpose ASP reports to LM that it has successfully received a REG RSP
message from SG.
M-LINK_KEY_REG Indication
Direction M2UA -> LM
Purpose SG reports to LM that it has successfully processed an incoming
REG REQ message from ASP.
M-LINK_KEY_DEREG Request
Direction LM -> M2UA
Purpose LM requests ASP to de-register Link Key with SG by sending DEREG
REQ message.
M-LINK_KEY_DEREG Confirm
Direction M2UA -> LM
Purpose ASP reports to LM that it has successfully received a DEREG RSP
message from SG.
M-LINK_KEY_DEREG Indication
Direction M2UA -> LM
Purpose SG reports to LM that it has successfully processed an incoming
DEREG REQ message from ASP.
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, SHOULD
NOT, RECOMMENDED, NOT RECOMMENDED, MAY, and OPTIONAL, when they appear NOT, RECOMMENDED, NOT RECOMMENDED, MAY, and OPTIONAL, when they appear
in this document, are to be interpreted as described in [RFC2119]. 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 which contains a version, message class, message type, message
length, and message contents. This message header is common among all length, and message contents. This message header is common among all
signaling protocol adaptation layers: 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 3 Common Message Header Figure 3 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 adapation The version field (vers) contains the version of the M2UA adaptation
layer. The supported versions are: layer. The supported versions are:
Value Version Value Version
----- ------- ----- -------
1 Release 1.0 1 Release 1.0
3.1.2 Message Type 3.1.2 Spare
The Spare field is 8-bits. It SHOULD be set to all '0's by the sender
and ignored by the receiver.
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/M2UA/SUA] 0 Management (MGMT) Message [IUA/M2UA/M3UA/SUA]
1 Transfer Messages [M2UA] 1 Transfer Messages [M3UA]
2 SS7 Signalling Network Management (SSNM) Messages [M2UA/SUA] 2 SS7 Signalling Network Management (SSNM) Messages [M3UA/SUA]
3 ASP State Maintenance (ASPSM) Messages [IUA/M2UA/M2UA/SUA] 3 ASP State Maintenance (ASPSM) Messages [IUA/M2UA/M3UA/SUA]
4 ASP Traffic Maintenance (ASPTM) Messages [IUA/M2UA/M2UA/SUA] 4 ASP Traffic Maintenance (ASPTM) Messages [IUA/M2UA/M3UA/SUA]
5 Q.921/Q.931 Boundary Primitives Tranport (QPTM) 5 Q.921/Q.931 Boundary Primitives Transport (QPTM)
Messages [IUA] Messages [IUA]
6 MTP2 User Adaptatation (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 (M2UA) 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
The following list contains the message types for the defined messages. 3.1.4 Message Type
The following List contains the Message Types for the valid Message
Classes:
MTP2 User Adaptatation (MAUP) Messages MTP2 User Adaptatation (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
skipping to change at page 12, line 9 skipping to change at page 17, line 9
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 Reserved 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 Reserved 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)
skipping to change at page 12, line 43 skipping to change at page 17, line 43
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.3 Reserved 3.1.5 Message Length
The Reserved field is 8-bits. It SHOULD be set to all '0's and
ignored by the receiver.
3.1.4 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 includes parameter including the header. The Message Length includes parameter
padding bytes, if any. padding bytes, if any.
3.1.5 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 paramters 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 parameter Tags (used by all takes a value of 0 to 65534. The common parameters used by adaptation
User Adaptation layers) defined are as follows: layers are in the range of 0x00 to 0xff. The M2UA specific parameters
have Tags in the range 0x300 to 0x3ff.
The common parameter Tags (used by all User Adaptation layers) defined
are as follows:
Parameter Value Parameter Name Parameter Value Parameter Name
--------------- -------------- --------------- --------------
0 (0x0) Reserved 0 (0x0) Reserved
1 (0x1) Interface Identifier (Integer) 1 (0x1) Interface Identifier (Integer)
2 (0x2) Interface Identifier (Integer Range) 2 (0x2) Unused
3 (0x3) Interface Identifier (Text) 3 (0x3) Interface Identifier (Text)
4 (0x4) Info String 4 (0x4) Info String
5 (0x5) Unused 5 (0x5) Unused
6 (0x6) Unused 6 (0x6) Unused
7 (0x7) Diagnostic Information 7 (0x7) Diagnostic Information
8 (0x8) Unused 8 (0x8) Interface Identifier (Integer Range)
9 (0x9) Heartbeat Data 9 (0x9) Heartbeat Data
10 (0xa) Reason 10 (0xa) Reason
11 (0xb) Traffic Mode Type 11 (0xb) Traffic Mode Type
12 (0xc) Error Code 12 (0xc) Error Code
13 (0xd) Status Type/Information 13 (0xd) Status Type/Information
14 (0xe) ASP Identifier 14 (0xe) ASP Identifier
15-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 (0x0309) Retrieval Result 776 (0x0308) Retrieval Result
777 (0x030a) Link Key 777 (0x0309) Link Key
778 (0x030b) Local-LK-Identifier 778 (0x030a) Local-LK-Identifier
779 (0x030c) Signaling Data Terminal (SDT) Identifier 779 (0x030b) Signalling Data Terminal (SDT) Identifier
780 (0x030d) Signailng Data Link (SDL) Identifier 780 (0x030c) Signailng Data Link (SDL) Identifier
781 (0x030e) Registration Result 781 (0x030d) Registration Result
782 (0x030f) Registration Status 782 (0x030e) Registration Status
783 (0x0310) De-Registration Result 783 (0x030f) De-Registration Result
784 (0x0311) De-Registration Status 784 (0x0310) De-Registration Status
785 (0x0312) Correlation Id 785 (0x0311) Correlation Id
786 (0x0313) Correlation Id Ack 786 (0x0312) Correlation Id Ack
Parameter Length: 16 bits (unsigned integer) Parameter Length: 16 bits (unsigned integer)
The Parameter Length field contains the size of the parameter in bytes, The Parameter Length field contains the size of the parameter in
including the Parameter Tag, Parameter Length, and Parameter Value bytes, including the Parameter Tag, Parameter Length, and Parameter
fields. The Parameter Length does not include any padding bytes. Value fields. The Parameter Length does not 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 Value The total length of a parameter (including Tag, Parameter Length and
fields) MUST be a multiple of 4 bytes. If the length of the parameter is Value fields) MUST be a multiple of 4 bytes. If the length of the
not a multiple of 4 bytes, the sender pads the Parameter at the end (i.e., parameter is not a multiple of 4 bytes, the sender pads the Parameter
after the Parameter Value field) with all zero bytes. The length of the at the end (i.e., after the Parameter Value field) with all zero
padding is NOT included in the parameter length field. A sender SHOULD bytes. The length of the padding is NOT included in the parameter
NOT pad with more than 3 bytes. The receiver MUST ignore the padding length field. A sender MUST NOT pad with more than 3 bytes. The
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 specific In addition to the common message header, there will be a M2UA
message header. The M2UA specific message header will immediately specific message header. The M2UA specific message header will
follow the common message header, but will only be used with MAUP immediately follow the common message header, but will only be used
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 signaling 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 4 M2UA Message Header (Integer-based Interface Identifier) Figure 4 M2UA Message Header (Integer-based Interface Identifier)
The Tag value for Integer-based Interface Identifier is 0x1. The length The Tag value for Integer-based Interface Identifier is 0x1. The
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 5 M2UA Message Header (Text-based Interface Identifier) Figure 5 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
length is variable. length is variable.
3.3 M2UA Messages 3.3 M2UA Messages
The following section defines the messages and parameter contents. The The following section defines the messages and parameter contents.
M2UA messages will use the common message header (Figure 3) and the The M2UA messages will use the common message header (Figure 3) and
M2UA message header (Figure 4). the M2UA message header (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 The Data message contains an SS7 MTP2-User Protocol Data Unit (PDU).
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 (0x312) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Correlation Id |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x300) | Length | | Tag (0x300) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \ / \
\ Protocol Data / \ Protocol Data /
/ \ / \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x311) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 Signaling Information Octet (SIO). network byte order starting with the Signalling Information Octet (SIO).
The Correlation Id parameter uniquely identifies the MSU carried in the The Correlation Id parameter uniquely identifies the MSU carried in the
Protocol Data within a Routing Context. This Correlation Id parameter Protocol Data within an AS. This Correlation Id parameter is assigned
is assigned by the sending M3UA. by the sending M2UA. The purpose of the Correlation Id is to permit
the newly active ASP to synchronize its processing of the traffic in
each ordered stream with other ASPs in the broadcast group.
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 (0x312) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Correlation Id |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x301) | Length | | Tag (0x301) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \ / \
\ Protocol Data / \ Protocol Data /
/ \ / \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x312) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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. priority.
3.3.3 Data Acknowledge Message 3.3.1.2 Data Acknowledge Message
The Data Acknowlege 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 which the sending M2UA is acknowledging as successfully
processed to the peer M2UA. The Data Acknowlege message contains the processed to the peer M2UA.
following parameter:
Correlation Id Ack Mandatory The Data Acknowledge message contains the following parameter:
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 (0x313 | Length = 8 | | Tag (0x312) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Correlation Id Ack | | Correlation Id |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Correlation Id Ack parameter acknowledges to the perr the receipt The Correlation Id parameter of the Data message and the Data Ack
and processing of the MSU to which the Correlation Id Ack parameter message provide a mechanism, for those SG implementations capable for
corresponds. taking advantage of them, to obtain an acknowledgement that the MSU
has been transferred to the M2UA peer before acknowleding the MSU to
the SS7 peer, removing the risk of losing messages due to association
failure or SCTP congestion.
3.3.1.2 Establish (Request, Confirmation) The Data Ack message MUST be sent if a Correlation Id parameter is
received from the peer. Otherwise the Data Ack message SHOULD NOT be
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
dueto lack of MTP Level 2 acknowledgements of the SS7 peer's MSUs.
3.3.1.3 Establish (Request, Confirmation)
The Establish Request message is used to establish the link or to The Establish Request message is used to establish the 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-service, it will send the Establish Request message. Note that the in-service, it will send the Establish Request message. Note that
gateway MAY already have the SS7 link established at its layer. If so, the SGP MAY already have the SS7 link established at its layer.
upon receipt of an Establish Request, the gateway takes no action except If so, upon receipt of an Establish Request, the SGP takes no action
to send an Establish Confirm. except 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 re-send 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 words,
the MGC MAY continue to request the establishment of the data link the MGC MAY continue to request the establishment of the data link
on periodic basis until the desired state is achieved or take some on periodic basis until the desired state is achieved or take some
other action (notify the Management Layer). other action (notify the Management Layer).
The mode (Normal or Emergency) for bringing the link in service is The mode (Normal or Emergency) for bringing the link in service is
defaulted to Normal. The State Request (described in Section 3.3.1.4 defaulted to Normal. The State Request (described in Section 3.3.1.5
below) can be used to change the mode to Emergency. below) can be used to change the mode to Emergency.
3.3.1.3 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.4 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 Signaling Gateway. The on a particular SS7 link supported by the Signalling Gateway Process.
gateway sends a State Confirm to the MGC if the action has been success- The SGP sends a State Confirm to the MGC if the action has been
fully completed. The State Confirm reflects that state value received successfully completed. The State Confirm reflects that state value
in the State Request message. received in the State Request message.
The State Request message contains the following parameter:
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 | | Tag (0x302) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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
procedure procedure
STATUS_EMER_CLEAR 0x3 Request normal alignment (cancel STATUS_EMER_CLEAR 0x3 Request normal alignment (cancel
emergency) procedure emergency) procedure
STATUS_FLUSH_BUFFERS 0x4 Flush or clear receive, transmit and STATUS_FLUSH_BUFFERS 0x4 Flush or clear receive, transmit
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.5 State Confirm 3.3.1.6 State Confirm
The State Confirm message will be sent by the SG in response to a State The State Confirm message will be sent by the SGP in response to a State
Request from the MGC. The State Confirm reflects that state value Request from the MGC. The State Confirm reflects that state value
received in the State Request message. received in the State Request message.
The State Confirm message contains the following parameter:
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 | | Tag (0x302) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| State | | State |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The valid values for State are shown in the following table. The value 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 of the State field should reflect the value received in the State
message. Request message.
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
procedure procedure
STATUS_EMER_CLEAR 0x3 Request normal alignment (cancel STATUS_EMER_CLEAR 0x3 Request normal alignment (cancel
emergency) procedure emergency) procedure
STATUS_FLUSH_BUFFERS 0x4 Flush or clear receive, transmit and STATUS_FLUSH_BUFFERS 0x4 Flush or clear receive, transmit
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 Indication 3.3.1.7 State Indication
The MTP2 State Indication message can be sent from a gateway to an The MTP2 State Indication message can be sent from a SGP to an ASP to
ASP to indicate a condition on a link. indicate a condition on a link.
The State Indication message contains the following parameter:
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 | | Tag (0x303) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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.7 Congestion Indication 3.3.1.8 Congestion Indication
The Congestion Indication message can be sent from a Signaling Gateway The Congestion Indication message can be sent from a Signalling Gateway
to an ASP to indicate the congestion status and discard status of a link. Process to an ASP to indicate the congestion status and discard status
When the MSU buffer fill increases above an Onset threshold or decreases of a link. When the MSU buffer fill increases above an Onset threshold
below an Abatement threshold or crosses a Discard threshold in either or decreases below an Abatement threshold or crosses a Discard threshold
direction, the SG SHALL send a congestion indication message. in either direction, the SGP SHALL send a congestion indication message.
The SG 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 addition,
the SG SHALL use an implementation dependent algorithm to limit the the SGP SHALL use an implementation dependent algorithm to limit the
frequency of congestion indication messages. frequency of congestion indication messages.
An implementation may optionally send Congestion Indication messages on An implementation may optionally send Congestion Indication messages on
a "high priority" stream in order to potentially reduce delay (Refer to a "high priority" stream in order to potentially reduce delay (Refer to
[12] for more details). [12] for more details).
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)
skipping to change at page 14, line 98 skipping to change at page 25, line 24
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The valid values for Congestion Status and Discard Status are shown in The valid values for Congestion Status and Discard Status are shown in
the following table. 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
LEVEL_4 0x4 Congestion Level 4 - Discarding
For networks that do not support multiple levels of congestion, only the For networks that do not support multiple levels of congestion, only
LEVEL_NONE and LEVEL_3 values will be used. For networks that support theLEVEL_NONE and LEVEL_3 values will be used. For networks that
multiple levels of congestion, it is possible for all values to be used. supportmultiple levels of congestion, it is possible for all values to
Refer to [2] and [9] for more details. be used. Refer to [2], [3] and [9] for more details on the congestion
status of signalling links.
When the SG runs out of buffer space for MSUs received from the MGC, the
SG MAY send a Congestion Indication message with Congestion Status and
Discard Status set to LEVEL_4 and discard MSUs received from the MGC.
3.3.1.8 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. queue.
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)
skipping to change at page 14, line 140 skipping to change at page 26, line 13
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 NOT
be present if the Action field is ACTION_RTRV_BSN, ACTION_DROP_MSGS or be present if the Action field is ACTION_RTRV_BSN. The Sequence Number
ACTION_RTRV_TRANS. The Sequence Number field contains the Forward field contains the Forward Sequence Number (FSN) of the far end if the
Sequnce Number (FSN) of the far end if the Action is ACTION_RTRV_MSGS. Action is ACTION_RTRV_MSGS.
3.3.1.9 Retrieval Confirm 3.3.1.10 Retrieval Confirm
The MTP2 Retrieval Confirm message is sent by the Signaling Gateway The MTP2 Retrieval Confirm message is sent by the Signalling Gateway
in response to a Retrieval Request message. in response to a Retrieval Request message.
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 | | Tag (0x306) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Action | | Action |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x308) | Length | | Tag (0x308) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Result | | Result |
skipping to change at page 15, line 28 skipping to change at page 26, line 52
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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: in the following table.
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 Signaling Gateway sends a Retrieval Confirm to a Retrieval When the Signalling Gateway Process sends a Retrieval Confirm to a
Request, it echos the Action field. If the Action was ACTION_RTRV_BSN Retrieval Request, it echos the Action field. If the Action was
and the SG successfully retrieved the BSN, the SG will put the Backward ACTION_RTRV_BSN and the SGP successfully retrieved the BSN, the SGP
Sequence Number (BSN) in the Sequence Number field and will indicate a will put the Backward Sequence Number (BSN) in the Sequence Number
success in the Result field. If the BSN could not be retrieved, the field and will indicate a success in the Result field. If the BSN
Sequence Number field will not be included and the Result field will could not be retrieved, the Sequence Number field will not be included
indicate failure. and the Result field will indicate failure.
For a Retrieval Confirm with Action of ACTION_RTRV_MSGS and
ACTION_RTRV_TRANS, the value of of Result field will indicate success or
failure. A failure means that the buffers could not be retrieved. The
Sequence Number field is not used with ACTION_RTRV_MSGS.
For a Retrieval Confirm with an Action of ACTION_DROP_MSGS, the Result For a Retrieval Confirm with Action of ACTION_RTRV_MSGS, the value of
value will indicate success or failure. The Sequence Number field is the Result field will indicate success or failure. A failure means
not used with ACTION_DROP_MSGS. that the buffers could not be retrieved. The Sequence Number field is
not used with ACTION_RTRV_MSGS.
3.3.1.10 Retrieval Indication 3.3.1.11 Retrieval Indication
The Retrieval Indication message is sent by the Signaling Gateway with a The Retrieval Indication message is sent by the Signalling Gateway with
PDU from the transmit or retransmit queue. The Retrieval Indication a PDU from the transmit or retransmit queue. The Retrieval Indication
message does not contain the Action or seq_num fields, just a MTP3 message does not contain the Action or seq_num fields, just a MTP3
Protocol Data Unit (PDU) from the transmit or retransmit queue. Protocol Data Unit (PDU) from the transmit or retransmit queue.
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
| PDU | \ 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 indicate
a TTC PDU which starts at LI. 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 PDU | \ 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.11 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 that the MTP2 Retrieval Indication message except that it also indicates
it contains the last PDU from the transmit or retransmit queue. that retrieval is complete. In addition, it MAY contain a PDU (which
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
identify the ASP by pre-configured address/port number
information (e.g., where an ASP is resident on a Host using
dynamic address/port number assignment).
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 (0xe) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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
SG 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 8-bit ASCII The optional INFO String parameter can carry any meaningful 8-bit ASCII
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 characters. No procedures are presently parameter is from 0 to 255 characters. 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 received The ASP Up Ack message is used to acknowledge an ASP Up message
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:
ASP Identifier (optional)
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 (0xe) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ASP Identifier* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length | | Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
| INFO String* | \ INFO String* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
If the ASPUP message contains an ASP Identifer, the ASPUP Ack will
reflect the ASP Identifier back to the ASP.
The format and description of the optional Info String parameter is the 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). 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 peer
that the adaptation layer is not ready to receive traffic or 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
Reason
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 (0xa) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reason |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 the
same as for the ASP Up message (See Section 3.3.2.1). same as for the ASP Up message (See Section 3.3.2.1).
The Reason parameter indicates the reason that the remote M2UA
adaptation layer is unavailable. The valid values for Reason are shown
in the following table:
Value Description
0x1 Management
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:
Reason
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 (0xa) | Length | | Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reason | / \
\ INFO String* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length |
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.5 Heartbeat (BEAT)
The Heartbeat message is optionally used to ensure that the M2UA
peers are still available to each other.
The BEAT message contains the following parameter:
Heartbeat Data Optional
The format for the BEAT message is as follows:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0009 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Heartbeat Data /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| INFO String* | The sending node defines the Heartbeat Data field contents. It may
include a Heartbeat Sequence Number and/or Timestamp, or other
implementation specific details.
The receiver of a Heartbeat message does not process this field as
it is only of significance to the sender. The receiver echoes the
content of the Heartbeat Data in a BEAT ACK message.
3.3.2.6 Heartbeat Ack (BEAT ACK)
The Heartbeat ACK message is sent in response to a BEAT message. A
peer MUST send a BEAT ACK in response to a BEAT message. It includes
all the parameters of the received Heartbeat message, without any
change.
The BEAT ACK message contains the following parameter:
Heartbeat Data Optional
The format for the BEAT ACK message is as follows:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0009 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ Heartbeat Data /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format and description of the optional Info String parameter is the The sending node defines the Heartbeat Data field contents. It may
same as for the ASP UP message (See Section 3.3.2.1). include a Heartbeat Sequence Number and/or Timestamp, or other
implementation specific details.
The format of the Reason parameter is the same as for the ASP Down message The receiver of a Heartbeat message does not process this field as
(See Section 3.3.2.3). it is only of significance to the sender. The receiver echoes the
content of the Heartbeat Data in a BEAT ACK message.
3.3.2.5 ASP Active (ASPAC) 3.3.2.7 ASP Active (ASPAC)
The ASPAC message is sent by an ASP to indicate to an SG 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 (mandatory) Traffic Mode Type (mandatory)
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Start1* | | Interface Identifier Start1* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Stop1* | | Interface Identifier Stop1* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Start2* | | Interface Identifier Start2* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Stop2* | | Interface Identifier Stop2* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. . . .
. . . .
. . . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier StartN* | | Interface Identifier StartN* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier StopN* | | Interface Identifier StopN* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
| 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
| Interface Identifier* | \ Interface Identifier* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
| Additional Interface Identifiers | \ Additional Interface Identifiers /
| 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 Over-ride 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 Over-ride value indicates that the ASP is operating in Over-ride The Override value indicates that the ASP is operating in Override
mode, where the ASP takes over all traffic in an Application Server mode, where the ASP takes over all traffic in an Application Server
(i.e., primary/back-up operation), over-riding any currently active (i.e., primary/backup operation), over-riding any currently active
ASPs in the AS. In Load-share mode, the ASP will share in the traffic ASPs in the AS. In Load-share mode, the ASP will share in the traffic
distribution with any other currently active ASPs. In Broadcast mode, distribution with any other currently active ASPs. In Broadcast mode,
all of the Active ASPs receive all message traffic in the Application all of the Active ASPs receive all message traffic in the Application
Server. 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 is provisioned. If only a subset of Interface Identifiers are ASP is provisioned. If only a subset of Interface Identifiers for an
included, the ASP is noted as Active for all the Interface Identifiers AS are included, the ASP is noted as Active for all the Interface
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 the
text formatted Interface Identifier MAY be supported. text formatted Interface Identifier MAY be supported.
An SG that receives an ASPAC with an incorrect or unsupported Traffic An SGP that receives an ASPAC with an incorrect or unsupported Traffic
Mode Type for a particular Interface Identifier will respond with an Mode Type for a particular Interface Identifier will respond with an
Error Message (Cause: Unsupported Traffic Handling Mode). 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 the
same as for the ASP UP message (See Section 3.3.2.1). same as for the ASP UP message (See Section 3.3.2.1).
3.3.2.6 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 Active
message received from a remote M2UA peer. 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 (mandatory) Traffic Mode Type (mandatory)
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)
skipping to change at page 19, line ? skipping to change at page 35, line 14
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 (0x1=integer) | Length | | Tag (0x1=integer) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
| Interface Identifiers* | \ Interface Identifiers* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x8=integer range) | Length | | Tag (0x8=integer range) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Start1* | | Interface Identifier Start1* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Stop1* | | Interface Identifier Stop1* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Start2* | | Interface Identifier Start2* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Stop2* | | Interface Identifier Stop2* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. . . .
. . . .
. . . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier StartN* | | Interface Identifier StartN* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier StopN* | | Interface Identifier StopN* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
| 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 (string) The format for the ASP Active Ack 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
| Interface Identifier* | \ Interface Identifier* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
| Additional Interface Identifiers | \ Additional Interface Identifiers /
| 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 the
same as for the ASP UP message (See Section 3.3.2.1.) same as for the ASP Up message (See Section 3.3.2.1).
The format of the Type and Interface Identifier parameters is the same The format of the Type and Interface Identifier parameters 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.5).
3.3.2.7 ASP Inactive (ASPIA) 3.3.2.9 ASP Inactive (ASPIA)
The ASP Inactive (ASPIA) message is sent by an ASP to indicate to an SG The ASP Inactive (ASPIA) message is sent by an ASP to indicate to an
that it is no longer an active ASP to be used from within a list of ASPs. SGP that it is no longer an active ASP to be used from within a list
The SG will respond with an ASPIA Ack message and either discard incoming of ASPs. The SGP will respond with an ASPIA Ack message and either
messages or buffer for a timed period and then discard. discard incoming messages or buffer for a timed period and then
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* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x8=integer range) | Length | | Tag (0x8=integer range) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Start1* | | Interface Identifier Start1* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Stop1* | | Interface Identifier Stop1* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Start2* | | Interface Identifier Start2* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Stop2* | | Interface Identifier Stop2* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. . . .
. . . .
. . . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier StartN* | | Interface Identifier StartN* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier StopN* | | Interface Identifier StopN* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
| 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* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
| Additional Interface Identifiers | \ Additional Interface Identifiers /
| 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 and description of the optional Interface Identifiers and
Info String parameters is the same as for the ASP Active message (See Info String parameters is the same as for the ASP Active message (See
Section 3.3.2.3). Section 3.3.2.3).
The optional Interface Identifiers parameter contains a list of The optional Interface Identifiers parameter contains a list of
Interface Identifier integers indexing the Application Server traffic Interface Identifier integers indexing the Application Server traffic
that the sending ASP is configured/registered to receive, but does not that the sending ASP is configured/registered to receive, but does not
want to receive at this time. want to receive at this time.
3.3.2.8 ASP Inactive Ack 3.3.2.10 ASP Inactive Ack
The ASP Inactive (ASPIA) Ack message is used to acknowledge an ASP Inactive The ASP Inactive (ASPIA) Ack message is used to acknowledge an ASP
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* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x8=integer range) | Length | | Tag (0x8=integer range) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Start1* | | Interface Identifier Start1* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Stop1* | | Interface Identifier Stop1* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Start2* | | Interface Identifier Start2* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Stop2* | | Interface Identifier Stop2* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. . . .
. . . .
. . . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier StartN* | | Interface Identifier StartN* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier StopN* | | Interface Identifier StopN* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
| 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* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
| Additional Interface Identifiers | \ Additional Interface Identifiers /
| 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 The format of the Interface Identifier parameter is the same as for
ASP Inactive message (See Section 3.3.2.7). the ASP Inactive 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 might
be invalid. be invalid.
The ERR message contains the following parameters: The ERR message contains the following parameters:
Error Code (mandatory) Error Code (mandatory)
Interface Identifier (optional)
Diagnostic Information (optional) Diagnostic Information (optional)
The format for the ERR message is as follows: 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Error Code | | Error Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x1, 0x3, or 0x8) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
\ 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
Invalid Parameter Value 0xa Invalid Parameter Value 0xa
Refused - Management Blocking 0xb Refused - Management Blocking 0xb
Error - ASP Currently Active for 0xc
Interface Identifier
Reserved 0xd
Error - ASP Identifier Required 0xe
Error - Invalid ASP Identifier 0xf
Refused - ASP Identifier Required 0x10
The "Invalid Version" error would be sent if a message was The "Invalid Version" error would be sent if a message was
received with an invalid or unsupported version. The Error message received with an invalid or unsupported version. The Error message
would contain the supported version in the Common header. The would contain the supported version in the Common header. The
Error message could optionally provide the supported version in Error message could optionally provide the supported version in
the Diagnostic Information area. the Diagnostic Information area.
The "Invalid Interface Identifier" error would be sent by a SG if The "Invalid Interface Identifier" error would be sent by a SGP if
an ASP sends a message with an invalid (unconfigured) Interface an ASP sends a message (i.e. an ASP Active message) with an invalid
Identifier value. (unconfigured) Interface Identifier value. One of the optional
Interface Identifier parameters (Integer-based, text-based or integer
range) MUST be used with this error code to identify the invalid
Interface Identifier(s).
The "Unsupported Traffic Handling Mode" error would be sent by a SG 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 SG did not support Mode. An example would be a case in which the SGP did not support
load-sharing. load-sharing. One of the optional Interface Identifier parameters
(Integer-based, text-based or integer range) MAY be used with this
error code to identify the Interface Identifier(s).
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 SG 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 received on an unexpected SCTP stream (i.e. a MGMT message was received on an unexpected SCTP stream (i.e. a MGMT message
was received on a stream other than "0"). was 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 SG if an ASP sends a Text formatted Interface Identifier and the a SGP if an ASP sends a Text formatted Interface Identifier and the
SG only supports Integer formatted Interface Identifiers. When SGP only supports Integer formatted Interface Identifiers. When
the ASP receives this error, it will need to resend its message with the ASP receives this error, it will need to resend its message with
an Integer formatted Interface Identifier. an 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 "Unsupported Interface Identifier Type" error would be sent by
a SG if an ASP sends a Text formatted Interface Identifier and the
SG only supports Integer formatted Interface Identifiers. When
the ASP receives this error, it will need to resend its message with
an Integer formatted Interface Identifier.
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. with an invalid parameter value.
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 optional Diagnostic information can be any information germain to The "Error - ASP Currently Active for Interface Identifier(s)" error is
sent by a SGP when a Deregistration request is received from an ASP
that is active for Interface Identifier(s) specified in the
Deregistration request. One of the optional Interface Identifier
parameters (Integer-based, text-based or integer range) MAY be used
with this error code to identify the Interface Identifier(s).
The "Error - ASP Identifier Required" is sent by a SGP in response
to an ASPUP message which does not contain an ASP Identifier
parameter when the SGP requires one. The ASP should resend the
ASPUP message with a ASP Identifier.
The "Error - Invalid ASP Identifier" is send by a SGP in response
to an ASPUP message with an invalid (i.e. non-unique) ASP Identifier.
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 identification of the error condition.
In the case of an Invalid Version Error Code the Diagnostic information In the case of an Invalid Version Error Code the Diagnostic information
includes the supported Version parameter. In the other cases, the includes the supported Version parameter. In the other cases, the
Diagnostic information MAY be the first 40 bytes of the offending message. Diagnostic information MAY be the first 40 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 M2UA
events to an M2UA peer. 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)
skipping to change at page 20, line 34 skipping to change at page 42, line 34
| Tag (0xd) | Length | | Tag (0xd) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Status Type | Status Information | | Status Type | Status Information |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0xe) | Length | | Tag (0xe) | 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Start1* | | Interface Identifier Start1* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Stop1* | | Interface Identifier Stop1* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Start2* | | Interface Identifier Start2* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Stop2* | | Interface Identifier Stop2* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. . . .
. . . .
. . . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier StartN* | | Interface Identifier StartN* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier StopN* | | Interface Identifier StopN* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
| 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Status Type | Status Information | | Status Type | Status Information |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0xe) | Length | | Tag (0xe) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ASP Identifier* | | ASP Identifier* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x3=string) | Length | | Tag (0x3=string) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
| Interface Identifier* | \ Interface Identifier* /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
| Additional Interface Identifiers | \ Additional Interface Identifiers /
| 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 for The Status Information parameter contains more detailed information
the notification, based on the value of the Status Type. If the Status for the notification, based on the value of the Status Type. If the
Type is AS_State_Change the following Status Information values are used: Status Type is AS_State_Change the following Status Information values
are used:
Value Description Value Description
1 Application Server Down (AS_Down) 1 Application Server Down (AS_Down)
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 SG to an ASP upon a change in status These notifications are sent from an SGP to an ASP upon a change in
of a particular Application Server. The value reflects the new state of status of a particular Application Server. The value reflects the
the Application Server. The Interface Identifiers of the AS MAY be new state of the Application Server. The Interface Identifiers of
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 values If the Status Type is Other, then the following Status Information
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 Insufficent ASP Resources case, the SG 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 to
handle the load of the AS (Load-sharing mode). For the Alternate ASP handle the load of the AS (Load-sharing mode). For the Alternate ASP
Active case, the formerly Active ASP is informed when an alternate Active case, the formerly Active ASP is informed when an alternate
ASP transitions to the ASP Active state in Over-ride mode. The ASP ASP transitions to the ASP Active state in Override mode. The ASP
ID (if available) of the Alternate ASP MUST be placed in the message. Identifier (if available) of the Alternate ASP MUST be placed in the
For the ASP Failure case, the SG is indicating to ASP(s) in the AS message. For the ASP Failure case, the SGP is indicating to ASP(s)
that one of the ASPs has failed (i.e. the ASP Transition to Down due in the AS that one of the ASPs has transitioned to ASP-DOWN. The ASP
to SCTP Communication Down Indication). The ASP ID (if available) of Identifier (if available) of the failed ASP MUST be placed in the
the failed ASP MUST be placed in the message. 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 and description of the optional Interface Identifiers and
Info String parameters is the same as for the ASP Active message Info String parameters is the same as for the ASP Active message
(See Section 3.3.2.3). (See Section 3.3.2.3).
3.3.4 Interface Identifier Management (IIM) Messages 3.3.4 Interface Identifier Management (IIM) Messages
The Interface Identifier Managmement messages are optional. They are The Interface Identifier Management messages are optional. They are
used to support automatic allocation of Signaling Terminals or used to support automatic allocation of Signalling Terminals or
Signaling 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 expectes 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 = 0x030a | Length | | Tag = 0x0309 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ Link Key 1 / / Link Key 1 /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ ... / / ... /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x030a | 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 the receiver of this message will create a Link Key entry
skipping to change at page 21, line 71 skipping to change at page 45, line 50
| 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 SG) 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 = 0x030b | 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. The Signalling Data Terminal Identifier parameter is mandatory.
It identifies the Signalling Data Terminal associated with the It identifies the Signalling Data Terminal associated with 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 = 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 supported by the MTP Level 3 at the ASP. Insignificant SDTI is supported by the MTP Level 3 at the ASP. Insignificant SDTI
bits are coded 0. 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 Siganlling Data Link Identifier associated with identifies the Signalling Data Link Identifier associated with
the SS7 link for which the ASP is registering. The format is as the 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 = 0x030d | 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)
skipping to change at page 21, line 144 skipping to change at page 48, line ?
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 = 0x030e | Length | | Tag = 0x030d | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ Registration Result 1 / / Registration Result 1 /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ ... / / ... /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x030e | 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
skipping to change at page 21, line 208 skipping to change at page 49, line 27
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 = 0x030f | 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 is set to "0" if the registration was not successful. The It is set to "0" if the registration was not successful. The
format of integer-based and text-based Interface Identifier format of integer-based and text-based Interface Identifier
skipping to change at page 21, line 241 skipping to change at page 50, line 11
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 Identifer 1 / / Interface Identifier 1 /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ ... / / ... /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 SG but now wishes to currently registered to receive from the SGP but now wishes to
deregister. 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 = 0x0310 | Length | | Tag = 0x030f | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ De-Registration Result 1 / / De-Registration Result 1 /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ ... / / ... /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0310 | 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 results,
each containing the de-registration status for a single Interface each containing the de-registration status for a single Interface
Identifier in the DEREG REQ message. The number of results in a Identifier in the DEREG REQ message. The number of results in a
single DEREG RSP message MAY match the number of Interface Identifer single DEREG RSP message MAY match the number of Interface Identifier
parameters found in the corresponding DEREG REQ message. The format parameters found in the corresponding DEREG REQ message. The format
of each result is as follows: 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 deregister, 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:
skipping to change at page 21, line 336 skipping to change at page 51, line 47
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 = 0x0311 | 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 from
other layers as well as messages it receives from the peer-to-peer other layers as well as messages it receives from the peer-to-peer
messages. This section describes various procedures involved in messages. This section describes various procedures involved in
response to these events. response to these events.
4.1 Procedures to Support Service in Section 1.4.1 4.1 Procedures to Support the M2UA-User Layer
These procedures achieve the M2UA layer's "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 will On receiving a primitive from the local upper layer, the M2UA layer
send the corresponding MAUP message (see Section 3) to its peer. The will send the corresponding MAUP message (see Section 3) to its peer.
M2UA layer MUST fill in various fields of the common and specific headers The M2UA layer MUST fill in various fields of the common and specific
correctly. In addition the message SHOULD to be sent on the SCTP stream headers correctly. In addition the message SHOULD be sent on the SCTP
that corresponds to the SS7 link. 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 an
SG or MGC needs to invoke the corresponding layer primitives to the SG or MGC needs to invoke the corresponding layer primitives to the
local MTP Level 2 or MTP Level 3 layer. local MTP Level 2 or MTP Level 3 layer.
4.2 Procedures to Support Service in Section 1.4.2 4.2 Receipt of Primitives from the Layer Management
These procedures achieve the M2UA layer's "Support for Communication
between Layer Managements" service.
4.2.1 Layer Management Primitives Procedure
On receiving primitives from the local Layer Management, the M2UA layer On receiving primitives from the local Layer Management, the M2UA layer
will take the requested action and provide an appropriate response will take the requested action and provide an appropriate response
primitive to Layer Management. 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
or IPSP will initiate the establishment of an SCTP association. The will initiate the establishment of an SCTP association. The M2UA
M2UA layer will attempt to establish an SCTP association with the layer will attempt to establish an SCTP association with the remote
remote M2UA peer by sending an SCTP-ASSOCIATE primitive to the local M2UA peer by sending an SCTP-ASSOCIATE primitive to the local SCTP
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 local
M2UA layer. At the SGP or IPSP that initiated the request, the M2UA M2UA layer. At the SGP that initiated the request, the M2UA layer will
layer will send an M-SCTP_ESTABLISH confirm primitive to Layer send an M-SCTP_ESTABLISH confirm primitive to Layer Management when
Management when the association set-up is complete. At the peer M2UA the association setup is complete. At the peer M2UA layer, an
layer, an M-SCTP_ESTABLISH indication primitive is sent to Layer M-SCTP_ESTABLISH indication primitive is sent to Layer Management
Management upon successful completion of an incoming SCTP association upon successful completion of an incoming SCTP association setup.
set-up.
An M-SCTP_RELEASE request primitive from Layer Management initates the An M-SCTP_RELEASE request primitive from Layer Management initates the
tear-down of an SCTP association. The M2UA layer accomplishes a 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 that
initiated the request, the M2UA layer will send an M-SCTP_RELEASE initiated the request, the M2UA layer will send an M-SCTP_RELEASE
confirm primitive to Layer Management when the association teardown is confirm primitive to Layer Management when the association shutdown is
complete. At the peer M2UA Layer, an M-SCTP_RELEASE indication complete. At the peer M2UA Layer, an M-SCTP_RELEASE indication
primitive is sent to Layer Management upon successful tear-down of an primitive is sent to Layer Management upon abort or successful
SCTP association. shutdown of an SCTP association.
An M-SCTP_STATUS request primitive supports a Layer Management query of An M-SCTP_STATUS request primitive supports a Layer Management query
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.
M-NOTIFY indication and M-ERROR indication indicate to Layer Similar LM-to-M2UA-to-SCTP and/or SCTP-to-M2UA-to-LM primitive mappings
can be described for the various other SCTP Upper Layer primitives in
RFC2960 [13] such as INITIALIZE, SET PRIMARY, CHANGE HEARTBEAT,
REQUEST HEARTBEAT, GET SRTT REPORT, SET FAILURE THRESHOLD, SET PROTOCOL
PARAMETERS, DESTROY SCTP INSTANCE, SEND FAILURE, AND NETWORK STATUS
CHANGE. Alternatively, these SCTP Upper Layer primitives (and Status
as well) can be considered for modeling purposes as a Layer Management
interaction directly with the SCTP Layer.
M-NOTIFY indication and M-ERROR indication primitives indicate to Layer
Management the notification or error information contained in a 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 indications
can also be generated based on local M2UA events. 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 of
the status of a particular local or remote ASP. The M2UA layer 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 M2UA
peer protocol is invoked. 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 status
of a particular AS. The M2UA responds with an M-AS_STATUS confirm of a particular AS. The M2UA responds with an M-AS_STATUS confirm
primitive. No M2UA peer protocol is invoked. 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-ASP_
INACTIVE request primitives allow Layer Management at an ASP to 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 peer
at an SGP or IPSP. at an SGP.
All MGMT messages are sent on a sequenced stream to ensure ordering.
SCTP stream '0' SHOULD be used.
4.2.2 MGMT message procedures 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 Down, ASP Active and ASP Inactive messages from a peer M2UA, the ASP Down, ASP Active and ASP Inactive messages from a peer M2UA, the
M2UA layer SHOULD invoke corresponding M-ASP_UP, M-ASP_DOWN, M- M2UA layer SHOULD invoke corresponding M-ASP_UP, M-ASP_DOWN, M-
ASP_ACTIVE and M-ASP_INACTIVE, M-AS_ACTIVE, M-AS_INACTIVE, and M- ASP_ACTIVE and M-ASP_INACTIVE, M-AS_ACTIVE, M-AS_INACTIVE, and M-
AS_DOWN indication primitives to the local Layer Management. AS_DOWN indication primitives to the local Layer Management.
M-NOTIFY indication and M-ERROR indication indicate to Layer Management M-NOTIFY indication and M-ERROR indication primitives indicate to Layer
the notification or error information contained in a received M2UA Management the notification or error information contained in a
Notify or Error message. These indications can also be generated received M2UA Notify or Error message. These indications can also be
based on local M2UA events. generated based on local M2UA events.
All MGMT messages are sent on a sequenced stream to ensure ordering.
SCTP stream '0' SHOULD be used.
4.3 Procedures to Support Service in Section 1.4.3
These procedures achieve the M2UA layer's "Support for management of All MGMT messages, except BEAT and BEAT Ack, SHOULD be sent with
active associations between SG and MGC" service. sequenced delivery to ensure ordering. All MGMT messages, with the
exception of ASPTM, BEAT and BEAT Ack messages, SHOULD be sent on SCTP
stream '0'. All ASPTM messages SHOULD be sent on the stream which
normally carries the data traffic to which the message applies. BEAT
and BEAT Ack messages MAY be sent using out-of-order delivery, and
MAY be sent on any stream.
4.3.1 AS and ASP State Maintenance 4.3 AS and ASP State Maintenance
The M2UA layer on the SG maintains the state of each ASP, in each The M2UA layer on the SGP maintains the state of each remote ASP, in
Appliction Server that is configured to receive traffic. each Application Server that the ASP is configured to receive traffic,
as input to the M2UA message distribution function.
4.3.1.1 ASP States 4.3.1 ASP States
The state of the each ASP, in each AS that it is configured, is The state of each remote ASP, in each AS that it is configured to
maintained in the M2UA layer on the SG. The state of an ASP changes operate, is maintained in the M2UA layer in the SGP. The state of a
due to events. The events include particular ASP in a particular AS changes due to events. The events
include:
* Reception of messages from peer M2UA layer at that ASP * Reception of messages from the peer M2UA layer at the ASP;
* Reception of some messages from the peer M2UA layer at other * Reception of some messages from the peer M2UA layer at other ASPs
ASPs in the AS in the AS (e.g., ASP Active message indicating "Override");
* Reception of indications from SCTP layer * Reception of indications from the SCTP layer; or
* Local Management intervention.
The ASP state transition diagram is shown in Figure 6. The possible The ASP state transition diagram is shown in Figure 6. The possible
states of an ASP are the following: states of an ASP are:
ASP Down: Application Server Process is unavailable and/or the related ASP-DOWN: The remote M2UA peer at the ASP is unavailable and/or the
SCTP association is down. Initially all ASPs will be in this state. related SCTP association is down. Initially all ASPs will be in this
An ASP in this state SHOULD NOT not be sent any M2UA messages. state. An ASP in this state SHOULD NOT be sent any M2UA messages, with
the exception of Heartbeat 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 can 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. application traffic is active (for a particular Interface Identifier
or set of Interface Identifiers).
Figure 6 ASP State Transition Diagram Figure 6: ASP State Transition Diagram
+----------------+ +--------------+
| ASP-ACTIVE |
+----------------------| | +----------------------| |
| Alternate +-------| ASP-ACTIVE | | Other +-------| |
| ASP | | | | ASP in AS | +--------------+
| Takeover | +----------------+ | 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 local SCTP layer's Communication Down Indication to the
Upper Layer Protocol (M2UA) on an SG. The local SCTP will send this
indication when it detects the loss of connectivity to the ASP's peer
SCTP layer. SCTP CDI is understood as either a SHUTDOWN COMPLETE
notification and COMMUNICATION LOST notification from the SCTP.
SCTP RI: The local SCTP layer's Restart Indication to the Upper
Layer Protocol (M2UA) on an SG. The local SCTP will send this
indication when it detects a restart from the ASP's peer SCTP layer.
When an SCTP association fails at the SG, M2UA shall change the states SCTP CDI: The SCTP CDI denotes the local SCTP layer's Communication
of all ASPs reached through the aborted SCTP association to ASP-DOWN. Down Indication to the Upper Layer Protocol (M2UA) on an SGP. The local
SCTP layer will send this indication when it detects the loss of
connectivity to the ASP's peer SCTP layer. SCTP CDI is understood as
either a SHUTDOWN_COMPLETE notification or COMMUNICATION_LOST
notification from the SCTP layer.
4.3.1.2 AS States SCTP RI: The local SCTP layer's Restart indication to the upper layer
protocol (M2UA) on an SG. The local SCTP will send this indication when
it detects a restart from the ASP's peer SCTP layer.
The state of the AS is maintained in the M2UA layer on the SG. 4.3.2 AS States
The state of an AS changes due to events. These events include the The state of the AS is maintained in the M2UA layer on the SGP. The
following: 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 following: 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. When that all related ASPs are in the ASP-DOWN state for this AS. Initially
the AS transitions to the AS-DOWN state, all of the SS7 links (Interface the AS will be in this state. An Application Server MUST be in the AS-
Identifiers) for this AS should be taken out-of-service. Initially the DOWN state before it can be removed from a configuration.
AS will be in this state.
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-INACTIVE traffic is active (i.e., one or more related ASPs are in the ASP-
state, but none in the ASP-ACTIVE state). INACTIVE state, but none in the ASP-ACTIVE state). The recovery 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 traffic
is active. This state implies that one ASP is in the ASP-ACTIVE state. is active. This state implies that at least one ASP is in the ASP-
ACTIVE state.
AS-PENDING: An active ASP has transitioned from active to inactive or AS-PENDING: An active ASP has transitioned to ASP-INACTIVE or ASP-DOWN
down and it was the last remaining active ASP in the AS. A recovery and it was the last remaining active ASP in the AS. A recovery timer
timer T(r) will be started and all incoming SCN messages will be T(r) SHOULD be started and all incoming signalling messages SHOULD be
queued by the SG. If an ASP becomes active before T(r) expires, the queued by the SGP. If an ASP becomes ASP-ACTIVE before T(r) expires,
AS will move to AS-ACTIVE state and all the queued messages will be the AS is moved to the AS-ACTIVE state and all the queued messages will
sent to the active ASP. be sent to the ASP.
If T(r) expires before an ASP becomes active, the SG stops queueing If T(r) expires before an ASP becomes ASP-ACTIVE, the SGP stops queuing
messages and discards all previously queued messages. In addition, messages and discards all previously queued messages. The AS will move
the SG MAY send the Stop primitive to MTP2 to take the link out of to the AS-INACTIVE state if at least one ASP is in ASP-INACTIVE state,
service. Note that the actions taken by the SG should be accordance otherwise it will move to AS-DOWN state.
with the appropriate MTP specifications. The AS will move to AS-Inactive
if at least one ASP is in ASP-INACTIVE state, otherwise it will move to
AS-DOWN state.
If an ASP transitions to the ASP-DOWN state and all ASPs in the AS are Figure 7 shows an example AS state machine for the case where the
in the ASP-DOWN state, then the SG SHALL send the Stop primitive to MTP2 AS/ASP data is pre-configured. For other cases where the AS/ASP
to take the link out of service and moves the AS to the AS-DOWN state. configuration data is created dynamically, there would be differences
in the state machine, especially at creation of the AS.
Figure 7 AS State Transition Diagram For example, where the AS/ASP configuration data is not created until
Registration of the first ASP, the AS-INACTIVE state is entered
directly upon the first successful REG REQ from an ASP. Another
example is where the AS/ASP configuration data is not created until the
first ASP successfully enters the ASP-ACTIVE state. In this case the
AS-ACTIVE state is entered directly.
+----------+ one ASP trans ACTIVE +-------------+ Figure 7: AS State Transition Diagram
| |------------------------>| |
| AS-INACT | | AS-ACTIVE | +----------+ one ASP trans to ACTIVE +-------------+
| | | | | AS- |---------------------------->| AS- |
| |< | | | INACTIVE | | ACTIVE |
| |<--- | |
+----------+ \ +-------------+ +----------+ \ +-------------+
^ | \ Tr Expires ^ | ^ | \ Tr Expiry, ^ |
| | \ at least one | | | | \ at least one | |
| | \ ASP in UP | | | | \ ASP in ASP-INACTIVE | |
| | \ | |
| | \ | | | | \ | |
| | \ | | | | \ | |
one ASP | | \ one ASP | | Last ACTIVE ASP
trans | | all ASP \------\ trans to | | trans to INACT
to | | trans to \ ACTIVE | | or DOWN
INACT | | DOWN \ | | (start Tr timer)
| | \ | | | | \ | |
one ASP | | all ASP \ one ASP | | Last ACTIVE
trans | | trans to \ trans to | | ASP trans to
to | | ASP-DOWN -------\ ASP- | | ASP-INACTIVE
ASP- | | \ ACTIVE | | or ASP-DOWN
INACTIVE| | \ | | (start Tr)
| | \ | | | | \ | |
| | \ | | | | \ | |
| v \ | v | v \ | v
+----------+ \ +-------------+ +----------+ \ +-------------+
| | -| | | | --| |
| AS-DOWN | | AS-PENDING | | AS-DOWN | | AS-PENDING |
| | | (queueing) | | | | (queueing) |
| |<------------------------| | | |<----------------------------| |
+----------+ Tr Expiry and no +-------------+ +----------+ Tr Expiry and no ASP +-------------+
ASP in INACTIVE state in ASP-INACTIVE state
Tr = Recovery Timer Tr = Recovery Timer
4.3.2 ASPM 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 SG and ASP is assumed to be in the state ASP-DOWN. the SGP and ASP is assumed to be in the state ASP-DOWN.
As the ASP is responsible for initiating the setup of an SCTP
association to an SG, the M2UA layer at an ASP receives an M-SCTP
ESTABLISH request primitive from the Layer Management, the M2UA layer
will try to establish an SCTP association with the remote M2UA peer at
an SG. Upon reception of an eventual SCTP-COMMUNICATION_UP confirm
primitive from the SCTP, the M2UA layer will invoke the primitive
M-SCTP_ESTABLISH confirm to the Layer Management.
At the SG, the M2UA layer will receive an SCTP-COMMUNICATION_UP
indication primitive from the SCTP. The M2UA layer will then invoke
the primitive M-SCTP_ESTABLISH indication to the Layer Management.
Once the SCTP association is established and assuming that the local
M2UA-User is ready, the local ASP M2UA Application Server Process
Maintenance (ASPM) function will initiate the ASPM procedures, using
the ASP Up/Down/Active/Inactive messages to convey the ASP state to
the SG - see Section 4.3.3.
The Layer Management and the M2UA layer on SG can communicate the Once the SCTP association is established (see Section 4.2.1) and
status of the application server using the M-AS_STATUS primitives. assuming that the local M2UA-User is ready, the local M2UA ASP
The Layer Managements and the M2UA layers on both the SG and ASP Maintenance (ASPM) function will initiate the relevant procedures,
can communicate the status of an SCTP association using the using the ASP Up/ASP Down/ASP Active/ASP Inactive messages to convey
M-SCTP_STATUS primitives. the ASP state to the SGP (see Section 4.4.3).
If the Layer Management on SG or ASP wants to bring down an SCTP If the M2UA layer subsequently receives an SCTP-COMMUNICATION_DOWN
association for management reasons, they would send M-SCTP_RELEASE or SCTP-RESTART indication primitive from the underlying SCTP layer,
request primitive to the local M2UA layer. The M2UA layer would it will inform the Layer Management by invoking the M-SCTP_STATUS
release the SCTP association and upon receiving the SCTP Communication indication primitive. The state of the ASP will be moved to ASP-DOWN.
Down indication from the underlying SCTP layer, it would inform the
local Layer Management using M-SCTP_RELEASE confirm primitive.
If the M2UA layer receives an SCTP-COMMUNICATION_DOWN or Restart In the case of SCTP-COMMUNICATION_DOWN, the SCTP client MAY try to re-
indication from the underlying SCTP layer, it will inform the Layer establish the SCTP association. This MAY be done by the M2UA layer
Management by invoking the M-SCTP_RELEASE indication primitive. At the automatically, or Layer Management MAY re-establish using the
SG, M2UA shall change the states of all ASPs reached through the aborted M-SCTP_ESTABLISH request primitive.
SCTP association to ASP DOWN. At the ASP, the M2UA layer will take
action based on the appropriate MTP specification. The ASP may indicate
to another ASP that it should become active. However, the ASP to ASP
communication is out of the scope of this document.
At an ASP, the Layer Management MAY try to reestablish the SCTP In the case of an SCTP-RESTART indication at an ASP, the ASP is now
association using M-SCTP_ESTABLISH request primitive. 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.
4.3.3 ASPM procedures for peer-to-peer messages 4.3.4 ASPM Procedures for Peer-to-Peer Messages
All ASPM messages are sent on a sequenced stream to ensure ordering. 4.3.4.1 ASP Up Procedures
SCTP stream '0' SHOULD be used.
4.3.3.1 ASP Up After an ASP has successfully established an SCTP association to an
SGP, the SGP waits for the ASP to send an ASP Up message, indicating
that the ASP M2UA peer is available. The ASP is always the initiator
of the ASP Up message. This action MAY be initiated at the ASP by an
M-ASP_UP request primitive from Layer Management or MAY be initiated
automatically by an M2UA management function.
After an ASP has successfully established an SCTP association to an SG, When an ASP Up message is received at an SGP and internally the remote
the SG waits for the ASP to send an ASP Up message, indicating that the ASP is in the ASP-DOWN state and not considered locked-out for local
ASP M2UA peer is available. The ASP is always the initiator of the management reasons, the SGP marks the remote ASP in the state ASP-
ASP Up exchange. INACTIVE and informs Layer Management with an M-ASP_Up indication
primitive. If the SGP is aware, via current configuration data, which
Application Servers the ASP is configured to operate in, the SGP
updates the ASP state to ASP-INACTIVE in each AS that it is a member.
When an ASP Up message is received at an SG and internally the ASP is Alternatively, the SGP may move the ASP into a pool of Inactive ASPs
not considered locked-out for local management reasons, the SG marks available for future configuration within Application Server(s),
the remote ASP as Inactive. If the ASP UP message contains an ASP determined in a subsequent Registration Request or ASP Active
Identifier, the SG should save the ASP Identifier for that ASP. The procedure. If the ASP Up message contains an ASP Identifier, the SGP
SG responds with an ASP Up Ack message in acknowledgement. The SG should save the ASP Identifier for that ASP. The SGP MUST send an
sends an ASP Up Ack message in response to a received ASP Up message ASP Up Ack message in response to a received ASP Up message even if
even if the ASP is already marked as ASP-INACTIVE at the SG. 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".
When the ASP sends an ASP Up it starts timer T(ack). If the ASP does At the ASP, the ASP Up Ack message received is not acknowledged. Layer
not receive a response to an ASP Up within T(ack), the ASP MAY restart Management is informed with an M-ASP_UP confirm primitive. When an ASP
T(ack) and resend ASP Up messages until it receives an ASP Up Ack enters the ASP-INACTIVE state from the ASP-DOWN state towards an SGP
or ASP Down Ack message. T(ack) SHOULD be provisionable, with a default the M2UA MUST mark all SS7 destinations configured to be reachable via
of 2 seconds. Alternatively, retransmission of ASP Up messages MAY be this SGP as available.
put under control of Layer Management. In this method, expiry of T(ack)
results in a M-ASP_UP confirmation carrying a negative indication.
The ASP MUST wait for the ASP Up Ack message from the SG before When the ASP sends an ASP Up message it starts timer T(ack). If the
sending any ASP traffic control messages (ASPAC or ASPIA) or MAUP ASP does not receive a response to an ASP Up message within T(ack), the
messages or it will risk message loss. If the SG receives MAUP ASP MAY restart T(ack) and resend ASP Up messages until it receives an
messages before an ASP Up is received, the SG SHOULD discard them. ASP Up Ack message. T(ack) is provisionable, with a default of 2
seconds. Alternatively, retransmission of ASP Up messages MAY be put
under control of Layer Management. In this method, expiry of T(ack)
results in an M-ASP_UP confirm primitive carrying a negative
indication.
The ASP MUST wait for the ASP Up Ack message before sending any other
M2UA messages (e.g., ASP Active or REG REQ). If the SGP receives any
other M2UA messages before an ASP Up message is received, the SGP
SHOULD 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 or ASP-STANDBY state, an ASP-Up Ack message is returned, the ASP-ACTIVE state, an ASP Up Ack message is returned, as well as
as well as an Error message ("Unexpected Message), and the remote ASP an Error message ("Unexpected Message), and the remote ASP state is
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.3.2 ASP Down 4.3.4.1.1 M2UA Version Control
The ASP will send an ASP Down message to an SG when the ASP wishes to If an ASP Up message with an unsupported version is received, the
receiving end responds with an Error message, indicating the version
the receiving node supports and notifies Layer Management.
This is useful when protocol version upgrades are being performed in a
network. A node upgraded to a newer version should support the older
versions used on other nodes it is communicating with. Because ASPs
initiate the ASP Up procedure it is assumed that the Error message
would normally come from the SGP.
4.3.4.2 ASP Down Procedures
The ASP will send an ASP Down message to an SGP when the ASP wishes to
be removed from service in all Application Servers that it is a member be removed from service in all Application Servers that it is a member
and no longer receive any DATA, SSNM or ASPTM messages. This action and no longer receive any MAUP or ASPTM messages. This action MAY be
MAY be initiated at the ASP by an M-ASP_DOWN request primitive from Layer initiated at the ASP by an M-ASP_DOWN request primitive from Layer
Management or MAY be initiated automatically by an M2UA management Management or MAY be initiated automatically by an M2UA management
function. function.
The SG marks the ASP as ASP-DOWN, informs Layer Management with an M- Whether the ASP is permanently removed from any AS is a function of
ASP_Down indication primitive, and returns an ASP Down Ack message to configuration management. In the case where the ASP previously used
the ASP. has locked out the ASP for management reasons. the Registration procedures (see Section 4.3.5) to register within
Application Servers but has not deregistered from all of them prior to
sending the ASP Down message, the SGP SHOULD consider the ASP as
Deregistered in all Application Servers that it is still a member.
The SG MUST send an ASP Down Ack message in response to a received ASP- The SGP marks the ASP as ASP-DOWN, informs Layer Management with an
M-ASP_Down indication primitive, and returns an ASP Down Ack message
to the ASP.
The SGP MUST send an ASP Down Ack message in response to a received ASP
Down message from the ASP even if the ASP is already marked as ASP-DOWN Down message from the ASP even if the ASP is already marked as ASP-DOWN
at the SGP. The SG MUST send an ASP Down Ack message even if the reason at the SGP.
in the received ASP Down message is considered invalid.
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. If
the ASP receives an ASP Down Ack without having sent an ASP Down 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, the
ASP should then initiate procedures to return itself to its previous ASP should then initiate procedures to return itself to its previous
state. state.
When the ASP sends an ASP Down it starts timer T(ack). If the ASP does When the ASP sends an ASP Down message it starts timer T(ack). If the
not receive a response to an ASP Down within T(ack), the ASP MAY ASP does not receive a response to an ASP Down message within T(ack),
restart T(ack) and resend ASP Down messages until it receives an the ASP MAY restart T(ack) and resend ASP Down messages until it
ASP Down Ack message. T(ack) SHOULD be provisionable, with a default receives an ASP Down Ack message. T(ack) is provisionable, with a
of 2 seconds. Alternatively, retransmission of ASP Down messages MAY default of 2 seconds. Alternatively, retransmission of ASP Down
be put under control of Layer Management. In this method, expiry of messages MAY be put under control of Layer Management. In this method,
T(ack) results in a M-ASP_DOWN confirmation carrying a negative expiry of T(ack) results in an M-ASP_DOWN confirm primitive carrying a
indication. negative indication.
4.3.3.3 M2UA Version Control
If a ASP Up message with an unsupported version is received, the 4.3.4.4 ASP Active Procedures
receiving end responds with an Error message, indicating the version
the receiving node supports.
This is useful when protocol version upgrades are being performed in a Anytime after the ASP has received an ASP Up Ack message from the SGP,
network. A node upgraded to a newer version SHOULD support the older the ASP MAY send an ASP Active message to the SGP indicating that
versions used on other nodes it is communicating with. Because ASPs the ASP is ready to start processing traffic. This action MAY be
initiate the ASP Up procedure it is assumed that the Error message initiated at the ASP by an M-ASP_ACTIVE request primitive from Layer
would normally come from the SG. Management or MAY be initiated automatically by a M2UA management
function. In the case where an ASP wishes to process the traffic for
more than one Application Server across a common SCTP association, the
ASP Active message(s) SHOULD contain a list of one or more Interface
Identifiers to indicate for which Application Servers the ASP Active
message applies. It is not necessary for the ASP to include any
Interface Identifiers of interest in a single ASP Active message,
thus requesting to become active in all Interface Identifiers at the
same time. Multiple ASP Active messages MAY be used to activate
within the Application Servers independently, or in sets. In the
case where an ASP Active message does not contain a Interface
Identifier parameter, the receiver must know, via configuration data,
which Application Server(s) the ASP is a member.
4.3.3.4 ASP Active For the Application Servers that the ASP can successfully activate,
the SGP responds with one or more ASP Active Ack messages, including
the associated Interface Identifier(s) and reflecting any Traffic Mode
Type value present in the related ASP Active message. The Interface
Identifier parameter MUST be included in the ASP Active Ack message(s)
if the received ASP Active message contained any Interface Identifiers.
Depending on any Traffic Mode Type request in the ASP Active message
or local configuration data if there is no request, the SGP moves the
ASP to the correct ASP traffic state within the associated Application
Server(s). Layer Management is informed with an M-ASP_Active
indication. If the SGP receives any Data messages before an ASP Active
message is received, the SGP MAY discard them. By sending an ASP
Active Ack message, the SGP is now ready to receive and send traffic
for the related Interface Identifier(s). The ASP SHOULD NOT send MAUP
messages for the related Interface Identifier(s) before receiving an
ASP Active Ack message, or it will risk message loss.
Any time after the ASP has received a ASP Up Ack from the SG, the ASP Multiple ASP Active Ack messages MAY be used in response to an ASP
can send an ASP Active (ASPAC) to the SG indicating that the ASP is Active message containing multiple Interface Identifiers, allowing
ready to start processing traffic. This action MAY be initiated at the the SGP to independently acknowledge the ASP Active message for
ASP by an M-ASP_ACTIVE request primitive from Layer Management or MAY be different (sets of) Interface Identifiers. The SGP MUST send
initiated automatically by an M2UA management function. an Error message ("Invalid Interface Identifier") for each Interface
Identifier value that cannot be successfully activated.
When an ASP Active (ASPAC) message is received, the SG responds to the In the case where an "out-of-the-blue" ASP Active message is received
ASP with a ASPAC Ack message acknowledging that the ASPAC was received (i.e., the ASP has not registered with the SG or the SG has no static
and starts sending traffic for the associated Application Server configuration data for the ASP), the message MAY be silently discarded.
to that ASP. Note that the SG sends an ASP Active Ack message in
response to a received ASP Active message even if the ASP is already
marked as "Active" at the SG.
The ASP MUST wait for the ASP Active Ack message from the SG before The SGP MUST send an ASP Active Ack message in response to a received
sending any Data messages or it will risk message loss. If the SG ASP Active message from the ASP, if the ASP is already marked in the
receives MAUP messages before an ASP Active is received, the SG SHOULD ASP-ACTIVE state at the SGP.
discard these messages.
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
Active Ack message as the ASP Active Ack and Data messages from an SG
may be sent on different SCTP streams. Message loss is possible as
the ASP does not consider itself in the ASP-ACTIVE state until
reception of the ASP Active Ack message.
When the ASP sends an ASP Active 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 within T(ack), the the ASP does not receive a response to an ASP Active message within
ASP MAY restart T(ack) and resend ASP Active messages until it T(ack), the ASP MAY restart T(ack) and resend ASP Active message(s)
receives an ASP Active Ack message. T(ack) SHOULD be provisionable, with until it receives an ASP Active Ack message. T(ack) is provisionable,
a default of 2 seconds. Alternatively, retransmission of ASP Active with a default of 2 seconds. Alternatively, retransmission of ASP
messages may be put under control of Layer Management. In this method, Active messages MAY be put under control of Layer Management. In
expiry of T(ack) results in a M-ASP_ACTIVE confirmation carrying a this method, expiry of T(ack) results in an M-ASP_ACTIVE confirm
negative indication. primitive carrying a negative indication.
There are three modes of Application Server traffic handling in the SG There are three modes of Application Server traffic handling in the SGP
M2UA: Over-ride, Load-share and Broadcast. The Traffic Mode Type M2UA layer: Override, Loadshare and Broadcast. When included, the
parameter in the ASPAC messge indicates the mode used in a particular Traffic Mode Type parameter in the ASP Active message indicates the
Application Server. If the SG determines that the mode indicates in traffic handling mode to be used in a particular Application Server.
an ASPAC is incompatible with the traffic handling mode currently used If the SGP determines that the mode indicated in an ASP Active message
in the AS, the SG responds with an Error message indicating Unsupported is unsupported or incompatible with the mode currently configured for
Traffic Handling Mode. the AS, the SGP responds with an Error message ("Unsupported / Invalid
Traffic Handling Mode"). If the traffic handling mode of the
Application Server is not already known via configuration data, then
the traffic handling mode indicated in the first ASP Active message
causing the transition of the Application Server state to AS-ACTIVE MAY
be used to set the mode.
For Over-ride mode AS, the reception of an ASPAC message at an SG causes In the case of an 0verride mode AS, reception of an ASP Active message
the redirection of all traffic for the AS to the ASP that sent the ASPAC. at an SGP causes the (re)direction of all traffic for the AS to the ASP
The SG responds to the ASPAC with an ASP Active Ack message to the ASP. that sent the ASP Active message. Any previously active ASP in the AS
Any previously active ASP in the AS is now considered Inactive and will is now considered to be in state ASP-INACTIVE and SHOULD no longer
no longer receive traffic from the SG within the AS. The SG MUST send a receive traffic from the SGP within the AS. The SGP then MUST send a
Notify (Alternate ASP-Active) to the previously active ASP in the AS, Notify message ("Alternate ASP Active") to the previously active ASP
after stopping all traffic to that ASP. in the AS, and SHOULD stop traffic to/from that ASP. The ASP receiving
this Notify MUST consider itself now in the ASP-INACTIVE state, if it
is not already aware of this via inter-ASP communication with the
Overriding ASP.
In the case of a Load-share mode AS, reception of an ASPAC message at In the case of a Load-share mode AS, reception of an ASP Active
an SG causes the redirection of some traffic to the ASP sending the message at an SGP causes the direction of traffic to the ASP sending
ASPAC. The algorithm at the SG for load-sharing traffic within an AS the ASP Active message, in addition to all the other ASPs that are
to all the active ASPs is implementation dependent. The algorithm currently active in the AS. The algorithm at the SGP for load-sharing
could, for example be round-robin or based on information in the Data traffic within an AS to all the active ASPs is implementation
message (e.g., such as the SLS in the Routing Label). dependent. The algorithm could, for example be round-robin or based
on information in the Data message (e.g., such as the SLS in the
Routing Label).
In the case of a Broadcast mode AS, reception of an ASPAC message at An SGP, upon reception of an ASP Active message for the first ASP in
an SG causes the traffic to be sent to the ASP sending the ASPAC and a Loadshare AS, MAY choose not to direct traffic to a newly active ASP
the same traffic continues to be sent to the other Active ASP(s). The until it determines that there are sufficient resources to handle the
ASPs within a broadcast mode AS must coordinate between themselves to expected load (e.g., until there are "n" ASPs in state ASP-ACTIVE in
determine which portion of the broadcast traffic they will handle. the AS).
Whenever an ASP in a Broadcast mode AS becomes ASP-ACTIVE, the SG MUST All ASPs within a load-sharing mode AS must be able to process any
tag the first DATA message broadcast in each SCTP stream with a Data message received for the AS, to accommodate any potential
fail-over or rebalancing of the offered load.
In the case of a Broadcast mode AS, reception of an ASP Active message
at an SGP causes the direction of traffic to the ASP sending the ASP
Active message, in addition to all the other ASPs that are currently
active in the AS. The algorithm at the SGP for broadcasting
traffic within an AS to all the active ASPs is a simple broadcast
algorithm, where every message is sent to each of the active ASPs.
An SGP, upon reception of an ASP Active message for the first
ASP in a Broadcast AS, MAY choose not to direct traffic to a newly
active ASP until it determines that there are sufficient resources to
handle the expected load (e.g., until there are "n" ASPs in state
ASP-ACTIVE in the AS).
Whenever an ASP in a Broadcast mode AS becomes ASP-ACTIVE, the SGP
MUST tag the first DATA message broadcast in each SCTP stream with a
unique Correlation Id parameter. The purpose of this Correlation Id unique Correlation Id parameter. The purpose of this Correlation Id
is to permite the newly active ASP to synchronize its processing of is to permit the newly active ASP to synchronize its processing of
the traffic in each ordered stream with other ASPs in the broadcast traffic in each ordered stream with the other ASPs in the broadcast
group. group.
4.3.3.5 ASP Inactive 4.3.4.5 ASP Inactive Procedures
When an ASP wishes to withdraw from receiving traffic within an AS, When an ASP wishes to withdraw from receiving traffic within an AS, the
the ASP sends an ASP Inactive (ASPIA) to the SG. This action MAY ASP sends an ASP Inactive message to the SGP. This action MAY be
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. management function. In the case where an ASP is processing the
traffic for more than one Application Server across a common SCTP
association, the ASP Inactive message contains one or more Interface
Identifiers to indicate for which Application Servers the ASP Inactive
message applies. In the case where an ASP Inactive message does not
contain a Interface Identifier parameter, the receiver must know, via
configuration data, which Application Servers the ASP is a member and
move the ASP to the ASP-INACTIVE state in all Application Servers.
In the case of an Override mode AS, where another ASP has already
taken over the traffic within the AS with an ASP Active ("Override")
message, the ASP that sends the ASP Inactive message is already
considered by the SGP to be in state ASP-INACTIVE. An ASP Inactive
Ack message is sent to the ASP, after ensuring that all traffic is
stopped to the ASP.
There are three modes of Application Server traffic handling in the SG In the case of a Load-share mode AS, the SGP moves the ASP to the ASP-
M2UA when withdrawing an ASP from service - Over-ride, Load-share and INACTIVE state and the AS traffic is re-allocated across the remaining
Broadcast. The Traffic Mode Type parameter in the ASPIA messge indicates ASPs in the state ASP-ACTIVE, as per the load-sharing algorithm
the mode used in a particular Application Server. If the SG determines currently used within the AS. A Notify message ("Insufficient ASP
that the mode indicates in an ASPAC is incompatible with the traffic resources active in AS") MAY be sent to all inactive ASPs, if required.
handling mode currently used in the AS, the SG responds with an Error An ASP Inactive Ack message is sent to the ASP after all traffic
message indicating Unsupported Traffic Handling Mode. is halted and Layer Management is informed with an M-ASP_INACTIVE
indication primitive.
In the case of an Over-ride mode AS, where normally another ASP has In the case of a Broadcast mode AS, the SGP moves the ASP to the
already taken over the traffic within the AS with an Over-ride ASPAC, ASP-INACTIVE state and the AS traffic is broadcast only to the
the ASP which sends the ASPIA is already considered by the SG to be remaining ASPs in the state ASP-ACTIVE. A Notify message
in the ASP-INACTIVE state. An ASPIA Ack message is sent to the ASP, ("Insufficient ASP resources active in AS") MAY be sent to all
after ensuring that all traffic is stopped to the ASP. inactive ASPs, if required. An ASP Inactive Ack message is sent to
the ASP after all traffic is halted and Layer Management is informed
with an M-ASP_INACTIVE indication primitive.
In the case of a Load-share mode AS, the SG moves the ASP to the Multiple ASP Inactive Ack messages MAY be used in response to an
ASP-INACTIVE state and the AS traffic is re-allocated across the ASP Inactive message containing multiple Interface Identifers,
remaining "active" ASPs per the load-sharing algorithm currently used allowing the SGP to independently acknowledge for different (sets
within the AS. A NTFY(Insufficient ASP resources active in AS) MAY be of) Interface Identifiers. The SGP sends an Error message ("Invalid
sent to all inactive ASPs, if required. An ASPIA Ack message MUST be Interface Identifier") message for each invalid or unconfigured
sent to the ASP after all traffic is halted and Layer Management is Interface Identifer value in a received ASP Inactive message.
informed with an ASP-INACTIVE indication primitive.
In the case of a Broadcast mode AS, the SG moves the ASP to the The SGP MUST send an ASP Inactive Ack message in response to a received
ASP-INACTIVE state and stops sending the AS traffic to the ASP. The ASP Inactive message from the ASP and the ASP is already marked as ASP-
SG continues to send the AS traffic to the remaining "active" ASPs. INACTIVE at the SGP.
A NTFY(Insufficient ASP resources active in AS) MAY be sent to all
inactive ASPs, if required. An ASPIA Ack message MUST be sent to
the ASP after all traffic is halted and Layer Management is informed
with an ASP-INACTIVE indication primitive.
When the ASP sends an ASP Inactive it starts timer T(ack). If the ASP At the ASP, the ASP Inactive Ack message received is not acknowledged.
does not receive a response to an ASP Inactive within T(ack), the ASP Layer Management is informed with an M-ASP_INACTIVE confirm primitive.
MAY restart T(ack) and resend ASP Inactive messages until it receives If the ASP receives an ASP Inactive Ack without having sent an ASP
an ASP Inactive Ack message. T(ack) SHOULD be provisionable, with a Inactive message, the ASP should now consider itself as in the
default of 2 seconds. Alternatively, retransmission of ASP Inactive ASP-INACTIVE state. If the ASP was previously in the ASP-ACTIVE
messages may be put under control of Layer Management. In this method, state, the ASP should then initiate procedures to return itself to
expiry of T(ack) results in a M-ASP-Inactive confirmation carrying a its previous state.
negative indication.
If no other ASPs are Active in the Application Server, the SG either When the ASP sends an ASP Inactive message it starts timer T(ack).
discards all incoming messages for the AS or starts buffering the If the ASP does not receive a response to an ASP Inactive message
incoming messages for T(r) seconds, after which messages will be within T(ack), the ASP MAY restart T(ack) and resend ASP Inactive
discarded. T(r) is configurable by the network operator. If the SG messages until it receives an ASP Inactive Ack message. T(ack) is
receives an ASPAC from an ASP in the AS before expiry of T(r), the provisionable, with a default of 2 seconds. Alternatively,
buffered traffic is directed to the ASP and the timer is cancelled. retransmission of ASP Inactive messages MAY be put under control of
Layer Management. In this method, expiry of T(ack) results in a M-
ASP_Inactive confirm primitive carrying a negative indication.
4.3.3.6 Notify If no other ASPs in the Application Server are in the state ASP-ACTIVE
or ASP-STANDBY, the SGP MUST send a Notify message ("AS-Pending") to
all of the ASPs in the AS which are in the state ASP-INACTIVE. The SGP
SHOULD start buffering the incoming messages for T(r)seconds, after
which messages MAY be discarded. T(r) is configurable by the network
operator. If the SGP receives an ASP Active message from an ASP in the
AS before expiry of T(r), the buffered traffic is directed to that ASP
and the timer is cancelled. If T(r) expires, the AS is moved to the
AS-INACTIVE state.
A Notify message reflecting a change in the AS state MUST be sent to all 4.3.4.6 Notify Procedures
ASP(s) in the AS, except those in the ASP-DOWN state, with appropriate
Status Information.
In the case where a Notify (AS-Pending) message is sent by an SG A Notify message reflecting a change in the AS state MUST be sent to
that now has no ASP(s) active to service the traffic, the Notify does all ASPs in the AS, except those in the ASP-DOWN state, with
not explicitly force the ASP(s) receiving the message to become appropriate Status Information and any ASP Identifier of the failed
active. The ASP remain in control of what (and when) action is ASP. At the ASP, Layer Management is informed with an M-NOTIFY
taken. indication primitive. The Notify message MUST be sent whether the
AS state change was a result of an ASP failure or reception of an
ASP State Management (ASPSM) / ASP Traffic Management (ASPTM) message.
In the second case, the Notify message MUST be sent after any related
acknowledgement messages (e.g., ASP Up Ack, ASP Down Ack, ASP Active
Ack, or ASP Inactive Ack).
In addition, the Notify message MUST be sent to all ASP(s) in the In the case where a Notify ("AS-PENDING") message is sent by an
AS, except those in the ASP-DOWN state, when an ASP fails with the SGP that now has no ASPs active to service the traffic, or where a
ASP Identifier of the failed ASP. Notify ("Insufficient ASP resources active in AS") message MUST be sent
in the Loadshare or Broadcast mode, the Notify message does not
explicitly compel the ASP(s) receiving the message to become active.
The ASPs remain in control of what (and when) traffic action is taken.
In the case where a Notify message does not contain a Interface
Identifier parameter, the receiver must know, via configuration data,
of which Application Servers the ASP is a member and take the
appropriate action in each AS.
4.3.4.7 Heartbeat Procedures
The optional Heartbeat procedures MAY be used when operating over
transport layers that do not have their own heartbeat mechanism for
detecting loss of the transport association (i.e., other than SCTP).
Either M2UA peer may optionally send Heartbeat messages periodically,
subject to a provisionable timer T(beat). Upon receiving a Heartbeat
message, the M2UA peer MUST respond with a Heartbeat Ack message.
If no Heartbeat Ack message (or any other M2UA message) is received
from the M2UA peer within 2*T(beat), the remote M2UA peer is considered
unavailable. Transmission of Heartbeat messages is stopped and the
signalling process SHOULD attempt to re-establish communication if it
is configured as the client for the disconnected M2UA peer.
The Heartbeat message may optionally contain an opaque Heartbeat Data
parameter that MUST be echoed back unchanged in the related Heartbeat
Ack message. The sender, upon examining the contents of the returned
Heartbeat Ack message, MAY choose to consider the remote M2UA peer as
unavailable. The contents/format of the Heartbeat Data parameter is
implementation-dependent and only of local interest to the original
sender. The contents may be used, for example, to support a Heartbeat
sequence algorithm (to detect missing Heartbeats), and/or a timestamp
mechanism (to evaluate delays).
Note: Heartbeat related events are not shown in Figure 6 "ASP state
transition diagram".
4.4 Link Key Management Procedures 4.4 Link Key Management Procedures
The Interface Identifer Management procedures can be used to support The Interface Identifier Management procedures are optional. They can
automatic allocation of Signaling Terminals or Signaling Data be used to support automatic allocation of Signalling Terminals or
Links [2][3]. Signalling Data Links [2][3].
4.4.1 Registration 4.4.1 Registration
An ASP MAY dynamically register with an SG as an ASP within an An ASP MAY dynamically register with an SGP as an ASP within an
Application Server using the REG REQ message. A Link Key parameter Application Server for individual Interface Identifier(s) using
in the REG REQ specifies the parameters associated with the Link the REG REQ message. A Link Key parameter in the REG REQ specifies
Key. the parameters associated with the Link Key.
The SG examines the contents of the received Link Key parameters (SDLI The SGP examines the contents of the received Link Key parameters (SDLI
and SDTI) and compares them with the currently provisioned Interface and SDTI) and compares them with the currently provisioned Interface
Identifiers. If the received Link Key matches an existing SG Link Key Identifiers. If the received Link Key matches an existing SGP Link Key
entry, and the ASP is not currently included in the list of ASPs for entry, and the ASP is not currently included in the list of ASPs for
the related Application Server, the SG MAY authorize the ASP to be added the related Application Server, the SGP MAY authorize the ASP to be
to the AS. Or, if the Link Key does not currently exist and the added to the AS. Or, if the Link Key does not currently exist and the
received Link Key data is valid and unique, an SG supporting dynamic received Link Key data is valid and unique, an SGP supporting dynamic
configuration MAY authorize the creation of a new Interface Identifier configuration MAY authorize the creation of a new Interface Identifier
and related Application Server and add the ASP to the new AS. In either and related Application Server and add the ASP to the new AS. In either
case, the SG returns a Registration Response message to the ASP, case, the SGP returns a Registration Response message to the ASP,
containing the same Local-LK-Identifier as provided in the initial containing the same Local-LK-Identifier as provided in the initial
request, a Registration Result "Successfully Registered" and the request, a Registration Result "Successfully Registered" and the
Interface Identifier. A unique method of Interface Identifier valid Interface Identifier. A unique method of Interface Identifier valid
assignment at the SG/SGP is implementation dependent but must be assignment at the SG/SGP is implementation dependent but must be
guaranteed to be unique across all SGPs in an SG. guaranteed to be unique for each Application server or Link Key
served by SGP.
If the SG determins 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 SG 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 SG determins that the Link Key parameter overlaps with an If the SGP determins that the Link Key parameter overlaps with an
existing Link Key entry, the SG 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 SG cannot match against more than one Link Key. received at an SGP cannot match against more than one Link Key.
If the SG does not authorize the registration request, the SG 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 SG determines that a received Link Key does not currently If an SGP determines that a received Link Key does not currently
exist and the SG does not support dynamic configuration, the SG 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 SG determines that a received Link Key does not currently If an SGP determines that a received Link Key does not currently
exist and the SG 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
SG 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 SG 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, response 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 SG 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 deregister with an SG as an ASP within an An ASP MAY dynamically de-register with an SGP as an ASP within an
Application Server for particular Interface Identifier(s) using Application Server for individual Interface Identifier(s) using
the DEREG REQ message. A Interface Identifier parameter in the the DEREG REQ message. A Interface Identifier parameter in the
DEREG REQ specifies which Inteface Identifer to de-register. DEREG REQ specifies which Interface Identifier to de-register.
The SG 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 SG. 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, in which case the Link Key data CANNOT be deleted. If a Server, 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
SG MAY delte the Link Key data. SGP MAY delete the Link Key data.
The SG acknowledges the de-registration requres by returning a DEREG The SGP acknowledges the de-registration requires by returning a DEREG
RSP to the requesting ASP. The result of the de-registration is RSP to the requesting ASP. The result of the de-registration is
found in the Deregistration Result paraemeter, indicating success or found in the Deregistration Result parameter, indicating success or
faliure with cause. failure with cause.
An ASP MAY deregister 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 SG MUST response to each deregistration request in a message. The SGP MUST response 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 SG 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 establishment
of traffic between an SG and an ASP, where only one ASP is configured of traffic between an SGP and an ASP, where only one ASP is configured
within an AS (no backup). It is assumed that the SCTP association is within an AS (no backup). It is assumed that the SCTP association is
already set-up. already set-up.
SG 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)---->|
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 Interface
Identifier(s). Identifier(s).
SG 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--------|
|------ASPActive Ack----->| |------ASPActive Ack----->|
| | | |
|------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 establishment
of traffic between an SG and two ASPs in the same Application Server, of traffic between an SGP and two ASPs in the same Application Server,
where ASP1 is configured to be active and ASP2 to be standby in the event where ASP1 is configured to be active and ASP2 to be standby in the event
of communication failure or the withdrawal from service of ASP1. ASP2 MAY of communication failure or the withdrawal from service of ASP1. ASP2 MAY
act as a hot, warm, or cold standby depending on the extent to which ASP1 act as a hot, warm, or cold standby depending on the extent to which ASP1
and ASP2 share call/transaction state or can communicate call state under and ASP2 share call/transaction state or can communicate call state under
failure/withdrawal events. failure/withdrawal events.
SG 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)------------------>|
5.2 ASP Traffic Fail-over Examples 5.2 ASP Traffic Fail-over Examples
5.2.1 (1+1 Sparing, withdrawal of ASP, Back-up Over-ride) 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 from
service: service:
SG ASP1 ASP2 SGP ASP1 ASP2
| | | | | |
|<-----ASP Inactive-------| | |<-----ASP Inactive-------| |
|----ASP Inactive Ack---->| | |----ASP Inactive Ack---->| |
|--------------------NTFY(AS-Down) (Optional)------->| | | |
|------------------NTFY(AS-PENDING)----------------->|
| | | | | |
|<------------------------------ ASP Active----------| |<------------------------------ ASP Active----------|
|-----------------------------ASP Active Ack)------->| |-----------------------------ASP Active Ack-------->|
| | | | |
|------------------NTFY(AS-ACTIVE)------------------>|
| | |
In this case, the SG notifies ASP2 that the AS has moved to the In this case, the SGP notifies ASP2 that the AS has moved to the
AS-DOWN state. The SG could have also (optionally) sent a Notify AS-PENDING state. ASP2 sends ASP Active to bring the AS back to
message when the AS moved to the AS-PEND state. the AS-ACTIVE state. If ASP2 did not send the ASP Active message
before T(r) expired, the SGP would send a NOTIFY (AS-DOWN).
Note: If the SG 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 SG-ASP1 ASP Inactive message exchange of SCTP failure), the initial SGP-ASP1 ASP Inactive message exchange
would not occur. would not occur.
5.2.2 (1+1 Sparing, Back-up Over-ride) SGP ASP1 ASP2
| | |
(detects SCTP failure)
|------------------NTFY(AS-PENDING)----------------->|
| | |
|<------------------------------ ASP Active----------|
|-----------------------------ASP Active Ack-------->|
| | |
|------------------NTFY(AS-ACTIVE)------------------>|
| | |
Following on from the example in Section 5.1.2, and ASP2 wishes to over- 5.2.2 (1+1 Sparing, backup Override)
ride ASP1 and take over the traffic:
SG ASP1 ASP2 Following on from the example in Section 5.1.2, and ASP2 wishes to
override ASP1 and take over the traffic:
SGP ASP1 ASP2
| | | | | |
|<-------------------------------ASP Active----------| |<-------------------------------ASP Active----------|
|-----------------------------ASP Active Ack-------->| |-----------------------------ASP Active Ack-------->|
|----NTFY( Alt ASP-Act)-->| |----NTFY(Alt ASP-Act)--->| |
| (optional) | | | | |
In this case, the SG 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 SG 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 SG, it When the M2UA layer on the ASP has a MAUP message to send to the SGP, it
will do the following: will do the following:
- Determine the correct SG - Determine the correct SGP
- Find the SCTP association to the chosen SG - 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 SG, over the - Send the MAUP message to the remote M2UA peer in the SGP, over the
SCTP association SCTP association
When the M2UA layer on the SG 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, it
will do the following: 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
skipping to change at page 24, line 526 skipping to change at page 70, line 6
SCTP association 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 the
normal or emergency procedure. An example of the message flow to bring normal or emergency procedure. An example of the message flow to bring
a SS7 link in-service using the normal alignment procedure is shown a SS7 link in-service using the normal alignment procedure is shown
below. below.
MTP2 M2UA M2UA MTP3 MTP2 M2UA M2UA MTP3
SG SG 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 the
emergency alignment procedure. emergency alignment procedure.
MTP2 M2UA M2UA MTP3 MTP2 M2UA M2UA MTP3
SG SG 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
SG SG 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 SG can autonomously indicate that a SS7 link has gone out-of-service The SGP can autonomously indicate that a SS7 link has gone out-of-
as shown below. service as shown below.
MTP2 M2UA M2UA MTP3 MTP2 M2UA M2UA MTP3
SG SG 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
SG SG 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
SG SG 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 SG can indicate Remote has entered or exited the Processor Outage The SGP can indicate Remote has entered or exited the Processor Outage
condition. It uses the State Indication message as shown below. condition. It uses the State Indication message as shown below.
MTP2 M2UA M2UA MTP3 MTP2 M2UA M2UA MTP3
SG SG 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 Link Congestion 5.3.5 Notification of Link Congestion
The SG can indicate that a link has become congested. It uses the The SGP can indicate that a link has become congested. It uses the
Congestion Indication message as shown below. Congestion Indication message as shown below.
MTP2 M2UA M2UA MTP3 MTP2 M2UA M2UA MTP3
SG SG 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 retransmission
queue that needed to be retrieved. queue that needed to be retrieved.
MTP2 M2UA M2UA MTP3 MTP2 M2UA M2UA MTP3
SG SG 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)
<-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)
skipping to change at page 31, line 52 skipping to change at page 72, line 9
-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 number of
messages in the retransmit queue that have been requested. Only one messages in the retransmit queue that have been requested. Only one
Retrieval Complete Indication SHOULD be sent. 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 shown
below. below.
MTP2 M2UA M2UA MTP3 MTP2 M2UA M2UA MTP3
SG SG 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---
skipping to change at page 31, line 77 skipping to change at page 72, line 34
<-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
SG SG ASP ASP SGP SGP ASP ASP
<-Clr TB/RTB Req-|<-Rtrv Req (ACTION_DROP_MSGS)-|<--Clr TB/RTB Req--- <-Clr TB/RTB Req-|<-Rtrv Req (ACTION_DROP_MSGS)-|<--Clr TB/RTB Req---
-Clr TB/RTB Ind->|-Rtrv Cfm (ACTION_DROP_MSGS)->|---Clr TB/RTB Ind--> -Clr TB/RTB Ind->|-Rtrv Cfm (ACTION_DROP_MSGS)->|---Clr TB/RTB Ind-->
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
SG SG 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
SG SG 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 link.
The flows below show an example of the request and all the potential The flows below show an example of the request and all the potential
responses. 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
SG SG 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
SG SG 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
SG SG 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 Remote
Processor Outage. Processor Outage.
MTP2 M2UA M2UA MGMT MTP2 M2UA M2UA MGMT
SG SG 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--->
skipping to change at page 31, line 188 skipping to change at page 74, line 48
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
7.0 Security 7.0 Security
M2UA is designed to carry signaling 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:
skipping to change at page 32, line 65 skipping to change at page 76, line 18
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 information: Documentation of the message type MUST contain the following
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 field
within the message. within the message.
(d) A detailed procedural description of the use of the new message type (d) A detailed procedural description of the use of the new message
within the operation of the protocol. type within the operation of the protocol.
(e) A detailed description of error conditions when receiving this message (e) A detailed description of error conditions when receiving this
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 support,
it MUST respond with an Error (ERR) message with an Error Code of it MUST respond with an Error (ERR) message with an Error Code of
Unsupported Message Type. 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:
skipping to change at page 32, line 99 skipping to change at page 76, line 53
(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 Acknowledgements
The authors would like to thank John Loughney, Neil Olson, Michael The authors would like to thank John Loughney, Neil Olson, Michael
Tuexen, Nikhil Jain, Steve Lorusso, Dan Brendes, Joe Keller, Heinz Tuexen, Nikhil Jain, Steve Lorusso, Dan Brendes, Joe Keller, Heinz
Prantner, Barry Nagelberg, Naoto Makinae, Joyce Archibald and Mark Prantner, Barry Nagelberg, Naoto Makinae, Joyce Archibald, Mark
Kobine for their valuable comments and suggestions. Kobine, Nitin Tomar, Harsh Bhondwe and Karen King for their valuable
comments and suggestions.
10.0 References 10.0 References
[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 Signaling System Number 7', Volume 1, December 1995 of Signalling System Number 7', Volume 1, December 1995
[5] Stream Control Transmission Protocol, RFC 2960, October 2000 [5] Stream Control Transmission Protocol, RFC 2960, October 2000
[6] Architectural Framework for Signaling Transport, RFC 2719, [6] Architectural Framework for Signalling Transport, RFC 2719,
October 1999 October 1999
[7] ITU-T Recommendation Q.2140, 'B-ISDN ATM Adaptation Layer', February [7] ITU-T Recommendation Q.2140, 'B-ISDN ATM Adaptation Layer',
1995 February 1995
[8] ITU-T Recommendation Q.2210, 'Message transfer part level 3 [8] 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
[9] ITU-T Recommendation Q.751.1, 'Network Element Management Information [9] ITU-T Recommendation Q.751.1, 'Network Element Management
Model for the Messsage Transfer Part', October 1995 Information Model for the Message Transfer Part', October 1995
[10] Site Security Handbook, RFC 2196, September 1997 [10] Site Security Handbook, RFC 2196, September 1997
[11] Security Architecture for the Internet Protocol, RFC 2401 [11] Security Architecture for the Internet Protocol, RFC 2401
[12] SCTP Dynamic Addition of IP addresses, draft-ietf-tsvwg-addip- [12] SCTP Dynamic Addition of IP addresses, draft-ietf-tsvwg-addip-
sctp-00.txt, Work In Progress sctp-00.txt, Work In Progress
11.0 Author's Addresses 11.0 Author's Addresses
Ken Morneault Tel: +1-703-484-3323 Ken Morneault Tel: +1-703-484-3323
Cisco Systems Inc. EMail: kmorneau@cisco.com Cisco Systems Inc. EMail: kmorneau@cisco.com
13615 Dulles Technology Drive 13615 Dulles Technology Drive
Herndon, VA. 20171 Herndon, VA. 20171
USA USA
Ram Dantu, Ph.D. Tel +1-469-255-0716 Ram Dantu, Ph.D. Tel +1-214-291-1111
Cisco Systems EMail rdantu@cisco.com NetRake Corporation EMail rdantu@netrake.com
17919 Waterview 3000 Technology Drive
Dallas, TX 75252 Plano, TX 75074
USA USA
Greg Sidebottom Tel: +1-613-763-7305 Greg Sidebottom EMail: gregside@home.net
Nortel Networks EMail: gregside@nortelnetworks.com Kanata, Ontario
3685 Richmond Rd, Canada
Nepean, Ontario
Canada K2H5B7
Tom George Tel: +1-972-519-3168 Tom George Tel: +1-972-519-3168
Alcatel USA EMail: tom.george@usa.alcatel.com Alcatel USA EMail: tom.george@usa.alcatel.com
1000 Coit Road 1000 Coit Road
Plano, TX 74075 Plano, TX 74075
USA USA
Brian Bidulock Tel +1-972-839-4489 Brian Bidulock Tel +1-972-839-4489
OpenSS7 Project EMail: bidulock@openss7.org OpenSS7 Project EMail: bidulock@openss7.org
c/o #424, 4701 Preston Park Blvd. c/o #424, 4701 Preston Park Blvd.
Dallas, TX 75093 Plano, TX 75093
USA USA
Jacob Heitz Tek +1-510-747-2917 Jacob Heitz Tek +1-510-747-2917
Lucent Technologies Email: jheitz@lucent.com Lucent Technologies Email: jheitz@lucent.com
1701 Harbor Bay Parkway 1701 Harbor Bay Parkway
Alameda, CA, 94502 Alameda, CA, 94502
USA USA
This Internet Draft expires December 2001. This Internet Draft expires March 2002.
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/