draft-ietf-sigtran-rfc3332bis-06.txt   rfc4666.txt 
Network Working Group K. Morneault Network Working Group K. Morneault, Ed.
INTERNET-DRAFT Cisco Systems Request for Comments: 4666 Cisco Systems
Obsoletes: 3332 J. Pastor-Balbas Obsoletes: 3332 J. Pastor-Balbas, Ed.
Ericsson Category: Standards Track Ericsson
September 2006
Signaling System 7 (SS7) Message Transfer Part 3 (MTP3) - Signaling System 7 (SS7) Message Transfer Part 3 (MTP3) -
User Adaptation Layer (M3UA) User Adaptation Layer (M3UA)
<draft-ietf-sigtran-rfc3332bis-06.txt>
STATUS OF THIS MEMO
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working 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
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 Status of This Memo
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire August 2006. This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). All Rights Reserved. Copyright (C) The Internet Society (2006).
Abstract Abstract
This memo defines a protocol for supporting the transport of any SS7 This memo defines a protocol for supporting the transport of any SS7
MTP3-User signalling (e.g., ISUP and SCCP messages) over IP using the MTP3-User signalling (e.g., ISUP and SCCP messages) over IP 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, or between two Gateway Controller (MGC) or IP-resident Database, or between two IP-
IP-based applications. It is assumed that the SG receives SS7 based applications. It is assumed that the SG receives SS7
signalling over a standard SS7 interface using the SS7 Message signalling over a standard SS7 interface using the SS7 Message
Transfer Part (MTP) to provide transport. This document obsoletes Transfer Part (MTP) to provide transport. This document obsoletes
RFC 3332. RFC 3332.
TABLE OF CONTENTS Table of Contents
1. Introduction.....................................................5 1. Introduction ....................................................6
1.1 Scope............................................................5 1.1. Scope ......................................................6
1.2 Terminology......................................................5 1.2. Terminology ................................................6
1.3 M3UA Overview....................................................7 1.3. M3UA Overview ..............................................9
1.4 Functional Areas................................................11 1.3.1. Protocol Architecture ...............................9
1.5 Sample Configuration............................................18 1.3.2. Services Provided by the M3UA Layer ................10
1.6 Definition of M3UA Boundaries...................................20 1.3.2.1. Support for the Transport of
2. Conventions......................................................24 MTP3-User Messages ........................10
3. M3UA Protocol Elements...........................................24 1.3.2.2. Native Management Functions ...............11
3.1 Common Message Header...........................................25 1.3.2.3. Interworking with MTP3 Network
3.2 Variable Length Parameter Format................................27 Management Functions ......................11
3.3 Transfer Messages...............................................29 1.3.2.4. Support for the Management of SCTP
3.4 SS7 Signalling Network Management (SSNM) Messages...............32 Associations between the ..................11
3.5 ASP State Maintenance (ASPSM) Messages..........................41 1.3.2.5. Support for the Management of
3.6 Routing Key Management (RKM) Messages [Optional]................44 Connections to Multiple SGPs ..............12
3.7 ASP Traffic Maintenance (ASPTM) Messages........................52 1.4. Functional Areas ..........................................12
3.8 Management (MGMT) Messages.....................................57 1.4.1. Signalling Point Code Representation ...............12
4. Procedures.......................................................62 1.4.2. Routing Contexts and Routing Keys ..................14
4.1 Procedures to Support the M3UA-User.............................62 1.4.2.1. Overview ..................................14
4.2 Receipt of Primitives from the Layer Management.................63 1.4.2.2. Routing Key Limitations ...................15
4.3 AS and ASP/IPSP State Maintenance...............................65 1.4.2.3. Managing Routing Contexts and
4.4 Routing Key Management Procedures [Optional]....................81 Routing Keys ..............................15
4.5 Procedures to Support the Availability or Congestion Status of 1.4.2.4. Message Distribution at the SGP ...........15
SS7 Destination.................................................84 1.4.2.5. Message Distribution at the ASP ...........16
4.6 MTP3 Restart....................................................86 1.4.3. SS7 and M3UA Interworking ..........................16
4.7 NIF not Available...............................................87 1.4.3.1. Signalling Gateway SS7 Layers .............16
4.8 M3UA Version Control............................................88 1.4.3.2. SS7 and M3UA Interworking at the SG .......17
4.9 M3UA Termination................................................88 1.4.3.3. Application Server ........................17
5. Examples of M3UA Procedures......................................88 1.4.3.4. IPSP Considerations .......................18
5.1 Establishment of Association and Traffic between SGPs and ASPs..88 1.4.4. Redundancy Models ..................................18
5.2 ASP Traffic Failover Examples...................................94 1.4.4.1. Application Server Redundancy .............18
5.3 Normal Withdrawal of an ASP from an Application Server..........95 1.4.5. Flow Control .......................................18
5.4 Auditing examples...............................................96 1.4.6. Congestion Management ..............................19
5.5 M3UA/MTP3-User Boundary Examples................................96 1.4.7. SCTP Stream Mapping ................................19
5.6 Examples for IPSP communication................................100 1.4.8. SCTP Client/Server Model ...........................19
6. Security Considerations.........................................101 1.5. Sample Configuration ......................................20
7. IANA Considerations.............................................101 1.5.1. Example 1: ISUP Message Transport ..................20
7.1 SCTP Payload Protocol Identifier...............................102 1.5.2. Example 2: SCCP Transport between IPSPs ............21
7.2 M3UA Port Number...............................................102 1.5.3. Example 3: SGP Resident SCCP Layer, with
7.3 M3UA Protocol Extensions.......................................103 Remote ASP .........................................22
8. References......................................................103 1.6. Definition of M3UA Boundaries .............................23
8.1 Normative References...........................................103 1.6.1. Definition of the Boundary between M3UA and
8.2 Informative References.........................................104 an MTP3-User .......................................23
9. Acknowledgements................................................105 1.6.2. Definition of the Boundary between M3UA and SCTP ...23
10. Document Contributors..........................................106 1.6.3. Definition of the Boundary between M3UA and
11. Change Log.....................................................106 Layer Management ...................................24
Appendix A.........................................................107 2. Conventions ....................................................27
A.1 Signalling Network Architecture................................108 3. M3UA Protocol Elements .........................................28
A.2 Redundancy Models..............................................110 3.1. Common Message Header .....................................28
Editors' Addresses.................................................113 3.1.1. M3UA Protocol Version: 8 bits (unsigned integer) ...28
3.1.2. Message Classes and Types ..........................28
3.1.3. Reserved: 8 Bits ...................................30
3.1.4. Message Length: 32-Bits (Unsigned Integer) .........30
3.2. Variable-Length Parameter Format ..........................30
3.3. Transfer Messages .........................................33
3.3.1. Payload Data Message (DATA) ........................33
3.4. SS7 Signalling Network Management (SSNM) Messages .........36
3.4.1. Destination Unavailable (DUNA) .....................36
3.4.2. Destination Available (DAVA) .......................39
3.4.3. Destination State Audit (DAUD) .....................40
3.4.4. Signalling Congestion (SCON) .......................40
3.4.5. Destination User Part Unavailable (DUPU) ...........43
3.4.6. Destination Restricted (DRST) ......................45
3.5. ASP State Maintenance (ASPSM) Messages ....................45
3.5.1. ASP Up .............................................45
3.5.2. ASP Up Acknowledgement (ASP Up Ack) ................46
3.5.3. ASP Down ...........................................47
3.5.4. ASP Down Acknowledgement (ASP Down Ack) ............48
3.5.5. Heartbeat (BEAT) ...................................48
3.5.6. Heartbeat Acknowledgement (BEAT Ack) ...............49
3.6. Routing Key Management (RKM) Messages [Optional] ..........49
3.6.1. Registration Request (REG REQ) .....................49
3.6.2. Registration Response (REG RSP) ....................54
3.6.3. Deregistration Request (DEREG REQ) .................56
3.6.4. Deregistration Response (DEREG RSP) ................57
3.7. ASP Traffic Maintenance (ASPTM) Messages ..................59
3.7.1. ASP Active .........................................59
3.7.2. ASP Active Acknowledgement (ASP Active Ack) ........60
3.7.3. ASP Inactive .......................................61
3.7.4. ASP Inactive Acknowledgement (ASP Inactive Ack) ....62
3.8. Management (MGMT) Messages ................................63
3.8.1. Error ..............................................63
3.8.2. Notify .............................................67
4. Procedures .....................................................70
4.1. Procedures to Support the M3UA-User .......................70
4.1.1. Receipt of Primitives from the M3UA-User ...........70
4.2. Receipt of Primitives from the Layer Management ...........71
4.2.1. Receipt of M3UA Peer Management Messages ...........72
4.3. AS and ASP/IPSP State Maintenance .........................73
4.3.1. ASP/IPSP States ....................................74
4.3.2. AS States ..........................................76
4.3.3. M3UA Management Procedures for Primitives ..........78
4.3.4. ASPM Procedures for Peer-to-Peer Messages ..........79
4.3.4.1. ASP Up Procedures .........................79
4.3.4.2. ASP-Down Procedures .......................81
4.3.4.3. ASP Active Procedures .....................82
4.3.4.4. ASP Inactive Procedures ...................86
4.3.4.5. Notify Procedures .........................88
4.3.4.6. Heartbeat Procedures ......................89
4.4. Routing Key Management Procedures [Optional] ..............90
4.4.1. Registration .......................................90
4.4.2. Deregistration .....................................92
4.4.3. IPSP Considerations (REG/DEREG) ....................93
4.5. Procedures to Support the Availability or
Congestion Status of SS7 Destination ......................93
4.5.1. At an SGP ..........................................93
4.5.2. At an ASP ..........................................94
4.5.2.1. Single SG Configurations ..................94
4.5.2.2. Multiple SG Configurations ................94
4.5.3. ASP Auditing .......................................94
4.6. MTP3 Restart ..............................................96
4.7. NIF Not Available .........................................97
4.8. M3UA Version Control ......................................97
4.9. M3UA Termination ..........................................97
5. Examples of M3UA Procedures ....................................98
5.1. Establishment of Association and Traffic between
SGPs and ASPs .............................................98
5.1.1. Single ASP in an Application Server ("1+0"
sparing), No Registration ..........................98
5.1.1.1. Single ASP in an Application
Server ("1+0" Sparing), No Registration ...98
5.1.1.2. Single ASP in Application Server
("1+0" Sparing), Dynamic Registration .....99
5.1.1.3. Single ASP in Multiple
Application Servers (Each with "1+0"
Sparing), Dynamic Registration (Case 1
- Multiple Registration Requests) ........100
5.1.1.4. Single ASP in Multiple
Application Servers (each with "1+0"
sparing), Dynamic Registration (Case 2
- Single Registration Request) ...........101
5.1.2. Two ASPs in Application Server ("1+1" Sparing) ....102
5.1.3. Two ASPs in an Application Server ("1+1"
Sparing, Loadsharing Case) ........................103
5.1.4. Three ASPs in an Application Server ("n+k"
Sparing, Loadsharing Case) ........................104
5.2. ASP Traffic Failover Examples ............................105
5.2.1. 1+1 Sparing, Withdrawal of ASP, Backup Override ...105
5.2.2. 1+1 Sparing, Backup Override ......................105
5.2.3. n+k Sparing, Loadsharing Case, Withdrawal of ASP ..106
5.3. Normal Withdrawal of an ASP from an Application Server ...106
5.4. Auditing Examples ........................................107
5.4.1. SG State: Uncongested/Available ...................107
5.4.2. SG State: Congested (Congestion Level=2) /
Available .........................................107
5.4.3. SG State: Unknown/Available .......................107
5.4.4. SG State: Unavailable .............................108
5.5. M3UA/MTP3-User Boundary Examples .........................108
5.5.1. At an ASP .........................................108
5.5.1.1. Support for MTP-TRANSFER
Primitives at the ASP ....................108
5.5.2. At an SGP .........................................109
5.5.2.1. Support for MTP-TRANSFER Request
Primitive at the SGP .....................109
5.5.2.2. Support for MTP-TRANSFER
Indication Primitive at the SGP ..........110
5.5.2.3. Support for MTP-PAUSE,
MTP-RESUME, MTP-STATUS Indication
Primitives ...............................110
5.6. Examples for IPSP Communication ..........................112
5.6.1. Single Exchange ...................................112
5.6.2. Double Exchange ...................................113
6. Security Considerations .......................................113
7. IANA Considerations ...........................................114
7.1. SCTP Payload Protocol Identifier .........................114
7.2. M3UA Port Number .........................................114
7.3. M3UA Protocol Extensions .................................114
7.3.1. IETF-Defined Message Classes ......................115
7.3.2. IETF Defined Message Types ........................115
7.3.3. IETF-Defined Parameter Extension ..................115
8. Acknowledgements ..............................................115
9. Document Contributors .........................................116
10. References ...................................................116
10.1. Normative References ....................................116
10.2. Informative References ..................................117
Appendix A .......................................................119
A.1. Signalling Network Architecture .............................119
A.2. Redundancy Models ...........................................121
A.2.1. Application Server Redundancy ........................121
A.2.2. Signalling Gateway Redundancy ........................122
1. Introduction 1. Introduction
This memo defines a protocol for supporting the transport of any SS7 This memo defines a protocol for supporting the transport of any SS7
MTP3-User signalling (e.g., ISUP and SCCP messages) over IP using the MTP3-User signalling (e.g., ISUP and SCCP messages) over IP using the
services of the Stream Control Transmission Protocol [17]. Also, services of the Stream Control Transmission Protocol [18]. 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], or between two Gateway Controller (MGC) or IP-resident Database [12], or between two
IP-based applications. IP-based applications.
1.1 Scope 1.1. Scope
There is a need for Switched Circuit Network (SCN) signalling There is a need for Switched Circuit Network (SCN) signalling
protocol delivery from an SS7 Signalling Gateway (SG) to a Media protocol delivery from an SS7 Signalling Gateway (SG) to a Media
Gateway Controller (MGC) or IP-resident Database as described in the Gateway Controller (MGC) or IP-resident Database as described in the
Framework Architecture for Signalling Transport [11]. The delivery Framework Architecture for Signalling Transport [12]. The delivery
mechanism 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 [13], 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 traffic between an SG and one or more MGCs or IP-resident
Databases Databases
* Support for MGC or IP-resident Database process failover and load * Support for MGC or IP-resident database process failover and load
sharing sharing
* Support for the asynchronous reporting of status changes to * Support for the asynchronous reporting of status changes to
management management
In simplistic transport terms, the SG will terminate SS7 MTP2 and In simplistic transport terms, the SG will terminate SS7 MTP2 and
MTP3 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 MTP3-User protocol messages, as well as certain MTP network
management events, over SCTP transport associations to MTP3-User management events, over SCTP transport associations to MTP3-User
peers in MGCs or 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 signalling relation, identified by handling all call processing for a signalling relation, identified by
a SS7 DPC/OPC. Another example is a virtual database element, an SS7 DPC/OPC. Another example is a virtual database element,
handling all HLR transactions for a particular SS7 SIO/DPC/OPC handling all HLR transactions for a particular SS7 SIO/DPC/OPC
combination. The AS contains a set of one or more unique Application combination. The AS contains a set of one or more unique Application
Server Processes, of which one or more is normally actively processing Server Processes, of which one or more is normally actively
traffic. Note that there is a 1:1 relationship between an AS and a processing traffic. Note that there is a 1:1 relationship between an
Routing Key. AS and a Routing Key.
Application Server Process (ASP) - A process instance of an Application Server Process (ASP) - A process instance of an
Application Server. An Application Server Process serves as an active Application Server. An Application Server Process serves as an
or backup process of an Application Server (e.g., part of a active or backup process of an Application Server (e.g., part of a
distributed virtual switch or database). Examples of ASPs are distributed virtual switch or database). Examples of ASPs are
processes (or process instances) of MGCs, IP SCPs or IP HLRs. An ASP processes (or process instances) of MGCs, IP SCPs, or IP HLRs. An
contains an SCTP endpoint and may be configured to process signalling ASP contains an SCTP endpoint and may be configured to process
traffic within more than one Application Server. signalling 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 application. An IPSP is essentially the same as an ASP, except that
it uses M3UA in a point-to-point fashion. Conceptually, an IPSP does it uses M3UA in a point-to-point fashion. Conceptually, an IPSP does
not use the services of a Signalling Gateway node. not use the services of a Signalling Gateway node.
skipping to change at page 6, line 38 skipping to change at page 7, line 41
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 to which it belongs. It can be used to
between signalling traffic associated with different networks being distinguish between signalling traffic associated with different
sent between the SG and the ASP over a common SCTP association. An networks being sent between the SG and the ASP over a common SCTP
example scenario is where an SG appears as an element in multiple association. An example scenario is where an SG appears as an
separate national SS7 networks and the same Signaling Point Code element in multiple separate national SS7 networks and the same
value may be reused in different networks. Signaling Point Code 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 to be handled by a particular Application Server. Parameters within
the Routing Key cannot extend across more than a single Signalling the Routing Key cannot extend across more than a single Signalling
Point 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 configured either using a configuration
management interface, or by using the routing key management management interface, or by using the routing key management
procedures defined in this document. procedures defined in this document.
Signaling End Point (SEP) - A node in the SS7 network associated with Signaling End Point (SEP) - A node in the SS7 network associated with
an originating or terminating local exchange (switch) or a gateway an originating or terminating local exchange (switch) or a gateway
exchange. exchange.
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, load-sharing 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 (SG) - An SG is a signaling agent that receives/ Signalling Gateway (SG) - An SG is a signaling agent that
sends SCN native signaling at the edge of the IP network [11]. An SG receives/sends SCN native signaling at the edge of the IP network
appears to the SS7 network as an SS7 Signalling Point. An SG [12]. An SG appears to the SS7 network as an SS7 Signalling Point.
contains a set of one or more unique Signalling Gateway Processes, of An SG contains a set of one or more unique Signalling Gateway
which one or more is normally actively processing traffic. Where an Processes, of which one or more is normally actively processing
SG contains more than one SGP, the SG is a logical entity and the traffic. Where an SG contains more than one SGP, the SG is a logical
contained SGPs are assumed to be coordinated into a single management entity, and the contained SGPs are assumed to be coordinated into a
view to the SS7 network and to the supported Application Servers. single management 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 are used to aggregate the availability, congestion, and user part
status of an MTP entity (Signalling Point) that is distributed in the status of an MTP entity (Signalling Point) that is distributed in the
IP 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
/User_Part status should also be taken into account when considering availability/congestion/User_Part status should also be taken into
any supporting MTP3 management actions. account when considering any supporting MTP3 management actions.
Signaling Transfer Point (STP) - A node in the SS7 network that Signaling Transfer Point (STP) - A node in the SS7 network that
provides network access and performs message routing, screening and provides network access and performs message routing, screening and
transfer of of signaling messages. transfer of signaling messages.
Stream - A stream refers to an SCTP stream; a unidirectional logical Stream - An SCTP stream; a unidirectional logical channel established
channel established from one SCTP endpoint to another associated SCTP from one SCTP endpoint to another associated SCTP endpoint, within
endpoint, within which all user messages are delivered in-sequence which all user messages are delivered in-sequence except for those
except for those submitted to the unordered delivery service. 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 [12] 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] (SCCP) [4,5,6], and Telephone User Part (TUP) [13]. TCAP [14,15,16]
or RANAP [16] messages are transferred transparently by the M3UA or RANAP [16] messages are transferred transparently by the M3UA
protocol 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) [18] 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
- 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 primitives at its upper layer to the MTP3-Users as provided by the
MTP Level 3 to its local MTP3-Users at an SS7 SEP. In this way, the MTP Level 3 to its local MTP3-Users at an SS7 SEP. In this way, the
ISUP and/or SCCP layer at an ASP or IPSP is unaware that the expected ISUP and/or SCCP layer at an ASP or IPSP is unaware that the expected
MTP3 services are offered remotely from an MTP3 Layer at an SGP, and MTP3 services are offered remotely from an MTP3 Layer at an SGP, and
not by a local MTP3 layer. The MTP3 layer at an SGP may also be not by a local MTP3 layer. The MTP3 layer at an SGP may also be
unaware that its local users are actually remote user parts over unaware that its local users are actually remote user parts over
M3UA. In effect, the M3UA extends access to the MTP3 layer services M3UA. In effect, the M3UA extends access to the MTP3 layer services
to a remote IP-based application. The M3UA layer does not itself to a remote IP-based application. The M3UA layer does not itself
provide the MTP3 services. However, in the case where an ASP is provide the MTP3 services. However, in the case where an ASP is
connected to more than one SG, the M3UA layer at an ASP should connected to more than one SG, the M3UA layer at an ASP should
maintain the status of configured SS7 destinations and route messages maintain the status of configured SS7 destinations and route messages
according to the availability and congestion status of the routes to according to the availability and congestion status of the routes to
these destinations via each SG. 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 two IP Server Processes (IPSPs). In this case, the M3UA layer
provides the same set of primitives and services at its upper layer provides the same set of primitives and services at its upper layer
as the MTP3. However, in this case the expected MTP3 services are not as the MTP3. However, in this case the expected MTP3 services are
offered remotely from an SGP. The MTP3 services are provided but the not offered remotely from an SGP. The MTP3 services are provided,
procedures to support these services are a subset of the MTP3 but the 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-
IPSP relationship. to-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 The M3UA layer provides the transport of MTP-TRANSFER primitives
across an established SCTP association between an SGP and an ASP or across an established SCTP association between an SGP and an ASP or
between 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, thereby
missequencing. minimizing missequencing.
The M3UA layer does not impose a 272-octet signalling information The M3UA layer does not impose a 272-octet signalling information
field (SIF) length limit as specified by the SS7 MTP Level 2 protocol field (SIF) length limit as specified by the SS7 MTP Level 2 protocol
[7,8,9]. Larger information blocks can be accommodated directly by [7,8,9]. Larger information blocks can be accommodated directly by
M3UA/SCTP, without the need for an upper layer segmentation/re- M3UA/SCTP, without the need for an upper layer segmentation/
assembly procedure as specified in recent SCCP or ISUP versions. re-assembly procedure as specified in recent SCCP or ISUP versions.
However, in the context of an SG, the maximum 272-octet block size However, in the context of an SG, the maximum 272-octet block size
must be followed when interworking to a SS7 network that does not must be followed when interworking to a SS7 network that does not
support the transfer of larger information blocks to the final support the transfer of larger information blocks to the final
destination. This avoids potential ISUP or SCCP fragmentation destination. This avoids potential ISUP or SCCP fragmentation
requirements at the SGPs. The provisioning and configuration of the requirements at the SGPs. The provisioning and configuration of the
SS7 network determines the restriction placed on the maximum block SS7 network determines the restriction placed on the maximum block
size. Some configurations (e.g., Broadband MTP [21]) may permit size. Some configurations (e.g., Broadband MTP [19,20,22]) may
larger block sizes. 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 management At the SGP, the M3UA layer provides interworking with MTP3 management
functions to support seamless operation of the user SCN signalling functions to support seamless operation of the user SCN 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; and
- 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 and 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
and ASPs. SGP 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 the configured remote ASPs, to manage the SCTP Associations and the
traffic between the M3UA peers. As well, the active/inactive and traffic between the M3UA peers. Also, 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 associations (e.g., via knowledge of the expected local and remote
SCTP 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 determined either locally within the M3UA layer or by a primitive
from 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 As shown in Figure 1, an ASP may be connected to multiple SGPs. In
such a case a particular SS7 destination may be reachable via more such a case, a particular SS7 destination may be reachable via more
than one SGP and/or SG, i.e., via more than one route. As MTP3 users than one SGP and/or SG; i.e., via more than one route. As MTP3 users
only maintain status on a destination and not on a route basis, the only maintain status on a destination and not on a route basis, the
M3UA layer must maintain the status (availability, restriction, M3UA layer must maintain the status (availability, restriction,
and/or congestion of route to destination) of the individual routes, and/or congestion of route to destination) of the individual routes,
derive the overall availability or congestion status of the derive the overall availability or congestion status of the
destination from the status of the individual routes, and inform the destination from the status of the individual routes, and inform the
MTP3 users 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 charged with representing a set of nodes in the IP domain into the
SS7 network for routing purposes. The SG itself, as a signalling SS7 network for routing purposes. The SG itself, as a signalling
point in the SS7 network, might also be addressable with an SS7 Point point in the SS7 network, might also be addressable with an SS7 Point
Code for MTP3 Management purposes. The SG Point Code might also be Code for MTP3 Management purposes. The SG Point Code might also be
used for addressing any local MTP3-Users at the SG such as a local used for addressing any local MTP3-Users at the SG such as a local
SCCP layer. 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 appearances. In such a case, the SG could be addressable with a
Point Code in each network appearance, and represents a set of nodes Point Code in each network appearance, and it represents a set of
in the IP domain into each SS7 network. Alias Point Codes [8] may nodes in the IP domain into each SS7 network. Alias Point Codes [8]
also be used within an SG network appearance. may 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 Code of Application Servers can be represented under the same Point Code of
the SG, their own individual Point Codes or grouped with other the SG, under 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 than one SG, each with its own Point Code, the ASP(s) will typically
be represented by a Point Code that is separate from any SG Point be represented by a Point Code that is separate from any SG Point
Code. This allows, for example, these SGs to be viewed from the SS7 Code. This allows, for example, these SGs to be viewed from the SS7
network as "STPs", each having an ongoing "route" to the same ASP(s). network as "STPs", each having an ongoing "route" to the same ASP(s).
Under failure conditions where the ASP(s) become(s) unavailable from Under failure conditions where the ASP(s) become(s) unavailable from
one of the SGs, this approach enables MTP3 route management messaging one of the SGs, this approach enables MTP3 route management messaging
between the SG and SS7 network, allowing simple SS7 rerouting through between the SG and SS7 network, allowing simple SS7 rerouting through
an alternate SG without changing the Destination Point Code Address an alternate SG without changing the Destination Point Code Address
of SS7 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" |
+--------+ +--------+
Figure 1 Example with mated SGs Figure 1. Example with mated SGs
* Note:. SG-to-SG communication (i.e., "C-links") is recommended for * Note: SG-to-SG communication (i.e., "C-links") is recommended
carrier grade networks, using an MTP3 linkset or an equivalent, to for carrier grade networks, using an MTP3 linkset or an
allow rerouting between the SGs in the event of route failures. Where equivalent, to allow rerouting between the SGs in the event of
SGPs are used, inter-SGP communication might be used. Inter-SGP route failures. Where SGPs are used, inter-SGP communication
protocol is outside of the scope of this document. might be used. Inter-SGP protocol is outside of the scope of this
document.
The following example shows a signalling gateway partitioned into two The following example shows a signalling gateway partitioned into
network appearances. two network appearances.
SG SG
+-------+ +---------------+ +-------+ +---------------+
| SEP +--------------| SS7 Ntwk.|M3UA| ---- | SEP +--------------| SS7 Ntwk.|M3UA| ----
+-------+ SS7 links | "A" | | / \ +-------+ SS7 links | "A" | | / \
|__________| +-----------+ ASPs | |__________| +-----------+ ASPs |
| | | \ / | | | \ /
+-------+ | SS7 Ntwk.| | ---- +-------+ | SS7 Ntwk.| | ----
| SEP +--------------+ "B" | | | SEP +--------------+ "B" | |
+-------+ +---------------+ +-------+ +---------------+
Figure 2 Example with multiple Network 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 Servers is determined by the Routing Keys and their associated
Routing Contexts. A Routing Key is essentially a set of SS7 Routing Contexts. A Routing Key is essentially a set of SS7
parameters used to filter SS7 messages, whereas the Routing Context parameters used to filter SS7 messages, whereas the Routing Context
parameter is a 4-octet value (integer) that is associated to that parameter is a 4-octet value (integer) that is associated to that
Routing Key in a 1:1 relationship. The Routing Context therefore can Routing Key in a 1:1 relationship. The Routing Context therefore can
be viewed as an index into a sending node's Message Distribution be viewed as an index into a sending node's Message Distribution
Table containing the Routing 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, and SIO found in the MTP3
routing label. Some example Routing Keys are: the DPC alone, the routing label. Some example Routing Keys are: the DPC alone, the
DPC/OPC combination, or the DPC/OPC/SI combination. The particular DPC/OPC combination, or the DPC/OPC/SI combination. The particular
information used to define an M3UA Routing Key is application and information used to define an M3UA Routing Key is application and
network dependent, and none of the above examples are mandated. network dependent, and none of 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 traffic related to more than one Application Server, over a single
SCTP Association. In ASP Active and ASP Inactive management SCTP Association. In ASP Active and ASP Inactive management
messages, the signalling traffic to be started or stopped is messages, the signalling traffic to be started or stopped is
discriminated by the Routing Context parameter. At an ASP, the discriminated by the Routing Context parameter. At an ASP, the
Routing Context parameter uniquely identifies the range of signalling Routing Context parameter uniquely identifies the range of signalling
traffic associated with each Application Server that the ASP is traffic associated with each Application Server that the ASP is
configured to receive. 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. An example of a partial match would be a default routing result. An example of a partial match would be a default
Routing Key which would be the result if there are no other Routing Routing Key that would be the result if there are no other Routing
Keys to which the message belongs. It is not necessary for the Keys to which the message belongs. It is not necessary for the
parameter range values within a particular Routing Key to be parameter range values within a particular Routing Key to be
contiguous. contiguous.
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 There are two ways to provision a Routing Key at an SGP. A Routing
Key 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 message distribution function within the SGP is not limited to the
set of parameters defined in this document. Other implementation set of parameters defined in this document. Other implementation-
dependent 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 appropriate IP destination, the SGP must perform a message
distribution function using information from the received MTP3-User distribution function using information from the received MTP3-User
message. 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, maintain the equivalent of a network address translation table,
mapping incoming SS7 message information to an Application Server for mapping incoming SS7 message information to an Application Server for
a particular application and range of traffic. This could be a particular application and range of traffic. This could be
accomplished 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 These Routing Keys could in turn map directly to an Application
Server that is enabled by one or more ASPs. These ASPs provide Server that is enabled by one or more ASPs. These ASPs provide
dynamic status information regarding their availability, traffic dynamic status information regarding their availability, traffic-
handling capability and congestion to the SGP using various handling capability and congestion to the SGP using various
management messages defined in the M3UA protocol. management messages defined in the M3UA protocol.
The list of ASPs in an AS is assumed to be dynamic, taking into The list of ASPs in an AS is assumed to be dynamic, taking into
account the availability, traffic handling capability and congestion account the availability, traffic-handling capability, and congestion
status of the individual ASPs in the list, as well as configuration status of the individual ASPs in the list, as well as configuration
changes and 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 message, a default treatment MAY be specified. Possible solutions
are to provide a default Application Server at the SGP that directs 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 all unallocated traffic to a (set of) default ASPs, or to drop the
message and provide a notification to layer management. The message and provide a notification to layer management. The
treatment 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 possibly other elements of the outgoing message, such as the SLS
value). The ASP must also take into account whether the related value). The ASP must also take into account whether the related
Routing Context 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 Implementation Note: Where more than one route (or SGP) is possible
for routing to the SS7 network, the ASP could, for example, maintain for routing to the SS7 network, the ASP could, for example, maintain
a dynamic table of available SGP routes for the SS7 destinations, a dynamic table of available SGP routes for the SS7 destinations,
taking into account the SS7 destination taking into account the SS7 destination
availability/restricted/congestion status received from the SGP(s), availability/restricted/congestion status received from the SGP(s),
the availability status of the individual SGPs and configuration the availability status of the individual SGPs, and configuration
changes and failover mechanisms. There is, however, no M3UA messaging changes and failover mechanisms. There is, however, no M3UA
to manage the status of an SGP (e.g., SGP-Up/Down/Active/Inactive messaging to manage the status of an SGP (e.g., SGP-
messaging). 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 In the case of SS7 and M3UA interworking, the M3UA adaptation layer
is designed to provide an extension of the MTP3 defined user is designed to provide an extension of the MTP3-defined user
primitives. 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 The SG is responsible for terminating MTP Level 3 of the SS7
protocol, 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) over a transmits and receives SS7 Message Signalling Units (MSUs) over a
standard SS7 network interface, using the SS7 Message Transfer Part standard SS7 network interface, using the SS7 Message Transfer Part
(MTP) [7,8,9]. (MTP) [7,8,9].
As a standard SS7 network interface, the use of MTP Level 2 As a standard SS7 network interface, the use of MTP Level 2
signalling links is not the only possibility. ATM-based High Speed signalling links is not the only possibility. ATM-based High Speed
Links can also be used with the services of the Signalling ATM Links can also be used with the services of the Signalling ATM
Adaptation Layer (SAAL) [18,19]. Adaptation Layer (SAAL) [19,20].
Note: It is also possible for IP-based interfaces to be present, Note: It is also possible for IP-based interfaces to be present,
using the services of the MTP2-User Adaptation Layer (M2UA) [27] or using the services of the MTP2-User Adaptation Layer (M2UA) [24] or
M2PA [28]. M2PA [25].
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- be capable of communicating with remote SS7 SEPs in a quasi-
associated fashion, where STPs may be present in the SS7 path between associated fashion, where STPs may be present in the SS7 path between
the SEP and 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 between the SS7 network and the IP network by also supporting the
M3UA adaptation layer. It allows the transfer of MTP3-User M3UA adaptation layer. It allows the transfer of MTP3-User
signalling messages to and from an IP-based Application Server signalling messages to and from an IP-based Application Server
Process where the 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 unavailability, as would be expected in an SS7 SEP node. To
accomplish this, the MTP-PAUSE, MTP-RESUME and MTP-STATUS indication accomplish this, the MTP-PAUSE, MTP-RESUME, and MTP-STATUS indication
primitives received at the MTP3 upper layer interface at the SG need primitives received at the MTP3 upper layer interface at the SG need
to be propagated to the remote MTP3-User lower layer interface at the to be propagated to the remote MTP3-User lower layer interface at the
ASP. 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 network) MUST NOT be encapsulated as Data message Payload Data and
sent either from SG to ASP or from ASP to SG. The SG MUST terminate sent either from SG to ASP or from ASP to SG. The SG MUST terminate
these 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 layer must maintain the status of configured SS7 destinations and
route messages according to availability/congestion/restricted status route messages according to the availability/congestion/restricted
of the routes to these SS7 destinations. status 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 of routing of messages beyond the remote end. Therefore, SS7 and
M3UA 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) that 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,
unavailable. Active ASPs handle traffic; inactive ASPs might be used or unavailable. Active ASPs handle traffic; inactive ASPs might be
when active ASPs become unavailable. used 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. and "k" ASPs are available to take over for a failed or unavailable
Traffic SHOULD be sent after "n" ASPs are active. "k" ASPs MAY be ASP. Traffic SHOULD be sent after "n" ASPs are active. "k" ASPs MAY
either active at the same time as "n" or kept inactive until needed be either active at the same time as "n" or kept inactive until
due to a failed or unavailable ASP. needed due to a failed or unavailable ASP.
A "1+1" active/backup redundancy is a subset of this model. A A "1+1" active/backup redundancy is a subset of this model. A
simplex "1+0" model is also supported as a subset, with no ASP simplex "1+0" model is also supported as a subset, with no ASP
redundancy. 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 perform testing and maintenance activity. The function could
optionally be used to control the start of traffic on to a newly optionally be used to control the start of traffic on to a newly
available SCTP 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 The M3UA layer is informed of local and IP network congestion by
means of an implementation-dependent function (e.g., an means of an implementation-dependent function (e.g., an
implementation dependent indication from the SCTP of IP network implementation-dependent indication from the SCTP of IP network
congestion). congestion).
At an ASP or IPSP, the M3UA layer indicates IP network congestion to At an ASP or IPSP, the M3UA layer indicates IP network congestion to
local MTP3-Users by means of an MTP-STATUS primitive, as per current local MTP3-Users by means of an MTP-STATUS primitive, as per current
MTP3 procedures, to invoke appropriate upper layer responses. MTP3 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 Signalling Point Management Cluster (SPMC) is encountering IP network
IP network congestion, the SG MAY trigger SS7 MTP3 Transfer Controlled congestion, the SG MAY trigger SS7 MTP3 Transfer Controlled
management messages to originating SS7 nodes, per the congestion management messages to originating SS7 nodes, per the congestion
procedures of the relevant MTP3 standard. The triggering of SS7 MTP3 procedures of the relevant MTP3 standard. The triggering of SS7 MTP3
Management messages from an SG is an implementation-dependent Management messages from an SG is an implementation-dependent
function. 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 The M3UA layer at both the SGP and ASP also supports the assignment
of signalling traffic into streams within an SCTP association. of signalling traffic into streams within an SCTP association.
Traffic that requires sequencing SHOULD be assigned to the same Traffic that requires sequencing SHOULD be assigned to the same
stream. To accomplish this, MTP3-User traffic may be assigned to stream. To accomplish this, MTP3-User traffic may be assigned to
individual streams based on, for example, the SLS value in the MTP3 individual streams based on, for example, the SLS value in the MTP3
Routing Label, subject of course to the maximum number of streams Routing Label, subject of course to the maximum number of streams
supported by the underlying SCTP association. supported by the underlying SCTP association.
The following rules apply (see section 3.1.2): The following rules apply (see Section 3.1.2):
1. DATA message MUST NOT be sent on stream 0. 1. The DATA message MUST NOT be sent on stream 0.
2. ASPSM, MGMT, RKM classes SHOULD be sent on stream 0 (Other than 2. The ASPSM, MGMT, RKM classes SHOULD be sent on stream 0 (other
BEAT, BEAT ACK and NTFY messages) than BEAT, BEAT ACK and NTFY messages).
3. SSNM, ASPTM classes and BEAT, BEAT ACK and NTFY messages can be 3. The SSNM, ASPTM classes and BEAT, BEAT ACK and NTFY messages can
sent on any stream. be sent on any stream.
1.4.8 SCTP Client/Server Model 1.4.8. SCTP 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 configured so that one always takes on the role of client and the
other the role of server for initiating SCTP associations. The other the role of server for initiating SCTP associations. The
default orientation would be for the SGP to take on the role of 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 server while the ASP is the client. In this case, ASPs SHOULD
initiate the SCTP association to the SGP. initiate the SCTP association to the SGP.
In the case of IPSP to IPSP communication, the peer endpoints using In the case of IPSP to IPSP communication, the peer endpoints using
M3UA SHOULD be configured so that one always takes on the role of M3UA SHOULD be configured so that one always takes on the role of
client and the other the role of server for initiating SCTP client and the other the role of server for initiating SCTP
associations. associations.
The SCTP and TCP Registered User Port Number Assignment for M3UA is The SCTP and TCP Registered User Port Number Assignment for M3UA is
2905. 2905.
1.5 Sample Configuration 1.5. Sample Configuration
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 |
+------| +------+-+------+ +------+ +------| +------+-+------+ +------+
skipping to change at page 18, line 49 skipping to change at page 21, line 8
either the MGC or SEP. It also provides network status information either the MGC or SEP. It also provides network status information
to one or 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 M3UA-resident message distribution function for ongoing routing to
the final IP destination. Messages received from the local M3UA the final IP destination. Messages received from the local M3UA
network address translation and mapping function as MTP-TRANSFER network address translation and mapping function as MTP-TRANSFER
indication primitives are sent to the MTP Level 3 upper layer indication primitives are sent to the MTP Level 3 upper-layer
interface as MTP-TRANSFER request primitives for ongoing MTP Level 3 interface as MTP-TRANSFER request primitives for ongoing MTP Level 3
routing to an SS7 SEP. For the purposes of providing SS7 network routing to an SS7 SEP. For the purposes of providing SS7 network
status information the NIF also delivers MTP-PAUSE, MTP-RESUME and status information, the NIF also delivers MTP-PAUSE, MTP-RESUME, and
MTP-STATUS indication primitives received from the MTP Level 3 upper MTP-STATUS indication primitives received from the MTP Level 3
layer interface to the local M3UA-resident management function. In upper-layer interface to the local M3UA-resident management function.
addition, as an implementation and network option, restricted In addition, as an implementation and network option, restricted
destinations are communicated from MTP network management to the destinations are communicated from MTP network management to the
local M3UA-resident 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 ******** ******** IP ********
* IPSP * * IPSP * * IPSP * * IPSP *
******** ******** ******** ********
+------+ +------+ +------+ +------+
|SCCP- | |SCCP- | |SCCP- | |SCCP- |
| User | | User | | User | | User |
+------+ +------+ +------+ +------+
| SCCP | | SCCP | | SCCP | | SCCP |
skipping to change at page 19, line 32 skipping to change at page 21, line 41
+------+ +------+ +------+ +------+
| SCTP | | SCTP | | SCTP | | SCTP |
+------+ +------+ +------+ +------+
| IP | | IP | | IP | | IP |
+------+ +------+ +------+ +------+
|________________| |________________|
This example shows an architecture where no Signalling Gateway is This example shows an architecture where no Signalling Gateway is
used. In this example, SCCP messages are exchanged directly between used. In this example, SCCP messages are exchanged directly between
two IP-resident IPSPs with resident SCCP-User protocol instances, two IP-resident IPSPs with resident SCCP-User protocol instances,
such as RANAP or TCAP. SS7 network interworking is not required, such as RANAP or TCAP. SS7 network interworking is not required;
therefore there is no MTP3 network management status information for therefore, there is no MTP3 network management status information for
the SCCP and SCCP-User protocols to consider. Any MTP-PAUSE, MTP- the SCCP and SCCP-User protocols to consider. Any MTP-PAUSE, MTP-
RESUME or MTP-STATUS indications from the M3UA layer to the SCCP RESUME, or MTP-STATUS indications from the M3UA layer to the SCCP
layer should consider the status of the SCTP Association and layer should consider the status of the SCTP Association and
underlying IP network and any congestion information received from underlying IP network and any congestion information received from
the remote site. 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 |
skipping to change at page 20, line 27 skipping to change at page 22, line 43
or DPC/SSN address of an SCCP peer located in the IP domain, the or DPC/SSN address of an SCCP peer located in the IP domain, the
resulting MTP-TRANSFER request primitive is sent to the local M3UA- resulting MTP-TRANSFER request primitive is sent to the local M3UA-
resident network address translation and mapping function for ongoing resident network address translation and mapping function for ongoing
routing to the final IP destination. routing to the final IP destination.
Similarly, the SCCP instance in an SGP can perform the SCCP GTT Similarly, the SCCP instance in an SGP can perform the SCCP GTT
service for messages logically addressed to it from SCCP peers in the service for messages logically addressed to it from SCCP peers in the
IP domain. In this case, MTP-TRANSFER indication primitives are sent IP domain. In this case, MTP-TRANSFER indication primitives are sent
from 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 TRANSFER request primitive is given to the MTP3 for delivery to an
SS7-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- address of an SCCP peer in the IP domain, and that the resulting
TRANSFER request primitive would be sent back to the M3UA layer for MTP-TRANSFER request primitive would be sent back to the M3UA layer
delivery to an IP destination. for 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/SI address information. This nodal based on the SS7 DPC or DPC/SI 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 Note that the services and interface provided by the M3UA layer are
the same as in Example 1 and the functions taking place in the SCCP the same as in Example 1 and that the functions taking place in the
entity are transparent to the M3UA layer. The SCCP protocol SCCP entity are transparent to the M3UA layer. The SCCP protocol
functions are not 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
This section provides a definition of the boundaries of the M3UA This section provides a definition of the boundaries of the M3UA
protoccol. They consist of SCTP, Layer Management and the MTP3-User. protocol. They consist of SCTP, Layer Management, and the MTP3-User.
+-----------+ +-----------+
| MTP3-User | | MTP3-User |
+-----------+ +-----------+
| |
| |
+-----------+ +------------+ +-----------+ +------------+
| M3UA |-----| Layer Mgmt | | M3UA |-----| Layer Mgmt |
+-----------+ +------------+ +-----------+ +------------+
| |
| |
+-----------+ +-----------+
| SCTP | | SCTP |
+-----------+ +-----------+
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 [18], 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 that ASP establish an SCTP association with its
peer. peer.
M-SCTP_ESTABLISH confirm M-SCTP_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 that ASP 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 that 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 that M3UA 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 that M3UA 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 the 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 that M3UA 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 that ASP 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 it 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 that it has successfully processed an incoming
Up message from its peer. ASP 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 that ASP 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 it 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 that it has successfully processed an incoming
Down message from its peer, or the SCTP association has ASP 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 that ASP 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 it 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 that it has successfully processed an incoming
Active message from its peer. ASP 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 that ASP 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 it 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 that it has successfully processed an incoming
Inactive message from its peer. ASP 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 If dynamic registration of RK is supported by the M3UA layer, the
layer 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 that ASP register RK(s) with its peer by sending
REG REQ message an 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 a
registration status as successful from its peer. registration status of 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 that ASP deregister RK(s) with its peer by
sending DEREG REQ message. sending a 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 a
deregistration status as successful from its peer. deregistration status of 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, In this document, the keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL
SHOULD NOT, RECOMMENDED, NOT RECOMMENDED, MAY, and OPTIONAL, when NOT, SHOULD, SHOULD NOT, RECOMMENDED, NOT RECOMMENDED, MAY, and
they appear in this document, are to be interpreted as described in OPTIONAL are to be interpreted as described in [21].
[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 The protocol messages for MTP3-User Adaptation require a message
header which contains the adaptation layer version, the message type, header that contains the adaptation layer version, the message type,
and 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 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 as follows:
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) Messages 0 Management (MGMT) Messages
1 Transfer Messages 1 Transfer Messages
2 SS7 Signalling Network Management (SSNM) Messages 2 SS7 Signalling Network Management (SSNM) Messages
skipping to change at page 26, line 4 skipping to change at page 29, line 10
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 The following list contains the message types for the defined
messages. messages.
Management (MGMT) Messages (See Section 3.8) Management (MGMT) Messages (see Section 3.8)
0 Error (ERR) 0 Error (ERR)
1 Notify (NTFY) 1 Notify (NTFY)
2 to 127 Reserved by the IETF 2 to 127 Reserved by the IETF
128 to 255 Reserved for IETF-Defined MGMT extensions 128 to 255 Reserved for IETF-Defined MGMT extensions
Transfer Messages (See Section 3.3) Transfer Messages (see Section 3.3)
0 Reserved 0 Reserved
1 Payload Data (DATA) 1 Payload Data (DATA)
2 to 127 Reserved by the IETF 2 to 127 Reserved by the IETF
128 to 255 Reserved for IETF-Defined Transfer extensions 128 to 255 Reserved for IETF-Defined Transfer extensions
SS7 Signalling Network Management (SSNM) Messages (See Section SS7 Signalling Network Management (SSNM) Messages (see Section
3.4) 3.4)
0 Reserved 0 Reserved
1 Destination Unavailable (DUNA) 1 Destination Unavailable (DUNA)
2 Destination Available (DAVA) 2 Destination Available (DAVA)
3 Destination State Audit (DAUD) 3 Destination State Audit (DAUD)
4 Signalling Congestion (SCON) 4 Signalling Congestion (SCON)
5 Destination User Part Unavailable (DUPU) 5 Destination User Part Unavailable (DUPU)
6 Destination Restricted (DRST) 6 Destination Restricted (DRST)
7 to 127 Reserved by the IETF 7 to 127 Reserved by the IETF
128 to 255 Reserved for IETF-Defined SSNM extensions 128 to 255 Reserved for IETF-Defined SSNM extensions
ASP State Maintenance (ASPSM) Messages (See Section 3.5) ASP State Maintenance (ASPSM) Messages (see Section 3.5)
0 Reserved 0 Reserved
1 ASP Up (ASPUP) 1 ASP Up (ASPUP)
2 ASP Down (ASPDN) 2 ASP Down (ASPDN)
3 Heartbeat (BEAT) 3 Heartbeat (BEAT)
4 ASP Up Acknowledgement (ASPUP ACK) 4 ASP Up Acknowledgement (ASPUP ACK)
5 ASP Down Acknowledgement (ASPDN ACK) 5 ASP Down Acknowledgement (ASPDN ACK)
6 Heartbeat Acknowledgement (BEAT ACK) 6 Heartbeat Acknowledgement (BEAT ACK)
7 to 127 Reserved by the IETF 7 to 127 Reserved by the IETF
128 to 255 Reserved for IETF-Defined ASPSM extensions 128 to 255 Reserved for IETF-Defined ASPSM extensions
ASP Traffic Maintenance (ASPTM) Messages (See Section 3.7) 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.6) 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. The Message Length MUST include including the Common Header. The Message Length MUST include
parameter padding octets, if any. parameter padding octets, if there are any.
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 /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 28, line 9 skipping to change at page 31, line 26
parameters may be in any order, except where explicitly mandated. A parameters may be in any order, except where explicitly mandated. A
receiver SHOULD accept the parameters in any order. receiver SHOULD accept the parameters in any order.
Unless explicitly stated or shown in a message format diagram, only Unless explicitly stated or shown in a message format diagram, only
one parameter of the same type is allowed in a message. one parameter of the same type is allowed in a message.
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 layers are in the range of 0x00 to 0x3f. M3UA-specific parameters
parameters have Tags in the range 0x0200 to 0x02ff. The parameter have Tags in the range 0x0200 to 0x02ff. The parameter Tags
Tags defined are as follows: 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
skipping to change at page 28, line 39 skipping to change at page 32, line 7
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 M3UA-Specific parameters. These TLV parameters are specific to the
the M3UA protocol: M3UA protocol:
Network Appearance 0x0200 Network Appearance 0x0200
Reserved 0x0201 Reserved 0x0201
Reserved 0x0202 Reserved 0x0202
Reserved 0x0203 Reserved 0x0203
User/Cause 0x0204 User/Cause 0x0204
Congestion Indications 0x0205 Congestion Indications 0x0205
Concerned Destination 0x0206 Concerned Destination 0x0206
Routing Key 0x0207 Routing Key 0x0207
Registration Result 0x0208 Registration Result 0x0208
skipping to change at page 29, line 10 skipping to change at page 32, line 30
Local Routing Key Identifier 0x020a Local Routing Key Identifier 0x020a
Destination Point Code 0x020b Destination Point Code 0x020b
Service Indicators 0x020c Service Indicators 0x020c
Reserved 0x020d Reserved 0x020d
Originating Point Code List 0x020e Originating Point Code List 0x020e
Reserved 0x020f Reserved 0x020f
Protocol Data 0x0210 Protocol Data 0x0210
Reserved 0x0211 Reserved 0x0211
Registration Status 0x0212 Registration Status 0x0212
Deregistration Status 0x0213 Deregistration Status 0x0213
Reserved by the IETF 0x0214 to 0xffff Reserved by the IETF 0x0214 to 0xffff
The value of 65535 is reserved for IETF-defined extensions. The value of 65535 is reserved for IETF-defined extensions.
Values other than those defined in specific parameter description Values other than those defined in specific parameter descriptions
are reserved for use by the IETF. A RFC is required to make use are reserved for use by the IETF. An RFC is required to make use
of parameter values "Reserved by the IETF". of parameter values "Reserved by the IETF".
Parameter Length: 16 bits (unsigned integer) Parameter Length: 16 bits (unsigned integer)
The Parameter Length field contains the size of the parameter The Parameter Length field contains the size of the parameter in
in octets, including the Parameter Tag, Parameter Length, and octets, including the Parameter Tag, Parameter Length, and
Parameter Value fields. Thus, a parameter with a zero-length Parameter Value fields. Thus, a parameter with a zero-length
Parameter Value field would have a Length field of 4. The Parameter Value field would have a Length field of 4. The
Parameter Length does not include any padding octets. If the Parameter Length does not include any padding octets. If the
parameter contains subparameters, the Parameter Length field parameter contains subparameters, the Parameter Length field will
will include all the octets of each subparameter including include all the octets of each subparameter, including
subparameter padding octets (if any). subparameter padding octets (if there are any).
Parameter Value: variable length. Parameter Value: variable length
The Parameter Value field contains the actual information to be The Parameter Value field contains the actual information to be
transferred in the parameter. transferred in the parameter.
The total length of a parameter (including Tag, Parameter Length The total length of a parameter (including Tag, Parameter Length,
and Value fields) MUST be a multiple of 4 octets. If the length of and Value fields) MUST be a multiple of 4 octets. If the length
the parameter is not a multiple of 4 octets, the sender pads the of the parameter is not a multiple of 4 octets, the sender pads
Parameter at the end (i.e., after the Parameter Value field) with the Parameter at the end (i.e., after the Parameter Value field)
all zero octets. The length of the padding is NOT included in the with all zero octets. The length of the padding is NOT included
parameter length field. A sender MUST NOT pad with more than 3 in the parameter length field. A sender MUST NOT pad with more
octets. The receiver MUST ignore the padding octets. than 3 octets. The receiver MUST ignore the padding octets.
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 The DATA message contains the SS7 MTP3-User protocol data, which is
an MTP-TRANSFER primitive, including the complete MTP3 Routing Label. an MTP-TRANSFER primitive, including the complete MTP3 Routing Label.
The 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 Conditional Routing Context Conditional
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
skipping to change at page 30, line 29 skipping to change at page 34, line 4
| 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 Point context for the message and implicitly identifies the SS7 Point
Code format used, the SS7 Network Indicator value, and the MTP3 Code format used, the SS7 Network Indicator value, and the 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 a 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 if individual SCTP
are dedicated to each SS7 network context, the Network Appearance associations are dedicated to each SS7 network context, the
parameter is not required. In other cases the parameter may be Network Appearance parameter is not required. In other cases, the
configured to be present for the use of the receiver. parameter may be 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 where an ASP is connected to more than one SGP, the same SS7
network context may be identified by different Network Appearance network context may be identified by different Network Appearance
values depending over which SGP a message is being transmitted/ values, depending on which SGP a message is being transmitted/
received. received.
Where the optional Network Appearance parameter is present, it Where the optional Network Appearance parameter is present, it
MUST be the first parameter in the message as it defines the MUST be the first parameter in the message, as it defines the
format of 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 value The Routing Context parameter contains the Routing Context value
associated with the DATA message. Where a Routing Key has not associated with the DATA message. Where a Routing Key has 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 MUST be sent to identify the traffic flow, assisting in the
internal 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 message, including the Service Information Octet and Routing
Label. 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, which 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 32, line 17 skipping to change at page 36, line 5
and DPC from the routing label of the original SS7 message in Network and DPC from the routing label of the original SS7 message in Network
Byte Order, justified to the least significant bit. Unused bits are Byte Order, justified to the least significant bit. Unused 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 are SS7 message justified to the least significant bit. Unused bits 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 [26] message
priority bits. The MP bits are aligned to the least significant bit. priority bits. The MP bits are aligned to the least significant 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 The Signalling Link Selection field contains the SLS bits from the
routing label of the original SS7 message justified to the least routing label of the original SS7 message justified to the least
significant bit and in Network Byte Order. Unused bits are coded significant bit and in Network Byte Order. Unused bits are coded
`0'. `0'.
User Protocol Data: (variable length octet string) User Protocol Data: variable-length octet string
The User Protocol Data field contains a octet string of MTP-User The User Protocol Data field contains an octet string of MTP-User
information from the original SS7 message starting with the information from the original SS7 message, starting with the first
first octet of the original SS7 message following the Routing octet of the original SS7 message following the Routing Label
Label [7][8][29]. [7][8][26].
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 to indicate that the SG has determined that one or more SS7
destinations are unreachable. It is also sent by an SGP in response destinations are unreachable. It is also sent by an SGP in response
to a message from the ASP to an unreachable SS7 destination. As an to a message from the ASP to an unreachable SS7 destination. As an
implementation option the SG may suppress the sending of subsequent implementation option, the SG may suppress the sending of subsequent
"response" DUNA messages regarding a certain unreachable SS7 "response" DUNA messages regarding a certain unreachable SS7
destination for a certain period to give the remote side time to destination for a certain period to give the remote side time to
react. If there is no alternate route via another SG, the MTP3-User react. If there is no alternate route via another SG, the MTP3-User
at the ASP is expected to stop traffic to the affected destination at the ASP is expected to stop traffic to the affected destination
via the SG as per the defined MTP3-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 Conditional Routing Context Conditional
skipping to change at page 34, line 4 skipping to change at page 37, line 45
| 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
The description of Network Appearance in Section 3.3.1 applies
with the exception that Network Appearance does not have to be
the first parameter in this message.
Routing Context: n x 32-bits (unsigned integer) The description of Network Appearance in Section 3.3.1 applies,
with the exception that Network Appearance does not have to be the
first parameter in this message.
Routing Context: n x 32 bits (unsigned integer)
The conditional Routing Context parameter contains the Routing The conditional Routing Context parameter contains the Routing
Context values associated with the DUNA message. Where a Routing Context values associated with the DUNA message. Where a Routing
Key has not been coordinated between the SGP and ASP, sending of Key has not 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 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 Destination Point Code fields, each a three-octet parameter to
allow for 14-, 16- and 24-bit binary formatted SS7 Point Codes. allow for 14-, 16-, and 24-bit binary formatted SS7 Point Codes.
Affected Point Codes that are less than 24-bits, are padded on the Affected Point Codes that are less than 24 bits are padded on the
left to the 24-bit boundary. The encoding is shown below for ANSI left to the 24-bit boundary. The encoding is shown below for ANSI
and ITU 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.
multiple Affected PCs may be useful when reception of an MTP3 Including multiple Affected PCs may be useful when receipt of an
management message or a linkset event simultaneously affects the MTP3 management message or a linkset event simultaneously affects
availability status of a list of destinations at an SG. the 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 Affected Destination Point Codes. Identifying a contiguous range
of Affected DPCs may be useful when reception of an MTP3 of Affected DPCs may be useful when receipt of an MTP3 management
management message or a linkset event simultaneously affects the message or a linkset event simultaneously affects the availability
availability status of a series of destinations at an SG. status of a series of destinations at an SG.
The Mask parameter is an integer representing a bit mask that can The Mask parameter is an integer representing a bit mask that can
be applied to the related Affected PC field. The bit mask be applied to the related Affected PC field. The bit mask
identifies how many bits of the Affected PC field are significant identifies how many bits of the Affected PC field are significant
and which are effectively "wildcarded". For example, a mask of and which are effectively "wildcarded". For example, a mask of
"8" indicates that the last eight bits of the PC is "wildcarded". "8" indicates that the last eight bits of the PC are "wildcarded".
For an ANSI 24-bit Affected PC, this is equivalent to signalling For an ANSI 24-bit Affected PC, this is equivalent to signalling
that all PCs in an ANSI Cluster are unavailable. A mask of "3" that all PCs in an ANSI Cluster are unavailable. A mask of "3"
indicates that the last three bits of the PC is "wildcarded". For indicates that the last three bits of the PC are "wildcarded".
a 14-bit ITU Affected PC, this is equivalent to signaling that an For a 14-bit ITU Affected PC, this is equivalent to signaling that
ITU Region is unavailable. A mask value equal (or greater than) an ITU Region is unavailable. A mask value equal (or greater
the number of bits in the PC indicates that the entire network than) the number of bits in the PC indicates that the entire
appearance is affected - this is used to indicate network network appearance is affected; this is used to indicate network
isolation 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 presently identified for its use, but the INFO String MAY be used
for debugging purposes. An INFO String with a zero length for debugging purposes. An INFO String with a zero-length
parameter is not considered as an error (A zero length parameter is parameter is not considered an error (a zero length parameter is
one in which the Length field in the TLV will be set to 4). one in which the Length field in the TLV will be set to 4).
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 The DAVA message is sent from an SGP to all concerned ASPs to
indicate that the SG has determined that one or more SS7 destinations indicate that the SG has determined that one or more SS7 destinations
are now reachable (and not restricted), or in response to a DAUD are now reachable (and not restricted), or in response to a DAUD
message if appropriate. If the ASP M3UA layer previously had no message, if appropriate. If the ASP M3UA layer previously had no
routes to the affected destinations the ASP MTP3-User protocol is routes to the affected destinations, the ASP MTP3-User protocol is
informed and may now resume traffic to the affected destination. The informed and may now resume traffic to the affected destination. The
ASP M3UA layer now routes the MTP3-user traffic through the SG ASP M3UA layer now routes the MTP3-user traffic through the SG
initiating the DAVA 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 Conditional Routing Context Conditional
Affected Point Code Mandatory Affected Point Code Mandatory
INFO String Optional INFO String Optional
skipping to change at page 36, line 4 skipping to change at page 40, line 11
informed and may now resume traffic to the affected destination. The informed and may now resume traffic to the affected destination. The
ASP M3UA layer now routes the MTP3-user traffic through the SG ASP M3UA layer now routes the MTP3-user traffic through the SG
initiating the DAVA 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 Conditional Routing Context Conditional
Affected Point Code Mandatory Affected Point Code Mandatory
INFO String Optional INFO String Optional
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 are the same
as for the 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 or availability/congestion state of SS7 routes from the SG to one 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 Conditional Routing Context Conditional
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 are the same as
for the DUNA message (See Section 3.4.1). for the DUNA message (See Section 3.4.1).
It is recommended that during normal operation (traffic handling) the It is recommended that during normal operation (traffic handling) the
mask field of the Affected Point Code parameter in the DAUD message is mask field of the Affected Point Code parameter in the DAUD message
kept to a zero value in order to avoid SG overloading. be kept to a zero value in order to avoid SG overloading.
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 a DATA or DAUD message, as appropriate. For some MTP protocol
variants (e.g., ANSI MTP) the SCON message may be sent when the SS7 variants (e.g., ANSI MTP) the SCON message may be sent when the SS7
congestion level changes. The SCON message MAY also be sent from the congestion level changes. The SCON message MAY also be sent from the
M3UA layer of an ASP to an M3UA peer indicating that the congestion M3UA layer of an ASP to an M3UA peer, indicating that the congestion
level of the M3UA layer or the ASP has changed. level of the M3UA layer or the ASP has changed.
IMPLEMENTATION NOTE: An M3UA node may maintain a timer to control IMPLEMENTATION NOTE: An M3UA node may maintain a timer to control
congestion notification validity, if desired. This timer will be congestion notification validity, if desired. This timer will be
useful in those cases where the peer node fails to indicate useful in cases where the peer node fails to indicate congestion
congestion abatement. abatement.
The SCON message contains the following parameters: The SCON message contains the following parameters:
Network Appearance Optional Network Appearance Optional
Routing Context Conditional Routing Context Conditional
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
skipping to change at page 37, line 42 skipping to change at page 42, line 4
| Tag = 0x0205 | Length = 8 | | 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 are the
as for the DUNA message (See Section 3.4.1). same 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
of multiple destinations or ranges of destinations. congestion 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
code of the originator of the message that triggered the SCON point code of the originator of the message that triggered the
message. The Concerned Destination parameter contains one SCON message. The Concerned Destination parameter contains one
Concerned Destination Point Code field, a three-octet parameter to Concerned Destination Point Code field, a three-octet parameter to
allow for 14-, 16- and 24-bit binary formatted SS7 Point Codes. A allow for 14-, 16-, and 24-bit binary formatted SS7 Point Codes.
Concerned Point Code that is less than 24-bits is padded on the A Concerned Point Code that is less than 24 bits is padded on the
left to the 24-bit boundary. Any resulting Transfer Controlled left to the 24-bit boundary. Any resulting Transfer Controlled
(TFC) message from the SG is sent to the Concerned Point Code (TFC) message from the SG is sent to the Concerned Point Code
using the single Affected DPC contained in the SCON message to using the single Affected DPC contained in the SCON message to
populate the (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 The optional Congestion Indications parameter contains a
Congestion Level field. This optional parameter is used to Congestion Level field. This optional parameter is used to
communicate congestion levels in national MTP networks with communicate congestion levels in national MTP networks with
multiple congestion thresholds, such as in ANSI MTP3. For MTP multiple congestion thresholds, such as in ANSI MTP3. For MTP
congestion methods without multiple congestion levels (e.g., the congestion methods without multiple congestion levels (e.g., the
ITU international 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 Conditional Routing Context Conditional
Affected Point Code Mandatory Affected Point Code Mandatory
skipping to change at page 39, line 28 skipping to change at page 44, line 4
| 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, etc.). Some of the valid values
the MTP3-User Identity are shown below. The values align with for the MTP3-User Identity are shown below. The values align with
those provided in the SS7 MTP3 User Part Unavailable message and those provided in the SS7 MTP3 User Part Unavailable message and
Service Indicator. Depending on the MTP3 protocol variant/version Service Indicator. Depending on the MTP3 protocol variant/version
used in the Network Appearance, additional values may be used. used in the Network Appearance, additional values may be used.
The relevant MTP3 protocol variant/version recommendation is The relevant MTP3 protocol variant/version recommendation is
definitive. 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
the same as for the DUNA message (See Section 3.4.1.) except that are the same as for the DUNA message (see Section 3.4.1.) except
the Mask field is not used and only a single Affected DPC is that the Mask field is not used and only a single Affected DPC is
included. Ranges and lists of Affected DPCs cannot be signaled 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 are 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 The DRST message is optionally sent from the SGP to all concerned
ASPs 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,
in response to a DAUD message if appropriate. The M3UA layer at the or in response to a DAUD message, if appropriate. The M3UA layer
ASP is expected to send traffic to the affected destination via an at the ASP is expected to send traffic to the affected destination
alternate SG with route(s) of equal priority, but only if such an via an alternate SG with a route of equal priority, but only if
alternate route exists and is available. If the affected destination such an alternate route exists and is available. If the affected
is currently considered unavailable by the ASP, The MTP3-User should destination is currently considered unavailable by the ASP, The
be informed that traffic to the affected destination can be resumed. MTP3-User should be informed that traffic to the affected
In this case, the M3UA layer should route the traffic through the SG destination can be resumed. In this case, the M3UA layer should
initiating the DRST message. route the traffic through the SG initiating the DRST message.
This message is optional for the SG to send and it is optional for This message is optional for the SG to send, and it is optional
the ASP to act on any information received in the message. It is for for the ASP to act on any information received in the message. It
use in the "STP" case described in Section 1.4.1. is for 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 Conditional Routing Context Conditional
Affected Point Code Mandatory Affected Point Code Mandatory
INFO String Optional INFO String Optional
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 are the
as for the DUNA message (See Section 3.4.1). same 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
adaptation layer is ready to receive any ASPSM/ASPTM messages for all the adaptation layer is ready to receive any ASPSM/ASPTM messages
Routing Keys that the ASP is configured to serve. for all 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
skipping to change at page 41, line 51 skipping to change at page 46, line 34
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
ASP Identifier: 32-bit unsigned integer ASP Identifier: 32-bit unsigned integer
The optional ASP Identifier parameter contains a unique value that The optional ASP Identifier parameter contains a unique value that
is locally significant among the ASPs that support an AS. The SGP is locally significant among the ASPs that support an AS. The SGP
should save the ASP Identifier to be used, if necessary, with the should save the ASP Identifier to be used, if necessary, with the
Notify message (see Section 3.8.2). Notify message (see Section 3.8.2).
The format and description of the optional INFO String parameter The format and description of the optional INFO String parameter
is the same as for the DUNA message (See Section 3.4.1). are 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:
ASP Identifier Optional ASP Identifier Optional
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 = 0x0011 | Length = 8 | | Tag = 0x0011 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ASP Identifier | | ASP Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag =0x0004 | Length | | Tag =0x0004 | Length |
skipping to change at page 42, line 28 skipping to change at page 47, line 21
| ASP Identifier | | ASP Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag =0x0004 | Length | | Tag =0x0004 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ INFO String / / INFO String /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The optional ASP Identifier parameter is specifically useful for IPSP The optional ASP Identifier parameter is specifically useful for IPSP
communication. In that case the IPSP answering the ASP Up message MAY communication. In that case, the IPSP answering the ASP Up message
include its own ASP Identifier value. MAY include its own ASP Identifier value.
The format and description of the optional INFO String parameter is The format and description of the optional INFO String parameter are
the same as for the DUNA message (See Section 3.4.1). The INFO the same as for the DUNA message (see Section 3.4.1). The INFO
String in an ASP Up Ack message is independent from the INFO String String in an ASP Up Ack message is independent from the INFO String
in the ASP Up message (i.e., it does not have to echo back the INFO in the ASP Up message (i.e., it does not have to echo back the INFO
String received). 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 ASP Down message is used to indicate to a remote M3UA peer that
the adaptation layer is NOT ready to receive DATA, SSNM, RKM or ASPTM the adaptation layer is NOT ready to receive DATA, SSNM, RKM, or
messages. ASPTM messages.
The ASP Down message contains the following parameters: The ASP Down message contains the following parameter:
INFO String Optional INFO String Optional
The format for the ASP Down message parameters is as follows: 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 are
the same as for the DUNA message (see Section 3.4.1).
The format and description of the optional INFO String parameter is 3.5.4. ASP Down Acknowledgement (ASP Down Ack)
the same as for the DUNA message (See Section 3.4.1).
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 parameter:
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 format and description of the optional INFO String parameter are
the 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 The INFO String in an ASP Down Ack message is independent from the
INFO String in the ASP Down message (i.e., it does not have to echo INFO String in the ASP Down message (i.e., it does not have to echo
back the 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 are The BEAT message is optionally used to ensure that the M3UA peers 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 M3UA runs over a transport layer other than the SCTP, which has its
own heartbeat. own heartbeat.
The BEAT message contains the following parameters: The BEAT message contains the following parameter:
Heartbeat Data Optional Heartbeat Data Optional
The format for the BEAT message is as follows: The format for the BEAT message is as follows:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0009 | Length | | Tag = 0x0009 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ Heartbeat Data / / Heartbeat Data /
\ \ \ \
skipping to change at page 44, line 15 skipping to change at page 49, line 19
| Tag = 0x0009 | Length | | Tag = 0x0009 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ Heartbeat Data / / Heartbeat Data /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Heartbeat Data parameter contents are defined by the sending The Heartbeat Data parameter contents are defined by the sending
node. The Heartbeat Data could include, for example, a Heartbeat node. The Heartbeat Data could include, for example, a Heartbeat
Sequence Number and/or Timestamp. The receiver of a BEAT message Sequence Number and/or Timestamp. The receiver of a BEAT message
does not process this field as it is only of significance to the does not process this field, as it is only of significance to the
sender. 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 message. The BEAT Ack message is sent in response to a received BEAT message.
It includes all the parameters of the received BEAT message, without It includes all the parameters of the received BEAT 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 The REG REQ message is sent by an ASP to indicate to a remote M3UA
peer that it wishes to register one or more given Routing Keys with peer that it wishes to register one or more given Routing Keys with
the remote peer. Typically, an ASP would send this message to an the remote peer. Typically, an ASP would send this message to an SGP
SGP, and expects to receive a REG RSP message in return with an and expect to receive a REG RSP message in return with an associated
associated Routing Context value. Routing Context value.
The REG REQ message contains the following parameters: The REG REQ message contains the following parameter:
Routing Key Mandatory Routing Key Mandatory
One or more Routing Key parameters MAY be included. The format for One or more Routing Key parameters MAY be included. The format for
the 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 /
skipping to change at page 45, line 12 skipping to change at page 50, line 29
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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
expects that the receiver of this message will create a Routing message expects that the receiver of this message will create a
Key entry and assign a unique Routing Context value to it, if the Routing Key entry and assign a unique Routing Context value to it,
Routing Key entry does not already exist. if the Routing Key entry does not already exist.
The Routing Key parameter may be present multiple times in the The Routing Key parameter may be present multiple times in the
same message. This is used to allow the registration of multiple same message. This is used to allow the registration of multiple
Routing 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Routing Context (optional) | | Routing Context (optional) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Traffic Mode Type (optional) | | Traffic Mode Type (optional) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 46, line 9 skipping to change at page 51, line 44
Note: The Destination Point Code, Service Indicators, and Note: The Destination Point Code, Service Indicators, and
Originating Point Code List parameters MAY be repeated as a Originating Point Code List parameters MAY be repeated as a
grouping within the Routing Key parameter, in the structure shown grouping within the Routing Key parameter, in the structure shown
above. above.
Local-RK-Identifier: 32-bit unsigned integer Local-RK-Identifier: 32-bit unsigned integer
The mandatory Local-RK-Identifier field is used to uniquely The mandatory Local-RK-Identifier field is used to uniquely
identify the registration request. The Identifier value is identify the registration request. The Identifier value is
assigned by the ASP, and is used to correlate the response in an assigned by the ASP and used to correlate the response in an REG
REG RSP message with the original registration request. The RSP message with the original registration request. The
Identifier value must remain unique until the REG RSP message is Identifier value must remain unique until the REG RSP message is
received. 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 46, line 45 skipping to change at page 52, line 36
| Traffic Mode Type | | Traffic Mode Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The valid values for Traffic Mode Type are shown in the following The valid values for Traffic Mode Type are shown in the 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 The Destination Point Code parameter is mandatory, and it
Identifies the Destination Point Code of incoming SS7 traffic identifies the Destination Point Code of incoming SS7 traffic
for which the ASP is registering. For an alias point code for which the ASP is registering. For an alias point code
configuration, the DPC parameter would be repeated for each configuration, the DPC parameter would be repeated for each
point code. The format is the same as described for the point code. 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 it has the same format as
the DATA message (See Section 3.3.1) with the exception that it in the DATA message (see Section 3.3.1) with the exception that it
does not have to be the first parameter in the message. If the does not have to be the first parameter in the message. If the
Network Appearance is not specified and the Routing Key applies to Network Appearance is not specified and the Routing Key applies to
all Network Appearances, then this Routing Key MUST be the only all Network Appearances, then this Routing Key MUST be the only
one registered for the association: that is, Routing Context is one registered for the association; that is, Routing Context is
implied and DATA and SSNM messages are discriminated on Network implied, and DATA and SSNM messages are discriminated on Network
Appearance rather than Routing Context. Where Network Appearance Appearance rather than on Routing Context. Where Network
is not specified and there is only one Network Appearance, then Appearance is not specified and there is only one Network
Network Appearance is implied. Its format is: Appearance, then Network Appearance is implied. 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 [7,8] field contains one or more Service The optional SI [7,8] field contains one or more Service
Indicators from the values as described in the MTP3-User Identity Indicators from the values described in the MTP3-User Identity
field of the DUPU message. The absence of the SI parameter in the field of the DUPU message. The absence of the SI parameter in the
Routing Key indicates the use of any SI value, excluding of course Routing Key indicates the use of any SI value, excluding of course
MTP management. Where an SI parameter does not contain a multiple MTP management. Where an SI parameter does not contain a multiple
of 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 for the Destination
Code parameter. The absence of the OPC List parameter in the Point Code parameter. The absence of the OPC List parameter in
Routing Key indicates the use of any OPC value, the 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 | Origination Point Code #1 | | Mask | Origination Point Code #1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mask | Origination Point Code #2 | | Mask | Origination Point Code #2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ ... / / ... /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mask | Origination Point Code #n | | Mask | Origination Point Code #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 The REG RSP message is used as a response to the REG REQ message from
a 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 successful registration requests, to be used in subsequent M3UA
Traffic Management protocol. Traffic Management protocol.
The REG RSP message contains the following parameters: The REG RSP message contains the following parameter:
Registration Result Mandatory Registration Result Mandatory
One or more Registration Result parameters MUST be included. The One or more Registration Result parameters MUST be included. The
format 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 |
skipping to change at page 49, line 7 skipping to change at page 55, line 21
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ ... / / ... /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 corresponding REG REQ message. Where multiple REG RSP messages
are used in reply to REG REQ message, a specific result SHOULD be are used in reply to REG REQ message, a specific result SHOULD be
in only one REG RSP message. The format of each result is as in only one REG RSP message. The format of each result is as
follows: follows:
skipping to change at page 50, line 16 skipping to change at page 56, line 32
10 Error - Unsupported/Invalid Traffic Handling Mode 10 Error - Unsupported/Invalid Traffic Handling Mode
11 Error - Routing Key Change Refused 11 Error - Routing Key Change Refused
12 Error - Routing Key Already Registered 12 Error - Routing Key Already Registered
Routing Context: 32-bit integer Routing Context: 32-bit integer
The Routing Context field contains the Routing Context value for The Routing Context field contains the Routing Context value for
the associated Routing Key if the registration was successful. It the associated Routing Key if the registration was successful. It
is set 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 /
\ \ \ \
skipping to change at page 50, line 46 skipping to change at page 57, line 23
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Routing Context: n X 32-bit integers Routing Context: n X 32-bit integers
The Routing Context parameter contains (a list of) integers The Routing Context parameter contains (a list of) integers
indexing the Application Server traffic that the sending ASP is indexing the Application Server traffic that the sending ASP is
currently registered to receive from the SGP but now wishes to currently registered to receive from the SGP but now wishes to
deregister. 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 parameter:
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 51, line 22 skipping to change at page 58, line 4
| 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 number of results in a single DEREG RSP message MAY be anywhere
from one to the total number of number of Routing Context values from one to the total number of number of Routing Context values
found in the corresponding DEREG REQ message. found in the corresponding DEREG REQ message.
Where multiple DEREG RSP messages are used in reply to DEREG REQ Where multiple DEREG RSP messages are used in reply to DEREG REQ
message, a specific result SHOULD be in only one DEREG RSP message, a specific result SHOULD be in only one DEREG RSP
message. The format of each result is as follows: message. The format of each result is as follows:
skipping to change at page 52, line 16 skipping to change at page 59, line 5
Its values may be: Its values may be:
0 Successfully Deregistered 0 Successfully Deregistered
1 Error - Unknown 1 Error - Unknown
2 Error - Invalid Routing Context 2 Error - Invalid Routing Context
3 Error - Permission Denied 3 Error - Permission Denied
4 Error - Not Registered 4 Error - Not Registered
5 Error - ASP Currently Active for Routing Context 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 Application Server. The ASP Active message affects only the ASP
state for the Routing Keys identified by the Routing Contexts, if state for the Routing Keys identified by the Routing Contexts, if
present. 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
skipping to change at page 53, line 4 skipping to change at page 59, line 44
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 operation of the ASP within an AS. The valid values for Traffic
Mode 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, in which the ASP takes over
traffic in an Application Server (i.e., primary/backup operation), all traffic in an Application Server (i.e., primary/backup
overriding any currently active ASPs in the AS. In Loadshare operation), overriding any currently active ASPs in the AS. In
mode, the ASP will share in the traffic distribution with any Loadshare mode, the ASP will share in the traffic distribution
other currently active ASPs. In Broadcast mode, the ASP will with any other currently active ASPs. In Broadcast mode, the ASP
receive the same messages as any other currently active ASP. will 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) The optional Routing Context parameter contains (a list of)
integers indexing the Application Server traffic that the sending integers indexing the Application Server traffic that the sending
ASP is 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 a one-to-one relationship between an index entry and an
Routing Key or AS Name. Because an AS can only appear in one SGP Routing Key or AS Name. Because an AS can only appear in one
Network Appearance, the Network Appearance parameter is not Network Appearance, the Network Appearance parameter is not
required 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 for more than one logical Application Server. From the
perspective of an ASP, a Routing Context defines a range of perspective of an ASP, a Routing Context defines a range of
signalling traffic that the ASP is currently configured to receive signalling traffic that the ASP is currently configured to receive
from the SGP. For example, an ASP could be configured to support from the SGP. For example, an ASP could be configured to support
signalling for multiple MTP3-Users, identified by separate SS7 signalling for multiple MTP3-Users, identified by separate SS7
DPC/OPC/SI ranges. DPC/OPC/SI ranges.
The format and description of the optional INFO String parameter is The format and description of the optional INFO String parameter are
the 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 The ASP Active Ack message is used to acknowledge an ASP Active
message 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:
skipping to change at page 55, line 26 skipping to change at page 61, line 26
/ 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 format and description of the optional INFO String parameter are
the 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.7.1). 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 The ASP Inactive message is sent by an ASP to indicate to a remote
M3UA peer that it is no longer an active ASP to be used from within a M3UA peer that it is no longer an active ASP to be used from within a
list of ASPs. The ASP Inactive message affects only the ASP state in list of ASPs. The ASP Inactive message affects only the ASP state in
the 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 /
\ \ \ \
skipping to change at page 56, line 17 skipping to change at page 62, line 23
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 are 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 /
\ \ \ \
skipping to change at page 56, line 48 skipping to change at page 63, line 22
/ 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 format and description of the optional INFO String parameter are
the 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 INFO String in an ASP Inactive Ack message is independent from
the INFO String in the ASP Inactive message (i.e., it does not have the INFO String in the ASP Inactive message (i.e., it does not have
to echo 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 The format of the Routing Context parameter is the same as for the
ASP Inactive message. (See Section 3.7.3). 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 The Error message is used to notify a peer of an error event
associated with an incoming message. For example, the message type associated with an incoming message. For example, the message type
might be unexpected given the current state, or a parameter value might be unexpected given the current state, or a parameter value
might be invalid. Error messages MUST NOT be generated in response to might be invalid. Error messages MUST NOT be generated in response
other Error messages. to other Error messages.
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 Conditional Diagnostic Information Conditional
(*) Only mandatory for specific Error Codes * Only mandatory for specific Error Codes.
The format for the Error message is as follows: The format for the Error 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 = 0x000c | Length = 8 | | Tag = 0x000c | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Error Code | | Error Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 58, line 12 skipping to change at page 64, line 41
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Network Appearance | | Network Appearance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0007 | Length | | Tag = 0x0007 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ Diagnostic Information / / Diagnostic Information /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Error Code: 32-bits (unsigned integer) Error Code: 32 bits (unsigned integer)
The Error Code parameter indicates the reason for the Error The Error Code parameter indicates the reason for the Error
Message. The Error parameter value can be one of the following Message. The Error parameter value can be one of the following
values: values:
0x01 Invalid Version 0x01 Invalid Version
0x02 Not Used in M3UA 0x02 Not Used in M3UA
0x03 Unsupported Message Class 0x03 Unsupported Message Class
0x04 Unsupported Message Type 0x04 Unsupported Message Type
0x05 Unsupported Traffic Mode Type 0x05 Unsupported Traffic Mode Type
skipping to change at page 58, line 24 skipping to change at page 65, line 4
The Error Code parameter indicates the reason for the Error The Error Code parameter indicates the reason for the Error
Message. The Error parameter value can be one of the following Message. The Error parameter value can be one of the following
values: values:
0x01 Invalid Version 0x01 Invalid Version
0x02 Not Used in M3UA 0x02 Not Used in M3UA
0x03 Unsupported Message Class 0x03 Unsupported Message Class
0x04 Unsupported Message Type 0x04 Unsupported Message Type
0x05 Unsupported Traffic Mode Type 0x05 Unsupported Traffic Mode Type
0x06 Unexpected Message 0x06 Unexpected Message
0x07 Protocol Error 0x07 Protocol Error
0x08 Not used in M3UA 0x08 Not Used in M3UA
0x09 Invalid Stream Identifier 0x09 Invalid Stream Identifier
0x0a Not used in M3UA 0x0a Not Used in M3UA
0x0b Not used in M3UA 0x0b Not Used in M3UA
0x0c Not used in M3UA 0x0c Not Used in M3UA
0x0d Refused - Management Blocking 0x0d Refused - Management Blocking
0x0e ASP Identifier Required 0x0e ASP Identifier Required
0x0f Invalid ASP Identifier 0x0f Invalid ASP Identifier
0x10 Not Used in M3UA 0x10 Not Used in M3UA
0x11 Invalid Parameter Value 0x11 Invalid Parameter Value
0x12 Parameter Field Error 0x12 Parameter Field Error
0x13 Unexpected Parameter 0x13 Unexpected Parameter
0x14 Destination Status Unknown 0x14 Destination Status Unknown
0x15 Invalid Network Appearance 0x15 Invalid Network Appearance
0x16 Missing Parameter 0x16 Missing Parameter
0x17 Not Used in M3UA 0x17 Not Used in M3UA
0x18 Not Used in M3UA 0x18 Not Used in M3UA
0x19 Invalid Routing Context 0x19 Invalid Routing Context
0x1a No Configured AS for ASP 0x1a No Configured AS for ASP
The "Invalid Version" error is sent if a message with an unsupported The "Invalid Version" error is sent if a message with an unsupported
version is received, the receiving end responds with an Error message, version is received. The receiving end responds with an Error
indicating the version the receiving node supports and notifies layer message, indicating the version the receiving node supports, and
management. notifies layer management.
The "Unsupported Message Class" error is sent if a message with an The "Unsupported Message Class" error is sent if a message with an
unexpected or unsupported Message Class is received. For this error, unexpected or unsupported Message Class is received. For this error,
the Diagnostic Information parameter MUST be included with the first the Diagnostic Information parameter MUST be included with the first
40 octets of the offending message. 40 octets of the offending message.
The "Unsupported Message Type" error is sent if a message with an The "Unsupported Message Type" error is sent if a message with an
unexpected or unsupported Message Type is received. For this error, unexpected or unsupported Message Type is received. For this error,
the Diagnostic Information parameter MUST be included with the first the Diagnostic Information parameter MUST be included with the first
40 octets of the offending message. 40 octets of the offending message.
The "Unsupported Traffic Mode Type" error is sent by a SGP if an ASP The "Unsupported Traffic Mode Type" error is sent by a SGP if an ASP
sends an ASP Active message with an unsupported Traffic Mode Type or sends an ASP Active message with an unsupported Traffic Mode Type or
a Traffic Mode Type that is inconsistent with the presently a Traffic Mode Type that is inconsistent with the presently
configured mode for the Application Server. An example would be a configured mode for the Application Server. An example would be a
case in which the SGP did not support loadsharing. case in which the SGP did not support loadsharing.
The "Unexpected Message" error MAY be sent if a defined and The "Unexpected Message" error MAY be sent if a defined and
recognized message is received that is not expected in the current recognized message is received that is not expected in the current
state (in some cases the ASP may optionally silently discard the state (in some cases, the ASP may optionally silently discard the
message and not send an Error message). For example, silent discard 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 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 was in the ASP-INACTIVE state. If the Unexpected message contained
Routing Context(s), the Routing Context(s) SHOULD be included in the Routing Contexts, the Routing Contexts SHOULD be included in the
Error message. Error message.
The "Protocol Error" error is sent for any protocol anomaly (i.e., The "Protocol Error" error is sent for any protocol anomaly (i.e.,
reception of a parameter that is syntactically correct but unexpected receipt of a parameter that is syntactically correct but unexpected
in the current situation. in the current situation).
The "Invalid Stream Identifier" error is sent if a message is The "Invalid Stream Identifier" error is sent if a message is
received on an unexpected SCTP stream (e.g., a Management message was received on an unexpected SCTP stream (e.g., a Management message was
received on a stream other than "0"). received on a stream other than "0").
The "Refused - Management Blocking" error is sent when an ASP Up or The "Refused - Management Blocking" error is sent when an ASP Up or
ASP Active message is received and the request is refused for ASP Active message is received and the request is refused for
management reasons (e.g., management lockout"). If this error is in management reasons (e.g., management lockout). If this error is in
response to an ASP Active message, the Routing Context(s) in the ASP response to an ASP Active message, the Routing Context(s) in the ASP
Active message SHOULD be included in the Error message. Active message SHOULD be included in the Error message.
The "ASP Identifier Required" is sent by a SGP in response to an ASP The "ASP Identifier Required" error is sent by an SGP in response to
Up message which does not contain an ASP Identifier parameter when an ASP Up message that does not contain an ASP Identifier parameter
the SGP requires one. The ASP SHOULD resend the ASP Up message with when the SGP requires one. The ASP SHOULD resend the ASP Up message
an ASP Identifier. with an ASP Identifier.
The "Invalid ASP Identifier" is sent by an SGP in response to an ASP The "Invalid ASP Identifier" error is sent by an SGP in response to
Up message with an invalid (i.e., non-unique) ASP Identifier. an ASP Up message with an invalid (i.e., non-unique) ASP Identifier.
The "Invalid Parameter Value " error is sent if a message is received The "Invalid Parameter Value " error is sent if a message is received
with an invalid parameter value (e.g., a DUPU message was received with an invalid parameter value (e.g., a DUPU message was received
with a Mask value other than "0". with a Mask value other than "0".
The "Parameter Field Error" would be sent if a message is received The "Parameter Field Error" would be sent if a message is received
with a parameter having a wrong length field. with a parameter having a wrong length field.
The "Unexpected Parameter" error would be sent if a message contains The "Unexpected Parameter" error would be sent if a message contains
an invalid parameter. an invalid parameter.
The "Destination Status Unknown" Error MAY be sent if a DAUD is The "Destination Status Unknown" error MAY be sent if a DAUD is
received at an SG enquiring of the availability/congestion status of received at an SG enquiring of the availability/congestion status of
a destination, and the SG does not wish to provide the status (e.g., 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 sender is not authorized to know the status). For this error,
the invalid or unauthorized Point Code(s) MUST be included along with the invalid or unauthorized Point Code(s) MUST be included along with
the Network Appearance and/or Routing Context associated with the the Network Appearance and/or Routing Context associated with the
Point Code(s). Point Code(s).
The "Invalid Network Appearance" error is sent by a SGP if an ASP The "Invalid Network Appearance" error is sent by an SGP if an ASP
sends a message with an invalid (unconfigured) Network Appearance sends a message with an invalid (unconfigured) Network Appearance
value. For this error, the invalid (unconfigured) Network Appearance value. For this error, the invalid (unconfigured) Network Appearance
MUST be included in the Network Appearance parameter. MUST be included in the Network Appearance parameter.
The "Missing Parameter" error would be sent if a mandatory parameter The "Missing Parameter" error would be sent if a mandatory parameter
were not included in a message. This error is also sent if a were not included in a message. This error is also sent if a
conditional parameter is not included in the message but is required conditional parameter is not included in the message but is required
in the context of the received message. in the context of the received message.
The "Invalid Routing Context" error is sent if a message is received The "Invalid Routing Context" error is sent if a message is received
from a peer with an invalid (unconfigured) Routing Context value. For from a peer with an invalid (unconfigured) Routing Context value.
this error, the invalid Routing Context(s) MUST be included in the For this error, the invalid Routing Context(s) MUST be included in
Error message. the Error message.
The "No Configured AS for ASP" error is sent if a message is received 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 from a peer without a Routing Context parameter and it is not known
configuration data which Application Servers are referenced. by configuration data which Application Servers are referenced.
Diagnostic Information: variable length Diagnostic Information: variable length
When included, the optional Diagnostic information can be any When included, the optional Diagnostic Information can be any
information germane to the error condition, to assist in information germane to the error condition, to assist in
identification of the error condition. The Diagnostic information identification of the error condition. The Diagnostic Information
SHOULD contain the offending message. The Diagnostic Information SHOULD contain the offending message. A Diagnostic Information
parameter with a zero length parameter is not considered as an parameter with a zero length parameter is not considered an error
error (this means that the Length field in the TLV will be set to (this means that the Length field in the TLV will be set to 4).
4).
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 Conditional ASP Identifier Conditional
Routing Context Optional Routing Context Optional
INFO String Optional INFO String Optional
skipping to change at page 61, line 30 skipping to change at page 68, line 29
/ 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 The Status Type parameter identifies the type of the Notify
message. 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 The Status Information parameter contains more detailed
information for the notification, based on the value of the Status information for the notification, based on the value of the Status
Type. 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 These notifications are sent from an SGP to an ASP upon a change
in status of a particular Application Server. The value reflects in status of a particular Application Server. The value reflects
the 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:
skipping to change at page 62, line 20 skipping to change at page 69, line 20
3 ASP Failure 3 ASP Failure
These notifications are not based on the SGP reporting the state These notifications are not based on the SGP reporting the state
change of an ASP or AS. In the Insufficient ASP Resources case, change of an ASP or AS. In the Insufficient ASP Resources case,
the SGP is indicating to an ASP_INACTIVE ASP in the AS that the SGP is indicating to an ASP_INACTIVE ASP in the AS that
another ASP is required to handle the load of the AS (Loadsharing another ASP is required to handle the load of the AS (Loadsharing
or Broadcast mode). For the Alternate ASP Active case, an ASP is or Broadcast mode). For the Alternate ASP Active case, an ASP is
informed when an alternate ASP transitions to the ASP-ACTIVE state informed when an alternate ASP transitions to the ASP-ACTIVE state
in Override mode. The ASP Identifier (if available) of the in Override mode. The ASP Identifier (if available) of the
Alternate ASP MUST be placed in the message. For the ASP Failure Alternate ASP MUST be placed in the message. For the ASP Failure
case, the SGP is indicating to ASP(s) in the AS that one of the case, the SGP is indicating to ASPs in the AS that one of the
ASPs has failed. The ASP Identifier (if available) of the failed ASPs has failed. The ASP Identifier (if available) of the failed
ASP MUST be placed in the message. ASP MUST be placed in the message.
The format and description of the conditional ASP Identifier is the The format and description of the conditional ASP Identifier is the
same as for the ASP Up message (See Section 3.5.1). The format and 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 description of the Routing Context and Info String parameters are the
same as for the ASP Active message (See Section 3.7.1) 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 The M3UA layer needs to respond to various local primitives it
receives from other layers as well as the messages that it receives receives from other layers, as well as to the messages that it
from the peer M3UA layer. This section describes the M3UA procedures receives from the peer M3UA layer. This section describes the M3UA
in response to these events. procedures 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) The M3UA message distribution function (see Section 1.4.2.1)
determines the Application Server (AS) based on comparing the determines the Application Server (AS) by comparing the information
information in the MTP-TRANSFER request primitive with a provisioned in the MTP-TRANSFER request primitive with a provisioned Routing Key.
Routing Key.
From the list of ASPs within the AS table, an ASP in the ASP-ACTIVE From the list of ASPs within the AS table, an ASP in the ASP-ACTIVE
state is selected and a DATA message is constructed and issued on the state is selected and a DATA message is constructed and issued on the
corresponding SCTP association. If more than one ASP is in the ASP- corresponding SCTP association. If more than one ASP is in the ASP-
ACTIVE state (i.e., traffic is to be loadshared across more than one 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 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 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 selected, and the message will be sent to each of the active ASPs.
selection algorithm is implementation dependent but could, for The selection algorithm is implementation dependent but could, for
example, be round robin or based on the SLS or ISUP CIC. The example, be round robin or based on the SLS or ISUP CIC. The
appropriate selection algorithm must be chosen carefully as it is appropriate selection algorithm must be chosen carefully, as it is
dependent on application assumptions and understanding of the degree dependent on application assumptions and understanding of the degree
of state coordination between the ASP-ACTIVE ASPs in the AS. of state coordination between the ASP-ACTIVE ASPs in the AS.
In addition, the message needs to be sent on the appropriate SCTP In addition, the message needs to be sent on the appropriate SCTP
stream, again taking care to meet the message sequencing needs of the stream, again taking care to meet the message sequencing needs of the
signalling application. DATA messages MUST be sent on an SCTP stream signalling application. DATA messages MUST be sent on an SCTP stream
other than stream '0'. other than stream '0'.
When there is no Routing Key match, or only a partial match, for an When there is no Routing Key match, or only a partial match, for an
incoming SS7 message, a default treatment MAY be specified. Possible incoming SS7 message, a default treatment MAY be specified. Possible
solutions are to provide a default Application Server at the SGP that 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 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 drop the message and provide a notification to Layer Management in an
M-ERROR indication primitive. The treatment of unallocated traffic M-ERROR indication primitive. The treatment of unallocated traffic
is implementation dependent. is implementation dependent.
4.2 Receipt of Primitives from the Layer Management 4.2. Receipt of Primitives from the Layer Management
On receiving primitives from the local Layer Management, the M3UA On receiving primitives from the local Layer Management, the M3UA
layer will take the requested action and provide an appropriate layer will take the requested action and provide an appropriate
response primitive to Layer Management. response primitive to Layer Management.
An M-SCTP_ESTABLISH request primitive from Layer Management at an ASP An M-SCTP_ESTABLISH request primitive from Layer Management at an ASP
or IPSP will initiate the establishment of an SCTP association. The or IPSP will initiate the establishment of an SCTP association. The
M3UA layer will attempt to establish an SCTP association with the M3UA layer will attempt to establish an SCTP association with the
remote M3UA peer by sending an SCTP-ASSOCIATE primitive to the local remote M3UA peer by sending an SCTP-ASSOCIATE primitive to the local
SCTP layer. SCTP layer.
skipping to change at page 64, line 19 skipping to change at page 71, line 49
An M-SCTP_STATUS request primitive supports a Layer Management query An M-SCTP_STATUS request primitive supports a Layer Management query
of the local status of a particular SCTP association. The M3UA layer of the local status of a particular SCTP association. The M3UA layer
simply maps the M-SCTP_STATUS request primitive to an SCTP-STATUS simply maps the M-SCTP_STATUS request primitive to an SCTP-STATUS
primitive to the SCTP layer. When the SCTP responds, the M3UA layer primitive to the SCTP layer. When the SCTP responds, the M3UA layer
maps the association status information to an M-SCTP_STATUS confirm maps the association status information to an M-SCTP_STATUS confirm
primitive. No peer protocol is invoked. primitive. No peer protocol is invoked.
Similar LM-to-M3UA-to-SCTP and/or SCTP-to-M3UA-to-LM primitive Similar LM-to-M3UA-to-SCTP and/or SCTP-to-M3UA-to-LM primitive
mappings can be described for the various other SCTP Upper Layer mappings can be described for the various other SCTP Upper Layer
primitives in RFC2960 [17] such as INITIALIZE, SET PRIMARY, CHANGE primitives in RFC2960 [18], such as INITIALIZE, SET PRIMARY, CHANGE
HEARTBEAT, REQUEST HEARTBEAT, GET SRTT REPORT, SET FAILURE THRESHOLD, HEARTBEAT, REQUEST HEARTBEAT, GET SRTT REPORT, SET FAILURE THRESHOLD,
SET PROTOCOL PARAMETERS, DESTROY SCTP INSTANCE, SEND FAILURE, AND SET PROTOCOL PARAMETERS, DESTROY SCTP INSTANCE, SEND FAILURE, and
NETWORK STATUS CHANGE. Alternatively, these SCTP Upper Layer NETWORK STATUS CHANGE. Alternatively, these SCTP Upper Layer
primitives (and Status as well) can be considered for modeling primitives (and Status as well) can be considered, for modeling
purposes as a Layer Management interaction directly with the SCTP purposes, as a Layer Management interaction directly with the SCTP
Layer. Layer.
M-NOTIFY indication and M-ERROR indication primitives indicate to M-NOTIFY indication and M-ERROR indication primitives indicate to
Layer 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 respectively. These received M3UA Notify or Error message, respectively. These
indications can also be generated based on local M3UA events. indications can also be generated based on local M3UA events.
An M-ASP_STATUS request primitive supports a Layer Management query An M-ASP_STATUS request primitive supports a Layer Management query
of the status of a particular local or remote ASP. The M3UA layer of the status of a particular local or remote ASP. The M3UA layer
responds with the status in an M-ASP_STATUS confirm primitive. No responds with the status in an M-ASP_STATUS confirm primitive. No
M3UA peer protocol is invoked. M3UA peer protocol is invoked.
An M-AS_STATUS request supports a Layer Management query of the An M-AS_STATUS request supports a Layer Management query of the
status of a particular AS. The M3UA responds with an M-AS_STATUS status of a particular AS. The M3UA responds with an M-AS_STATUS
confirm primitive. No M3UA peer protocol is invoked. confirm primitive. No M3UA peer protocol is invoked.
M-ASP_UP request, M-ASP_DOWN request, M-ASP_ACTIVE request and M- M-ASP_UP, M-ASP_DOWN, M-ASP_ACTIVE, and M-ASP_INACTIVE request
ASP_INACTIVE request primitives allow Layer Management at an ASP to primitives allow Layer Management at an ASP to initiate state
initiate state changes. Upon successful completion, a corresponding changes. Upon successful completion, a corresponding confirm
confirm primitive is provided by the M3UA layer to Layer Management. primitive is provided by the M3UA layer to Layer Management. If an
If an invocation is unsuccessful, an Error indication primitive is invocation is unsuccessful, an Error indication primitive is provided
provided in the primitive. These requests result in outgoing ASP Up, in the primitive. These requests result in outgoing ASP Up, ASP
ASP Down, ASP Active and ASP Inactive messages to the remote M3UA Down, ASP Active, and ASP Inactive messages to the remote M3UA peer
peer at an SGP or IPSP. 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, ASP Upon successful state changes resulting from reception of ASP Up, ASP
Down, ASP Active and ASP Inactive messages from a peer M3UA, the M3UA Down, ASP Active, and ASP Inactive messages from a peer M3UA, the
layer MAY invoke corresponding M-ASP_UP, M-ASP_DOWN, M-ASP_ACTIVE and M3UA layer MAY invoke corresponding M-ASP_UP, M-ASP_DOWN, M-
M-ASP_INACTIVE, M-AS_ACTIVE, M-AS_INACTIVE, and M-AS_DOWN indication ASP_ACTIVE, M-ASP_INACTIVE, M-AS_ACTIVE, M-AS_INACTIVE, and M-AS_DOWN
primitives to the local Layer Management. indication primitives to the local Layer Management.
M-NOTIFY indication and M-ERROR indication primitives indicate to M-NOTIFY indication and M-ERROR indication primitives indicate to
Layer 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 traffic related to the Routing Context(s), to minimize possible
message loss. BEAT and BEAT Ack messages MAY be sent using out-of- message loss. BEAT and BEAT Ack messages MAY be sent using out-of-
order delivery, and MAY be sent on any stream. order delivery and MAY be sent on any stream.
4.3 AS and ASP/IPSP State Maintenance 4.3. AS and ASP/IPSP 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 each Application Server that the ASP is configured to receive
traffic, as input to the M3UA message distribution function. traffic, as input to the M3UA message distribution function.
Similarly, where IPSPs use M3UA in a point-to-point fashion, the M3UA Similarly, where IPSPs use M3UA in a point-to-point fashion, the M3UA
layer in an IPSP maintains the state of remote IPSPs. layer in an IPSP maintains the state of remote IPSPs.
Two IPSP models are defined as follows: Two IPSP models are defined as follows:
1- IPSP Single Exchange (SE) model. Only a single exchange of ASPTM 1. IPSP Single Exchange (SE) model. Only a single exchange of ASPTM
and ASPSM messages are needed to change the IPSP states. This means and ASPSM messages is needed to change the IPSP states. This
that a set of request from one end and acknowledgement from the means that a set of requests from one end and acknowledgements
other will be enough. The RK must define both sides of the traffic from the other will be enough. The RK must define both sides of
flow. Each exchange of ASPTM or ASPSM messages can be initiated by the traffic flow. Each exchange of ASPTM or ASPSM messages can be
either IPSP. For this exchange, the initiating IPSP follows the initiated by either IPSP. For this exchange, the initiating IPSP
procedures described in section 4.3.1. follows the procedures described in Section 4.3.1.
2- IPSP Double Exchange (DE) model. A double exchange of ASPTM and 2. IPSP Double Exchange (DE) model. A double exchange of ASPTM and
ASPSM messages are normally needed (ASPSM single exchange is ASPSM messages is normally needed (ASPSM single exchange is
optional as a simplification). Each exchange of ASPTM or ASPSM optional as a simplification). Each exchange of ASPTM or ASPSM
messages can be initiated by either IPSP. The RKs define the messages can be initiated by either IPSP. The RKs define the
traffic to be directed to the peer as in the AS-SG model. Therefore traffic to be directed to the peer as in the AS-SG model.
two different RKs are usually used, one installed on each peer. Therefore, two different RKs are usually used, one installed on
each peer.
When using double exchanges for ASPSM messages, the management of When using double exchanges for ASPSM messages, the management of
the connection in the two directions are considered independent. the connection in the two directions is considered independent.
This means that connections from IPSP-A to IPSP-B is handled in an This means that connections from IPSP-A to IPSP-B is handled
independent way that connection from IPSP-B to IPSP-A. Therefore it independently of connections from IPSP-B to IPSP-A. Therefore, it
could happen that only one of the two directions are activated or could happen that only one of the two directions is activated or
closed, while the other remain in the same state as it was. closed, while the other remains in the same state as it was.
When using single exchange of ASPSM, what is seen as a When using single exchange of ASPSM, what is seen as a
simplification, it is only the activation phase (ASPTM messages) simplification, only the activation phase (ASPTM messages) is
what is independent for each of the two directions. In this case it independent for each of the two directions. In this case, it
could happen the sending the ASPSM from IPSP-A or IPSP-B will have could happen that the sending of the ASPSM from IPSP-A or IPSP-B
an effect in the whole communication as it is defined in the could have an effect in the whole communication, as it is defined
standard SG-AS communication. in the standard SG-AS communication.
Because of these differences, there should be an agreements on the Because of these differences, there should be an agreement on the
way ASPSM messages are being handled before starting DE-IPSP way ASPSM messages are being handled before starting DE-IPSP
communication. communication.
In order to ensure interoperability, an M3UA implementation supporting In order to ensure interoperability, an M3UA implementation
IPSP communication MUST support IPSP SE model and MAY implement IPSP supporting IPSP communication MUST support the IPSP SE model and MAY
DE model. implement the IPSP DE model.
In section 4.3.1 ASP/IPSP States are described. In Section 4.3.1, ASP/IPSP States are described.
In section 4.3.2, only the SGP-ASP scenario is described. All of the In Section 4.3.2, only the SGP-ASP scenario is described. All of the
procedures referring to an AS served by ASPs are also applicable to procedures referring to an AS served by ASPs are also applicable to
ASes served by IPSPs. ASes served by IPSPs.
In section 4.3.3, only the Management procedures for the SGP-ASP In Section 4.3.3, only the Management procedures for the SGP-ASP
scenario are described. The corresponding Management procedures for scenario are described. The corresponding Management procedures for
IPSPs are directly inferred. IPSPs are directly implied.
The remaining sections contain specific IPSP Considerations sub- The remaining sections contain specific IPSP Considerations
sections. subsections.
4.3.1 ASP/IPSP States 4.3.1. ASP/IPSP States
The state of each remote ASP/IPSP, in each AS that it is configured to The state of each remote ASP/IPSP, in each AS that it is configured
operate, is maintained in the peer M3UA layer (i.e. in the SGP or peer to operate, is maintained in the peer M3UA layer (i.e., in the SGP or
IPSP, respectively). The state of a particular ASP/IPSP in a peer IPSP, respectively). The state of a particular ASP/IPSP in a
particular AS changes due to events. The events include: particular AS changes due to events. The events include:
* Reception of messages from the peer M3UA layer at the ASP/IPSP; * Receipt of messages from the peer M3UA layer at the ASP/IPSP;
* Reception of some messages from the peer M3UA layer at other * Receipt of some messages from the peer M3UA layer at other
ASPs/IPSPs in the AS (e.g., ASP Active message indicating ASPs/IPSPs in the AS (e.g., ASP Active message indicating
"Override"); "Override");
* Reception of indications from the SCTP layer; or * Receipt of indications from the SCTP layer; and
* Local Management intervention. * Local Management intervention.
The ASP/C-IPSP/D-IPSP state transition diagram is shown in Figure 3. The ASP/C-IPSP/D-IPSP state transition diagram is shown in Figure 3.
The possible states of an ASP/D-IPSP/C-IPSP are: The possible states of an ASP/D-IPSP/C-IPSP are:
ASP-DOWN: The remote M3UA peer at the ASP/IPSP is unavailable and/or ASP-DOWN: The remote M3UA peer at the ASP/IPSP is unavailable, and/or
the related SCTP association is down. Initially all ASPs/IPSPs will the related SCTP association is down. Initially, all ASPs/IPSPs will
be in this state. An ASP/IPSP in this state SHOULD NOT be sent any be in this state. An ASP/IPSP in this state SHOULD NOT be sent any
M3UA messages, with the exception of Heartbeat, ASP Down Ack and Error M3UA messages, with the exception of Heartbeat, ASP Down Ack, and
messages. Error messages.
ASP-INACTIVE: The remote M3UA peer at the ASP/IPSP is available (and ASP-INACTIVE: The remote M3UA peer at the ASP/IPSP is available (and
the related SCTP association is up) but application traffic is the related SCTP association is up), but application traffic is
stopped. In this state the ASP/IPSP SHOULD NOT be sent any DATA or stopped. In this state, the ASP/IPSP SHOULD NOT be sent any DATA or
SSNM messages for the AS for which the ASP/IPSP is inactive. SSNM messages for the AS for which the ASP/IPSP is inactive.
ASP-ACTIVE: The remote M3UA peer at the ASP/IPSP is available and ASP-ACTIVE: The remote M3UA peer at the ASP/IPSP is available and
application traffic is active (for a particular Routing Context or application traffic is active (for a particular Routing Context or
set 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 Down Indication to the Upper Layer Protocol (M3UA) on an SGP. The
local SCTP layer will send this indication when it detects the loss local SCTP layer will send this indication when it detects the loss
of connectivity to the ASP's peer SCTP layer. SCTP CDI is understood of connectivity to the ASP's peer SCTP layer. SCTP CDI is understood
as either a SHUTDOWN_COMPLETE notification or COMMUNICATION_LOST as either a SHUTDOWN_COMPLETE notification or a 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 peer SCTP layer. when it detects a restart from the peer SCTP layer.
Figure 3: ASP State Transition Diagram, per AS
+--------------+ +--------------+
| | | |
+----------------------| ASP-ACTIVE | +----------------------| ASP-ACTIVE |
| Other ASP/ +-------| | | Other ASP/ +-------| |
| IPSP in AS | +--------------+ | IPSP in AS | +--------------+
| Overrides | ^ | | Overrides | ^ |
| | ASPAC/ | | ASPIA/ | | ASPAC/ | | ASPIA/
| |[ASPAC-Ack]| | [ASPIA-Ack] | |[ASPAC-Ack]| | [ASPIA-Ack]
| | | v | | | v
| | +--------------+ | | +--------------+
skipping to change at page 67, line 50 skipping to change at page 75, line 38
[ASPDN-Ack/]| ASPUP/ | | [ASPDN-Ack /] [ASPDN-Ack/]| ASPUP/ | | [ASPDN-Ack /]
SCTP CDI/ | [ASPUP-Ack] | | SCTP CDI/ SCTP CDI/ | [ASPUP-Ack] | | SCTP CDI/
SCTP RI | | | SCTP RI SCTP RI | | | SCTP RI
| | v | | v
| +--------------+ | +--------------+
| | | | | |
+--------------------->| ASP-DOWN | +--------------------->| ASP-DOWN |
| | | |
+--------------+ +--------------+
Figure 3: ASP State Transition Diagram, per AS
The transitions are depicted as a result of the reception of ASP*M The transitions are depicted as a result of the reception of ASP*M
messages or other events. In some of the transitions there are some messages or other events. In some of the transitions, there are some
messages in brackets. They mean that for a given node the state messages in brackets. They mean that for a given node the state
transition will be different depending on its role: whether or not it transition will be different, depending on its role: whether or not
is generating the ASP*M request message (i.e. ASPUP, ASPAC, ASPIA or it is generating the ASP*M request message (i.e., ASPUP, ASPAC, ASPIA
ASPDN) or simply receiving it. In a peer-to-peer based architecture or ASPDN) or simply receiving it. In a peer-to-peer based
(IPSP), this role may change between the peers. architecture (IPSP), this role may change between the peers.
The transitions not in brackets are valid to track the states of ASPs The transitions not in brackets are valid to track the states of ASPs
and IPSPs that send an ASP*M request message at the peer node. and IPSPs that send an ASP*M request message at the peer node.
The transition in brackets may be used in an ASP or in the IPSP that The transition in brackets may be used in an ASP or in the IPSP that
receives an ASP*M request to track the peer SGP/IPSP states receives an ASP*M request to track the peer SGP/IPSP states,
respectively. There may be an SGP per AS state machine at ASPs. respectively. There may be an SGP per AS state machine at ASPs.
Then the transitions in brackets can be used for the IPSP DE model Then, the transitions in brackets can be used for the IPSP DE model
communication (DE-IPSPs) and are related to the special cases when communication (DE-IPSPs) and are related to the special cases when
just one ASP*M messages exchange is needed, as follows: just one ASP*M messages exchange is needed, as follows:
- ASPSM messages. When exchanging ASPSM messages using only a single - ASPSM messages. When ASPSM messages are exchanged using only a
exchange (only one request and one acknowledgment). . single exchange (only one request and one acknowledgement).
Example: (see section 5.6.2) whenever a DE-IPSP is taking the Example (see Section 5.6.2): Whenever a DE-IPSP is taking the
leading role to start communication to a peer DE-IPSP, it sends ASP leading role to start communication to a peer DE-IPSP, it sends an
Up message to the peer DE-IPSP. The peer MAY consider the initiating ASP Up message to the peer DE-IPSP. The peer MAY consider the
DE-IPSPs as being in ASP-INACTIVE state, as it already sent a initiating DE-IPSPs to be in ASP-INACTIVE state, as it already sent
message, and answer back with ASP Up Ack. Upon the reception of this a message, and answer back with ASP Up Ack. Upon receipt of this
answer by the initiating DE-IPSP it alsoMAY consider the peer as answer by the initiating DE-IPSP, it also MAY consider the peer to
being in ASP-INACTIVE state since it did respond. Therefore a second be in ASP-INACTIVE state, since it did respond. Therefore, a
ASP Up message exchange to be started by the peer DE-IPSP could be second ASP Up message exchange to be started by the peer DE-IPSP
avoided. In this case the reception of ASP Up Ack will turn into a could be avoided. In this case, the receipt of ASP Up Ack will
state change. turn into a state change.
- ASPTM messages. When sending ASPTM messages to activate/deactivate - ASPTM messages. When sending ASPTM messages to activate/deactivate
all the traffic independently of routing keys by not specifying any all the traffic independently of routing keys by not specifying any
RC, a single exchange could be sufficient. RC, a single exchange could be sufficient.
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 ASP-DOWN state for this AS. Initially the that all related ASPs are in ASP-DOWN state for this AS. Initially
AS will be in this state. An Application Server is in the AS-DOWN the AS will be in this state. An Application Server is in the AS-
state when it is removed from a configuration. 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. One or more related ASPs are in ASP-INACTIVE state traffic is active. One or more related ASPs are in ASP-INACTIVE
and/or the number of related ASPs in ASP-ACTIVE state has not reached state, and/or the number of related ASPs in ASP-ACTIVE state has not
n (n is the number of ASPs required to be in ASP-ACTIVE state before reached n (n is the number of ASPs required to be in ASP-ACTIVE state
AS can transition to AS-ACTIVE, n = 1 for Override Traffic Mode) for before AS can transition to AS-ACTIVE; n = 1 for Override Traffic
this AS. The recovery timer T(r) is not running or has expired. Mode) for this AS. The recovery timer T(r) is not running or has
expired.
AS-ACTIVE: The Application Server is available and application traffic AS-ACTIVE: The Application Server is available and application
is active. The AS moves to this state after being in AS-INACTIVE and traffic is active. The AS moves to this state after being in AS-
getting n ASPs (n is the number of ASPs required to be in ASP-ACTIVE INACTIVE and getting n ASPs (n is the number of ASPs required to be
state before AS can transition to AS-ACTIVE, n = 1 for Override in ASP-ACTIVE state before AS can transition to AS-ACTIVE; n = 1 for
Traffic Mode) in ASP-ACTIVE state or, after reaching AS-ACTIVE and Override Traffic Mode) in ASP-ACTIVE state or after reaching AS-
keeping one or more ASPs in ASP-ACTIVE state. ACTIVE and keeping one or more ASPs in ASP-ACTIVE state. When one
When it is considered that one ASP is enough to handle traffic (smooth ASP is considered enough to handle traffic (smooth start), the AS in
start), the AS in AS-INACTIVE MAY reach the AS-ACTIVE as soon as the AS-INACTIVE MAY reach the AS-ACTIVE as soon as the first ASP moves to
first ASP moves to the ASP-ACTIVE state. the ASP-ACTIVE state.
AS-PENDING: An active ASP has transitioned to ASP-INACTIVE or ASP DOWN AS-PENDING: An active ASP has transitioned to ASP-INACTIVE or ASP
and it was the last remaining active ASP in the AS. A recovery timer DOWN and it was the last remaining active ASP in the AS. A recovery
T(r) SHOULD be started and all incoming signalling messages SHOULD be timer T(r) SHOULD be started, and all incoming signalling messages
queued by the SGP. If an ASP becomes ASP-ACTIVE before T(r) expires, SHOULD be queued by the SGP. If an ASP becomes ASP-ACTIVE before
the AS is moved to the AS-ACTIVE state and all the queued messages T(r) expires, the AS is moved to the AS-ACTIVE state, and all the
will be sent to the ASP. queued 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 stop queuing messages and discards all alternative, the SGP may stop queuing messages and discard all
previously queued messages. The AS will move to the AS-INACTIVE state previously queued messages. The AS will move to the AS-INACTIVE
if at least one ASP is in ASP-INACTIVE, otherwise it will move to AS- state if at least one ASP is in ASP-INACTIVE; otherwise, it will move
DOWN state. to AS-DOWN state.
Figure 4 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 and an n+k redundancy model. In other AS/ASP data is preconfigured and is an n+k redundancy model. In
cases where the AS/ASP configuration data is created dynamically, other cases where the AS/ASP configuration data is created
there would be differences in the state machine, especially at dynamically, there would be differences in the state machine,
creation of the AS. especially at creation of the AS.
Figure 4: AS State Transition Diagram
+----------+ IA2AC +-------------+ +----------+ IA2AC +-------------+
| AS- |---------------------------->| AS- | | AS- |---------------------------->| AS- |
| INACTIVE | | ACTIVE | | INACTIVE | | ACTIVE |
| |<----------- | | | |<----------- | |
+----------+ \ +-------------+ +----------+ \ +-------------+
^ | \ ^ | ^ | \ ^ |
| | IA2DN \ PN2IA | | AC2PN | | IA2DN \ PN2IA | | AC2PN
| | \ | | | | \ | |
DN2IA | | \ PN2AC | | DN2IA | | \ PN2AC | |
| v \ | v | v \ | v
+----------+ \ +-------------+ +----------+ \ +-------------+
| | ----------| | | | ----------| |
| AS-DOWN | | AS-PENDING | | AS-DOWN | | AS-PENDING |
| | PN2DN | (queueing) | | | PN2DN | (queueing) |
| |<----------------------------| | | |<----------------------------| |
+----------+ +-------------+ +----------+ +-------------+
Figure 4: AS State Transition Diagram
DN2IA: One ASP moves from ASP-DOWN to ASP-INACTIVE state. DN2IA: One ASP moves from ASP-DOWN to ASP-INACTIVE state.
IA2DN: The last ASP in ASP-INACTIVE moves to ASP-DOWN causing that the IA2DN: The last ASP in ASP-INACTIVE moves to ASP-DOWN, causing all
all the ASPs are in ASP-DOWN state. the ASPs to be in ASP-DOWN state.
IA2AC: one ASP moves to ASP-ACTIVE, causing number of ASPs in the ASP- IA2AC: One ASP moves to ASP-ACTIVE, causing the number of ASPs in the
ACTIVE state to be n. ASP-ACTIVE state to be n. In a special case of smooth start, this
In a special case of smooth start, this transition MAY be done when transition MAY be done when the first ASP moves to ASP-ACTIVE state.
the first ASP moves to ASP-ACTIVE state.
AC2PN: the last ASP in ASP-ACTIVE state moves to ASP-INACTIVE or ASP- AC2PN: The last ASP in ASP-ACTIVE state moves to ASP-INACTIVE or
DOWN states, causing the number of ASPs in ASP-ACTIVE drop below 1. ASP-DOWN states, causing the number of ASPs in ASP-ACTIVE to drop
below 1.
PN2AC: One ASP moves to ASP-ACTIVE. PN2AC: One ASP moves to ASP-ACTIVE.
PN2IA: T(r) Expiry, an ASP is in ASP-INACTIVE state but no ASPs are in PN2IA: T(r) expiry; an ASP is in ASP-INACTIVE state but no ASPs are
ASP-ACTIVE state. in ASP-ACTIVE state.
PN2DN: T(r) Expiry, all the ASPs are in ASP-DOWN state. PN2DN: T(r) expiry; all the ASPs are in ASP-DOWN state.
An AS becomes AS-ACTIVE right after n ASPs reach the ASP-ACTIVE state An AS becomes AS-ACTIVE right after n ASPs reach the ASP-ACTIVE state
during the start-up phase (except for smooth start). Once the traffic during the startup phase (except for smooth start). Once the traffic
is flowing, an AS keeps the AS-ACTIVE state till the last ASP turns to is flowing, an AS keeps the AS-ACTIVE state till the last ASP turns
another state different to ASP-ACTIVE, avoiding unnecessary traffic to another state different from ASP-ACTIVE, avoiding unnecessary
disturbances as long as there are ASPs available, in the assumption traffic disturbances as long as there are ASPs available (this
that the system will not always be exposed to the maximum load. assumes that the system will not always be exposed to the maximum
load).
There are other cases where the AS/ASP configuration data is created There are other cases where the AS/ASP configuration data is created
dynamically. In those cases there would be differences in the state dynamically. In those cases there would be differences in the state
machine, especially at creation of the AS. For example, where the machine, especially at creation of the AS. For example, where the
AS/ASP configuration data is not created until Registration of the AS/ASP configuration data is not created until Registration of the
first ASP, the AS-INACTIVE state is entered directly upon the nth first ASP, the AS-INACTIVE state is entered directly upon the nth
successful REG REQ from an ASP belonging to that AS. Another example successful REG REQ from an ASP belonging to that AS. Another example
is where the AS/ASP configuration data is not created until the nth is where the AS/ASP configuration data is not created until the nth
ASP successfully enters the ASP-ACTIVE state. In this latter case the ASP successfully enters the ASP-ACTIVE state. In this latter 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
the SGP and ASP is assumed to be in the state ASP-DOWN. both the SGP and ASP is assumed to be in the state ASP-DOWN.
Once the SCTP association is established (see Section 4.2) and Once the SCTP association is established (see Section 4.2), assuming
assuming that the local M3UA-User is ready, the local M3UA ASP that the local M3UA-User is ready, the local M3UA ASP Maintenance
Maintenance (ASPM) function will initiate the relevant procedures, (ASPM) function will initiate the relevant procedures, using the ASP
using the ASP Up/ASP Down/ASP Active/ASP Inactive messages to convey Up/ASP Down/ASP Active/ASP Inactive messages to convey the ASP state
the ASP state to the SGP (see Section 4.3.4). to the SGP (see Section 4.3.4).
If the M3UA layer subsequently receives an SCTP-COMMUNICATION_DOWN or If the M3UA layer subsequently receives an SCTP-COMMUNICATION_DOWN 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-
At an ASP, the MTP3-User will be informed of the unavailability of DOWN. At an ASP, the MTP3-User will be informed of the
any affected SS7 destinations through the use of MTP-PAUSE indication unavailability of any affected SS7 destinations through the use of
primitives. MTP-PAUSE indication primitives.
In the case of SCTP-COMMUNICATION_DOWN, the SCTP client MAY try to In the case of SCTP-COMMUNICATION_DOWN, the SCTP client MAY try to
re-establish the SCTP Association. This MAY be done by the M3UA re-establish the SCTP Association. This MAY be done by the M3UA
layer automatically, or Layer Management MAY re-establish using the layer automatically, or Layer Management MAY reestablish 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 to be in the ASP-DOWN state by its M3UA peer. 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 When an ASP Up message is received at an SGP and, internally, the
remote ASP is in the ASP-DOWN state and not considered locked out for remote ASP is in the ASP-DOWN state and is not considered locked out
local management reasons, the SGP marks the remote ASP in the state for local management reasons, the SGP marks the remote ASP in the
ASP-INACTIVE and informs Layer Management with an M-ASP_Up indication state ASP-INACTIVE and informs Layer Management with an M-ASP_Up
primitive. If the SGP is aware, via current configuration data, indication primitive. If the SGP is aware, via current configuration
which Application Servers the ASP is configured to operate in, the data, which Application Servers the ASP is configured to operate in,
SGP updates the ASP state to ASP-INACTIVE in each AS that it is a the SGP updates the ASP state to ASP-INACTIVE in each AS that it is a
member. 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 Servers,
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 ASP should save the ASP Identifier for that ASP. The SGP MUST send an
Up Ack message in response to a received ASP Up message even if the ASP Up Ack message in response to a received ASP Up message even if
ASP is already marked as ASP-INACTIVE at the SGP. the ASP is already marked as ASP-INACTIVE at the SGP.
If for any local reason (e.g., management 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 the reason "Refused - Management
Blocking". Blocking".
At the ASP, the ASP Up Ack message received is not acknowledged. At the ASP, the ASP Up Ack message received is not acknowledged.
Layer 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), ASP does not receive a response to an ASP Up message within T(ack),
the ASP MAY restart T(ack) and resend ASP Up messages until it the ASP MAY restart T(ack) and resend ASP Up messages until it
receives an ASP Up Ack message. T(ack) is provisionable, with a receives an ASP Up Ack message. T(ack) is provisionable, with a
default of 2 seconds. Alternatively, retransmission of ASP Up default of 2 seconds. Alternatively, retransmission of ASP Up
messages MAY be put under control of Layer Management. In this messages MAY be put under control of Layer Management. In this
method, expiry of T(ack) results in an M-ASP_UP confirm primitive method, expiry of T(ack) results in an M-ASP_UP confirm primitive
carrying a negative 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
the ASP-ACTIVE state, an ASP Up Ack message is returned, as well as, in the ASP-ACTIVE state, an ASP Up Ack message is returned, as well
an Error message ("Unexpected Message). In addition, the remote ASP as an Error message ("Unexpected Message"). In addition, the remote
state is changed to ASP-INACTIVE in all relevant Application Servers ASP state is changed to ASP-INACTIVE in all relevant Application
and all registered Routing Keys are considered deregistered. Servers, and all registered Routing Keys are considered deregistered.
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.
If the ASP receives an unexpected ASP Up Ack message, the ASP should If the ASP receives an unexpected ASP Up Ack message, the ASP should
consider itself in the ASP-INACTIVE state. If the ASP was not in the consider itself in the ASP-INACTIVE state. If the ASP was not in the
ASP-INACTIVE state, it SHOULD send an Error message and then initiate ASP-INACTIVE state, it SHOULD send an Error message and then initiate
procedures to return itself to its previous state. procedures to return itself to its previous state.
4.3.4.1.1 M3UA Version Control and ASP Up 4.3.4.1.1. M3UA Version Control and ASP Up
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. See section the receiving node supports and notifies Layer Management. See
4.8 for more on this issue. Section 4.8 for more on this issue.
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 An IPSP may be considered in the ASP-INACTIVE state after an ASP Up
or ASP Up Ack has been received from it. An IPSP can be considered or ASP Up Ack has been received from it. An IPSP can be considered
in the ASP-DOWN state after an ASP Down or ASP Down Ack has been in the ASP-DOWN state after an ASP Down or ASP Down Ack has been
received from it. The IPSP may inform Layer Management of the change received from it. The IPSP may inform Layer Management of the change
in state of the remote IPSP using M-ASP_UP or M-ASP_DN indication or in state of the remote IPSP using M-ASP_UP or M-ASP_DN indication or
confirmation primitives. confirmation primitives.
Alternatively, when using IPSP DE model, an interchange of ASP Up Alternatively, when using the IPSP DE model, an interchange of ASP Up
messages from each end MUST be performed. Four messages are needed for messages from each end MUST be performed. Four messages are needed
completion. 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 respond to an ASP Up message with an ASP Up Ack message, it responds
to an ASP Up message with an Error message with reason "Refused to an ASP Up message with an Error message with the reason "Refused
Management Blocking" and leaves the remote IPSP in the ASP-DOWN Management Blocking" and leaves the remote IPSP in the ASP-DOWN
state. 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 The ASP will send an ASP Down message to an SGP when the ASP wishes
to be removed from service in all Application Servers that it is a to be removed from service in all Application Servers that it is a
member and no longer receive any DATA, SSNM or ASPTM messages. This member and no longer receive any DATA, SSNM or, ASPTM messages. This
action MAY be initiated at the ASP by an M-ASP_DOWN request primitive action MAY be initiated at the ASP by an M-ASP_DOWN request primitive
from Layer Management or MAY be initiated automatically by an M3UA from Layer Management or MAY be initiated automatically 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 Application Servers but has not deregistered from all of them prior
to sending the ASP Down message, the SGP MUST consider the ASP as to sending the ASP Down message, the SGP MUST consider the ASP
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 The SGP marks the ASP as ASP-DOWN, informs Layer Management with an
M-ASP_Down indication primitive, and returns an ASP Down Ack message M-ASP_Down indication primitive, and returns an ASP Down Ack message
to the ASP. to the ASP.
The SGP MUST send an ASP Down Ack message in response to a received 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. Layer Management is informed with an M-ASP_DOWN confirm primitive.
If the ASP receives an ASP Down Ack without having sent an ASP Down 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 to be in the ASP-DOWN
state.
If the ASP was previously in the ASP-ACTIVE or ASP-INACTIVE 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 the ASP should then initiate procedures to return itself to its
previous state. previous state.
When the ASP sends an ASP Down message it starts timer T(ack). If When the ASP sends an ASP Down message, it starts timer T(ack). If
the ASP does not receive a response to an ASP Down message within the ASP does not receive a response to an ASP Down message within
T(ack), the ASP MAY restart T(ack) and resend ASP Down messages until T(ack), the ASP MAY restart T(ack) and resend ASP Down messages until
it receives an ASP Down Ack message. T(ack) is provisionable, with a it receives an ASP Down Ack message. T(ack) is provisionable, with a
default of 2 seconds. Alternatively, retransmission of ASP Down default of 2 seconds. Alternatively, retransmission of ASP Down
messages MAY be put under control of Layer Management. In this messages MAY be put under control of Layer Management. In this
method, expiry of T(ack) results in an M-ASP_DOWN confirm primitive method, expiry of T(ack) results in an M-ASP_DOWN confirm primitive,
carrying a negative indication. 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,
that the ASP is ready to start processing traffic. This action MAY indicating that the ASP is ready to start processing traffic. This
be initiated at the ASP by an M-ASP_ACTIVE request primitive from action MAY be initiated at the ASP by an M-ASP_ACTIVE 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 wishes to process the an M3UA management function. In the case where an ASP wishes to
traffic for more than one Application Server across a common SCTP process the traffic for more than one Application Server across a
association, the ASP Active message(s) SHOULD contain a list of one common SCTP association, the ASP Active message(s) SHOULD contain a
or more Routing Contexts to indicate for which Application Servers list of one or more Routing Contexts to indicate for which
the ASP Active message applies. It is not necessary for the ASP to Application Servers the ASP Active message applies. It is not
include all Routing Contexts of interest in a single ASP Active necessary for the ASP to include all Routing Contexts of interest in
message, thus requesting to become active in all Routing Contexts at a single ASP Active message, thus requesting to become active in all
the same time. Multiple ASP Active messages MAY be used to activate Routing Contexts at the same time. Multiple ASP Active messages MAY
within the Application Servers independently, or in sets. be used to activate within the Application Servers independently, or
in sets.
In the case where an ASP Active message does not contain a Routing In the case where an ASP Active message does not contain a Routing
Context parameter, the receiver must know, via configuration data, Context parameter, the receiver must know, via configuration data,
which Application Server(s) the ASP is a member. which Application Server(s) the ASP is a member.
For the Application Servers that the ASP can be successfully For the Application Servers for which the ASP can be successfully
activated, the SGP or IPSP responds with one or more ASP Active Ack activated, the SGP or IPSP responds with one or more ASP Active Ack
messages, including the associated Routing Context(s) and reflecting messages, including the associated Routing Context(s) and reflecting
any Traffic Mode Type value present in the related ASP Active any Traffic Mode Type value present in the related ASP Active
message. The Routing Context parameter MUST be included in the ASP message. The Routing Context parameter MUST be included in the ASP
Active Ack message(s) if the received ASP Active message contained Active Ack message(s) if the received ASP Active message contained
any 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 receives informed with an M-ASP_Active indication. If the SGP or IPSP
any Data messages before an ASP Active message is received, the SGP receives any Data messages before an ASP Active message is received,
or IPSP MAY discard them. By sending an ASP Active Ack message, the the SGP or IPSP MAY discard them. By sending an ASP Active Ack
SGP or IPSP is now ready to receive and send traffic for the related message, the SGP or IPSP is now ready to receive and send traffic for
the related Routing Context(s). The ASP SHOULD NOT send Data or SSNM
Routing Context(s). The ASP SHOULD NOT send Data or SSNM messages messages for the related Routing Context(s) before receiving an ASP
for the related Routing Context(s) before receiving an ASP Active Ack Active Ack message, or it will risk message loss.
message, or it will risk message loss.
Multiple ASP Active Ack messages MAY be used in response to an ASP Multiple ASP Active Ack messages MAY be used in response to an ASP
Active message containing multiple 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. different (sets of) Routing Contexts.
The ASP Active message will be responded in the following way as a The ASP Active message will be responded to in the following way as a
function of the presence/need of the RC parameter: function of the presence/need of the RC parameter:
- If the RC parameter is included in the ASP Active message and the - If the RC parameter is included in the ASP Active message and the
corresponding RK has been previously defined (by either static corresponding RK has been previously defined (by either static
configuration or dynamic registration), the peer node MUST respond configuration or dynamic registration), the peer node MUST respond
with an ASP Active Ack message. If for any local reason (e.g. with an ASP Active Ack message. If for any local reason (e.g.,
management lockout) the SGP responds t an ASP Active message with an management lockout) the SGP responds to an ASP Active message with
Error message with reason "Refused Management Blocking". an Error message with reason "Refused Management Blocking".
- If the RC parameter is included in the ASP Active message and a - If the RC parameter is included in the ASP Active message and a
corresponding RK has not been previously defined (by either static corresponding RK has not been previously defined (by either static
configuration or dynamic registration), the peer MUST respond with configuration or dynamic registration), the peer MUST respond with
an ERROR message with Error Code = "No configured AS for ASP". an ERROR message with the Error Code "No configured AS for ASP".
- If the RC parameter is not included in the ASP Active message, there - If (1) the RC parameter is not included in the ASP Active message,
are RKs defined (by either static configuration or dynamic (2) there are RKs defined (by either static configuration or
registration) and RC is not mandatory, the peer node SHOULD respond dynamic registration) and (3) RC is not mandatory, the peer node
with an ASP Active Ack message and activate all the RKs it has SHOULD respond with an ASP Active Ack message and activate all the
defined for that specific ASP. RKs it has defined for that specific ASP.
- If the RC parameter is not included in the ASP Active message, there - If (!) the RC parameter is not included in the ASP Active message,
are RKs defined (by either static configuration or dynamic (2) there are RKs defined (by either static configuration or
registration) and RC is mandatory, the peer node MUST respond with dynamic registration), (3) and RC is mandatory, the peer node MUST
and ERROR message with the Error Code = "Missing Parameter". respond with an ERROR message with the Error Code "Missing
Parameter".
- If the RC parameter is not included in the ASP Active message, there - If (1) the RC parameter is not included in the ASP Active message,
are RKs defined (by either static configuration or dynamic (2) there are RKs defined (by either static configuration or
registration) and RC is not mandatory, the peer node MUST respond dynamic registration) and (3) RC is not mandatory, the peer node
with an ASP Active Ack message if it is ready to handle traffic; MUST respond with an ASP Active Ack message if it is ready to
otherwise it will send an ERROR message with the Error Code = "No handle traffic; otherwise, it will send an ERROR message with the
Configured AS for ASP" (meaning that it is not ready to become Error Code "No Configured AS for ASP" (meaning that it is not ready
active). to become active).
- If the RC parameter is not included in the ASP Active message and - If the RC parameter is not included in the ASP Active message and
there are no RKs defined, the peer node SHOULD respond with and there are no RKs defined, the peer node SHOULD respond with and
ERROR message with the Error Code = "Invalid Routing Context". ERROR message with the Error Code "Invalid Routing Context".
Independently of the RC, the SGP MUST send an ASP Active Ack message Independently of the RC, the SGP MUST send an ASP Active Ack message
in response to a received ASP Active message from the ASP, if the ASP in response to a received ASP Active message from the ASP, if the ASP
is already marked in the APS-ACTIVE state. is already marked in the APS-ACTIVE state.
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 messages 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 receipt 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 the timer T(ack).
the ASP does not receive a response to an ASP Active message within If the ASP does not receive a response to an ASP Active message
T(ack), the ASP MAY restart T(ack) and resend ASP Active messages within T(ack), the ASP MAY restart T(ack) and resend ASP Active
until it receives an ASP Active Ack message. T(ack) is messages until it receives an ASP Active Ack message. T(ack) is
provisionable, with a default of 2 seconds. Alternatively, provisionable, with a default of 2 seconds. Alternatively,
retransmission of ASP Active messages MAY be put under control of retransmission of ASP Active messages MAY be put under control of
Layer Management. In this method, expiry of T(ack) results in an M- Layer Management. In this method, expiry of T(ack) results in an M-
ASP_ACTIVE confirm primitive carrying a negative indication. ASP_ACTIVE confirm primitive carrying a negative indication.
There are three modes of Application Server traffic handling in the There are three modes of Application Server traffic handling in the
SGP M3UA layer: Override, Loadshare and Broadcast. When included, SGP M3UA layer: Override, Loadshare and Broadcast. When included,
the Traffic Mode Type parameter in the ASP Active message indicates the Traffic Mode Type parameter in the ASP Active message indicates
the traffic handling mode to be used in a particular Application the traffic handling mode to be used in a particular Application
Server. If the SGP determines that the mode indicated in an ASP Server. If the SGP determines that the mode indicated in an ASP
Active 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 In the case of an Override mode AS, receipt of an ASP Active message
message at an SGP causes the (re)direction of all traffic for the AS at an SGP causes the (re)direction of all traffic for the AS to the
to the ASP that sent the ASP Active message. Any previously active ASP that sent the ASP Active message. Any previously active ASP in
ASP in the AS is now considered to be in state ASP-INACTIVE and the AS is now considered to be in the state ASP-INACTIVE and SHOULD
SHOULD no longer receive traffic from the SGP within the AS. The SGP no longer receive traffic from the SGP within the AS. The SGP or
or IPSP then MUST send a Notify message ("Alternate ASP_Active") to IPSP then MUST send a Notify message ("Alternate ASP_Active") to the
the previously active ASP in the AS, and SHOULD stop traffic to/from previously active ASP in the AS and SHOULD stop traffic to/from that
that ASP. The ASP receiving this Notify MUST consider itself now in ASP. The ASP receiving this Notify MUST consider itself now in the
the ASP-INACTIVE state, if it is not already aware of this via ASP-INACTIVE state, if it is not already aware of this via inter-ASP
inter-ASP communication with the Overriding ASP. communication with the Overriding ASP.
In the case of a Loadshare mode AS, reception of an ASP Active In the case of a Loadshare mode AS, receipt of an ASP Active message
message at an SGP or IPSP causes the direction of traffic to the ASP at an SGP or IPSP causes direction of traffic to the ASP sending the
sending the ASP Active message, in addition to all the other ASPs ASP Active message, in addition to all the other ASPs that are
that are currently active in the AS. The algorithm at the SGP for currently active in the AS. The algorithm at the SGP for loadsharing
loadsharing traffic within an AS to all the active ASPs is traffic within an AS to all the active ASPs is implementation
implementation dependent. The algorithm could, for example, be dependent. The algorithm could, for example, be round-robin or based
round-robin or based on information in the Data message (e.g., the on information in the Data message (e.g., the SLS, SCCP SSN, or ISUP
SLS, SCCP SSN, ISUP CIC value). CIC value). An SGP or IPSP, upon receipt of an ASP Active message
An SGP or IPSP, upon reception of an ASP Active message for the first for the first ASP in a Loadshare AS, MAY choose not to direct traffic
ASP in a Loadshare AS, MAY choose not to direct traffic to a newly to a newly active ASP until it determines that there are sufficient
active ASP until it determines that there are sufficient resources to resources to handle the expected load (e.g., until there are "n" ASPs
handle the expected load (e.g., until there are "n" ASPs in state in state ASP-ACTIVE in the AS). In this case, the SGP or IPSP SHOULD
ASP-ACTIVE in the AS). In this case, the SGP or IPSP SHOULD withhold withhold the 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 For the n+k redundancy case, ASPs that are in that AS should
coordinate among themselves the number of active ASPs in the AS, and coordinate among themselves the number of active ASPs in the AS and
should start sending traffic only after n ASPs are active. should start sending traffic only after n ASPs are active. All ASPs
All ASPs within a loadsharing mode AS must be able to process any within a loadsharing mode AS must be able to process any Data message
Data message received for the AS, to accommodate any potential received for the AS, to accommodate any potential failover or
failover or rebalancing of the offered load. rebalancing of the offered load.
In the case of a Broadcast mode AS, reception of an ASP Active In the case of a Broadcast mode AS, receipt of an ASP Active message
message at an SGP or IPSP causes the direction of traffic to the ASP at an SGP or IPSP causes direction of traffic to the ASP sending the
sending the ASP Active message, in addition to all the other ASPs ASP Active message, in addition to all the other ASPs that are
that are currently active in the AS. The algorithm at the SGP for currently active in the AS. The algorithm at the SGP for
broadcasting traffic within an AS to all the active ASPs is a simple broadcasting traffic within an AS to all the active ASPs is a simple
broadcast algorithm, where every message is sent to each of the broadcast algorithm, where every message is sent to each of the
active ASPs. active ASPs.
At start-up or re-start phases, an SGP or IPSP, upon reception of an At startup or restart phases, an SGP or IPSP, upon receipt of an ASP
ASP Active message for the first ASP in a Loadshare AS, SHOULD NOT Active message for the first ASP in a Loadshare AS, SHOULD NOT direct
direct traffic to a newly active ASP until it determines that there traffic to a newly active ASP until it determines that there are
are sufficient resources to handle the expected load (e.g., until sufficient resources to handle the expected load (e.g., until there
there are "n" ASPs in state ASP-ACTIVE in the AS). In this case, the are "n" ASPs in state ASP-ACTIVE in the AS). In this case, the SGP
SGP or IPSP SHOULD withhold the Notify (AS-ACTIVE) until there are or IPSP SHOULD withhold the Notify (AS-ACTIVE) until there are
sufficient resources. sufficient resources.
An SGP or IPSP, upon reception of an ASP Active message for the first An SGP or IPSP, upon receipt 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 ASP-ACTIVE in the AS). In this case, the SGP or IPSP SHOULD withhold
the 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 For the n+k redundancy case, ASPs that are in that AS should
coordinate among themselves the number of active ASPs in the AS, and coordinate among themselves the number of active ASPs in the AS and
should start 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
a unique Correlation Id parameter. The purpose of this Id is to unique Correlation Id parameter. The purpose of this Id is to permit
permit the newly active ASP to synchronize its processing of traffic the newly active ASP to synchronize its processing of traffic in each
in each traffic flow with the other ASPs in the broadcast group. 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 Either of the IPSPs can initiate communication. When an IPSP
an ASP Active, it should mark the peer as ASP-ACTIVE and return an receives an ASP Active, it should mark the peer as ASP-ACTIVE and
ASP Active Ack message. An ASP receiving an ASP Active Ack message return an ASP Active Ack message. An ASP receiving an ASP Active Ack
may mark the peer as ASP-Active, if it is not already in the ASP- message may mark the peer as ASP-Active, if it is not already in the
ACTIVE state. ASP-ACTIVE state.
Alternatively, when using IPSP DE model, an interchange of ASP Active Alternatively, when using the IPSP DE model, an interchange of ASP
messages from each end MUST be performed. Four messages are needed for Active messages from each end MUST be performed. Four messages are
completion. needed 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, or When an ASP wishes to withdraw from receiving traffic within an AS or
the ASP wants to initiate the process of deactivation, the ASP sends the ASP wants to initiate the process of deactivation, the ASP sends
an ASP Inactive message to the SGP or IPSP. an ASP Inactive message to the SGP or IPSP.
An ASP Inactive message MUST always be responded by the peer (although An ASP Inactive message MUST always be responded to by the peer
other messages may be sent in the middle) in the following way: (although other messages may be sent in the middle) in the following
way:
- If the received ASP Inactive message contains a RC parameter and - If the received ASP Inactive message contains an RC parameter
the corresponding RK is defined (by either static configuration and the corresponding RK is defined (by either static
or dynamic registration), the SGP/IPSP MUST respond with an ASP configuration or dynamic registration), the SGP/IPSP MUST
Inactive Ack message. respond with an ASP Inactive Ack message.
- If the received ASP Inactive message contains a RC parameter - If the received ASP Inactive message contains an RC parameter
that is not defined (by either static configuration or dynamic that is not defined (by either static configuration or dynamic
registration), the SGP/IPSP MUST respond with an ERROR message registration), the SGP/IPSP MUST respond with an ERROR message
with Error Code = "Invalid Routing Context". with the Error Code "Invalid Routing Context".
- If the received ASP Inactive message does not contain a RC - If the received ASP Inactive message does not contain an RC
parameter and the RK is defined (by either static configuration parameter and the RK is defined (by either static configuration
or dynamic registration), the SGP/IPSP must turn the ASP/IPSP to or dynamic registration), the SGP/IPSP must turn the ASP/IPSP to
ASP-INACTIVE state in all the ASes it serves and MUST respond ASP-INACTIVE state in all the ASes it serves and MUST respond
with an ASP Inactive Ack message. with an ASP Inactive Ack message.
- If the received ASP Inactive message does not contain a RC - If the received ASP Inactive message does not contain an RC
parameter and the RK is not defined (by either static parameter and the RK is not defined (by either static
configuration or dynamic registration), the SGP/IPSP MUST configuration or dynamic registration), the SGP/IPSP MUST
respond with an ERROR message with Error Code = "No configured respond with an ERROR message with the Error Code "No configured
AS for ASP". AS for ASP".
The action of sending the ASP Inactive message MAY be initiated at the The action of sending the ASP Inactive message MAY be initiated at
ASP by an M-ASP_INACTIVE request primitive from Layer Management or the ASP by an M-ASP_INACTIVE request primitive from Layer Management
MAY be initiated automatically by an M3UA management function. In the or MAY be initiated automatically by an M3UA management function. In
case where an ASP is processing the traffic for more than one the case where an ASP is processing the traffic for more than one
Application Server across a common SCTP association, the ASP Inactive Application Server across a common SCTP association, the ASP Inactive
message contains one or more Routing Contexts to indicate for which message contains one or more Routing Contexts to indicate for which
Application Servers the ASP Inactive message applies. Application Servers the ASP Inactive message applies.
In the case where an ASP Inactive message does not contain a Routing In the case where an ASP Inactive message does not contain a Routing
Context parameter, the receiver must know, via configuration data, Context parameter, the receiver must know, via configuration data,
which Application Servers the ASP is a member and move the ASP to the which Application Servers the ASP is a member of and then move the
ASP-INACTIVE state in all Application Servers. ASP to the ASP-INACTIVE state in all Application Servers.
In the case of an Override mode AS, where another ASP has already In the case of an Override mode AS, where another ASP has already
taken over the traffic within the AS with an ASP Active ("Override") 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 to be in ASP-INACTIVE state by the SGP. An ASP Inactive
Ack message is sent to the ASP, after ensuring that all traffic is Ack message is sent to the ASP, after ensuring that all traffic is
stopped to the ASP. stopped to the ASP.
In the case of a Loadshare mode AS, the SGP moves the ASP to the In the case of a Loadshare mode AS, the SGP moves the ASP to the
ASP-INACTIVE state and the AS traffic is reallocated across the ASP-INACTIVE state, and the AS traffic is reallocated across the
remaining ASPs in the state ASP-ACTIVE, as per the loadsharing remaining ASPs in the state ASP-ACTIVE, as per the loadsharing
algorithm currently used within the AS. A Notify message algorithm currently used within the AS. A Notify message
("Insufficient ASP resources active in AS") MAY be sent to all ("Insufficient ASP resources active in AS") MAY be sent to all
inactive ASPs, if required. An ASP Inactive Ack message is sent to inactive ASPs, if required. An ASP Inactive Ack message is sent to
the ASP after all traffic is halted and Layer Management is informed the ASP after all traffic is halted, and Layer Management is informed
with an M-ASP_INACTIVE indication primitive. with an M-ASP_INACTIVE indication primitive.
In the case of a Broadcast mode AS, the SGP moves the ASP to the In the case of a Broadcast mode AS, the SGP moves the ASP to the
ASP-INACTIVE state and the AS traffic is broadcast only to the ASP-INACTIVE state, and the AS traffic is broadcast only to the
remaining ASPs in the state ASP-ACTIVE. A Notify message remaining ASPs in the state ASP-ACTIVE. A Notify message
("Insufficient ASP resources active in AS") MAY be sent to all ("Insufficient ASP resources active in AS") MAY be sent to all
inactive ASPs, if required. An ASP Inactive Ack message is sent to inactive ASPs, if required. An ASP Inactive Ack message is sent to
the ASP after all traffic is halted and Layer Management is informed the ASP after all traffic is halted, and Layer Management is informed
with an M-ASP_INACTIVE indication primitive. with an M-ASP_INACTIVE indication primitive.
Multiple ASP Inactive Ack messages MAY be used in response to an ASP Multiple ASP Inactive Ack messages MAY be used in response to an ASP
Inactive message containing multiple Routing Contexts, allowing the Inactive message containing multiple Routing Contexts, allowing the
SGP or IPSP to independently acknowledge for different (sets of) SGP or IPSP to independently acknowledge for different (sets of)
Routing Contexts. The SGP or IPSP sends an Error message ("Invalid Routing Contexts. The SGP or IPSP sends an Error message ("Invalid
Routing Context") message for each invalid or unconfigured Routing Routing Context") message for each invalid or unconfigured Routing
Context 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 The SGP MUST send an ASP Inactive Ack message in response to a
received ASP Inactive message from the ASP and the ASP is already received ASP Inactive message from the ASP; the ASP is already marked
marked as ASP-INACTIVE at the SGP. as ASP-INACTIVE at the SGP.
At the ASP, the ASP Inactive Ack message received is not At the ASP, the ASP Inactive Ack message received is not
acknowledged. Layer Management is informed with an M-ASP_INACTIVE acknowledged. Layer Management is informed with an M-ASP_INACTIVE
confirm primitive. If the ASP receives an ASP Inactive Ack without confirm primitive. If the ASP receives an ASP Inactive Ack without
having sent an ASP Inactive message, the ASP should now consider having sent an ASP Inactive message, the ASP should now consider
itself as in the ASP-INACTIVE state. If the ASP was previously in itself to be in the ASP-INACTIVE state. If the ASP was previously in
the ASP-ACTIVE state, the ASP should then initiate procedures to the ASP-ACTIVE state, the ASP should then initiate procedures to
return itself to its previous state. return itself to its previous state.
When the ASP sends an ASP Inactive message it starts timer T(ack). When the ASP sends an ASP Inactive message, it starts the timer
If the ASP does not receive a response to an ASP Inactive message T(ack). If the ASP does not receive a response to an ASP Inactive
within T(ack), the ASP MAY restart T(ack) and resend ASP Inactive message within T(ack), the ASP MAY restart T(ack) and resend ASP
messages until it receives an ASP Inactive Ack message. T(ack) is Inactive messages until it receives an ASP Inactive Ack message.
provisionable, with a default of 2 seconds. Alternatively, T(ack) is provisionable, with a default of 2 seconds. Alternatively,
retransmission of ASP Inactive messages MAY be put under control of retransmission of ASP Inactive messages MAY be put under 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 an 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 ASP- If no other ASPs in the Application Server are in the state ASP-
ACTIVE, the SGP MUST send a Notify message ("AS-Pending") to all of ACTIVE, the SGP MUST send a Notify message ("AS-Pending") to all ASPs
the ASPs in the AS which are in the state ASP-INACTIVE. The SGP in the AS that are in the state ASP-INACTIVE. The SGP SHOULD start
SHOULD start buffering the incoming messages for T(r) seconds, after buffering the incoming messages for T(r) seconds, after which
which messages MAY be discarded. T(r) is configurable by the network messages MAY be discarded. T(r) is configurable by the network
operator. If the SGP receives an ASP Active message from an ASP in operator. If the SGP receives an ASP Active message from an ASP in
the AS before expiry of T(r), the buffered traffic is directed to the AS before expiry of T(r), the buffered traffic is directed to
that ASP and the timer is cancelled. If T(r) expires, the AS is moved that ASP, and the timer is cancelled. If T(r) expires, the AS is
to the AS-INACTIVE state. moved 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 after an ASP Inactive or ASP Inactive Ack message has been received
from it. from it.
Alternatively, when using IPSP DE model, an interchange of ASP Alternatively, when using IPSP DE model, an interchange of ASP
Inactive messages from each end MUST be performed. Four messages are Inactive messages from each end MUST be performed. Four messages are
needed for completion. needed 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 AS indication primitive. The Notify message must be sent whether the AS
state change was a result of an ASP failure or reception of an ASP state change was a result of an ASP failure or receipt of an ASP
State management (ASPSM) / ASP Traffic Management (ASPTM) message. State management (ASPSM) / ASP Traffic Management (ASPTM) message.
In the second case, the Notify message MUST be sent after any related In the second case, the Notify message MUST be sent after any related
acknowledgement messages (e.g., ASP Up Ack, ASP Down Ack, ASP Active acknowledgement messages (e.g., ASP Up Ack, ASP Down Ack, ASP Active
Ack, or ASP Inactive Ack). Ack, or ASP Inactive Ack).
When an ASP moves from ASP-DOWN to ASP-INACTIVE within a particular When an ASP moves from ASP-DOWN to ASP-INACTIVE within a particular
AS, a Notify message SHOULD be sent, by the ASP-UP receptor, after AS, a Notify message SHOULD be sent, by the ASP-UP receptor, after
sending the ASP-UP-ACK, in order to inform the ASP of the current AS sending the ASP-UP-ACK, in order to inform the ASP of the current AS
state. state.
skipping to change at page 80, line 43 skipping to change at page 89, line 20
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 active. explicitly compel the ASP(s) receiving the message to become active.
The ASPs remain in control of what (and when) traffic action is The ASPs remain in control of what (and when) traffic action 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 Notify works in the same manner as in the SG-AS case. One of the
IPSPs can send this message to any remote IPSP that is not in the IPSPs can send this message to any remote IPSP that is not in the
ASP-DOWN 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
message, the M3UA peer MUST respond with a Heartbeat Ack message. Heartbeat 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 disconnected communication if it is configured as the client for the 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 sender. The contents may be used, for example, to support a
Heartbeat sequence algorithm (to detect missing Heartbeats), and/or a Heartbeat sequence algorithm (to detect missing Heartbeats), and/or a
timestamp mechanism (to evaluate delays). timestamp mechanism (to evaluate delays).
Note: Heartbeat related events are not shown in Figure 3 "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 Application Server using the REG REQ message. A Routing Key
parameter in the REG REQ message specifies the parameters associated parameter in the REG REQ message specifies the parameters associated
with the Routing Key. with the Routing Key.
The SGP examines the contents of the received Routing Key parameter The SGP examines the contents of the received Routing Key parameter
and 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 received Routing Key matches an existing SGP Routing Key entry and
the ASP is not currently included in the list of ASPs for the related 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 request, and a Registration Result "Successfully Registered". A
unique Routing Context value assigned to the SGP Routing Key is unique Routing Context value assigned to the SGP Routing Key is
skipping to change at page 82, line 12 skipping to change at page 90, line 41
is implementation dependent but must be guaranteed to be unique for is implementation dependent but must be guaranteed to be unique for
each 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 If the SGP does not support the registration procedure, the SGP
returns an Error message to the ASP, with an error code of returns an Error message to the ASP, with an error code of
"Unsupported Message Class". "Unsupported Message Class".
If the SGP determines that the received Routing Key data is invalid, If the SGP determines that the received Routing Key data is invalid,
or 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", or "Error - Invalid
Appearance" as appropriate. Network Appearance", as appropriate.
If the SGP determines that the requested RK partially, but not If the SGP determines that the requested RK partially, but not
exactly, matches an existing RK, and that an incoming signalling exactly, matches an existing RK, and that an incoming signalling
message received at an SGP could possibly match both the requested and message received at an SGP could possibly match both the requested
the existing RK, the SGP returns a Registration Response message to and the existing RK, the SGP returns a Registration Response message
the ASP, with a Registration Status of "Error - "Cannot Support Unique to the ASP, with a Registration Status of "Error - "Cannot Support
Routing. An incoming signalling message received at an SGP should not Unique Routing". An incoming signalling message received at an SGP
match against more than one Routing Key. should not match against more than one Routing Key.
If the SGP determines that the received RK was already registered, If the SGP determines that the received RK was already registered,
fully and exactly, either statically or dynamically, by the sending fully and exactly, either statically or dynamically, by the sending
ASP, the SGP returns a Registration Response message to the ASP, ASP, the SGP returns a Registration Response message to the ASP,
containing a Registration Result "Error - Routing Key Already containing a Registration Result "Error - Routing Key Already
Registered ". This error applies whether the sending ASP/IPSP is in Registered ". This error applies whether the sending ASP/IPSP is in
ASP-ACTIVE or ASP-INACTIVE for the corresponding AS. For this error ASP-ACTIVE or ASP-INACTIVE for the corresponding AS. For this error
code, the RC field in the Registration Response message MUST be code, the RC field in the Registration Response message MUST be
populated with the actual value of RC in SGP corresponding to the populated with the actual value of RC in SGP corresponding to the
specified RK in the Registration Request message. specified RK in the Registration Request message.
An ASP MAY request modification of an existing Routing Key by An ASP MAY request modification of an existing Routing Key by
including a Routing Context parameter in a Registration Request including a Routing Context parameter in a Registration Request
message. Upon receipt of a Registration Request message containing a message. Upon receipt of a Registration Request message containing a
Routing Context, if the SGP determines that the Routing Context Routing Context, if the SGP determines that the Routing Context
applies to an existing Routing Key, the SGP MAY adjust the existing applies to an existing Routing Key, the SGP MAY adjust the existing
Routing Key to match the new information provided in the Routing Key Routing Key to match the new information provided in the Routing Key
parameter. A Registration Response "ERR Routing Key Change Refused" parameter. A Registration Response "ERR Routing Key Change Refused"
is returned if the SGP does not support this re-registration procedure is returned if the SGP does not support this re-registration
or RC does not exist. Otherwise, a Registration Response "Successfully procedure or RC does not exist. Otherwise, a Registration Response
Registered" is returned. "Successfully Registered" is returned.
If the SGP does not authorize an otherwise valid registration request, If the SGP does not authorize an otherwise valid registration
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 that the SGP does not support dynamic configuration, the
returns a Registration Response message to the ASP, containing a SGP 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 exist and that the SGP supports dynamic configuration but does not
the capacity to add new Routing Key and Application Server entries, have the capacity to add new Routing Key and Application Server
the SGP returns a Registration Response message to the ASP, entries, the SGP returns a Registration Response message to the ASP,
containing a Registration Result "Error - Insufficient Resources". containing a Registration Result "Error - Insufficient Resources".
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 requires that exist, and the SGP supports dynamic configuration but requires that
the Routing Key first be manually provisioned at the SGP, the SGP the Routing Key first be manually provisioned at the SGP, 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 one or more of the Routing Key parameters If an SGP determines that one or more of the Routing Key parameters
are not supported for the purpose of creating new Routing Key entries, are not supported for the purpose of creating new Routing Key
the SGP returns a Registration Response message to the ASP, containing entries, the SGP returns a Registration Response message to the ASP,
a Registration Result "Error - Unsupported RK parameter field. containing a Registration Result "Error - Unsupported RK parameter
field".
A Registration Response "Error - Unsupported Traffic Handling Mode" A Registration Response "Error - Unsupported Traffic Handling Mode"
is returned if the Routing Key in the REG REQ contains an Traffic is returned if the Routing Key in the REG REQ contains an Traffic
Handling Mode that is inconsistent with the presently configured mode Handling Mode that is inconsistent with the presently configured mode
for the matching Application Server. for the matching Application Server.
An ASP MAY register multiple Routing Keys at once by including a An ASP MAY register multiple Routing Keys at once by including a
number of Routing Key parameters in a single REG REQ message. The number of Routing Key parameters in a single REG REQ message. The
SGP MAY respond to each registration request in a single REG RSP SGP MAY respond to each registration request in a single REG RSP
message, indicating the success or failure result for each Routing message, indicating the success or failure result for each Routing
Key in a separate Registration Result parameter. Alternatively the Key in a separate Registration Result parameter. Alternatively the
SGP MAY 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 of which it is a
before attempting to move to the ASP-Down state. member before attempting to move to the ASP-Down state.
The SGP examines the contents of the received Routing Context The SGP examines the contents of the received Routing Context
parameter and validates that the ASP is currently registered in the parameter and validates that the ASP is currently registered in the
Application Server(s) related to the included Routing Context(s). If Application Server(s) related to the included Routing Context(s). If
validated, the ASP is deregistered as an ASP in the related validated, the ASP is deregistered as an ASP in the related
Application Server. Application Server.
The deregistration procedure does not necessarily imply the deletion The deregistration procedure does not necessarily imply the deletion
of Routing Key and Application Server configuration data at the SG. of Routing Key and Application Server configuration data at the SG.
skipping to change at page 84, line 21 skipping to change at page 93, line 11
RSP message to the requesting ASP. The result of the deregistration RSP message to the requesting ASP. The result of the deregistration
is found in the Deregistration Result parameter, indicating success is found in the Deregistration Result parameter, indicating success
or failure with cause. or failure with cause.
An ASP MAY deregister multiple Routing Contexts at once by including An ASP MAY deregister multiple Routing Contexts at once by including
a number of Routing Contexts in a single DEREG REQ message. The SGP a number of Routing Contexts in a single DEREG REQ message. The SGP
MAY respond to each deregistration request in a single DEREG RSP MAY respond to each deregistration request in a single DEREG RSP
message, indicating the success or failure result for each Routing message, indicating the success or failure result for each Routing
Context in a 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 Registration/Deregistration procedures work in the IPSP cases in
the same way as in AS-SG cases. An IPSP may register an RK in the the same way as in AS-SG cases. An IPSP may register an RK in the
remote IPSP. An IPSP is responsible for deregistering the RKs that it remote IPSP. An IPSP is responsible for deregistering the RKs that
has 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
Destination SS7 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 primitive from the nodal interworking function at an SGP, the SGP
M3UA layer will send a corresponding SS7 Signalling Network M3UA layer will send a corresponding SS7 Signalling Network
Management (SSNM) DUNA, DAVA, SCON, or DUPU message (see Section 3.4) Management (SSNM) DUNA, DAVA, SCON, or DUPU message (see Section 3.4)
to the M3UA peers at concerned ASPs. The M3UA layer must fill in to the M3UA peers at concerned ASPs. The M3UA layer must fill in
various fields of the SSNM messages consistently with the information various fields of the SSNM messages consistently with the information
received in the 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.
For the particular case that an ASP becomes active for an AS and For the particular case that an ASP becomes active for an AS and
destinations normally accessible to the AS are inaccessible, destinations normally accessible to the AS are inaccessible,
restricted or congested, the SG MAY send DUNA, DRST or SCON messages restricted, or congested, the SG MAY send DUNA, DRST, or SCON
for the inaccessible, restricted or congested destinations to the ASP messages for the inaccessible, restricted, or congested destinations
newly active for the AS to prevent the ASP from sending traffic for to the ASP newly active for the AS to prevent the ASP from sending
destinations that it might otherwise not know that are inaccessible, traffic for destinations that it might not otherwise know that are
restricted or congested. For the newly activating ASP from which the inaccessible, restricted, or congested. For the newly activating ASP
SGP has received an ASP Active message, these DUNA, DRST and SCON from which the SGP has received an ASP Active message, these DUNA,
messages MAY be sent before sending the ASP Active Ack that completes DRST, and SCON messages MAY be sent before sending the ASP Active Ack
the activation procedure. that completes the activation procedure.
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
4.5.2.1 Single SG Configurations 4.5.2.1. Single SG Configurations
At an ASP, upon receiving an SS7 Signalling Network Management (SSNM) At an ASP, upon receiving an SS7 Signalling Network Management (SSNM)
message from the remote M3UA Peer, the M3UA layer invokes the message from the remote M3UA Peer, the M3UA layer invokes the
appropriate primitive indications to the resident M3UA-Users. Local appropriate primitive indications to the resident M3UA-Users. Local
management is informed. management is informed.
In the case where a local event has caused the unavailability or In the case where a local event has caused the unavailability or
congestion status of SS7 destinations, the M3UA layer at the ASP congestion status of SS7 destinations, the M3UA layer at the ASP
SHOULD pass up appropriate indications in the primitives to the M3UA SHOULD pass up appropriate indications in the primitives to the M3UA
User, as though equivalent SSNM messages were received. For example, User, as though equivalent SSNM messages were received. For example,
the loss of an SCTP association to an SGP may cause the the loss of an SCTP association to an SGP may cause the
unavailability of a set of SS7 destinations. MTP-PAUSE indication unavailability of a set of SS7 destinations. MTP-PAUSE indication
primitives to the M3UA User are appropriate. primitives to the M3UA User are appropriate.
4.5.2.2 Multiple SG Configurations 4.5.2.2. Multiple SG Configurations
At an ASP, upon receiving a Signalling Network Management message At an ASP, upon receiving a Signalling Network Management message
from the remote M3UA Peer, the M3UA layer updates the status of the from the remote M3UA Peer, the M3UA layer updates the status of the
affected route(s) via the originating SG and determines, whether or affected route(s) via the originating SG and determines whether or
not the overall availability or congestion status of the effected not the overall availability or congestion status of the affected
destination(s) has changed. If so, the M3UA layer invokes the destination(s) has changed. If so, the M3UA layer invokes the
appropriate primitive indications to the resident M3UA-Users. Local appropriate primitive indications to the resident M3UA-Users. Local
management is informed. management is informed.
Implementation Note: To accomplish this, the M3UA layer at an ASP Implementation Note: To accomplish this, the M3UA layer at an ASP
maintains the status of routes via the SG, much like an MTP3 layer maintains the status of routes via the SG, much like an MTP3 layer
maintains route-set status. maintains route-set status.
4.5.3 ASP Auditing 4.5.3. ASP Auditing
An ASP may optionally initiate an audit procedure to enquire of an An ASP may optionally initiate an audit procedure to enquire of an
SGP the availability and, if the national congestion method with SGP the availability and (if the national congestion method with
multiple congestion levels and message priorities is used, congestion multiple congestion levels and message priorities is used) congestion
status of an SS7 destination or set of destinations. A Destination status of an SS7 destination or set of destinations. A Destination
Audit (DAUD) message is sent from the ASP to the SGP, requesting the
Audit (DAUD) message is sent from the ASP to the SGP requesting the
current availability and congestion status of one or more SS7 current availability and congestion status of one or more SS7
Destination Point Codes. Destination Point Codes.
The DAUD message MAY be sent unsequenced. The DAUD MAY be sent by the The DAUD message MAY be sent unsequenced. The DAUD MAY be sent by
ASP in the following cases: the ASP in the following cases:
- Periodic. A Timer originally set upon reception of a DUNA, SCON - Periodic. A Timer originally set upon receipt of a DUNA, SCON,
or DRST message has expired without a subsequent or DRST message has expired without a subsequent DAVA, DUNA,
DAVA, DUNA, SCON or DRST message updating the SCON, or DRST message updating the availability/congestion
availability/congestion status of the affected status of the affected Destination Point Codes. The Timer is
Destination Point Codes. The Timer is reset upon reset upon issuing a DAUD. In this case, the DAUD is sent to
issuing a DAUD. In this case the DAUD is sent to the the SGP that originally sent the SSNM message.
SGP that originally sent the SSNM message.
- Isolation. The ASP is newly ASP-ACTIVE or has been - Isolation. The ASP is newly ASP-ACTIVE or has been isolated
isolated from an SGP for an extended period. The ASP from an SGP for an extended period. The ASP MAY request the
MAY request the availability/congestion status of one availability/congestion status of one or more SS7 destinations
or more SS7 destinations to which it expects to to which it expects to communicate.
communicate.
IMPLEMENTATION NOTE: In the first of the cases above, the auditing Implementation Note: In the first of the cases above, the auditing
procedure must not be invoked for the case of a received SCON procedure must not be invoked for the case of a received SCON
message message containing a congestion level value of "no congestion" or
containing a congestion level value of "no congestion" or undefined" "undefined" (i.e., congestion Level = "0").