draft-ietf-sigtran-m3ua-12.txt   rfc3332.txt 
Network Working Group Greg Sidebottom
INTERNET-DRAFT gregside consulting
Javier Pastor-Balbas, Ian Rytina
Ericsson
Guy Mousseau
Nortel Networks
Lyndon Ong
Ciena
Hanns Juergen Schwarzbauer
Siemens
Klaus Gradischnig
NeuStar
Ken Morneault
Cisco
Mallesh Kalla
Telcordia
Normand Glaude
Performance Technologies
Brian Bidulock
OpenSS7
John Loughney
Nokia
Expires in six months Feb 2002 Network Working Group G. Sidebottom
Request for Comments: 3332 Signatus Technologies
SS7 MTP3-User Adaptation Layer (M3UA) Category: Standards Track K. Morneault
<draft-ietf-sigtran-m3ua-12.txt> Cisco
J. Pastor-Balbas
Status of This Memo Ericsson
Editors
September 2002
This document is an Internet-Draft and is in full conformance with all Signaling System 7 (SS7) Message Transfer Part 3 (MTP3) -
provisions of Section 10 of RFC 2026. Internet-Drafts are working User Adaptation Layer (M3UA)
documents of the Internet Engineering Task Force (IETF), its areas, and
its working groups. Note that other groups may also distribute working
documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Status of this Memo
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference material
or to cite them other than as 'work in progress.'
The list of current Internet-Drafts can be accessed at This document specifies an Internet standards track protocol for the
http://www.ietf.org/1id-abstracts.html Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
The list of Internet-Draft Shadow Directories can be accessed at Copyright Notice
http://www.ietf.org/shadow.html
To learn the current status of any Internet-Draft, please check the Copyright (C) The Internet Society (2002). All Rights Reserved.
'1id-abstracts.txt' listing contained in the Internet- Drafts Shadow
Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe),
munnari.oz.au (Pacific Rim), ftp.ietf.org (US East Coast), or
ftp.isi.edu (US West Coast).
Abstract Abstract
This Internet Draft defines a protocol for supporting the transport of This memo defines a protocol for supporting the transport of any SS7
any SS7 MTP3-User signalling (e.g., ISUP and SCCP messages) over IP MTP3-User signalling (e.g., ISUP and SCCP messages) over IP using the
using the services of the Stream Control Transmission Protocol. Also, services of the Stream Control Transmission Protocol. Also,
provision is made for protocol elements that enable a seamless provision is made for protocol elements that enable a seamless
operation of the MTP3-User peers in the SS7 and IP domains. This operation of the MTP3-User peers in the SS7 and IP domains. This
protocol would be used between a Signalling Gateway (SG) and a Media protocol would be used between a Signalling Gateway (SG) and a Media
Gateway Controller (MGC) or IP-resident Database. It is assumed that Gateway Controller (MGC) or IP-resident Database, or between two
the SG receives SS7 signalling over a standard SS7 interface using the IP-based applications. It is assumed that the SG receives SS7
SS7 Message Transfer Part (MTP) to provide transport. signalling over a standard SS7 interface using the SS7 Message
Transfer Part (MTP) to provide transport.
TABLE OF CONTENTS Table of Contents
1. Introduction..................................................3
1.1 Scope.........................................................3
1.2 Terminology...................................................4
1.3 M3UA Overview.................................................6
1.4 Functional Areas.............................................10
1.5 Sample Configurations........................................18
1.6 Definition of M3UA Boundaries................................21
2. Conventions..................................................25
3. M3UA Protocol Elements.......................................25
3.1 Common Message Header........................................26
3.2 Variable Length Parameter....................................29
3.3 Transfer Messages............................................31
3.4 SS7 Signalling Network Management (SSNM) Messages............35
3.5 ASP State Maintenance (ASPSM) Messages.......................45
3.6 Routing Key Management (RKM) Messages........................48
3.7 ASP Traffic Maintenance (ASPTM) Messages.....................59
3.8 Management (MGMT) Messages...................................63
4. Procedures...................................................69
4.1 Procedures to Support the M3UA-User .........................69
4.2 Procedures to Support the Management of SCTP Associations ...70
4.3 AS and ASP State Maintenance.................................72
4.4 Routing Key Management Procedures............................87
4.5 Procedures to Support the Availability or Congestion Status
of SS7 Destination...........................................89
4.6 MTP3 Restart.................................................92
5. Examples of M3UA Procedures..................................93
5.1 Establishment of Association and Traffic
Between SGs and ASPs.........................................93
5.2 ASP traffic Failover Examples................................99
5.3 Normal Withdrawal of an ASP from an Application Server
and Teardown of an Association..............................100
5.4 M3UA/MTP3-User Boundary Examples............................101
5.5 Examples of IPSP communication..............................105
6. Security Considerations.....................................108
6.1 Introduction................................................108
6.2 Threats.....................................................108
6.3 Protecting Confidentiality..................................108
7. IANA Considerations.........................................109
7.1 SCTP Payload Protocol Identifier............................109
7.2 M3UA Port Number............................................109
7.3 M3UA Protocol Extensions....................................109
8. References...................................................111
8.1 Normative References........................................111
8.2 Informative References......................................111
9. Acknowledgements.............................................113
10. Document Contributors.......................................113
Appendix A......................................................114
A.1 Signalling Network Architecture.............................114
A.2 Redundancy Models...........................................117
Editors' Addresses..............................................119
Full Copyright Statement........................................120
1. Introduction.......................................................4
1.1 Scope.........................................................4
1.2 Terminology...................................................4
1.3 M3UA Overview.................................................6
1.4 Functional Areas.............................................10
1.5 Sample Configurations........................................16
1.6 Definition of M3UA Boundaries................................19
2. Conventions.......................................................24
3. M3UA Protocol Elements............................................24
3.1 Common Message Header........................................24
3.2 Variable Length Parameter....................................26
3.3 Transfer Messages............................................29
3.4 SS7 Signalling Network Management (SSNM) Messages............32
3.5 ASP State Maintenance (ASPM) Messages........................41
3.6 Routing Key Management (RKM) Messages........................44
3.7 ASP Traffic Maintenance (ASPTM) Messages.....................57
3.8 Management (MGMT) Messages...................................61
4. Procedures........................................................66
4.1 Procedures to Support the M3UA-User .........................66
4.2 Procedures to Support the Management of SCTP Associations ...69
4.3 AS and ASP State Maintenance.................................69
4.4 Routing Key Management Procedures............................81
4.5 Procedures to Support the Availability or Congestion Status
of SS7 Destination...........................................83
4.6 MTP3 Restart.................................................86
5. Examples of M3UA Procedures.......................................86
5.1 Establishment of Association and Traffic
Between SGs and ASPs.........................................86
5.2 ASP traffic Failover Examples................................91
5.3 Normal Withdrawal of an ASP from an Application Server
and Teardown of an Association...............................92
5.4 M3UA/MTP3-User Boundary Examples.............................93
6. Security Considerations...........................................97
6.1 Introduction.................................................97
6.2 Threats......................................................97
6.3 Protecting Confidentiality...................................98
7. IANA Considerations...............................................98
7.1 SCTP Payload Protocol Identifier.............................98
7.2 M3UA Port Number.............................................98
7.3 M3UA Protocol Extensions.....................................99
8. Acknowledgements.................................................100
9. References.......................................................100
9.1 Normative References........................................100
9.2 Informative References......................................100
11. Author's Addresses..............................................102
Appendix A..........................................................103
1. Introduction 1. Introduction
This draft defines a protocol for supporting the transport of This memo defines a protocol for supporting the transport of any SS7
any SS7 MTP3-User signalling (e.g., ISUP and SCCP messages) over IP MTP3-User signalling (e.g., ISUP and SCCP messages) over IP using the
using the services of the Stream Control Transmission Protocol [17]. services of the Stream Control Transmission Protocol [17]. Also,
Also, provision is made for protocol elements that enable a seamless provision is made for protocol elements that enable a seamless
operation of the MTP3-User peers in the SS7 and IP domains. This operation of the MTP3-User peers in the SS7 and IP domains. This
protocol would be used between a Signalling Gateway (SG) and a Media protocol would be used between a Signalling Gateway (SG) and a Media
Gateway Controller (MGC) or IP-resident Database [11]. Gaway Controller (MGC) or IP-resident Database [11], or between two
IP-based applications.
1.1 Scope 1.1 Scope
There is a need for Switched Circuit Network (SCN) signalling protocol There is a need for Switched Circuit Network (SCN) signalling
delivery from an SS7 Signalling Gateway (SG) to a Media Gateway protocol delivery from an SS7 Signalling Gateway (SG) to a Media
Controller (MGC) or IP-resident Database as described in the Framework Gateway Controller (MGC) or IP-resident Database as described in the
Architecture for Signalling Transport [11]. The delivery mechanism Framework Architecture for Signalling Transport [11]. The delivery
should meet the following criteria: mechanism should meet the following criteria:
* Support for the transfer of all SS7 MTP3-User Part messages (e.g., * Support for the transfer of all SS7 MTP3-User Part messages (e.g.,
ISUP [1,2,3], SCCP [4,5,6], TUP [12], etc.) ISUP [1,2,3], SCCP [4,5,6], TUP [12], etc.)
* Support for the seamless operation of MTP3-User protocol peers * Support for the seamless operation of MTP3-User protocol peers
* Support for the management of SCTP transport associations and * Support for the management of SCTP transport associations and
traffic between an SG and one or more MGCs or IP-resident Databases traffic between an SG and one or more MGCs or IP-resident
* Support for MGC or IP-resident Database process failover and load Databases
sharing * Support for MGC or IP-resident Database process failover and load
* Support for the asynchronous reporting of status changes to sharing
management * Support for the asynchronous reporting of status changes to
management
In simplistic transport terms, the SG will terminate SS7 MTP2 and MTP3 In simplistic transport terms, the SG will terminate SS7 MTP2 and
protocol layers [7,8,9] and deliver ISUP, SCCP and/or any other MTP3 protocol layers [7,8,9] and deliver ISUP, SCCP and/or any other
MTP3-User protocol messages, as well as certain MTP network management MTP3-User protocol messages, as well as certain MTP network
events, over SCTP transport associations to MTP3-User peers in MGCs or management events, over SCTP transport associations to MTP3-User
IP-resident Databases. peers in MGCs or IP-resident Databases.
1.2 Terminology 1.2 Terminology
Application Server (AS) - A logical entity serving a specific Routing Application Server (AS) - A logical entity serving a specific Routing
Key. An example of an Application Server is a virtual switch element Key. An example of an Application Server is a virtual switch element
handling all call processing for a unique range of PSTN trunks, handling all call processing for a unique range of PSTN trunks,
identified by an SS7 SIO/DPC/OPC/CIC_range. Another example is a identified by an SS7 SIO/DPC/OPC/CIC_range. Another example is a
virtual database element, handling all HLR transactions for a virtual database element, handling all HLR transactions for a
particular SS7 DPC/OPC/SCCP_SSN combination. The AS contains a set of particular SS7 DPC/OPC/SCCP_SSN combination. The AS contains a set
one or more unique Application Server Processes, of which one or more of one or more unique Application Server Processes, of which one or
is normally actively processing traffic. Note that there is a 1:1 more is normally actively processing traffic. Note that there is a
relationship between an AS and a Routing Key. 1:1 relationship between an AS and a Routing Key.
Application Server Process (ASP) - A process instance of an Application Application Server Process (ASP) - A process instance of an
Server. An Application Server Process serves as an active or backup Application Server. An Application Server Process serves as an active
process of an Application Server (e.g., part of a distributed virtual or backup process of an Application Server (e.g., part of a
switch or database). Examples of ASPs are processes (or process distributed virtual switch or database). Examples of ASPs are
instances) of MGCs, IP SCPs or IP HLRs. An ASP contains an SCTP processes (or process instances) of MGCs, IP SCPs or IP HLRs. An ASP
endpoint and may be configured to process signalling traffic within contains an SCTP endpoint and may be configured to process signalling
more than one Application Server. traffic within more than one Application Server.
Association - An association refers to an SCTP association. The Association - An association refers to an SCTP association. The
association provides the transport for the delivery of MTP3-User association provides the transport for the delivery of MTP3-User
protocol data units and M3UA adaptation layer peer messages. protocol data units and M3UA adaptation layer peer messages.
IP Server Process (IPSP) - A process instance of an IP-based IP Server Process (IPSP) - A process instance of an IP-based
application. An IPSP is essentially the same as an ASP, except that it application. An IPSP is essentially the same as an ASP, except that
uses M3UA in a point-to-point fashion. Conceptually, an IPSP does not it uses M3UA in a point-to-point fashion. Conceptually, an IPSP does
use the services of a Signalling Gateway node. not use the services of a Signalling Gateway node.
Failover - The capability to reroute signalling traffic as required Failover - The capability to reroute signalling traffic as required
to an alternate Application Server Process, or group of ASPs, within an to an alternate Application Server Process, or group of ASPs, within
Application Server in the event of failure or unavailability of a an Application Server in the event of failure or unavailability of a
currently used Application Server Process. Failover also applies upon currently used Application Server Process. Failover also applies
the return to service of a previously unavailable Application Server upon the return to service of a previously unavailable Application
Process. Server Process.
Host - The computing platform that the process (SGP, ASP or IPSP) is Host - The computing platform that the process (SGP, ASP or IPSP) is
running on. running on.
Layer Management - Layer Management is a nodal function that handles Layer Management - Layer Management is a nodal function that handles
the inputs and outputs between the M3UA layer and a local management the inputs and outputs between the M3UA layer and a local management
entity. entity.
Linkset - A number of signalling links that directly interconnect two Linkset - A number of signalling links that directly interconnect two
signalling points, which are used as a module. signalling points, which are used as a module.
MTP - The Message Transfer Part of the SS7 protocol. MTP - The Message Transfer Part of the SS7 protocol.
MTP3 - MTP Level 3, the signalling network layer of SS7 MTP3 - MTP Level 3, the signalling network layer of SS7
MTP3-User - Any protocol normally using the services of the SS7 MTP3 MTP3-User - Any protocol normally using the services of the SS7 MTP3
(e.g., ISUP, SCCP, TUP, etc.). (e.g., ISUP, SCCP, TUP, etc.).
Network Appearance - The Network Appearance is a M3UA local reference Network Appearance - The Network Appearance is a M3UA local reference
shared by SG and AS (typically an integer) that together with an shared by SG and AS (typically an integer) that together with an
Signaling Point Code uniquely identifies an SS7 node by indicating Signaling Point Code uniquely identifies an SS7 node by indicating
the specific SS7 network it belongs to. It can be used to distinguish the specific SS7 network it belongs to. It can be used to distinguish
between signalling traffic associated with different networks being between signalling traffic associated with different networks being
sent between the SG and the ASP over a common SCTP association. An sent between the SG and the ASP over a common SCTP association. An
example scenario is where an SG appears as an element in multiple example scenario is where an SG appears as an element in multiple
separate national SS7 networks and the same Signaling Point Code separate national SS7 networks and the same Signaling Point Code
value may be reused in different networks. value may be reused in different networks.
Network Byte Order: Most significant byte first, a.k.a Big Endian. Network Byte Order: Most significant byte first, a.k.a Big Endian.
Routing Key: A Routing Key describes a set of SS7 parameters and Routing Key: A Routing Key describes a set of SS7 parameters and
parameter values that uniquely define the range of signalling traffic parameter values that uniquely define the range of signalling traffic
to be handled by a particular Application Server. Parameters within the to be handled by a particular Application Server. Parameters within
Routing Key cannot extend across more than a single Signalling Point the Routing Key cannot extend across more than a single Signalling
Management Cluster. Point Management Cluster.
Routing Context - A value that uniquely identifies a Routing Key. Routing Context - A value that uniquely identifies a Routing Key.
Routing Context values are either configured using a configuration Routing Context values are either configured using a configuration
management interface, or by using the routing key management procedures management interface, or by using the routing key management
defined in this document. procedures defined in this document.
Signalling Gateway Process (SGP) - A process instance of a Signalling Signalling Gateway Process (SGP) - A process instance of a Signalling
Gateway. It serves as an active, backup, loadsharing or broadcast Gateway. It serves as an active, backup, load-sharing or broadcast
process of a Signalling Gateway. process of a Signalling Gateway.
Signalling Gateway - An SG is a signaling agent that receives/sends SCN Signalling Gateway - An SG is a signaling agent that receives/sends
native signaling at the edge of the IP network [11]. An SG appears to SCN native signaling at the edge of the IP network [11]. An SG
the SS7 network as an SS7 Signalling Point. An SG contains a set of appears to the SS7 network as an SS7 Signalling Point. An SG
one or more unique Signalling Gateway Processes, of which one or more contains a set of one or more unique Signalling Gateway Processes, of
is normally actively processing traffic. Where an SG contains more which one or more is normally actively processing traffic. Where an
than one SGP, the SG is a logical entity and the contained SGPs are SG contains more than one SGP, the SG is a logical entity and the
assumed to be coordinated into a single management view to the SS7 contained SGPs are assumed to be coordinated into a single management
network and to the supported Application Servers. view to the SS7 network and to the supported Application Servers.
Signalling Process - A process instance that uses M3UA to communicate Signalling Process - A process instance that uses M3UA to communicate
with other signalling processes. An ASP, an SGP and an IPSP are all with other signalling processes. An ASP, an SGP and an IPSP are all
signalling processes. signalling processes.
Signalling Point Management Cluster (SPMC) - The complete set of Signalling Point Management Cluster (SPMC) - The complete set of
Application Servers represented to the SS7 network under a single MTP Application Servers represented to the SS7 network under a single MTP
entity (Signalling Point) in one specific Network Appearance. SPMCs entity (Signalling Point) in one specific Network Appearance. SPMCs
are used to aggregate the availability, congestion, and user part status are used to aggregate the availability, congestion, and user part
of an MTP entity (Signalling Point) that is distributed in the IP status of an MTP entity (Signalling Point) that is distributed in the
domain, for the purpose of supporting MTP3 management procedures IP domain, for the purpose of supporting MTP3 management procedures
towards the SS7 network. In some cases, the SG itself may also be a towards the SS7 network. In some cases, the SG itself may also be a
member of the SPMC. In this case, the SG availability /congestion member of the SPMC. In this case, the SG availability /congestion
/User_Part status should also be taken into account when considering any /User_Part status should also be taken into account when considering
supporting MTP3 management actions. any supporting MTP3 management actions.
Stream - A stream refers to an SCTP stream; a unidirectional logical Stream - A stream refers to an SCTP stream; a unidirectional logical
channel established from one SCTP endpoint to another associated SCTP channel established from one SCTP endpoint to another associated SCTP
endpoint, within which all user messages are delivered in-sequence endpoint, within which all user messages are delivered in-sequence
except for those submitted to the unordered delivery service. except for those submitted to the unordered delivery service.
1.3 M3UA Overview 1.3 M3UA Overview
1.3.1 Protocol Architecture. 1.3.1 Protocol Architecture
The framework architecture that has been defined for SCN signalling The framework architecture that has been defined for SCN signalling
transport over IP [11] uses multiple components, including a common transport over IP [11] uses multiple components, including a common
signalling transport protocol and an adaptation module to support the signalling transport protocol and an adaptation module to support the
services expected by a particular SCN signalling protocol from its services expected by a particular SCN signalling protocol from its
underlying protocol layer. underlying protocol layer.
Within the framework architecture, this document defines an MTP3-User Within the framework architecture, this document defines an MTP3-User
adaptation module suitable for supporting the transfer of messages of adaptation module suitable for supporting the transfer of messages of
any protocol layer that is identified to the MTP Level 3 as an MTP any protocol layer that is identified to the MTP Level 3 as an MTP
User. The list of these protocol layers includes, but is not limited User. The list of these protocol layers includes, but is not limited
to, ISDN User Part (ISUP) [1,2,3], Signalling Connection Control Part to, ISDN User Part (ISUP) [1,2,3], Signalling Connection Control Part
(SCCP) [4,5,6] and Telephone User Part (TUP) [12]. TCAP [13,14,15] or (SCCP) [4,5,6] and Telephone User Part (TUP) [12]. TCAP [13,14,15]
RANAP [16] messages are transferred transparently by the M3UA protocol or RANAP [16] messages are transferred transparently by the M3UA
as SCCP payload, as they are SCCP-User protocols. protocol as SCCP payload, as they are SCCP-User protocols.
It is recommended that M3UA use the services of the Stream Control It is recommended that M3UA use the services of the Stream Control
Transmission Protocol (SCTP) [17] as the underlying reliable common Transmission Protocol (SCTP) [17] as the underlying reliable common
signalling transport protocol. This is to take advantage of various signalling transport protocol. This is to take advantage of various
SCTP features such as: SCTP features such as:
- 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.
Under certain scenarios, such as back-to-back connections without Under certain scenarios, such as back-to-back connections without
redundancy requirements, the SCTP functions above might not be a redundancy requirements, the SCTP functions above might not be a
requirement and TCP MAY be used as the underlying common transport requirement and TCP MAY be used as the underlying common transport
protocol. protocol.
1.3.2 Services Provided by the M3UA Layer 1.3.2 Services Provided by the M3UA Layer
The M3UA Layer at an ASP or IPSP provides the equivalent set of The M3UA Layer at an ASP or IPSP provides the equivalent set of
primitives at its upper layer to the MTP3-Users as provided by the MTP primitives at its upper layer to the MTP3-Users as provided by the
Level 3 to its local MTP3-Users at an SS7 SEP. In this way, the ISUP MTP Level 3 to its local MTP3-Users at an SS7 SEP. In this way, the
and/or SCCP layer at an ASP or IPSP is unaware that the expected MTP3 ISUP and/or SCCP layer at an ASP or IPSP is unaware that the expected
services are offered remotely from an MTP3 Layer at an SGP, and not by MTP3 services are offered remotely from an MTP3 Layer at an SGP, and
a local MTP3 layer. The MTP3 layer at an SGP may also be unaware that not by a local MTP3 layer. The MTP3 layer at an SGP may also be
its local users are actually remote user parts over M3UA. In effect, unaware that its local users are actually remote user parts over
the M3UA extends access to the MTP3 layer services to a remote IP-based M3UA. In effect, the M3UA extends access to the MTP3 layer services
application. The M3UA layer does not itself provide the MTP3 services. to a remote IP-based application. The M3UA layer does not itself
However, in the case where an ASP is connected to more than one SG, provide the MTP3 services. However, in the case where an ASP is
the M3UA layer at an ASP should maintain the status of configured SS7 connected to more than one SG, the M3UA layer at an ASP should
destinations and route messages according to the availability and maintain the status of configured SS7 destinations and route messages
congestion status of the routes to these destinations via each SG. according to the availability and congestion status of the routes to
these destinations via each SG.
The M3UA layer may also be used for point-to-point signalling between The M3UA layer may also be used for point-to-point signalling between
two IP Server Processes (IPSPs). In this case, the M3UA layer provides two IP Server Processes (IPSPs). In this case, the M3UA layer
the same set of primitives and services at its upper layer as the MTP3. provides the same set of primitives and services at its upper layer
However, in this case the expected MTP3 services are not offered as the MTP3. However, in this case the expected MTP3 services are not
remotely from an SGP. The MTP3 services are provided but the offered remotely from an SGP. The MTP3 services are provided but the
procedures to support these services are a subset of the MTP3 procedures to support these services are a subset of the MTP3
procedures due to the simplified point-to-point nature of the IPSP to procedures due to the simplified point-to-point nature of the IPSP to
IPSP relationship. IPSP relationship.
1.3.2.1 Support for the Transport of MTP3-User Messages 1.3.2.1 Support for the Transport of MTP3-User Messages
The M3UA layer provides the transport of MTP-TRANSFER primitives across The M3UA layer provides the transport of MTP-TRANSFER primitives
an established SCTP association between an SGP and an ASP or between across an established SCTP association between an SGP and an ASP or
IPSPs. between IPSPs.
At an ASP, in the case where a destination is reachable via multiple At an ASP, in the case where a destination is reachable via multiple
SGPs, the M3UA layer must also choose via which SGP the message is to SGPs, the M3UA layer must also choose via which SGP the message is to
be routed or support load balancing across the SGPs, minimizing be routed or support load balancing across the SGPs, minimizing
missequencing. missequencing.
The M3UA layer does not impose a 272-octet signalling information field The M3UA layer does not impose a 272-octet signalling information
(SIF) length limit as specified by the SS7 MTP Level 2 protocol [7,8,9]. field (SIF) length limit as specified by the SS7 MTP Level 2 protocol
Larger information blocks can be accommodated directly by M3UA/SCTP, [7,8,9]. Larger information blocks can be accommodated directly by
without the need for an upper layer segmentation/reassembly procedure as M3UA/SCTP, without the need for an upper layer segmentation/re-
specified in recent SCCP or ISUP versions. However, in the context of assembly procedure as specified in recent SCCP or ISUP versions.
an SG, the maximum 272-octet block size must be followed when However, in the context of an SG, the maximum 272-octet block size
interworking to a SS7 network that does not support the transfer of must be followed when interworking to a SS7 network that does not
larger information blocks to the final destination. This avoids support the transfer of larger information blocks to the final
potential ISUP or SCCP fragmentation requirements at the SGPs. The destination. This avoids potential ISUP or SCCP fragmentation
provisioning and configuration of the SS7 network determines the requirements at the SGPs. The provisioning and configuration of the
restriction placed on the maximum block size. Some configurations SS7 network determines the restriction placed on the maximum block
(e.g., Broadband MTP [21]) may permit larger block sizes. size. Some configurations (e.g., Broadband MTP [21]) may permit
larger block sizes.
1.3.2.2 Native Management Functions 1.3.2.2 Native Management Functions
The M3UA layer provides the capability to indicate errors associated The M3UA layer provides the capability to indicate errors associated
with received M3UA messages and to notify, as appropriate, local with received M3UA messages and to notify, as appropriate, local
management and/or the peer M3UA. management and/or the peer M3UA.
1.3.2.3 Interworking with MTP3 Network Management Functions 1.3.2.3 Interworking with MTP3 Network Management Functions
At the SGP, the M3UA layer provides interworking with MTP3 At the SGP, the M3UA layer provides interworking with MTP3 management
management functions to support seamless operation of the user SCN functions to support seamless operation of the user SCN signalling
signalling applications in the SS7 and IP domains. This includes: applications in the SS7 and IP domains. This includes:
- Providing an indication to MTP3-Users at an ASP that a destination - Providing an indication to MTP3-Users at an ASP that a destination
in the SS7 network is not reachable. in the SS7 network is not reachable.
- Providing an indication to MTP3-Users at an ASP that a destination - Providing an indication to MTP3-Users at an ASP that a destination
in the SS7 network is now reachable. in the SS7 network is now reachable.
- Providing an indication to MTP3-Users at an ASP that messages to a - Providing an indication to MTP3-Users at an ASP that messages to a
destination in the SS7 network are experiencing SS7 congestion. destination in the SS7 network are experiencing SS7 congestion.
- Providing an indication to the M3UA layer at an ASP that the routes - Providing an indication to the M3UA layer at an ASP that the routes
to a destination in the SS7 network are restricted. to a destination in the SS7 network are restricted.
- Providing an indication to MTP3-Users at an ASP that a MTP3-User - Providing an indication to MTP3-Users at an ASP that a MTP3-User
peer is unavailable. peer is unavailable.
The M3UA layer at an ASP keeps the state of the routes to remote SS7 The M3UA layer at an ASP keeps the state of the routes to remote SS7
destinations and may initiate an audit of the availability, the destinations and may initiate an audit of the availability, the
restricted or the congested state of remote SS7 destinations. This restricted or the congested state of remote SS7 destinations. This
information is requested from the M3UA layer at the SGP. information is requested from the M3UA layer at the SGP.
The M3UA layer at an ASP may also indicate to the SG that the M3UA The M3UA layer at an ASP may also indicate to the SG that the M3UA
layer itself or the ASP or the ASP's Host is congested. layer itself or the ASP or the ASP's Host is congested.
1.3.2.4 Support for the Management of SCTP Associations between the SGP 1.3.2.4 Support for the Management of SCTP Associations between the SGP
and ASPs. and ASPs.
The M3UA layer at the SGP maintains the availability state of all The M3UA layer at the SGP maintains the availability state of all
configured remote ASPs, to manage the SCTP Associations and configured remote ASPs, to manage the SCTP Associations and the
the traffic between the M3UA peers. As well, the active/inactive and traffic between the M3UA peers. As well, the active/inactive and
congestion state of remote ASPs is maintained. congestion state of remote ASPs is maintained.
The M3UA layer MAY be instructed by local management to establish an The M3UA layer MAY be instructed by local management to establish an
SCTP association to a peer M3UA node. This can be achieved using the SCTP association to a peer M3UA node. This can be achieved using the
M-SCTP_ESTABLISH primitives (See Section 1.6.3 for a description of M-SCTP_ESTABLISH primitives (See Section 1.6.3 for a description of
management primitives) to request, indicate and confirm the management primitives.) to request, indicate and confirm the
establishment of an SCTP association with a peer M3UA node. In order establishment of an SCTP association with a peer M3UA node. In order
to avoid redundant SCTP associations between two M3UA peers, one side to avoid redundant SCTP associations between two M3UA peers, one side
(client) SHOULD be designated to establish the SCTP association, or (client) SHOULD be designated to establish the SCTP association, or
M3UA configuration information maintained to detect redundant M3UA configuration information maintained to detect redundant
associations (e.g., via knowledge of the expected local and remote SCTP associations (e.g., via knowledge of the expected local and remote
endpoint addresses). SCTP endpoint addresses).
Local management MAY request from the M3UA layer the status of the Local management MAY request from the M3UA layer the status of the
underlying SCTP associations using the M-SCTP_STATUS request and underlying SCTP associations using the M-SCTP_STATUS request and
confirm primitives. Also, the M3UA MAY autonomously inform local confirm primitives. Also, the M3UA MAY autonomously inform local
management of the reason for the release of an SCTP association, management of the reason for the release of an SCTP association,
determined either locally within the M3UA layer or by a primitive from determined either locally within the M3UA layer or by a primitive
the SCTP. from the SCTP.
Also the M3UA layer MAY inform the local management of the change in Also the M3UA layer MAY inform the local management of the change in
status of an ASP or AS. This MAY be achieved using the M-ASP_STATUS status of an ASP or AS. This MAY be achieved using the M-ASP_STATUS
request or M-AS_STATUS request primitives. request or M-AS_STATUS request primitives.
1.3.2.5 Support for the Management of Connections to Multiple SGPs 1.3.2.5 Support for the Management of Connections to Multiple SGPs
As shown in Figure 1 an ASP may be connected to multiple SGPs. In such As shown in Figure 1 an ASP may be connected to multiple SGPs. In
a case a particular SS7 destination may be reachable via more than one such a case a particular SS7 destination may be reachable via more
SGP and/or SG, i.e., via more than one route. As MTP3 users only than one SGP and/or SG, i.e., via more than one route. As MTP3 users
maintain status on a destination and not on a route basis, the M3UA only maintain status on a destination and not on a route basis, the
layer must maintain the status (availability, restriction, and/or M3UA layer must maintain the status (availability, restriction,
congestion of route to destination) of the individual routes, derive and/or congestion of route to destination) of the individual routes,
the overall availability or congestion status of the destination derive the overall availability or congestion status of the
from the status of the individual routes, and inform the MTP3 users destination from the status of the individual routes, and inform the
of this derived status whenever it changes. MTP3 users of this derived status whenever it changes.
1.4 Functional Areas 1.4 Functional Areas
1.4.1 Signalling Point Code Representation 1.4.1 Signalling Point Code Representation
For example, within an SS7 network, a Signalling Gateway might be For example, within an SS7 network, a Signalling Gateway might be
charged with representing a set of nodes in the IP domain into the SS7 charged with representing a set of nodes in the IP domain into the
network for routing purposes. The SG itself, as a signalling point in SS7 network for routing purposes. The SG itself, as a signalling
the SS7 network, might also be addressable with an SS7 Point Code for point in the SS7 network, might also be addressable with an SS7 Point
MTP3 Management purposes. The SG Point Code might also be used for Code for MTP3 Management purposes. The SG Point Code might also be
addressing any local MTP3-Users at the SG such as a local SCCP layer. used for addressing any local MTP3-Users at the SG such as a local
SCCP layer.
An SG may be logically partitioned to operate in multiple SS7 network An SG may be logically partitioned to operate in multiple SS7 network
appearances. In such a case, the SG could be addressable with a Point appearances. In such a case, the SG could be addressable with a
Code in each network appearance, and represents a set of nodes in the Point Code in each network appearance, and represents a set of nodes
IP domain into each SS7 network. Alias Point Codes [8] may also be in the IP domain into each SS7 network. Alias Point Codes [8] may
used within an SG network appearance. also be used within an SG network appearance.
Where an SG contains more than one SGP, the MTP3 routeset, SPMC and Where an SG contains more than one SGP, the MTP3 routeset, SPMC and
remote AS/ASP states of each SGP SHOULD be coordinated across all the remote AS/ASP states of each SGP SHOULD be coordinated across all the
SGPs. Rerouting of traffic between the SGPs MAY also be supported. SGPs. Rerouting of traffic between the SGPs MAY also be supported.
Application Servers can be represented under the same Point Application Servers can be represented under the same Point Code of
Code of the SG, their own individual Point Codes or grouped with other the SG, their own individual Point Codes or grouped with other
Application Servers for Point Code preservation purposes. A single Application Servers for Point Code preservation purposes. A single
Point Code may be used to represent the SG and all the Application Point Code may be used to represent the SG and all the Application
Servers together, if desired. Servers together, if desired.
If an ASP or group of ASPs is available to the SS7 network via more If an ASP or group of ASPs is available to the SS7 network via more
than one SG, each with its own Point Code, the ASP(s) will typically be than one SG, each with its own Point Code, the ASP(s) will typically
represented by a Point Code that is separate from any SG Point Code. be represented by a Point Code that is separate from any SG Point
This allows, for example, these SGs to be viewed from the SS7 network Code. This allows, for example, these SGs to be viewed from the SS7
as "STPs", each having an ongoing "route" to the same ASP(s). Under network as "STPs", each having an ongoing "route" to the same ASP(s).
failure conditions where the ASP(s) become(s) unavailable from one of Under failure conditions where the ASP(s) become(s) unavailable from
the SGs, this approach enables MTP3 route management messaging between one of the SGs, this approach enables MTP3 route management messaging
the SG and SS7 network, allowing simple SS7 rerouting through an between the SG and SS7 network, allowing simple SS7 rerouting through
alternate SG without changing the Destination Point Code Address of SS7 an alternate SG without changing the Destination Point Code Address
traffic to the ASP(s). of SS7 traffic to the ASP(s).
Where a particular AS can be reached via more than one SGP, the Where a particular AS can be reached via more than one SGP, the
corresponding Routing Keys in the SGPs should be identical. (Note: corresponding Routing Keys in the SGPs should be identical. (Note:
It is possible for the SGP Routing Key configuration data to be It is possible for the SGP Routing Key configuration data to be
temporarily out-of-sync during configuration updates). temporarily out-of-sync during configuration updates).
+--------+ +--------+
| | | |
+------------+ SG 1 +--------------+ +------------+ SG 1 +--------------+
+-------+ | SS7 links | "STP" | IP network | ---- +-------+ | SS7 links | "STP" | IP network | ----
| SEP +---+ +--------+ +---/ \ | SEP +---+ +--------+ +---/ \
| or | |* | ASPs | | or | |* | ASPs |
| STP +---+ +--------+ +---\ / | STP +---+ +--------+ +---\ /
+-------+ | | | | ---- +-------+ | | | | ----
+------------+ SG 2 +--------------+ +------------+ SG 2 +--------------+
| "STP" | | "STP" |
+--------+ +--------+
* Note:. SG-to-SG communication (i.e., "C-links") is recommended for Figure 1 Example with mated SGs
carrier grade networks, using an MTP3 linkset or an equivalent, to
allow rerouting between the SGs in the event of route failures.
Where SGPs are used, inter-SGP communication might be used. Inter-SGP
protocol is outside of the scope of this document.
The following example shows a signalling gateway partitioned into two * Note:. SG-to-SG communication (i.e., "C-links") is recommended for
network appearances. carrier grade networks, using an MTP3 linkset or an equivalent, to
allow rerouting between the SGs in the event of route failures. Where
SGPs are used, inter-SGP communication might be used. Inter-SGP
protocol is outside of the scope of this document.
SG The following example shows a signalling gateway partitioned into two
+-------+ +---------------+ network appearances.
| SEP +--------------| SS7 Ntwk |M3UA| ----
+-------+ SS7 links | "A" | | / \ SG
|__________| +-----------+ ASPs | +-------+ +---------------+
| | | \ / | SEP +--------------| SS7 Ntwk |M3UA| ----
+-------+ | SS7 Ntwk | | ---- +-------+ SS7 links | "A" | | / \
| SEP +--------------+ "B" | | |__________| +-----------+ ASPs |
+-------+ +---------------+ | | | \ /
+-------+ | SS7 Ntwk | | ----
| SEP +--------------+ "B" | |
+-------+ +---------------+
Figure 2 Example with multiple Network
1.4.2 Routing Contexts and Routing Keys 1.4.2 Routing Contexts and Routing Keys
1.4.2.1 Overview 1.4.2.1 Overview
The distribution of SS7 messages between the SGP and the Application The distribution of SS7 messages between the SGP and the Application
Servers is determined by the Routing Keys and their associated Routing Servers is determined by the Routing Keys and their associated
Contexts. A Routing Key is essentially a set of SS7 parameters used to Routing Contexts. A Routing Key is essentially a set of SS7
filter SS7 messages, whereas the Routing Context parameter is a 4-byte parameters used to filter SS7 messages, whereas the Routing Context
value (integer) that is associated to that Routing Key in a 1:1 parameter is a 4-byte value (integer) that is associated to that
relationship. The Routing Context therefore can be viewed as an index Routing Key in a 1:1 relationship. The Routing Context therefore can
into a sending node's Message Distribution Table containing the Routing be viewed as an index into a sending node's Message Distribution
Key entries. Table containing the Routing Key entries.
Possible SS7 address/routing information that comprise a Routing Key Possible SS7 address/routing information that comprise a Routing Key
entry includes, for example, the OPC, DPC, SIO found in the MTP3 entry includes, for example, the OPC, DPC, SIO found in the MTP3
routing label, or MTP3-User specific fields (such as the ISUP CIC, SCCP routing label, or MTP3-User specific fields (such as the ISUP CIC,
subsystem number). Some example Routing Keys are: the DPC alone, the SCCP subsystem number). Some example Routing Keys are: the DPC
DPC/OPC combination, the DPC/OPC/CIC combination, or the DPC/SSN alone, the DPC/OPC combination, the DPC/OPC/CIC combination, or the
combination. The particular information used to define an M3UA DPC/SSN combination. The particular information used to define an
Routing Key is application and network dependent, and none of the M3UA Routing Key is application and network dependent, and none of
above examples are mandated. the above examples are mandated.
An Application Server Process may be configured to process signalling An Application Server Process may be configured to process signalling
traffic related to more than one Application Server, over a single SCTP traffic related to more than one Application Server, over a single
Association. In ASP Active and ASP Inactive management messages, the SCTP Association. In ASP Active and ASP Inactive management
signalling traffic to be started or stopped is discriminated by the messages, the signalling traffic to be started or stopped is
Routing Context parameter. At an ASP, the Routing Context parameter discriminated by the Routing Context parameter. At an ASP, the
uniquely identifies the range of signalling traffic associated with Routing Context parameter uniquely identifies the range of signalling
each Application Server that the ASP is configured to receive. traffic associated with each Application Server that the ASP is
configured to receive.
1.4.2.2 Routing Key Limitations 1.4.2.2 Routing Key Limitations
Routing Keys SHOULD be unique in the sense that each received SS7 Routing Keys SHOULD be unique in the sense that each received SS7
signalling message SHOULD have a full or partial match to a single signalling message SHOULD have a full or partial match to a single
routing result. It is not necessary for the parameter range values routing result. It is not necessary for the parameter range values
within a particular Routing Key to be contiguous. For example, an within a particular Routing Key to be contiguous. For example, an AS
AS could be configured to support call processing for multiple ranges could be configured to support call processing for multiple ranges of
of PSTN trunks that are not represented by contiguous CIC values. PSTN trunks that are not represented by contiguous CIC values.
1.4.2.3 Managing Routing Contexts and Routing Keys 1.4.2.3 Managing Routing Contexts and Routing Keys
There are two ways to provision a Routing Key at an SGP. A Routing Key There are two ways to provision a Routing Key at an SGP. A Routing
may be configured statically using an implementation dependent Key may be configured statically using an implementation dependent
management interface, or dynamically using the M3UA Routing Key management interface, or dynamically using the M3UA Routing Key
registration procedure. registration procedure.
When using a management interface to configure Routing Keys, the When using a management interface to configure Routing Keys, the
message distribution function within the SGP is not limited to the set message distribution function within the SGP is not limited to the
of parameters defined in this document. Other implementation dependent set of parameters defined in this document. Other implementation
distribution algorithms may be used. dependent distribution algorithms may be used.
1.4.2.4 Message Distribution at the SGP 1.4.2.4 Message Distribution at the SGP
To direct messages received from the SS7 MTP3 network to the To direct messages received from the SS7 MTP3 network to the
appropriate IP destination, the SGP must perform a message distribution appropriate IP destination, the SGP must perform a message
function using information from the received MTP3-User message. distribution function using information from the received MTP3-User
message.
To support this message distribution, the SGP might, for example, To support this message distribution, the SGP might, for example,
maintain the equivalent of a network address translation table, mapping maintain the equivalent of a network address translation table,
incoming SS7 message information to an Application Server for a mapping incoming SS7 message information to an Application Server for
particular application and range of traffic. This could be accomplished a particular application and range of traffic. This could be
by comparing elements of the incoming SS7 message to accomplished by comparing elements of the incoming SS7 message to
currently defined Routing Keys in the SGP. currently defined Routing Keys in the SGP.
These Routing Keys could in turn map directly to an Application Server These Routing Keys could in turn map directly to an Application
that is enabled by one or more ASPs. These ASPs provide dynamic status Server that is enabled by one or more ASPs. These ASPs provide
information regarding their availability, traffic handling capability dynamic status information regarding their availability, traffic
and congestion to the SGP using various management messages defined in handling capability and congestion to the SGP using various
the M3UA protocol. management messages defined in the M3UA protocol.
The list of ASPs in an AS is assumed to be dynamic, taking into account The list of ASPs in an AS is assumed to be dynamic, taking into
the availability, traffic handling capability and congestion status of account the availability, traffic handling capability and congestion
the individual ASPs in the list, as well as configuration changes and status of the individual ASPs in the list, as well as configuration
possible failover mechanisms. changes and possible failover mechanisms.
Normally, one or more ASPs are active (i.e., currently processing Normally, one or more ASPs are active (i.e., currently processing
traffic) in the AS but in certain failure and transition cases it is traffic) in the AS but in certain failure and transition cases it is
possible that there may be no active ASP available. Broadcast, possible that there may be no active ASP available. Broadcast,
loadsharing and backup scenarios are supported. loadsharing and backup scenarios are supported.
When there is no matching Routing Key entry for an incoming SS7 When there is no matching Routing Key entry for an incoming SS7
message, a default treatment MAY be specified. Possible solutions are message, a default treatment MAY be specified. Possible solutions
to provide a default Application Server at the SGP that directs all are to provide a default Application Server at the SGP that directs
unallocated traffic to a (set of) default ASP(s), or to drop the all unallocated traffic to a (set of) default ASP(s), or to drop the
message and provide a notification to layer management. The treatment message and provide a notification to layer management. The
of unallocated traffic is implementation dependent. treatment of unallocated traffic is implementation dependent.
1.4.2.5 Message Distribution at the ASP 1.4.2.5 Message Distribution at the ASP
The ASP must choose an SGP to direct a message to the SS7 network. The ASP must choose an SGP to direct a message to the SS7 network.
This is accomplished by observing the Destination Point Code (and This is accomplished by observing the Destination Point Code (and
possibly other elements of the outgoing message such as the SLS value). possibly other elements of the outgoing message such as the SLS
The ASP must also take into account whether the related Routing Context value). The ASP must also take into account whether the related
is active or not (See Section 4.3.4.3). Routing Context is active or not (See Section 4.3.4.3).
Implementation Note: Where more than one route (or SGP) is possible for Implementation Note: Where more than one route (or SGP) is possible
routing to the SS7 network, the ASP could, for example, maintain a for routing to the SS7 network, the ASP could, for example, maintain
dynamic table of available SGP routes for the SS7 destinations, taking a dynamic table of available SGP routes for the SS7 destinations,
into account the SS7 destination availability/restricted/congestion taking into account the SS7 destination
status received from the SGP(s), the availability status of the availability/restricted/congestion status received from the SGP(s),
individual SGPs and configuration changes and failover mechanisms. There the availability status of the individual SGPs and configuration
is, however, no M3UA messaging to manage the status of an SGP (e.g., changes and failover mechanisms. There is, however, no M3UA messaging
SGP-Up/Down/Active/Inactive messaging). to manage the status of an SGP (e.g., SGP-Up/Down/Active/Inactive
messaging).
Whenever an SCTP association to an SGP exists, the SGP is assumed to Whenever an SCTP association to an SGP exists, the SGP is assumed to
be ready for the purposes of responding to M3UA ASPSM messages (Refer be ready for the purposes of responding to M3UA ASPSM messages (Refer
to Section 3). to Section 3).
1.4.3 SS7 and M3UA Interworking 1.4.3 SS7 and M3UA Interworking
In the case of SS7 and M3UA interworking, the M3UA adaptation layer is In the case of SS7 and M3UA interworking, the M3UA adaptation layer
designed to provide an extension of the MTP3 defined user primitives. is designed to provide an extension of the MTP3 defined user
primitives.
1.4.3.1 Signalling Gateway SS7 Layers 1.4.3.1 Signalling Gateway SS7 Layers
The SG is responsible for terminating MTP Level 3 of the SS7 protocol, The SG is responsible for terminating MTP Level 3 of the SS7
and offering an IP-based extension to its users. protocol, and offering an IP-based extension to its users.
>From an SS7 perspective, it is expected that the Signalling Gateway From an SS7 perspective, it is expected that the Signalling Gateway
transmits and receives SS7 Message Signalling Units (MSUs) to and transmits and receives SS7 Message Signalling Units (MSUs) to and
from the PSTN over a standard SS7 network interface, using the SS7 from the PSTN over a standard SS7 network interface, using the SS7
Message Transfer Part (MTP) [7,8,9] to provide reliable transport of Message Transfer Part (MTP) [7,8,9] to provide reliable transport of
the messages. the messages.
As a standard SS7 network interface, the use of MTP Level 2 signalling As a standard SS7 network interface, the use of MTP Level 2
links is not the only possibility. ATM-based High Speed Links can also signalling links is not the only possibility. ATM-based High Speed
be used with the services of the Signalling ATM Adaptation Layer (SAAL) Links can also be used with the services of the Signalling ATM
[18,19]. Adaptation Layer (SAAL) [18,19].
Note: It is also possible for IP-based interfaces to be present, using Note: It is also possible for IP-based interfaces to be present,
the services of the MTP2-User Adaptation Layer (M2UA) [27] or M2PA [28]. using the services of the MTP2-User Adaptation Layer (M2UA) [27] or
M2PA [28].
These could be terminated at a Signalling Transfer Point (STP) or These could be terminated at a Signalling Transfer Point (STP) or
Signalling End Point (SEP). Using the services of MTP3, the SG could Signalling End Point (SEP). Using the services of MTP3, the SG could
be capable of communicating with remote SS7 SEPs in a quasi-associated be capable of communicating with remote SS7 SEPs in a quasi-
fashion, where STPs may be present in the SS7 path between the SEP and associated fashion, where STPs may be present in the SS7 path between
the SG. the SEP and the SG.
1.4.3.2 SS7 and M3UA Interworking at the SG 1.4.3.2 SS7 and M3UA Interworking at the SG
The SGP provides a functional interworking of transport functions The SGP provides a functional interworking of transport functions
between the SS7 network and the IP network by also supporting the M3UA between the SS7 network and the IP network by also supporting the
adaptation layer. It allows the transfer of MTP3-User signalling M3UA adaptation layer. It allows the transfer of MTP3-User
messages to and from an IP-based Application Server Process where the signalling messages to and from an IP-based Application Server
peer MTP3-User protocol layer exists. Process where the peer MTP3-User protocol layer exists.
For SS7 user part management, it is required that the MTP3-User For SS7 user part management, it is required that the MTP3-User
protocols at ASPs receive indications of SS7 signalling point protocols at ASPs receive indications of SS7 signalling point
availability, SS7 network congestion, and remote User Part availability, SS7 network congestion, and remote User Part
unavailability as would be expected in an SS7 SEP node. To accomplish unavailability as would be expected in an SS7 SEP node. To
this, the MTP-PAUSE, MTP-RESUME and MTP-STATUS indication primitives accomplish this, the MTP-PAUSE, MTP-RESUME and MTP-STATUS indication
received at the MTP3 upper layer interface at the SG need to be primitives received at the MTP3 upper layer interface at the SG need
propagated to the remote MTP3-User lower layer interface at the ASP. to be propagated to the remote MTP3-User lower layer interface at the
ASP.
MTP3 management messages (such as TFPs or TFAs received from the SS7 MTP3 management messages (such as TFPs or TFAs received from the SS7
network) MUST NOT be encapsulated as Data message Payload Data and sent network) MUST NOT be encapsulated as Data message Payload Data and
either from SG to ASP or from ASP to SG. The SG MUST terminate these sent either from SG to ASP or from ASP to SG. The SG MUST terminate
messages and generate M3UA messages as appropriate. these messages and generate M3UA messages as appropriate.
1.4.3.3 Application Server 1.4.3.3 Application Server
A cluster of application servers is responsible for providing the A cluster of application servers is responsible for providing the
overall support for one or more SS7 upper layers. From an SS7 overall support for one or more SS7 upper layers. From an SS7
standpoint, a Signalling Point Management Cluster (SPMC) provides standpoint, a Signalling Point Management Cluster (SPMC) provides
complete support for the upper layer service for a given point code. complete support for the upper layer service for a given point code.
As an example, an SPMC providing MGC capabilities could provide As an example, an SPMC providing MGC capabilities could provide
complete support for ISUP (and any other MTP3 user located at the complete support for ISUP (and any other MTP3 user located at the
point code of the SPMC) for a given point code. point code of the SPMC) for a given point code.
In the case where an ASP is connected to more than one SGP, the M3UA In the case where an ASP is connected to more than one SGP, the M3UA
layer must maintain the status of configured SS7 destinations and route layer must maintain the status of configured SS7 destinations and
messages according to availability/congestion/restricted status of the route messages according to availability/congestion/restricted status
routes to these SS7 destinations. of the routes to these SS7 destinations.
1.4.3.4 IPSP Considerations 1.4.3.4 IPSP Considerations
Since IPSPs use M3UA in a point-to-point fashion, there is no concept Since IPSPs use M3UA in a point-to-point fashion, there is no concept
of routing of messages beyond the remote end. Therefore, SS7 and M3UA of routing of messages beyond the remote end. Therefore, SS7 and
interworking is not necessary for this model. M3UA interworking is not necessary for this model.
1.4.4 Redundancy Models 1.4.4 Redundancy Models
1.4.4.1 Application Server Redundancy 1.4.4.1 Application Server Redundancy
All MTP3-User messages (e.g., ISUP, SCCP) which match a provisioned All MTP3-User messages (e.g., ISUP, SCCP) which match a provisioned
Routing Key at an SGP are mapped to an Application Server. Routing Key at an SGP are mapped to an Application Server.
The Application Server is the set of all ASPs associated with a The Application Server is the set of all ASPs associated with a
specific Routing Key. Each ASP in this set may be active, inactive or specific Routing Key. Each ASP in this set may be active, inactive or
unavailable. Active ASPs handle traffic; inactive ASPs might be used unavailable. Active ASPs handle traffic; inactive ASPs might be used
when active ASPs become unavailable. when active ASPs become unavailable.
The failover model supports an "n+k" redundancy model, where "n" ASPs The failover model supports an "n+k" redundancy model, where "n" ASPs
is the minimum number of redundant ASPs required to handle traffic and is the minimum number of redundant ASPs required to handle traffic
"k" ASPs are available to take over for a failed or unavailable ASP. A and "k" ASPs are available to take over for a failed or unavailable
"1+1" active/backup redundancy is a subset of this model. A simplex ASP. A "1+1" active/backup redundancy is a subset of this model. A
"1+0" model is also supported as a subset, with no ASP redundancy. simplex "1+0" model is also supported as a subset, with no ASP
redundancy.
1.4.5 Flow Control 1.4.5 Flow Control
Local Management at an ASP may wish to stop traffic across an SCTP Local Management at an ASP may wish to stop traffic across an SCTP
association to temporarily remove the association from service or to association to temporarily remove the association from service or to
perform testing and maintenance activity. The function could optionally perform testing and maintenance activity. The function could
be used to control the start of traffic on to a newly available SCTP optionally be used to control the start of traffic on to a newly
association. available SCTP association.
1.4.6 Congestion Management 1.4.6 Congestion Management
The M3UA layer is informed of local and IP network congestion by means The M3UA layer is informed of local and IP network congestion by
of an implementation-dependent function (e.g., an implementation- means of an implementation-dependent function (e.g., an
dependent indication from the SCTP of IP network congestion). implementation dependent indication from the SCTP of IP network
congestion).
At an ASP or IPSP, the M3UA layer indicates congestion to local MTP3- At an ASP or IPSP, the M3UA layer indicates congestion to local
Users by means of an MTP-STATUS primitive, as per current MTP3 MTP3-Users by means of an MTP-STATUS primitive, as per current MTP3
procedures, to invoke appropriate upper layer responses. procedures, to invoke appropriate upper layer responses.
When an SG determines that the transport of SS7 messages to a When an SG determines that the transport of SS7 messages to a
Signalling Point Management Cluster (SPMC) is encountering congestion, Signalling Point Management Cluster (SPMC) is encountering
the SG MAY trigger SS7 MTP3 Transfer Controlled management messages congestion, the SG MAY trigger SS7 MTP3 Transfer Controlled
to originating SS7 nodes, per the congestion procedures of the relevant management messages to originating SS7 nodes, per the congestion
MTP3 standard. The triggering of SS7 MTP3 Management messages from an procedures of the relevant MTP3 standard. The triggering of SS7 MTP3
SG is an implementation-dependent function. Management messages from an SG is an implementation-dependent
function.
The M3UA layer at an ASP or IPSP MAY indicate local congestion to an The M3UA layer at an ASP or IPSP MAY indicate local congestion to an
M3UA peer with an SCON message. When an SG receives a congestion M3UA peer with an SCON message. When an SG receives a congestion
message (SCON) from an ASP, and the SG determines that an SPMC is now message (SCON) from an ASP, and the SG determines that an SPMC is now
encountering congestion, it MAY trigger SS7 MTP3 Transfer Controlled encountering congestion, it MAY trigger SS7 MTP3 Transfer Controlled
management messages to concerned SS7 destinations according to management messages to concerned SS7 destinations according to
congestion procedures of the relevant MTP3 standard. congestion procedures of the relevant MTP3 standard.
1.4.7 SCTP Stream Mapping. 1.4.7 SCTP Stream Mapping.
The M3UA layer at both the SGP and ASP also supports the assignment of The M3UA layer at both the SGP and ASP also supports the assignment
signalling traffic into streams within an SCTP association. Traffic of signalling traffic into streams within an SCTP association.
that requires sequencing SHOULD be assigned to the same stream. To Traffic that requires sequencing SHOULD be assigned to the same
accomplish this, MTP3-User traffic may be assigned to individual stream. To accomplish this, MTP3-User traffic may be assigned to
streams based on, for example, the SLS value in the MTP3 Routing Label individual streams based on, for example, the SLS value in the MTP3
or the ISUP CIC assignment, subject of course to the maximum number of Routing Label or the ISUP CIC assignment, subject of course to the
streams supported by the underlying SCTP association. maximum number of streams supported by the underlying SCTP
association.
1.4.8 Client/Server Model 1.4.8 Client/Server Model
It is recommended that the SGP and ASP be able to support both client It is recommended that the SGP and ASP be able to support both client
and server operation. The peer endpoints using M3UA SHOULD be and server operation. The peer endpoints using M3UA SHOULD be
configured so that one always takes on the role of client and the
other the role of server for initiating SCTP associations. The
default orientation would be for the SGP to take on the role of
server while the ASP is the client. In this case, ASPs SHOULD
initiate the SCTP association to the SGP.
configured so that one always takes on the role of client and the In the case of IPSP to IPSP communication, the peer endpoints using
other the role of server for initiating SCTP associations. The default M3UA SHOULD be configured so that one always takes on the role of
orientation would be for the SGP to take on the role of server while client and the other the role of server for initiating SCTP
the ASP is the client. In this case, ASPs SHOULD initiate the associations.
SCTP association to the SGP.
In the case of IPSP to IPSP communication, the peer endpoints using The SCTP and TCP Registered User Port Number Assignment for M3UA is
M3UA SHOULD be configured so that one always takes on the role of 2905.
client and the other the role of server for initiating SCTP
associations.
The SCTP and TCP Registered User Port Number Assignment for M3UA is 1.5 Sample Configuration
2905.
1.5 Sample Configurations
1.5.1 Example 1: ISUP Message Transport 1.5.1 Example 1: ISUP Message Transport
******** SS7 ***************** IP ******** ******** SS7 ***************** IP ********
* SEP *---------* SGP *--------* ASP * * SEP *---------* SGP *--------* ASP *
******** ***************** ******** ******** ***************** ********
+------+ +---------------+ +------+ +------+ +---------------+ +------+
| ISUP | | (NIF) | | ISUP | | ISUP | | (NIF) | | ISUP |
+------+ +------+ +------+ +------+ +------+ +------+ +------+ +------+
| MTP3 | | MTP3 | | M3UA | | M3UA | | MTP3 | | MTP3 | | M3UA | | M3UA |
+------| +------+-+------+ +------+ +------| +------+-+------+ +------+
| MTP2 | | MTP2 | | SCTP | | SCTP | | MTP2 | | MTP2 | | SCTP | | SCTP |
+------+ +------+ +------+ +------+ +------+ +------+ +------+ +------+
| L1 | | L1 | | IP | | IP | | L1 | | L1 | | IP | | IP |
+------+ +------+ +------+ +------+ +------+ +------+ +------+ +------+
|_______________| |______________| |_______________| |______________|
SEP - SS7 Signalling End Point SEP - SS7 Signalling End Point
SCTP - Stream Control Transmission Protocol SCTP - Stream Control Transmission Protocol
NIF - Nodal Interworking Function NIF - Nodal Interworking Function
In this example, the SGP provides an implementation-dependent nodal In this example, the SGP provides an implementation-dependent nodal
interworking function (NIF) that allows the MGC to exchange SS7 interworking function (NIF) that allows the MGC to exchange SS7
signalling messages with the SS7-based SEP. The NIF within the SGP signalling messages with the SS7-based SEP. The NIF within the SGP
serves as the interface within the SGP between the MTP3 and M3UA. This serves as the interface within the SGP between the MTP3 and M3UA.
nodal interworking function has no visible peer protocol with either This nodal interworking function has no visible peer protocol with
the MGC or SEP. It also provides network status information to one or either the MGC or SEP. It also provides network status information
both sides of the network. to one or both sides of the network.
For internal SGP modeling purposes, at the NIF level, SS7 signalling For internal SGP modeling purposes, at the NIF level, SS7 signalling
messages that are destined to the MGC are received as MTP-TRANSFER messages that are destined to the MGC are received as MTP-TRANSFER
indication primitives from the MTP Level 3 upper layer interface, indication primitives from the MTP Level 3 upper layer interface,
translated to MTP-TRANSFER request primitives, and sent to the local translated to MTP-TRANSFER request primitives, and sent to the local
M3UA-resident message distribution function for ongoing routing to the M3UA-resident message distribution function for ongoing routing to
final IP destination. Messages received from the local M3UA network the final IP destination. Messages received from the local M3UA
address translation and mapping function as MTP-TRANSFER indication network address translation and mapping function as MTP-TRANSFER
primitives are sent to the MTP Level 3 upper layer interface as MTP- indication primitives are sent to the MTP Level 3 upper layer
TRANSFER request primitives for ongoing MTP Level 3 routing to an SS7 interface as MTP-TRANSFER request primitives for ongoing MTP Level 3
SEP. For the purposes of providing SS7 network status information the routing to an SS7 SEP. For the purposes of providing SS7 network
NIF also delivers MTP-PAUSE, MTP-RESUME and MTP-STATUS indication status information the NIF also delivers MTP-PAUSE, MTP-RESUME and
primitives received from the MTP Level 3 upper layer interface to the MTP-STATUS indication primitives received from the MTP Level 3 upper
local M3UA-resident management function. In addition, as an layer interface to the local M3UA-resident management function. In
implementation and network option, restricted destinations are addition, as an implementation and network option, restricted
communicated from MTP network management to the local M3UA-resident destinations are communicated from MTP network management to the
management function. local M3UA-resident management function.
1.5.2 Example 2: SCCP Transport between IPSPs 1.5.2 Example 2: SCCP Transport between IPSPs
******** IP ********
* IPSP * * IPSP *
******** ********
+------+ +------+ ******** IP ********
|SCCP- | |SCCP- | * IPSP * * IPSP *
| User | | User | ******** ********
+------+ +------+
| SCCP | | SCCP |
+------+ +------+
| M3UA | | M3UA |
+------+ +------+
| SCTP | | SCTP |
+------+ +------+
| IP | | IP |
+------+ +------+
|________________|
This example shows an architecture where no Signalling Gateway is used. +------+ +------+
In this example, SCCP messages are exchanged directly between two IP- |SCCP- | |SCCP- |
resident IPSPs with resident SCCP-User protocol instances, such as | User | | User |
RANAP or TCAP. SS7 network interworking is not required, therefore +------+ +------+
there is no MTP3 network management status information for the SCCP and | SCCP | | SCCP |
SCCP-User protocols to consider. Any MTP-PAUSE, MTP-RESUME or MTP- +------+ +------+
STATUS indications from the M3UA layer to the SCCP layer should | M3UA | | M3UA |
consider the status of the SCTP Association and underlying IP network +------+ +------+
and any congestion information received from the remote site. | SCTP | | SCTP |
+------+ +------+
| IP | | IP |
+------+ +------+
|________________|
This example shows an architecture where no Signalling Gateway is
used. In this example, SCCP messages are exchanged directly between
two IP-resident IPSPs with resident SCCP-User protocol instances,
such as RANAP or TCAP. SS7 network interworking is not required,
therefore there is no MTP3 network management status information for
the SCCP and SCCP-User protocols to consider. Any MTP-PAUSE, MTP-
RESUME or MTP-STATUS indications from the M3UA layer to the SCCP
layer should consider the status of the SCTP Association and
underlying IP network and any congestion information received from
the remote site.
1.5.3 Example 3: SGP Resident SCCP Layer, with Remote ASP 1.5.3 Example 3: SGP Resident SCCP Layer, with Remote ASP
******** SS7 ***************** IP ******** ******** SS7 ***************** IP ********
* SEP *---------* *--------* * * SEP *---------* *--------* *
* or * * SGP * * ASP * * or * * SGP * * ASP *
* STP * * * * * * STP * * * * *
******** ***************** ******** ******** ***************** ********
+------+ +---------------+ +------+ +------+ +---------------+ +------+
| SCCP-| | SCCP | | SCCP-| | SCCP-| | SCCP | | SCCP-|
| User | +---------------+ | User | | User | +---------------+ | User |
+------+ | _____ | +------+ +------+ | _____ | +------+
| SCCP | | | | | | SCCP | | SCCP | | | | | | SCCP |
+------+ +------+-+------+ +------+ +------+ +------+-+------+ +------+
| MTP3 | | MTP3 | | M3UA | | M3UA | | MTP3 | | MTP3 | | M3UA | | M3UA |
+------| +------+ +------+ +------+ +------| +------+ +------+ +------+
| MTP2 | | MTP2 | | SCTP | | SCTP | | MTP2 | | MTP2 | | SCTP | | SCTP |
+------+ +------+ +------+ +------+ +------+ +------+ +------+ +------+
| L1 | | L1 | | IP | | IP | | L1 | | L1 | | IP | | IP |
+------+ +------+ +------+ +------+ +------+ +------+ +------+ +------+
|_______________| |______________| |_______________| |______________|
STP - SS7 Signalling Transfer Point STP - SS7 Signalling Transfer Point
In this example, the SGP contains an instance of the SS7 SCCP protocol In this example, the SGP contains an instance of the SS7 SCCP
layer that may, for example, perform the SCCP Global Title Translation protocol layer that may, for example, perform the SCCP Global Title
(GTT) function for messages logically addressed to the SG SCCP. If the Translation (GTT) function for messages logically addressed to the SG
result of a GTT for an SCCP message yields an SS7 DPC or DPC/SSN SCCP. If the result of a GTT for an SCCP message yields an SS7 DPC
address of an SCCP peer located in the IP domain, the resulting MTP- or DPC/SSN address of an SCCP peer located in the IP domain, the
TRANSFER request primitive is sent to the local M3UA-resident network resulting MTP-TRANSFER request primitive is sent to the local M3UA-
address translation and mapping function for ongoing routing to the resident network address translation and mapping function for ongoing
final IP destination. routing to the final IP destination.
Similarly, the SCCP instance in an SGP can perform the SCCP GTT service Similarly, the SCCP instance in an SGP can perform the SCCP GTT
for messages logically addressed to it from SCCP peers in the IP service for messages logically addressed to it from SCCP peers in the
domain. In this case, MTP-TRANSFER indication primitives are sent from IP domain. In this case, MTP-TRANSFER indication primitives are sent
the local M3UA-resident network address translation and mapping from the local M3UA-resident network address translation and mapping
function to the SCCP for GTT. If the result of the GTT yields the function to the SCCP for GTT. If the result of the GTT yields the
address of an SCCP peer in the SS7 network then the resulting MTP- address of an SCCP peer in the SS7 network then the resulting MTP-
TRANSFER request primitive is given to the MTP3 for delivery to an SS7- TRANSFER request primitive is given to the MTP3 for delivery to an
resident node. SS7-resident node.
It is possible that the above SCCP GTT at the SGP could yield the It is possible that the above SCCP GTT at the SGP could yield the
address of an SCCP peer in the IP domain and the resulting MTP-TRANSFER address of an SCCP peer in the IP domain and the resulting MTP-
request primitive would be sent back to the M3UA layer for delivery to TRANSFER request primitive would be sent back to the M3UA layer for
an IP destination. delivery to an IP destination.
For internal SGP modeling purposes, this may be accomplished with the For internal SGP modeling purposes, this may be accomplished with the
use of an implementation-dependent nodal interworking function within use of an implementation-dependent nodal interworking function within
the SGP that effectively sits below the SCCP and routes MTP-TRANSFER the SGP that effectively sits below the SCCP and routes MTP-TRANSFER
request/indication messages to/from both the MTP3 and the M3UA layer, request/indication messages to/from both the MTP3 and the M3UA layer,
based on the SS7 DPC or DPC/SSN address information. This nodal based on the SS7 DPC or DPC/SSN address information. This nodal
interworking function has no visible peer protocol with either the interworking function has no visible peer protocol with either the
ASP or SEP. ASP or SEP.
Note that the services and interface provided by the M3UA layer are the Note that the services and interface provided by the M3UA layer are
same as in Example 1 and the functions taking place in the SCCP entity the same as in Example 1 and the functions taking place in the SCCP
are transparent to the M3UA layer. The SCCP protocol functions are not entity are transparent to the M3UA layer. The SCCP protocol
reproduced in the M3UA protocol. functions are not reproduced in the M3UA protocol.
1.6 Definition of M3UA Boundaries 1.6 Definition of M3UA Boundaries
1.6.1 Definition of the Boundary between M3UA and an MTP3-User. 1.6.1 Definition of the Boundary between M3UA and an MTP3-User.
>From ITU Q.701 [7]: From ITU Q.701 [7]:
MTP-TRANSFER request MTP-TRANSFER request
MTP-TRANSFER indication MTP-TRANSFER indication
MTP-PAUSE indication MTP-PAUSE indication
MTP-RESUME indication MTP-RESUME indication
MTP-STATUS indication MTP-STATUS indication
1.6.2 Definition of the Boundary between M3UA and SCTP 1.6.2 Definition of the Boundary between M3UA and SCTP
An example of the upper layer primitives provided by the SCTP are An example of the upper layer primitives provided by the SCTP are
provided in Reference [17] Section 10. provided in Reference [17] Section 10.
1.6.3 Definition of the Boundary between M3UA and Layer Management 1.6.3 Definition of the Boundary between M3UA and Layer Management
M-SCTP_ESTABLISH request M-SCTP_ESTABLISH request
Direction: LM -> M3UA Direction: LM -> M3UA
Purpose: LM requests ASP to establish an SCTP association with its Purpose: LM requests ASP to establish an SCTP association with its
peer. peer.
M-STCP_ESTABLISH confirm M-STCP_ESTABLISH confirm
Direction: M3UA -> LM Direction: M3UA -> 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 its peer. association with its peer.
M-SCTP_ESTABLISH indication M-SCTP_ESTABLISH indication
Direction: M3UA -> LM Direction: M3UA -> LM
Purpose: M3UA informs LM that a remote ASP has established an SCTP Purpose: M3UA informs LM that a remote ASP has established an SCTP
association. association.
M-SCTP_RELEASE request M-SCTP_RELEASE request
Direction: LM -> M3UA Direction: LM -> M3UA
Purpose: LM requests ASP to release an SCTP association with its Purpose: LM requests ASP to release an SCTP association with its
peer. peer.
M-SCTP_RELEASE confirm M-SCTP_RELEASE confirm
Direction: M3UA -> LM Direction: M3UA -> LM
Purpose: ASP confirms to LM that it has released SCTP association Purpose: ASP confirms to LM that it has released SCTP association
with its peer. with its peer.
M-SCTP_RELEASE indication M-SCTP_RELEASE indication
Direction: M3UA -> LM Direction: M3UA -> LM
Purpose: M3UA informs LM that a remote ASP has released an SCTP Purpose: M3UA informs LM that a remote ASP has released an SCTP
Association or the SCTP association has failed. Association or the SCTP association has failed.
M-SCTP RESTART indication M-SCTP_RESTART indication
Direction: M3UA -> LM Direction: M3UA -> LM
Purpose: M3UA informs LM that an SCTP restart indication has been Purpose: M3UA informs LM that an SCTP restart indication has been
received. received.
M-SCTP_STATUS request M-SCTP_STATUS request
Direction: LM -> M3UA Direction: LM -> M3UA
Purpose: LM requests M3UA to report the status of an SCTP Purpose: LM requests M3UA to report the status of an SCTP
association. association.
M-SCTP_STATUS confirm M-SCTP_STATUS confirm
Direction: M3UA -> LM Direction: M3UA -> LM
Purpose: M3UA responds with the status of an SCTP association. Purpose: M3UA responds with the status of an SCTP association.
M-SCTP STATUS indication M-SCTP STATUS indication
Direction: M3UA -> LM Direction: M3UA -> LM
Purpose: M3UA reports the status of an SCTP association. Purpose: M3UA reports the status of an SCTP association.
M-ASP_STATUS request M-ASP_STATUS request
Direction: LM -> M3UA Direction: LM -> M3UA
Purpose: LM requests M3UA to report the status of a local or remote Purpose: LM requests M3UA to report the status of a local or remote
ASP. ASP.
M-ASP_STATUS confirm M-ASP_STATUS confirm
Direction: M3UA -> LM Direction: M3UA -> LM
Purpose: M3UA reports status of local or remote ASP. Purpose: M3UA reports status of local or remote ASP.
M-AS_STATUS request M-AS_STATUS request
Direction: LM -> M3UA Direction: LM -> M3UA
Purpose: LM requests M3UA to report the status of an AS. Purpose: LM requests M3UA to report the status of an AS.
M-AS_STATUS confirm M-AS_STATUS confirm
Direction: M3UA -> LM Direction: M3UA -> LM
Purpose: M3UA reports the status of an AS. Purpose: M3UA reports the status of an AS.
M-NOTIFY indication M-NOTIFY indication
Direction: M3UA -> LM Direction: M3UA -> LM
Purpose: M3UA reports that it has received a Notify message Purpose: M3UA reports that it has received a Notify message
from its peer. from its peer.
M-ERROR indication M-ERROR indication
Direction: M3UA -> LM Direction: M3UA -> LM
Purpose: M3UA reports that it has received an Error message from Purpose: M3UA reports that it has received an Error message from
its peer or that a local operation has been unsuccessful. its peer or that a local operation has been unsuccessful.
M-ASP_UP request M-ASP_UP request
Direction: LM -> M3UA Direction: LM -> M3UA
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 its peer. message to its peer.
M-ASP_UP confirm M-ASP_UP confirm
Direction: M3UA -> LM Direction: M3UA -> LM
Purpose: ASP reports that is has received an ASP UP Ack message from Purpose: ASP reports that is has received an ASP UP Ack message from
its peer. its peer.
M-ASP_UP indication M-ASP_UP indication
Direction: M3UA -> LM Direction: M3UA -> LM
Purpose: M3UA reports it has successfully processed an incoming ASP Purpose: M3UA reports it has successfully processed an incoming ASP
Up message from its peer. Up message from its peer.
M-ASP_DOWN request M-ASP_DOWN request
Direction: LM -> M3UA Direction: LM -> M3UA
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 its peer. message to its peer.
M-ASP_DOWN confirm M-ASP_DOWN confirm
Direction: M3UA -> LM Direction: M3UA -> LM
Purpose: ASP reports that is has received an ASP Down Ack message Purpose: ASP reports that is has received an ASP Down Ack message
from its peer. from its peer.
M-ASP_DOWN indication M-ASP_DOWN indication
Direction: M3UA -> LM Direction: M3UA -> LM
Purpose: M3UA reports it has successfully processed an incoming ASP Purpose: M3UA reports it has successfully processed an incoming ASP
Down message from its peer, or the SCTP association has Down message from its peer, or the SCTP association has
been lost/reset. been lost/reset.
M-ASP_ACTIVE request M-ASP_ACTIVE request
Direction: LM -> M3UA Direction: LM -> M3UA
Purpose: LM requests ASP to send an ASP Active message to its peer. Purpose: LM requests ASP to send an ASP Active message to its peer.
M-ASP_ACTIVE confirm M-ASP_ACTIVE confirm
Direction: M3UA -> LM Direction: M3UA -> LM
Purpose: ASP reports that is has received an ASP Active Purpose: ASP reports that is has received an ASP Active
Ack message from its peer. Ack message from its peer.
M-ASP_ACTIVE indication M-ASP_ACTIVE indication
Direction: M3UA -> LM Direction: M3UA -> LM
Purpose: M3UA reports it has successfully processed an incoming ASP Purpose: M3UA reports it has successfully processed an incoming ASP
Active message from its peer. Active message from its peer.
M-ASP_INACTIVE request M-ASP_INACTIVE request
Direction: LM -> M3UA Direction: LM -> M3UA
Purpose: LM requests ASP to send an ASP Inactive message to its Purpose: LM requests ASP to send an ASP Inactive message to its
peer. peer.
M-ASP_INACTIVE confirm M-ASP_INACTIVE confirm
Direction: LM -> M3UA Direction: LM -> M3UA
Purpose: ASP reports that is has received an ASP Inactive Purpose: ASP reports that is has received an ASP Inactive
Ack message from its peer. Ack message from its peer.
M-ASP_INACTIVE indication M-ASP_INACTIVE indication
Direction: M3UA -> LM Direction: M3UA -> LM
Purpose: M3UA reports it has successfully processed an incoming ASP Purpose: M3UA reports it has successfully processed an incoming ASP
Inactive message from its peer. Inactive message from its peer.
M-AS_ACTIVE indication M-AS_ACTIVE indication
Direction: M3UA -> LM Direction: M3UA -> LM
Purpose: M3UA reports that an AS has moved to the AS-ACTIVE state. Purpose: M3UA reports that an AS has moved to the AS-ACTIVE state.
M-AS_INACTIVE indication M-AS_INACTIVE indication
Direction: M3UA -> LM Direction: M3UA -> LM
Purpose: M3UA reports that an AS has moved to the AS-INACTIVE state. Purpose: M3UA reports that an AS has moved to the AS-INACTIVE state.
M-AS_DOWN indication M-AS_DOWN indication
Direction: M3UA -> LM Direction: M3UA -> LM
Purpose: M3UA reports that an AS has moved to the AS-DOWN state. Purpose: M3UA reports that an AS has moved to the AS-DOWN state.
If dynamic registration of RK is supported by the M3UA layer, the layer If dynamic registration of RK is supported by the M3UA layer, the
MAY support the following additional primitives: layer MAY support the following additional primitives:
M-RK_REG request M-RK_REG request
Direction: LM -> M3UA Direction: LM -> M3UA
Purpose: LM requests ASP to register RK(s) with its peer by sending Purpose: LM requests ASP to register RK(s) with its peer by sending
REG REQ message REG REQ message
M-RK_REG confirm M-RK_REG confirm
Direction: M3UA -> LM Direction: M3UA -> LM
Purpose: ASP reports that it has received REG RSP message with Purpose: ASP reports that it has received REG RSP message with
registration status as successful from its peer. registration status as successful from its peer.
M-RK_REG indication M-RK_REG indication
Direction: M3UA -> LM Direction: M3UA -> LM
Purpose: M3UA informs LM that it has successfully processed an Purpose: M3UA informs LM that it has successfully processed an
incoming REG REQ message. incoming REG REQ message.
M-RK_DEREG request M-RK_DEREG request
Direction: LM -> M3UA Direction: LM -> M3UA
Purpose: LM requests ASP to deregister RK(s) with its peer by Purpose: LM requests ASP to deregister RK(s) with its peer by
sending DEREG REQ message. sending DEREG REQ message.
M-RK_DEREG confirm M-RK_DEREG confirm
Direction: M3UA -> LM Direction: M3UA -> LM
Purpose: ASP reports that it has received DEREG REQ message with Purpose: ASP reports that it has received DEREG REQ message with
deregistration status as successful from its peer. deregistration status as successful from its peer.
M-RK_DEREG indication M-RK_DEREG indication
Direction: M3UA -> LM Direction: M3UA -> LM
Purpose: M3UA informs LM that it has successfully processed an Purpose: M3UA informs LM that it has successfully processed an
incoming DEREG REQ from its peer. incoming DEREG REQ from its peer.
2. Conventions 2. Conventions
The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,
NOT, RECOMMENDED, NOT RECOMMENDED, MAY, and OPTIONAL, when they appear SHOULD NOT, RECOMMENDED, NOT RECOMMENDED, MAY, and OPTIONAL, when
in this document, are to be interpreted as described in [20]. they appear in this document, are to be interpreted as described in
[20].
3. M3UA Protocol Elements 3. M3UA Protocol Elements
The general M3UA message format includes a Common Message Header The general M3UA message format includes a Common Message Header
followed by zero or more parameters as defined by the Message Type. followed by zero or more parameters as defined by the Message Type.
For forward compatibility, all Message Types may have attached For forward compatibility, all Message Types may have attached
parameters even if none are specified in this version. parameters even if none are specified in this version.
3.1 Common Message Header 3.1 Common Message Header
The protocol messages for MTP3-User Adaptation require a message header The protocol messages for MTP3-User Adaptation require a message
which contains the adaptation layer version, the message type, and header which contains the adaptation layer version, the message type,
message length. and message length.
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 | Reserved | Message Class | Message Type | | Version | Reserved | Message Class | Message Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Message Length | | Message Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ / / /
All fields in an M3UA message MUST be transmitted in the network byte All fields in an M3UA message MUST be transmitted in the network byte
order, unless otherwise stated. order, unless otherwise stated.
3.1.1 M3UA Protocol Version: 8 bits (unsigned integer) 3.1.1 M3UA Protocol Version: 8 bits (unsigned integer)
The version field contains the version of the M3UA adaptation layer. The version field contains the version of the M3UA adaptation layer.
The supported versions are the following: The supported versions are the following:
1 Release 1.0 1 Release 1.0
3.1.2 Message Classes and Types 3.1.2 Message Classes and Types
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)
The following list contains the valid Message Type Classes: The following list contains the valid Message Type Classes:
0 Management (MGMT) Message 0 Management (MGMT) Messages
1 Transfer Messages
1 Transfer Messages 2 SS7 Signalling Network Management (SSNM) Messages
2 SS7 Signalling Network Management (SSNM) Messages 3 ASP State Maintenance (ASPSM) Messages
3 ASP State Maintenance (ASPSM) Messages 4 ASP Traffic Maintenance (ASPTM) Messages
4 ASP Traffic Maintenance (ASPTM) Messages 5 Reserved for Other Sigtran Adaptation Layers
5 Reserved for Other Sigtran Adaptation Layers 6 Reserved for Other Sigtran Adaptation Layers
6 Reserved for Other Sigtran Adaptation Layers 7 Reserved for Other Sigtran Adaptation Layers
7 Reserved for Other Sigtran Adaptation Layers 8 Reserved for Other Sigtran Adaptation Layers
8 Reserved for Other Sigtran Adaptation Layers 9 Routing Key Management (RKM) Messages
9 Routing Key Management (RKM) Messages 10 to 127 Reserved by the IETF
10 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 Message Type: 8 bits (unsigned integer)
Message Type: 8 bits (unsigned integer)
The following list contains the message types for the defined
messages.
Management (MGMT) Messages (See Section 3.6) The following list contains the message types for the defined
messages.
0 Error (ERR) Management (MGMT) Messages (See Section 3.8)
1 Notify (NTFY)
2 to 127 Reserved by the IETF
128 to 255 Reserved for IETF-Defined MGMT extensions
Transfer Messages (See Section 3.3) 0 Error (ERR)
1 Notify (NTFY)
2 to 127 Reserved by the IETF
128 to 255 Reserved for IETF-Defined MGMT extensions
0 Reserved Transfer Messages (See Section 3.3)
1 Payload Data (DATA)
2 to 127 Reserved by the IETF
128 to 255 Reserved for IETF-Defined Transfer extensions
SS7 Signalling Network Management (SSNM) Messages (See Section 0 Reserved
3.4) 1 Payload Data (DATA)
2 to 127 Reserved by the IETF
128 to 255 Reserved for IETF-Defined Transfer extensions
0 Reserved SS7 Signalling Network Management (SSNM) Messages (See Section
1 Destination Unavailable (DUNA) 3.4)
2 Destination Available (DAVA)
3 Destination State Audit (DAUD)
4 Signalling Congestion (SCON)
5 Destination User Part Unavailable (DUPU)
6 Destination Restricted (DRST)
7 to 127 Reserved by the IETF
128 to 255 Reserved for IETF-Defined SSNM extensions
ASP State Maintenance (ASPSM) Messages (See Section 3.5) 0 Reserved
1 Destination Unavailable (DUNA)
2 Destination Available (DAVA)
3 Destination State Audit (DAUD)
4 Signalling Congestion (SCON)
5 Destination User Part Unavailable (DUPU)
6 Destination Restricted (DRST)
7 to 127 Reserved by the IETF
128 to 255 Reserved for IETF-Defined SSNM extensions
0 Reserved ASP State Maintenance (ASPSM) Messages (See Section 3.5)
1 ASP Up (ASPUP)
2 ASP Down (ASPDN)
3 Heartbeat (BEAT)
4 ASP Up Acknowledgement (ASPUP ACK)
5 ASP Down Acknowledgement (ASPDN ACK)
6 Heartbeat Acknowledgement (BEAT ACK)
7 to 127 Reserved by the IETF
128 to 255 Reserved for IETF-Defined ASPSM extensions
ASP Traffic Maintenance (ASPTM) Messages (See Section 3.5) 0 Reserved
1 ASP Up (ASPUP)
2 ASP Down (ASPDN)
3 Heartbeat (BEAT)
4 ASP Up Acknowledgement (ASPUP ACK)
5 ASP Down Acknowledgement (ASPDN ACK)
6 Heartbeat Acknowledgement (BEAT ACK)
7 to 127 Reserved by the IETF
128 to 255 Reserved for IETF-Defined ASPSM extensions
ASP Traffic Maintenance (ASPTM) Messages (See Section 3.7)
0 Reserved 0 Reserved
1 ASP Active (ASPAC) 1 ASP Active (ASPAC)
2 ASP Inactive (ASPIA) 2 ASP Inactive (ASPIA)
3 ASP Active Acknowledgement (ASPAC ACK) 3 ASP Active Acknowledgement (ASPAC ACK)
4 ASP Inactive Acknowledgement (ASPIA ACK) 4 ASP Inactive Acknowledgement (ASPIA ACK)
5 to 127 Reserved by the IETF 5 to 127 Reserved by the IETF
128 to 255 Reserved for IETF-Defined ASPTM extensions 128 to 255 Reserved for IETF-Defined ASPTM extensions
Routing Key Management (RKM) Messages (See Section 3.7) Routing Key Management (RKM) Messages (See Section 3.6)
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 RKM extensions 128 to 255 Reserved for IETF-Defined RKM extensions
3.1.3 Reserved: 8 bits 3.1.3 Reserved: 8 bits
The Reserved field SHOULD be set to all '0's and ignored by the The Reserved field SHOULD be set to all '0's and ignored by the
receiver. receiver.
3.1.4 Message Length: 32-bits (unsigned integer) 3.1.4 Message Length: 32-bits (unsigned integer)
The Message Length defines the length of the message in octets, The Message Length defines the length of the message in octets,
including the Common Header. For messages with a final parameter including the Common Header. The Message Length MUST include
containing padding, the parameter padding MUST be included in the parameter padding bytes, if any.
Message Length.
Note: A receiver SHOULD accept the message whether or not the final Note: A receiver SHOULD accept the message whether or not the final
parameter padding is included in the message length. parameter padding is included in the message length.
3.2 Variable Length Parameter Format 3.2 Variable Length Parameter Format
M3UA messages consist of a Common Header followed by zero or more M3UA messages consist of a Common Header followed by zero or more
variable length parameters, as defined by the message type. All the variable length parameters, as defined by the message type. All the
parameters contained in a message are defined in a Tag Length-Value parameters contained in a message are defined in a Tag Length-Value
format as shown below. 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 /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Where more than one parameter is included in a message, the parameters Where more than one parameter is included in a message, the
may be in any order, except where explicitly mandated. A receiver parameters may be in any order, except where explicitly mandated. A
SHOULD accept the parameters in any order. receiver SHOULD accept the parameters in any order.
Parameter Tag: 16 bits (unsigned integer) Parameter Tag: 16 bits (unsigned integer)
The Tag field is a 16-bit identifier of the type of parameter. It The Tag field is a 16-bit identifier of the type of parameter. It
takes a value of 0 to 65534. Common parameters used by adaptation takes a value of 0 to 65534. Common parameters used by adaptation
layers are in the range of 0x00 to 0x3f. M3UA-specific parameters layers are in the range of 0x00 to 0x3f. M3UA-specific
have Tags in the range 0x0200 to 0x02ff. The parameter Tags defined parameters have Tags in the range 0x0200 to 0x02ff. The parameter
are as follows: Tags defined are as follows:
Common Parameters. These TLV parameters are common across the Common Parameters. These TLV parameters are common across the
different adaptation layers: different adaptation layers:
Parameter Name Parameter ID Parameter Name Parameter ID
============== ============ ============== ============
Reserved 0x0000 Reserved 0x0000
Not Used in M3UA 0x0001 Not Used in M3UA 0x0001
Not Used in M3UA 0x0002 Not Used in M3UA 0x0002
Not Used in M3UA 0x0003 Not Used in M3UA 0x0003
INFO String 0x0004 INFO String 0x0004
Not Used in M3UA 0x0005 Not Used in M3UA 0x0005
Routing Context 0x0006 Routing Context 0x0006
Diagnostic Information 0x0007 Diagnostic Information 0x0007
Not Used in M3UA 0x0008 Not Used in M3UA 0x0008
Heartbeat Data 0x0009 Heartbeat Data 0x0009
Not Used in M3UA 0x000a Not Used in M3UA 0x000a
Traffic Mode Type 0x000b Traffic Mode Type 0x000b
Error Code 0x000c Error Code 0x000c
Status 0x000d Status 0x000d
Not Used in M3UA 0x000e Not Used in M3UA 0x000e
Not Used in M3UA 0x000f Not Used in M3UA 0x000f
Not Used in M3UA 0x0010 Not Used in M3UA 0x0010
ASP Identifier 0x0011 ASP Identifier 0x0011
Affected Point Code 0x0012 Affected Point Code 0x0012
Correlation ID 0x0013 Correlation ID 0x0013
M3UA-Specific parameters. These TLV parameters are specific to the
M3UA protocol:
Network Appearance 0x0200 M3UA-Specific parameters. These TLV parameters are specific to
Reserved 0x0201 the M3UA protocol:
Reserved 0x0202
Reserved 0x0203
User/Cause 0x0204
Congestion Indications 0x0205
Concerned Destination 0x0206
Routing Key 0x0207
Registration Result 0x0208
Deregistration Result 0x0209
Local_Routing Key Identifier 0x020a
Destination Point Code 0x020b
Service Indicators 0x020c
Reserved 0x020d
Originating Point Code List 0x020e
Circuit Range 0x020f
Protocol Data 0x0210
Reserved 0x0211
Registration Status 0x0212
Deregistration Status 0x0213
Reserved by the IETF 0x0214 to 0xffff Network Appearance 0x0200
Reserved 0x0201
Reserved 0x0202
Reserved 0x0203
User/Cause 0x0204
Congestion Indications 0x0205
Concerned Destination 0x0206
Routing Key 0x0207
Registration Result 0x0208
Deregistration Result 0x0209
Local_Routing Key Identifier 0x020a
Destination Point Code 0x020b
Service Indicators 0x020c
Reserved 0x020d
Originating Point Code List 0x020e
Circuit Range 0x020f
Protocol Data 0x0210
Reserved 0x0211
Registration Status 0x0212
Deregistration Status 0x0213
The value of 65535 is reserved for IETF-defined extensions. Values Reserved by the IETF 0x0214 to 0xffff
other than those defined in specific parameter description are
reserved for use by the IETF.
Parameter Length: 16 bits (unsigned integer) The value of 65535 is reserved for IETF-defined extensions.
Values other than those defined in specific parameter description
are reserved for use by the IETF.
The Parameter Length field contains the size of the parameter in Parameter Length: 16 bits (unsigned integer)
bytes, including the Parameter Tag, Parameter Length, and Parameter
Value fields. Thus, a parameter with a zero-length Parameter Value
field would have a Length field of 4. The Parameter Length does
not include any padding bytes.
Parameter Value: variable length. The Parameter Length field contains the size of the parameter in
bytes, including the Parameter Tag, Parameter Length, and
Parameter Value fields. Thus, a parameter with a zero-length
Parameter Value field would have a Length field of 4. The
Parameter Length does not include any padding bytes.
The Parameter Value field contains the actual information to be Parameter Value: variable length.
transferred in the parameter.
The total length of a parameter (including Tag, Parameter Length and The Parameter Value field contains the actual information to be
Value fields) MUST be a multiple of 4 bytes. If the length of the transferred in the parameter.
parameter is not a multiple of 4 bytes, the sender pads the
Parameter at the end (i.e., after the Parameter Value field) with The total length of a parameter (including Tag, Parameter Length
all zero bytes. The length of the padding is NOT included in the and Value fields) MUST be a multiple of 4 bytes. If the length of
parameter length field. A sender SHOULD NOT pad with more than 3 the parameter is not a multiple of 4 bytes, the sender pads the
bytes. The receiver MUST ignore the padding bytes. Parameter at the end (i.e., after the Parameter Value field) with
all zero bytes. The length of the padding is NOT included in the
parameter length field. A sender SHOULD NOT pad with more than 3
bytes. The receiver MUST ignore the padding bytes.
3.3 Transfer Messages 3.3 Transfer Messages
The following section describes the Transfer messages and parameter The following section describes the Transfer messages and parameter
contents. contents.
3.3.1 Payload Data Message (DATA) 3.3.1 Payload Data Message (DATA)
The DATA message contains the SS7 MTP3-User protocol data, which is an The DATA message contains the SS7 MTP3-User protocol data, which is
MTP-TRANSFER primitive, including the complete MTP3 Routing Label. The an MTP-TRANSFER primitive, including the complete MTP3 Routing Label.
DATA message contains the following variable length parameters: The DATA message contains the following variable length parameters:
Network Appearance Optional Network Appearance Optional
Routing Context Optional Routing Context Optional
Protocol Data Mandatory Protocol Data Mandatory
Correlation Id Optional Correlation Id Optional
The following format MUST be used for the Data Message: The following format MUST be used for the Data 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 = 0x0200 | Length = 8 | | Tag = 0x0200 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Network Appearance | | Network Appearance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0006 | Length = 8 | | Tag = 0x0006 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Routing Context | | Routing Context |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0210 | Length | | Tag = 0x0210 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ Protocol Data / / Protocol Data /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0013 | Length = 8 | | Tag = 0x0013 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Correlation Id | | Correlation Id |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Network Appearance: 32-bits (unsigned integer) Network Appearance: 32-bits (unsigned integer)
The Network Appearance parameter identifies the SS7 network The Network Appearance parameter identifies the SS7 network
context for the message and implicitly identifies the SS7 context for the message and implicitly identifies the SS7 Point
Point Code format used, the SS7 Network Indicator value, and the Code format used, the SS7 Network Indicator value, and the MTP3
MTP3 and possibly the MTP3-User protocol type/variant/version used and possibly the MTP3-User protocol type/variant/version used
within the specific SS7 network. Where an SG operates in the within the specific SS7 network. Where an SG operates in the
context of a single SS7 network, or individual SCTP associations context of a single SS7 network, or individual SCTP associations
are dedicated to each SS7 network context, the Network Appearance are dedicated to each SS7 network context, the Network Appearance
parameter is not required. In other cases the parameter may be parameter is not required. In other cases the parameter may be
configured to be present for the use of the receiver. configured to be present for the use of the receiver.
The Network Appearance parameter value is of local significance The Network Appearance parameter value is of local significance
only, coordinated between the SGP and ASP. Therefore, in the case only, coordinated between the SGP and ASP. Therefore, in the case
where an ASP is connected to more than one SGP, the same SS7 network where an ASP is connected to more than one SGP, the same SS7
context may be identified by different Network Appearance values network context may be identified by different Network Appearance
depending over which SGP a message is being transmitted/received. values depending over which SGP a message is being
transmitted/received.
Where the optional Network Appearance parameter is present, it must Where the optional Network Appearance parameter is present, it
be the first parameter in the message as it defines the format of must be the first parameter in the message as it defines the
the Protocol Data field. format of the Protocol Data field.
IMPLEMENTATION NOTE: For simplicity of configuration it may be IMPLEMENTATION NOTE: For simplicity of configuration it may be
desirable to use the same NA value across all nodes sharing a desirable to use the same NA value across all nodes sharing a
particular network context. particular network context.
Routing Context: 32-bits (unsigned integer) Routing Context: 32-bits (unsigned integer)
The Routing Context parameter contains the Routing Context The Routing Context parameter contains the Routing Context value
value associated with the DATA message. Where a Routing Key has associated with the DATA message. Where a Routing Key has not
not been coordinated between the SGP and ASP, sending of Routing been coordinated between the SGP and ASP, sending of Routing
Context is not required. Where multiple Routing Keys and Routing Context is not required. Where multiple Routing Keys and Routing
Contexts are used across a common association, the Routing Context Contexts are used across a common association, the Routing Context
MUST be sent to identify the traffic flow, assisting in the internal MUST be sent to identify the traffic flow, assisting in the
distribution of Data messages. internal distribution of Data messages.
Protocol Data: variable length Protocol Data: variable length
The Protocol Data parameter contains the original SS7 MTP3 The Protocol Data parameter contains the original SS7 MTP3
message, including the Service Information Octet and Routing Label. message, including the Service Information Octet and Routing
Label.
The Protocol Data parameter contains the following fields: The Protocol Data parameter contains the following fields:
Service Indicator, Service Indicator,
Network Indicator, Network Indicator,
Message Priority. Message Priority.
Destination Point Code, Destination Point Code,
Originating Point Code, Originating Point Code,
Signalling Link Selection Code (SLS).
Signalling Link Selection Code (SLS).
User Protocol Data. Includes:
User Protocol Data. Includes:
MTP3-User protocol elements (e.g., ISUP, SCCP, or TUP MTP3-User protocol elements (e.g., ISUP, SCCP, or TUP
parameters). parameters).
The Protocol Data parameter is encoded as follows: The Protocol Data parameter is encoded 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Originating Point Code | | Originating Point Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination Point Code | | Destination Point Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SI | NI | MP | SLS | | SI | NI | MP | SLS |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ Protocol Data / / User Protocol Data /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Originating Point Code: 32 bits (unsigned integer) Originating Point Code: 32 bits (unsigned integer)
Destination Point Code: 32 bits (unsigned integer) Destination Point Code: 32 bits (unsigned integer)
The Originating and Destination Point Code fields contains the OPC The Originating and Destination Point Code fields contains the OPC
and DPC from the routing label of the original SS7 message in and DPC from the routing label of the original SS7 message in Network
Network Byte Order, justified to the least significant bit. Unused Byte Order, justified to the least significant bit. Unused bits are
bits are coded `0'. coded `0'.
Service Indicator: 8 bits (unsigned integer) Service Indicator: 8 bits (unsigned integer)
The Service Indicator field contains the SI field from the original The Service Indicator field contains the SI field from the original
SS7 message justified to the least significant bit. Unused bits SS7 message justified to the least significant bit. Unused bits are
are coded `0'. coded `0'.
Network Indicator: 8-bits (unsigned integer) Network Indicator: 8-bits (unsigned integer)
The Network Indicator contains the NI field from the original SS7 The Network Indicator contains the NI field from the original SS7
message justified to the least significant bit. Unused bits are message justified to the least significant bit. Unused bits are
coded `0'. coded `0'.
Message Priority: 8 bits (unsigned integer) Message Priority: 8 bits (unsigned integer)
The Message Priority field contains the MP bits (if any) from the The Message Priority field contains the MP bits (if any) from the
original SS7 message, both for ANSI-style and TTC-style [29] message original SS7 message, both for ANSI-style and TTC-style [29] message
priority bits. The MP bits are aligned to the least significant priority bits. The MP bits are aligned to the least significant bit.
bit. Unused bits are coded `0'. Unused bits are coded `0'.
Signalling Link Selection: 8 bits (unsigned integer) Signalling Link Selection: 8 bits (unsigned integer)
The Signalling Link Selection field contains the SLS bits from The Signalling Link Selection field contains the SLS bits from the
the routing label of the original SS7 message justified to the routing label of the original SS7 message justified to the least
least significant bit and in Network Byte Order. Unused bits are significant bit and in Network Byte Order. Unused bits are coded
coded `0'. `0'.
Protocol Data: (variable) User Protocol Data: (byte string)
The Protocol Data field contains a byte string of MTP-User The User Protocol Data field contains a byte string of MTP-User
information from the original SS7 message starting with the information from the original SS7 message starting with the first
first byte of the original SS7 message following the Routing Label. byte of the original SS7 message following the Routing Label.
Correlation Id: 32-bits (unsigned integer) Correlation Id: 32-bits (unsigned integer)
The Correlation Id parameter uniquely identifies the MSU carried in The Correlation Id parameter uniquely identifies the MSU carried in
the Protocol Data within an AS. This Correlation Id parameter is the Protocol Data within an AS. This Correlation Id parameter is
assigned by the sending M3UA. assigned by the sending M3UA.
3.4 SS7 Signalling Network Management (SSNM) Messages 3.4 SS7 Signalling Network Management (SSNM) Messages
3.4.1 Destination Unavailable (DUNA) 3.4.1 Destination Unavailable (DUNA)
The DUNA message is sent from an SGP in an SG to all concerned ASPs The DUNA message is sent from an SGP in an SG to all concerned ASPs
to indicate that the SG has determined that one or more SS7 destinations to indicate that the SG has determined that one or more SS7
are unreachable. It is also sent by an SGP in response to a message destinations are unreachable. It is also sent by an SGP in response
from the ASP to an unreachable SS7 destination. As an implementation to a message from the ASP to an unreachable SS7 destination. As an
option the SG may suppress the sending of subsequent "response" DUNA implementation option the SG may suppress the sending of subsequent
messages regarding a certain unreachable SS7 destination for a certain "response" DUNA messages regarding a certain unreachable SS7
period to give the remote side time to react. If there is no alternate destination for a certain period to give the remote side time to
route via another SG, the MTP3-User at the ASP is expected to stop react. If there is no alternate route via another SG, the MTP3-User
traffic to the affected destination via the SG as per the defined MTP3- at the ASP is expected to stop traffic to the affected destination
User procedures. via the SG as per the defined MTP3-User procedures.
The DUNA message contains the following parameters: The DUNA message contains the following parameters:
Network Appearance Optional Network Appearance Optional
Routing Context Optional Routing Context Optional
Affected Point Code Mandatory Affected Point Code Mandatory
INFO String Optional INFO String Optional
The format for DUNA Message parameters is as follows: The format for DUNA 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 = 0x0200 | Length = 8 | | Tag = 0x0200 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Network Appearance | | Network Appearance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0006 | Length | | Tag = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ Routing Context / / Routing Context /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0012 | Length | | Tag = 0x0012 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mask | Affected PC 1 | | Mask | Affected PC 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ ... / / ... /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mask | Affected PC n | | Mask | Affected PC n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | Length | | Tag = 0x0004 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ INFO String / / INFO String /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Network Appearance: 32-bit unsigned integer Network Appearance: 32-bit unsigned integer
See Section 3.3.1 See Section 3.3.1
Routing Context: n x 32-bits (unsigned integer) Routing Context: n x 32-bits (unsigned integer)
The optional Routing Context parameter contains the Routing Context The optional Routing Context parameter contains the Routing
values associated with the DUNA message. Where a Routing Key has Context values associated with the DUNA message. Where a Routing
not been coordinated between the SGP and ASP, sending of Routing Key has not been coordinated between the SGP and ASP, sending of
Context is not required. Where multiple Routing Keys and Routing Routing Context is not required. Where multiple Routing Keys and
Contexts are used across a common association, the Routing Routing Contexts are used across a common association, the Routing
Context(s) MUST be sent to identify the concerned traffic flows Context(s) MUST be sent to identify the concerned traffic flows
for which the DUNA message applies, assisting in outgoing traffic for which the DUNA message applies, assisting in outgoing traffic
management and internal distribution of MTP-PAUSE indications to management and internal distribution of MTP-PAUSE indications to
MTP3-Users at the receiver. MTP3-Users at the receiver.
Affected Point Code: n x 32-bits Affected Point Code: n x 32-bits
The Affected Point Code parameter contains a list of Affected The Affected Point Code parameter contains a list of Affected
Destination Point Code fields, each a three-octet parameter to allow Destination Point Code fields, each a three-octet parameter to
for 14-, 16- and 24-bit binary formatted SS7 Point Codes. Affected allow for 14-, 16- and 24-bit binary formatted SS7 Point Codes.
Point Codes that are less than 24-bits, are padded on the left to Affected Point Codes that are less than 24-bits, are padded on the
the 24-bit boundary. The encoding is shown below for ANSI and ITU left to the 24-bit boundary. The encoding is shown below for ANSI
Point Code examples. and ITU Point Code examples.
ANSI 24-bit Point Code: ANSI 24-bit Point Code:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mask | Network | Cluster | Member | | Mask | Network | Cluster | Member |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|MSB-----------------------------------------LSB| |MSB-----------------------------------------LSB|
ITU 14-bit Point Code: ITU 14-bit Point Code:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mask |0 0 0 0 0 0 0 0 0 0|Zone | Region | SP | | Mask |0 0 0 0 0 0 0 0 0 0|Zone | Region | SP |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|MSB--------------------LSB| |MSB--------------------LSB|
It is optional to send an Affected Point Code parameter with more It is optional to send an Affected Point Code parameter with more
than one Affected PC but it is mandatory to receive it. Including than one Affected PC but it is mandatory to receive it. Including
multiple Affected PCs may be useful when reception of an MTP3 multiple Affected PCs may be useful when reception of an MTP3
management message or a linkset event simultaneously affects the management message or a linkset event simultaneously affects the
availability status of a list of destinations at an SG. availability status of a list of destinations at an SG.
Mask: 8-bits (unsigned integer) Mask: 8-bits (unsigned integer)
The Mask field can be used to identify a contiguous range of The Mask field can be used to identify a contiguous range of
Affected Destination Point Codes. Identifying a contiguous range of Affected Destination Point Codes. Identifying a contiguous range
Affected DPCs may be useful when reception of an MTP3 management of Affected DPCs may be useful when reception of an MTP3
message or a linkset event simultaneously affects the availability management message or a linkset event simultaneously affects the
status of a series of destinations at an SG. availability status of a series of destinations at an SG.
The Mask parameter is an integer representing a bit mask that can be The Mask parameter is an integer representing a bit mask that can
applied to the related Affected PC field. The bit mask identifies be applied to the related Affected PC field. The bit mask
how many bits of the Affected PC field are significant and which are identifies how many bits of the Affected PC field are significant
effectively "wildcarded". For example, a mask of "8" indicates that and which are effectively "wildcarded". For example, a mask of
the last eight bits of the PC is "wildcarded". For an ANSI 24- "8" indicates that the last eight bits of the PC is "wildcarded".
bit Affected PC, this is equivalent to signalling that all PCs in For an ANSI 24-bit Affected PC, this is equivalent to signalling
an ANSI Cluster are unavailable. A mask of "3" indicates that the that all PCs in an ANSI Cluster are unavailable. A mask of "3"
last three bits of the PC is "wildcarded". For a 14-bit ITU indicates that the last three bits of the PC is "wildcarded". For
Affected PC, this is equivalent to signaling that an ITU a 14-bit ITU Affected PC, this is equivalent to signaling that an
ITU
Region is unavailable. A mask value equal (or greater than) the Region is unavailable. A mask value equal (or greater than) the
number of bits in the PC indicates that the entire network number of bits in the PC indicates that the entire network
appearance is affected - this is used to indicate network isolation appearance is affected - this is used to indicate network
to the ASP. isolation to the ASP.
INFO String: variable length INFO String: variable length
The optional INFO String parameter can carry any meaningful UTF-8 The optional INFO String parameter can carry any meaningful UTF-8
[10] character string along with the message. Length of the INFO [10] character string along with the message. Length of the INFO
String parameter is from 0 to 255 octets. No procedures are String parameter is from 0 to 255 octets. No procedures are
presently identified for its use but the INFO String MAY be used for presently identified for its use but the INFO String MAY be used
debugging purposes. for debugging purposes.
3.4.2 Destination Available (DAVA) 3.4.2 Destination Available (DAVA)
The DAVA message is sent from an SGP to all concerned ASPs to indicate The DAVA message is sent from an SGP to all concerned ASPs to
that the SG has determined that one or more SS7 destinations are now indicate that the SG has determined that one or more SS7 destinations
reachable (and not restricted), or in response to a DAUD message if are now reachable (and not restricted), or in response to a DAUD
appropriate. If the ASP M3UA layer previously had no routes to the message if appropriate. If the ASP M3UA layer previously had no
affected destinations the ASP MTP3-User protocol is informed and may routes to the affected destinations the ASP MTP3-User protocol is
now resume traffic to the affected destination. The ASP M3UA layer informed and may now resume traffic to the affected destination. The
now routes the MTP3-user traffic through the SG initiating the DAVA ASP M3UA layer now routes the MTP3-user traffic through the SG
message. initiating the DAVA message.
The DAVA message contains the following parameters: The DAVA message contains the following parameters:
Network Appearance Optional Network Appearance Optional
Routing Context Optional Routing Context Optional
Affected Point Code Mandatory Affected Point Code Mandatory
INFO String Optional INFO String Optional
The format and description of the Network Appearance, Routing Context, The format and description of the Network Appearance, Routing
Affected Point Code and INFO String parameters is the same as for the Context, Affected Point Code and INFO String parameters is the same
DUNA message (See Section 3.4.1). as for the DUNA message (See Section 3.4.1).
3.4.3 Destination State Audit (DAUD) 3.4.3 Destination State Audit (DAUD)
The DAUD message MAY be sent from the ASP to the SGP to audit the The DAUD message MAY be sent from the ASP to the SGP to audit the
availability/congestion state of SS7 routes from the SG to one availability/congestion state of SS7 routes from the SG to one or
or more affected destinations. more affected destinations.
The DAUD message contains the following parameters: The DAUD message contains the following parameters:
Network Appearance Optional Network Appearance Optional
Routing Context Optional Routing Context Optional
Affected Point Code Mandatory Affected Point Code Mandatory
INFO String Optional INFO String Optional
The format and description of DAUD Message parameters is the same as The format and description of DAUD Message parameters is the same as
for the DUNA message (See Section 3.4.1). for the DUNA message (See Section 3.4.1).
3.4.4 Signalling Congestion (SCON) 3.4.4 Signalling Congestion (SCON)
The SCON message can be sent from an SGP to all concerned ASPs to The SCON message can be sent from an SGP to all concerned ASPs to
indicate that an SG has determined that there is congestion in the indicate that an SG has determined that there is congestion in the
SS7 network to one or more destinations, or to an ASP in response to SS7 network to one or more destinations, or to an ASP in response to
a DATA or DAUD message as appropriate. For some MTP protocol variants a DATA or DAUD message as appropriate. For some MTP protocol
(e.g., ANSI MTP) the SCON message may be sent when the SS7 congestion variants (e.g., ANSI MTP) the SCON message may be sent when the SS7
level changes. The SCON message MAY also be sent from the M3UA layer of congestion level changes. The SCON message MAY also be sent from the
an ASP to an M3UA peer indicating that the M3UA layer or the ASP is M3UA layer of an ASP to an M3UA peer indicating that the M3UA layer
congested. or the ASP is congested.
The SCON message contains the following parameters: The SCON message contains the following parameters:
Network Appearance Optional Network Appearance Optional
Routing Context Optional Routing Context Optional
Affected Point Code Mandatory Affected Point Code Mandatory
Concerned Destination Optional Concerned Destination Optional
Congestion Indications Optional Congestion Indications Optional
INFO String Optional INFO String Optional
The format for SCON Message parameters is as follows: The format for SCON 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 = 0x0200 | Length =8 | | Tag = 0x0200 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Network Appearance | | Network Appearance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0006 | Length | | Tag = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ Routing Context / / Routing Context /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0012 | Length | | Tag = 0x0012 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mask | Affected PC 1 | | Mask | Affected PC 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ ... / / ... /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mask | Affected PC n | | Mask | Affected PC n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0206 | Length | | Tag = 0x0206 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| reserved | Concerned DPC | | reserved | Concerned DPC |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0205 | Length | | Tag = 0x0205 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | Cong. Level | | Reserved | Cong. Level |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | Length | | Tag = 0x0004 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ INFO String / / INFO String /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format and description of the Network Appearance, Routing The format and description of the Network Appearance, Routing
Context, Affected Point Code, and INFO String parameters is the same Context, Affected Point Code, and INFO String parameters is the same
as for the DUNA message (See Section 3.4.1). as for the DUNA message (See Section 3.4.1).
The Affected Point Code parameter can be used to indicate congestion The Affected Point Code parameter can be used to indicate congestion
of multiple destinations or ranges of destinations. of multiple destinations or ranges of destinations.
Concerned Destination: 32-bits Concerned Destination: 32-bits
The optional Concerned Destination parameter is only used if the The optional Concerned Destination parameter is only used if the
SCON message is sent from an ASP to the SGP. It contains the point SCON message is sent from an ASP to the SGP. It contains the point
code of the originator of the message that triggered the SCON code of the originator of the message that triggered the SCON
message. The Concerned Destination parameter contains one Concerned message. The Concerned Destination parameter contains one
Destination Point Code field, a three-octet parameter to allow for Concerned Destination Point Code field, a three-octet parameter to
14-, 16- and 24-bit binary formatted SS7 Point Codes. A Concerned allow for 14-, 16- and 24-bit binary formatted SS7 Point Codes. A
Point Code that is less than 24-bits is padded on the left to the Concerned Point Code that is less than 24-bits is padded on the
24-bit boundary. Any resulting Transfer Controlled (TFC) message left to the 24-bit boundary. Any resulting Transfer Controlled
from the SG is sent to the Concerned Point Code using the single (TFC) message from the SG is sent to the Concerned Point Code
Affected DPC contained in the SCON message to populate the using the single Affected DPC contained in the SCON message to
(affected) Destination field of the TFC message populate the (affected) Destination field of the TFC message
Congested Indications: 32-bits Congested Indications: 32-bits
The optional Congestion Indications parameter contains a Congestion The optional Congestion Indications parameter contains a
Level field. This optional parameter is used to communicate Congestion Level field. This optional parameter is used to
congestion levels in national MTP networks with multiple congestion communicate congestion levels in national MTP networks with
thresholds, such as in ANSI MTP3. For MTP congestion methods multiple congestion thresholds, such as in ANSI MTP3. For MTP
without multiple congestion levels (e.g., the ITU international congestion methods without multiple congestion levels (e.g., the
method) the parameter is not included. ITU international method) the parameter is not included.
Congestion Level field: 8-bits (unsigned integer) Congestion Level field: 8-bits (unsigned integer)
The Congestion Level field, associated with all of the Affected The Congestion Level field, associated with all of the Affected
DPC(s) in the Affected Destinations parameter, contains one of the DPC(s) in the Affected Destinations parameter, contains one of the
Following values: following values:
0 No Congestion or Undefined 0 No Congestion or Undefined
1 Congestion Level 1 1 Congestion Level 1
2 Congestion Level 2 2 Congestion Level 2
3 Congestion Level 3 3 Congestion Level 3
The congestion levels are defined in the congestion method in the The congestion levels are defined in the congestion method in the
appropriate national MTP recommendations [7,8]. appropriate national MTP recommendations [7,8].
3.4.5 Destination User Part Unavailable (DUPU) 3.4.5 Destination User Part Unavailable (DUPU)
The DUPU message is used by an SGP to inform concerned ASPs that a The DUPU message is used by an SGP to inform concerned ASPs that a
remote peer MTP3-User Part (e.g., ISUP or SCCP) at an SS7 node is remote peer MTP3-User Part (e.g., ISUP or SCCP) at an SS7 node is
unavailable. unavailable.
The DUPU message contains the following parameters: The DUPU message contains the following parameters:
Network Appearance Optional Network Appearance Optional
Routing Context Optional Routing Context Optional
Affected Point Code Mandatory Affected Point Code Mandatory
User/Cause Mandatory User/Cause Mandatory
INFO String Optional INFO String Optional
The format for DUPU message parameters is as follows: The format for DUPU 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 = 0x0200 | Length | | Tag = 0x0200 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Network Appearance | | Network Appearance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0006 | Length | | Tag = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ Routing Context / / Routing Context /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0012 | Length = 8 | | Tag = 0x0012 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mask = 0 | Affected PC | | Mask = 0 | Affected PC |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0204 | Length = 8 | | Tag = 0x0204 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Cause | User | | Cause | User |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | Length | | Tag = 0x0004 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ INFO String / / INFO String /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
User/Cause: 32-bits User/Cause: 32-bits
The Unavailability Cause and MTP3-User Identity fields, associated The Unavailability Cause and MTP3-User Identity fields, associated
with the Affected PC in the Affected Point Code parameter, are with the Affected PC in the Affected Point Code parameter, are
encoded as follows: encoded as follows:
Unavailability Cause field: 16-bits (unsigned integer) Unavailability Cause field: 16-bits (unsigned integer)
The Unavailability Cause parameter provides the reason for the The Unavailability Cause parameter provides the reason for the
unavailability of the MTP3-User. The valid values for the unavailability of the MTP3-User. The valid values for the
Unavailability Cause parameter are shown in the following table. Unavailability Cause parameter are shown in the following table.
The values agree with those provided in the SS7 MTP3 User Part The values agree with those provided in the SS7 MTP3 User Part
Unavailable message. Depending on the MTP3 protocol used in the Unavailable message. Depending on the MTP3 protocol used in the
Network Appearance, additional values may be used - the Network Appearance, additional values may be used - the
specification of the relevant MTP3 protocol variant/version specification of the relevant MTP3 protocol variant/version
recommendation is definitive. recommendation is definitive.
0 Unknown 0 Unknown
1 Unequipped Remote User 1 Unequipped Remote User
2 Inaccessible Remote User 2 Inaccessible Remote User
MTP3-User Identity field: 16-bits (unsigned integer) MTP3-User Identity field: 16-bits (unsigned integer)
The MTP3-User Identity describes the specific MTP3-User that is The MTP3-User Identity describes the specific MTP3-User that is
unavailable (e.g., ISUP, SCCP, ...). Some of the valid values for unavailable (e.g., ISUP, SCCP, ...). Some of the valid values for
the MTP3-User Identity are shown below. The values align with those the MTP3-User Identity are shown below. The values align with
provided in the SS7 MTP3 User Part Unavailable message and Service those provided in the SS7 MTP3 User Part Unavailable message and
Indicator. Depending on the MTP3 protocol variant/version used in Service Indicator. Depending on the MTP3 protocol variant/version
the network appearance, additional values may be used. The relevant used in the network appearance, additional values may be used.
MTP3 protocol variant/version recommendation is definitive. The relevant MTP3 protocol variant/version recommendation is
definitive.
0 to 2 Reserved 0 to 2 Reserved
3 SCCP 3 SCCP
4 TUP 4 TUP
5 ISUP 5 ISUP
6 to 8 Reserved 6 to 8 Reserved
9 Broadband ISUP 9 Broadband ISUP
10 Satellite ISUP 10 Satellite ISUP
11 Reserved 11 Reserved
12 AAL type 2 Signalling 12 AAL type 2 Signalling
13 Bearer Independent Call Control (BICC) 13 Bearer Independent Call Control (BICC)
14 Gateway Control Protocol 14 Gateway Control Protocol
15 Reserved 15 Reserved
The format and description of the Affected Point Code parameter is The format and description of the Affected Point Code parameter is
the same as for the DUNA message (See Section 3.4.1.) except that the same as for the DUNA message (See Section 3.4.1.) except that
the Mask field is not used and only a single Affected DPC is the Mask field is not used and only a single Affected DPC is
included. Ranges and lists of Affected DPCs cannot be signalled in included. Ranges and lists of Affected DPCs cannot be signaled in
a DUPU message, but this is consistent with UPU operation in the a DUPU message, but this is consistent with UPU operation in the
SS7 network. The Affected Destinations parameter in an MTP3 User SS7 network. The Affected Destinations parameter in an MTP3 User
Part Unavailable message (UPU) received by an SGP from the SS7 Part Unavailable message (UPU) received by an SGP from the SS7
network contains only one destination. network contains only one destination.
The format and description of the Network Appearance, Routing The format and description of the Network Appearance, Routing
Context, and INFO String parameters is the same as for the DUNA Context, and INFO String parameters is the same as for the DUNA
message (See Section 3.4.1). message (See Section 3.4.1).
3.4.6 Destination Restricted (DRST) 3.4.6 Destination Restricted (DRST)
The DRST message is optionally sent from the SGP to all concerned ASPs The DRST message is optionally sent from the SGP to all concerned
to indicate that the SG has determined that one or more SS7 ASPs to indicate that the SG has determined that one or more SS7
destinations are now restricted from the point of view of the SG, or destinations are now restricted from the point of view of the SG, or
in response to a DAUD message if appropriate. The M3UA layer at the ASP in response to a DAUD message if appropriate. The M3UA layer at the
is expected to send traffic to the affected destination via an ASP is expected to send traffic to the affected destination via an
alternate SG with route(s) of equal priority, but only if such an alternate SG with route(s) of equal priority, but only if such an
alternate route exists and is available. If the affected destination alternate route exists and is available. If the affected destination
is currently considered unavailable by the ASP, The MTP3-User should is currently considered unavailable by the ASP, The MTP3-User should
be informed that traffic to the affected destination can be resumed. be informed that traffic to the affected destination can be resumed.
In this case, the M3UA layer should route the traffic through the SG In this case, the M3UA layer should route the traffic through the SG
initiating the DRST message. initiating the DRST message.
This message is optional for the SG to send and it is optional for the This message is optional for the SG to send and it is optional for
ASP to act on any information received in the message. It is for use in the ASP to act on any information received in the message. It is for
the "STP" case described in Section 1.4.1. use in the "STP" case described in Section 1.4.1.
The DRST message contains the following parameters: The DRST message contains the following parameters:
Network Appearance Optional Network Appearance Optional
Routing Context Optional Routing Context Optional
Affected Point Code Mandatory Affected Point Code Mandatory
INFO String Optional INFO String Optional
The format and description of the Network Appearance, Routing Context, The format and description of the Network Appearance, Routing
Affected Point Code and INFO String parameters is the same as for the Context, Affected Point Code and INFO String parameters is the same
DUNA message (See Section 3.4.1). as for the DUNA message (See Section 3.4.1).
3.5 ASP State Maintenance (ASPSM) Messages 3.5 ASP State Maintenance (ASPSM) Messages
3.5.1 ASP Up 3.5.1 ASP Up
The ASP Up message is used to indicate to a remote M3UA peer that the The ASP Up message is used to indicate to a remote M3UA peer that the
adaptation layer is ready to receive any ASPSM/ASPTM messages adaptation layer is ready to receive any ASPSM/ASPTM messages for all
for all Routing Keys that the ASP is configured to serve. Routing Keys that the ASP is configured to serve.
The ASP Up message contains the following parameters: The ASP Up message contains the following parameters:
ASP Identifier Optional ASP Identifier Optional
INFO String Optional INFO String Optional
The format for ASP Up message parameters is as follows: The format for ASP Up 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 = 0x0011 | Length = 8 | | Tag = 0x0011 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ASP Identifier | | ASP Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | Length | | Tag = 0x0004 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ INFO String / / INFO String /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
ASP Identifier: 32-bit unsigned integer ASP Identifier: 32-bit unsigned integer
The optional ASP Identifier parameter contains a unique value that is The optional ASP Identifier parameter contains a unique value that
locally significant among the ASPs that support an AS. The SGP should is locally significant among the ASPs that support an AS. The SGP
save the ASP Identifier to be used, if necessary, with the Notify should save the ASP Identifier to be used, if necessary, with the
message (see Section 3.8.2). Notify message (see Section 3.8.2).
The format and description of the optional INFO String parameter is the The format and description of the optional INFO String parameter
same as for the DUNA message (See Section 3.4.1). is the same as for the DUNA message (See Section 3.4.1).
3.5.2 ASP Up Acknowledgement (ASP Up Ack) 3.5.2 ASP Up Acknowledgement (ASP Up Ack)
The ASP UP Ack message is used to acknowledge an ASP Up message The ASP UP Ack message is used to acknowledge an ASP Up message
received from a remote M3UA peer. received from a remote M3UA peer.
The ASP Up Ack message contains the following parameters: The ASP Up Ack message contains the following parameters:
INFO String (optional) INFO String (optional)
The format for ASP Up Ack message parameters is as follows: The format for ASP Up 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 =0x0004 | Length | | Tag =0x0004 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ INFO String / / INFO String /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format and description of the optional INFO String parameter is the The format and description of the optional INFO String parameter is
same as for the DUNA message (See Section 3.4.1). The INFO String in the same as for the DUNA message (See Section 3.4.1). The INFO
an ASP Up Ack message is independent from the INFO String in the ASP Up String in an ASP Up Ack message is independent from the INFO String
message (i.e., it does not have to echo back the INFO String received). in the ASP Up message (i.e., it does not have to echo back the INFO
String received).
3.5.3 ASP Down 3.5.3 ASP Down
The ASP Down message is used to indicate to a remote M3UA peer that the The ASP Down message is used to indicate to a remote M3UA peer that
adaptation layer is NOT ready to receive DATA, SSNM, RKM or ASPTM the adaptation layer is NOT ready to receive DATA, SSNM, RKM or ASPTM
messages. messages.
The ASP Down message contains the following parameters:
INFO String Optional The ASP Down message contains the following parameters:
The format for the ASP Down message parameters is as follows: INFO String Optional
The format for the ASP Down 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 =0x0004 | Length | | Tag =0x0004 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ INFO String / / INFO String /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format and description of the optional INFO String parameter is the The format and description of the optional INFO String parameter is
same as for the DUNA message (See Section 3.4.1). the same as for the DUNA message (See Section 3.4.1).
3.5.4 ASP Down Acknowledgement (ASP Down Ack) 3.5.4 ASP Down Acknowledgement (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 M3UA peer. received from a remote M3UA peer.
The ASP Down Ack message contains the following parameters: The ASP Down Ack message contains the following parameters:
INFO String Optional INFO String Optional
The format for the ASP Down Ack message parameters is as follows: The format for the ASP Down 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 = 0x0004 | Length | | Tag = 0x0004 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ INFO String / / INFO String /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format and description of the optional INFO String parameter is the The format and description of the optional INFO String parameter is
same as for the DUNA message (See Section 3.4.1). the same as for the DUNA message (See Section 3.4.1).
The INFO String in an ASP Down Ack message is independent from the INFO The INFO String in an ASP Down Ack message is independent from the
String in the ASP Down message (i.e., it does not have to echo back the INFO String in the ASP Down message (i.e., it does not have to echo
INFO String received). back the INFO String received).
3.5.5 Heartbeat (BEAT) 3.5.5 Heartbeat (BEAT)
The BEAT message is optionally used to ensure that the M3UA peers The BEAT message is optionally used to ensure that the M3UA peers are
are still available to each other. It is recommended for use when the still available to each other. It is recommended for use when the
M3UA runs over a transport layer other than the SCTP, which has its own M3UA runs over a transport layer other than the SCTP, which has its
heartbeat. own heartbeat.
The BEAT message contains the following parameters: The BEAT message contains the following parameters:
Heartbeat Data Optional Heartbeat Data Optional
The format for the BEAT message is as follows: The format for the BEAT message is as follows:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0009 | Length | | Tag = 0x0009 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ Heartbeat Data / / Heartbeat Data /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Heartbeat Data parameter contents are defined by the sending node. The Heartbeat Data parameter contents are defined by the sending
The Heartbeat Data could include, for example, a Heartbeat Sequence node. The Heartbeat Data could include, for example, a Heartbeat
Number and/or Timestamp. The receiver of a BEAT message does not Sequence Number and/or Timestamp. The receiver of a BEAT message
process this field as it is only of significance to the sender. The does not process this field as it is only of significance to the
receiver MUST respond with a BEAT Ack message. sender. The receiver MUST respond with a BEAT Ack message.
3.5.6 Heartbeat Acknowledgement (BEAT Ack) 3.5.6 Heartbeat Acknowledgement (BEAT Ack)
The BEAT Ack message is sent in response to a received BEAT The BEAT Ack message is sent in response to a received BEAT message.
message. It includes all the parameters of the received BEAT It includes all the parameters of the received BEAT message, without
message, without any change. any change.
3.6 Routing Key Management (RKM) Messages [Optional] 3.6 Routing Key Management (RKM) Messages [Optional]
3.6.1 Registration Request (REG REQ) 3.6.1 Registration Request (REG REQ)
The REG REQ message is sent by an ASP to indicate to a remote M3UA peer The REG REQ message is sent by an ASP to indicate to a remote M3UA
that it wishes to register one or more given Routing Keys with the peer that it wishes to register one or more given Routing Keys with
remote peer. Typically, an ASP would send this message to an SGP, and the remote peer. Typically, an ASP would send this message to an
expects to receive a REG RSP message in return with an associated SGP, and expects to receive a REG RSP message in return with an
Routing Context value. associated Routing Context value.
The REG REQ message contains the following parameters: The REG REQ message contains the following parameters:
Routing Key Mandatory Routing Key Mandatory
One or more Routing Key parameters MAY be included. The format for the One or more Routing Key parameters MAY be included. The format for
REG REQ message is as follows: 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 = 0x0207 | Length | | Tag = 0x0207 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ Routing Key 1 / / Routing Key 1 /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ ... / / ... /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0207 | Length | | Tag = 0x0207 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ Routing Key n / / Routing Key n /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Routing Key: variable length Routing Key: variable length
The Routing Key parameter is mandatory. The sender of this message The Routing Key parameter is mandatory. The sender of this message
expects that the receiver of this message will create a Routing expects that the receiver of this message will create a Routing
Key entry and assign a unique Routing Context value to it, if the Key entry and assign a unique Routing Context value to it, if the
Routing Key entry does not already exist. Routing Key entry does not already exist.
The Routing Key parameter may be present multiple times in the same The Routing Key parameter may be present multiple times in the
message. This is used to allow the registration of multiple Routing same message. This is used to allow the registration of multiple
Keys in a single message. Routing Keys in a single message.
The format of the Routing Key parameter is as follows. The format of the Routing Key parameter is as follows.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local-RK-Identifier | | Local-RK-Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Traffic Mode Type (optional) | | Traffic Mode Type (optional) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination Point Code | | Destination Point Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Network Appearance (optional) | | Network Appearance (optional) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Service Indicators (optional) | | Service Indicators (optional) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Originating Point Code List (optional) | | Originating Point Code List (optional) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Circuit Range List (optional) | | Circuit Range List (optional) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ ... / / ... /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination Point Code | | Destination Point Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Service Indicators (optional) | | Service Indicators (optional) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Originating Point Code List (optional) | | Originating Point Code List (optional) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Circuit Range List (optional) | | Circuit Range List (optional) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Note: The Destination Point Code, Service Indicators, Originating Point Note: The Destination Point Code, Service Indicators, Originating
Code List and Circuit Range List parameters MAY be repeated as a Point Code List and Circuit Range List parameters MAY be repeated
grouping within the Routing Key parameter, in the structure shown above. as a grouping within the Routing Key parameter, in the structure
shown above.
Local-RK-Identifier: 32-bit integer Local-RK-Identifier: 32-bit unsigned integer
The mandatory Local-RK-Identifier field is used to uniquely identify The mandatory Local-RK-Identifier field is used to uniquely
the registration request. The Identifier value is assigned by the identify the registration request. The Identifier value is
ASP, and is used to correlate the response in an REG RSP message assigned by the ASP, and is used to correlate the response in an
with the original registration request. The Identifier value must REG RSP message with the original registration request. The
remain unique until the REG RSP message is received. Identifier value must remain unique until the REG RSP message is
received.
The format of the Local-RK-Identifier field is as follows: The format of the Local-RK-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 = 0x020a | Length = 8 | | Tag = 0x020a | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local-RK-Identifier value | | Local-RK-Identifier value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Traffic Mode Type: 32-bit (unsigned integer) Traffic Mode Type: 32-bit (unsigned integer)
The optional Traffic Mode Type parameter identifies the traffic mode The optional Traffic Mode Type parameter identifies the traffic mode
of operation of the ASP(s) within an Application Server. The format of operation of the ASP(s) within an Application Server. The format
of the Traffic Mode Type Identifier is as follows: of the Traffic Mode Type Identifier 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 = 0x000b | Length = 8 | | Tag = 0x000b | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Traffic Mode Type | | Traffic Mode Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The valid values for Traffic Mode Type are shown in the The valid values for Traffic Mode Type are shown in the following
following table: table:
1 Override 1 Override
2 Loadshare 2 Loadshare
3 Broadcast 3 Broadcast
Destination Point Code: Destination Point Code:
The Destination Point Code parameter is mandatory, and identifies The Destination Point Code parameter is mandatory, and identifies
the Destination Point Code of incoming SS7 traffic for which the ASP the Destination Point Code of incoming SS7 traffic for which the
is registering. The format is the same as described for the ASP is registering. The format is the same as described for the
Affected Destination parameter in the DUNA message (See Section Affected Destination parameter in the DUNA message (See Section
3.4.1). Its format is: 3.4.1). Its format is:
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 = 0x020b | Length = 8 | | Tag = 0x020b | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mask = 0 | Destination Point Code | | Mask = 0 | Destination Point Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Network Appearance: Network Appearance:
The optional Network Appearance parameter field identifies the SS7 The optional Network Appearance parameter field identifies the SS7
network context for the Routing Key, and has the same format as in network context for the Routing Key, and has the same format as in
the DATA message (See Section 3.3.1). The absence of the Network the DATA message (See Section 3.3.1). The absence of the Network
Appearance parameter in the Routing Key indicates the use Appearance parameter in the Routing Key indicates the use of any
of any Network Appearance value, Its format is: Network Appearance value. Its format is:
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 = 0x0200 | Length = 8 | | Tag = 0x0200 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Network Appearance | | Network Appearance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Service Indicators (SI): n X 8-bit integers Service Indicators (SI): n X 8-bit integers
The optional SI field contains one or more Service Indicators from The optional SI [7,8] field contains one or more Service
the values as described in the MTP3-User Identity field of the DUPU Indicators from the values as described in the MTP3-User Identity
message. The absence of the SI parameter in the Routing Key field of the DUPU message. The absence of the SI parameter in the
indicates the use of any SI value, excluding of course MTP Routing Key indicates the use of any SI value, excluding of course
management. Where an SI parameter does not contain a multiple of MTP management. Where an SI parameter does not contain a multiple
four SIs, the parameter is padded out to 32-byte alignment. of four SIs, the parameter is padded out to 32-byte alignment.
The SI format is: The SI format is:
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 = 0x020c | Length | | Tag = 0x020c | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SI #1 | SI #2 | SI #3 | SI #4 | | SI #1 | SI #2 | SI #3 | SI #4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ ... / / ... /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SI #n | 0 Padding, if necessary | | SI #n | 0 Padding, if necessary |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
OPC List: OPC List:
The Originating Point Code List parameter contains one or more SS7 The Originating Point Code List parameter contains one or more SS7
OPC entries, and its format is the same as the Destination Point OPC entries, and its format is the same as the Destination Point
Code parameter. The absence of the OPC List parameter in the Code parameter. The absence of the OPC List parameter in the
Routing Key indicates the use of any OPC value, Routing Key indicates the use of any OPC value,
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 = 0x020e | Length | | Tag = 0x020e | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mask = 0 | Origination Point Code #1 | | Mask = 0 | Origination Point Code #1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mask = 0 | Origination Point Code #2 | | Mask = 0 | Origination Point Code #2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ ... / / ... /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mask = 0 | Origination Point Code #n | | Mask = 0 | Origination Point Code #n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Circuit Range: Circuit Range:
An ISUP controlled circuit is uniquely identified by the SS7 OPC, An ISUP controlled circuit is uniquely identified by the SS7 OPC,
DPC and CIC value. For the purposes of identifying Circuit Ranges DPC and CIC value. For the purposes of identifying Circuit Ranges
in an M3UA Routing Key, the optional Circuit Range parameter in an M3UA Routing Key, the optional Circuit Range parameter
includes one or more circuit ranges, each identified by an OPC and includes one or more circuit ranges, each identified by an OPC and
Upper/Lower CIC value. The DPC is implicit as it is mandatory and Upper/Lower CIC value. The DPC is implicit as it is mandatory and
already included in the DPC parameter of the Routing Key. The already included in the DPC parameter of the Routing Key. The
absence of the Circuit Range parameter in the Routing Key indicates absence of the Circuit Range parameter in the Routing Key
the use of any Circuit Range values, in the case of ISUP/TUP indicates the use of any Circuit Range values, in the case of
traffic. The Origination Point Code is encoded the same as the ISUP/TUP traffic. The Origination Point Code is encoded the same
Destination Point Code parameter, while the CIC values are 16-bit as the Destination Point Code parameter, while the CIC values are
integers. 16-bit integers.
The Circuit Range format is as follows: The Circuit Range format is as follows:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x020f | Length | | Tag = 0x020f | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mask = 0 | Origination Point Code #1 | | Mask = 0 | Origination Point Code #1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Lower CIC Value #1 | Upper CIC Value #1 | | Lower CIC Value #1 | Upper CIC Value #1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mask = 0 | Origination Point Code #2 | | Mask = 0 | Origination Point Code #2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Lower CIC Value #2 | Upper CIC Value #2 | | Lower CIC Value #2 | Upper CIC Value #2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ ... / / ... /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mask = 0 | Origination Point Code #n | | Mask = 0 | Origination Point Code #n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Lower CIC Value #n | Upper CIC Value #n | | Lower CIC Value #n | Upper CIC Value #n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3.6.2 Registration Response (REG RSP) 3.6.2 Registration Response (REG RSP)
The REG RSP message is used as a response to the REG REQ message from a The REG RSP message is used as a response to the REG REQ message from
remote M3UA peer. It contains indications of success/failure for a remote M3UA peer. It contains indications of success/failure for
registration requests and returns a unique Routing Context value for registration requests and returns a unique Routing Context value for
successful registration requests, to be used in subsequent M3UA Traffic successful registration requests, to be used in subsequent M3UA
Management protocol. Traffic Management protocol.
The REG RSP message contains the following parameters: The REG RSP message contains the following parameters:
Registration Result Mandatory Registration Result Mandatory
One or more Registration Result parameters MUST be included. The format One or more Registration Result parameters MUST be included. The
for the REG RSP message is as follows: 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 = 0x0208 | Length | | Tag = 0x0208 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Registration Result 1 | | Registration Result 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ ... / / ... /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0208 | Length | | Tag = 0x0208 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Registration Result n | | Registration Result n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Registration Results: Registration Results:
The Registration Result parameter contains the registration result The Registration Result parameter contains the registration result
for a single Routing Key in an REG REQ message. The number of for a single Routing Key in an REG REQ message. The number of
results in a single REG RSP message MUST be anywhere from one to results in a single REG RSP message MUST be anywhere from one to
the total number of number of Routing Key parameters found in the the total number of number of Routing Key parameters found in the
corresponding REG REQ message. Where multiple REG RSP messages are corresponding REG REQ message. Where multiple REG RSP messages
used in reply to REG REQ message, a specific result SHOULD be in are used in reply to REG REQ message, a specific result SHOULD be
only one REG RSP message. The format of each result is as follows: in only one REG RSP message. The format of each result is as
follows:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x020a | Length = 8 | | Tag = 0x020a | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local-RK-Identifier value | | Local-RK-Identifier value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0212 | Length = 8 | | Tag = 0x0212 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Registration Status | | Registration Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0006 | Length = 8 | | Tag = 0x0006 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Routing Context | | Routing Context |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Local-RK-Identifier: 32-bit integer Local-RK-Identifier: 32-bit integer
The Local-RK-Identifier contains the same value as found in the The Local-RK-Identifier contains the same value as found in the
matching Routing Key parameter found in the REG REQ message (See matching Routing Key parameter found in the REG REQ message (See
Section 3.5.5.1). Section 3.6.1).
Registration Status: 32-bit integer Registration Status: 32-bit integer
The Registration Result Status field indicates the success or the The Registration Result Status field indicates the success or the
reason for failure of a registration request. reason for failure of a registration request.
Its values may be: Its values may be:
0 Successfully Registered 0 Successfully Registered
1 Error - Unknown 1 Error - Unknown
2 Error - Invalid DPC 2 Error - Invalid DPC
3 Error - Invalid Network Appearance 3 Error - Invalid Network Appearance
4 Error - Invalid Routing Key 4 Error - Invalid Routing Key
5 Error - Permission Denied 5 Error - Permission Denied
6 Error - Cannot Support Unique Routing 6 Error - Cannot Support Unique Routing
7 Error - Routing Key not Currently Provisioned 7 Error - Routing Key not Currently Provisioned
8 Error - Insufficient Resources 8 Error - Insufficient Resources
9 Error - Unsupported RK parameter Field 9 Error - Unsupported RK parameter Field
10 Error - Unsupported/Invalid Traffic Handling Mode 10 Error - Unsupported/Invalid Traffic Handling Mode
Routing Context: 32-bit integer Routing Context: 32-bit integer
The Routing Context field contains the Routing Context value for the The Routing Context field contains the Routing Context value for
associated Routing Key if the registration was successful. It is set the associated Routing Key if the registration was successful. It
to "0" if the registration was not successful. is set to "0" if the registration was not successful.
3.6.3 Deregistration Request (DEREG REQ) 3.6.3 Deregistration Request (DEREG REQ)
The DEREG REQ message is sent by an ASP to indicate to a remote M3UA The DEREG REQ message is sent by an ASP to indicate to a remote M3UA
peer that it wishes to deregister a given Routing Key. Typically, an peer that it wishes to deregister a given Routing Key. Typically, an
ASP would send this message to an SGP, and expects to receive a DEREG ASP would send this message to an SGP, and expects to receive a DEREG
RSP message in return with the associated Routing Context value. RSP message in return with the associated Routing Context value.
The DEREG REQ message contains the following parameters: The DEREG REQ message contains the following parameters:
Routing Context Mandatory Routing Context 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 = 0x0006 | Length | | Tag = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ Routing Context / / Routing Context /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Routing Context: n X 32-bit integers Routing Context: n X 32-bit integers
The Routing Context parameter contains (a list of) integers indexing The Routing Context parameter contains (a list of) integers
the Application Server traffic that the sending ASP is currently indexing the Application Server traffic that the sending ASP is
registered to receive from the SGP but now wishes to deregister. currently registered to receive from the SGP but now wishes to
deregister.
3.6.4 Deregistration Response (DEREG RSP) 3.6.4 Deregistration 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 M3UA peer. from a remote M3UA peer.
The DEREG RSP message contains the following parameters: The DEREG RSP message contains the following parameters:
Deregistration Result Mandatory Deregistration Result Mandatory
One or more Deregistration Result parameters MUST be included. The One or more Deregistration Result parameters MUST be included. The
format for the DEREG RSP message is as follows: 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 = 0x0209 | Length | | Tag = 0x0209 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Deregistration Result 1 | | Deregistration Result 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ ... / / ... /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0209 | Length | | Tag = 0x0209 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Deregistration Result n | | Deregistration Result n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Deregistration Results: Deregistration Results:
The Deregistration Result parameter contains the deregistration The Deregistration Result parameter contains the deregistration
status for a single Routing Context in a DEREG REQ message. The status for a single Routing Context in a DEREG REQ message. The
number of results in a single DEREG RSP message MAY be anywhere from number of results in a single DEREG RSP message MAY be anywhere
one to the total number of number of Routing Context values found in from one to the total number of number of Routing Context values
the corresponding REG REQ message. Where multiple DEREG RSP messages found in the corresponding DEREG REQ message.
are used in reply to DEREG REQ message, a specific result SHOULD be
in only one DEREG RSP message. The format of each result is as
follows:
0 1 2 3 Where multiple DEREG RSP messages are used in reply to DEREG REQ
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 message, a specific result SHOULD be in only one DEREG RSP
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ message. The format of each result is as follows:
| Tag = 0x0006 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Routing Context |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0213 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Deregistration Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Routing Context: 32-bit integer 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0006 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Routing Context |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0213 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Deregistration Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Routing Context field contains the Routing Context value of the Routing Context: 32-bit integer
matching Routing Key to deregister, as found in the DEREG REQ
message.
Deregistration Status: 32-bit integer The Routing Context field contains the Routing Context value of
the matching Routing Key to deregister, as found in the DEREG REQ
message.
The Deregistration Result Status field indicates the success or the Deregistration Status: 32-bit integer
reason for failure of the deregistration.
Its values may be: The Deregistration Result Status field indicates the success or
0 Successfully Deregistered the reason for failure of the deregistration.
1 Error - Unknown
2 Error - Invalid Routing Context Its values may be:
3 Error - Permission Denied
4 Error - Not Registered 0 Successfully Deregistered
5 Error - ASP Currently Active for Routing Context 1 Error - Unknown
2 Error - Invalid Routing Context
3 Error - Permission Denied
4 Error - Not Registered
5 Error - ASP Currently Active for Routing Context
3.7 ASP Traffic Maintenance (ASPTM) Messages 3.7 ASP Traffic Maintenance (ASPTM) Messages
3.7.1 ASP Active 3.7.1 ASP Active
The ASP Active message is sent by an ASP to indicate to a remote M3UA The ASP Active message is sent by an ASP to indicate to a remote M3UA
peer that it is ready to process signalling traffic for a particular peer that it is ready to process signalling traffic for a particular
Application Server. The ASP Active message affects only the ASP state Application Server. The ASP Active message affects only the ASP
for the Routing Keys identified by the Routing Contexts, if present. state for the Routing Keys identified by the Routing Contexts, if
present.
The ASP Active message contains the following parameters: The ASP Active message contains the following parameters:
Traffic Mode Type Optional Traffic Mode Type Optional
Routing Context Optional Routing Context Optional
INFO String Optional INFO String Optional
The format for the ASP Active message is as follows: The format for the ASP Active 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 = 0x000b | Length = 8 | | Tag = 0x000b | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Traffic Mode Type | | Traffic Mode Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0006 | Length | | Tag = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ Routing Context / / Routing Context /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | Length | | Tag = 0x0004 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ INFO String / / INFO String /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Traffic Mode Type: 32-bit (unsigned integer) Traffic Mode Type: 32-bit (unsigned integer)
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 Traffic Mode operation of the ASP within an AS. The valid values for Traffic
Type are shown in the following table: Mode Type are shown in the following table:
1 Override 1 Override
2 Loadshare 2 Loadshare
3 Broadcast 3 Broadcast
Within a particular Routing Context, Override, Loadshare and Within a particular Routing Context, Override, Loadshare and
Broadcast SHOULD NOT be mixed. The Override value indicates that Broadcast SHOULD NOT be mixed. The Override value indicates that
the ASP is operating in Override mode, and the ASP takes over all the ASP is operating in Override mode, and the ASP takes over all
traffic in an Application Server (i.e., primary/backup operation), traffic in an Application Server (i.e., primary/backup operation),
overriding any currently active ASPs in the AS. In Loadshare mode, overriding any currently active ASPs in the AS. In Loadshare
the ASP will share in the traffic distribution with any other mode, the ASP will share in the traffic distribution with any
currently active ASPs. In Broadcast mode, the ASP will receive the other currently active ASPs. In Broadcast mode, the ASP will
same messages as any other currently active ASP. receive the same messages as any other currently active ASP.
Routing Context: n X 32-bit integers Routing Context: n X 32-bit integers
The optional Routing Context parameter contains (a list of) integers The optional Routing Context parameter contains (a list of)
indexing the Application Server traffic that the sending ASP is integers indexing the Application Server traffic that the sending
configured/registered to receive. ASP is configured/registered to receive.
There is one-to-one relationship between an index entry and an SGP There is one-to-one relationship between an index entry and an SGP
Routing Key or AS Name. Because an AS can only appear in one Routing Key or AS Name. Because an AS can only appear in one
Network Appearance, the Network Appearance parameter is not required Network Appearance, the Network Appearance parameter is not
in the ASP Active message. required in the ASP Active message.
An Application Server Process may be configured to process traffic An Application Server Process may be configured to process traffic
for more than one logical Application Server. From the perspective for more than one logical Application Server. From the
of an ASP, a Routing Context defines a range of signalling traffic perspective of an ASP, a Routing Context defines a range of
that the ASP is currently configured to receive from the SGP. For signalling traffic that the ASP is currently configured to receive
example, an ASP could be configured to support call processing for from the SGP. For example, an ASP could be configured to support
multiple ranges of PSTN trunks and therefore receive related call processing for multiple ranges of PSTN trunks and therefore
signalling traffic, identified by separate SS7 DPC/OPC/CIC ranges. receive related signalling traffic, identified by separate SS7
DPC/OPC/CIC ranges.
The format and description of the optional INFO String parameter is the The format and description of the optional INFO String parameter is
same as for the DUNA message (See Section 3.4.1). the same as for the DUNA message (See Section 3.4.1).
3.7.2 ASP Active Acknowledgement (ASP Active Ack) 3.7.2 ASP Active Acknowledgement (ASP Active Ack)
The ASP Active Ack message is used to acknowledge an ASP Active message The ASP Active Ack message is used to acknowledge an ASP Active
received from a remote M3UA peer. message received from a remote M3UA peer.
The ASP Active Ack message contains the following parameters: The ASP Active Ack message contains the following parameters:
Traffic Mode Type Optional Traffic Mode Type Optional
Routing Context Optional Routing Context Optional
INFO String Optional INFO String Optional
The format for the ASP Active Ack message is as follows: The format for the ASP Active 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 = 0x000b | Length = 8 | | Tag = 0x000b | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Traffic Mode Type | | Traffic Mode Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0006 | Length | | Tag = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ Routing Context / / Routing Context /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | Length | | Tag = 0x0004 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ INFO String / / INFO String /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format and description of the optional INFO String parameter is the The format and description of the optional INFO String parameter is
same as for the DUNA message (See Section 3.4.1). the same as for the DUNA message (See Section 3.4.1).
The INFO String in an ASP Active Ack message is independent from the The INFO String in an ASP Active Ack message is independent from the
INFO String in the ASP Active message (i.e., it does not have to echo INFO String in the ASP Active message (i.e., it does not have to echo
back the INFO String received). back the INFO String received).
The format of the Traffic Mode Type and Routing Context parameters is The format of the Traffic Mode Type and Routing Context parameters is
the same as for the ASP Active message. (See Section 3.5.5). the same as for the ASP Active message. (See Section 3.7.1).
3.7.3 ASP Inactive 3.7.3 ASP Inactive
The ASP Inactive message is sent by an ASP to indicate to a remote M3UA The ASP Inactive message is sent by an ASP to indicate to a remote
peer that it is no longer an active ASP to be used from within a list of M3UA peer that it is no longer an active ASP to be used from within a
ASPs. The ASP Inactive message affects only the ASP state in the list of ASPs. The ASP Inactive message affects only the ASP state in
Routing Keys identified by the Routing Contexts, if present. the Routing Keys identified by the Routing Contexts, if present.
The ASP Inactive message contains the following parameters: The ASP Inactive message contains the following parameters:
Routing Context Optional Routing Context Optional
INFO String Optional INFO String Optional
The format for the ASP Inactive message parameters is as follows: The format for the ASP Inactive 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 = 0x0006 | Length | | Tag = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ Routing Context / / Routing Context /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | Length | | Tag = 0x0004 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ INFO String / / INFO String /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format and description of the optional Routing Context and INFO The format and description of the optional Routing Context and INFO
String parameters is the same as for the ASP Active message (See String parameters is the same as for the ASP Active message (See
Section 3.5.5.) Section 3.5.5.)
3.7.4 ASP Inactive Acknowledgement (ASP Inactive Ack) 3.7.4 ASP Inactive Acknowledgement (ASP Inactive Ack)
The ASP Inactive Ack message is used to acknowledge an ASP Inactive The ASP Inactive Ack message is used to acknowledge an ASP Inactive
message received from a remote M3UA peer. message received from a remote M3UA peer.
The ASP Inactive Ack message contains the following parameters: The ASP Inactive Ack message contains the following parameters:
Routing Context Optional Routing Context Optional
INFO String Optional INFO String Optional
The format for the ASP Inactive Ack message is as follows: The format for the ASP Inactive 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 = 0x0006 | Length | | Tag = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ Routing Context / / Routing Context /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | Length | | Tag = 0x0004 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ INFO String / / INFO String /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format and description of the optional INFO String parameter is the The format and description of the optional INFO String parameter is
same as for the DUNA message (See Section 3.4.1.) the same as for the DUNA message (See Section 3.4.1.)
The INFO String in an ASP Inactive Ack message is independent from the The INFO String in an ASP Inactive Ack message is independent from
INFO String in the ASP Inactive message (i.e., it does not have to echo the INFO String in the ASP Inactive message (i.e., it does not have
back the INFO String received). to echo back the INFO String received).
The format of the Routing Context parameter is the same as for the ASP The format of the Routing Context parameter is the same as for the
Inactive message. (See Section 3.5.7). ASP Inactive message. (See Section 3.7.3).
3.8 Management (MGMT) Messages 3.8 Management (MGMT) Messages
3.8.1 Error 3.8.1 Error
The Error message is used to notify a peer of an error event associated The Error message is used to notify a peer of an error event
with an incoming message. For example, the message type might be associated with an incoming message. For example, the message type
unexpected given the current state, or a parameter value might be might be unexpected given the current state, or a parameter value
invalid. might be invalid.
The Error message contains the following parameters: The Error message contains the following parameters:
Error Code Mandatory Error Code Mandatory
Routing Context Mandatory* Routing Context Mandatory*
Network Appearance Mandatory* Network Appearance Mandatory*
Affected Point Code Mandatory* Affected Point Code Mandatory*
Diagnostic Information Optional Diagnostic Information Optional
(*) Only mandatory for specific Error Codes (*) Only mandatory for specific Error Codes
The format for the Error message is as follows:
0 1 2 3 The format for the Error message is as follows:
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x000c | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Error Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag - 0x0012 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mask | Affected Point Code 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ ... /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mask | Affected Point Code n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0200 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Network Appearance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0007 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ Diagnostic Information /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Error Code: 32-bits (unsigned integer) 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x000c | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Error Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag - 0x0012 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mask | Affected Point Code 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ ... /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mask | Affected Point Code n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0200 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Network Appearance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0007 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ Diagnostic Information /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Error Code parameter indicates the reason for the Error Message. Error Code: 32-bits (unsigned integer)
The Error parameter value can be one of the following values:
0x01 Invalid Version The Error Code parameter indicates the reason for the Error
0x02 Not Used in M3UA Message. The Error parameter value can be one of the following
0x03 Unsupported Message Class values:
0x04 Unsupported Message Type
0x05 Unsupported Traffic Handling Mode
0x06 Unexpected Message
0x07 Protocol Error
0x08 Not used in M3UA
0x09 Invalid Stream Identifier
0x0a Not used in M3UA
0x0b Not used in M3UA
0x0c Not used in M3UA
0x0d Refused - Management Blocking
0x0e ASP Identifier Required
0x0f Invalid ASP Identifier
0x10 Not Used in M3UA
0x11 Invalid Parameter Value
0x12 Parameter Field Error
0x13 Unexpected Parameter
0x14 Destination Status Unknown
0x15 Invalid Network Appearance
0x16 Missing Parameter
0x17 Not Used in M3UA
0x18 Not Used in M3UA
0x19 Invalid Routing Context
0x1a No Configured AS for ASP
The "Invalid Version" error is sent if a message was received with an 0x01 Invalid Version
invalid or unsupported version. The Error message contains the 0x02 Not Used in M3UA
supported version in the Common header. The Error message could 0x03 Unsupported Message Class
optionally provide the supported version in the Diagnostic Information 0x04 Unsupported Message Type
area. 0x05 Unsupported Traffic Mode Type
0x06 Unexpected Message
0x07 Protocol Error
0x08 Not used in M3UA
0x09 Invalid Stream Identifier
0x0a Not used in M3UA
0x0b Not used in M3UA
0x0c Not used in M3UA
0x0d Refused - Management Blocking
0x0e ASP Identifier Required
0x0f Invalid ASP Identifier
0x10 Not Used in M3UA
0x11 Invalid Parameter Value
0x12 Parameter Field Error
0x13 Unexpected Parameter
0x14 Destination Status Unknown
0x15 Invalid Network Appearance
0x16 Missing Parameter
0x17 Not Used in M3UA
0x18 Not Used in M3UA
0x19 Invalid Routing Context
0x1a No Configured AS for ASP
The "Unsupported Message Class" error is sent if a message with an The "Invalid Stream Identifier" error is sent if a message is
unexpected or unsupported Message Class is received. received on an unexpected SCTP stream (e.g., a MGMT message was
received on a stream other than "0"). Error messages MUST NOT be
generated in response to other Error messages.
The "Unsupported Message Type" error is sent if a message with an The "Unsupported Message Class" error is sent if a message with an
unexpected or unsupported Message Type is received. unexpected or unsupported Message Class is received.
The "Unsupported Traffic Handling Mode" error is sent by a SGP The "Unsupported Message Type" error is sent if a message with an
if an ASP sends an ASP Active message with an unsupported Traffic Mode unexpected or unsupported Message Type is received.
Type or a Traffic Mode Type that is inconsistent with the presently
configured mode for the Application Server. An example would be a case
in which the SGP did not support loadsharing.
The "Unexpected Message" error MAY be sent if a defined and recognized The "Unsupported Traffic Mode Type" error is sent by a SGP if an ASP
message is received that is not expected in the current state (in some sends an ASP Active message with an unsupported Traffic Mode Type or
cases the ASP may optionally silently discard the message and not send a Traffic Mode Type that is inconsistent with the presently
an Error message). For example, silent discard is used by an ASP if it configured mode for the Application Server. An example would be a
received a DATA message from an SGP while it was in the ASP-INACTIVE case in which the SGP did not support loadsharing.
state. If the Unexpected message contained Routing Context(s), the
Routing Context(s) SHOULD be included in the Error message.
The "Protocol Error" error is sent for any protocol anomaly (i.e., The "Unexpected Message" error MAY be sent if a defined and
reception of a parameter that is syntactically correct but unexpected recognized message is received that is not expected in the current
in the current situation. state (in some cases the ASP may optionally silently discard the
message and not send an Error message). For example, silent discard
is used by an ASP if it received a DATA message from an SGP while it
was in the ASP-INACTIVE state. If the Unexpected message contained
Routing Context(s), the Routing Context(s) SHOULD be included in the
Error message.
The "Invalid Stream Identifier" error is sent if a message is received The "Protocol Error" error is sent for any protocol anomaly (i.e.,
on an unexpected SCTP stream (e.g., a Management message was received reception of a parameter that is syntactically correct but unexpected
on a stream other than "0"). in the current situation.
The "Refused - Management Blocking" error is sent when an ASP Up or The "Invalid Stream Identifier" error is sent if a message is
ASP Active message is received and the request is refused for received on an unexpected SCTP stream (e.g., a Management message was
management reasons (e.g., management lockout"). If this error is in received on a stream other than "0").
response to an ASP Active message, the Routing Context(s) in the ASP
Active message SHOULD be included in the Error message.
The "ASP Identifier Required" is sent by a SGP in response The "Refused - Management Blocking" error is sent when an ASP Up or
to an ASP Up message which does not contain an ASP Identifier ASP Active message is received and the request is refused for
parameter when the SGP requires one. The ASP SHOULD resend the management reasons (e.g., management lockout"). If this error is in
ASP Up message with an ASP Identifier. response to an ASP Active message, the Routing Context(s) in the ASP
Active message SHOULD be included in the Error message.
The "Invalid ASP Identifier" is send by a SGP in response The "ASP Identifier Required" is sent by a SGP in response to an ASP
to an ASP Up message with an invalid (i.e., non-unique) ASP Identifier. Up message which does not contain an ASP Identifier parameter when
the SGP requires one. The ASP SHOULD resend the ASP Up message with
an ASP Identifier.
The "Invalid Parameter Value " error is sent if a message is received The "Invalid ASP Identifier" is sent by an SGP in response to an ASP
with an invalid parameter value (e.g., a DUPU message was received with Up message with an invalid (i.e., non-unique) ASP Identifier.
a Mask value other than "0".
The "Parameter Field Error" would be sent if a message is received The "Invalid Parameter Value " error is sent if a message is received
with a parameter having a wrong length field. with an invalid parameter value (e.g., a DUPU message was received
with a Mask value other than "0".
The "Unexpected Parameter" error would be sent if a message contains The "Parameter Field Error" would be sent if a message is received
an invalid parameter. with a parameter having a wrong length field.
The "Destination Status Unknown" Error MAY be sent if a DAUD is The "Unexpected Parameter" error would be sent if a message contains
received at an SG enquiring of the availability/congestion status of an invalid parameter.
a destination, and the SG does not wish to provide the status (e.g.,
the sender is not authorized to know the status). For this error, the
invalid or unauthorized Point Code(s) MUST be included along with the
Network Appearance and/or Routing Context associated with the Point
Code(s).
The "Invalid Network Appearance" error is sent by a SGP if an ASP sends The "Destination Status Unknown" Error MAY be sent if a DAUD is
a message with an invalid (unconfigured) Network Appearance value. received at an SG enquiring of the availability/congestion status of
For this error, the invalid (unconfigured) Network Appearance MUST be a destination, and the SG does not wish to provide the status (e.g.,
included in the Network Appearance parameter. the sender is not authorized to know the status). For this error,
the invalid or unauthorized Point Code(s) MUST be included along with
the Network Appearance and/or Routing Context associated with the
Point Code(s).
The "Missing Parameter" error would be sent if a mandatory parameter The "Invalid Network Appearance" error is sent by a SGP if an ASP
were not included in a message. sends a message with an invalid (unconfigured) Network Appearance
value. For this error, the invalid (unconfigured) Network Appearance
MUST be included in the Network Appearance parameter.
The "Invalid Routing Context" error is sent if a message is received The "Missing Parameter" error would be sent if a mandatory parameter
from a peer with an invalid (unconfigured) Routing Context value. For were not included in a message.
this error, the invalid Routing Context(s) MUST be included in the Error
message.
The "No Configured AS for ASP" error is sent if a message is received The "Invalid Routing Context" error is sent if a message is received
from a peer without a Routing Context parameter and it is not known by from a peer with an invalid (unconfigured) Routing Context value.
configuration data which Application Servers are referenced. For this error, the invalid Routing Context(s) MUST be included in
the Error message.
Diagnostic Information: variable length The "No Configured AS for ASP" error is sent if a message is received
from a peer without a Routing Context parameter and it is not known
by configuration data which Application Servers are referenced.
When included, the optional Diagnostic information can be any Diagnostic Information: variable length
information germane to the error condition, to assist in
identification of the error condition. The Diagnostic information
SHOULD contain the offending message.
Error messages MUST NOT be generated in response to other Error When included, the optional Diagnostic information can be any
messages. information germane to the error condition, to assist in
identification of the error condition. The Diagnostic information
SHOULD contain the offending message.
3.8.2 Notify 3.8.2 Notify
The Notify message used to provide an autonomous indication of M3UA The Notify message used to provide an autonomous indication of M3UA
events to an M3UA peer. events to an M3UA peer.
The Notify message contains the following parameters: The Notify message contains the following parameters:
Status Mandatory Status Mandatory
ASP Identifier Optional ASP Identifier Optional
Routing Context Optional Routing Context Optional
INFO String Optional INFO String Optional
The format for the Notify message is as follows: The format for the Notify 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 = 0x000d | Length = 8 | | Tag = 0x000d | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Status Type | Status Information | | Status Type | Status Information |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0011 | Length | | Tag = 0x0011 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ASP Identifier | | ASP Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0006 | Length | | Tag = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ Routing Context / / Routing Context /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | Length | | Tag = 0x0004 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ INFO String / / INFO String /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Status Type: 16-bits (unsigned integer) Status Type: 16-bits (unsigned integer)
The Status Type parameter identifies the type of the Notify message. The Status Type parameter identifies the type of the Notify
The following are the valid Status Type values: message. The following are the valid Status Type values:
1 Application Server State Change (AS-State_Change) 1 Application Server State Change (AS-State_Change)
2 Other 2 Other
Status Information: 16-bits (unsigned integer) Status Information: 16-bits (unsigned integer)
The Status Information parameter contains more detailed information The Status Information parameter contains more detailed
for the notification, based on the value of the Status Type. information for the notification, based on the value of the Status
If the Status Type is AS-State_Change the following Status Type. If the Status Type is AS-State_Change the following Status
Information values are used: Information values are used:
1 reserved 1 reserved
2 Application Server Inactive (AS-INACTIVE) 2 Application Server Inactive (AS-INACTIVE)
3 Application Server Active (AS-ACTIVE) 3 Application Server Active (AS-ACTIVE)
4 Application Server Pending (AS-PENDING) 4 Application Server Pending (AS-PENDING)
These notifications are sent from an SGP to an ASP upon a change in These notifications are sent from an SGP to an ASP upon a change
status of a particular Application Server. The value reflects the in status of a particular Application Server. The value reflects
new state of the Application Server. the new state of the Application Server.
If the Status Type is Other, then the following Status Information If the Status Type is Other, then the following Status Information
values are defined: values are defined:
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
These notifications are not based on the SGP reporting the state change These notifications are not based on the SGP reporting the state
of an ASP or AS. In the Insufficent ASP Resources case, the SGP is change of an ASP or AS. In the Insufficient ASP Resources case, the
indicating to an ASP_INACTIVE ASP in the AS that another ASP is SGP is indicating to an ASP_INACTIVE ASP in the AS that another ASP
required to handle the load of the AS (Loadsharing or Broadcast mode). is required to handle the load of the AS (Loadsharing or Broadcast
For the Alternate ASP Active case, an ASP is informed when an alternate mode). For the Alternate ASP Active case, an ASP is informed when an
ASP transitions to the ASP-ACTIVE state in Override mode. The ASP alternate ASP transitions to the ASP-ACTIVE state in Override mode.
Identifier (if available) of the Alternate ASP MUST be placed in the The ASP Identifier (if available) of the Alternate ASP MUST be placed
message. For the ASP Failure case, the SGP is indicating to ASP(s) in the message. For the ASP Failure case, the SGP is indicating to
in the AS that one of the ASPs has transitioned to ASP-DOWN. The ASP ASP(s) in the AS that one of the ASPs has transitioned to ASP-DOWN.
Identifier (if available) of the failed ASP MUST be placed in the The ASP Identifier (if available) of the failed ASP MUST be placed in
message. the message.
The format and description of the optional ASP Identifier is the same
as for the ASP Up message (See Section 3.5.1). The format and
description of the Routing Context and Info String parameters is the
same as for the ASP Active message (See Section 3.7.1)
The format and description of the optional ASP Identifier is the same as
for the ASP Up message (See Section 3.5.1). The format and description
of the Routing Context and Info String parameters is the same as for the
ASP Active message (See Section 3.7.1)
4. Procedures 4. Procedures
The M3UA layer needs to respond to various local primitives it receives The M3UA layer needs to respond to various local primitives it
from other layers as well as the messages that it receives from the receives from other layers as well as the messages that it receives
peer M3UA layer. This section describes the M3UA procedures in from the peer M3UA layer. This section describes the M3UA procedures
response to these events. in response to these events.
4.1 Procedures to Support the M3UA-User 4.1 Procedures to Support the M3UA-User
4.1.1 Receipt of Primitives from the M3UA-User 4.1.1 Receipt of Primitives from the M3UA-User
On receiving an MTP-TRANSFER request primitive from an upper layer at On receiving an MTP-TRANSFER request primitive from an upper layer at
an ASP/IPSP, or the nodal interworking function at an SGP, the M3UA an ASP/IPSP, or the nodal interworking function at an SGP, the M3UA
layer sends a corresponding DATA message (see Section 3) to its M3UA layer sends a corresponding DATA message (see Section 3) to its M3UA
peer. The M3UA peer receiving the DATA message sends an MTP-TRANSFER peer. The M3UA peer receiving the DATA message sends an MTP-TRANSFER
indication primitive to the upper layer. indication primitive to the upper layer.
The M3UA message distribution function (see Section 1.4.2.1) determines
the Application Server (AS) based on comparing the information in the
MTP-TRANSFER request primitive with a provisioned Routing Key.
>From the list of ASPs within the AS table, an ASP in the ASP-ACTIVE The M3UA message distribution function (see Section 1.4.2.1)
state is selected and a DATA message is constructed and issued on the determines the Application Server (AS) based on comparing the
corresponding SCTP association. If more than one ASP is in the ASP- information in the MTP-TRANSFER request primitive with a provisioned
ACTIVE state (i.e., traffic is to be loadshared across more than one Routing Key.
ASP), one of the ASPs in the ASP_ACTIVE state is selected from the
list. If the ASPs are in Broadcast Mode, all active ASPs will be
selected and the message sent to each of the active ASPs. The
selection algorithm is implementation dependent but could, for
example, be round robin or based on the SLS or ISUP CIC. The a
appropriate selection algorithm must be chosen carefully as it is
dependent on application assumptions and understanding of the
degree of state coordination between the ASP_ACTIVE ASPs in the AS.
In addition, the message needs to be sent on the appropriate SCTP From the list of ASPs within the AS table, an ASP in the ASP-ACTIVE
stream, again taking care to meet the message sequencing needs of the state is selected and a DATA message is constructed and issued on the
signalling application. DATA messages MUST be sent on an SCTP stream corresponding SCTP association. If more than one ASP is in the ASP-
other than stream '0'. ACTIVE state (i.e., traffic is to be loadshared across more than one
ASP), one of the ASPs in the ASP-ACTIVE state is selected from the
list. If the ASPs are in Broadcast Mode, all active ASPs will be
selected and the message sent to each of the active ASPs. The
selection algorithm is implementation dependent but could, for
example, be round robin or based on the SLS or ISUP CIC. The
appropriate selection algorithm must be chosen carefully as it is
dependent on application assumptions and understanding of the degree
of state coordination between the ASP-ACTIVE ASPs in the AS.
When there is no Routing Key match, or only a partial match, for an In addition, the message needs to be sent on the appropriate SCTP
incoming SS7 message, a default treatment MAY be specified. Possible stream, again taking care to meet the message sequencing needs of the
solutions are to provide a default Application Server at the SGP that signalling application. DATA messages MUST be sent on an SCTP stream
directs all unallocated traffic to a (set of) default ASP(s), or to other than stream '0'.
drop the message and provide a notification to Layer Management in an
M-ERROR indication primitive. The treatment of unallocated traffic is
implementation dependent.
4.1.2 Receipt of Primitives from the Layer Management When there is no Routing Key match, or only a partial match, for an
incoming SS7 message, a default treatment MAY be specified. Possible
solutions are to provide a default Application Server at the SGP that
directs all unallocated traffic to a (set of) default ASP(s), or to
drop the message and provide a notification to Layer Management in an
M-ERROR indication primitive. The treatment of unallocated traffic
is implementation dependent.
On receiving primitives from the local Layer Management, the M3UA layer 4.2 Receipt of Primitives from the Layer Management
will take the requested action and provide an appropriate response
primitive to Layer Management.
An M-SCTP_ESTABLISH request primitive from Layer Management at an ASP On receiving primitives from the local Layer Management, the M3UA
or IPSP will initiate the establishment of an SCTP association. The layer will take the requested action and provide an appropriate
M3UA layer will attempt to establish an SCTP association with the response primitive to Layer Management.
remote M3UA peer by sending an SCTP-ASSOCIATE primitive to the local
SCTP layer.
When an SCTP association has been successfully established, the SCTP An M-SCTP_ESTABLISH request primitive from Layer Management at an ASP
will send an SCTP-COMMUNICATION_UP notification primitive to the local or IPSP will initiate the establishment of an SCTP association. The
M3UA layer. At the SGP or IPSP that initiated the request, the M3UA M3UA layer will attempt to establish an SCTP association with the
layer will send an M-SCTP_ESTABLISH confirm primitive to Layer remote M3UA peer by sending an SCTP-ASSOCIATE primitive to the local
Management when the association setup is complete. At the peer M3UA SCTP layer.
layer, an M-SCTP_ESTABLISH indication primitive is sent to Layer
Management upon successful completion of an incoming SCTP association
setup.
An M-SCTP_RELEASE request primitive from Layer Management initiates the When an SCTP association has been successfully established, the SCTP
teardown of an SCTP association. The M3UA layer accomplishes a will send an SCTP-COMMUNICATION_UP notification primitive to the
graceful shutdown of the SCTP association by sending an SCTP-SHUTDOWN local M3UA layer. At the SGP or IPSP that initiated the request, the
primitive to the SCTP layer. M3UA layer will send an M-SCTP_ESTABLISH confirm primitive to Layer
Management when the association setup is complete. At the peer M3UA
layer, an M-SCTP_ESTABLISH indication primitive is sent to Layer
Management upon successful completion of an incoming SCTP association
setup.
When the graceful shutdown of the SCTP association has been An M-SCTP_RELEASE request primitive from Layer Management initiates
accomplished, the SCTP layer returns an SCTP-SHUTDOWN_COMPLETE the teardown of an SCTP association. The M3UA layer accomplishes a
notification primitive to the local M3UA layer. At the M3UA Layer that graceful shutdown of the SCTP association by sending an SCTP-SHUTDOWN
initiated the request, the M3UA layer will send an M-SCTP_RELEASE primitive to the SCTP layer.
confirm primitive to Layer Management when the association shutdown
is complete. At the peer M3UA Layer, an M-SCTP_RELEASE indication
primitive is sent to Layer Management upon abort or successful
shutdown of an SCTP association.
An M-SCTP_STATUS request primitive supports a Layer Management query of When the graceful shutdown of the SCTP association has been
the local status of a particular SCTP association. The M3UA layer accomplished, the SCTP layer returns an SCTP-SHUTDOWN_COMPLETE
simply maps the M-SCTP_STATUS request primitive to an SCTP-STATUS notification primitive to the local M3UA layer. At the M3UA Layer
primitive to the SCTP layer. When the SCTP responds, the M3UA layer that initiated the request, the M3UA layer will send an M-
maps the association status information to an M-SCTP_STATUS confirm SCTP_RELEASE confirm primitive to Layer Management when the
primitive. No peer protocol is invoked. association shutdown is complete. At the peer M3UA Layer, an M-
SCTP_RELEASE indication primitive is sent to Layer Management upon
abort or successful shutdown of an SCTP association.
Similar LM-to-M3UA-to-SCTP and/or SCTP-to-M3UA-to-LM primitive mappings An M-SCTP_STATUS request primitive supports a Layer Management query
can be described for the various other SCTP Upper Layer primitives in of the local status of a particular SCTP association. The M3UA layer
RFC2960 [17] such as INITIALIZE, SET PRIMARY, CHANGE HEARTBEAT, simply maps the M-SCTP_STATUS request primitive to an SCTP-STATUS
REQUEST HEARTBEAT, GET SRTT REPORT, SET FAILURE THRESHOLD, SET PROTOCOL primitive to the SCTP layer. When the SCTP responds, the M3UA layer
PARAMETERS, DESTROY SCTP INSTANCE, SEND FAILURE, AND NETWORK STATUS maps the association status information to an M-SCTP_STATUS confirm
CHANGE. Alternatively, these SCTP Upper Layer primitives (and Status primitive. No peer protocol is invoked.
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 Similar LM-to-M3UA-to-SCTP and/or SCTP-to-M3UA-to-LM primitive
Management the notification or error information contained in a mappings can be described for the various other SCTP Upper Layer
received M3UA Notify or Error message respectively. These indications primitives in RFC2960 [17] such as INITIALIZE, SET PRIMARY, CHANGE
can also be generated based on local M3UA events. 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.
An M-ASP_STATUS request primitive supports a Layer Management query of M-NOTIFY indication and M-ERROR indication primitives indicate to
the status of a particular local or remote ASP. The M3UA layer Layer Management the notification or error information contained in a
responds with the status in an M-ASP_STATUS confirm primitive. No M3UA received M3UA Notify or Error message respectively. These
peer protocol is invoked. indications can also be generated based on local M3UA events.
An M-AS_STATUS request supports a Layer Management query of the status An M-ASP_STATUS request primitive supports a Layer Management query
of a particular AS. The M3UA responds with an M-AS_STATUS confirm of the status of a particular local or remote ASP. The M3UA layer
primitive. No M3UA peer protocol is invoked. responds with the status in an M-ASP_STATUS confirm primitive. No
M3UA peer protocol is invoked.
M-ASP_UP request, M-ASP_DOWN request, M-ASP_ACTIVE request and M-ASP_ An M-AS_STATUS request supports a Layer Management query of the
INACTIVE request primitives allow Layer Management at an ASP to status of a particular AS. The M3UA responds with an M-AS_STATUS
initiate state changes. Upon successful completion, a corresponding confirm primitive. No M3UA peer protocol is invoked.
confirm primitive is provided by the M3UA layer to Layer Management.
If an invocation is unsuccessful, an Error indication primitive is
provided in the primitive. These requests result in outgoing ASP Up,
ASP Down, ASP Active and ASP Inactive messages to the remote M3UA
peer at an SGP or IPSP.
4.2 Procedures to Support the Management of SCTP Associations M-ASP_UP request, M-ASP_DOWN request, M-ASP_ACTIVE request and M-
ASP_INACTIVE request primitives allow Layer Management at an ASP to
initiate state changes. Upon successful completion, a corresponding
confirm primitive is provided by the M3UA layer to Layer Management.
If an invocation is unsuccessful, an Error indication primitive is
provided in the primitive. These requests result in outgoing ASP Up,
ASP Down, ASP Active and ASP Inactive messages to the remote M3UA
peer at an SGP or IPSP.
4.2.1 Receipt of M3UA Peer Management Messages 4.2.1 Receipt of M3UA Peer Management Messages
Upon successful state changes resulting from reception of ASP Up, Upon successful state changes resulting from reception of ASP Up, ASP
ASP Down, ASP Active and ASP Inactive messages from a peer M3UA, the Down, ASP Active and ASP Inactive messages from a peer M3UA, the M3UA
M3UA layer MAY invoke corresponding M-ASP_UP, M-ASP_DOWN, M- layer MAY invoke corresponding M-ASP_UP, M-ASP_DOWN, M-ASP_ACTIVE and
ASP_ACTIVE and M-ASP_INACTIVE, M-AS_ACTIVE, M-AS_INACTIVE, and M- M-ASP_INACTIVE, M-AS_ACTIVE, M-AS_INACTIVE, and M-AS_DOWN indication
AS_DOWN indication primitives to the local Layer Management. primitives to the local Layer Management.
M-NOTIFY indication and M-ERROR indication primitives indicate to Layer M-NOTIFY indication and M-ERROR indication primitives indicate to
Management the notification or error information contained in a Layer Management the notification or error information contained in a
received M3UA Notify or Error message. These indications can also be received M3UA Notify or Error message. These indications can also be
generated based on local M3UA events. generated based on local M3UA events.
All non-Transfer and non-SSNM, messages, except BEAT and BEAT Ack, All non-Transfer and non-SSNM, messages, except BEAT and BEAT Ack,
SHOULD be sent with sequenced delivery to ensure ordering. ASPTM SHOULD be sent with sequenced delivery to ensure ordering. ASPTM
messages MAY be sent on one of the streams used to carry the data messages MAY be sent on one of the streams used to carry the data
traffic related to the Routing Context(s), to minimize possible message traffic related to the Routing Context(s), to minimize possible
loss. BEAT and BEAT Ack messages MAY be sent using out-of-order message loss. BEAT and BEAT Ack messages MAY be sent using out-of-
delivery, and MAY be sent on any stream. order delivery, and MAY be sent on any stream.
4.3 AS and ASP State Maintenance 4.3 AS and ASP State Maintenance
The M3UA layer on the SGP maintains the state of each remote ASP, in The M3UA layer on the SGP maintains the state of each remote ASP, in
each Application Server that the ASP is configured to receive traffic, each Application Server that the ASP is configured to receive
as input to the M3UA message distribution function. Similarly, where traffic, as input to the M3UA message distribution function.
IPSPs use M3UA in a point-to-point fashion, the M3UA layer in an IPSP Similarly, where IPSPs use M3UA in a point-to-point fashion, the M3UA
maintains the state of remote IPSPs. For the purposes of the following layer in an IPSP maintains the state of remote IPSPs. For the
procedures, only the SGP/ASP case is described but the SGP side of the purposes of the following procedures, only the SGP/ASP case is
procedures also apply to an IPSP sending traffic to an AS consisting of described but the SGP side of the procedures also apply to an IPSP
a set of remote IPSPs. sending traffic to an AS consisting of a set of remote IPSPs.
4.3.1 ASP States 4.3.1 ASP States
The state of each remote ASP, in each AS that it is configured to The state of each remote ASP, in each AS that it is configured to
operate, is maintained in the M3UA layer in the SGP. The state of a operate, is maintained in the M3UA layer in the SGP. The state of a
particular ASP in a particular AS changes due to events. The events particular ASP in a particular AS changes due to events. The events
include: include:
* Reception of messages from the peer M3UA layer at the ASP; * Reception of messages from the peer M3UA layer at the ASP;
* Reception of some messages from the peer M3UA layer at other ASPs * Reception of some messages from the peer M3UA layer at other ASPs
in the AS (e.g., ASP Active message indicating "Override"); in the AS (e.g., ASP Active message indicating "Override");
* Reception of indications from the SCTP layer; or * Reception of indications from the SCTP layer; or
* Local Management intervention. * Local Management intervention.
The ASP state transition diagram is shown in Figure 4. The possible The ASP state transition diagram is shown in Figure 3. The possible
states of an ASP are: states of an ASP are:
ASP-DOWN: The remote M3UA peer at the ASP is unavailable and/or the ASP-DOWN: The remote M3UA peer at the ASP is unavailable and/or the
related SCTP association is down. Initially all ASPs will be in this related SCTP association is down. Initially all ASPs will be in this
state. An ASP in this state SHOULD NOT be sent any M3UA messages, state. An ASP in this state SHOULD NOT be sent any M3UA messages,
with the exception of Heartbeat, ASP Down Ack and Error messages. with the exception of Heartbeat, ASP Down Ack and Error messages.
ASP-INACTIVE: The remote M3UA peer at the ASP is available (and the ASP-INACTIVE: The remote M3UA peer at the ASP is available (and the
related SCTP association is up) but application traffic is stopped. In related SCTP association is up) but application traffic is stopped.
this state the ASP SHOULD NOT be sent any DATA or SSNM messages for the In this state the ASP SHOULD NOT be sent any DATA or SSNM messages
AS for which the ASP is inactive. for the AS for which the ASP is inactive.
ASP-ACTIVE: The remote M3UA peer at the ASP is available and ASP-ACTIVE: The remote M3UA peer at the ASP is available and
application traffic is active (for a particular Routing Context or set application traffic is active (for a particular Routing Context or
of Routing Contexts). set of Routing Contexts).
SCTP CDI: The SCTP CDI denotes the local SCTP layer's Communication SCTP CDI: The SCTP CDI denotes the local SCTP layer's Communication
Down Indication to the Upper Layer Protocol (M3UA) on an SGP. The local Down Indication to the Upper Layer Protocol (M3UA) on an SGP. The
SCTP layer will send this indication when it detects the loss of local SCTP layer will send this indication when it detects the loss
connectivity to the ASP's peer SCTP layer. SCTP CDI is understood as of connectivity to the ASP's peer SCTP layer. SCTP CDI is understood
either a SHUTDOWN_COMPLETE notification or COMMUNICATION_LOST as either a SHUTDOWN_COMPLETE notification or COMMUNICATION_LOST
notification from the SCTP layer. notification from the SCTP layer.
SCTP RI: The local SCTP layer's Restart indication to the upper layer SCTP RI: The local SCTP layer's Restart indication to the upper layer
protocol (M3UA) on an SG. The local SCTP will send this indication protocol (M3UA) on an SG. The local SCTP will send this indication
when it detects a restart from the ASP's peer SCTP layer. when it detects a restart from the ASP's peer SCTP layer.
Figure 4: ASP State Transition Diagram, per AS Figure 3: ASP State Transition Diagram, per AS
+--------------+ +--------------+
| | | |
+----------------------| ASP-ACTIVE | +----------------------| ASP-ACTIVE |
| Other +-------| | | Other +-------| |
| ASP in AS | +--------------+ | ASP in AS | +--------------+
| Overrides | ^ | | Overrides | ^ |
| | ASP | | ASP | | ASP | | ASP
| | Active | | Inactive | | Active | | Inactive
| | | v | | | v
| | +--------------+ | | +--------------+
| | | | | | | |
| +------>| ASP-INACTIVE | | +------>| ASP-INACTIVE |
| +--------------+ | +--------------+
| ^ | | ^ |
ASP Down/ | ASP | | ASP Down / ASP Down/ | ASP | | ASP Down /
SCTP CDI/ | Up | | SCTP CDI/ SCTP CDI/ | Up | | SCTP CDI/
SCTP RI | | v SCTP RI SCTP RI | | v SCTP RI
| +--------------+ | +--------------+
| | | | | |
+--------------------->| ASP-DOWN | +--------------------->| ASP-DOWN |
| | | |
+--------------+ +--------------+
4.3.2 AS States 4.3.2 AS States
The state of the AS is maintained in the M3UA layer on the SGPs. The The state of the AS is maintained in the M3UA layer on the SGPs. The
state of an AS changes due to events. These events include: state of an AS changes due to events. These events include:
* ASP state transitions * ASP state transitions
* Recovery timer triggers * Recovery timer triggers
The possible states of an AS are: The possible states of an AS are:
AS-DOWN: The Application Server is unavailable. This state implies AS-DOWN: The Application Server is unavailable. This state implies
that all related ASPs are in the ASP-DOWN state for this AS. Initially that all related ASPs are in the ASP-DOWN state for this AS.
the AS will be in this state. An Application Server is in the AS-DOWN Initially the AS will be in this state. An Application Server is in
state when it is removed from a configuration. the AS-DOWN state when it is removed from a configuration.
AS-INACTIVE: The Application Server is available but no application AS-INACTIVE: The Application Server is available but no application
traffic is active (i.e., one or more related ASPs are in the ASP- traffic is active (i.e., one or more related ASPs are in the ASP-
INACTIVE state, but none in the ASP-ACTIVE state). The recovery INACTIVE state, but none in the ASP-ACTIVE state). The recovery
timer T(r) is not running or has expired. timer T(r) is not running or has expired.
AS-ACTIVE: The Application Server is available and application traffic AS-ACTIVE: The Application Server is available and application
is active. This state implies that at least one ASP is in the ASP- traffic is active. This state implies that at least one ASP is in
ACTIVE state. the ASP-ACTIVE state.
AS-PENDING: An active ASP has transitioned to ASP-INACTIVE or ASP-DOWN AS-PENDING: An active ASP has transitioned to ASP-INACTIVE or ASP-
and it was the last remaining active ASP in the AS. A recovery timer DOWN and it was the last remaining active ASP in the AS. A recovery
T(r) SHOULD be started and all incoming signalling messages SHOULD be timer T(r) SHOULD be started and all incoming signalling messages
queued by the SGP. If an ASP becomes ASP-ACTIVE before T(r) expires, SHOULD be queued by the SGP. If an ASP becomes ASP-ACTIVE before T(r)
the AS is moved to the AS-ACTIVE state and all the queued messages expires, the AS is moved to the AS-ACTIVE state and all the queued
will be sent to the ASP. messages will be sent to the ASP.
If T(r) expires before an ASP becomes ASP-ACTIVE, and the SGP has no If T(r) expires before an ASP becomes ASP-ACTIVE, and the SGP has no
alternative, the SGP may stops queuing messages and discards all alternative, the SGP may stops queuing messages and discards all
previously queued messages. The AS will move to the AS-INACTIVE state previously queued messages. The AS will move to the AS-INACTIVE
state.
if at least one ASP is in ASP-INACTIVE state, otherwise it will move If at least one ASP is in ASP-INACTIVE state, otherwise it will move
to AS-DOWN state. to AS-DOWN state.
Figure 5 shows an example AS state machine for the case where the Figure 4 shows an example AS state machine for the case where the
AS/ASP data is preconfigured. For other cases where the AS/ASP AS/ASP data is preconfigured. For other cases where the AS/ASP
configuration data is created dynamically, there would be differences configuration data is created dynamically, there would be differences
in the state machine, especially at creation of the AS. in the state machine, especially at creation of the AS.
Figure 5: AS State Transition Diagram Figure 4: AS State Transition Diagram
+----------+ one ASP trans to ACTIVE +-------------+ +----------+ one ASP trans to ACTIVE +-------------+
| AS- |---------------------------->| AS- | | AS- |---------------------------->| AS- |
| INACTIVE | | ACTIVE | | INACTIVE | | ACTIVE |
| |<--- | | | |<--- | |
+----------+ \ +-------------+ +----------+ \ +-------------+
^ | \ Tr Expiry, ^ | ^ | \ Tr Expiry, ^ |
| | \ at least one | | | | \ at least one | |
| | \ ASP in ASP-INACTIVE | | | | \ ASP in ASP-INACTIVE | |
| | \ | | | | \ | |
| | \ | | | | \ | |
| | \ | | | | \ | |
one ASP | | all ASP \ one ASP | | Last ACTIVE one ASP | | all ASP \ one ASP | | Last ACTIVE
trans | | trans to \ trans to | | ASP trans to trans | | trans to \ trans to | | ASP trans to
to | | ASP-DOWN -------\ ASP- | | ASP-INACTIVE to | | ASP-DOWN -------\ ASP- | | ASP-INACTIVE
ASP- | | \ ACTIVE | | or ASP-DOWN ASP- | | \ ACTIVE | | or ASP-DOWN
INACTIVE| | \ | | (start Tr) INACTIVE| | \ | | (start Tr)
| | \ | | | | \ | |
| | \ | | | | \ | |
| v \ | v | v \ | v
+----------+ \ +-------------+ +----------+ \ +-------------+
| | --| | | | --| |
| AS-DOWN | | AS-PENDING | | AS-DOWN | | AS-PENDING |
| | | (queueing) | | | | (queuing) |
| |<----------------------------| | | |<----------------------------| |
+----------+ Tr Expiry and no ASP +-------------+ +----------+ Tr Expiry and no ASP +-------------+
in ASP-INACTIVE state) in ASP-INACTIVE state)
Tr = Recovery Timer Tr = Recovery Timer
For example, where the AS/ASP configuration data is not created until For example, where the AS/ASP configuration data is not created until
Registration of the first ASP, the AS-INACTIVE state is entered Registration of the first ASP, the AS-INACTIVE state is entered
directly upon the first successful REG REQ from an ASP. Another directly upon the first successful REG REQ from an ASP. Another
example is where the AS/ASP configuration data is not created until the example is where the AS/ASP configuration data is not created until
first ASP successfully enters the ASP-ACTIVE state. In this case the the first ASP successfully enters the ASP-ACTIVE state. In this case
AS-ACTIVE state is entered directly. the AS-ACTIVE state is entered directly.
4.3.3 M3UA Management Procedures for Primitives 4.3.3 M3UA Management Procedures for Primitives
Before the establishment of an SCTP association the ASP state at both Before the establishment of an SCTP association the ASP state at both
the SGP and ASP is assumed to be in the state ASP-DOWN. the SGP and ASP is assumed to be in the state ASP-DOWN.
Once the SCTP association is established (see Section 4.2.1) and Once the SCTP association is established (see Section 4.2) and
assuming that the local M3UA-User is ready, the local M3UA ASP assuming that the local M3UA-User is ready, the local M3UA ASP
Maintenance (ASPM) function will initiate the relevant procedures, Maintenance (ASPM) function will initiate the relevant procedures,
using the ASP Up/ASP Down/ASP Active/ASP Inactive messages to convey using the ASP Up/ASP Down/ASP Active/ASP Inactive messages to convey
the ASP state to the SGP (see Section 4.3.4). the ASP state to the SGP (see Section 4.3.4).
If the M3UA layer subsequently receives an SCTP-COMMUNICATION_DOWN If the M3UA layer subsequently receives an SCTP-COMMUNICATION_DOWN or
or SCTP-RESTART indication primitive from the underlying SCTP layer, it SCTP-RESTART indication primitive from the underlying SCTP layer, it
will inform the Layer Management by invoking the M-SCTP_STATUS will inform the Layer Management by invoking the M-SCTP_STATUS
indication primitive. The state of the ASP will be moved to ASP-DOWN. indication primitive. The state of the ASP will be moved to ASP-DOWN.
At an ASP, the MTP3-User will be informed of the unavailability of any At an ASP, the MTP3-User will be informed of the unavailability of
affected SS7 destinations through the use of MTP-PAUSE indication any affected SS7 destinations through the use of MTP-PAUSE indication
primitives. primitives.
In the case of SCTP-COMMUNICATION_DOWN, the SCTP client MAY try to re- In the case of SCTP-COMMUNICATION_DOWN, the SCTP client MAY try to
establish the SCTP Association. This MAY be done by the M3UA layer re-establish the SCTP Association. This MAY be done by the M3UA
automatically, or Layer Management MAY re-establish using the layer automatically, or Layer Management MAY re-establish using the
M-SCTP_ESTABLISH request primitive. M-SCTP_ESTABLISH request primitive.
In the case of an SCTP-RESTART indication at an ASP, the ASP is now In the case of an SCTP-RESTART indication at an ASP, the ASP is now
considered by its M3UA peer to be in the ASP-DOWN state. The ASP, if considered by its M3UA peer to be in the ASP-DOWN state. The ASP, if
it is to recover, must begin any recovery with the ASP-Up procedure. it is to recover, must begin any recovery with the ASP-Up procedure.
4.3.4 ASPM Procedures for Peer-to-Peer Messages 4.3.4 ASPM Procedures for Peer-to-Peer Messages
4.3.4.1 ASP Up Procedures 4.3.4.1 ASP Up Procedures
After an ASP has successfully established an SCTP association to an After an ASP has successfully established an SCTP association to an
SGP, the SGP waits for the ASP to send an ASP Up message, indicating SGP, the SGP waits for the ASP to send an ASP Up message, indicating
that the ASP M3UA peer is available. The ASP is always the initiator that the ASP M3UA peer is available. The ASP is always the initiator
of the ASP Up message. This action MAY be initiated at the ASP by an of the ASP Up message. This action MAY be initiated at the ASP by an
M-ASP_UP request primitive from Layer Management or MAY be initiated M-ASP_UP request primitive from Layer Management or MAY be initiated
automatically by an M3UA management function. automatically by an M3UA management function.
When an ASP Up message is received at an SGP and internally the remote When an ASP Up message is received at an SGP and internally the
ASP is in the ASP-DOWN state and not considered locked out for local remote ASP is in the ASP-DOWN state and not considered locked out for
management reasons, the SGP marks the remote ASP in the state ASP- local management reasons, the SGP marks the remote ASP in the state
INACTIVE and informs Layer Management with an M-ASP_Up indication ASP-INACTIVE and informs Layer Management with an M-ASP_Up indication
primitive. If the SGP is aware, via current configuration data, which primitive. If the SGP is aware, via current configuration data,
Application Servers the ASP is configured to operate in, the SGP which Application Servers the ASP is configured to operate in, the
updates the ASP state to ASP-INACTIVE in each AS that it is a member. SGP updates the ASP state to ASP-INACTIVE in each AS that it is a
member.
Alternatively, the SGP may move the ASP into a pool of Inactive ASPs Alternatively, the SGP may move the ASP into a pool of Inactive ASPs
available for future configuration within Application Server(s), available for future configuration within Application Server(s),
determined in a subsequent Registration Request or ASP Active determined in a subsequent Registration Request or ASP Active
procedure. If the ASP Up message contains an ASP Identifier, the SGP procedure. If the ASP Up message contains an ASP Identifier, the SGP
should save the ASP Identifier for that ASP. The SGP MUST send an should save the ASP Identifier for that ASP. The SGP MUST send an ASP
ASP Up Ack message in response to a received ASP Up message even if Up Ack message in response to a received ASP Up message even if the
the ASP is already marked as ASP-INACTIVE at the SGP. ASP is already marked as ASP-INACTIVE at the SGP.
If for any local reason (e.g., management lockout) the SGP cannot If for any local reason (e.g., management lockout) the SGP cannot
respond with an ASP Up Ack message, the SGP responds to an ASP Up respond with an ASP Up Ack message, the SGP responds to an ASP Up
message with an Error message with reason "Refused - Management message with an Error message with reason "Refused - Management
Blocking". Blocking".
At the ASP, the ASP Up Ack message received is not acknowledged. Layer At the ASP, the ASP Up Ack message received is not acknowledged.
Management is informed with an M-ASP_UP confirm primitive. Layer Management is informed with an M-ASP_UP confirm primitive.
When the ASP sends an ASP Up message it starts timer T(ack). If the When the ASP sends an ASP Up message it starts timer T(ack). If the
ASP does not receive a response to an ASP Up message within T(ack), the ASP does not receive a response to an ASP Up message within T(ack),
ASP MAY restart T(ack) and resend ASP Up messages until it receives an the ASP MAY restart T(ack) and resend ASP Up messages until it
ASP Up Ack message. T(ack) is provisionable, with a default of 2 receives an ASP Up Ack message. T(ack) is provisionable, with a
seconds. Alternatively, retransmission of ASP Up messages MAY be put default of 2 seconds. Alternatively, retransmission of ASP Up
under control of Layer Management. In this method, expiry of T(ack) messages MAY be put under control of Layer Management. In this
results in an M-ASP_UP confirm primitive carrying a negative method, expiry of T(ack) results in an M-ASP_UP confirm primitive
indication. carrying a negative indication.
The ASP must wait for the ASP Up Ack message before sending any other The ASP must wait for the ASP Up Ack message before sending any other
M3UA messages (e.g., ASP Active or REG REQ). If the SGP receives any M3UA messages (e.g., ASP Active or REG REQ). If the SGP receives any
other M3UA messages before an ASP Up message is received (other than other M3UA messages before an ASP Up message is received (other than
ASP Down - see Section 4.3.4.2), the SGP MAY discard them. ASP Down - see Section 4.3.4.2), the SGP MAY discard them.
If an ASP Up message is received and internally the remote ASP is in If an ASP Up message is received and internally the remote ASP is in
the ASP-ACTIVE state, an ASP Up Ack message is returned, as well as an the ASP-ACTIVE state, an ASP Up Ack message is returned, as well as
Error message ("Unexpected Message), and the remote ASP state is an Error message ("Unexpected Message), and the remote ASP state is
changed to ASP-INACTIVE in all relevant Application Servers. changed to ASP-INACTIVE in all relevant Application Servers.
If an ASP Up message is received and internally the remote ASP is If an ASP Up message is received and internally the remote ASP is
already in the ASP-INACTIVE state, an ASP Up Ack message is returned already in the ASP-INACTIVE state, an ASP Up Ack message is returned
and no further action is taken. and no further action is taken.
4.3.4.1.1 M3UA Version Control 4.3.4.1.1 M3UA Version Control
If an ASP Up message with an unsupported version is received, the If an ASP Up message with an unsupported version is received, the
receiving end responds with an Error message, indicating the version receiving end responds with an Error message, indicating the version
the receiving node supports and notifies Layer Management. the receiving node supports and notifies Layer Management.
This is useful when protocol version upgrades are being performed in a This is useful when protocol version upgrades are being performed in
network. A node upgraded to a newer version should support the older a network. A node upgraded to a newer version should support the
versions used on other nodes it is communicating with. Because ASPs older versions used on other nodes it is communicating with. Because
initiate the ASP Up procedure it is assumed that the Error message ASPs initiate the ASP Up procedure it is assumed that the Error
would normally come from the SGP. message would normally come from the SGP.
4.3.4.1.2 IPSP Considerations (ASP Up) 4.3.4.1.2 IPSP Considerations (ASP Up)
An IPSP may be considered in the ASP-INACTIVE state after an ASP Up or An IPSP may be considered in the ASP-INACTIVE state after an ASP Up
ASP Up Ack has been received from it. An IPSP can be considered in the or ASP Up Ack has been received from it. An IPSP can be considered
ASP-DOWN state after an ASP Down or ASP Down Ack has been received from in the ASP-DOWN state after an ASP Down or ASP Down Ack has been
it. The IPSP may inform Layer Management of the change in state of the received from it. The IPSP may inform Layer Management of the change
remote IPSP using M-ASP_UP or M-ASP_DN indication or confirmation in state of the remote IPSP using M-ASP_UP or M-ASP_DN indication or
primitives. confirmation primitives.
Alternatively, an interchange of ASP Up messages from each end can be Alternatively, an interchange of ASP Up messages from each end can be
performed. This option follows the ASP state transition diagram. It performed. This option follows the ASP state transition diagram. It
would need four messages for completion. would need four messages for completion.
If for any local reason (e.g., management lockout) an IPSP cannot If for any local reason (e.g., management lockout) an IPSP cannot
respond to an ASP Up message with an ASP Up Ack message, it responds to respond to an ASP Up message with an ASP Up Ack message, it responds
an ASP Up message with an Error message with reason "Refused - to an ASP Up message with an Error message with reason "Refused
Management Blocking" and leaves the remote IPSP in the ASP-DOWN state. Management Blocking" and leaves the remote IPSP in the ASP-DOWN
state.
4.3.4.2 ASP-Down Procedures 4.3.4.2 ASP-Down Procedures
The ASP will send an ASP Down message to an SGP when the ASP wishes to The ASP will send an ASP Down message to an SGP when the ASP wishes
be removed from service in all Application Servers that it is a to be removed from service in all Application Servers that it is a
member and no longer receive any DATA, SSNM or ASPTM messages. member and no longer receive any DATA, SSNM or ASPTM messages. This
This action MAY be initiated at the ASP by an M-ASP_DOWN request action MAY be initiated at the ASP by an M-ASP_DOWN request primitive
primitive from Layer Management or MAY be initiated automatically from Layer Management or MAY be initiated automatically by an M3UA
by an M3UA management function. management function.
Whether the ASP is permanently removed from any AS is a function of Whether the ASP is permanently removed from any AS is a function of
configuration management. In the case where the ASP previously used configuration management. In the case where the ASP previously used
the Registration procedures (see Section 4.4.1) to register within the Registration procedures (see Section 4.4.1) to register within
Application Servers but has not deregistered from all of them prior to Application Servers but has not deregistered from all of them prior
sending the ASP Down message, the SGP MUST consider the ASP as to sending the ASP Down message, the SGP MUST consider the ASP as
Deregistered in all Application Servers that it is still a member. Deregistered in all Application Servers that it is still a member.
The SGP marks the ASP as ASP-DOWN, informs Layer Management with an M- The SGP marks the ASP as ASP-DOWN, informs Layer Management with an
ASP_Down indication primitive, and returns an ASP Down Ack message to M-ASP_Down indication primitive, and returns an ASP Down Ack message
the ASP. to the ASP.
The SGP MUST send an ASP Down Ack message in response to a received 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 message from the ASP even if the ASP is already marked as
ASP-DOWN at the SGP. ASP-DOWN at the SGP.
At the ASP, the ASP Down Ack message received is not acknowledged. At the ASP, the ASP Down Ack message received is not acknowledged.
Layer Management is informed with an M-ASP_DOWN confirm primitive. If Layer Management is informed with an M-ASP_DOWN confirm primitive.
the ASP receives an ASP Down Ack without having sent an ASP Down If the ASP receives an ASP Down Ack without having sent an ASP Down
message, the ASP should now consider itself as in the ASP-DOWN state. message, the ASP should now consider itself as in the ASP-DOWN state.
If the ASP was previously in the ASP-ACTIVE or ASP-INACTIVE state, the
ASP should then initiate procedures to return itself to its previous
state.
When the ASP sends an ASP Down message it starts timer T(ack). If the If the ASP was previously in the ASP-ACTIVE or ASP-INACTIVE state,
ASP does not receive a response to an ASP Down message within T(ack), the ASP should then initiate procedures to return itself to its
the ASP MAY restart T(ack) and resend ASP Down messages until it previous state.
receives an ASP Down Ack message. T(ack) is provisionable, with a
default of 2 seconds. Alternatively, retransmission of ASP Down When the ASP sends an ASP Down message it starts timer T(ack). If
messages MAY be put under control of Layer Management. In this method, the ASP does not receive a response to an ASP Down message within
expiry of T(ack) results in an M-ASP_DOWN confirm primitive carrying a T(ack), the ASP MAY restart T(ack) and resend ASP Down messages until
negative indication. it receives an ASP Down Ack message. T(ack) is provisionable, with a
default of 2 seconds. Alternatively, retransmission of ASP Down
messages MAY be put under control of Layer Management. In this
method, expiry of T(ack) results in an M-ASP_DOWN confirm primitive
carrying a negative indication.
4.3.4.3 ASP Active Procedures 4.3.4.3 ASP Active Procedures
Anytime after the ASP has received an ASP Up Ack message from the SGP Anytime after the ASP has received an ASP Up Ack message from the SGP
or IPSP, the ASP MAY send an ASP Active message to the SGP indicating or IPSP, the ASP MAY send an ASP Active message to the SGP indicating
that the ASP is ready to start processing traffic. This action MAY be that the ASP is ready to start processing traffic. This action MAY
initiated at the ASP by an M-ASP_ACTIVE request primitive from Layer be initiated at the ASP by an M-ASP_ACTIVE request primitive from
Management or MAY be initiated automatically by an M3UA management Layer Management or MAY be initiated automatically by an M3UA
function. In the case where an ASP wishes to process the traffic for management function. In the case where an ASP wishes to process the
more than one Application Server across a common SCTP association, the traffic for more than one Application Server across a common SCTP
ASP Active message(s) SHOULD contain a list of one or more Routing association, the ASP Active message(s) SHOULD contain a list of one
Contexts to indicate for which Application Servers the ASP Active or more Routing Contexts to indicate for which Application Servers
message applies. It is not necessary for the ASP to include all Routing the ASP Active message applies. It is not necessary for the ASP to
Contexts of interest in a single ASP Active message, thus requesting to include all Routing Contexts of interest in a single ASP Active
become active in all Routing Contexts at the same time. Multiple ASP message, thus requesting to become active in all Routing Contexts at
Active messages MAY be used to activate within the Application Servers the same time. Multiple ASP Active messages MAY be used to activate
independently, or in sets. In the case where an ASP Active message within the Application Servers independently, or in sets. In the
does not contain a Routing Context parameter, the receiver must know, case where an ASP Active message does not contain a Routing Context
via configuration data, which Application Server(s) the ASP is a parameter, the receiver must know, via configuration data, which
member. Application Server(s) the ASP is a member.
For the Application Servers that the ASP can be successfully activated, For the Application Servers that the ASP can be successfully
the SGP or IPSP responds with one or more ASP Active Ack messages, activated, the SGP or IPSP responds with one or more ASP Active Ack
including the associated Routing Context(s) and reflecting any messages, including the associated Routing Context(s) and reflecting
Traffic Mode Type value present in the related ASP Active message. any Traffic Mode Type value present in the related ASP Active
The Routing Context parameter MUST be included in the ASP Active message. The Routing Context parameter MUST be included in the ASP
Ack message(s) if the received ASP Active message contained any Active Ack message(s) if the received ASP Active message contained
Routing Contexts. Depending on any Traffic Mode Type request in any Routing Contexts. Depending on any Traffic Mode Type request in
the ASP Active message, or local configuration data if there is no the ASP Active message, or local configuration data if there is no
request, the SGP moves the ASP to the correct ASP traffic state request, the SGP moves the ASP to the correct ASP traffic state
within the associated Application Server(s). Layer Management is within the associated Application Server(s). Layer Management is
informed with an M-ASP_Active indication. If the SGP or IPSP informed with an M-ASP_Active indication. If the SGP or IPSP receives
receives any Data messages before an ASP Active message is any Data messages before an ASP Active message is received, the SGP
received, the SGP or IPSP MAY discard them. By sending an ASP or IPSP MAY discard them. By sending an ASP Active Ack message, the
Active Ack message, the SGP or IPSP is now ready to receive and SGP or IPSP is now ready to receive and send traffic for the related
send traffic for the related Routing Context(s). The ASP SHOULD Routing Context(s). The ASP SHOULD NOT send Data or SSNM messages
NOT send Data or SSNM messages for the related Routing Context(s) for the related Routing Context(s) before receiving an ASP Active Ack
before receiving an ASP Active Ack message, or it will risk message message, or it will risk message loss.
loss.
Multiple ASP Active Ack messages MAY be used in response to an ASP Multiple ASP Active Ack messages MAY be used in response to an ASP
Active message containing multiple Routing Contexts, allowing the SGP Active message containing multiple Routing Contexts, allowing the SGP
or IPSP to independently acknowledge the ASP Active message for or IPSP to independently acknowledge the ASP Active message for
different (sets of) Routing Contexts. The SGP or IPSP MUST send an different (sets of) Routing Contexts. The SGP or IPSP MUST send an
Error message ("Invalid Routing Context") for each Routing Context Error message ("Invalid Routing Context") for each Routing Context
value that the ASP cannot be successfully activated . value that the ASP cannot be successfully activated .
In the case where an "out-of-the-blue" ASP Active message is received In the case where an "out-of-the-blue" ASP Active message is received
(i.e., the ASP has not registered with the SG or the SG has no static (i.e., the ASP has not registered with the SG or the SG has no static
configuration data for the ASP), the message MAY be silently discarded. configuration data for the ASP), the message MAY be silently
discarded.
The SGP MUST send an ASP Active Ack message in response to a received The SGP MUST send an ASP Active Ack message in response to a received
ASP Active message from the ASP, if the ASP is already marked in the ASP Active message from the ASP, if the ASP is already marked in the
ASP-ACTIVE state at the SGP. ASP-ACTIVE state at the SGP.
At the ASP, the ASP Active Ack message received is not acknowledged. At the ASP, the ASP Active Ack message received is not acknowledged.
Layer Management is informed with an M-ASP_ACTIVE confirm primitive. Layer Management is informed with an M-ASP_ACTIVE confirm primitive.
It is possible for the ASP to receive Data message(s) before the ASP It is possible for the ASP to receive Data message(s) before the ASP
Active Ack message as the ASP Active Ack and Data messages from an SG Active Ack message as the ASP Active Ack and Data messages from an SG
or IPSP may be sent on different SCTP streams. Message loss is or IPSP may be sent on different SCTP streams. Message loss is
possible as the ASP does not consider itself in the ASP-ACTIVE state possible as the ASP does not consider itself in the ASP-ACTIVE state
until reception of the ASP Active Ack message. until reception of the ASP Active Ack message.
When the ASP sends an ASP Active message it starts timer T(ack). If When the ASP sends an ASP Active message it starts timer T(ack). If
the ASP does not receive a response to an ASP Active message within the ASP does not receive a response to an ASP Active message within
T(ack), the ASP MAY restart T(ack) and resend ASP Active messages until T(ack), the ASP MAY restart T(ack) and resend ASP Active messages
it receives an ASP Active Ack message. T(ack) is provisionable, with a until it receives an ASP Active Ack message. T(ack) is
default of 2 seconds. Alternatively, retransmission of ASP Active provisionable, with a default of 2 seconds. Alternatively,
messages MAY be put under control of Layer Management. In this method, retransmission of ASP Active messages MAY be put under control of
expiry of T(ack) results in an M-ASP_ACTIVE confirm primitive carrying Layer Management. In this method, expiry of T(ack) results in an M-
a negative indication. ASP_ACTIVE confirm primitive carrying a negative indication.
There are three modes of Application Server traffic handling in the SGP There are three modes of Application Server traffic handling in the
M3UA layer: Override, Loadshare and Broadcast. When included, the SGP M3UA layer: Override, Loadshare and Broadcast. When included,
Traffic Mode Type parameter in the ASP Active message indicates the the Traffic Mode Type parameter in the ASP Active message indicates
traffic handling mode to be used in a particular Application Server. the traffic handling mode to be used in a particular Application
If the SGP determines that the mode indicated in an ASP Active Server. If the SGP determines that the mode indicated in an ASP
message is unsupported or incompatible with the mode currently Active message is unsupported or incompatible with the mode currently
configured for the AS, the SGP responds with an Error message configured for the AS, the SGP responds with an Error message
("Unsupported / Invalid Traffic Handling Mode"). If the traffic ("Unsupported / Invalid Traffic Handling Mode"). If the traffic
handling mode of the Application Server is not already known via handling mode of the Application Server is not already known via
configuration data, then the traffic handling mode indicated in the configuration data, then the traffic handling mode indicated in the
first ASP Active message causing the transition of the Application first ASP Active message causing the transition of the Application
Server state to AS-ACTIVE MAY be used to set the mode. Server state to AS-ACTIVE MAY be used to set the mode.
In the case of an Override mode AS, reception of an ASP Active message In the case of an Override mode AS, reception of an ASP Active
at an SGP causes the (re)direction of all traffic for the AS to the ASP message at an SGP causes the (re)direction of all traffic for the AS
that sent the ASP Active message. Any previously active ASP in the AS to the ASP that sent the ASP Active message. Any previously active
is now considered to be in state ASP-INACTIVE and SHOULD no longer ASP in the AS is now considered to be in state ASP-INACTIVE and
receive traffic from the SGP within the AS. The SGP or IPSP then MUST SHOULD no longer receive traffic from the SGP within the AS. The SGP
send a Notify message ("Alternate ASP_Active") to the previously active or IPSP then MUST send a Notify message ("Alternate ASP_Active") to
ASP in the AS, and SHOULD stop traffic to/from that ASP. The ASP the previously active ASP in the AS, and SHOULD stop traffic to/from
receiving this Notify MUST consider itself now in the ASP-INACTIVE that ASP. The ASP receiving this Notify MUST consider itself now in
state, if it is not already aware of this via inter-ASP communication the ASP-INACTIVE state, if it is not already aware of this via
with the Overriding ASP. inter-ASP communication with the Overriding ASP.
In the case of a Loadshare mode AS, reception of an ASP Active message In the case of a Loadshare mode AS, reception of an ASP Active
at an SGP or IPSP causes the direction of traffic to the ASP sending message at an SGP or IPSP causes the direction of traffic to the ASP
the ASP Active message, in addition to all the other ASPs that are sending the ASP Active message, in addition to all the other ASPs
currently active in the AS. The algorithm at the SGP for loadsharing that are currently active in the AS. The algorithm at the SGP for
traffic within an AS to all the active ASPs is implementation loadsharing traffic within an AS to all the active ASPs is
dependent. The algorithm could, for example, be round-robin or based implementation dependent. The algorithm could, for example, be
on information in the Data message (e.g., the SLS, SCCP SSN, ISUP CIC round-robin or based on information in the Data message (e.g., the
value). SLS, SCCP SSN, ISUP CIC value).
An SGP or IPSP, upon reception of an ASP Active message for the first An SGP or IPSP, upon reception of an ASP Active message for the first
ASP in a Loadshare AS, MAY choose not to direct traffic to a newly ASP in a Loadshare AS, MAY choose not to direct traffic to a newly
active ASP until it determines that there are sufficient resources to 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- handle the expected load (e.g., until there are "n" ASPs in state
ACTIVE in the AS). In this case, the SGP or IPSP SHOULD withhold the ASP-ACTIVE in the AS). In this case, the SGP or IPSP SHOULD withhold
Notify (AS-ACTIVE) until there are sufficient resources. the Notify (AS-ACTIVE) until there are sufficient resources.
For the n+k redundancy case, ASPs which are in that AS should coordinate For the n+k redundancy case, ASPs which are in that AS should
among themselves the number of active ASPs in the AS, and should start coordinate among themselves the number of active ASPs in the AS, and
sending traffic only after n ASPs are active. should start sending traffic only after n ASPs are active.
All ASPs within a loadsharing mode AS must be able to process any All ASPs within a loadsharing mode AS must be able to process any
Data message received for the AS, to accommodate any potential Data message received for the AS, to accommodate any potential
failover or rebalancing of the offered load. failover or rebalancing of the offered load.
In the case of a Broadcast mode AS, reception of an ASP Active message In the case of a Broadcast mode AS, reception of an ASP Active
at an SGP or IPSP causes the direction of traffic to the ASP sending message at an SGP or IPSP causes the direction of traffic to the ASP
the ASP Active message, in addition to all the other ASPs that are sending the ASP Active message, in addition to all the other ASPs
currently active in the AS. The algorithm at the SGP for broadcasting that are currently active in the AS. The algorithm at the SGP for
traffic within an AS to all the active ASPs is a simple broadcast broadcasting traffic within an AS to all the active ASPs is a simple
algorithm, where every message is sent to each of the active ASPs. broadcast algorithm, where every message is sent to each of the
active ASPs.
An SGP or IPSP, upon reception of an ASP Active message for the first An SGP or IPSP, upon reception of an ASP Active message for the first
ASP in a Broadcast AS, MAY choose not to direct traffic to a newly 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 active ASP until it determines that there are sufficient resources to
handle the expected load (e.g., until there are "n" ASPs in state handle the expected load (e.g., until there are "n" ASPs in state
ASP-ACTIVE in the AS). In this case, the SGP or IPSP SHOULD withhold the ASP-ACTIVE in the AS). In this case, the SGP or IPSP SHOULD withhold
Notify (AS-ACTIVE) until there are sufficient resources. the Notify (AS-ACTIVE) until there are sufficient resources.
For the n+k redundancy case, ASPs which are in that AS should coordinate For the n+k redundancy case, ASPs which are in that AS should
among themselves the number of active ASPs in the AS, and should start coordinate among themselves the number of active ASPs in the AS, and
sending traffic only after n ASPs are active. should start sending traffic only after n ASPs are active.
Whenever an ASP in a Broadcast mode AS becomes ASP-ACTIVE, the SGP Whenever an ASP in a Broadcast mode AS becomes ASP-ACTIVE, the SGP
MUST tag the first DATA message broadcast in each traffic flow with MUST tag the first DATA message broadcast in each traffic flow with
a unique Correlation Id parameter. The purpose of this Id is to permit
the newly active ASP to synchronize its processing of traffic in each a unique Correlation Id parameter. The purpose of this Id is to
traffic flow with the other ASPs in the broadcast group. permit the newly active ASP to synchronize its processing of traffic
in each traffic flow with the other ASPs in the broadcast group.
4.3.4.3.1 IPSP Considerations (ASP Active) 4.3.4.3.1 IPSP Considerations (ASP Active)
Either of the IPSPs can initiate communication. When an IPSP receives an Either of the IPSPs can initiate communication. When an IPSP receives
ASP Active, it should mark the peer as ASP-ACTIVE and return an ASP an ASP Active, it should mark the peer as ASP-ACTIVE and return an
Active Ack message. An ASP receiving an ASP Active Ack message may mark ASP Active Ack message. An ASP receiving an ASP Active Ack message
the peer as ASP-Active, if it is not already in the ASP-ACTIVE state. may mark the peer as ASP-Active, if it is not already in the ASP-
ACTIVE state.
Alternatively, an interchange of ASP Active messages from each end can Alternatively, an interchange of ASP Active messages from each end
be performed. This option follows the ASP state transition diagram and can be performed. This option follows the ASP state transition
gives the additional advantage of selecting a particular AS to be diagram and gives the additional advantage of selecting a particular
activated from each end. It is especially useful when an IPSP is serving AS to be activated from each end. It is especially useful when an
more than one AS. It would need four messages for completion. IPSP is serving more than one AS. It would need four messages for
completion.
4.3.4.4 ASP Inactive Procedures 4.3.4.4 ASP Inactive Procedures
When an ASP wishes to withdraw from receiving traffic within an AS, the When an ASP wishes to withdraw from receiving traffic within an AS,
ASP sends an ASP Inactive message to the SGP or IPSP. This action MAY the ASP sends an ASP Inactive message to the SGP or IPSP. This
be initiated at the ASP by an M-ASP_INACTIVE request primitive from action MAY be initiated at the ASP by an M-ASP_INACTIVE request
Layer Management or MAY be initiated automatically by an M3UA primitive from Layer Management or MAY be initiated automatically by
management function. In the case where an ASP is processing the an M3UA management function. In the case where an ASP is processing
traffic for more than one Application Server across a common SCTP the traffic for more than one Application Server across a common SCTP
association, the ASP Inactive message contains one or more Routing association, the ASP Inactive message contains one or more Routing
Contexts to indicate for which Application Servers the ASP Inactive Contexts to indicate for which Application Servers the ASP Inactive
message applies. In the case where an ASP Inactive message does not message applies. In the case where an ASP Inactive message does not
contain a Routing Context parameter, the receiver must know, via contain a Routing Context parameter, the receiver must know, via
configuration data, which Application Servers the ASP is a member and
configuration data, which Application Servers the ASP is a member and move the ASP to the ASP-INACTIVE state in all Application Servers. In
move the ASP to the ASP-INACTIVE state in all Application Servers. the case of an Override mode AS, where another ASP has already taken
In the case of an Override mode AS, where another ASP has already over the traffic within the AS with an ASP Active ("Override")
taken over the traffic within the AS with an ASP Active ("Override") message, the ASP that sends the ASP Inactive message is already
message, the ASP that sends the ASP Inactive message is already considered by the SGP to be in state ASP-INACTIVE. An ASP Inactive
considered by the SGP to be in state ASP-INACTIVE. An ASP Inactive Ack Ack message is sent to the ASP, after ensuring that all traffic is
message is sent to the ASP, after ensuring that all traffic is stopped stopped to the ASP.
to the ASP.
In the case of a Loadshare mode AS, the SGP moves the ASP to the ASP- In the case of a Loadshare mode AS, the SGP moves the ASP to the
INACTIVE state and the AS traffic is reallocated across the remaining ASP-INACTIVE state and the AS traffic is reallocated across the
ASPs in the state ASP-ACTIVE, as per the loadsharing algorithm remaining ASPs in the state ASP-ACTIVE, as per the loadsharing
currently used within the AS. A Notify message ("Insufficient ASP algorithm currently used within the AS. A Notify message
resources active in AS") MAY be sent to all inactive ASPs, if required. ("Insufficient ASP resources active in AS") MAY be sent to all
An ASP Inactive Ack message is sent to the ASP after all traffic inactive ASPs, if required. An ASP Inactive Ack message is sent to
is halted and Layer Management is informed with an M-ASP_INACTIVE the ASP after all traffic is halted and Layer Management is informed
indication primitive. with an M-ASP_INACTIVE indication primitive.
In the case of a Broadcast mode AS, the SGP moves the ASP to the In the case of a Broadcast mode AS, the SGP moves the ASP to the
ASP-INACTIVE state and the AS traffic is broadcast only to the ASP-INACTIVE state and the AS traffic is broadcast only to the
remaining ASPs in the state ASP-ACTIVE. A Notify message remaining ASPs in the state ASP-ACTIVE. A Notify message
("Insufficient ASP resources active in AS") MAY be sent to all ("Insufficient ASP resources active in AS") MAY be sent to all
inactive ASPs, if required. An ASP Inactive Ack message inactive ASPs, if required. An ASP Inactive Ack message is sent to
is sent to the ASP after all traffic is halted and Layer Management is the ASP after all traffic is halted and Layer Management is informed
informed with an M-ASP_INACTIVE indication primitive. with an M-ASP_INACTIVE indication primitive.
Multiple ASP Inactive Ack messages MAY be used in response to an ASP Multiple ASP Inactive Ack messages MAY be used in response to an ASP
Inactive message containing multiple Routing Contexts, allowing the SGP Inactive message containing multiple Routing Contexts, allowing the
or IPSP to independently acknowledge for different (sets of) Routing SGP or IPSP to independently acknowledge for different (sets of)
Contexts. The SGP or IPSP sends an Error message ("Invalid Routing Routing Contexts. The SGP or IPSP sends an Error message ("Invalid
Context") message for each invalid or unconfigured Routing Context Routing Context") message for each invalid or unconfigured Routing
value in a received ASP Inactive message. Context value in a received ASP Inactive message.
The SGP MUST send an ASP Inactive Ack message in response to a received The SGP MUST send an ASP Inactive Ack message in response to a
ASP Inactive message from the ASP and the ASP is already marked as ASP- received ASP Inactive message from the ASP and the ASP is already
INACTIVE at the SGP. marked as ASP-INACTIVE at the SGP.
At the ASP, the ASP Inactive Ack message received is not acknowledged. At the ASP, the ASP Inactive Ack message received is not
Layer Management is informed with an M-ASP_INACTIVE confirm primitive. acknowledged. Layer Management is informed with an M-ASP_INACTIVE
If the ASP receives an ASP Inactive Ack without having sent an ASP confirm primitive. If the ASP receives an ASP Inactive Ack without
Inactive message, the ASP should now consider itself as in the having sent an ASP Inactive message, the ASP should now consider
ASP-INACTIVE state. If the ASP was previously in the ASP-ACTIVE itself as in the ASP-INACTIVE state. If the ASP was previously in
state, the ASP should then initiate procedures to return itself to the ASP-ACTIVE state, the ASP should then initiate procedures to
its previous state. return itself to its previous state.
When the ASP sends an ASP Inactive message it starts timer T(ack). If When the ASP sends an ASP Inactive message it starts timer T(ack).
the ASP does not receive a response to an ASP Inactive message within If the ASP does not receive a response to an ASP Inactive message
T(ack), the ASP MAY restart T(ack) and resend ASP Inactive messages within T(ack), the ASP MAY restart T(ack) and resend ASP Inactive
until it receives an ASP Inactive Ack message. T(ack) is messages until it receives an ASP Inactive Ack message. T(ack) is
provisionable, with a default of 2 seconds. Alternatively, provisionable, with a default of 2 seconds. Alternatively,
retransmission of ASP Inactive messages MAY be put under control of retransmission of ASP Inactive messages MAY be put under control of
Layer Management. In this method, expiry of T(ack) results in a M- Layer Management. In this method, expiry of T(ack) results in a M-
ASP_Inactive confirm primitive carrying a negative indication. ASP_Inactive confirm primitive carrying a negative indication.
If no other ASPs in the Application Server are in the state If no other ASPs in the Application Server are in the state ASP-
ASP-ACTIVE, the SGP MUST send a Notify message ("AS-Pending") to ACTIVE, the SGP MUST send a Notify message ("AS-Pending") to all of
all of the ASPs in the AS which are in the state ASP-INACTIVE. the ASPs in the AS which are in the state ASP-INACTIVE. The SGP
The SGP SHOULD start buffering the incoming messages for T(r) SHOULD start buffering the incoming messages for T(r) seconds, after
seconds, after which messages MAY be discarded. T(r) is which messages MAY be discarded. T(r) is configurable by the network
configurable by the network operator. If the SGP receives an ASP operator. If the SGP receives an ASP Active message from an ASP in
Active message from an ASP in the AS before expiry of T(r), the the AS before expiry of T(r), the buffered traffic is directed to
buffered traffic is directed to that ASP and the timer is cancelled. that ASP and the timer is cancelled. If T(r) expires, the AS is moved
If T(r) expires, the AS is moved to the AS-INACTIVE state. to the AS-INACTIVE state.
4.3.4.4.1 IPSP Considerations (ASP Inactive) 4.3.4.4.1 IPSP Considerations (ASP Inactive)
An IPSP may be considered in the ASP-INACTIVE state by a remote IPSP An IPSP may be considered in the ASP-INACTIVE state by a remote IPSP
after an ASP Inactive or ASP Inactive Ack message has been received from after an ASP Inactive or ASP Inactive Ack message has been received
it. from it.
Alternatively, an interchange of ASP Inactive messages from each end can Alternatively, an interchange of ASP Inactive messages from each end
be performed. This option follows the ASP state transition diagram and can be performed. This option follows the ASP state transition
gives the additional advantage of selecting a particular AS to be diagram and gives the additional advantage of selecting a particular
deactivated from each end. It is especially useful when an IPSP is AS to be deactivated from each end. It is especially useful when an
serving more than one AS. It would need four messages for completion. IPSP is serving more than one AS. It would need four messages for
completion.
4.3.4.5 Notify Procedures 4.3.4.5 Notify Procedures
A Notify message reflecting a change in the AS state MUST be sent to A Notify message reflecting a change in the AS state MUST be sent to
all ASPs in the AS, except those in the ASP-DOWN state, with all ASPs in the AS, except those in the ASP-DOWN state, with
appropriate Status Information and any ASP Identifier of the failed appropriate Status Information and any ASP Identifier of the failed
ASP. At the ASP, Layer Management is informed with an M-NOTIFY ASP. At the ASP, Layer Management is informed with an M-NOTIFY
indication primitive. The Notify message must be sent whether the indication primitive. The Notify message must be sent whether the AS
AS state change was a result of an ASP failure or reception of an state change was a result of an ASP failure or reception of an ASP
ASP State management (ASPSM) / ASP Traffic Management (ASPTM) State management (ASPSM) / ASP Traffic Management (ASPTM) message.
message. In the second case, the Notify message MUST be sent after In the second case, the Notify message MUST be sent after any related
any related acknowledgement messages (e.g., ASP Up Ack, ASP Down acknowledgement messages (e.g., ASP Up Ack, ASP Down Ack, ASP Active
Ack, ASP Active Ack, or ASP Inactive Ack). Ack, or ASP Inactive Ack).
In the case where a Notify message("AS-PENDING") message is sent by In the case where a Notify message ("AS-PENDING") message is sent by
an SGP that now has no ASPs active to service the traffic, or where a an SGP that now has no ASPs active to service the traffic, or where a
Notify ("Insufficient ASP resources active in AS") message is Notify ("Insufficient ASP resources active in AS") message is sent in
sent in the Loadshare or Broadcast mode, the Notify message does not the Loadshare or Broadcast mode, the Notify message does not
explicitly compel the ASP(s) receiving the message to become explicitly compel the ASP(s) receiving the message to become active.
active. The ASPs remain in control of what (and when) traffic action The ASPs remain in control of what (and when) traffic action is
is taken. taken.
In the case where a Notify message does not contain a Routing Context In the case where a Notify message does not contain a Routing Context
parameter, the receiver must know, via configuration data, of which parameter, the receiver must know, via configuration data, of which
Application Servers the ASP is a member and take the appropriate Application Servers the ASP is a member and take the appropriate
action in each AS. action in each AS.
4.3.4.5.1 IPSP Considerations (NTFY) 4.3.4.5.1 IPSP Considerations (NTFY)
Notify works in the same manner as in the SG-AS case. One of the IPSPs Notify works in the same manner as in the SG-AS case. One of the
can send this message to any remote IPSP that is not in the ASP-DOWN IPSPs can send this message to any remote IPSP that is not in the
state. ASP-DOWN state.
4.3.4.6 Heartbeat Procedures 4.3.4.6 Heartbeat Procedures
The optional Heartbeat procedures MAY be used when operating over The optional Heartbeat procedures MAY be used when operating over
transport layers that do not have their own heartbeat mechanism for transport layers that do not have their own heartbeat mechanism for
detecting loss of the transport association (i.e., other than SCTP). detecting loss of the transport association (i.e., other than SCTP).
Either M3UA peer may optionally send Heartbeat messages periodically, Either M3UA peer may optionally send Heartbeat messages periodically,
subject to a provisionable timer T(beat). Upon receiving a Heartbeat subject to a provisionable timer T(beat). Upon receiving a Heartbeat
message, the M3UA peer MUST respond with a Heartbeat Ack message. message, the M3UA peer MUST respond with a Heartbeat Ack message.
If no Heartbeat Ack message (or any other M3UA message) is received If no Heartbeat Ack message (or any other M3UA message) is received
from the M3UA peer within 2*T(beat), the remote M3UA peer is from the M3UA peer within 2*T(beat), the remote M3UA peer is
considered unavailable. Transmission of Heartbeat messages is considered unavailable. Transmission of Heartbeat messages is
stopped and the signalling process SHOULD attempt to re-establish stopped and the signalling process SHOULD attempt to re-establish
communication if it is configured as the client for the communication if it is configured as the client for the disconnected
disconnected M3UA peer. M3UA peer.
The Heartbeat message may optionally contain an opaque Heartbeat Data The Heartbeat message may optionally contain an opaque Heartbeat Data
parameter that MUST be echoed back unchanged in the related Heartbeat parameter that MUST be echoed back unchanged in the related Heartbeat
Ack message. The sender, upon examining the contents of the returned Ack message. The sender, upon examining the contents of the returned
Heartbeat Ack message, MAY choose to consider the remote M3UA peer as Heartbeat Ack message, MAY choose to consider the remote M3UA peer as
unavailable. The contents/format of the Heartbeat Data parameter is unavailable. The contents/format of the Heartbeat Data parameter is
implementation-dependent and only of local interest to the original implementation-dependent and only of local interest to the original
sender. The contents may be used, for example, to support a Heartbeat sender. The contents may be used, for example, to support a
sequence algorithm (to detect missing Heartbeats), and/or a timestamp Heartbeat sequence algorithm (to detect missing Heartbeats), and/or a
mechanism (to evaluate delays). timestamp mechanism (to evaluate delays).
Note: Heartbeat related events are not shown in Figure 4 "ASP state Note: Heartbeat related events are not shown in Figure 3 "ASP state
transition diagram". transition diagram".
4.4 Routing Key Management Procedures [Optional] 4.4 Routing Key Management Procedures [Optional]
4.4.1 Registration 4.4.1 Registration
An ASP MAY dynamically register with an SGP as an ASP within an An ASP MAY dynamically register with an SGP as an ASP within an
Application Server using the REG REQ message. A Routing Key parameter Application Server using the REG REQ message. A Routing Key
in the REG REQ message specifies the parameters associated with the parameter in the REG REQ message specifies the parameters associated
Routing Key. with the Routing Key.
The SGP examines the contents of the received Routing Key parameter and The SGP examines the contents of the received Routing Key parameter
compares it with the currently provisioned Routing Keys. If the and compares it with the currently provisioned Routing Keys. If the
received Routing Key matches an existing SGP Routing Key entry, and the received Routing Key matches an existing SGP Routing Key entry, and
ASP is not currently included in the list of ASPs for the related the ASP is not currently included in the list of ASPs for the related
Application Server, the SGP MAY authorize the ASP to be added to the Application Server, the SGP MAY authorize the ASP to be added to the
AS. Or, if the Routing Key does not currently exist and the received AS. Or, if the Routing Key does not currently exist and the received
Routing Key data is valid and unique, an SGP supporting dynamic Routing Key data is valid and unique, an SGP supporting dynamic
configuration MAY authorize the creation of a new Routing Key and configuration MAY authorize the creation of a new Routing Key and
related Application Server and add the ASP to the new AS. In either related Application Server and add the ASP to the new AS. In either
case, the SGP returns a Registration Response message to the ASP, case, the SGP returns a Registration Response message to the ASP,
containing the same Local-RK-Identifier as provided in the initial containing the same Local-RK-Identifier as provided in the initial
request, and a Registration Result "Successfully Registered". A unique request, and a Registration Result "Successfully Registered". A
Routing Context value assigned to the SGP Routing Key is included. The unique Routing Context value assigned to the SGP Routing Key is
method of Routing Context value assignment at the SGP is included. The method of Routing Context value assignment at the SGP
implementation dependent but must be guaranteed to be unique for each is implementation dependent but must be guaranteed to be unique for
Application Server or Routing Key supported by the SGP. each Application Server or Routing Key supported by the SGP.
If the SGP does not support the registration procedure, the SGP returns If the SGP does not support the registration procedure, the SGP
an Error message to the ASP, with an error code of "Unsupported Message returns an Error message to the ASP, with an error code of
Type". "Unsupported Message Type".
If the SGP determines that the received Routing Key data is invalid, or If the SGP determines that the received Routing Key data is invalid,
contains invalid parameter values, the SGP returns a Registration or 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 Routing Key", "Error - Invalid DPC", "Error - Invalid Network Invalid Routing Key", "Error - Invalid DPC", "Error - Invalid Network
Appearance" as appropriate. Appearance" as appropriate.
If the SGP determines that a unique Routing Key cannot be created, the If the SGP determines that a unique Routing Key cannot be created,
SGP returns a Registration Response message to the ASP, with a the SGP returns a Registration Response message to the ASP, with a
Registration Status of "Error - "Cannot Support Unique Routing" An Registration Status of "Error - "Cannot Support Unique Routing" An
incoming signalling message received at an SGP should not match against incoming signalling message received at an SGP should not match
more than one Routing Key. against more than one Routing Key.
If the SGP does not authorize an otherwise valid registration If the SGP does not authorize an otherwise valid registration
request, the SGP returns a REG RSP message to the ASP containing the request, the SGP returns a REG RSP message to the ASP containing the
Registration Result "Error - Permission Denied". Registration Result "Error - Permission Denied".
If an SGP determines that a received Routing Key does not currently If an SGP determines that a received Routing Key does not currently
exist and the SGP does not support dynamic configuration, the SGP exist and the SGP does not support dynamic configuration, the SGP
returns a Registration Response message to the ASP, containing a returns a Registration Response message to the ASP, containing a
Registration Result "Error - Routing Key not Currently Provisioned". Registration Result "Error - Routing Key not Currently Provisioned".
If an SGP determines that a received Routing Key does not currently If an SGP determines that a received Routing Key does not currently
exist and the SGP supports dynamic configuration but does not have the exist and the SGP supports dynamic configuration but does not have
capacity to add new Routing Key and Application Server entries, the SGP the capacity to add new Routing Key and Application Server entries,
returns a Registration Response message to the ASP, containing a the SGP returns a Registration Response message to the ASP,
Registration Result "Error - Insufficient Resources". containing a Registration Result "Error - Insufficient Resources".
If an SGP determines that one or more of the Routing Key parameters are If an SGP determines that one or more of the Routing Key parameters
not supported for the purpose of creating new Routing Key entries, the are not supported for the purpose of creating new Routing Key
SGP returns a Registration Response message to the ASP, containing a entries, the SGP returns a Registration Response message to the ASP,
Registration Result "Error - Unsupported RK parameter field". This containing a Registration Result "Error - Unsupported RK parameter
result MAY be used if, for example, the SGP does not support RK Circuit field". This result MAY be used if, for example, the SGP does not
Range Lists in a Routing Key because the SGP does not support ISUP support RK Circuit Range Lists in a Routing Key because the SGP does
traffic, or does not provide CIC range granularity. not support ISUP traffic, or does not provide CIC range granularity.
A Registration Response "Error - Unsupported Traffic Handling Mode" is A Registration Response "Error - Unsupported Traffic Handling Mode"
returned if the Routing Key in the REG REQ contains an Traffic Handling is returned if the Routing Key in the REG REQ contains an Traffic
Mode that is inconsistent with the presently configured mode for the Handling Mode that is inconsistent with the presently configured mode
matching Application Server. for the matching Application Server.
An ASP MAY register multiple Routing Keys at once by including a number An ASP MAY register multiple Routing Keys at once by including a
of Routing Key parameters in a single REG REQ message. The SGP MAY number of Routing Key parameters in a single REG REQ message. The
respond to each registration request in a single REG RSP message, SGP MAY respond to each registration request in a single REG RSP
indicating the success or failure result for each Routing Key in a message, indicating the success or failure result for each Routing
separate Registration Result parameter. Alternatively the SGP MAY Key in a separate Registration Result parameter. Alternatively the
respond with multiple REG RSP messages, each with one or more SGP MAY respond with multiple REG RSP messages, each with one or more
Registration Result parameters. The ASP uses the Local-RK-Identifier Registration Result parameters. The ASP uses the Local-RK-Identifier
parameter to correlate the requests with the responses. parameter to correlate the requests with the responses.
Upon successful registration of an ASP in an AS, the SGP can now send Upon successful registration of an ASP in an AS, the SGP can now send
related SS7 Signalling Network Management messaging, if this did not related SS7 Signalling Network Management messaging, if this did not
previously start upon the ASP transitioning to state ASP-INACTIVE previously start upon the ASP transitioning to state ASP-INACTIVE
4.4.2 Deregistration 4.4.2 Deregistration
An ASP MAY dynamically deregister with an SGP as an ASP within an An ASP MAY dynamically deregister with an SGP as an ASP within an
Application Server using the DEREG REQ message. A Routing Context Application Server using the DEREG REQ message. A Routing Context
parameter in the DEREG REQ message specifies which Routing Keys to parameter in the DEREG REQ message specifies which Routing Keys to
deregister. An ASP SHOULD move to the ASP-INACTIVE state for an deregister. An ASP SHOULD move to the ASP-INACTIVE state for an
Application Server before attempting to deregister the Routing Key Application Server before attempting to deregister the Routing Key
(i.e., deregister after receiving an ASP Inactive Ack). Also, an ASP (i.e., deregister after receiving an ASP Inactive Ack). Also, an ASP
SHOULD deregister from all Application Servers that it is a member SHOULD deregister from all Application Servers that it is a member
before attempting to move to the ASP-Down state. before attempting to move to the ASP-Down state.
The SGP examines the contents of the received Routing Context parameter The SGP examines the contents of the received Routing Context
and validates that the ASP is currently registered in the Application parameter and validates that the ASP is currently registered in the
Server(s) related to the included Routing Context(s). If validated, Application Server(s) related to the included Routing Context(s). If
the ASP is deregistered as an ASP in the related Application Server. validated, the ASP is deregistered as an ASP in the related
Application Server.
The deregistration procedure does not necessarily imply the deletion of The deregistration procedure does not necessarily imply the deletion
Routing Key and Application Server configuration data at the SG. Other of Routing Key and Application Server configuration data at the SG.
ASPs may continue to be associated with the Application Server, in Other ASPs may continue to be associated with the Application Server,
which case the Routing Key data SHOULD NOT be deleted. If a in which case the Routing Key data SHOULD NOT be deleted. If a
Deregistration results in no more ASPs in an Application Server, an SG Deregistration results in no more ASPs in an Application Server, an
MAY delete the Routing Key data. SG MAY delete the Routing Key data.
The SGP acknowledges the deregistration request by returning a DEREG The SGP acknowledges the deregistration request by returning a DEREG
RSP message to the requesting ASP. The result of the deregistration is RSP message to the requesting ASP. The result of the deregistration
found in the Deregistration Result parameter, indicating success or is found in the Deregistration Result parameter, indicating success
failure with cause. or failure with cause.
An ASP MAY deregister multiple Routing Contexts at once by including a An ASP MAY deregister multiple Routing Contexts at once by including
number of Routing Contexts in a single DEREG REQ message. The SGP MAY a number of Routing Contexts in a single DEREG REQ message. The SGP
respond to each deregistration request in a single DEREG RSP message, MAY respond to each deregistration request in a single DEREG RSP
indicating the success or failure result for each Routing Context in a message, indicating the success or failure result for each Routing
separate Deregistration Result parameter. Context in a separate Deregistration Result parameter.
4.4.3 IPSP Considerations (REG/DEREG) 4.4.3 IPSP Considerations (REG/DEREG)
The Registration/Deregistration procedures work in the IPSP cases in the The Registration/Deregistration procedures work in the IPSP cases in
same way as in AS-SG cases. An IPSP may register an RK in the remote the same way as in AS-SG cases. An IPSP may register an RK in the
IPSP. An IPSP is responsible for deregistering the RKs that it has remote IPSP. An IPSP is responsible for deregistering the RKs that
registered. it has registered.
4.5 Procedures to Support the Availability or Congestion Status of SS7 4.5 Procedures to Support the Availability or Congestion Status of SS7
Destination Destination
4.5.1 At an SGP 4.5.1 At an SGP
On receiving an MTP-PAUSE, MTP-RESUME or MTP-STATUS indication On receiving an MTP-PAUSE, MTP-RESUME or MTP-STATUS indication
primitive from the nodal interworking function at an SGP, the SGP M3UA primitive from the nodal interworking function at an SGP, the SGP
layer will send a corresponding SS7 Signalling Network Management M3UA layer will send a corresponding SS7 Signalling Network
(SSNM) DUNA, DAVA, SCON, or DUPU message (see Section 3.4) to the M3UA Management (SSNM) DUNA, DAVA, SCON, or DUPU message (see Section 3.4)
peers at concerned ASPs. The M3UA layer must fill in various fields of to the M3UA peers at concerned ASPs. The M3UA layer must fill in
the SSNM messages consistently with the information received in the various fields of the SSNM messages consistently with the information
primitives. received in the primitives.
The SGP M3UA layer determines the set of concerned ASPs to be informed The SGP M3UA layer determines the set of concerned ASPs to be
based on the specific SS7 network for which the primitive indication informed based on the specific SS7 network for which the primitive
is relevant. In this way, all ASPs configured to send/receive traffic indication is relevant. In this way, all ASPs configured to
within a particular network appearance are informed. If the SGP send/receive traffic within a particular network appearance are
operates within a single SS7 network appearance, then all ASPs are informed. If the SGP operates within a single SS7 network
informed. appearance, then all ASPs are informed.
DUNA, DAVA, SCON, and DRST messages may be sent sequentially and DUNA, DAVA, SCON, and DRST messages may be sent sequentially and
processed at the receiver in the order sent. processed at the receiver in the order sent.
Sequencing is not required for the DUPU or DAUD messages, which MAY Sequencing is not required for the DUPU or DAUD messages, which MAY
be sent unsequenced. be sent unsequenced.
4.5.2 At an ASP 4.5.2 At an ASP