draft-ietf-sigtran-m3ua-08.txt   draft-ietf-sigtran-m3ua-09.txt 
Network Working Group Greg Sidebottom Network Working Group Greg Sidebottom
INTERNET-DRAFT Guy Mousseau INTERNET-DRAFT gregside consulting
Javier Pastor-Balb▀s
Ian Rytina
Ericsson
Guy Mousseau
Nortel Networks Nortel Networks
Lyndon Ong Lyndon Ong
Ciena Ciena
Ian Rytina
Ericsson
Hanns Juergen Schwarzbauer Hanns Juergen Schwarzbauer
Siemens Siemens
Klaus Gradischnig Klaus Gradischnig
NeuStar NeuStar
Ken Morneault Ken Morneault
Cisco Cisco
Mallesh Kalla Mallesh Kalla
Telcordia Telcordia
Normand Glaude Normand Glaude
Performance Technologies Performance Technologies
Brian Bidulock Brian Bidulock
OpenSS7 OpenSS7
John Loughney
Nokia
Expires in six months Jul 2001 Expires in six months Oct 2001
SS7 MTP3-User Adaptation Layer (M3UA) SS7 MTP3-User Adaptation Layer (M3UA)
<draft-ietf-sigtran-m3ua-08.txt> <draft-ietf-sigtran-m3ua-09.txt>
Status of This Memo Status of This Memo
This document is an Internet-Draft and is in full conformance with all This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 of RFC 2026. Internet-Drafts are working provisions of Section 10 of RFC 2026. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, and documents of the Internet Engineering Task Force (IETF), its areas, and
its working groups. Note that other groups may also distribute working its working groups. Note that other groups may also distribute working
documents as Internet-Drafts. documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference material time. It is inappropriate to use Internet-Drafts as reference material
or to cite them other than as 'work in progress.' or to cite them other than as 'work in progress.'
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/1id-abstracts.html http://www.ietf.org/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html
To learn the current status of any Internet-Draft, please check the To learn the current status of any Internet-Draft, please check the
'1id-abstracts.txt' listing contained in the Internet- Drafts Shadow '1id-abstracts.txt' listing contained in the Internet- Drafts Shadow
Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe),
munnari.oz.au (Pacific Rim), ftp.ietf.org (US East Coast), or munnari.oz.au (Pacific Rim), ftp.ietf.org (US East Coast), or
ftp.isi.edu (US West Coast). ftp.isi.edu (US West Coast).
Abstract Abstract
This Internet Draft defines a protocol for supporting the transport of This Internet Draft defines a protocol for supporting the transport of
skipping to change at page 3, line 12 skipping to change at page 3, line 12
the SG receives SS7 signalling over a standard SS7 interface using the the SG receives SS7 signalling over a standard SS7 interface using the
SS7 Message Transfer Part (MTP) to provide transport. SS7 Message Transfer Part (MTP) to provide transport.
TABLE OF CONTENTS TABLE OF CONTENTS
1. Introduction.......................................................4 1. Introduction.......................................................4
1.1 Scope.........................................................4 1.1 Scope.........................................................4
1.2 Terminology...................................................4 1.2 Terminology...................................................4
1.3 M3UA Overview.................................................6 1.3 M3UA Overview.................................................6
1.4 Functional Areas.............................................12 1.4 Functional Areas.............................................12
1.5 Sample Configurations........................................21 1.5 Sample Configurations........................................20
1.6 Definition of M3UA Boundaries................................24 1.6 Definition of M3UA Boundaries................................23
2. Conventions.......................................................28 2. Conventions.......................................................28
3. M3UA Protocol Elements............................................28 3. M3UA Protocol Elements............................................28
3.1 Common Message Header........................................28 3.1 Common Message Header........................................28
3.2 Variable-Length Parameter....................................31 3.2 Variable Length Parameter....................................31
3.3 Transfer Messages............................................32 3.3 Transfer Messages............................................33
3.4 SS7 Signalling Network management (SSNM) Messages............35 3.4 SS7 Signalling Network management (SSNM) Messages............36
3.5 ASP State Maintenance (ASPM) Messages........................43 3.5 ASP State Maintenance (ASPM) Messages........................45
3.6 Routing Key Management (RKM) Messages........................46 3.6 Routing Key Management (RKM) Messages........................48
3.7 ASP Traffic Maintenance (ASPTM) Messages.....................55 3.7 ASP Traffic Maintenance (ASPTM) Messages.....................58
3.8 Management(MGMT) Messages....................................60 3.8 Management(MGMT) Messages....................................62
4. Procedures........................................................64 4. Procedures........................................................66
4.1 Procedures to Support the M3UA-User and Layer Management 4.1 Procedures to Support the M3UA-User .........................66
Layers.......................................................64 4.2 Procedures to Support the Management of SCTP Associations ...69
4.2 Procedures to Support the Management of SCTP Associations 4.3 AS and ASP State Maintenance.................................69
with M3UA Peers..............................................67 4.4 Routing Key Management Procedures............................81
4.3 Procedures to support the Unavailability or Congestion 4.5 Procedures to Support the Availability or Congestion Status
Status of SS7 Destinations...................................81 of SS7 Destination...........................................83
4.4 MTP3 Restart.................................................83 4.6 MTP3 Restart.................................................86
5. Examples of M3UA Procedures.......................................84 5. Examples of M3UA Procedures.......................................86
5.1 Establishment of Association and Traffic 5.1 Establishment of Association and Traffic
Between SGs and ASPs.........................................84 Between SGs and ASPs.........................................86
5.2 ASP traffic Fail-over Examples...............................89 5.2 ASP traffic Failover Examples................................91
5.3 Normal Withdrawal of an ASP from an Application Server 5.3 Normal Withdrawal of an ASP from an Application Server
and Tear-down of an Association..............................90 and Teardown of an Association...............................92
5.4.M3UA/MTP3-User Boundary Examples.............................91 5.4.M3UA/MTP3-User Boundary Examples.............................93
6. Security..........................................................95 6. Security..........................................................97
6.1 Introduction.................................................95 6.1 Introduction.................................................97
6.2 Threats......................................................95 6.2 Threats......................................................97
6.3 Protecting Confidentiality...................................95 6.3 Protecting Confidentiality...................................98
7. IANA Considerations...............................................96 7. IANA Considerations...............................................98
7.1 SCTP Payload Protocol Identifier.............................96 7.1 SCTP Payload Protocol Identifier.............................98
7.2 M3UA Protocol Extensions.....................................96 7.2 M3UA Port Number.............................................98
8. Acknowledgements..................................................97 7.3 M3UA Protocol Extensions.....................................99
9. References........................................................97 8. Acknowledgements.................................................100
10. Bibliography....................................................99 9. References.......................................................100
11. Author's Addresses..............................................99 11. Author's Addresses.............................................102
1. Introduction 1. Introduction
1.1 Scope 1.1 Scope
There is a need for Switched Circuit Network (SCN) signalling protocol There is a need for Switched Circuit Network (SCN) signalling protocol
delivery from an SS7 Signalling Gateway (SG) to a Media Gateway delivery from an SS7 Signalling Gateway (SG) to a Media Gateway
Controller (MGC) or IP-resident Database as described in the Framework Controller (MGC) or IP-resident Database as described in the Framework
Architecture for Signalling Transport [1]. The delivery mechanism Architecture for Signalling Transport [1]. The delivery mechanism
SHOULD meet the following criteria: 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, SCCP, TUP, etc.) ISUP, SCCP, TUP, etc.)
* Support for the seamless operation of MTP3-User protocol peers * Support for the seamless operation of MTP3-User protocol peers
* Support for the management of SCTP transport associations and * Support for the management of SCTP transport associations and
traffic between an SG and one or more MGCs or IP-resident Databases traffic between an SG and one or more MGCs or IP-resident Databases
* Support for MGC or IP-resident Database process fail-over 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 MTP3 In simplistic transport terms, the SG will terminate SS7 MTP2 and MTP3
protocol layers and deliver ISUP, SCCP and/or any other MTP3-User protocol layers and deliver ISUP, SCCP and/or any other MTP3-User
protocol messages, as well as certain MTP network management events, protocol messages, as well as certain MTP network management events,
over SCTP transport associations to MTP3-User peers in MGCs or IP- over SCTP transport associations to MTP3-User peers in MGCs or IP-
resident Databases. resident Databases.
skipping to change at page 4, line 44 skipping to change at page 4, line 44
Key. An example of an Application Server is a virtual switch element Key. An example of an Application Server is a virtual switch element
handling all call processing for a unique range of PSTN trunks, handling all call processing for a unique range of PSTN trunks,
identified by an SS7 SIO/DPC/OPC/CIC_range. Another example is a identified by an SS7 SIO/DPC/OPC/CIC_range. Another example is a
virtual database element, handling all HLR transactions for a virtual database element, handling all HLR transactions for a
particular SS7 DPC/OPC/SCCP_SSN combination. The AS contains a set of particular SS7 DPC/OPC/SCCP_SSN combination. The AS contains a set of
one or more unique Application Server Processes, of which one or more one or more unique Application Server Processes, of which one or more
is normally actively processing traffic. Note that there is a 1:1 is normally actively processing traffic. Note that there is a 1:1
relationship between an AS and a Routing Key. relationship between an AS and a Routing Key.
Application Server Process (ASP) - A process instance of an Application Application Server Process (ASP) - A process instance of an Application
Server. An Application Server Process serves as an active or back-up Server. An Application Server Process serves as an active or backup
process of an Application Server (e.g., part of a distributed virtual process of an Application Server (e.g., part of a distributed virtual
switch or database). Examples of ASPs are processes (or process switch or database). Examples of ASPs are processes (or process
instances) of MGCs, IP SCPs or IP HLRs. An ASP contains an SCTP end- instances) of MGCs, IP SCPs or IP HLRs. An ASP contains an SCTP
point and may be configured to process signalling traffic within more endpoint and may be configured to process signalling traffic within
than one Application Server. more than one Application Server.
Association - An association refers to an SCTP association. The Association - An association refers to an SCTP association. The
association provides the transport for the delivery of MTP3-User association provides the transport for the delivery of MTP3-User
protocol data units and M3UA adaptation layer peer messages. protocol data units and M3UA adaptation layer peer messages.
IP Server Process (IPSP) - A process instance of an IP-based IP Server Process (IPSP) - A process instance of an IP-based
application. An IPSP is essentially the same as an ASP, except that it application. An IPSP is essentially the same as an ASP, except that it
uses M3UA in a point-to-point fashion. Conceptually, an IPSP does not uses M3UA in a point-to-point fashion. Conceptually, an IPSP does not
use the services of a Signalling Gateway. use the services of a Signalling Gateway.
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, back-up, load-sharing or broadcast Gateway. It serves as an active, backup, loadsharing or broadcast
process of a Signalling Gateway. process of a Signalling Gateway.
Signalling Gateway - An SG is a signaling agent that receives/sends SCN Signalling Gateway - An SG is a signaling agent that receives/sends SCN
native signaling at the edge of the IP network [1]. An SG appears to native signaling at the edge of the IP network [1]. An SG appears to
the SS7 network as an SS7 Signalling Point. An SG contains a set of one the SS7 network as an SS7 Signalling Point. An SG contains a set of
or more unique Signalling Gateway Processes, of which one or more is one or more unique Signalling Gateway Processes, of which one or more
normally actively processing traffic. Where an SG contains more than is normally actively processing traffic. Where an SG contains more
one SGP, the SG is a logical entity and the contained SGPs might than one SGP, the SG is a logical entity and the contained SGPs are
typically be coordinated into a single management view to the SS7 assumed to be coordinated into a single management view to the SS7
network and to the supported Application Servers. 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.
Routing Key: A Routing Key describes a set of SS7 parameters and Routing Key: A Routing Key describes a set of SS7 parameters and
parameter values that uniquely define the range of signalling traffic parameter values that uniquely define the range of signalling traffic
to be handled by a particular Application Server. Parameters within the to be handled by a particular Application Server. Parameters within the
Routing Key cannot extend across more than a single Signalling Point Routing Key cannot extend across more than a single Signalling Point
Management Cluster. Management Cluster.
Routing Context - A value that uniquely identifies a Routing Key. Routing Context - A value that uniquely identifies a Routing Key.
Routing Context values are either configured using a configuration Routing Context values are either configured using a configuration
management interface, or by using the routing key management procedures management interface, or by using the routing key management procedures
defined in this document. defined in this document.
Fail-over - The capability to re-route signalling traffic as required Failover - The capability to reroute signalling traffic as required
to an alternate Application Server Process, or group of ASPs, within an to an alternate Application Server Process, or group of ASPs, within an
Application Server in the event of failure or unavailability of a Application Server in the event of failure or unavailability of a
currently used Application Server Process. Fail-over also applies upon currently used Application Server Process. Failover also applies upon
the return to service of a previously unavailable Application Server the return to service of a previously unavailable Application Server
Process. Process.
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). SPMCs are used to aggregate the entity (Signalling Point) in one specific Network Appearance. SPMCs
availability, congestion, and user part status of an MTP entity are used to aggregate the availability, congestion, and user part status
(Signalling Point) that is distributed in the IP domain, for the purpose of an MTP entity (Signalling Point) that is distributed in the IP domain,
of supporting MTP3 management procedures towards the SS7 network. In for the purpose of supporting MTP3 management procedures
some
cases, the SG itself may also be a member of the SPMC. In this case, towards the SS7 network. In some cases, the SG itself may also be a
the SG availability/congestion/User_Part status should also be taken member of the SPMC. In this case, the SG availability /congestion
into account when considering any supporting MTP3 management actions. /User_Part status should also be taken into account when considering any
supporting MTP3 management actions.
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 uniquely identifies an SS7 Network Appearance - The Network Appearance is a M3UA local reference
entity (Point Code) into an SS7 network, as presented by the SG. It is shared by SG and AS (typically an integer) that together with an
used for the purposes of logically separating the signalling traffic Signaling Point Code uniquely identifies an SS7 node by indicating
between the SG and the Application Server Processes over a common SCTP the specific SS7 network it belongs to. It can be used to distinguish
association. This partitioning is necessary where an SG is logically between signalling traffic associated with different networks being
partitioned to appear as end node elements in multiple separate SS7 sent between the SG and the ASP over a common SCTP association. An
networks, in which case there is a separate network appearance for each example scenario is where an SG appears as an element in multiple
point code in the SS7 networks. It is also necessary when an SG is separate national SS7 networks and the same Signaling Point Code
configured as an STP hosting multiple point codes, or when configured value may be reused in different networks.
as multiple end nodes within the same network, in which case each point
code is a separate network appearance.between the SG and the
Application Server Processes over a common SCTP Association. An
example is where an SG is logically partitioned to appear as an element
in four separate national SS7 networks. A Network Appearance
implicitly defines the SS7 Point Code(s), Network Indicator and MTP3
protocol type/variant/version used within a separate SS7 network.
Network Byte Order: Most significant byte first, a.k.a Big Endian. Network Byte Order: Most significant byte first, a.k.a Big Endian.
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.
Host - The computing platform that the process (SGP, ASP or IPSP) is Host - The computing platform that the process (SGP, ASP or IPSP) is
running on. running on.
Stream - A stream refers to an SCTP stream; a uni-directional logical Stream - A stream refers to an SCTP stream; a unidirectional logical
channel established from one SCTP endpoint to another associated SCTP channel established from one SCTP endpoint to another associated SCTP
endpoint, within which all user messages are delivered in-sequence endpoint, within which all user messages are delivered in-sequence
except for those submitted to the un-ordered delivery service. except for those submitted to the unordered delivery service.
1.3 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 [1] uses multiple components, including a common transport over IP [1] 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 User. any protocol layer that is identified to the MTP Level 3 as an MTP
The list of these protocol layers include, but is not limited to, ISDN User. The list of these protocol layers include, but is not limited
User Part (ISUP) [2,3,4], Signalling Connection Control Part (SCCP)
[5,6,7] and Telephone User Part (TUP) [8]. TCAP [9,10,11] or RANAP [12] to, ISDN User Part (ISUP) [2,3,4], Signalling Connection Control Part
messages are transferred transparently by the M3UA protocol as SCCP (SCCP) [5,6,7] and Telephone User Part (TUP) [8]. TCAP [9,10,11] or
payload, as they are SCCP-User protocols. RANAP [12] messages are transferred transparently by the M3UA 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) [13] as the underlying reliable common Transmission Protocol (SCTP) [13] as the underlying reliable common
signalling transport protocol. This is to take advantage of various signalling transport protocol. This is to take advantage of various
SCTP features such as: SCTP features such as:
- Explicit packet-oriented delivery (not stream-oriented), - Explicit packet-oriented delivery (not stream-oriented),
- Sequenced delivery of user messages within multiple streams, - Sequenced delivery of user messages within multiple streams,
with an option for order-of-arrival delivery of individual with an option for order-of-arrival delivery of individual
user messages, user messages,
- Optional multiplexing of user messages into SCTP datagrams, - Optional multiplexing of user messages into SCTP datagrams,
- Network-level fault tolerance through support of multi-homing - Network-level fault tolerance through support of multi-homing
at either or both ends of an association, at either or both ends of an association,
- Resistance to flooding and masquerade attacks, and - Resistance to flooding and masquerade attacks, and
- Data segmentation to conform to discovered path MTU size. - Data segmentation to conform to discovered path MTU size.
Under certain scenarios, such as back-to-back connections without Under certain scenarios, such as back-to-back connections without
redundancy requirements, the SCTP functions above MAY NOT be a redundancy requirements, the SCTP functions above might not be a
requirement and TCP can be used as the underlying common transport requirement and TCP MAY be used as the underlying common transport
protocol. protocol.
1.3.2 Services Provided by the M3UA Layer 1.3.2 Services Provided by the M3UA Layer
The M3UA Layer at an ASP or IPSP provides the equivalent set of The M3UA Layer at an ASP or IPSP provides the equivalent set of
primitives at its upper layer to the MTP3-Users as provided by the MTP primitives at its upper layer to the MTP3-Users as provided by the MTP
Level 3 to its local MTP3-Users at an SS7 SEP. In this way, the ISUP 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 MTP3 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 not by 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 unaware that a local MTP3 layer. The MTP3 layer at an SGP may also be unaware that
its local users are actually remote user parts over M3UA. In effect, its local users are actually remote user parts over M3UA. In effect,
the M3UA extends access to the MTP3 layer services to a remote IP-based the M3UA extends access to the MTP3 layer services to a remote IP-based
application. The M3UA layer does not itself provide the MTP3 services. application. The M3UA layer does not itself provide the MTP3 services.
However, in the case where an ASP is connected to more than one SGP, However, in the case where an ASP is connected to more than one SG,
the M3UA layer at an ASP should maintain the status of configured SS7 the M3UA layer at an ASP should maintain the status of configured SS7
destinations and route messages according to the availability and destinations and route messages according to the availability and
congestion status of the routes to these destinations via each SGP. congestion status of the routes to these destinations via each SG.
The M3UA layer may also be used for point-to-point signalling between The M3UA layer may also be used for point-to-point signalling between
two IP Server Processes (IPSPs). In this case, the M3UA layer provides two IP Server Processes (IPSPs). In this case, the M3UA layer provides
the same set of primitives and services at its upper layer as the MTP3. the same set of primitives and services at its upper layer as the MTP3.
However, in this case the expected MTP3 services are not offered However, in this case the expected MTP3 services are not offered
remotely from an SGP. The MTP3 services are provided but the remotely from an SGP. The MTP3 services are provided but the
procedures to support these services are a subset of the MTP3 procedures to support these services are a subset of the MTP3
procedures due to the simplified point-to-point nature of the IPSP to procedures due to the simplified point-to-point nature of the IPSP to
IPSP relationship. IPSP relationship.
1.3.2.1 Support for the Transport of MTP3-User Messages 1.3.2.1 Support for the Transport of MTP3-User Messages
The M3UA layer provides the transport of MTP-TRANSFER primitives across The M3UA layer provides the transport of MTP-TRANSFER primitives across
an established SCTP association between an SGP and an ASP or between an established SCTP association between an SGP and an ASP or between
IPSPs. IPSPs.
The MTP-TRANSFER primitive information is encoded as in MTP3-User
messages. In this way, the User Part messages received from the
SS7 network by the SGP are not re-encoded into a different format for
transport between the M3UA peers. The MTP3 Service Information Octet
(SIO) and Routing Label (OPC, DPC, and SLS) are included, encoded as
expected by the MTP3 and MTP3-User protocol layer.
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, ensuring that no be routed or support load balancing across the SGPs, minimizing
missequencing occurs. missequencing.
The M3UA layer does not impose a 272-octet signalling information field The M3UA layer does not impose a 272-octet signalling information field
(SIF) length limit as specified by the SS7 MTP Level 2 protocol [14] (SIF) length limit as specified by the SS7 MTP Level 2 protocol [14]
[15] [16]. Larger information blocks can be accommodated directly by [15] [16]. Larger information blocks can be accommodated directly by
M3UA/SCTP, without the need for an upper layer segmentation/re-assembly M3UA/SCTP, without the need for an upper layer segmentation/reassembly
procedure as specified in recent SCCP or ISUP versions. However, in procedure as specified in recent SCCP or ISUP versions. However, in
the context of an SG, the maximum 272-octet block size must be followed the context of an SG, the maximum 272-octet block size must be followed
when inter-working to a SS7 network that does not support the transfer when interworking to a SS7 network that does not support the transfer
of larger information blocks to the final destination. This avoids of larger information blocks to the final destination. This avoids
potential ISUP or SCCP fragmentation requirements at the SGPs. potential ISUP or SCCP fragmentation requirements at the SGPs. The
However, if the SS7 network is provisioned to support the Broadband MTP provisioning and configuration of the SS7 network determines the
[20] to the final SS7 destination, the information block size limit MAY restriction placed on the maximum block size. Some configurations
be increased past 272 octets. (e.g., Broadband MTP [20]) may permit larger block sizes.
1.3.2.2 Native Management Functions 1.3.2.2 Native Management Functions
The M3UA layer provides the capability to indicate errors associated The M3UA layer provides the capability to indicate errors associated
with received M3UA messages and to notify, as appropriate, local with received M3UA messages and to notify, as appropriate, local
management and/or the peer M3UA. management and/or the peer M3UA.
1.3.2.3 Inter-working with MTP3 Network Management Functions 1.3.2.3 Interworking with MTP3 Network Management Functions
At the SGP, the M3UA layer must also provide inter-working with MTP3 At the SGP, the M3UA layer provides interworking with MTP3
management functions to support seamless operation of the user SCN management functions to support seamless operation of the user SCN
signalling applications in the SS7 and IP domains. This includes: signalling 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
skipping to change at page 10, line 18 skipping to change at page 9, line 49
the SCTP. the SCTP.
Also the M3UA layer MAY inform the local management of the change in Also the M3UA layer MAY inform the local management of the change in
status of an ASP or AS. This MAY be achieved using the M-ASP_STATUS status of an ASP or AS. This MAY be achieved using the M-ASP_STATUS
request or M-AS_STATUS request primitives. request or M-AS_STATUS request primitives.
1.3.2.5 Support for the Management of Connections to Multiple SGPs 1.3.2.5 Support for the Management of Connections to Multiple SGPs
As shown in Figure 1 an ASP may be connected to multiple SGPs. In such As shown in Figure 1 an ASP may be connected to multiple SGPs. In such
a case a particular SS7 destination may be reachable via more than one a case a particular SS7 destination may be reachable via more than one
SGP, i.e., via more than one route. As MTP3 users only maintain status SGP and/or SG, i.e., via more than one route. As MTP3 users only
on a destination and not on a route basis, the M3UA layer must maintain maintain status on a destination and not on a route basis, the M3UA
the status (availability, restriction, and/or congestion of route to layer must maintain the status (availability, restriction, and/or
destination) of the individual routes, derive the overall availability congestion of route to destination) of the individual routes, derive
or congestion status of the destination from the status of the the overall availability or congestion status of the destination
individual routes, and inform the MTP3 users of this derived status
whenever it changes. from the status of the individual routes, and inform the MTP3 users
of this derived status whenever it changes.
1.3.3 Signalling Network Architecture 1.3.3 Signalling Network Architecture
A Signalling Gateway is used to support the transport of MTP3-User A Signalling Gateway is used to support the transport of MTP3-User
signalling traffic received from the SS7 network to multiple signalling traffic received from the SS7 network to multiple
distributed ASPs (e.g., MGCs and IP Databases). Clearly, the M3UA distributed ASPs (e.g., MGCs and IP Databases). Clearly, the M3UA
protocol is not designed to meet the performance and reliability protocol is not designed to meet the performance and reliability
requirements for such transport by itself. However, the conjunction of requirements for such transport by itself. However, the conjunction
distributed architecture and redundant networks does allow for a of distributed architecture and redundant networks provides support
sufficiently reliable transport of signalling traffic over IP. The for reliable transport of signalling traffic over IP. The M3UA
M3UA protocol is flexible enough to allow its operation and management protocol is flexible enough to allow its operation and management
in a variety of physical configurations, enabling Network Operators to in a variety of physical configurations, enabling Network Operators
meet their performance and reliability requirements. to meet their performance and reliability requirements.
To meet the stringent SS7 signalling reliability and performance To meet the stringent SS7 signalling reliability and performance
requirements for carrier grade networks, Network Operators SHOULD requirements for carrier grade networks, Network Operators SHOULD
ensure that no single point of failure is present in the end-to-end ensure that no single point of failure is present in the end-to-end
network architecture between an SS7 node and an IP-based application. network architecture between an SS7 node and an IP-based application.
This can typically be achieved through the use of redundant SGPs or This can typically be achieved through the use of redundant SGPs or
SGs, redundant hosts, and the provision of redundant QOS-bounded IP SGs, redundant hosts, and the provision of redundant QOS-bounded IP
network paths for SCTP Associations between SCTP End Points. Obviously, network paths for SCTP Associations between SCTP End Points. Obviously,
the reliability of the SG, the MGC and other IP-based functional the reliability of the SG, the MGC and other IP-based functional
elements also needs to be taken into account. The distribution of ASPs elements also needs to be taken into account. The distribution of ASPs
and SGPs within the available Hosts MAY also be considered. As an and SGPs within the available Hosts MAY also be considered. As an
example, for a particular Application Server, the related ASPs SHOULD example, for a particular Application Server, the related ASPs could
be distributed over at least two Hosts. be distributed over at least two Hosts.
One example of a physical network architecture relevant to SS7 carrier- One example of a physical network architecture relevant to SS7 carrier-
grade operation in the IP network domain is shown in Figure 1 below: grade operation in the IP network domain is shown in Figure 1 below:
SG MGC SG MGC
Host#1 ************** ************** Host#3 Host#1 ************** ************** Host#3
= * ********__*__________________________*__******** * = = * ********__*__________________________*__******** * =
* * SGP1 *__*_____ _______________*__* ASP1 * * MGC1 * * SGP1 *__*_____ _______________*__* ASP1 * * MGC1
skipping to change at page 11, line 37 skipping to change at page 11, line 37
* : * SCTP Associations * : * * : * SCTP Associations * : *
* ******** * * ******** * * ******** * * ******** *
* * SGPn * * * * ASPn * * * * SGPn * * * * ASPn * *
* ******** * * ******** * * ******** * * ******** *
************** ************** ************** **************
Figure 1 - Physical Model Figure 1 - Physical Model
In this model, each host MAY have many application processes. In the In this model, each host MAY have many application processes. In the
case of the MGC, an ASP may provide service to one or more Application case of the MGC, an ASP may provide service to one or more Application
Servers, and is identified as an SCTP end point. A pair of Signalling Servers, and is identified as an SCTP end point. One or more
Gateway Processes MAY represent, as an example, a single Signalling Signalling Gateway Processes make up a single Signalling Gateway.
Gateway, serving a signalling point management cluster.
This example model can also be applied to IPSP-IPSP signalling. In This example model can also be applied to IPSP-IPSP signalling. In
this case, each IPSP MAY have its services distributed across 2 hosts this case, each IPSP MAY have its services distributed across 2 hosts
or more, and may have multiple server processes on each host. or more, and may have multiple server processes on each host.
In the example above, each signalling process (SGP, ASP or IPSP) is the In the example above, each signalling process (SGP, ASP or IPSP) is the
end point to more than one SCTP association, leading to more than one end point to more than one SCTP association, leading to more than one
other signalling processes. To support this, a signalling process must other signalling processes. To support this, a signalling process must
be able to support distribution of M3UA messages to many simultaneous be able to support distribution of M3UA messages to many simultaneous
active associations. This message distribution function is based on active associations. This message distribution function is based on
the status of provisioned Routing Keys, the status of the signalling the status of provisioned Routing Keys, the status of the signalling
routes to signalling points in the SS7 network , and the redundancy routes to signalling points in the SS7 network , and the redundancy
model (active-standby, load-sharing, broadcast, n+k) of the remote model (active-standby, load sharing, broadcast, n+k) of the remote
signalling processes. signalling processes.
For carrier grade networks, the failure or isolation of a particular For carrier grade networks, the failure or isolation of a particular
signalling process should not cause stable calls or transactions to be signalling process should not cause stable calls or transactions to be
lost. This implies that signalling processes need, in some cases, to lost. This implies that signalling processes need, in some cases, to
share the call/transaction state or be able to pass the call state share the call/transaction state or be able to pass the call state
information between each other. In the case of ASPs performing call information between each other. In the case of ASPs performing call
processing, coordination may also be required with the related Media processing, coordination may also be required with the related Media
Gateway to transfer the MGC control for a particular trunk termination. Gateway to transfer the MGC control for a particular trunk termination.
However, this sharing or communication of call/transaction state However, this sharing or communication of call/transaction state
skipping to change at page 12, line 31 skipping to change at page 12, line 31
1.4 Functional Areas 1.4 Functional Areas
1.4.1 Signalling Point Code Representation 1.4.1 Signalling Point Code Representation
For example, within an SS7 network, a Signalling Gateway might be For example, within an SS7 network, a Signalling Gateway might be
charged with representing a set of nodes in the IP domain into the SS7 charged with representing a set of nodes in the IP domain into the SS7
network for routing purposes. The SG itself, as a signalling point in network for routing purposes. The SG itself, as a signalling point in
the SS7 network, might also be addressable with an SS7 Point Code for the SS7 network, might also be addressable with an SS7 Point Code for
MTP3 Management purposes. The SG Point Code might also be used for MTP3 Management purposes. The SG Point Code might also be used for
addressing any local MTP3-Users at the SG such as an SG-resident SCCP addressing any local MTP3-Users at the SG such as a local SCCP layer.
function.
An SG may be logically partitioned to operate in multiple SS7 network An SG may be logically partitioned to operate in multiple SS7 network
appearances. In such a case, the SG could be addressable with a Point appearances. In such a case, the SG could be addressable with a Point
Code in each network appearance, and represents a set of nodes in the Code in each network appearance, and represents a set of nodes in the
IP domain into each SS7 network. Alias Point Codes [15] may also be IP domain into each SS7 network. Alias Point Codes [15] may also be
used within an SG network appearance. 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. Re-routing of traffic between the SGPs SHOULD also be supported. SGPs. Rerouting of traffic between the SGPs SHOULD also be supported.
Application Servers can be represented under the same Point Application Servers can be represented under the same Point
Code of the SG, their own individual Point Codes or grouped with other Code of the SG, their own individual Point Codes or grouped with other
Application Servers for Point Code preservation purposes. A single Application Servers for Point Code preservation purposes. A single
Point Code may be used to represent the SG and all the Application Point Code may be used to represent the SG and all the Application
Servers together, if desired. Servers together, if desired.
If an ASP or group of ASPs is available to the SS7 network via more If an ASP or group of ASPs is available to the SS7 network via more
than one SG, each with its own Point Code, the ASP(s) will typically be than one SG, each with its own Point Code, the ASP(s) will typically be
represented by a Point Code that is separate from any SG Point Code. 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 network as This allows, for example, these SGs to be viewed from the SS7 network
"STPs", each as "STPs", each
having an ongoing "route" to the same ASP(s). Under failure conditions having an ongoing "route" to the same ASP(s). Under failure conditions
where the ASP(s) become(s) unavailable from one of the SGs, this where the ASP(s) become(s) unavailable from one of the SGs, this
approach enables MTP3 route management messaging between the SG and SS7 approach enables MTP3 route management messaging between the SG and SS7
network, allowing simple SS7 re-routing through an alternate SG without network, allowing simple SS7 rerouting through an alternate SG without
changing the Destination Point Code Address of SS7 traffic to the changing the Destination Point Code Address of SS7 traffic to the
ASP(s). ASP(s).
Where an AS can be reached via more than one SGP the corresponding Where a particular AS can be reached via more than one SGP, the
Routing Keys in the involved SGPs should be identical. (Note: It is corresponding Routing Keys in the SGPs should be identical. (Note:
possible for the SGP Routing Key configuration data to be temporarily It is possible for the SGP Routing Key configuration data to be
out-of-synch during configuration updates). temporarily out-of-synch during configuration updates).
+--------+ +--------+
| | | |
+------------+ SG 1 +--------------+ +------------+ SG 1 +--------------+
+-------+ | SS7 links | "STP" | IP network | ---- +-------+ | SS7 links | "STP" | IP network | ----
| SEP +---+ +--------+ +---/ \ | SEP +---+ +--------+ +---/ \
| or | * | ASPs | | or | |* | ASPs |
| STP +---+ +--------+ +---\ / | STP +---+ +--------+ +---\ /
+-------+ | | | | ---- +-------+ | | | | ----
+------------+ SG 2 +--------------+ +------------+ SG 2 +--------------+
| "STP" | | "STP" |
+--------+ +--------+
* Note:. SG-to -SG communication is recommended for carrier grade * Note:. SG-to-SG communication (i.e., "C-links") is recommended for
networks, using an MTP3 linkset or an equivalent, to allow re-routing carrier grade networks, using an MTP3 linkset or an equivalent, to
between the SGs in the event of route failures. Where SGPs are used, allow rerouting between the SGs in the event of route failures.
inter-SGP communication is recommended. Inter-SGP protocol is outside Where SGPs are used, inter-SGP communication might be used.
of the scope of this document. 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 two
network appearances. network appearances.
SG SG
+-------+ +---------------+ +-------+ +---------------+
| SEP +--------------| SS7 Ntwk |M3UA| ---- | SEP +--------------| SS7 Ntwk |M3UA| ----
+-------+ SS7 links | "A" | | / \ +-------+ SS7 links | "A" | | / \
|__________| +-----------+ ASPs | |__________| +-----------+ ASPs |
| | | \ / | | | \ /
skipping to change at page 14, line 14 skipping to change at page 14, line 14
filter SS7 messages, whereas the Routing Context parameter is a 4-byte filter SS7 messages, whereas the Routing Context parameter is a 4-byte
value (integer) that is associated to that Routing Key in a 1:1 value (integer) that is associated to that Routing Key in a 1:1
relationship. The Routing Context therefore can be viewed as an index relationship. The Routing Context therefore can be viewed as an index
into a sending node's Message Distribution Table containing the Routing into a sending node's Message Distribution Table containing the Routing
Key entries. Key entries.
Possible SS7 address/routing information that comprise a Routing Key Possible SS7 address/routing information that comprise a Routing Key
entry includes, for example, the OPC, DPC, SIO found in the MTP3 entry includes, for example, the OPC, DPC, SIO found in the MTP3
routing label, or MTP3-User specific fields (such as the ISUP CIC, SCCP routing label, or MTP3-User specific fields (such as the ISUP CIC, SCCP
subsystem number) or TCAP transaction ID. Some example Routing Keys subsystem number). Some example Routing Keys are: the DPC alone, the
are: the DPC alone, the DPC/OPC combination, the DPC/OPC/CIC DPC/OPC combination, the DPC/OPC/CIC combination, or the DPC/SSN
combination, or the DPC/SSN combination. The particular information combination. The particular information used to define an M3UA
used to define an M3UA Routing Key is application and network Routing Key is application and network dependent, and none of the
dependent, and none of the above examples are mandated. above examples are mandated.
An Application Server Process may be configured to process signalling An Application Server Process may be configured to process signalling
traffic related to more than one Application Server, over a single SCTP traffic related to more than one Application Server, over a single SCTP
Association. In ASP Active and ASP Inactive management messages, the Association. In ASP Active and ASP Inactive management messages, the
signalling traffic to be started or stopped is discriminated by the signalling traffic to be started or stopped is discriminated by the
Routing Context parameter. At an ASP, the Routing Context parameter Routing Context parameter. At an ASP, the Routing Context parameter
uniquely identifies the range of signalling traffic associated with uniquely identifies the range of signalling traffic associated with
each Application Server that the ASP is configured to receive. each Application Server that the ASP is configured to receive.
1.4.2.2 Routing Key Limitations 1.4.2.2 Routing Key Limitations
Routing Keys SHOULD be unique in the sense that each received SS7 Routing Keys SHOULD be unique in the sense that each received SS7
signalling message SHOULD have a full or partial match to a single signalling message SHOULD have a full or partial match to a single
routing result to an Application Server. It is not necessary for the routing result. It is not necessary for the parameter range values
parameter range values within a particular Routing Key to be contiguous. within a particular Routing Key to be contiguous. For example, an
For example, an AS could be configured to support call processing for AS could be configured to support call processing for multiple ranges
multiple ranges of PSTN trunks that are not represented by contiguous of PSTN trunks that are not represented by contiguous CIC values.
CIC values.
1.4.2.3 Managing Routing Contexts and Routing Keys 1.4.2.3 Managing Routing Contexts and Routing Keys
There are two ways to provision a Routing Key at an SGP. A There are two ways to provision a Routing Key at an SGP. A Routing Key
Routing Key may be configured statically using an implementation may be configured statically using an implementation dependent
dependent management interface, or dynamically using the M3UA Routing management interface, or dynamically using the M3UA Routing Key
Key registration procedure. registration procedure.
When using a management interface to configure Routing Keys, the When using a management interface to configure Routing Keys, the
message distribution function within the SGP is not limited to the set message distribution function within the SGP is not limited to the set
of parameters defined in this document. Other implementation dependent of parameters defined in this document. Other implementation dependent
distribution algorithms may be used. distribution algorithms may be used.
1.4.2.4 Message Distribution at the SGP 1.4.2.4 Message Distribution at the SGP
To direct messages received from the SS7 MTP3 network to the To direct messages received from the SS7 MTP3 network to the
appropriate IP destination, the SGP must perform a message distribution appropriate IP destination, the SGP must perform a message distribution
skipping to change at page 15, line 25 skipping to change at page 15, line 19
by comparing elements of the incoming SS7 message to currently defined by comparing elements of the incoming SS7 message to currently defined
Routing Keys in the SGP. These Routing Keys could in turn map directly Routing Keys in the SGP. These Routing Keys could in turn map directly
to an Application Server that is enabled by one or more ASPs. These to an Application Server that is enabled by one or more ASPs. These
ASPs provide dynamic status information regarding their availability, ASPs provide dynamic status information regarding their availability,
traffic handling capability and congestion to the SGP using various traffic 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 account The list of ASPs in an AS is assumed to be dynamic, taking into account
the availability, traffic handling capability and congestion status of the availability, traffic handling capability and congestion status of
the individual ASPs in the list, as well as configuration changes and the individual ASPs in the list, as well as configuration changes and
possible fail-over mechanisms. 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, load- possible that there may be no active ASP available. Broadcast,
sharing and backup scenarios are supported. loadsharing and backup scenarios are supported.
When there is no matching Routing Key entry for an incoming SS7 When there is no matching Routing Key entry for an incoming SS7
message, a default treatment MAY be specified. Possible solutions are message, a default treatment MAY be specified. Possible solutions are
to provide a default Application Server at the SGP that directs all to provide a default Application Server at the SGP that directs all
unallocated traffic to a (set of) default ASP(s), or to drop the message unallocated traffic to a (set of) default ASP(s), or to drop the
and provide a notification to layer management. The treatment of message and provide a notification to layer management. The treatment
unallocated traffic is implementation dependent. 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. This The ASP must choose an SGP to direct a message to the SS7 network.
is accomplished by observing the Destination Point Code (and possibly This is accomplished by observing the Destination Point Code (and
other elements of the outgoing message such as the SLS value). possibly other elements of the outgoing message such as the SLS value).
Implementation Note: Where more than one route (or SGP) is Implementation Note: Where more than one route (or SGP) is
possible for routing to the SS7 network, the ASP could, for example, possible for routing to the SS7 network, the ASP could, for example,
maintain a dynamic table of available SGP routes for the SS7 maintain a dynamic table of available SGP routes for the SS7
destinations, taking into account the SS7 destination destinations, taking into account the SS7 destination
availability/restricted/congestion status received from the SGP(s), the availability/restricted/congestion status received from the SGP(s), the
availability status of the individual SGPs and configuration changes and availability status of the individual SGPs and configuration changes
fail-over mechanisms. There is, however, no M3UA messaging to manage the and failover mechanisms. There is, however, no M3UA messaging to manage
status of an SGP (e.g., SGP-Up/Down/Active/Inactive messaging). the status of an SGP (e.g., SGP-Up/Down/Active/Inactive messaging).
Whenever an SCTP
association to an SGP exists, the SGP is assumed to be ready for the
purposes of responding to M3UA ASPSM messages (Refer to Section 3).
Every SGP of one SG ASP regarding one AS provides identical SS7 Whenever an SCTP association to an SGP exists, the SGP is assumed to
connectivity to this ASP. be ready for the purposes of responding to M3UA ASPSM messages
(Refer to Section 3).
1.4.3 SS7 and M3UA Interworking 1.4.3 SS7 and M3UA Interworking
In the case of SS7 and M3UA inter-working, the M3UA adaptation layer is In the case of SS7 and M3UA interworking, the M3UA adaptation layer is
designed to provide an extension of the MTP3 defined user primitives. designed to provide an extension of the MTP3 defined user primitives.
1.4.3.1 Signalling Gateway SS7 Layers 1.4.3.1 Signalling Gateway SS7 Layers
The SG is responsible for terminating MTP Level 3 of the SS7 protocol, The SG is responsible for terminating MTP Level 3 of the SS7 protocol,
and offering an IP-based extension to its users. and offering an IP-based extension to its users.
>From an SS7 perspective, it is expected that the Signalling Gateway >From an SS7 perspective, it is expected that the Signalling Gateway
transmits and receives SS7 Message Signalling Units (MSUs) to and transmits and receives SS7 Message Signalling Units (MSUs) to and
from the PSTN over a standard SS7 network interface, using the SS7 from the PSTN over a standard SS7 network interface, using the SS7
skipping to change at page 16, line 36 skipping to change at page 16, line 30
As a standard SS7 network interface, the use of MTP Level 2 signalling As a standard SS7 network interface, the use of MTP Level 2 signalling
links is not the only possibility. ATM-based High Speed Links can also links is not the only possibility. ATM-based High Speed Links can also
be used with the services of the Signalling ATM Adaptation Layer (SAAL) be used with the services of the Signalling ATM Adaptation Layer (SAAL)
[17,18]. [17,18].
Note: It is also possible for IP-based interfaces to be present, using Note: It is also possible for IP-based interfaces to be present, using
the services of the MTP2-User Adaptation Layer (M2UA) [26] or M2PA [27]. the services of the MTP2-User Adaptation Layer (M2UA) [26] or M2PA [27].
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 be Signalling End Point (SEP). Using the services of MTP3, the SG could
capable of communicating with remote SS7 SEPs in a quasi-associated be capable of communicating with remote SS7 SEPs in a quasi-associated
fashion, where STPs may be present in the SS7 path between the SEP and fashion, where STPs may be present in the SS7 path between the SEP and
the SG. the SG.
1.4.3.2 SS7 and M3UA Inter-Working at the SG 1.4.3.2 SS7 and M3UA Interworking at the SG
The SGP provides a functional inter-working of transport functions The SGP provides a functional interworking of transport functions
between the SS7 network and the IP network by also supporting the M3UA between the SS7 network and the IP network by also supporting the M3UA
adaptation layer. It allows the transfer of MTP3-User signalling adaptation layer. It allows the transfer of MTP3-User signalling
messages to and from an IP-based Application Server Process where the messages to and from an IP-based Application Server Process where the
peer MTP3-User protocol layer exists. peer MTP3-User protocol layer exists.
For SS7 user part management, it is required that the MTP3-User For SS7 user part management, it is required that the MTP3-User
protocols at ASPs receive indications of SS7 signalling point protocols at ASPs receive indications of SS7 signalling point
availability, SS7 network congestion, and remote User Part availability, SS7 network congestion, and remote User Part
unavailability as would be expected in an SS7 SEP node. To accomplish unavailability as would be expected in an SS7 SEP node. To accomplish
this, the MTP-PAUSE, MTP-RESUME and MTP-STATUS indication primitives this, the MTP-PAUSE, MTP-RESUME and MTP-STATUS indication primitives
skipping to change at page 17, line 24 skipping to change at page 17, line 11
network) MUST NOT be encapsulated as Data message Payload Data and sent 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 these either from SG to ASP or from ASP to SG. The SG MUST terminate these
messages and generate M3UA messages as appropriate. 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 complete As an example, an SPMC providing MGC capabilities could provide
support for ISUP (and any other MTP3 user located at the point code of complete support for ISUP (and any other MTP3 user located at the
the SPMC) for a given point code. point code of the SPMC) for a given point code.
In the case where an ASP is connected to more than one SGP, the M3UA In the case where an ASP is connected to more than one SGP, the M3UA
layer must maintain the status of configured SS7 destinations and route layer must maintain the status of configured SS7 destinations and route
messages according to availability/congestion/restricted status of the messages according to availability/congestion/restricted status of the
routes to these SS7 destinations. routes to these SS7 destinations.
1.4.3.4 IPSP Considerations 1.4.3.4 IPSP Considerations
Since IPSPs use M3UA in a point-to-point fashion, there is no concept Since IPSPs use M3UA in a point-to-point fashion, there is no concept
of routing of messages beyond the remote end. Therefore, SS7 and M3UA of routing of messages beyond the remote end. Therefore, SS7 and M3UA
inter-working is not necessary for this model. interworking is not necessary for this model.
1.4.4 Redundancy Models 1.4.4 Redundancy Models
1.4.4.1 Application Server Redundancy 1.4.4.1 Application Server Redundancy
All MTP3-User messages (e.g., ISUP, SCCP) which match a provisioned All MTP3-User messages (e.g., ISUP, SCCP) which match a provisioned
Routing Key at an SGP are mapped to an Application Server. Routing Key at an SGP are mapped to an Application Server.
The Application Server is the set of all ASPs associated with a specific The Application Server is the set of all ASPs associated with a
Routing Key. Each ASP in this set may be active inactive or unavailable. specific Routing Key. Each ASP in this set may be active inactive or
Active ASPs handle traffic; inactive ASPs might be used when active ASPs unavailable. Active ASPs handle traffic; inactive ASPs might be used
become unavailable. when active ASPs become unavailable.
The fail-over 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 and
"k" ASPs are available to take over for a failed or unavailable ASP. A "k" ASPs are available to take over for a failed or unavailable ASP. A
"1+1" active/back-up redundancy is a subset of this model. A simplex "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 redundancy. "1+0" model is also supported as a subset, with no ASP redundancy.
At the SGP, an Application Server list contains active and inactive At the SGP, an Application Server list contains active and inactive
ASPs to support ASP broadcast, load-sharing and fail-over procedures. ASPs to support ASP broadcast, loadsharing and failover procedures.
The list of ASPs within a logical Application Server is kept updated in The list of ASPs within a logical Application Server is kept updated in
the SGP to reflect the active Application Server Process(es). the SGP to reflect the active Application Server Process(es).
For example, in the network shown in Figure 1, all messages to DPC x For example, in the network shown in Figure 1, all messages to DPC x
could be sent to ASP1 in Host3 or ASP1 in Host4. The AS list at SGP1 in could be sent to ASP1 in Host3 or ASP1 in Host4. The AS list at SGP1
Host 1 might look like the following: in Host 1 might look like the following:
Routing Key {DPC=x) - "Application Server #1" Routing Key {DPC=x) - "Application Server #1"
ASP1/Host3 - State = Active ASP1/Host3 - State = Active
ASP1/Host4 - State = Inactive ASP1/Host4 - State = Inactive
In this "1+1" redundancy case, ASP1 in Host3 would be sent any incoming In this "1+1" redundancy case, ASP1 in Host3 would be sent any incoming
message with DPC=x. ASP1 in Host4 would normally be brought to the message with DPC=x. ASP1 in Host4 would normally be brought to the
"active" state upon failure of, or loss of connectivity to, ASP1/Host1. "active" state upon failure of, or loss of connectivity to, ASP1/Host1.
The AS List at SGP1 in Host1 might also be set up in load-share mode: The AS List at SGP1 in Host1 might also be set up in loadshare mode:
Routing Key {DPC=x) - "Application Server #1" Routing Key {DPC=x) - "Application Server #1"
ASP1/Host3 - State = Active ASP1/Host3 - State = Active
ASP1/Host4 - State = Active ASP1/Host4 - State = Active
In this case, both the ASPs would be sent a portion of the traffic. In this case, both the ASPs would be sent a portion of the traffic.
For example the two ASPs could together form a database, where incoming For example the two ASPs could together form a database, where incoming
queries may be sent to any active ASP. queries may be sent to any active ASP.
Care might need to be exercised by a Network Operator in the selection Care might need to be exercised by a Network Operator in the selection
of the routing information to be used as the Routing Key for a of the routing information to be used as the Routing Key for a
particular AS. particular AS.
For example, where Application Servers are defined using ranges of ISUP For example, where Application Servers are defined using ranges of ISUP
CIC values, the Operator is implicitly splitting up control of the CIC values, the Operator is implicitly splitting up control of the
related circuit groups. Some CIC value range assignments may interfere related circuit groups. Some CIC value range assignments may interfere
with ISUP circuit group management procedures. with ISUP circuit group management procedures.
In the process of fail-over, it is recommended that in the case of ASPs In the process of failover, it is recommended that in the case of ASPs
supporting call processing, stable calls do not fail. It is possible supporting call processing, stable calls do not fail. It is possible
that calls in "transition" MAY fail, although measures of communication that calls in "transition" MAY fail, although measures of communication
between the ASPs involved can be used to mitigate this. For example, between the ASPs involved can be used to mitigate this. For example,
the two ASPs MAY share call state via shared memory, or MAY use an ASP the two ASPs MAY share call state via shared memory, or MAY use an ASP
to ASP protocol to pass call state information. Any ASP-to-ASP to ASP protocol to pass call state information. Any ASP-to-ASP
protocol to support this function is outside the scope of this protocol to support this function is outside the scope of this
document. document.
1.4.4.2 Signalling Gateway Redundancy 1.4.4.2 Signalling Gateway Redundancy
Signalling Gateways MAY also be distributed over multiple hosts. Much Signalling Gateways MAY also be distributed over multiple hosts. Much
like the AS model, SGs may comprise one or more SG Processes (SGPs), like the AS model, SGs may comprise one or more SG Processes (SGPs),
distributed over one or more hosts, using an active/back-up or a load- distributed over one or more hosts, using an active/backup or a
sharing model. Also, every SGP within an SG communicating with an ASP loadsharing model. Should an SGP lose all or partial SS7
provides identical SS7 connectivity to this ASP. Should an SGP lose all connectivity and other SGPs exist, the SGP MUST terminate the SCTP
or partial SS7 connectivity and other SGPs exist, the SGP MUST associations to the concerned ASPs.
terminate the SCTP associations to the concerned ASPs.
It is therefore possible for an ASP to route signalling messages It is therefore possible for an ASP to route signalling messages
destined to the SS7 network using more than one SGP. In this model, a destined to the SS7 network using more than one SGP. In this model, a
Signalling Gateway is deployed as a cluster of hosts acting as a single Signalling Gateway is deployed as a cluster of hosts acting as a single
SG. A primary/back-up redundancy model is possible, where the SG. A primary/backup redundancy model is possible, where the
unavailability of the SCTP association to a primary SGP could be used unavailability of the SCTP association to a primary SGP could be used
to reroute affected traffic to an alternate SGP. A load-sharing model to reroute affected traffic to an alternate SGP. A loadsharing model
is possible, where the signalling messages are load-shared between is possible, where the signalling messages are loadshared between
multiple SGPs. A broadcast model is also possible, where signalling multiple SGPs. A broadcast model is also possible, where signalling
messages are sent to each active SGP in the SG. The distribution of the messages are sent to each active SGP in the SG. The distribution of the
MTP3-user messages over the SGPs should be done in such a way to MTP3-user messages over the SGPs should be done in such a way to
minimize message mis-sequencing, as required by the SS7 User Parts. minimize message missequencing, as required by the SS7 User Parts.
It may also be possible for an ASP to use more than one SG to access a It may also be possible for an ASP to use more than one SG to access a
specific SS7 end point, in a model that resembles an SS7 STP mated specific SS7 end point, in a model that resembles an SS7 STP mated
pair. Typically, SS7 STPs are deployed in mated pairs, with traffic pair. Typically, SS7 STPs are deployed in mated pairs, with traffic
load-shared between them. Other models are also possible, subject to loadshared between them. Other models are also possible, subject to
the limitations of the local SS7 network provisioning guidelines. the limitations of the local SS7 network provisioning guidelines.
>From the perspective of the M3UA layer at an ASP, a particular SG is >From the perspective of the M3UA layer at an ASP, a particular SG is
capable of transferring traffic to an SS7 destination if an SCTP capable of transferring traffic to a provisioned SS7 destination X if
association with at least one SGP of the SG is established, the SGP has an SCTP association with at least one SGP of the SG is established,
returned an acknowledgement to the ASP to indicate that the ASP is the SGP has returned an acknowledgement to the ASP to indicate that
actively handling traffic for that destination, and the SGP has not the ASP is actively handling traffic for that destination X, the SGP
indicated that the destination is inaccessible. When an ASP is has not indicated that the destination X is inaccessible and the SGP
configured to use multiple SGPs for transferring traffic to the SS7 has not indicated MTP Restart. When an ASP is configured to use
network, the ASP must maintain knowledge of the current capability of multiple SGPs for transferring traffic to the SS7 network, the ASP
the SGPs to handle traffic to destinations of interest. This must maintain knowledge of the current capability of the SGPs to
information is crucial to the overall reliability of the service, for handle traffic to destinations of interest. This information is
active/back-up, load-sharing and broadcast models, in the event of crucial to the overall reliability of the service, for active/backup,
failures, recovery and maintenance activities. The ASP M3UA may also loadsharing and broadcast models, in the event of failures, recovery
use this information for congestion avoidance purposes. The and maintenance activities. The ASP M3UA may also use this
distribution of the MTP3-user messages over the SGPs should be done in information for congestion avoidance purposes. The distribution of
such a way to minimize message mis-sequencing, as required by the SS7 the MTP3-user messages over the SGPs should be done in such a way to
User Parts. minimize message missequencing, as required by the SS7 User Parts.
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 association to temporarily remove the association from service
or to perform testing and maintenance activity. The function could or to 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
skipping to change at page 21, line 8 skipping to change at page 20, line 32
signalling traffic into streams within an SCTP association. Traffic signalling traffic into streams within an SCTP association. Traffic
that requires sequencing SHOULD be assigned to the same stream. To that requires sequencing SHOULD be assigned to the same stream. To
accomplish this, MTP3-User traffic may be assigned to individual accomplish this, MTP3-User traffic may be assigned to individual
streams based on, for example, the SLS value in the MTP3 Routing Label streams based on, for example, the SLS value in the MTP3 Routing Label
or the ISUP CIC assignment, subject of course to the maximum number of or the ISUP CIC assignment, subject of course to the maximum number of
streams supported by the underlying SCTP association. streams supported by the underlying SCTP association.
1.4.8 Client/Server Model 1.4.8 Client/Server Model
It is recommended that the SGP and ASP be able to support both client It is recommended that the SGP and ASP be able to support both client
and server and server operation. The peer endpoints using M3UA SHOULD be
operation. The peer endpoints using M3UA SHOULD be configured so that configured so that one always takes on the role of client and the
one always other the role of server for initiating SCTP associations. The default
takes on the role of client and the other the role of server for orientation would be for the SGP to take on the role of server while
initiating SCTP the ASP is the client. In this case, ASPs SHOULD initiate the
associations. The default orientation would be for the SGP to take on SCTP association to the SGP.
the role
of server while the ASP is the client. In this case, ASPs SHOULD
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 Registered User Port Number Assignment for M3UA is 2905. The SCTP Registered User Port Number Assignment for M3UA is 2905.
1.5 Sample Configurations 1.5 Sample Configurations
skipping to change at page 21, line 47 skipping to change at page 21, line 24
| MTP3 | | MTP3 | | M3UA | | M3UA | | MTP3 | | MTP3 | | M3UA | | M3UA |
+------| +------+-+------+ +------+ +------| +------+-+------+ +------+
| MTP2 | | MTP2 | | SCTP | | SCTP | | MTP2 | | MTP2 | | SCTP | | SCTP |
+------+ +------+ +------+ +------+ +------+ +------+ +------+ +------+
| L1 | | L1 | | IP | | IP | | L1 | | L1 | | IP | | IP |
+------+ +------+ +------+ +------+ +------+ +------+ +------+ +------+
|_______________| |______________| |_______________| |______________|
SEP - SS7 Signalling End Point SEP - SS7 Signalling End Point
SCTP - Stream Control Transmission Protocol SCTP - Stream Control Transmission Protocol
NIF - Nodal Inter-working Function NIF - Nodal Interworking Function
In this example, the SGP provides an implementation-dependent nodal In this example, the SGP provides an implementation-dependent nodal
inter-working function (NIF) that allows the MGC to exchange SS7 interworking function (NIF) that allows the MGC to exchange SS7
signalling messages with the SS7-based SEP. The NIF within the SGP signalling messages with the SS7-based SEP. The NIF within the SGP
serves as the interface within the SGP between the MTP3 and M3UA. This serves as the interface within the SGP between the MTP3 and M3UA. This
nodal inter-working function has no visible peer protocol with either nodal interworking function has no visible peer protocol with either
the MGC or SEP. It also provides network status information to one or the MGC or SEP. It also provides network status information to one or
both sides of the network. both sides of the network.
For internal SGP modeling purposes, at the NIF level, SS7 signalling For internal SGP modeling purposes, at the NIF level, SS7 signalling
messages that are destined to the MGC are received as MTP-TRANSFER messages that are destined to the MGC are received as MTP-TRANSFER
indication primitives from the MTP Level 3 upper layer interface, indication primitives from the MTP Level 3 upper layer interface,
translated to MTP-TRANSFER request primitives, and sent to the local translated to MTP-TRANSFER request primitives, and sent to the local
M3UA-resident message distribution function for ongoing routing to the M3UA-resident message distribution function for ongoing routing to the
final IP destination. Messages received from the local M3UA network final IP destination. Messages received from the local M3UA network
address translation and mapping function as MTP-TRANSFER indication address translation and mapping function as MTP-TRANSFER indication
primitives are sent to the MTP Level 3 upper layer interface as MTP- primitives are sent to the MTP Level 3 upper layer interface as MTP-
TRANSFER request primitives for on-going MTP Level 3 routing to an SS7 TRANSFER request primitives for ongoing MTP Level 3 routing to an SS7
SEP. For the purposes of providing SS7 network status information the SEP. For the purposes of providing SS7 network status information the
NIF also delivers MTP-PAUSE, MTP-RESUME and MTP-STATUS indication NIF also delivers MTP-PAUSE, MTP-RESUME and MTP-STATUS indication
primitives received from the MTP Level 3 upper layer interface to the primitives received from the MTP Level 3 upper layer interface to the
local M3UA-resident management function. In addition, as an local M3UA-resident management function. In addition, as an
implementation and network option, restricted destinations are implementation and network option, restricted destinations are
communicated from MTP network management to the local M3UA-resident communicated from MTP network management to the local M3UA-resident
management function. management function.
1.5.2 Example 2: SCCP Transport between IPSPs 1.5.2 Example 2: SCCP Transport between IPSPs
skipping to change at page 22, line 45 skipping to change at page 22, line 28
+------+ +------+ +------+ +------+
| SCTP | | SCTP | | SCTP | | SCTP |
+------+ +------+ +------+ +------+
| IP | | IP | | IP | | IP |
+------+ +------+ +------+ +------+
|________________| |________________|
This example shows an architecture where no Signalling Gateway is used. This example shows an architecture where no Signalling Gateway is used.
In this example, SCCP messages are exchanged directly between two IP- In this example, SCCP messages are exchanged directly between two IP-
resident IPSPs with resident SCCP-User protocol instances, such as resident IPSPs with resident SCCP-User protocol instances, such as
RANAP or TCAP. SS7 network inter-working is not required, therefore RANAP or TCAP. SS7 network interworking is not required, therefore
there is no MTP3 network management status information for the SCCP and there is no MTP3 network management status information for the SCCP and
SCCP-User protocols to consider. Any MTP-PAUSE, MTP-RESUME or MTP- SCCP-User protocols to consider. Any MTP-PAUSE, MTP-RESUME or MTP-
STATUS indications from the M3UA layer to the SCCP layer should STATUS indications from the M3UA layer to the SCCP layer should
consider the status of the SCTP Association and underlying IP network consider the status of the SCTP Association and underlying IP network
and any congestion information received from the remote site. and any congestion information received from the remote site.
1.5.3 Example 3: SGP Resident SCCP Layer, with Remote ASP 1.5.3 Example 3: SGP Resident SCCP Layer, with Remote ASP
******** SS7 ***************** IP ******** ******** SS7 ***************** IP ********
* SEP *---------* *--------* * * SEP *---------* *--------* *
skipping to change at page 23, line 53 skipping to change at page 23, line 29
address of an SCCP peer in the SS7 network then the resulting MTP- address of an SCCP peer in the SS7 network then the resulting MTP-
TRANSFER request primitive is given to the MTP3 for delivery to an SS7- TRANSFER request primitive is given to the MTP3 for delivery to an SS7-
resident node. resident node.
It is possible that the above SCCP GTT at the SGP could yield the It is possible that the above SCCP GTT at the SGP could yield the
address of an SCCP peer in the IP domain and the resulting MTP-TRANSFER address of an SCCP peer in the IP domain and the resulting MTP-TRANSFER
request primitive would be sent back to the M3UA layer for delivery to request primitive would be sent back to the M3UA layer for delivery to
an IP destination. 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 inter-working function within use of an implementation-dependent nodal interworking function within
the SGP that effectively sits below the SCCP and routes MTP-TRANSFER the SGP that effectively sits below the SCCP and routes MTP-TRANSFER
request/indication messages to/from both the MTP3 and the M3UA layer, request/indication messages to/from both the MTP3 and the M3UA layer,
based on the SS7 DPC or DPC/SSN address information. This nodal inter- based on the SS7 DPC or DPC/SSN address information. This nodal
working function has no visible peer protocol with either the ASP or interworking function has no visible peer protocol with either the
SEP. ASP or SEP.
Note that the services and interface provided by the M3UA layer are the Note that the services and interface provided by the M3UA layer are the
same as in Example 1 and the functions taking place in the SCCP entity same as in Example 1 and the functions taking place in the SCCP entity
are transparent to the M3UA layer. The SCCP protocol functions are not are transparent to the M3UA layer. The SCCP protocol functions are not
reproduced in the M3UA protocol. reproduced in the M3UA protocol.
1.6 Definition of M3UA Boundaries 1.6 Definition of M3UA Boundaries
1.6.1 Definition of the Boundary between M3UA and an MTP3-User. 1.6.1 Definition of the Boundary between M3UA and an MTP3-User.
skipping to change at page 26, line 21 skipping to change at page 26, line 12
Purpose: ASP reports that is has received an ASP UP Ack message from Purpose: ASP reports that is has received an ASP UP Ack message from
its peer. its peer.
M-ASP_UP indication M-ASP_UP indication
Direction: M3UA -> LM Direction: M3UA -> LM
Purpose: M3UA reports it has successfully processed an incoming ASP Purpose: M3UA reports it has successfully processed an incoming ASP
Up message from its peer. Up message from its peer.
M-ASP_DOWN request M-ASP_DOWN request
Direction: LM -> M3UA Direction: LM -> M3UA
Purpose: LM requests ASP to stop its operation and send an ASP-Down Purpose: LM requests ASP to stop its operation and send an ASP Down
message to its peer. message to its peer.
M-ASP_DOWN confirm M-ASP_DOWN confirm
Direction: M3UA -> LM Direction: M3UA -> LM
Purpose: ASP reports that is has received an ASP Down Purpose: ASP reports that is has received an ASP Down Ack message
Ack message from its peer. from its peer.
M-ASP_DOWN indication M-ASP_DOWN indication
Direction: M3UA -> LM Direction: M3UA -> LM
Purpose: M3UA reports it has successfully processed an incoming ASP Purpose: M3UA reports it has successfully processed an incoming ASP
Down message from its peer, or the SCTP association has Down message from its peer, or the SCTP association has
been lost/reset. been lost/reset.
M-ASP_ACTIVE request M-ASP_ACTIVE request
Direction: LM -> M3UA Direction: LM -> M3UA
Purpose: LM requests ASP to send an ASP Active message to its peer. Purpose: LM requests ASP to send an ASP Active message to its peer.
skipping to change at page 27, line 47 skipping to change at page 27, line 37
Purpose: ASP reports that it has received REG RSP message with Purpose: ASP reports that it has received REG RSP message with
registration status as successful from its peer. registration status as successful from its peer.
M-RK_REG indication M-RK_REG indication
Direction: M3UA -> LM Direction: M3UA -> LM
Purpose: M3UA informs LM that it has successfully processed an Purpose: M3UA informs LM that it has successfully processed an
incoming REG REQ message. incoming REG REQ message.
M-RK_DEREG request M-RK_DEREG request
Direction: LM -> M3UA Direction: LM -> M3UA
Purpose: LM requests ASP to de-register RK(s) with its peer by Purpose: LM requests ASP to deregister RK(s) with its peer by
sending DEREG REQ message. sending DEREG REQ message.
M-RK_DEREG confirm M-RK_DEREG confirm
Direction: M3UA -> LM Direction: M3UA -> LM
Purpose: ASP reports that it has received DEREG REQ message with de- Purpose: ASP reports that it has received DEREG REQ message with
registration status as successful from its peer. deregistration status as successful from its peer.
M-RK_DEREG indication M-RK_DEREG indication
Direction: M3UA -> LM Direction: M3UA -> LM
Purpose: M3UA informs LM that it has successfully processed an Purpose: M3UA informs LM that it has successfully processed an
incoming DEREG REQ from its peer. incoming DEREG REQ from its peer.
2.0 Conventions 2.0 Conventions
The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD
NOT, RECOMMENDED, NOT RECOMMENDED, MAY, and OPTIONAL, when they appear NOT, RECOMMENDED, NOT RECOMMENDED, MAY, and OPTIONAL, when they appear
skipping to change at page 29, line 52 skipping to change at page 29, line 52
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 SS7 Network 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 Heatbeat 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.5) ASP Traffic Maintenance (ASPTM) Messages (See Section 3.5)
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)
skipping to change at page 31, line 5 skipping to change at page 31, line 5
3.1.4 Message Length: 32-bits (unsigned integer) 3.1.4 Message Length: 32-bits (unsigned integer)
The Message Length defines the length of the message in octets, The Message Length defines the length of the message in octets,
including the Common Header. For messages with a final parameter including the Common Header. For messages with a final parameter
containing padding, the parameter padding MUST be included in the containing padding, the parameter padding MUST be included in the
Message Length. Message Length.
Note: A receiver SHOULD accept the message whether or not the final Note: A receiver SHOULD accept the message whether or not the final
parameter padding is included in the message length. parameter padding is included in the message length.
3.2 Variable-Length Parameter Format 3.2 Variable Length Parameter Format
M3UA messages consist of a Common Header followed by zero or more M3UA messages consist of a Common Header followed by zero or more
variable length parameters, as defined by the message type. All the variable length parameters, as defined by the message type. All the
parameters contained in a message are defined in a Tag-Length-Value parameters contained in a message are defined in a Tag Length-Value
format as shown below. format as shown below.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Parameter Tag | Parameter Length | | Parameter Tag | Parameter Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ Parameter Value / / Parameter Value /
\ \ \ \
skipping to change at page 31, line 34 skipping to change at page 31, line 34
SHOULD accept the parameters in any order. SHOULD accept the parameters in any order.
Parameter Tag: 16 bits (unsigned integer) Parameter Tag: 16 bits (unsigned integer)
The Tag field is a 16-bit identifier of the type of parameter. It The Tag field is a 16-bit identifier of the type of parameter. It
takes a value of 0 to 65534. Common parameters used by adaptation takes a value of 0 to 65534. Common parameters used by adaptation
layers are in the range of 0x00 to 0x3f. M3UA-specific parameters layers are in the range of 0x00 to 0x3f. M3UA-specific parameters
have Tags in the range 0x0200 to 0x02ff. The parameter Tags defined have Tags in the range 0x0200 to 0x02ff. The parameter Tags defined
are as follows: are as follows:
0x0000 Reserved Common Parameters. These TLV parameters are common across the
0x0200 Network Appearance different adaptation layers:
0x0201 Protocol Data 1
0x0202 Protocol Data 2
0x0004 INFO String
0x0203 Affected Destinations
0x0006 Routing Context
0x0007 Diagnostic Information
0x0009 Heartbeat Data
0x0204 User/Cause
0x000a Reason
0x000b Traffic Mode Type
0x000c Error Code
0x000d Status
0x000e ASP Identifier
0x0205 Congestion Indications
0x0206 Concerned Destination
0x0207 Routing Key
0x0208 Registration Result
0x0209 De-registration Result
0x020a Local_Routing Key Identifier
0x020b Destination Point Code
0x020c Service Indicators
0x02 Subsystem Numbers
0x020e Originating Point Code List
0x020f Circuit Range
0x0210 to 0xffff...Reserved by the IETF Parameter Name Parameter ID
============== ============
Reserved 0x0000
Not Used in M3UA 0x0001
Not Used in M3UA 0x0002
Not Used in M3UA 0x0003
INFO String 0x0004
Not Used in M3UA 0x0005
Routing Context 0x0006
Diagnostic Information 0x0007
Not Used in M3UA 0x0008
Heartbeat Data 0x0009
Not Used in M3UA 0x000a
Traffic Mode Type 0x000b
Error Code 0x000c
Status 0x000d
Not Used in M3UA 0x000e
Not Used in M3UA 0x000f
Not Used in M3UA 0x0010
ASP Identifier 0x0011
Affected Point Code 0x0012
M3UA-Specific parameters. These TLV parameters are specific to the
M3UA protocol:
Network Appearance 0x0200
Reserved 0x0201
Reserved 0x0202
Reserved 0x0203
User/Cause 0x0204
Congestion Indications 0x0205
Concerned Destination 0x0206
Routing Key 0x0207
Registration Result 0x0208
Deregistration Result 0x0209
Local_Routing Key Identifier 0x020a
Destination Point Code 0x020b
Service Indicators 0x020c
Subsystem Numbers 0x020d
Originating Point Code List 0x020e
Circuit Range 0x020f
Protocol Data 0x0210
Correlation Id 0x0211
Registration Status 0x0212
Deregistration Status 0x0213
Reserved by the IETF 0x0214 to 0xffff
The value of 65535 is reserved for IETF-defined extensions. Values The value of 65535 is reserved for IETF-defined extensions. Values
other than those defined in specific parameter description are other than those defined in specific parameter description are
reserved for use by the IETF. reserved for use 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 in The Parameter Length field contains the size of the parameter in
bytes, including the Parameter Tag, Parameter Length, and Parameter bytes, including the Parameter Tag, Parameter Length, and Parameter
Value fields. The Parameter Length does not include any padding Value fields. The Parameter Length does not include any padding
bytes. bytes.
Parameter Value: variable-length. Parameter Value: variable length.
The Parameter Value field contains the actual information to be The Parameter Value field contains the actual information to be
transferred in the parameter. transferred in the parameter.
The total length of a parameter (including Tag, Parameter Length and The total length of a parameter (including Tag, Parameter Length and
Value fields) MUST be a multiple of 4 bytes. If the length of the Value fields) MUST be a multiple of 4 bytes. If the length of the
parameter is not a multiple of 4 bytes, the sender pads the parameter is not a multiple of 4 bytes, the sender pads the
Parameter at the end (i.e., after the Parameter Value field) with Parameter at the end (i.e., after the Parameter Value field) with
all zero bytes. The length of the padding is NOT included in the all zero bytes. The length of the padding is NOT included in the
parameter length field. A sender SHOULD NOT pad with more than 3 parameter length field. A sender SHOULD NOT pad with more than 3
skipping to change at page 32, line 46 skipping to change at page 33, line 17
The following section describes the Transfer messages and parameter The following section describes the Transfer messages and parameter
contents. contents.
3.3.1 Payload Data Message (DATA) 3.3.1 Payload Data Message (DATA)
The DATA message contains the SS7 MTP3-User protocol data, which is an The DATA message contains the SS7 MTP3-User protocol data, which is an
MTP-TRANSFER primitive, including the complete MTP3 Routing Label. The MTP-TRANSFER primitive, including the complete MTP3 Routing Label. The
DATA message contains the following variable length parameters: DATA message contains the following variable length parameters:
Network Appearance Optional Network Appearance Optional
Protocol Data 1 or 2 Mandatory Routing Context Optional
Protocol Data Mandatory
Correlation Id Optional
3.3 Transfer Messages
The following section describes the Transfer messages and parameter
contents.
3.3.1 Payload Data Message (DATA)
The DATA message contains the SS7 MTP3-User protocol data, which is an
MTP-TRANSFER primitive, including the complete MTP3 Routing Label. The
DATA message contains the following variable length parameters:
Network Appearance Optional
Routing Context Optional
Protocol Data Mandatory
Correlation Id Optional
The following format MUST be used for the Data Message: The following format MUST be used for the Data Message:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0200 | Length = 8 | | Tag = 0x0200 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Network Appearance | | Network Appearance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0201 or 0x0202 | Length | | Tag = 0x0006 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Routing Context |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0210 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ Protocol Data / / Protocol Data /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0211 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Correlation Id |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Network Appearance: 32-bits (unsigned integer) Network Appearance: 32-bits (unsigned integer)
The optional Network Appearance parameter identifies the SS7 network The optional Network Appearance parameter identifies the SS7 network
context for the message, for the purposes of logically separating context for the message, for the purposes of logically separating
the signalling traffic between the SGP and the ASP over a common the signalling traffic between the SGP and the ASP over a common
SCTP association. An example is where an SG is logically SCTP association. An example is where an SG is logically
partitioned to appear as an element in four different national SS7 partitioned to appear as an element in four different national SS7
networks. networks.
skipping to change at page 33, line 47 skipping to change at page 34, line 55
included. included.
The Network Appearance parameter value is of local significance The Network Appearance parameter value is of local significance
only, coordinated between the SGP and ASP. Therefore, in the case only, coordinated between the SGP and ASP. Therefore, in the case
where an ASP is connected to more than one SGP, the same SS7 network where an ASP is connected to more than one SGP, the same SS7 network
context may be identified by different Network Appearance values context may be identified by different Network Appearance values
depending over which SGP a message is being transmitted/received. depending over which SGP a message is being transmitted/received.
Where the optional Network Appearance parameter is present, it must Where the optional Network Appearance parameter is present, it must
be the first parameter in the message as it defines the format of be the first parameter in the message as it defines the format of
the Protocol Data field the Protocol Data field.
One of two possible Protocol Data parameters are included in a DATA Routing Context: 32-bits (unsigned integer)
message: Protocol Data 1 or Protocol Data 2.
The optional Routing Context parameter contains the Routing Context
value associated with the DATA message. Where multiple Routing
Keys and Routing Contexts are used across a common association, the
Routing Context may identify to the receiver the traffic flow,
assisting in the internal distribution of Data messages.
Protocol Data 1 or 2: variable length Protocol Data 1 or 2: variable length
The Protocol Data 1 parameter contains the original SS7 MTP3 The Protocol Data parameter contains the original SS7 MTP3
message, including the Service Information Octet and Routing Label. message, including the Service Information Octet and Routing Label.
The Protocol Data 1 parameter contains the following fields: The Protocol Data parameter contains the following fields:
Service Information Octet. Includes:
Service Indicator, Service Indicator,
Network Indicator, Network Indicator,
and Spare/Priority codes. Message Priority.
Routing Label. Includes:
Destination Point Code, Destination Point Code,
Originating Point Code, Originating Point Code,
And Signalling Link Selection Code (SLS). Signalling Link Selection Code (SLS).
User Protocol Data. Includes: User Protocol Data. Includes:
MTP3-User protocol elements (e.g., ISUP, SCCP, or TUP MTP3-User protocol elements (e.g., ISUP, SCCP, or TUP
parameters). parameters).
The Protocol Data 2 parameter contains all the information in The Protocol Data parameter is encoded as follows:
Protocol Data 1 as described above, plus the MTP2 Length Indicator
octet. The MTP2 Length Indicator (LI) octet appears before the SIO
and Routing Label information. The MTP2 Length Indicator octet is
required for some national MTP variants that use the spare bits in
the LI to carry additional information of interest to the MTP3 and
MTP3-User (e.g., the Japan TTC standard use of LI spare bits to
indicate message priority)
The Payload Data format is as defined in the relevant MTP standards
for the SS7 protocol being transported. The format is either
implicitly known or identified by the Network Appearance parameter.
Note: In the SS7 Recommendations, the format of the messages and
fields within the messages are based on bit transmission order. In
these recommendations the Least Significant Bit (LSB) of each field
is positioned to the right. The received SS7 fields are populated
octet by octet as received into the 4-octet word as shown in the two
examples below.
For the ANSI protocol example, the Protocol Data 1 field format is
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SIO | DPC Member | DPC Cluster | DPC Network | | Originating Point Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OPC Member | OPC Cluster | OPC Network | SLS | | Destination Point Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SI | NI | MP | SLS |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ Protocol Data / / Protocol Data /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|MSB---------------------------------------------------------LSB| Originating Point Code: 32 bits (unsigned integer)
Destination Point Code: 32 bits (unsigned integer)
Within each octet the Least Significant Bit (LSB) per the SS7 The Originating and Destination Point Code fields contains the OPC
Recommendations is to the right (e.g., bit 7 of SIO is the LSB). and DPC from the routing label of the original SS7 message in
Network Byte Order, justified to the least significant bit. Unused
bits are coded `0'.
For the ITU international protocol example (with the 3/8/3 Point Service Indicator: 8 bits (unsigned integer)
Code format), the Protocol Data 1 field is shown below.
0 1 2 3 The Service Indicator field contains the SI field from the original
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 SS7 message justified to the least significant bit. Unused bits
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ are coded `0'.
| SIO | DPC | DPC |OPC| DPC | DPC | OPC |@|
| | Region *| SP *|SP*|Zone*| reg.| Region *| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SLS | OPC |$| Protocol |
| *|Zone*| | Data |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
* marks LSB of each field; @ = OPC SP MSB; $ = OPC region MSB Network Indicator: 8-bits (unsigned integer)
The Network Indicator contains the NI field from the original SS7
message justified to the least significant bit. Unused bits are
coded `0'.
Message Priority: 8 bits (unsigned integer)
The Message Priority field contains the MP bits (if any) from the
original SS7 message, both for ANSI-style and TTC-style message
priority bits. The MP bits are aligned to the least significant
bit. Unused bits are coded `0'.
Signalling Link Selection: 8 bits (unsigned integer)
The Signalling Link Selection field contains the SLS bits from
the routing label of the original SS7 message justified to the
least significant bit and in Network Byte Order. Unused bits are
coded `0'.
Protocol Data: (variable)
The Protocol Data field contains a byte string of MTP-User
information from the original SS7 message starting with the
first byte of the original SS7 message following the Routing Label.
Correlation Id: 32-bits (unsigned integer)
The Correlation Id parameter uniquely identifies the MSU carried in
the Protocol Data within an AS. This Correlation Id parameter is
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 all SGPs 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 to destinations are unreachable. It is also sent by an SGP in response
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 destination for a certain period to give the remote side time
to react. The MTP3-User at the ASP is expected to stop traffic to the to react. If there is no alternate route via another SG, the
affected destination through the SGPs initiating the DUNA message as MTP3-User at the ASP is expected to stop traffic to the
per the defined MTP3-User procedures. affected destination 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
Affected Destinations Mandatory Routing Context Optional
Affected Point Code Mandatory
INFO String Optional INFO String Optional
The format for DUNA Message parameters is as follows: The format for DUNA Message parameters is as follows:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0200 | Length =8 | | Tag = 0x0200 | Length =8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Network Appearance | | Network Appearance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0203 | Length | | Tag = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mask | Affected DPC 1 | \ \
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0012 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mask | Affected PC 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ ... / / ... /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mask | Affected DPC n | | Mask | Affected PC n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | Length | | Tag = 0x0004 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ INFO String / / INFO String /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Network Appearance: 32-bit unsigned integer Network Appearance: 32-bit unsigned integer
See Section 3.3.1 See Section 3.3.1
Affected Destinations: n x 32-bits Routing Context: n x 32-bits (unsigned integer)
The Affected Destinations parameter contains up to sixteen Affected The optional Routing Context parameter contains the Routing Context
values associated with the DUNA message. Where multiple Routing
Keys and Routing Contexts are used across a common association, the
Routing Context(s) may identify to the receiver the concerned
traffic flows for which the DUNA message applies, assisting in
outgoing traffic management and internal distribution of MTP-PAUSE
indications to MTP3-Users at the receiver.
Affected Point Code: n x 32-bits
The Affected Point Code parameter contains up to sixteen Affected
Destination Point Code fields, each a three-octet parameter to allow Destination Point Code fields, each a three-octet parameter to allow
for 14-, 16- and 24-bit binary formatted SS7 Point Codes. Affected for 14-, 16- and 24-bit binary formatted SS7 Point Codes. Affected
Point Codes that are less than 24-bits, are padded on the left to 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 and ITU the 24-bit boundary. The encoding is shown below for ANSI and ITU
Point Code examples. 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
skipping to change at page 37, line 25 skipping to change at page 38, line 44
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 Destinations parameter with more It is optional to send an Affected Point Code parameter with more
than one Affected DPC but it is mandatory to receive and process it. than one Affected PC but it is mandatory to receive it. All the
All the Affected DPCs included must be within the same Network Affected PCs included must be within the same Routing Context.
Appearance. Including multiple Affected DPCs may be useful when Including multiple Affected PCs may be useful when reception of an
reception of an MTP3 management message or a linkset event MTP3 management message or a linkset event simultaneously affects
simultaneously affects the availability status of a list of the availability status of a list of destinations at an SG.
destinations at an SG.
Mask: 8-bits (unsigned integer) Mask: 8-bits (unsigned integer)
The Mask field associated with each Affected DPC in the Affected The Mask field can be used to identify a contiguous range of
Destinations parameter, used to identify a contiguous range of
Affected Destination Point Codes, independent of the point code Affected Destination Point Codes, independent of the point code
format. Identifying a contiguous range of Affected DPCs may be format. Identifying a contiguous range of Affected DPCs may be
useful when reception of an MTP3 management message or a linkset useful when reception of an MTP3 management message or a linkset
event simultaneously affects the availability status of a series of event simultaneously affects the availability status of a series of
destinations at an SG. For example, if all DPCs in an ANSI cluster destinations at an SG.
are determined to be unavailable due to local linkset
unavailability, the DUNA could identify potentially 256 Affected
DPCs in a single Affected DPC field.
The Mask parameter represents a bit mask that can be applied to the The Mask parameter is an integer representing a bit mask that can be
related Affected DPC field. The bit mask identifies how many bits applied to the related Affected PC field. The bit mask identifies
of the Affected DPC field are significant and which are effectively how many bits of the Affected PC field are significant and which are
"wildcarded". For example, a mask of "8" indicates that the least effectively "wildcarded". For example, a mask of "8" indicates that
significant eight bits of the DPC is "wildcarded". For an ANSI 24- the last eight bits of the PC is "wildcarded". For an ANSI 24-
bit Affected DPC, this is equivalent to signalling that all DPCs in bit Affected PC, this is equivalent to signalling that all PCs in
an ANSI Cluster are unavailable. A mask of "3" indicates that the an ANSI Cluster are unavailable. A mask of "3" indicates that the
least significant three bits of the DPC is "wildcarded". For a 14- last three bits of the PC is "wildcarded". For a 14-bit ITU
bit ITU Affected DPC, this is equivalent to signaling that an ITU Affected PC, this is equivalent to signaling that an ITU
Region is unavailable. A mask value equal to the number of bits in
the DPC indicates that the entire network appearance is affected - Region is unavailable. A mask value equal (or greater than) the
this is used to indicate network isolation to the ASP. number of bits in the PC indicates that the entire network
appearance is affected - this is used to indicate network isolation
to the ASP.
INFO String: variable length INFO String: variable length
The optional INFO String parameter can carry any 8-bit ASCII The optional INFO String parameter can carry any 8-bit ASCII
character string along with the message. Length of the INFO character string along with the message. Length of the INFO
String parameter is from 0 to 255 characters. No procedures are String parameter is from 0 to 255 characters. No procedures are
presently identified for its use but the INFO String MAY be used by presently identified for its use but the INFO String MAY be used by
Operators to identify in text form the location reflected by the Operators to identify in text form the location reflected by the
Affected DPC for debugging purposes. Affected DPC for debugging purposes.
3.4.2 Destination Available (DAVA) 3.4.2 Destination Available (DAVA)
The DAVA message is sent from the SGP to all concerned ASPs to indicate 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 are now that the SG has determined that one or more SS7 destinations are now
reachable (and not restricted), or in response to a DAUD message if reachable (and not restricted), or in response to a DAUD message if
appropriate. The ASP MTP3-User protocol is informed and may now resume appropriate. If the ASP M3UA layer previously had no routes to the
traffic to the affected destination. The ASP M3UA layer routes the affected destinations the ASP MTP3-User protocol is informed and may
MTP3_user traffic through the SGP(s) initiating the DAVA message. now resume traffic to the affected destination. The ASP M3UA layer
now routes the MTP3-user traffic through the SG initiating the DAVA
message.
The DAVA message contains the following parameters: The DAVA message contains the following parameters:
Network Appearance Optional Network Appearance Optional
Affected Destinations Mandatory Routing Context Optional
Affected Point Code Mandatory
INFO String Optional INFO String Optional
The format and description of the Network Appearance, Affected The format and description of the Network Appearance, Routing Context,
Destinations and INFO String parameters is the same as for the DUNA Affected Point Code and INFO String parameters is the same as for the
message (See Section 3.4.1). 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 to one or more affected availability/congestion state of SS7 routes from the SG to one
destinations. or more affected destinations.
The DAUD message contains the following parameters: The DAUD message contains the following parameters:
Network Appearance Optional Network Appearance Optional
Affected Destinations Mandatory Routing Context Optional
Affected Point Code Mandatory
INFO String Optional INFO String Optional
The format and description of DAUD Message parameters is the same as The format and description of DAUD Message parameters is the same as
for the DUNA message (See Section 3.4.1). for the DUNA message (See Section 3.4.1).
3.4.4 SS7 Network Congestion (SCON) 3.4.4 Signalling Congestion (SCON)
The SCON message can be sent from the SGP to all concerned ASPs to
indicate congestion in the SS7 network to one or more destinations, or
to an ASP in response to a DATA or DAUD message as appropriate. For 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
SS7 network to one or more destinations, or to an ASP in response to
a DATA or DAUD message as appropriate. For
some MTP protocol variants (e.g., ANSI MTP) the SCON message may be some MTP protocol variants (e.g., ANSI MTP) the SCON message may be
sent when the SS7 congestion level changes. The SCON message MAY also sent when the SS7 congestion level changes. The SCON message MAY also
be sent from the M3UA layer of an ASP to an M3UA peer indicating that be sent from the M3UA layer of an ASP to an M3UA peer indicating that
the M3UA layer or the ASP is congested. the M3UA layer or the ASP is congested.
The SCON message contains the following parameters: The SCON message contains the following parameters:
Network Appearance Optional Network Appearance Optional
Affected Destinations Mandatory Routing Context Optional
Affected Point Code Mandatory
Concerned Destination Optional Concerned Destination Optional
Congestion Indications Optional Congestion Indications Optional
INFO String Optional INFO String Optional
The format for SCON Message parameters is as follows: The format for SCON Message parameters is as follows:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0200 | Length =8 | | Tag = 0x0200 | Length =8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Network Appearance | | Network Appearance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0203 | Length | | Tag = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mask | Affected DPC 1 | \ \
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0012 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mask | Affected PC 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ ... / / ... /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mask | Affected DPC n | | Mask | Affected PC n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0206 | Length | | Tag = 0x0206 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| reserved | Concerned DPC | | reserved | Concerned DPC |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0205 | Length | | Tag = 0x0205 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | Cong. Level | | Reserved | Cong. Level |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | Length | | Tag = 0x0004 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ INFO String / / INFO String /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format and description of the Network Appearance, Affected The format and description of the Network Appearance, Routing
Destinations, and INFO String parameters is the same as for the DUNA Context, Affected Point Code, and INFO String parameters is the same
message (See Section 3.4.1). as for the DUNA message (See Section 3.4.1).
The Affected Destinations parameter can be used to indicate congestion The Affected Point Code parameter can be used to indicate congestion
of multiple destinations or ranges of destinations. However, an SCON of multiple destinations or ranges of destinations. However, an
message MUST not be delayed to "collect" individual congested SCON message MUST not be delayed to "collect" individual congested
destinations into a single SCON message as any delay might affect the destinations into a single SCON message as any delay might affect
timing of congestion indications to the M3UA Users. One use for the timing of congestion indications to the M3UA Users. One use for
including a range of Congested DPCs is when the SG supports an ANSI including a range of Congested DPCs is when the SG supports an ANSI
cluster route set to the SS7 network that becomes congested due to cluster route set to the SS7 network that becomes congested due to
outgoing link set congestion. outgoing link set congestion.
Concerned Destination: 32-bits Concerned Destination: 32-bits
The optional Concerned Destination parameter is only used if the The optional Concerned Destination parameter is only used if the
SCON message is sent from an ASP to the SGP. It contains the point SCON message is sent from an ASP to the SGP. It contains the point
code of the originator of the message that triggered the SCON code of the originator of the message that triggered the SCON
message. The Concerned Destination parameter contains one Concerned message. The Concerned Destination parameter contains one Concerned
skipping to change at page 40, line 53 skipping to change at page 42, line 44
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 [14,15]. appropriate national MTP recommendations [14,15].
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 an ASP that a remote peer The DUPU message is used by an SGP to inform concerned ASPs that a
MTP3-User Part (e.g., ISUP or SCCP) at an SS7 node is unavailable. remote peer MTP3-User Part (e.g., ISUP or SCCP) at an SS7 node is
unavailable.
The DUPU message contains the following parameters: The DUPU message contains the following parameters:
Network Appearance Optional Network Appearance Optional
Affected Destinations Mandatory Routing Context Optional
Affected Point Code Mandatory
User/Cause Mandatory User/Cause Mandatory
INFO String Optional INFO String Optional
The format for DUPU message parameters is as follows: The format for DUPU message parameters is as follows:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0200 | Length | | Tag = 0x0200 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Network Appearance | | Network Appearance |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0203 | Length = 8 | | Tag = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mask = 0 | Affected DPC | \ \
/ Routing Context /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0012 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Mask = 0 | Affected PC |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0204 | Length = 8 | | Tag = 0x0204 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Cause | User | | Cause | User |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | Length | | Tag = 0x0004 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ INFO String / / INFO String /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
User/Cause: 32-bits User/Cause: 32-bits
The Unavailability Cause and MTP3-User Identity fields, associated The Unavailability Cause and MTP3-User Identity fields, associated
with the Affected DPC in the Affected Destinations 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
skipping to change at page 42, line 28 skipping to change at page 44, line 28
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 Destinations parameter is The format and description of the Affected Point Code parameter is
the same as for the DUNA message (See Section 3.4.1.) except that the the same as for the DUNA message (See Section 3.4.1.) except that
Mask field is not used and only a single Affected DPC is included. the Mask field is not used and only a single Affected DPC is
Ranges and lists of Affected DPCs cannot be signalled in a DUPU included. Ranges and lists of Affected DPCs cannot be signalled in
message, but this is consistent with UPU operation in the SS7 network. a DUPU message, but this is consistent with UPU operation in the
The Affected Destinations parameter in an MTP3 User Part Unavailable SS7 network. The Affected Destinations parameter in an MTP3 User
message (UPU) received by an SGP from the SS7 network contains only one Part Unavailable message (UPU) received by an SGP from the SS7
destination. network contains only one destination.
The format and description of the Network Appearance and INFO String The format and description of the Network Appearance, Routing
parameters is the same as for the DUNA message (See Section 3.4.1). Context, and INFO String parameters is the same as for the DUNA
message (See Section 3.4.1).
3.4.6 Destination Restricted (DRST) 3.4.6 Destination Restricted (DRST)
The DRST message is optionally sent from the SGP to all concerned ASPs The DRST message is optionally sent from the SGP to all concerned 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 now restricted from the point of view of the SGP, or destinations are now restricted from the point of view of the SG, or
in response to a DAUD message if appropriate. The M3UA layer at the ASP in response to a DAUD message if appropriate. The M3UA layer at the ASP
is expected to send traffic to the affected destination via an is expected to send traffic to the affected destination via an
alternate SGP of equal priority, but only if such an alternate route alternate SG with route(s) of equal priority, but only if such an
exists and is available. If the affected destination is currently alternate route exists and is available. If the affected destination
considered unavailable by the ASP, The MTP3-User should be informed is currently considered unavailable by the ASP, The MTP3-User should
that traffic to the affected destination can be resumed. In this case, be informed that traffic to the affected destination can be resumed.
the M3UA layer should route the traffic through the SGP initiating the In this case, the M3UA layer should route the traffic through the SG
DRST message. initiating the DRST message.
This message is optional for the SGP to send and it is optional for the This message is optional for the SG to send and it is optional for the
ASP to act on any information received in the message. It is for use in ASP to act on any information received in the message. It is for use in
the "STP" case described in Section 1.4.1. 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
Affected Destinations Mandatory Routing Context Optional
Affected Point Code Mandatory
INFO String Optional INFO String Optional
The format and description of the Network Appearance, Affected The format and description of the Network Appearance, Routing Context,
Destinations and INFO String parameters is the same as for the DUNA Affected Point Code and INFO String parameters is the same as for the
message (See Section 3.4.1). DUNA message (See Section 3.4.1).
3.5 ASP State Maintenance (ASPSM) Messages 3.5 ASP State Maintenance (ASPSM) Messages
3.5.1 ASP Up 3.5.1 ASP Up
The ASP Up message is used to indicate to a remote M3UA peer that the The ASP Up message is used to indicate to a remote M3UA peer that the
adaptation layer is ready to receive any SSNM or ASPSM/ASPTM messages adaptation layer is ready to receive any SSNM or ASPSM/ASPTM messages
for all 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x000e | Length | | Tag = 0x0011 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ASP Identifier | | ASP Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | Length | | Tag = 0x0004 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ INFO String / / INFO String /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 45, line 15 skipping to change at page 47, line 15
The format and description of the optional INFO String parameter is the The format and description of the optional INFO String parameter is the
same as for the DUNA message (See Section 3.4.1). same as for the DUNA message (See Section 3.4.1).
3.5.4 ASP Down Acknowledgement (ASP Down Ack) 3.5.4 ASP Down Acknowledgement (ASP Down Ack)
The ASP Down Ack message is used to acknowledge an ASP Down message The ASP Down Ack message is used to acknowledge an ASP Down message
received from a remote M3UA peer. received from a remote M3UA peer.
The ASP Down Ack message contains the following parameters: The ASP Down Ack message contains the following parameters:
Reason Mandatory
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
skipping to change at page 46, line 14 skipping to change at page 47, line 45
3.5.5 Heartbeat (BEAT) 3.5.5 Heartbeat (BEAT)
The BEAT message is optionally used to ensure that the M3UA peers The BEAT message is optionally used to ensure that the M3UA peers
are still available to each other. It is recommended for use when the are still available to each other. It is recommended for use when the
M3UA runs over a transport layer other than the SCTP, which has its own M3UA runs over a transport layer other than the SCTP, which has its own
heartbeat. heartbeat.
The BEAT message contains the following parameters: The BEAT message contains the following parameters:
Heatbeat 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 48, line 12 skipping to change at page 50, line 12
message. This is used to allow the registration of multiple Routing message. This is used to allow the registration of multiple Routing
Keys in a single message. Keys in a single message.
The format of the Routing Key parameter is as follows. The format of the Routing Key parameter is as follows.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local-RK-Identifier | | Local-RK-Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Traffic Mode Type | | Traffic Mode Type (optional) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination Point Code | | Destination Point Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Network Appearance (optional) | | Network Appearance (optional) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SI (optional) | | Service Indicators (optional) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSN (optional) | | Originating Point Code List (optional) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Origination Point Code List (optional) | | Circuit Range List (optional) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ ... /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Destination Point Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Network Appearance (optional) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Service Indicators (optional) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Originating Point Code List (optional) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Circuit Range List (optional) | | Circuit Range List (optional) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Local-RK-Identifier: 32-bit integer Local-RK-Identifier: 32-bit integer
The mandatory Local-RK-Identifier field is used to uniquely identify The mandatory Local-RK-Identifier field is used to uniquely identify
the registration request. The Identifier value is assigned by the the registration request. The Identifier value is assigned by the
ASP, and is used to correlate the response in an REG RSP message ASP, and is used to correlate the response in an REG RSP message
with the original registration request. The Identifier value must with the original registration request. The Identifier value must
skipping to change at page 48, line 47 skipping to change at page 51, line 17
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x020a | Length = 8 | | Tag = 0x020a | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local-RK-Identifier value | | Local-RK-Identifier value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Traffic Mode Type: 32-bit (unsigned integer) Traffic Mode Type: 32-bit (unsigned integer)
The Traffic Mode Type parameter is mandatory and identifies the The optional Traffic Mode Type parameter identifies the traffic mode
traffic mode of operation of the ASP(s) within an Application of operation of the ASP(s) within an Application Server. The format
Server. The valid values for Traffic Mode Type are shown in the of the Traffic Mode Type Identifier is as follows:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x000b | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Traffic Mode Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The valid values for Traffic Mode Type are shown in the
following table: following table:
1 Over-ride 1 Override
2 Load-share 2 Loadshare
3 Broadcast 3 Broadcast
If the receiver of the REG REQ creates a new Routing Key entry, then If the receiver of the REG REQ creates a new Routing Key entry, then
the Traffic Mode Type sets the traffic mode for the new Application the Traffic Mode Type sets the traffic mode for the new Application
Server. If the receiver of the REG REQ determines that a matching Server. If the receiver of the REG REQ determines that a matching
Routing Key already exists, the Traffic Mode Type MUST match the Routing Key already exists, the Traffic Mode Type MUST match the
existing traffic mode for the AS. existing traffic mode for the AS.
Destination Point Code: Destination Point Code:
skipping to change at page 50, line 17 skipping to change at page 52, line 43
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Subsystem Numbers (SSN): n X 8-bit integers
The optional SSN field contains one or more SCCP subsystem numbers,
and is used in conjunction with an SI values of 3 (i.e., SCCP) only.
The absence of the SSN parameter in the Routing Key indicates the
use of any SSN value, in the case of SCCP traffic. Where an SSN
parameter does not contain a multiple of four SSNs, the parameter is
padded out to 32-byte alignment. The subsystem number values
associated are defined by the local network operator, and typically
follow ITU-T Recommendation Q.713 [5]. An SSN value of zero is not
valid in M3UA. The format of this field is as follows:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x020d | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSN #1 | SSN #2 | SSN #3 | SSN #4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ ... /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSN #n | 0 Padding, if necessary |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
OPC List: OPC List:
The Originating Point Code List parameter contains one or more SS7 The Originating Point Code List parameter contains one or more SS7
OPC entries, and its format is the same as the Destination Point OPC entries, and its format is the same as the Destination Point
Code parameter. The absence of the OPC List parameter in the Code parameter. The absence of the OPC List parameter in the
Routing Key indicates the use of any OPC value, Routing Key indicates the use of any OPC value,
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x020e | Length | | Tag = 0x020e | Length |
skipping to change at page 52, line 38 skipping to change at page 54, line 38
/ ... / / ... /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0208 | Length | | Tag = 0x0208 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Registration Result n | | Registration Result n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Registration Results: Registration Results:
The Registration Result parameter contains the registration status 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 MAY be anywhere from one to the results in a single REG RSP message MAY be anywhere from one to the
total number of number of Routing Key parameters found in the total number of number of Routing Key parameters found in the
corresponding REG REQ message. Where multiple REG RSP messages are corresponding REG REQ message. Where multiple REG RSP messages are
used in reply to REG REQ message, a specific result SHOULD be in 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 follows: only one REG RSP message. The format of each result is as follows:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x020a | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local-RK-Identifier value | | Local-RK-Identifier value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0212 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Registration Status | | Registration Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0006 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Routing Context | | Routing Context |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Local-RK-Identifier: 32-bit integer Local-RK-Identifier: 32-bit integer
The Local-RK-Identifier contains the same value as found in the The Local-RK-Identifier contains the same value as found in the
matching Routing Key parameter found in the REG REQ message (See matching Routing Key parameter found in the REG REQ message (See
Section 3.5.5.1). Section 3.5.5.1).
Registration Status: 32-bit integer Registration Status: 32-bit integer
skipping to change at page 53, line 30 skipping to change at page 56, line 5
8 Error - Insufficient Resources 8 Error - Insufficient Resources
9 Error - Unsupported RK parameter Field 9 Error - Unsupported RK parameter Field
10 Error - Unsupported/Invalid Traffic Handling Mode 10 Error - Unsupported/Invalid Traffic Handling Mode
Routing Context: 32-bit integer Routing Context: 32-bit integer
The Routing Context field contains the Routing Context value for the The Routing Context field contains the Routing Context value for the
associated Routing Key if the registration was successful. It is set associated Routing Key if the registration was successful. It is set
to "0" if the registration was not successful. to "0" if the registration was not successful.
3.6.3 De-Registration 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 de-register 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
skipping to change at page 54, line 11 skipping to change at page 56, line 34
/ Routing Context / / Routing Context /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Routing Context: n X 32-bit integers Routing Context: n X 32-bit integers
The Routing Context parameter contains (a list of) integers indexing The Routing Context parameter contains (a list of) integers indexing
the Application Server traffic that the sending ASP is currently the Application Server traffic that the sending ASP is currently
registered to receive from the SGP but now wishes to deregister. registered to receive from the SGP but now wishes to deregister.
3.6.4 De-Registration Response (DEREG RSP) 3.6.4 Deregistration Response (DEREG RSP)
The DEREG RSP message is used as a response to the DEREG REQ message The DEREG RSP message is used as a response to the DEREG REQ message
from a remote M3UA peer. from a remote M3UA peer.
The DEREG RSP message contains the following parameters: The DEREG RSP message contains the following parameters:
De-registration Result Mandatory Deregistration Result Mandatory
One or more De-registration Result parameters MAY be included. The One or more Deregistration Result parameters MAY 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| De-Registration Result 1 | | Deregistration Result 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ ... / / ... /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0209 | Length | | Tag = 0x0209 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| De-Registration Result n | | Deregistration Result n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
De-Registration Results: Deregistration Results:
The De-Registration Result parameter contains the de-registration The Deregistration Result parameter contains the deregistration
status for a single Routing Context in a DEREG REQ message. The status for a single Routing Context in a DEREG REQ message. The
number of results in a single DEREG RSP message MAY be anywhere from number of results in a single DEREG RSP message MAY be anywhere from
one to the total number of number of Routing Context values found in one to the total number of number of Routing Context values found in
the corresponding REG REQ message. Where multiple DEREG RSP messages the corresponding REG REQ message. Where multiple DEREG RSP messages
are used in reply to DEREG REQ message, a specific result SHOULD be are used in reply to DEREG REQ message, a specific result SHOULD be
in only one DEREG RSP message. The format of each result is as in only one DEREG RSP message. The format of each result is as
follows: follows:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0006 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Routing Context | | Routing Context |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| De-Registration Status | | Tag = 0x0213 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Deregistration Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Routing Context: 32-bit integer Routing Context: 32-bit integer
The Routing Context field contains the Routing Context value of the The Routing Context field contains the Routing Context value of the
matching Routing Key to deregister, as found in the DEREG REQ matching Routing Key to deregister, as found in the DEREG REQ
message. message.
De-Registration Status: 32-bit integer Deregistration Status: 32-bit integer
The De-Registration Result Status field indicates the success or the The Deregistration Result Status field indicates the success or the
reason for failure of the de-registration. reason for failure of the deregistration.
Its values may be: Its values may be:
0 Successfully De-registered 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 state Application Server. The ASP Active message affects only the ASP state
for the Routing Keys identified by the Routing Contexts, if present. for the Routing Keys identified by the Routing Contexts, if present.
The ASP Active message contains the following parameters: The ASP Active message contains the following parameters:
Traffic Mode Type Mandatory Traffic Mode Type Optional
Routing Context Optional Routing Context Optional
INFO String Optional INFO String Optional
The format for the ASP Active message is as follows: The format for the ASP Active message is as follows:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x000b | Length | | Tag = 0x000b | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Traffic Mode Type | | Traffic Mode Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0006 | Length | | Tag = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ Routing Context / / Routing Context /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | Length | | Tag = 0x0004 | Length |
skipping to change at page 56, line 33 skipping to change at page 59, line 5
/ INFO String / / INFO String /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Traffic Mode Type: 32-bit (unsigned integer) Traffic Mode Type: 32-bit (unsigned integer)
The Traffic Mode Type parameter identifies the traffic mode of The Traffic Mode Type parameter identifies the traffic mode of
operation of the ASP within an AS. The valid values for Traffic Mode operation of the ASP within an AS. The valid values for Traffic Mode
Type are shown in the following table: Type are shown in the following table:
1 Over-ride 1 Override
2 Load-share 2 Loadshare
3 Broadcast 3 Broadcast
5 Over-ride (Standby)
6 Load-share (Standby)
7 Broadcst (Standby)
Within a particular Routing Context, Over-ride,Load-share and Within a particular Routing Context, Override, Loadshare and
Broadcast, either active or standby, MUST NOT be mixed. The Over- Broadcast MUST NOT be mixed. The Override value indicates that the
ride value indicates that the ASP is operating in Over-ride mode, ASP is operating in Override mode, and the ASP takes over all
and the ASP takes over all traffic in an Application Server (i.e., traffic in an Application Server (i.e., primary/backup operation),
primary/back-up operation), over-riding any currently active ASPs in overriding any currently active ASPs in the AS. In Loadshare mode,
the AS. In Load-share mode, the ASP will share in the traffic the ASP will share in the traffic distribution with any other
distribution with any other currently active ASPs. In Broadcast currently active ASPs. In Broadcast mode, the ASP will receive the
mode, the ASP will receive the same messages as any other currently same messages as any other currently active ASP.
active ASP. The Standby versions of the Over-ride, Load-share and
Broadcast Types indicate that the ASP is declaring itself ready to
accept traffic but leaves it up to the sender as to when the traffic
is started. Over-ride (Standby) indicates that the traffic sender
continues to use the currently active ASP until it can no longer
send/receive traffic (i.e., the currently active ASP transitions to
state ASP-DOWN or ASP-INACTIVE). At this point the sender MUST move
the standby ASP to the ASP-ACTIVE state and commence traffic. Load-
share (Standby) and Broadcast (Standby) are similar - the sender
continues to load-share or broadcast to the current ASPs until it is
determined
that there is insufficient resources in the Load-share or Broadcast
group. When there are insufficient ASPs, the sender MUST move the
ASP to state ASP-ACTIVE.
Routing Context: n X 32-bit integers Routing Context: n X 32-bit integers
The optional Routing Context parameter contains (a list of) integers The optional Routing Context parameter contains (a list of) integers
indexing the Application Server traffic that the sending ASP is indexing the Application Server traffic that the sending ASP is
configured/registered to receive. configured/registered to receive.
There is one-to-one relationship between an index entry and an SGP There is one-to-one relationship between an index entry and an SGP
Routing Key or AS Name. Because an AS can only appear in one Routing Key or AS Name. Because an AS can only appear in one
Network Appearance, the Network Appearance parameter is not required Network Appearance, the Network Appearance parameter is not required
skipping to change at page 57, line 33 skipping to change at page 59, line 43
example, an ASP could be configured to support call processing for example, an ASP could be configured to support call processing for
multiple ranges of PSTN trunks and therefore receive related multiple ranges of PSTN trunks and therefore receive related
signalling traffic, identified by separate SS7 DPC/OPC/CIC ranges. signalling traffic, identified by separate SS7 DPC/OPC/CIC ranges.
The format and description of the optional INFO String parameter is the The format and description of the optional INFO String parameter is the
same as for the DUNA message (See Section 3.4.1). same as for the DUNA message (See Section 3.4.1).
3.7.2 ASP Active Acknowledgement (ASP Active Ack) 3.7.2 ASP Active Acknowledgement (ASP Active Ack)
The ASP Active Ack message is used to acknowledge an ASP Active message The ASP Active Ack message is used to acknowledge an ASP Active message
received from a remote M3UA peer. In the case where an ASP Active received from a remote M3UA peer.
(Over-ride (standby)), ASP Active (Load-share (standby)) or ASP Active
(Broadcast (standby)) message is
received, a second ASP Active Ack message is sent when the ASP is moved
from the ASP-STANDBY to the ASP-ACTIVE state.
The ASP Active Ack message contains the following parameters: The ASP Active Ack message contains the following parameters:
Traffic Mode Type Mandatory Traffic Mode Type Optional
Routing Context Optional Routing Context Optional
INFO String Optional INFO String Optional
The format for the ASP Active Ack message is as follows: The format for the ASP Active Ack message is as follows:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x000b | Length | | Tag = 0x000b | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Traffic Mode Type | | Traffic Mode Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0006 | Length | | Tag = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ Routing Context / / Routing Context /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | Length | | Tag = 0x0004 | Length |
skipping to change at page 60, line 34 skipping to change at page 62, line 34
The Error message contains the following parameters: The Error message contains the following parameters:
Error Code Mandatory Error Code Mandatory
Diagnostic Information Optional Diagnostic Information Optional
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 | | Tag = 0x000c | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Error Code | | Error Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 Message. The Error Code parameter indicates the reason for the Error Message.
The Error parameter value can be one of the following values: The Error parameter value can be one of the following values:
1 Invalid Version 0x01 Invalid Version
2 Invalid Network Appearance 0x02 Not Used in M3UA
3 Unsupported Message Class 0x03 Unsupported Message Class
4 Unsupported Message Type 0x04 Unsupported Message Type
5 Unsupported/Invalid Traffic Handling Mode 0x05 Unsupported Traffic Handling Mode
6 Unexpected Message 0x06 Unexpected Message
7 Protocol Error 0x07 Protocol Error
8 Invalid Routing Context 0x08 Not used in M3UA
9 Invalid Stream Identifier 0x09 Invalid Stream Identifier
10 Invalid Parameter Value 0x0a Not used in M3UA
11 Refused - Management Blocking 0x0b Not used in M3UA
12 Unknown Routing Context 0x0c Not used in M3UA
13 Missing, Duplicated or Invalid ASP Identifier 0x0d Refused - Management Blocking
0x0e ASP Identifier Required
0x0f Invalid ASP Identifier
0x10 Invalid Routing Context
0x11 Invalid Parameter Value
0x12 Parameter Field Error
0x13 Unexpected Parameter
0x14 Destination Status Unknown
0x15 Invalid Network Appearance
The "Invalid Version" error is sent if a message was received with an The "Invalid Version" error is sent if a message was received with an
invalid or unsupported version. The Error message contains the invalid or unsupported version. The Error message contains the
supported version in the Common header. The Error message could supported version in the Common header. The Error message could
optionally provide the supported version in the Diagnostic Information optionally provide the supported version in the Diagnostic Information
area. area.
The "Invalid Network Appearance" error is sent by a SGP if an ASP sends The "Invalid Network Appearance" error is sent by a SGP if an ASP sends
a message with an invalid (unconfigured) Network Appearance value. a message with an invalid (unconfigured) Network Appearance value.
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. unexpected or unsupported Message Class is received.
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. unexpected or unsupported Message Type is received.
The "Unsupported/Invalid Traffic Handling Mode" error is sent by a SGP The "Unsupported Traffic Handling Mode" error is sent by a SGP
if an ASP sends an ASP Active message with an unsupported Traffic Mode if an ASP sends an ASP Active message with an unsupported Traffic Mode
Type or a Traffic Mode Type that is inconsistent with the presently Type or a Traffic Mode Type that is inconsistent with the presently
configured mode for the Application Server. An example would be a case configured mode for the Application Server. An example would be a case
in which the SGP did not support load-sharing. in which the SGP did not support loadsharing.
The "Unexpected Message" error MAY be sent if a defined and recognized The "Unexpected Message" error MAY be sent if a defined and recognized
message is received that is not expected in the current state (in some message is received that is not expected in the current state (in some
cases the ASP may optionally silently discard the message and not send cases the ASP may optionally silently discard the message and not send
an Error message). For example, silent discard is used by an ASP if it an Error message). For example, silent discard is used by an ASP if it
received a DATA message from an SGP while it was in the ASP-INACTIVE received a DATA message from an SGP while it was in the ASP-INACTIVE
state. state.
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 reception of a parameter that is syntactically correct but unexpected
in the current situation. in the current situation.
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. from a peer with an invalid (unconfigured) Routing Context value, or
if a message is received from a peer without a Routing Context
parameter and it is not known by configuration data which
Application Servers are referenced.
The "Invalid Stream Identifier" error is sent if a message is received 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"). on a stream other than "0").
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 with an invalid parameter value (e.g., a DUPU message was received with
a Mask value other than "0"). a Mask value 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 lock-out"). management reasons (e.g., management lockout").
The "Unknown Routing Context" Error is sent if a message is received The "ASP Identifier Required" is sent by a SGP in response
from a peer without a Routing Context parameter and it is not known by to an ASP Up message which does not contain an ASP Identifier
configuration data which Application Servers are referenced. parameter when the SGP requires one. The ASP should resend the
ASP Up message with an ASP Identifier.
The "Refused - Missing, Duplicated or Invalid ASP Identifier" error is The "Invalid ASP Identifier" is send by a SGP in response
sent when an ASP-Up message is received and the request is refused to an ASP Up message with an invalid (i.e., non-unique) ASP Identifier.
because an ASP ID is required, or the value is invalid/duplicated.
The "Destination Status Unknown" Error MAY be sent if a DAUD is
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.,
the sender is not authorized to know the status).
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. In the case of an Invalid identification of the error condition. In the case of an Invalid
Network Appearance, Traffic Handling Mode, Routing Context or Network Appearance, Traffic Handling Mode, Routing Context or
Parameter Value, the Diagnostic information parameter MUST be added Parameter Value, the Diagnostic information parameter MUST be added
and include the offending parameter. In the other cases, the and include the offending parameter. In the case of Destination
Status Unknown, the Diagnostic information SHOULD include the Point
Code in the original DAUD request. In the other cases, the
Diagnostic information MAY be the first 40 bytes of the offending Diagnostic information MAY be the first 40 bytes of the offending
message. message.
Error messages MUST NOT be generated in response to other Error Error messages MUST NOT be generated in response to other Error
messages. messages.
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.
skipping to change at page 63, line 10 skipping to change at page 65, line 22
Status Mandatory Status Mandatory
ASP Identifier Optional ASP Identifier Optional
Routing Context Optional Routing Context Optional
INFO String Optional INFO String Optional
The format for the Notify message is as follows: The format for the Notify message is as follows:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x000d | Length | | Tag = 0x000d | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Status Type | Status Information | | Status Type | Status Information |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x000e | Length | | Tag = 0x0011 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ASP Identifier | | ASP Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0006 | Length | | Tag = 0x0006 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ Routing Context / / Routing Context /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0004 | Length | | Tag = 0x0004 | Length |
skipping to change at page 64, line 10 skipping to change at page 66, line 22
These notifications are sent from an SGP to an ASP upon a change in These notifications are sent from an SGP to an ASP upon a change in
status of a particular Application Server. The value reflects the status of a particular Application Server. The value reflects the
new state of the Application Server. new state of the Application Server.
If the Status Type is Other, then the following Status Information If the Status Type is Other, then the following Status Information
values are defined: values are defined:
1 Insufficient ASP Resources Active in AS 1 Insufficient ASP Resources Active in AS
2 Alternate ASP Active 2 Alternate ASP Active
3 ASP Failure
These notifications are not based on the SGP reporting the state change These notifications are not based on the SGP reporting the state change
of an ASP or AS. In the Insufficent ASP Resources case, the SGP is of an ASP or AS. In the Insufficent ASP Resources case, the SGP is
indicating to an ASP_INACTIVE ASP in the AS that another ASP is indicating to an ASP_INACTIVE ASP in the AS that another ASP is
required to handle the load of the AS (Load-sharing or Broadcast mode). required to handle the load of the AS (Loadsharing or Broadcast mode).
For the Alternate ASP Active case, an ASP is informed when an alternate For the Alternate ASP Active case, an ASP is informed when an alternate
ASP transitions to the ASP-ACTIVE state in Over-ride mode. ASP transitions to the ASP-ACTIVE state in Override mode.
The format and description of the optional ASP Identifier, Routing The format and description of the optional ASP Identifier, Routing
Context and Info String parameters is the same as for the ASP Active Context and Info String parameters is the same as for the ASP Active
message (See Section 3.5.5.) message (See Section 3.5.5.)
4. Procedures 4. Procedures
The M3UA layer needs to respond to various local primitives it receives The M3UA layer needs to respond to various local primitives it receives
from other layers as well as the messages that it receives from the from other layers as well as the messages that it receives from the
peer M3UA layer. This section describes the M3UA procedures in peer M3UA layer. This section describes the M3UA procedures in
response to these events. response to these events.
4.1 Procedures to Support the M3UA-User and Layer Management Layers 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 inter-working function at an SGP, the M3UA an ASP/IPSP, or the nodal interworking function at an SGP, the M3UA
layer sends a corresponding DATA message (see Section 3) to its M3UA layer sends a corresponding DATA message (see Section 3) to its M3UA
peer. The M3UA peer receiving the DATA message sends an MTP-TRANSFER peer. The M3UA peer receiving the DATA message sends an MTP-TRANSFER
indication primitive to the upper layer. indication primitive to the upper layer.
The M3UA message distribution function (see Section 1.4.2.1) determines The M3UA message distribution function (see Section 1.4.2.1) determines
the Application Server (AS) based on comparing the information in the the Application Server (AS) based on comparing the information in the
MTP-TRANSFER request primitive with a provisioned Routing Key. MTP-TRANSFER request primitive with a provisioned 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 load-shared 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 selection selected and the message sent to each of the active ASPs. The
algorithm is implementation dependent but could, selection algorithm is implementation dependent but could, for
for example, be round-robin or based on, for example, the SLS or ISUP example, be round-robin or based on the SLS or ISUP CIC. The a
CIC. The appropriate selection algorithm must be chosen carefully as appropriate selection algorithm must be chosen carefully as it is
it is dependent on application assumptions and understanding of the dependent on application assumptions and understanding of the
degree of state coordination between the ASP_ACTIVE ASPs in the AS. degree 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. signalling application. DATA messages SHOULD be sent on an SCTP stream
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 MUST be specified. Possible incoming SS7 message, a default treatment MUST 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 is M-ERROR indication primitive. The treatment of unallocated traffic is
implementation dependent. implementation dependent.
4.1.2 Receipt of Primitives from the Layer Management 4.1.2 Receipt of Primitives from the Layer Management
skipping to change at page 65, line 33 skipping to change at page 67, line 47
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.
When an SCTP association has been successfully established, the SCTP When an SCTP association has been successfully established, the SCTP
will send an SCTP-COMMUNICATION_UP notification primitive to the local will send an SCTP-COMMUNICATION_UP notification primitive to the local
M3UA layer. At the SGP or IPSP that initiated the request, the M3UA M3UA layer. At the SGP or IPSP that initiated the request, the M3UA
layer will send an M-SCTP_ESTABLISH confirm primitive to Layer layer will send an M-SCTP_ESTABLISH confirm primitive to Layer
Management when the association set-up is complete. At the peer M3UA Management when the association setup is complete. At the peer M3UA
layer, an M-SCTP_ESTABLISH indication primitive is sent to Layer layer, an M-SCTP_ESTABLISH indication primitive is sent to Layer
Management upon successful completion of an incoming SCTP association Management upon successful completion of an incoming SCTP association
set-up. setup.
An M-SCTP_RELEASE request primitive from Layer Management initates the An M-SCTP_RELEASE request primitive from Layer Management initiates the
tear-down of an SCTP association. The M3UA layer accomplishes a teardown of an SCTP association. The M3UA layer accomplishes a
graceful shutdown of the SCTP association by sending an SCTP-SHUTDOWN graceful shutdown of the SCTP association by sending an SCTP-SHUTDOWN
primitive to the SCTP layer. primitive to the SCTP layer.
When the graceful shutdown of the SCTP association has been When the graceful shutdown of the SCTP association has been
accomplished, the SCTP layer returns an SCTP-SHUTDOWN_COMPLETE accomplished, the SCTP layer returns an SCTP-SHUTDOWN_COMPLETE
notification primitive to the local M3UA layer. At the M3UA Layer that notification primitive to the local M3UA layer. At the M3UA Layer that
initiated the request, the M3UA layer will send an M-SCTP_RELEASE initiated the request, the M3UA layer will send an M-SCTP_RELEASE
confirm primitive to Layer Management when the association teardown is confirm primitive to Layer Management when the association shutdown
complete. At the peer M3UA Layer, an M-SCTP_RELEASE indication is complete. At the peer M3UA Layer, an M-SCTP_RELEASE indication
primitive is sent to Layer Management upon successful tear-down of an primitive is sent to Layer Management upon abort or successful
SCTP association. shutdown of an SCTP association.
An M-SCTP_STATUS request primitive supports a Layer Management query of An M-SCTP_STATUS request primitive supports a Layer Management query of
the local status of a particular SCTP association. The M3UA layer 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 mappings Similar LM-to-M3UA-to-SCTP and/or SCTP-to-M3UA-to-LM primitive mappings
skipping to change at page 66, line 37 skipping to change at page 68, line 50
An M-AS_STATUS request supports a Layer Management query of the status An M-AS_STATUS request supports a Layer Management query of the status
of a particular AS. The M3UA responds with an M-AS_STATUS confirm of a particular AS. The M3UA responds with an M-AS_STATUS confirm
primitive. No M3UA peer protocol is invoked. primitive. No M3UA peer protocol is invoked.
M-ASP_UP request, M-ASP_DOWN request, M-ASP_ACTIVE request and M-ASP_ M-ASP_UP request, M-ASP_DOWN request, M-ASP_ACTIVE request and M-ASP_
INACTIVE request primitives allow Layer Management at an ASP to INACTIVE request primitives allow Layer Management at an ASP to
initiate state changes. Upon successful completion, a corresponding initiate state changes. Upon successful completion, a corresponding
confirm primitive is provided by the M3UA layer to Layer Management. confirm primitive is provided by the M3UA layer to Layer Management.
If an invocation is unsuccessful, an Error indication primitive is If an invocation is unsuccessful, an Error indication primitive is
provided in the primitive. provided in the primitive. These requests result in outgoing ASP Up,
ASP Down, ASP Active and ASP Inactive messages to the remote M3UA
peer at an SGP or IPSP.
These requests result in outgoing ASP Up, ASP Down, ASP Active and 4.2 Procedures to Support the Management of SCTP Associations
ASP Inactive messages to the remote M3UA peer at an SGP or IPSP.
4.1.3 Receipt of M3UA Peer Management Messages 4.2.1 Receipt of M3UA Peer Management Messages
Upon successful state changes resulting from reception of ASP Up, Upon successful state changes resulting from reception of ASP Up,
ASP Down, ASP Active and ASP Inactive messages from a peer M3UA, the ASP Down, ASP Active and ASP Inactive messages from a peer M3UA, the
M3UA layer SHOULD invoke corresponding M-ASP_UP, M-ASP_DOWN, M- M3UA layer SHOULD invoke corresponding M-ASP_UP, M-ASP_DOWN, M-
ASP_ACTIVE and M-ASP_INACTIVE, M-AS_ACTIVE, M-AS_INACTIVE, and M- ASP_ACTIVE and M-ASP_INACTIVE, M-AS_ACTIVE, M-AS_INACTIVE, and M-
AS_DOWN indication primitives to the local Layer Management. AS_DOWN indication primitives to the local Layer Management.
M-NOTIFY indication and M-ERROR indication primitives indicate to Layer M-NOTIFY indication and M-ERROR indication primitives indicate to Layer
Management the notification or error information contained in a Management the notification or error information contained in a
received 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.
4.2 Procedures to Support the Management of SCTP Associations with M3UA All Non-Transfer messages, except BEAT and BEAT Ack, SHOULD be sent
Peers with sequenced delivery to ensure ordering. All Non-Transfer
messages, with the exception of ASPTM, BEAT and BEAT Ack messages,
These procedures support the M3UA management of SCTP Associations SHOULD be sent on SCTP stream '0'. ASPTM messages MAY be sent on
between SGPs and ASPs or between IPSPs. one of the streams used to carry the data traffic related to the
Routing Context(s), to minimize possible message loss. BEAT and
BEAT Ack messages MAY be sent using out-of-order delivery, and MAY
be sent on any stream.
4.2.1 AS and ASP State Maintenance 4.3 AS and ASP State Maintenance
The M3UA layer on the SGP maintains the state of each remote ASP, in The M3UA layer on the SGP maintains the state of each remote ASP, in
each Application Server that the ASP is configured to receive traffic, each Application Server that the ASP is configured to receive traffic,
as input to the M3UA message distribution function. Similarly, where as input to the M3UA message distribution function. Similarly, where
IPSPs use M3UA in a point-to-point fashion, the M3UA layer in an IPSP IPSPs use M3UA in a point-to-point fashion, the M3UA layer in an IPSP
maintains the state of remote IPSPs. For the purposes of the following maintains the state of remote IPSPs. For the purposes of the following
procedures, only the SGP/ASP case is described but the SGP side of the procedures, only the SGP/ASP case is described but the SGP side of the
procedures also apply to an IPSP sending traffic to an AS consisting of procedures also apply to an IPSP sending traffic to an AS consisting of
a set of remote IPSPs. a set of remote IPSPs.
4.2.1.1 ASP States 4.3.1 ASP States
The state of each remote ASP, in each AS that it is configured to The state of each remote ASP, in each AS that it is configured to
operate, is maintained in the M3UA layer in the SGP. The state of a operate, is maintained in the M3UA layer in the SGP. The state of a
particular ASP in a particular AS changes due to events. The events particular ASP in a particular AS changes due to events. The events
include: include:
* Reception of messages from the peer M3UA layer at the ASP; * Reception of messages from the peer M3UA layer at the ASP;
* Reception of some messages from the peer M3UA layer at other ASPs * Reception of some messages from the peer M3UA layer at other ASPs
in the AS (e.g., ASP Active message indicating "Over-ride"); in the AS (e.g., ASP Active message indicating "Override");
* Reception of indications from the SCTP layer; or * Reception of indications from the SCTP layer; or
* Local Management intervention. * Local Management intervention.
The ASP state transition diagram is shown in Figure 4. The possible The ASP state transition diagram is shown in Figure 4. The possible
states of an ASP are: states of an ASP are:
ASP-DOWN: The remote M3UA peer at the ASP is unavailable and/or the ASP-DOWN: The remote M3UA peer at the ASP is unavailable and/or the
related SCTP association is down. Initially all ASPs will be in this related SCTP association is down. Initially all ASPs will be in this
state. An ASP in this state SHOULD NOT be sent any M3UA messages. state. An ASP in this state SHOULD NOT be sent any M3UA messages,
with the exception of Heartbeat messages.
ASP-INACTIVE: The remote M3UA peer at the ASP is available (and the ASP-INACTIVE: The remote M3UA peer at the ASP is available (and the
related SCTP association is up) but application traffic is stopped. In related SCTP association is up) but application traffic is stopped. In
this state the ASP MAY be sent any non-DATA M3UA messages. this state the ASP MAY be sent any non-DATA M3UA messages.
ASP-ACTIVE: The remote M3UA peer at the ASP is available and ASP-ACTIVE: The remote M3UA peer at the ASP is available and
application traffic is active (for a particular Routing Context or set application traffic is active (for a particular Routing Context or set
of Routing Contexts). of Routing Contexts).
ASP-STANDBY: The remote M3UA peer at the ASP is available and ready to Figure 4: ASP State Transition Diagram, per AS
receive application traffic at any time (for a particular Routing
Context or set of Routing Contexts). In this state the ASP MAY be sent
any non-Data M3UA messages.
Figure 4: ASP State Transition Diagram
+--------------+ +--------------+
| ASP-ACTIVE | | |
+----------------------| or | +----------------------| ASP-ACTIVE |
| Other +-------| ASP-STANDBY* | | Other +-------| |
| ASP in AS | +--------------+ | ASP in AS | +--------------+
| Overrides | ^ | | Overrides | ^ |
| | ASP | | ASP | | ASP | | ASP
| | Active | | Inactive | | Active | | Inactive
| | | v | | | v
| | +--------------+ | | +--------------+
| | | | | | | |
| +------>| ASP-INACTIVE | | +------>| ASP-INACTIVE |
| +--------------+ | +--------------+
| ^ | | ^ |
ASP Down/ | ASP | | ASP Down / ASP Down/ | ASP | | ASP Down /
SCTP CDI/ | Up | | SCTP CDI/ SCTP CDI/ | Up | | SCTP CDI/
SCTP RI | | v SCTP RI SCTP RI | | v SCTP RI
| +--------------+ | +--------------+
| | | | | |
+--------------------->| ASP-DOWN | +--------------------->| ASP-DOWN |
| | | |
+--------------+ +--------------+
*Note: ASP-ACTIVE and ASP-STANDBY differ only in whether the ASP is
currently receiving Data traffic within the AS.
SCTP CDI: The SCTP CDI denotes the local SCTP layer's Communication SCTP CDI: The SCTP CDI denotes the local SCTP layer's Communication
Down Indication to the Upper Layer Protocol (M3UA) on an SGP. The local Down Indication to the Upper Layer Protocol (M3UA) on an SGP. The local
SCTP layer will send this indication when it detects the loss of SCTP layer will send this indication when it detects the loss of
connectivity to the ASP's peer SCTP layer. SCTP CDI is understood as connectivity to the ASP's peer SCTP layer. SCTP CDI is understood as
either a SHUTDOWN_COMPLETE notification or COMMUNICATION_LOST either a SHUTDOWN_COMPLETE notification or COMMUNICATION_LOST
notification from the SCTP layer. notification from the SCTP layer.
SCTP RI: The local SCTP layer's Restart indication to the upper layer SCTP RI: The local SCTP layer's Restart indication to the upper layer
protocol (M3UA) on an SG. The local SCTP will send this indication when protocol (M3UA) on an SG. The local SCTP will send this indication
it detects a restart from the ASP's peer SCTP layer. when it detects a restart from the ASP's peer SCTP layer.
4.2.1.2 AS States 4.3.2 AS States
The state of the AS is maintained in the M3UA layer on the SGP. The The state of the AS is maintained in the M3UA layer on the SGP. The
state of an AS changes due to events. These events include: state of an AS changes due to events. These events include:
* ASP state transitions * ASP state transitions
* Recovery timer triggers * Recovery timer triggers
The possible states of an AS are: The possible states of an AS are:
AS-DOWN: The Application Server is unavailable. This state implies AS-DOWN: The Application Server is unavailable. This state implies
that all related ASPs are in the ASP-DOWN state for this AS. Initially that all related ASPs are in the ASP-DOWN state for this AS. Initially
the AS will be in this state. An Application Server MUST be in the AS- the AS will be in this state. An Application Server MUST be in the AS-
DOWN state before it can be removed from a configuration. DOWN state before it can be removed from a configuration.
AS-INACTIVE: The Application Server is available but no application AS-INACTIVE: The Application Server is available but no application
traffic is active (i.e., one or more related ASPs are in the ASP- traffic is active (i.e., one or more related ASPs are in the ASP-
INACTIVE state, but none in the ASP-ACTIVE or ASP-STANDBY states). The INACTIVE state, but none in the ASP-ACTIVE state). The recovery
recovery timer timer T(r) is not running or has expired.
T(r) is not running or has expired.
AS-ACTIVE: The Application Server is available and application traffic AS-ACTIVE: The Application Server is available and application traffic
is active. This state implies that at least one ASP is in the ASP- is active. This state implies that at least one ASP is in the ASP-
ACTIVE state. 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-DOWN
and it was the last remaining active ASP in the AS (and no ASPs in the and it was the last remaining active ASP in the AS. A recovery timer
ASP-STANDBY state are available. A recovery timer T(r) SHOULD be T(r) SHOULD be started and all incoming signalling messages SHOULD be
started and all incoming signalling messages SHOULD be queued by the queued by the SGP. If an ASP becomes ASP-ACTIVE before T(r) expires,
SGP. If an ASP becomes ASP-ACTIVE before T(r) expires, the AS is moved the AS is moved to the AS-ACTIVE state and all the queued messages
to the AS-ACTIVE state and all the queued messages will be will be sent to the ASP.
sent to the ASP.
If T(r) expires before an ASP becomes ASP-ACTIVE, the SGP stops queuing If T(r) expires before an ASP becomes ASP-ACTIVE, the SGP stops queuing
messages and discards all previously queued messages. The AS will move messages and discards all previously queued messages. The AS will move
to the AS-INACTIVE state if at least one ASP is in ASP-INACTIVE state, to the AS-INACTIVE state if at least one ASP is in ASP-INACTIVE state,
otherwise it will move to AS-DOWN state. otherwise it will move to AS-DOWN state.
Figure 5 shows an example AS state machine for the case where the Figure 5 shows an example AS state machine for the case where the
AS/ASP data is pre-configured. For other cases where the AS/ASP AS/ASP data is preconfigured. For other cases where the AS/ASP
configuration data is created dynamically, there would be differences configuration data is created dynamically, there would be differences
in the state machine, especially at creation of the AS. in the state machine, especially at creation of the AS.
For example, where the AS/ASP configuration data is not created until For example, where the AS/ASP configuration data is not created until
Registration of the first ASP, the AS-INACTIVE state is entered Registration of the first ASP, the AS-INACTIVE state is entered
directly upon the first successful REG REQ from an ASP. Another directly upon the first successful REG REQ from an ASP. Another
example is where the AS/ASP configuration data is not created until the example is where the AS/ASP configuration data is not created until the
first ASP successfully enters the ASP-ACTIVE state. In this case the first ASP successfully enters the ASP-ACTIVE state. In this case the
AS-ACTIVE state is entered directly. AS-ACTIVE state is entered directly.
skipping to change at page 70, line 22 skipping to change at page 72, line 22
^ | \ Tr Expiry, ^ | ^ | \ Tr Expiry, ^ |
| | \ at least one | | | | \ at least one | |
| | \ ASP in ASP-INACTIVE | | | | \ ASP in ASP-INACTIVE | |
| | \ | | | | \ | |
| | \ | | | | \ | |
| | \ | | | | \ | |
one ASP | | all ASP \ one ASP | | Last ACTIVE one ASP | | all ASP \ one ASP | | Last ACTIVE
trans | | trans to \ trans to | | ASP trans to trans | | trans to \ trans to | | ASP trans to
to | | ASP-DOWN -------\ ASP- | | ASP-INACTIVE to | | ASP-DOWN -------\ ASP- | | ASP-INACTIVE
ASP- | | \ ACTIVE | | or ASP-DOWN ASP- | | \ ACTIVE | | or ASP-DOWN
INACTIVE| | \ | | INACTIVE| | \ | | (start Tr)
| | \ | | | | \ | |
| | \ | | | | \ | |
| v \ | v | v \ | v
+----------+ \ +-------------+ +----------+ \ +-------------+
| | --| | | | --| |
| AS-DOWN | | AS-PENDING | | AS-DOWN | | AS-PENDING |
| | | (queueing) | | | | (queueing) |
| |<----------------------------| | | |<----------------------------| |
+----------+ Tr Expiry (no ASP +-------------+ +----------+ Tr Expiry and no ASP +-------------+
in ASP-INACTIVE state) in ASP-INACTIVE state)
Tr = Recovery Timer Tr = Recovery Timer
4.2.2 M3UA Management Procedures for Primitives 4.3.3 M3UA Management Procedures for Primitives
Before the establishment of an SCTP association the ASP state at both Before the establishment of an SCTP association the ASP state at both
the SGP and ASP is assumed to be in the state ASP-DOWN. the SGP and ASP is assumed to be in the state ASP-DOWN.
Once the SCTP association is established (see Section 4.1.2) and Once the SCTP association is established (see Section 4.2.1) and
assuming that the local M3UA-User is ready, the local M3UA ASP assuming that the local M3UA-User is ready, the local M3UA ASP
Maintenance (ASPM) function will initiate the relevant procedures, Maintenance (ASPM) function will initiate the relevant procedures,
using the ASP Up/ASP Down/ASP Active/ASP Inactive messages to convey using the ASP Up/ASP Down/ASP Active/ASP Inactive messages to convey
the ASP state to the SGP (see Section 4.3.3). the ASP state to the SGP (see Section 4.4.3).
If the M3UA layer subsequently receives an SCTP-COMMUNICATION_DOWN If the M3UA layer subsequently receives an SCTP-COMMUNICATION_DOWN
or SCTP-RESTART indication primitive from the underlying SCTP layer, it or SCTP-RESTART indication primitive from the underlying SCTP layer, it
will inform the Layer Management by invoking the M-SCTP_STATUS will inform the Layer Management by invoking the M-SCTP_STATUS
indication primitive. The state of the ASP will be moved to ASP-DOWN indication primitive. The state of the ASP will be moved to ASP-DOWN.
At an ASP, the MTP3-User will be informed of the unavailability of any At an ASP, the MTP3-User will be informed of the unavailability of any
affected SS7 destinations through the use of MTP-PAUSE indication affected SS7 destinations through the use of MTP-PAUSE indication
primitives. In the case primitives. In the case
of SS7 network isolation, the local MTP3-Users MAY be informed by of SS7 network isolation, the local MTP3-Users MAY be informed by
implementation-dependent means, as there is currently no primitive implementation-dependent means, as there is currently no primitive
defined for conveying this information. defined for conveying this information.
In the case of SCTP-COMMUNICATION_DOWN, the SCTP client MAY try to re- In the case of SCTP-COMMUNICATION_DOWN, the SCTP client MAY try to re-
establish the SCTP Association. This MAY be done by the M3UA layer establish the SCTP Association. This MAY be done by the M3UA layer
automatically, or Layer Management MAY re-establish using the M- automatically, or Layer Management MAY reestablish using the
SCTP_ESTABLISH request primitive. M-SCTP_ESTABLISH request primitive.
In the case of an SCTP-RESTART indication at an ASP, the ASP is now In the case of an SCTP-RESTART indication at an ASP, the ASP is now
considered by its M3UA peer to be in the ASP-DOWN state. The ASP, if considered by its M3UA peer to be in the ASP-DOWN state. The ASP, if
it is to recover, must begin any recovery with the ASP-Up procedure. it is to recover, must begin any recovery with the ASP-Up procedure.
4.2.3 M3UA Management Procedures for Peer-to-Peer Messages 4.3.4 ASPM Procedures for Peer-to-Peer Messages
All M3UA Management and ASP State and Traffic Maintenance messages are
sent on a sequenced
stream to ensure ordering. SCTP stream '0' is used.
4.2.3.1 ASP Up Procedures 4.3.4.1 ASP Up Procedures
After an ASP has successfully established an SCTP association to an After an ASP has successfully established an SCTP association to an
SGP, the SGP waits for the ASP to send an ASP Up message, indicating SGP, the SGP waits for the ASP to send an ASP Up message, indicating
that the ASP M3UA peer is available. The ASP is always the initiator that the ASP M3UA peer is available. The ASP is always the initiator
of the ASP Up message. This action MAY be initiated at the ASP by an of the ASP Up message. This action MAY be initiated at the ASP by an
M-ASP_UP request primitive from Layer Management or MAY be initiated M-ASP_UP request primitive from Layer Management or MAY be initiated
automatically by an M3UA management function. automatically by an M3UA management function.
When an ASP Up message is received at an SGP and internally the remote When an ASP Up message is received at an SGP and internally the remote
ASP is in the ASP-DOWN state and not considered locked-out for local ASP is in the ASP-DOWN state and not considered locked out for local
management reasons, the SGP marks the remote ASP in the state ASP- management reasons, the SGP marks the remote ASP in the state ASP-
INACTIVE and informs Layer Management with an M-ASP_Up indication INACTIVE and informs Layer Management with an M-ASP_Up indication
primitive. If the SGP is aware, via current configuration data, which primitive. If the SGP is aware, via current configuration data, which
Application Servers the ASP is configured to operate in, the SGP Application Servers the ASP is configured to operate in, the SGP
updates the ASP state to ASP-INACTIVE in each AS that it is a member. updates the ASP state to ASP-INACTIVE in each AS that it is a member.
Alternatively, the SGP may move the ASP into a pool of Inactive ASPs Alternatively, the SGP may move the ASP into a pool of Inactive ASPs
available for future configuration within Application Server(s), available for future configuration within Application Server(s),
determined in a subsequent Registration Request or ASP Active determined in a subsequent Registration Request or ASP Active
procedure. If the ASP Up message contains an ASP Identifier, the SGP procedure. If the ASP Up message contains an ASP Identifier, the SGP
should save the ASP Identifier for that ASP. should save the ASP Identifier for that ASP. The SGP MUST send an
The SGP responds with an ASP Up Ack message in ASP Up Ack message in response to a received ASP Up message even if
acknowledgement. The SGP sends an ASP Up Ack message in response to a the ASP is already marked as ASP-INACTIVE at the SGP.
received ASP Up message even if the ASP is already marked as ASP-
INACTIVE at the SGP.
If for any local reason (e.g., management lock-out) the SGP cannot If for any local reason (e.g., management lockout) the SGP cannot
respond with an ASP Up Ack message, the SGP responds to an ASP Up respond with an ASP Up Ack message, the SGP responds to an ASP Up
message with an Error message with Reason "Refused - Management message with an Error message with reason "Refused - Management
Blocking". Blocking".
At the ASP, the ASP Up Ack message received is not acknowledged. Layer At the ASP, the ASP Up Ack message received is not acknowledged. Layer
Management is informed with an M-ASP_UP confirm primitive. When an ASP Management is informed with an M-ASP_UP confirm primitive. When an ASP
enters the ASP-Inactive state from the ASP_Down state towards an SGP enters the ASP-Inactive state from the ASP-Down state towards an SGP
the M3UA MUST mark all SS7 destinations configured to be reachable via the M3UA MUST mark all SS7 destinations configured to be reachable via
this SGP as available. this SGP as available.
When the ASP sends an ASP Up message it starts timer T(ack). If the When the ASP sends an ASP Up message it starts timer T(ack). If the
ASP does not receive a response to an ASP Up message within T(ack), the ASP does not receive a response to an ASP Up message within T(ack), the
ASP MAY restart T(ack) and resend ASP-Up messages until it receives an ASP MAY restart T(ack) and resend ASP Up messages until it receives an
ASP Up Ack message. T(ack) is provisionable, with a default of 2 ASP Up Ack message. T(ack) is provisionable, with a default of 2
seconds. Alternatively, retransmission of ASP Up messages MAY be put seconds. Alternatively, retransmission of ASP Up messages MAY be put
under control of Layer Management. In this method, expiry of T(ack) under control of Layer Management. In this method, expiry of T(ack)
results in an M-ASP_UP confirm primitive carrying a negative results in an M-ASP_UP confirm primitive carrying a negative
indication. 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, the SGP other M3UA messages before an ASP Up message is received, the SGP
SHOULD discard them. SHOULD discard them.
If an ASP Up message is received and internally the remote ASP is in If an ASP Up message is received and internally the remote ASP is in
the ASP-ACTIVE or ASP-STANDBY state, an ASP-Up Ack message is returned, the ASP-ACTIVE state, an ASP-Up Ack message is returned, as well as an
as well as an Error message ("Unexpected Message), and the remote ASP Error message ("Unexpected Message), and the remote ASP state is
state is changed to ASP-INACTIVE in all relevant Application Servers. changed to ASP-INACTIVE in all relevant Application Servers.
If an ASP Up message is received and internally the remote ASP is If an ASP Up message is received and internally the remote ASP is
already in the ASP-INACTIVE state, an ASP Up Ack message is returned already in the ASP-INACTIVE state, an ASP Up Ack message is returned
and no further action is taken. and no further action is taken.
4.2.3.1.1 M3UA Version Control 4.3.4.1.1 M3UA Version Control
If an ASP Up message with an unsupported version is received, the If an ASP Up message with an unsupported version is received, the
receiving end responds with an Error message, indicating the version receiving end responds with an Error message, indicating the version
the receiving node supports and notifies Layer Management. the receiving node supports and notifies Layer Management.
This is useful when protocol version upgrades are being performed in a This is useful when protocol version upgrades are being performed in a
network. A node upgraded to a newer version should support the older network. A node upgraded to a newer version should support the older
versions used on other nodes it is communicating with. Because ASPs versions used on other nodes it is communicating with. Because ASPs
initiate the ASP Up procedure it is assumed that the Error message initiate the ASP Up procedure it is assumed that the Error message
would normally come from the SGP. would normally come from the SGP.
4.2.3.1.2 IPSP Considerations 4.3.4.1.2 IPSP Considerations
In the case of peer-to-peer IPSPs, either of the IPSPs (IPSP_A) may In the case of peer-to-peer IPSPs, either of the IPSPs (IPSP_A) may
start operations by sending an ASP Up message to the remote peer start operations by sending an ASP Up message to the remote peer
(IPSP_B). When the ASP Up message is received at IPSP_B and internally (IPSP_B). When the ASP Up message is received at IPSP_B and internally
the remote IPSP_A is in the ASP-DOWN state and not considered locked- the remote IPSP_A is in the ASP-DOWN state and not considered locked
out for local management reasons, IPSP_B marks the remote IPSP_A in the out for local management reasons, IPSP_B marks the remote IPSP_A in the
state ASP-INACTIVE and informs Layer Management with an M-ASP_Up state ASP-INACTIVE and informs Layer Management with an M-ASP_Up
indication primitive. IPSP_B returns an ASP-Up Ack message to IPSP_A. indication primitive. IPSP_B returns an ASP Up Ack message to IPSP_A.
IPSP_A moves IPSP_B to the ASP-INACTIVE state upon reception of an ASP IPSP_A moves IPSP_B to the ASP-INACTIVE state upon reception of an ASP
Up Ack message, if is not already in the ASP_INACTIVE state, and Up Ack message, if is not already in the ASP_INACTIVE state, and
informs Layer Management with an M-ASP_UP confirmation primitive. informs Layer Management with an M-ASP_UP confirmation primitive.
If for any local reason (e.g., management lock-out) the IPSP_B cannot If for any local reason (e.g., management lockout) the IPSP_B cannot
respond with an ASP Up Ack message, it responds to an ASP Up message respond with an ASP Up Ack message, it responds to an ASP Up message
with an Error message with Reason "Refused - Management Blocking" and with an Error message with reason "Refused - Management Blocking" and
leaves IPSP_A in the ASP-DOWN state. leaves IPSP_A in the ASP-DOWN state.
4.2.3.2 ASP-Down Procedures 4.3.4.2 ASP-Down Procedures
The ASP will send an ASP Down message to an SGP when the ASP wishes to The ASP will send an ASP Down message to an SGP when the ASP wishes to
be be removed from service in all Application Servers that it is a
removed from service in all Application Servers that it is a member and member and no longer receive any DATA, SSNM or ASPTM messages.
no longer receive any DATA, SSNM or ASPTM messages. This action MAY be This action MAY be initiated at the ASP by an M-ASP_DOWN request
initiated at the ASP by an M-ASP_DOWN request primitive from Layer primitive from Layer Management or MAY be initiated automatically
Management or MAY be initiated automatically by an M3UA management by an M3UA management function.
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 3.5.5) to register within the Registration procedures (see Section 4.3.5) to register within
Application Servers but has not deregistered from all of them prior to Application Servers but has not deregistered from all of them prior to
sending the ASP Down message, the SGP SHOULD consider the ASP as sending the ASP Down message, the SGP SHOULD consider the ASP as
Deregistered in all Application Servers that it is still a member. Deregistered in all Application Servers that it is still a member.
The SGP marks the ASP as ASP-DOWN, informs Layer Management with an M- The SGP marks the ASP as ASP-DOWN, informs Layer Management with an M-
ASP_Down indication primitive, and returns an ASP Down Ack message to ASP_Down indication primitive, and returns an ASP Down Ack message to
the ASP. the ASP.
The SGP sends an ASP Down Ack message in response to a received ASP- The SGP MUST send an ASP Down Ack message in response to a received
Down message from the ASP even if the ASP is already marked as ASP-DOWN ASP Down message from the ASP even if the ASP is already marked as
at the SGP. The SGP sends an ASP Down Ack message even if the reason ASP-DOWN at the SGP.
in the received ASP Down message is considered invalid.
At the ASP, the ASP Down Ack message received is not acknowledged. At the ASP, the ASP Down Ack message received is not acknowledged.
Layer Management is informed with an M-ASP_DOWN confirm primitive. If Layer Management is informed with an M-ASP_DOWN confirm primitive. If
the ASP receives an ASP Down Ack without having sent an ASP Down the ASP receives an ASP Down Ack without having sent an ASP Down
message, the ASP should now consider itself as in the ASP-DOWN state. message, the ASP should now consider itself as in the ASP-DOWN state.
If the ASP was previously in the ASP-ACTIVE or ASP_INACTIVE state, the If the ASP was previously in the ASP-ACTIVE or ASP-INACTIVE state, the
ASP should then initiate procedures to return itself to its previous ASP should then initiate procedures to return itself to its previous
state. state.
When the ASP sends an ASP Down message it starts timer T(ack). If the When the ASP sends an ASP Down message it starts timer T(ack). If the
ASP does not receive a response to an ASP Down message within T(ack), ASP does not receive a response to an ASP Down message within T(ack),
the ASP MAY restart T(ack) and resend ASP Down messages until it 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 receives an ASP Down Ack message. T(ack) is provisionable, with a
default of 2 seconds. Alternatively, retransmission of ASP Down default of 2 seconds. Alternatively, retransmission of ASP Down
messages MAY be put under control of Layer Management. In this method, messages MAY be put under control of Layer Management. In this method,
expiry of T(ack) results in an M-ASP_DOWN confirm primitive carrying a expiry of T(ack) results in an M-ASP_DOWN confirm primitive carrying a
negative indication. negative indication.
4.2.3.4 ASP-Active Procedures 4.3.4.4 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 sends an ASP Active message to the SGP indicating that or IPSP, the ASP MAY send an ASP Active message to the SGP indicating
the ASP is ready to start processing traffic. This action MAY be
that the ASP is ready to start processing traffic. This action MAY be
initiated at the ASP by an M-ASP_ACTIVE request primitive from Layer initiated at the ASP by an M-ASP_ACTIVE request primitive from Layer
Management or MAY be initiated automatically by an M3UA management Management or MAY be initiated automatically by an M3UA management
function. In the case where an ASP wishes to process the traffic for function. In the case where an ASP wishes to process the traffic for
more than one Application Server across a common SCTP association, the more than one Application Server across a common SCTP association, the
ASP Active message(s) SHOULD contain a list of one or more Routing ASP Active message(s) SHOULD contain a list of one or more Routing
Contexts to indicate for which Application Servers the ASP Active Contexts to indicate for which Application Servers the ASP Active
message applies. It is not necessary for the ASP to include all Routing message applies. It is not necessary for the ASP to include all Routing
Contexts of interest in a single ASP Active message, thus requesting to Contexts of interest in a single ASP Active message, thus requesting to
become active in all Routing Contexts at the same time. Multiple ASP become active in all Routing Contexts at the same time. Multiple ASP
Active messages MAY be used to activate within the Application Servers Active messages MAY be used to activate within the Application Servers
independently, or in sets. In the case where an ASP Active message independently, or in sets. In the case where an ASP Active message
does not contain a Routing Context parameter, the receiver must know, does not contain a Routing Context parameter, the receiver must know,
via configuration data, which Application Server(s) the ASP is a via configuration data, which Application Server(s) the ASP is a
member. member.
For the Application Servers that the ASP can be successfully activated, For the Application Servers that the ASP can be successfully activated,
the SGP or IPSP responds with one or more ASP Active Ack messages, the SGP or IPSP responds with one or more ASP Active Ack messages,
including the associated Routing Context and Traffic Mode Type values. including the associated Routing Context(s) and reflecting any
The Routing Context parameter MUST be included in the Asp Active Ack Traffic Mode Type value present in the related ASP Active message.
message if the received ASP Active message contained any Routing The Routing Context parameter MUST be included in the ASP Active
Contexts. Depending on the ASP Active Message Traffic Mode Type Ack message(s) if the received ASP Active message contained any
request, the SGP moves the ASP to the correct ASP traffic state within Routing Contexts. Depending on any Traffic Mode Type request in
the associated Application Server(s). Layer Management is informed with the ASP Active message, or local configuration data if there is no
an M-ASP_Active indication. If the SGP or IPSP receives any Data request, the SGP moves the ASP to the correct ASP traffic state
messages before an ASP Active message is received, the SGP or IPSP MAY within the associated Application Server(s). Layer Management is
discard them. By sending an ASP Active Ack message, the SGP or IPSP is informed with an M-ASP_Active indication. If the SGP or IPSP
now ready to receive and send traffic for the related Routing receives any Data messages before an ASP Active message is
Context(s). The ASP SHOULD NOT send Data messages for the related received, the SGP or IPSP MAY discard them. By sending an ASP
Routing Context(s) before receiving an ASP Active Ack message, or it Active Ack message, the SGP or IPSP is now ready to receive and
will risk message loss. send traffic for the related Routing Context(s). The ASP SHOULD
NOT send Data messages for the related Routing Context(s) before
receiving an ASP Active Ack message, or it will risk message loss.
Multiple ASP Active Ack messages MAY be used in response to an ASP Multiple ASP Active Ack messages MAY be used in response to an ASP
Active message containing multiple Routing Contexts, allowing the SGP Active message containing multiple Routing Contexts, allowing the SGP
or IPSP to independently acknowledge the ASP Active message for or IPSP to independently acknowledge the ASP Active message for
different (sets of) Routing Contexts. The SGP or IPSP sends an Error different (sets of) Routing Contexts. The SGP or IPSP MUST send an
message ("Invalid Routing Context") for each Routing Context value that Error message ("Invalid Routing Context") for each Routing Context
the ASP cannot be successfully activated . value that the ASP cannot be successfully activated .
In the case where an "out-of-the-blue" ASP Active message is received In the case where an "out-of-the-blue" ASP Active message is received
(i.e., the ASP has not registered with the SG or the SG has no static (i.e., the ASP has not registered with the SG or the SG has no static
configuration data for the ASP), the message may be silently discarded. configuration data for the ASP), the message MAY be silently discarded.
The SGP MUST send an ASP Active Ack message in response to a received The SGP MUST send an ASP Active Ack message in response to a received
ASP Active message from the ASP, if the ASP is already marked in the ASP Active message from the ASP, if the ASP is already marked in the
ASP-ACTIVE state at the SGP. ASP-ACTIVE state at the SGP.
At the ASP, the ASP Active Ack message received is not acknowledged. At the ASP, the ASP Active Ack message received is not acknowledged.
Layer Management is informed with an M-ASP_ACTIVE confirm primitive. Layer Management is informed with an M-ASP_ACTIVE confirm primitive.
It is possible for the ASP to receive Data message(s) before the ASP It is possible for the ASP to receive Data message(s) before the ASP
Active Ack message as the ASP Active Ack and Data messages from an SG Active Ack message as the ASP Active Ack and Data messages from an SG
or IPSP may be sent on different SCTP streams. Message loss is or IPSP may be sent on different SCTP streams. Message loss is
skipping to change at page 75, line 22 skipping to change at page 77, line 22
When the ASP sends an ASP Active message it starts timer T(ack). If When the ASP sends an ASP Active message it starts timer T(ack). If
the ASP does not receive a response to an ASP Active message within the ASP does not receive a response to an ASP Active message within
T(ack), the ASP MAY restart T(ack) and resend ASP Active messages until T(ack), the ASP MAY restart T(ack) and resend ASP Active messages until
it receives an ASP Active Ack message. T(ack) is provisionable, with a it receives an ASP Active Ack message. T(ack) is provisionable, with a
default of 2 seconds. Alternatively, retransmission of ASP Active default of 2 seconds. Alternatively, retransmission of ASP Active
messages MAY be put under control of Layer Management. In this method, messages MAY be put under control of Layer Management. In this method,
expiry of T(ack) results in an M-ASP_ACTIVE confirm primitive carrying expiry of T(ack) results in an M-ASP_ACTIVE confirm primitive carrying
a negative indication. a negative indication.
There are six modes of Application Server traffic handling in the SGP There are three modes of Application Server traffic handling in the SGP
M3UA layer - Over-ride, Over-ride (Standby), Load-share, Load-share M3UA layer: Override, Loadshare and Broadcast. When included, the
(Standby), Broadcast and Broadcast Standby. The Traffic Mode Type Traffic Mode Type parameter in the ASP Active message indicates the
parameter in the ASP Active message indicates the traffic handling mode traffic handling mode to be used in a particular Application Server.
used in a particular Application Server. If the SGP determines that the If the SGP determines that the mode indicated in an ASP Active
mode indicated in an ASP Active message is unsupported or incompatible message is unsupported or incompatible with the mode currently
with the mode currently configured for the AS, the SGP responds with an configured for the AS, the SGP responds with an Error message
Error message ("Unsupported / Invalid Traffic Handling Mode"). If the ("Unsupported / Invalid Traffic Handling Mode"). If the traffic
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 Over-ride mode AS, reception of an ASP Active message In the case of an Override mode AS, reception of an ASP Active message
at an SGP causes the (re)direction of all traffic for the AS to the ASP at an SGP causes the (re)direction of all traffic for the AS to the ASP
that sent the ASP Active message. Any previously active ASP in the AS that sent the ASP Active message. Any previously active ASP in the AS
is now considered to be in state ASP-INACTIVE and SHOULD no longer is now considered to be in state ASP-INACTIVE and SHOULD no longer
receive traffic from the SGP within the AS. The SGP or IPSP then MUST receive traffic from the SGP within the AS. The SGP or IPSP then MUST
send a Notify message ("Alternate ASP-Active") to the previously active send a Notify message ("Alternate ASP_Active") to the previously active
ASP in the AS, and SHOULD stop traffic to/from that ASP. The ASP ASP in the AS, and SHOULD stop traffic to/from that ASP. The ASP
receiving this Notify MUST consider itself now in the ASP-INACTIVE receiving this Notify MUST consider itself now in the ASP-INACTIVE
state, if it is not already aware of this via inter-ASP communication state, if it is not already aware of this via inter-ASP communication
with the Over-riding ASP. with the Overriding ASP.
In the case of Over-ride (Standby) mode the traffic is not started to
the ASP until the currently active ASP transitions to the ASP-INACTIVE
or ASP-DOWN state. At this point the ASP that sent the ASP Active
message ("Over-Ride (Standby)") is moved to the ASP-ACTIVE state and
the traffic is redirected. A second ASP Active Ack message with a new
Traffic Mode Type ("Over-ride", previously "Over-ride(Standby)") is
sent to the ASP. A Notify message ("Alternate ASP-Active") is not sent
in this case.
If there is no currently active ASP, an ASP Active Ack message ("Over-
ride") is returned right away and the traffic is directed to the ASP.
In the case of a Load-share mode AS, reception of an ASP Active message In the case of a Loadshare mode AS, reception of an ASP Active message
at an SGP or IPSP causes the direction of traffic to the ASP sending at an SGP or IPSP causes the direction of traffic to the ASP sending
the ASP Active message, in addition to all the other ASPs that are the ASP Active message, in addition to all the other ASPs that are
currently active in the AS. The algorithm at the SGP for load-sharing currently active in the AS. The algorithm at the SGP for loadsharing
traffic within an AS to all the active ASPs is implementation traffic within an AS to all the active ASPs is implementation
dependent. The algorithm could, for example, be round-robin or based dependent. The algorithm could, for example, be round-robin or based
on information in the Data message (e.g., the SLS, SCCP SSN, ISUP CIC on information in the Data message (e.g., the SLS, SCCP SSN, ISUP CIC
value). value).
An SGP or IPSP, upon reception of an ASP Active message for the first An SGP or IPSP, upon reception of an ASP Active message for the first
ASP in a Loadshare AS, MAY choose not to direct traffic to a newly ASP in a Loadshare AS, MAY choose not to direct traffic to a newly
active ASP until it determines that there are sufficient resources to active ASP until it determines that there are sufficient resources to
handle the expected load (e.g., until there are "n" ASPs in state ASP- handle the expected load (e.g., until there are "n" ASPs in state ASP-
ACTIVE in the AS). ACTIVE in the AS).
In the case of a Load-share (Standby) mode AS, the traffic is not All ASPs within a loadsharing mode AS must be able to process any
started to the ASP until the SGP or IPSP determines that there are
insufficient resources available in the AS. This is likely when one of
the active load-sharing ASPs transitions to either the ASP-INACTIVE or
ASP-DOWN state. At this point the ASP that sent the ASP Active message
("Load-share (Standby)") is moved to the ASP_ACTIVE state and traffic
is started. A second ASP Active Ack message with a new Traffic Mode
Type ("Load-share" - previously "Loadshare(Standby)") is sent to the
ASP. A Notify message ("Insufficient ASP resources active in AS ") is
not sent in this case.
If there is no currently active ASP, an ASP Active Ack message
("Loadshare") is returned right away and the traffic is directed to the
ASP.
All ASPs within a load-sharing mode AS must be able to process any
Data message received for the AS, to accommodate any potential Data message received for the AS, to accommodate any potential
fail-over or rebalancing of the offered load. failover or rebalancing of the offered load.
In the case of a Broadcast mode AS, reception of an ASP Active message In the case of a Broadcast mode AS, reception of an ASP Active message
at an SGP or IPSP cuases the direction of traffic to the ASP sending the at an SGP or IPSP causes the direction of traffic to the ASP sending
ASP Active message, in addition to all the other ASPs that are the ASP Active message, in addition to all the other ASPs that are
currently active in the AS. The algorithm at the SGP for broadcasting currently active in the AS. The algorithm at the SGP for broadcasting
traffic within an AS to all the active ASPs is a simple braoadcast traffic within an AS to all the active ASPs is a simple broadcast
algorithm, where every message is sent to each of the active ASPs. algorithm, where every message is sent to each of the active ASPs.
An SGP or IPSP, upon reception of an ASP Active message for the first An SGP or IPSP, upon reception of an ASP Active message for the first
ASP in a Broadcast AS, MAY choose not to direct traffic to a newly ASP in a Broadcast AS, MAY choose not to direct traffic to a newly
active ASP until it determines that there are sufficient resources to active ASP until it determines that there are sufficient resources to
handle the expected load (e.g., until there are "n" ASPs in state handle the expected load (e.g., until there are "n" ASPs in state
ASP-ACTIVE in the AS). ASP-ACTIVE in the AS).
In the case of Broadcast (Standby) mode AS, the traffic is not started Whenever an ASP in a Broadcast mode AS becomes ASP-ACTIVE, the SGP
to the ASP until the SGP or IPSP determines that there are sufficient MUST tag the first DATA message broadcast in each SCTP stream with
resuorces available in the AS. This is likely when one of the active a unique Correlation Id parameter. The purpose of this
broadcast ASPs transitions to either the ASP-INACTIVE or ASP-DOWN Id is to permit the newly active ASP to synchronize its processing
state. At this point the ASP that sent the ASP Active message of traffic in each ordered stream with the other ASPs in the
("Broadcast (Standby)") is moved to the ASP_ACTIVE state and traffic broadcast group.
is started. A second ASP Active Ack message with a new Traffic Mode
Type ("Broadcast" - previously "Broadcast (Standby)") is sent to the
ASP. A Notify message ("Insufficient ASP resources active in AS") is
not sent in this case.
If there is no currently active ASP, an ASP Active Ack message
("Broadcast") is returned right away and the traffic is directed to
the ASP.
4.2.3.5 ASP Inactive Procedures 4.3.4.5 ASP Inactive Procedures
When an ASP wishes to withdraw from receiving traffic within an AS, the When an ASP wishes to withdraw from receiving traffic within an AS, the
ASP sends an ASP Inactive message to the SGP or IPSP. This action MAY ASP sends an ASP Inactive message to the SGP or IPSP. This action MAY
be initiated at the ASP by an M-ASP_INACTIVE request primitive from be initiated at the ASP by an M-ASP_INACTIVE request primitive from
Layer Management or MAY be initiated automatically by an M3UA Layer Management or MAY be initiated automatically by an M3UA
management function. In the case where an ASP is processing the management function. In the case where an ASP is processing the
traffic for more than one Application Server across a common SCTP traffic for more than one Application Server across a common SCTP
association, the ASP Inactive message contains one or more Routing association, the ASP Inactive message contains one or more Routing
Contexts to indicate for which Application Servers the ASP Inactive Contexts to indicate for which Application Servers the ASP Inactive
message applies. In the case where an ASP Inactive message does not message applies. In the case where an ASP Inactive message does not
contain a Routing Context parameter, the receiver must know, via contain a Routing Context parameter, the receiver must know, via
configuration data, which Application Servers the ASP is a member and configuration data, which Application Servers the ASP is a member and
move the ASP to the ASP-INACTIVE state in each all Application Servers. move the ASP to the ASP-INACTIVE state in all Application Servers.
In the case of an Over-ride 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 ("Over-ride") 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 Ack considered by the SGP to be in state ASP-INACTIVE. An ASP Inactive Ack
message is sent to the ASP, after ensuring that all traffic is stopped message is sent to the ASP, after ensuring that all traffic is stopped
to the ASP. to the ASP.
In the case of a Load-share mode AS, the SGP moves the ASP to the ASP- In the case of a Loadshare mode AS, the SGP moves the ASP to the ASP-
INACTIVE state and the AS traffic is re-allocated across the remaining INACTIVE state and the AS traffic is reallocated across the remaining
ASPs in the state ASP-ACTIVE, as per the load-sharing algorithm ASPs in the state ASP-ACTIVE, as per the loadsharing algorithm
currently used within the AS. A Notify message("Insufficient ASP currently used within the AS. A Notify message("Insufficient ASP
resources active in AS") MAY be sent to all inactive ASPs, if required. resources active in AS") MAY be sent to all inactive ASPs, if required.
However, if a Loadshare ("Standby") ASP is available, it may be now An ASP Inactive Ack message is sent to the ASP after all traffic
immediately included in the loadshare group and a Notify message is not
sent. An ASP Inactive Ack message is sent to the ASP after all traffic
is halted and Layer Management is informed with an M-ASP_INACTIVE is halted and Layer Management is informed with an M-ASP_INACTIVE
indication primitive. 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. However, if a Broadcast ("Standby") ASP inactive ASPs, if required. An ASP Inactive Ack message
is available, it may be now immediately included in the broadcast
group and a Notify message is not sent. An ASP Inactive Ack message
is sent to the ASP after all traffic is halted and Layer Management is is sent to the ASP after all traffic is halted and Layer Management is
informed with an M-ASP_INACTIVE indication primitive. informed with an M-ASP_INACTIVE indication primitive.
Multiple ASP Inactive Ack messages MAY be used in response to an ASP Multiple ASP Inactive Ack messages MAY be used in response to an ASP
Inactive message containing multiple Routing Contexts, allowing the SGP Inactive message containing multiple Routing Contexts, allowing the SGP
or IPSP to independently acknowledge for different (sets of) Routing 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 un-configured Routing Context Context") message for each invalid or unconfigured Routing Context
value in a received ASP Inactive message message. value in a received ASP Inactive message.
The SGP MUST send an ASP Inactive Ack message in response to a received The SGP MUST send an ASP Inactive Ack message in response to a received
ASP Inactive message from the ASP and the ASP is already marked as ASP- ASP Inactive message from the ASP and the ASP is already marked as ASP-
INACTIVE at the SGP. INACTIVE at the SGP.
At the ASP, the ASP-Inactive Ack message received is not acknowledged. At the ASP, the ASP Inactive Ack message received is not acknowledged.
Layer Management is informed with an M-ASP_INACTIVE confirm primitive. Layer Management is informed with an M-ASP_INACTIVE confirm primitive.
If the ASP receives an ASP Inactive Ack without having sent an ASP
Inactive message, the ASP should now consider itself as in the
ASP-INACTIVE state. If the ASP was previously in the ASP-ACTIVE
state, the ASP should then initiate procedures to return itself to
its previous state.
When the ASP sends an ASP Inactive message it starts timer T(ack). If When the ASP sends an ASP Inactive message it starts timer T(ack). If
the ASP does not receive a response to an ASP Inactive message within the ASP does not receive a response to an ASP Inactive message within
T(ack), the ASP MAY restart T(ack) and resend ASP Inactive messages T(ack), the ASP MAY restart T(ack) and resend ASP Inactive messages
until it receives an ASP Inactive Ack message. T(ack) is until it receives an ASP Inactive Ack message. T(ack) is
provisionable, with a default of 2 seconds. Alternatively, provisionable, with a default of 2 seconds. Alternatively,
retransmission of ASP Inactive messages MAY be put under control of retransmission of ASP Inactive messages MAY be put under control of
Layer Management. In this method, expiry of T(ack) results in a M- Layer Management. In this method, expiry of T(ack) results in a M-
ASP_Inactive confirm primitive carrying a negative indication. ASP_Inactive confirm primitive carrying a negative indication.
If no other ASPs in the Application Server are in the state ASP-ACTIVE If no other ASPs in the Application Server are in the state
or ASP-STANDBY, the SGP MUST send a Notify message ("AS-Pending") to ASP-ACTIVE, the SGP MUST send a Notify message ("AS-Pending") to
all of the ASPs in the AS which are in the state ASP-INACTIVE. The SGP all of the ASPs in the AS which are in the state ASP-INACTIVE.
SHOULD start buffering the incoming messages for T(r)seconds, after The SGP SHOULD start buffering the incoming messages for T(r)
which messages MAY be discarded. T(r) is configurable by the network seconds, after which messages MAY be discarded. T(r) is
operator. If the SGP receives an ASP Active message from an ASP in the
AS before expiry of T(r), the buffered traffic is directed to that ASP
and the timer is cancelled. If T(r) expires, the AS is moved to the
AS-INACTIVE state.
4.2.3.6 Notify Procedures configurable by the network operator. If the SGP receives an ASP
Active message from an ASP in the AS before expiry of T(r), the
buffered traffic is directed to that ASP and the timer is cancelled.
If T(r) expires, the AS is moved to the AS-INACTIVE state.
4.3.4.6 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. The Notify message MUST be sent after any ASP State or Traffic ASP. At the ASP, Layer Management is informed with an M-NOTIFY
Management acknowledgement messages (e.g., ASP Up Ack, ASP Down Ack, ASP indication primitive. The Notify message must be sent whether the
Active Ack, or ASP Inactive Ack). At the ASP, Layer Management is AS state change was a result of an ASP failure or reception of an
informed with an M-NOTIFY indication primitive. ASP State management (ASPSM) / ASP Traffic Management (ASPTM)
message. In the second case, the Notify message MUST be sent after
any related acknowledgement messages (e.g., ASP Up Ack, ASP Down
Ack, ASP Active Ack, or ASP Inactive Ack).
In the case where a Notify message("AS-PENDING") message is sent by an In the case where a Notify message("AS-PENDING") message is sent by
SGP that now has no ASPs active to service the traffic, or where a an SGP that now has no ASPs active to service the traffic, or where a
Notify message("Insufficient ASP resources active in AS") MUST be sent Notify ("Insufficient ASP resources active in AS") message MUST be
in the Loadshare or Broadcast mode, the Notify message does not sent in the Loadshare or Broadcast mode, the Notify message does not
explicitly compel the ASP(s) receiving the message to become active. The explicitly compel the ASP(s) receiving the message to become
ASPs remain in control of what (and when) traffic action is taken. active. The ASPs remain in control of what (and when) traffic action
is taken.
In the case where a Notify message does not contain a 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 action Application Servers the ASP is a member and take the appropriate
in each AS. action in each AS.
4.2.3.7 Heartbeat Procedures 4.3.4.7 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).
After an ASP or IPSP has received an ASP Up Ack message from an M3UA Either M3UA peer may optionally send Heartbeat messages periodically,
peer in response to an ASP Up message, either M3UA peer may optionally subject to a provisionable timer T(beat). Upon receiving a Heartbeat
send Heartbeat messages periodically, subject to a provisionable timer message, the M3UA peer MUST respond with a Heartbeat Ack message.
T(beat). Upon receiving a Heartbeat message, the M3UA peer MUST respond
with a Heartbeat Ack message.
If no Heartbeat Ack message (or any other M3UA message) is received from If no Heartbeat Ack message (or any other M3UA message) is received
the M3UA peer within 2*T(beat), the remote M3UA peer is considered from the M3UA peer within 2*T(beat), the remote M3UA peer is
unavailable. Transmission of Heartbeat messages is stopped and the considered unavailable. Transmission of Heartbeat messages is
signalling process SHOULD attempt to re-establish communication if it is stopped and the signalling process SHOULD attempt to reestablish
configured as the client for the disconnectd M3UA peer. communication if it is configured as the client for the
disconnected M3UA peer.
The Heartbeat message may optionally contain an opaque Heartbeat Data The Heartbeat message may optionally contain an opaque Heartbeat Data
parameter that MUST be echoed back unchanged in the related Heartbeat parameter that MUST be echoed back unchanged in the related Heartbeat
Ack message. The sender, upon examining the contents of the returned Ack message. The sender, upon examining the contents of the returned
Heartbeat Ack message, MAY choose to consider the remote M3UA peer as Heartbeat Ack message, MAY choose to consider the remote M3UA peer as
unavailable. The contents/format of the Heartbeat Data parameter is unavailable. The contents/format of the Heartbeat Data parameter is
implementation-dependent and only of local interest to the original implementation-dependent and only of local interest to the original
sender. The contents may be used, for example, to support a Heartbeat sender. The contents may be used, for example, to support a Heartbeat
sequence algorithm (to detect missing Heartbeats), and/or a timestamp sequence algorithm (to detect missing Heartbeats), and/or a timestamp
mechanism (to evaluate delays). mechanism (to evaluate delays).
Note: Heartbeat related events are not shown in Figure 4 "ASP state Note: Heartbeat related events are not shown in Figure 4 "ASP state
transition diagram". transition diagram".
skipping to change at page 79, line 8 skipping to change at page 81, line 16
Heartbeat Ack message, MAY choose to consider the remote M3UA peer as Heartbeat Ack message, MAY choose to consider the remote M3UA peer as
unavailable. The contents/format of the Heartbeat Data parameter is unavailable. The contents/format of the Heartbeat Data parameter is
implementation-dependent and only of local interest to the original implementation-dependent and only of local interest to the original
sender. The contents may be used, for example, to support a Heartbeat sender. The contents may be used, for example, to support a Heartbeat
sequence algorithm (to detect missing Heartbeats), and/or a timestamp sequence algorithm (to detect missing Heartbeats), and/or a timestamp
mechanism (to evaluate delays). mechanism (to evaluate delays).
Note: Heartbeat related events are not shown in Figure 4 "ASP state Note: Heartbeat related events are not shown in Figure 4 "ASP state
transition diagram". transition diagram".
4.2.4 Routing Key Management Procedures 4.4 Routing Key Management Procedures
4.2.4.1 Registration 4.4.1 Registration
An ASP MAY dynamically register with an SGP as an ASP within an An ASP MAY dynamically register with an SGP as an ASP within an
Application Server using the REG REQ message. A Routing Key parameter Application Server using the REG REQ message. A Routing Key parameter
in the REG REQ message specifies the parameters associated with the in the REG REQ message specifies the parameters associated with the
Routing Key. Routing Key.
The SGP examines the contents of the received Routing Key parameter and The SGP examines the contents of the received Routing Key parameter and
compares it with the currently provisioned Routing Keys. If the compares it with the currently provisioned Routing Keys. If the
received Routing Key matches an existing SGP Routing Key entry, and the received Routing Key matches an existing SGP Routing Key entry, and the
ASP is not currently included in the list of ASPs for the related ASP is not currently included in the list of ASPs for the related
skipping to change at page 80, line 37 skipping to change at page 82, line 46
indicating the success or failure result for each Routing Key in a indicating the success or failure result for each Routing Key in a
separate Registration Result parameter. Alternatively the SGP MAY separate Registration Result parameter. Alternatively the SGP MAY
respond with multiple REG RSP messages, each with one or more respond with multiple REG RSP messages, each with one or more
Registration Result parameters. The ASP uses the Local-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.2.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 de- parameter in the DEREG REQ message specifies which Routing Keys to
register. An ASP SHOULD move to the ASP-INACTIVE state for an deregister. An ASP SHOULD move to the ASP-INACTIVE state for an
Application Server before attempting to deregister the Routing Key Application Server before attempting to deregister the Routing Key
(i.e., deregister after receiving an ASP Inactive Ack). Also, an ASP (i.e., deregister after receiving an ASP Inactive Ack). Also, an ASP
SHOULD deregister from all Application Servers that it is a member SHOULD deregister from all Application Servers that it is a member
before attempting to move to the ASP-Down state. before attempting to move to the ASP-Down state.
The SGP examines the contents of the received Routing Context parameter The SGP examines the contents of the received Routing Context parameter
and validates that the ASP is currently registered in the Application and validates that the ASP is currently registered in the Application
Server(s) related to the included Routing Context(s). If validated, Server(s) related to the included Routing Context(s). If validated,
the ASP is de-registered as an ASP in the related Application Server. the ASP is deregistered as an ASP in the related Application Server.
The deregistration procedure does not necessarily imply the deletion of The deregistration procedure does not necessarily imply the deletion of
Routing Key and Application Server configuration data at the SGP. Other Routing Key and Application Server configuration data at the SGP. Other
ASPs may continue to be associated with the Application Server, in ASPs may continue to be associated with the Application Server, in
which case the Routing Key data MUST NOT be deleted. If a which case the Routing Key data MUST NOT be deleted. If a
Deregistration results in no more ASPs in an Application Server, an SGP Deregistration results in no more ASPs in an Application Server, an SGP
MAY delete the Routing Key data. MAY delete the Routing Key data.
The SGP acknowledges the deregistration request by returning a DEREG The SGP acknowledges the deregistration request by returning a DEREG
RSP message to the requesting ASP. The result of the deregistration is RSP message to the requesting ASP. The result of the deregistration is
found in the Deregistration Result parameter, indicating success or found in the Deregistration Result parameter, indicating success or
failure with cause. failure with cause.
An ASP MAY deregister multiple Routing Contexts at once by including a An ASP MAY deregister multiple Routing Contexts at once by including a
number of Routing Contexts in a single DEREG REQ message. The SGP MAY number of Routing Contexts in a single DEREG REQ message. The SGP MAY
respond to each deregistration request in a single DEREG RSP message, respond to each deregistration request in a single DEREG RSP message,
indicating the success or failure result for each Routing Context in a indicating the success or failure result for each Routing Context in a
separate Deregistration Result parameter. separate Deregistration Result parameter.
4.3 Procedures to Support the Availability or Congestion Status of SS7 4.5 Procedures to Support the Availability or Congestion Status of SS7
Destination Destination
4.3.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 inter-working function at an SGP, the SGP M3UA primitive from the nodal interworking function at an SGP, the SGP M3UA
layer will send a corresponding SS7 Signalling Network Management layer will send a corresponding SS7 Signalling Network Management
(SSNM) DUNA, DAVA, SCON, or DUPU message (see Section 3.4) to the M3UA (SSNM) DUNA, DAVA, SCON, or DUPU message (see Section 3.4) to the M3UA
peers at concerned ASPs. The M3UA layer must fill in various fields of peers at concerned ASPs. The M3UA layer must fill in various fields of
the SSNM messages consistently with the information received in the the SSNM messages consistently with the information received in the
primitives. 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 informed
based on the specific SS7 network for which the primitive indication based on the specific SS7 network for which the primitive indication
is relevant. In this way, all ASPs configured to send/receive traffic is relevant. In this way, all ASPs configured to send/receive traffic
within a particular network appearance are informed. If the SGP within a particular network appearance are informed. If the SGP
operates within a single SS7 network appearance, then all ASPs are operates within a single SS7 network appearance, then all ASPs are
informed. informed.
DUNA, DAVA, SCON, and DRST messages MUST be sent sequentially and DUNA, DAVA, SCON, and DRST messages MUST be sent sequentially and
processed at the receiver in the order sent. SCTP stream "0" is used to processed at the receiver in the order sent. SCTP stream "0" is
provide the sequencing. The only exception to this is if the used to provide the sequencing. The only exception to this is if the
international congestion method (see Q.704) is used. If so, the international congestion method (see Q.704) is used. If so, the
Unordered bit in the SCTP DATA chunk MAY be used for the SCON message. Unordered bit in the SCTP DATA chunk MAY be used for the SCON message.
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 un-sequenced. Again, SCTP stream 0 is used, with optional use be sent unsequenced. Again, SCTP stream 0 is used, with optional use
of the Unordered bit in the SCTP DATA chunk. of the Unordered bit in the SCTP DATA chunk.
4.3.2 At an ASP 4.5.2 At an ASP
4.3.2.1 Single SGP Configurations 4.5.2.1 Single SGP 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 SHOULD congestion status of SS7 destinations, the M3UA layer at the ASP SHOULD
pass up appropriate indications in the primitives to the M3UA User, as pass up appropriate indications in the primitives to the M3UA User, as
though equivalent SSNM messages were received. For example, the loss though equivalent SSNM messages were received. For example, the loss
of an SCTP association to an SGP may cause the unavailability of a set of an SCTP association to an SGP may cause the unavailability of a set
of SS7 destinations. MTP-PAUSE indication primitives to the M3UA User of SS7 destinations. MTP-PAUSE indication primitives to the M3UA User
are appropriate. are appropriate.
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(P), much like an MTP3 layer maintains the status of routes via the SG(P), much like an MTP3 layer
maintains route-set status. maintains route-set status.
4.3.2.2 Multiple SGP Configurations 4.5.2.2 Multiple SGP Configurations
At an ASP, upon receiving a Signalling Network Management message from At an ASP, upon receiving a Signalling Network Management message from
the remote M3UA Peer, the M3UA layer updates the status of the affected the remote M3UA Peer, the M3UA layer updates the status of the affected
route(s) via the originating SGP and determines, whether or not the route(s) via the originating SG and determines, whether or not the
overall availability or congestion status of the effected overall availability or congestion status of the effected
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.
4.3.3 ASP Auditing 4.5.3 ASP Auditing
An ASP may optionally initiate an audit procedure to enquire An ASP may optionally initiate an audit procedure to enquire
of an SGP the availability and, if the national congestion method with of an 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 un-sequenced. The DAUD MAY be sent by the The DAUD message MAY be sent unsequenced. The DAUD MAY be sent by the
ASP in the following cases: ASP in the following cases:
- Periodic. A Timer originally set upon reception of a DUNA, SCON - Periodic. A Timer originally set upon reception of a DUNA, SCON
or DRST message has expired without a subsequent DAVA, or DRST message has expired without a subsequent DAVA,
DUNA, SCON or DRST message updating the DUNA, SCON or DRST message updating the
availability/congestion status of the affected availability/congestion status of the affected
Destination Point Codes. The Timer is reset upon Destination Point Codes. The Timer is reset upon
issuing a DAUD. In this case the DAUD is sent to the issuing a DAUD. In this case the DAUD is sent to the
SGP that originally sent the SSNM message. SGP that originally sent the SSNM message.
skipping to change at page 83, line 30 skipping to change at page 85, line 30
invoked for the case of a received SCON message containing a congestion invoked for the case of a received SCON message containing a congestion
level value of "no congestion" or undefined" (i.e., congestion Level = level value of "no congestion" or undefined" (i.e., congestion Level =
"0"). This is because the value indicates either congestion abatement "0"). This is because the value indicates either congestion abatement
or that the ITU MTP3 international congestion method is being used. In or that the ITU MTP3 international congestion method is being used. In
the international congestion method, the MTP3 layer at the SGP does not the international congestion method, the MTP3 layer at the SGP does not
maintain the congestion status of any destinations and therefore the maintain the congestion status of any destinations and therefore the
SGP cannot provide any congestion information in response to the DAUD. SGP cannot provide any congestion information in response to the DAUD.
For the same reason, in the second of the cases above a DAUD message For the same reason, in the second of the cases above a DAUD message
cannot reveal any congested destination(s). cannot reveal any congested destination(s).
The SGP MUST respond to a DAUD message with the MTP3 The SGP SHOULD respond to a DAUD message with the MTP3
availability/congested status of the routeset associated with each availability/congested status of the routeset associated with each
Destination Point Code(s) in the DAUD message. The status of each SS7 Destination Point Code(s) in the DAUD message. The status of each SS7
destination requested is indicated in a DUNA message (if unavailable), destination requested is indicated in a DUNA message (if unavailable),
a DAVA message (if available), or a DRST (if restricted and the SGP a DAVA message (if available), or a DRST (if restricted and the SGP
supports this feature). If the SS7 destination is available and supports this feature). Where the SGP maintains the congestion status
congested, the SGP responds with an SCON message in addition to the of the SS7 destination, and the SS7 destination is congested, the SGP
DAVA message. If the SS7 destination is restricted and congested, the MUST additionally respond with an SCON message before the DAVA or DRST
SGP responds with an SCON message in addition to the DRST. If the SGP message. If the SS7 destination is available and congested, the SGP
has no information on the availability/congestion status of the SS7 MUST respond with an SCON message DAVA message. If the SS7
destination, the SGP responds with a DUNA message, as it has no routing destination is restricted and congested, the SGP MUST respond with
information to allow it to route traffic to this destination an SCON message immediately followed by a DRST message. If the SGP
has no information on the availability status of the SS7 destination,
the SGP responds with a DUNA message, as it has no routing
information to allow it to route traffic to this destination.
Any DUNA or DAVA message in response to a DAUD message MAY contain a Any DUNA or DAVA message in response to a DAUD message MAY contain a
list of up to sixteen Affected Point Codes. list of up to sixteen Affected Point Codes.
4.4 MTP3 Restart An SG MAY refuse to provide the availability or congestion status of
a destination if, for example, the ASP is not authorized to know the
status of the destination. The SG MAY respond with an Error Message
(Error Code = "Destination Status Unknown")
4.6 MTP3 Restart
In the case where the MTP3 in the SG undergoes an MTP restart, event In the case where the MTP3 in the SG undergoes an MTP restart, event
communication SHOULD be handled as follows: communication SHOULD be handled as follows:
When the SG discovers SS7 network isolation, the SGPs send an When the SG discovers SS7 network isolation, the SGPs send an
indication to all concerned available ASPs (i.e., ASPs in the ASP- indication to all concerned available ASPs (i.e., ASPs in the ASP-
ACTIVE, ASP-STANDBY or ASP-INACTIVE state) using a DUNA message. For ACTIVE state) using DUNA messages for the concerned destinations.
the purpose of MTP restart, all Signalling Point Management Clusters
with point codes
different from that of the SG with at least one ASP in the ASP-ACTIVE When the SG has completed the MTP Restart procedure, the M3UA
state or that has sent an ASP ACTIVE message to the SG during the first layers at the SGPs inform all concerned ASPs in the ASP-ACTIVE state
part of the restart procedure should be considered as available. If the of any available/restricted SS7 destinations using the DAVA/DRST
M3UA layer at the SGP receives any ASP ACTIVE messages during the messages. No message is necessary for those destinations still
restart procedure, it delays the ASP ACTIVE ACK messages until the end unavailable after the restart procedure.
of the restart procedure. During the second part of the restart
procedure the SGP M3UA layers at the SGPs inform all concerned ASPs in
the ASP-ACTIVE, ASP-STANDBY or ASP-INACTIVE states of any
unavailable/restricted SS7 destinations using the DUNA/DRST message. At
the end of the restart procedure the SGP M3UA layers send an ASP ACTIVE
ACK message to all ASPs in the ASP-ACTIVE state.
When the M3UA layer at an ASP receives a DUNA message indicating SS7 When the M3UA layer at an ASP receives a DUNA message indicating SS7
network isolation at an SG, it will stop any affected traffic via this destination unavailability at an SG, MTP Users will receive an
route. When the M3UA subsequently receives any DUNA messages from an SGP MTP-PAUSE indication and will stop any affected traffic to this
it will mark the affected SS7 destinations as unavailable via that SG. destination. When the M3UA receives a DAVA/DRST message, MTP Users
When the M3UA receives an ASP ACTIVE ACK message it can resume traffic will receive an MTP-RESUME indication and can resume traffic to the
to available SS7 destinations via this SGP, provided the ASP is in the newly available SS7 destination, provided the ASP is in the
ASP-ACTIVE state towards this SGP. The ASP MAY choose to audit the ASP-ACTIVE state towards this SGP.
availability of any unavailable destinations
The ASP MAY choose to audit the availability of unavailable
destinations by sending DAUD messages. This would be for example the
case when an AS becomes active at an ASP and does not have current
destination statuses. If MTP restart is in progress at the
SG, the SGP returns a DUNA message for that destination, even if it
received an indication that the destination became available or
restricted.
In the IPSP case, MTP restart could be considered if the IPSP also has
connection to an SS7 network. In that case, the same behavior as
described above for the SGP would apply to the restarting IPSP. This
would also be the case if the IPSPs were perceived as exchanging MTP
Peer PDUs, instead of MTP primitives between MTP User and MTP
Provider. In other words, M3UA does not provide the equivalent to
Traffic Restart Allowed messages indicating the end of the restart
procedure between peer IPSPs that would also be connected to an SS7
network.
5. Examples of M3UA Procedures 5. Examples of M3UA Procedures
5.1 Establishment of Association and Traffic between SGPs and ASPs 5.1 Establishment of Association and Traffic between SGPs and ASPs
These scenarios show the example M3UA message flows for the
establishment of traffic between an SGP and an ASP or between two
IPSPs. In all cases it is assumed that the SCTP association is
already set up.
5.1.1 Single ASP in an Application Server ("1+0" sparing), 5.1.1 Single ASP in an Application Server ("1+0" sparing),
5.1.1.1 Single ASP in an Application Server ("1+0" sparing), No These scenarios show the example M3UA message flows for the
Registration establishment of traffic between an SGP and an ASP or between two
IPSPs, where only one ASP/IPSP is configured within an AS/IPS
(no backup).
This scenario shows the example M3UA message flows for the 5.1.1.1 Single ASP/IPSP in an Application Server/IPS ("1+0" sparing),
establishment of traffic between an SGP and an ASP, where only one ASP No Registration
is configured within an AS (no backup). It is assumed that the SCTP
association is already set-up. The sending of any DUNA/SCON messages by The sending of any DUNA/SCON messages by
the SGP is not shown but is similar to the case described in Section the SGP is not shown but is similar to the case described in Section
5.1.2. 5.1.2.
SGP ASP1 SGP/IPSP ASP1/IPSP1
| | | |
|<-------------ASP Up------------| |<-------------ASP Up------------|
|-----------ASP Up Ack---------->| |-----------ASP Up Ack---------->|
| | | |
|<------- ASP Active(RCn)--------| RC: Routing Context |<------- ASP Active(RCn)--------| RC: Routing Context
|-----ASP Active Ack (RCn)------>| (optional) |-----ASP Active Ack (RCn)------>| (optional)
| | | |
Note: If the ASP Active message contains an optional Routing Context Note: If the ASP Active message contains an optional Routing Context
parameter, The ASP Active message only applies for the specified RC parameter, The ASP Active message only applies for the specified RC
value(s). For an unknown RC value, the SGP responds with an Error value(s). For an unknown RC value, the SGP responds with an Error
message. message.
5.1.1.2 Single ASP in Application Server ("1+0" sparing), Dynamic 5.1.1.2 Single ASP/IPSP in Application Server/IPS ("1+0" sparing),
Registration Dynamic Registration
This scenario is the same as for 5.1.1.1 but with the optional exchange This scenario is the same as for 5.1.1.1 but with the optional exchange
of registration information. In this case the Registration is accepted of registration information. In this case the Registration is accepted
by the SGP. by the SGP/IPSP.
SGP ASP1 SGP/IPSP ASP1/IPSP1
| | | |
|<------------ASP Up-------------| |<------------ASP Up-------------|
|----------ASP Up Ack----------->| |----------ASP Up Ack----------->|
| | | |
|<----REGISTER REQ(LRCn,RKn)-----| LRC: Local Routing |<----REGISTER REQ(LRCn,RKn)-----| LRC: Local Routing
| | Context | | Context
|----REGISTER RESP(LRCn,RCn)---->| RK: Routing Key |----REGISTER RESP(LRCn,RCn)---->| RK: Routing Key
| | RC: Routing Context | | RC: Routing Context
| | | |
|<------- ASP Active(RCn)--------| |<------- ASP Active(RCn)--------|
|-----ASP Active Ack (RCn)------>| |-----ASP Active Ack (RCn)------>|
| | | |
Note: In the case of an unsuccessful registration attempt (e.g., Note: In the case of an unsuccessful registration attempt (e.g.,
Invalid RKn), the Register Response message will contain an invalid RKn), the Register Response message will contain an
unsuccessful indication and the ASP will not subsequently send an ASP unsuccessful indication and the ASP/IPSP will not subsequently send
Active message. an ASP Active message.
5.1.1.3 Single ASP in Multiple Application Servers (each with "1+0" 5.1.1.3 Single ASP/IPSP in Multiple Application Servers/IPSs (each
sparing), Dynamic Registration (Case 1 - Multiple Registration with "1+0" sparing), Dynamic Registration (Case 1 - Multiple
Requests) Registration Requests)
SGP ASP1 SGP/IPSP ASP1/IPSP1
| | | |
|<------------ASP Up-------------| |<------------ASP Up-------------|
|----------ASP Up Ack----------->| |----------ASP Up Ack----------->|
| | | |
|<----REGISTER REQ(LRC1,RK1)-----| LRC: Local Routing |<----REGISTER REQ(LRC1,RK1)-----| LRC: Local Routing
| | Context | | Context
|----REGISTER RESP(LRC1,RC1)---->| RK: Routing Key |----REGISTER RESP(LRC1,RC1)---->| RK: Routing Key
| | RC: Routing Context | | RC: Routing Context
| | | |
|<------- ASP Active(RC1)--------| |<------- ASP Active(RC1)--------|
skipping to change at page 86, line 6 skipping to change at page 88, line 38
|<----REGISTER REQ(LRCn,RKn)-----| |<----REGISTER REQ(LRCn,RKn)-----|
| | | |
|----REGISTER RESP(LRCn,RCn)---->| |----REGISTER RESP(LRCn,RCn)---->|
| | | |
| | | |
|<------- ASP Active(RCn)--------| |<------- ASP Active(RCn)--------|
|-----ASP Active Ack (RCn)------>| |-----ASP Active Ack (RCn)------>|
| | | |
Note: In the case of an unsuccessful registration attempt (e.g., Note: In the case of an unsuccessful registration attempt (e.g.,
Invalid RKn), the Register Response message will contain an invalid RKn), the Register Response message will contain an
unsuccessful indication and the ASP will not subsequently send an ASP unsuccessful indication and the ASP/IPSP will not subsequently send
Active message. Each LRC/RK pair registration is considered an ASP Active message. Each LRC/RK pair registration is considered
independently. independently.
It is not necessary to follow a Registration Request/Response message It is not necessary to follow a Registration Request/Response message
pair with an ASP Active message before sending the next Registration pair with an ASP Active message before sending the next Registration
Request. The ASP Active message can be sent at any time after the Request. The ASP Active message can be sent at any time after the
related successful registration. related successful registration.
5.1.1.4 Single ASP in Multiple Application Servers (each with "1+0" 5.1.1.4 Single ASP/IPSP in Multiple Application Servers/IPSs (each
sparing), Dynamic Registration (Case 2 - Single Registration Request) with "1+0" sparing), Dynamic Registration (Case 2 - Single
Registration Request)
SGP ASP1 SGP/IPSP ASP1/IPSP1
| | | |
|<------------ASP Up-------------| |<------------ASP Up-------------|
|----------ASP Up Ack----------->| |----------ASP Up Ack----------->|
| | | |
|<---REGISTER REQ({LRC1,RK1},----| |<---REGISTER REQ({LRC1,RK1},----|
| ..., | | ..., |
| {LRCn,RKn}),----| | {LRCn,RKn}),----|
| | | |
|---REGISTER RESP({LRC1,RC1},--->| |---REGISTER RESP({LRC1,RC1},--->|
| ..., | | ..., |
skipping to change at page 86, line 44 skipping to change at page 89, line 29
| | | |
: : : :
: : : :
| | | |
|<------- ASP Active(RCn)--------| |<------- ASP Active(RCn)--------|
|-----ASP Active Ack (RCn)------>| |-----ASP Active Ack (RCn)------>|
| | | |
Note: In the case of an unsuccessful registration attempt (e.g., Note: In the case of an unsuccessful registration attempt (e.g.,
Invalid RKn), the Register Response message will contain an Invalid RKn), the Register Response message will contain an
unsuccessful indication and the ASP will not subsequently send an ASP unsuccessful indication and the ASP/IPSP will not subsequently
Active message. Each LRC/RK pair registration is considered send an ASP Active message. Each LRC/RK pair registration is
independently. considered independently.
The ASP Active message can be sent at any time after the related The ASP Active message can be sent at any time after the related
successful registration, and may have more than one RC. successful registration, and may have more than one RC.
5.1.2 Two ASPs in Application Server ("1+1" sparing) 5.1.2 Two ASPs/IPSPs in Application Server/IPS ("1+1" sparing)
This scenario shows the example M3UA message flows for the This scenario shows the example M3UA message flows for the
establishment of traffic between an SGP and two ASPs in the same establishment of traffic between an SGP and two ASPs in the same
Application Server, where ASP1 is configured to be in the ASP-ACTIVE Application Server, or between an IPSP and two IPSPs in the same
state and ASP2 is to be a "back-up" in the event of communication IPS, where ASP1/IPSP1 is configured to be in the ASP-ACTIVE
failure or the withdrawal from service of ASP1. ASP2 may act as a hot, state and ASP2/IPSP2 is to be a "backup" in the event of
warm, or cold back-up depending on the extent to which ASP1 and ASP2 communication failure or the withdrawal from service of
share call/transaction state or can communicate call state under ASP1/IPSP1. ASP2/IPSP2 may act as a hot, warm, or cold backup
failure/withdrawal events. The example message flow is the same depending on the extent to which ASP1/IPSP1 and ASP2/IPSP2
whether the ASP Active messages indicate "Over-ride", "Load-share" or share call/transaction state or can communicate call state
"Broadcast" mode, although typically this example would use an Over-ride under failure/withdrawal events. The example message flow is
mode. The the same whether the ASP Active messages indicate "Override",
SGP MAY start sending any relevant DUNA, DRST and SCON messages to ASPs "Loadshare" or "Broadcast" mode, although typically this example
as soon as they enter the ASP-INACTIVE state. In the case of MTP would use an Override mode. The SGP MAY start sending any
Restart, the ASP-Active Ack message is only sent after all relevant relevant DUNA, DRST and SCON messages to ASPs as soon as they
DUNA/DRST/SCON messages have been transmitted to the concerned ASP. enter the ASP-INACTIVE state.
SGP ASP1 ASP2 SGP/IPSP ASP1/IPSP1 ASP2/IPSP2
| | | | | |
|<--------ASP Up----------| | |<--------ASP Up----------| |
|-------ASP Up Ack------->| | |-------ASP Up Ack------->| |
| | | | | |
|<-----------------------------ASP Up----------------| |<-----------------------------ASP Up----------------|
|-----------------------------ASP Up Ack------------>| |-----------------------------ASP Up Ack------------>|
| | | | | |
| | | | | |
|<-------ASP Active-------| | |<-------ASP Active-------| |
|------ASP Active Ack---->| | |------ASP Active Ack---->| |
| | | | | |
Note: It is also possible for ASP2 to send an ASP-Active ("Over-ride- 5.1.3 Two ASPs/IPSPs in an Application Server/IPS ("1+1" sparing,
Standby") message after ASP1 goes ASP-ACTIVE A similar sparing loadsharing case)
arrangement is created, except that the SGP may re-direct traffic to
ASP2 more quickly in certain fail-over cases.
5.1.3 Two ASPs in an Application Server ("1+1" sparing, load-sharing
case)
This scenario shows a similar case to Section 5.1.2 but where the two This scenario shows a similar case to Section 5.1.2 but where the
ASPs are brought to the state ASP-ACTIVE and subsequently load-share two ASPs/IPSPs are brought to the state ASP-ACTIVE and subsequently
the traffic. In this case, one ASP is sufficient to handle the total loadshare the traffic. In this case, one ASP/IPSP is sufficient
traffic load. The sending of DUNA, DRST and SCON messages by the SGP is to handle the total traffic load. The sending of DUNA, DRST and
not shown but is similar to the case described in Section 5.1.2. SCON messages by the SGP is not shown but is similar to the case
described in Section 5.1.2.
SGP ASP1 ASP2 SGP/IPSP ASP1/IPSP1 ASP2/IPSP2
| | | | | |
|<---------ASP Up---------| | |<---------ASP Up---------| |
|--------ASP Up Ack------>| | |--------ASP Up Ack------>| |
| | | | | |
|<------------------------------ASP Up---------------| |<------------------------------ASP Up---------------|
|-----------------------------ASP Up Ack------------>| |-----------------------------ASP Up Ack------------>|
| | | | | |
| | | | | |
|<--ASP Active (Ldshr)----| | |<--ASP Active (Ldshr)----| |
|-----ASP-Active Ack----->| | |-----ASP-Active Ack----->| |
| | | | | |
|----------------------------NOTIFY (AS-ACTIVE------>| |----------------------------NOTIFY (AS-ACTIVE------>|
| | | | | |
|<----------------------------ASP Active (Ldshr)-----| |<----------------------------ASP Active (Ldshr)-----|
|-------------------------------ASP Active Ack------>| |-------------------------------ASP Active Ack------>|
| | | | | |
5.1.4 Three ASPs in an Application Server ("n+k" sparing, load-sharing 5.1.4 Three ASPs/IPSPs in an Application Server/IPS ("n+k" sparing,
case) loadsharing case)
This scenario shows the example M3UA message flows for the This scenario shows the example M3UA message flows for the
establishment of traffic between an SGP and three ASPs in the same establishment of traffic between an SGP and three ASPs in the same
Application Server, where two of the ASPs are brought to the state ASP- Application Server, or between an IPSP and three IPSPs in the same
ACTIVE and subsequently share the load. In this case, a minimum of two
ASPs are required to handle the total traffic load (2+1 sparing). The
sending of DUNA, DRST and SCON messages by the SGP is not shown but is
similar to the case described in Section 5.1.2.
SGP ASP1 ASP2 ASP3 IPS, where two of the ASPs/IPSPs are brought to the state
ASP-ACTIVE and subsequently share the load. In this case, a minimum
of two ASPs/IPSPs are required to handle the total traffic load
(2+1 sparing). The sending of DUNA, DRST and SCON messages by the
SGP is not shown but is similar to the case described in Section 5.1.2.
SGP/IPSP ASP1/IPSP1 ASP2/IPSP2 ASP3/IPSP3
| | | | | | | |
|<------ASP Up-------| | | |<------ASP Up-------| | |
|-----ASP Up Ack---->| | | |-----ASP Up Ack---->| | |
| | | | | | | |
|<--------------------------ASP Up-------| | |<--------------------------ASP Up-------| |
|-------------------------ASP Up Ack---->| | |-------------------------ASP Up Ack---->| |
| | | | | | | |
|<---------------------------------------------ASP Up--------| |<---------------------------------------------ASP Up--------|
|---------------------------------------------ASP Up Ack---->| |---------------------------------------------ASP Up Ack---->|
| | | | | | | |
skipping to change at page 89, line 5 skipping to change at page 91, line 33
|<--ASP Act (Ldshr)--| | | |<--ASP Act (Ldshr)--| | |
|----ASP Act Ack---->| | | |----ASP Act Ack---->| | |
| | | | | | | |
-----------Notify (AS-ACTIVE)----------->| | -----------Notify (AS-ACTIVE)----------->| |
|-----------------------Notify (AS-ACTIVE)------------------>| |-----------------------Notify (AS-ACTIVE)------------------>|
| | | | | | | |
|<--------------------ASP Act. (Ldshr)---| | |<--------------------ASP Act. (Ldshr)---| |
|-----------------------ASP Act Ack----->| | |-----------------------ASP Act Ack----->| |
| | | | | | | |
Note: It is also possible for ASP3 to send an ASP Active message 5.2 ASP/IPSP Traffic Failover Examples
("Loadshare-Standby") after ASP1 and ASP2 go to the ASP-ACTIVE state A
similar sparing arrangement is created, except that the SGP may
redirect traffic to ASP3 more quickly in certain fail-over cases.
5.2 ASP Traffic Fail-over Examples
5.2.1 (1+1 Sparing, Withdrawal of ASP, Back-up Over-ride) 5.2.1 (1+1 Sparing, Withdrawal of ASP/IPSP, Backup Override)
Following on from the example in Section 5.1.2, and ASP1 withdraws from Following on from the example in Section 5.1.2, and ASP1/IPSP1
service: withdraws from service:
SGP ASP1 ASP2 SGP/IPSP ASP1/IPSP1 ASP2/IPSP2
| | | | | |
|<-----ASP Inactive-------| | |<-----ASP Inactive-------| |
|----ASP Inactive Ack---->| | |----ASP Inactive Ack---->| |
|------------------------NTFY(AS-Pending)----------->| |------------------------NTFY(AS-Pending)----------->|
| | | | | |
|<------------------------------ ASP Active----------| |<------------------------------ ASP Active----------|
|------------------------------ASP Active Ack------->| |------------------------------ASP Active Ack------->|
| | | |
Note: If the SGP M3UA layer detects the loss of the M3UA peer (M3UA Note: If the SGP/IPSP M3UA layer detects the loss of the M3UA peer
heartbeat loss or detection of SCTP failure), the initial ASP Inactive (e.g., M3UA heartbeat loss or detection of SCTP failure), the
message exchange (i.e., SGP to ASP1) would not occur. initial ASP Inactive message exchange (i.e., between ASP1/IPSP1
and SGP/IPSP) would not occur.
5.2.2 (1+1 Sparing, Back-up Over-ride) 5.2.2 (1+1 Sparing, Backup Override)
Following on from the example in Section 5.1.2, ASP2 wishes to Following on from the example in Section 5.1.2, ASP2/IPSP2 wishes to
over-ride ASP1 and take over the traffic: Override ASP1/IPSP1 and take over the traffic:
SGP ASP1 ASP2 SGP/IPSP ASP1/IPSP1 ASP2/IPSP2
| | | | | |
|<------------------------------ ASP Active----------| |<------------------------------ ASP Active----------|
|-------------------------------ASP Active Ack------>| |-------------------------------ASP Active Ack------>|
|----NTFY(Alt ASP-Act)--->| |----NTFY(Alt ASP-Act)--->|
| | | | | |
5.2.3 (n+k Sparing, Load-sharing case, Withdrawal of ASP) 5.2.3 (n+k Sparing, Loadsharing case, Withdrawal of ASP/IPSP)
Following on from the example in Section 5.1.4, and ASP1 withdraws from Following on from the example in Section 5.1.4, and ASP1/IPSP1
service: withdraws from service:
SGP ASP1 ASP2 ASP3 SGP/IPSP ASP1/IPSP1 ASP2/IPSP2 ASP3/IPSP3
| | | | | | | |
|<----ASP Inact.-----| | | |<----ASP Inact.-----| | |
|---ASP Inact Ack--->| | | |---ASP Inact Ack--->| | |
| | | | | | | |
|---------------------------------NTFY(Ins. ASPs)----------->| |---------------------------------NTFY(Ins. ASPs)----------->|
| | | | | | | |
|<-----------------------------------------ASP Act (Ldshr)---| |<-----------------------------------------ASP Act (Ldshr)---|
|-------------------------------------------ASP Act (Ack)--->| |-------------------------------------------ASP Act (Ack)--->|
| | | | | | | |
For the Notify message to be sent, the SG maintains knowledge of the For the Notify message to be sent, the SG/IPSP maintains knowledge of
minimum ASP resources required (e.g., if the SG knows that "n+k" = the minimum ASP/IPSP resources required (e.g., if the SG/IPSP knows
"2+1" for a load-share AS and "n" currently equals "1"). that "n+k" = "2+1" for a Loadshare AS/IPS and "n" currently equals
"1").
Note: If the SGP detects loss of the ASP1 M3UA peer (M3UA heartbeat Note: If the SGP/IPSP detects loss of the ASP1/IPSP1 M3UA peer (e.g.,
loss or detection of SCTP failure), the initial ASP Inactive message M3UA heartbeat loss or detection of SCTP failure), the initial ASP
exchange (i.e., SGP-ASP1) would not occur. Inactive message exchange (i.e., SGP/IPSP-ASP1/IPSP1) would not occur.
5.3 Normal Withdrawal of an ASP from an Application Server and Tear- 5.3 Normal Withdrawal of an ASP/IPSP from an Application Server/IPS
down of an Association and Teardown of an Association
An ASP which is now confirmed in the state ASP-INACTIVE (i.e., the ASP An ASP/IPSP which is now confirmed in the state ASP-INACTIVE (i.e.,
has received an ASP Inactive Ack message) may now proceed to the ASP- the ASP/IPSP has received an ASP Inactive Ack message) may now proceed
DOWN state, if it is to be removed from service. Following on from to the ASP-DOWN state, if it is to be removed from service. Following
Section 5.2.1 or 5.2.3, where ASP1 has moved to the "Inactive" state: on from Section 5.2.1 or 5.2.3, where ASP1/IPSP1 has moved to the
"Inactive" state:
SGP ASP1 SGP/IPSP ASP1/IPSP1
| | | |
|<-----ASP Inactive (RCn)-------| RC: Routing Context |<-----ASP Inactive (RCn)-------| RC: Routing Context
|----ASP Inactive Ack (RCn)---->| |----ASP Inactive Ack (RCn)---->|
| | | |
|<-----DEREGISTER REQ(RCn)------| See Notes |<-----DEREGISTER REQ(RCn)------| See Notes
| | | |
|---DEREGISTER RESP(LRCn,RCn)-->| |---DEREGISTER RESP(LRCn,RCn)-->|
| | | |
: : : :
| | | |
|<-----------ASP Down-----------| |<-----------ASP Down-----------|
|---------ASP Down Ack--------->| |---------ASP Down Ack--------->|
| | | |
Note: The Deregistration procedure MUST be used if the ASP previously Note: The Deregistration procedure MUST be used if the ASP/IPSP
used the Registration procedures for configuration within the previously used the Registration procedures for configuration
Application Server. ASP Inactive and Deregister messages exchanges may within the Application Server/IPS. ASP Inactive and Deregister
contain multiple Routing Contexts. messages exchanges may contain multiple Routing Contexts.
The ASP SHOULD be in the ASP-INACTIVE state and SHOULD have deregistered The ASP/IPSP SHOULD be in the ASP-INACTIVE state and SHOULD have
in all its Routing Contexts before attempting to move to the ASP-DOWN deregistered in all its Routing Contexts before attempting to move
state. to the ASP-DOWN state.
5.4 M3UA/MTP3-User Boundary Examples 5.4 M3UA/MTP3-User Boundary Examples
5.4.1 At an ASP 5.4.1 At an ASP/IPSP
This section describes the primitive mapping between the MTP3 User and This section describes the primitive mapping between the MTP3 User and
the M3UA layer at an ASP. the M3UA layer at an ASP or IPSP.
5.4.1.1 Support for MTP-TRANSFER Primitives at the ASP 5.4.1.1 Support for MTP-TRANSFER Primitives at the ASP
5.4.1.1.1 Support for MTP-TRANSFER Request Primitive 5.4.1.1.1 Support for MTP-TRANSFER Request Primitive
When the MTP3-User on the ASP has data to send into the SS7 network, it When the MTP3-User on the ASP/IPSP has data to send to a remote
uses the MTP-TRANSFER request primitive. The M3UA layer at the ASP MTP3-User, it uses the MTP-TRANSFER request primitive. The M3UA
will do the following when it receives an MTP-TRANSFER request layer at the ASP/IPSP will do the following when it receives an
primitive from the M3UA user: MTP-TRANSFER request primitive from the M3UA user:
- Determine the correct SGP; - Determine the correct SGP/IPSP;
- Determine the correct association to the chosen SGP; - Determine the correct association to the chosen SGP/IPSP;
- Determine the correct stream in the association (e.g., based on - Determine the correct stream in the association (e.g., based on
SLS); SLS);
- Determine whether to complete the optional fields of the DATA - Determine whether to complete the optional fields of the DATA
message; message;
- Map the MTP-TRANSFER request primitive into the Protocol Data - Map the MTP-TRANSFER request primitive into the Protocol Data
field of a DATA message; field of a DATA message;
- Send the DATA message to the remote M3UA peer at the SGP, over the - Send the DATA message to the remote M3UA peer at the SGP/IPSP, over
SCTP association. the SCTP association.
SGP ASP SGP/IPSP ASP/IPSP
| | | |
|<-----DATA Message-------|<--MTP-TRANSFER req. |<-----DATA Message-------|<--MTP-TRANSFER req.
| | | |
5.4.1.1.2 Support for the MTP-TRANSFER Indication Primitive 5.4.1.1.2 Support for the MTP-TRANSFER Indication Primitive
When the M3UA layer on the ASP receives a DATA message from the remote When the M3UA layer on the ASP/IPSP receives a DATA message from the
M3UA peer at the SGP, it will do the following: M3UA peer at the remote SGP/IPSP, it will do the following:
- Evaluate the optional fields of the DATA message, if present; - Evaluate the optional fields of the DATA message, if present;
- Map the Protocol Data field of a DATA message into the MTP-TRANSFER - Map the Protocol Data field of a DATA message into the MTP-TRANSFER
indication primitive; indication primitive;
- Pass the MTP-TRANSFER indication primitive to the user part. In - Pass the MTP-TRANSFER indication primitive to the user part. In
case of multiple user parts, the optional fields of the Data case of multiple user parts, the optional fields of the Data
message are used to determine the concerned user part. message are used to determine the concerned user part.
SGP ASP SGP/IPSP ASP/IPSP
| | | |
|------Data Message------>|-->MTP-Transfer ind. |------Data Message------>|-->MTP-Transfer ind.
| | | |
5.4.1.1.3 Support for ASP Querying of SS7 Destination States 5.4.1.1.3 Support for ASP Querying of SS7 Destination States
There are situations such as temporary loss of connectivity to the SGP There are situations such as temporary loss of connectivity to the SGP
that may cause the M3UA layer at the ASP to audit SS7 destination that may cause the M3UA layer at the ASP to audit SS7 destination
availability/congestion states. Note: there is no primitive for the availability/congestion states. Note: there is no primitive for the
MTP3-User to request this audit from the M3UA layer as this is MTP3-User to request this audit from the M3UA layer as this is
skipping to change at page 95, line 14 skipping to change at page 97, line 32
6. Security 6. Security
6.1 Introduction 6.1 Introduction
M3UA is designed to carry signalling messages for telephony services. M3UA is designed to carry signalling messages for telephony services.
As such, M3UA must involve the security needs of several parties: the As such, M3UA must involve the security needs of several parties: the
end users of the services; the network providers and the applications end users of the services; the network providers and the applications
involved. Additional requirements may come from local regulation. involved. Additional requirements may come from local regulation.
While having some overlapping security needs, any security solution While having some overlapping security needs, any security solution
should fulfil all of the different parties' needs. should fulfill all of the different parties' needs.
6.2 Threats 6.2 Threats
There is no quick fix, one-size-fits-all solution for security. As a There is no quick fix, one-size-fits-all solution for security. As a
transport protocol, M3UA has the following security objectives: transport protocol, M3UA has the following security objectives:
* Availability of reliable and timely user data transport. * Availability of reliable and timely user data transport.
* Integrity of user data transport. * Integrity of user data transport.
* Confidentiality of user data. * Confidentiality of user data.
skipping to change at page 96, line 28 skipping to change at page 98, line 47
values MUST not be used. This Payload Protocol Identifier is not values MUST not be used. This Payload Protocol Identifier is not
directly used by SCTP but MAY be used by certain network entities to directly used by SCTP but MAY be used by certain network entities to
identify the type of information being carried in a DATA chunk. identify the type of information being carried in a DATA chunk.
The User Adaptation peer MAY use the Payload Protocol Identifier as a The User Adaptation peer MAY use the Payload Protocol Identifier as a
way of determining additional information about the data being way of determining additional information about the data being
presented to it by SCTP. presented to it by SCTP.
7.2 M3UA Port Number 7.2 M3UA Port Number
IANA has registered SCTP (and UDP/TCP) Port Number 2905 for M3UA. IANA has registered SCTP (and UDP/TCP) Port Number 2905 for M3UA. It
is recommended that SGPs use this SCTP port number for listening for
new connections. SGPs MAY also use statically configured SCTP port
numbers instead.
7.3 M3UA Protocol Extensions 7.3 M3UA Protocol Extensions
This protocol may also be extended through IANA in three ways: This protocol may also be extended through IANA in three ways:
-- through definition of additional message classes, -- through definition of additional message classes,
-- through definition of additional message types, and -- through definition of additional message types, and
-- through definition of additional message parameters -- through definition of additional message parameters
The definition and use of new message classes, types and parameters is The definition and use of new message classes, types and parameters is
an integral part of SIGTRAN adaptation layers. Thus these extensions an integral part of SIGTRAN adaptation layers. Thus these extensions
skipping to change at page 97, line 37 skipping to change at page 100, line 11
(c) Detailed definition of each component of the parameter value; (c) Detailed definition of each component of the parameter value;
(d) Detailed description of the intended use of this parameter type, (d) Detailed description of the intended use of this parameter type,
and an indication of whether and under what circumstances multiple and an indication of whether and under what circumstances multiple
instances of this parameter type may be found within the same instances of this parameter type may be found within the same
message. message.
8. Acknowledgements 8. Acknowledgements
The authors would like to thank Antonio Roque Alvarez, Joyce Archibald, The authors would like to thank Antonio Roque Alvarez, Joyce Archibald,
Tolga Asveren, Maria-Cruz Bartolome-Rodrigo, Dan Brendes, Nikhil Jain, Tolga Asveren, Maria-Cruz Bartolome-Rodrigo, Dan Brendes, Nikhil Jain,
Joe Keller, Kurt Kite, Ming Lin, Steve Lorusso, John Loughney, Naoto Roland Jesske, Joe Keller, Kurt Kite, Ming Lin, Steve Lorusso, Naoto
Makinae, Howard May, Barry Nagelberg, Neil Olson, Heinz Prantner, Makinae, Howard May, Francois Mouillaud, Barry Nagelberg, Neil Olson,
Shyamal Prasad, Mukesh Punhani, Selvam Rengasami, Ray Singh, Michael Heinz Prantner, Shyamal Prasad, Mukesh Punhani, Selvam Rengasami,
Tuexen, Nitin Tomar, Gery Verwimp, Kazuo Watanabe, Ben Wilson and many John Shantz, Ray Singh, Michael Tuexen, Nitin Tomar, Gery Verwimp,
others for their valuable comments and suggestions. Tim Vetter, Kazuo Watanabe, Ben Wilson and many others for their
valuable comments and suggestions.
9. References 9. References
[1] RFC 2719, "Framework Architecture for Signaling Transport", L. Ong [1] RFC 2719, "Framework Architecture for Signaling Transport", L. Ong
et al, October 1999 et al, October 1999
[2] ITU-T Recommendations Q.761 to Q.767, "Signalling System No.7 (SS7) [2] ITU-T Recommendations Q.761 to Q.767, "Signalling System No.7 (SS7)
- ISDN User Part (ISUP)" - ISDN User Part (ISUP)"
[3] ANSI T1.113 - "Signaling System Number 7 - ISDN User Part" [3] ANSI T1.113 - "Signaling System Number 7 - ISDN User Part"
skipping to change at page 98, line 23 skipping to change at page 100, line 46
Control Part" Control Part"
[7] ETSI ETS 300 009-1, "Integrated Services Digital Network (ISDN); [7] ETSI ETS 300 009-1, "Integrated Services Digital Network (ISDN);
Signalling System No.7; Signalling Connection Control Part (SCCP) Signalling System No.7; Signalling Connection Control Part (SCCP)
(connectionless and connection-oriented class 2) to support (connectionless and connection-oriented class 2) to support
international interconnection; Part 1: Protocol specification" international interconnection; Part 1: Protocol specification"
[8] ITU-T Recommendation Q.720, "Telephone User Part" [8] ITU-T Recommendation Q.720, "Telephone User Part"
[9] ITU-T Recommendations Q.771 to Q.775 "Signalling System No. 7 (SS7) [9] ITU-T Recommendations Q.771 to Q.775 "Signalling System No. 7 (SS7)
- - Transaction Capabilities (TCAP)"
Transaction Capabilities (TCAP)"
[10] ANSI T1.114 "Signaling System Number 7 - Transaction Capabilities [10] ANSI T1.114 "Signaling System Number 7 - Transaction Capabilities
Application Part" Application Part"
[11] ETSI ETS 300 287-1, "Integrated Services Digital Network (ISDN); [11] ETSI ETS 300 287-1, "Integrated Services Digital Network (ISDN);
Signalling System No.7; Transaction Capabilities (TC) version 2; Signalling System No.7; Transaction Capabilities (TC) version 2;
Part 1: Protocol specification" Part 1: Protocol specification"
[12] 3G TS 25.410 V4.0.0 (2001-04) "Technical Specification - 3rd [12] 3G TS 25.410 V4.0.0 (2001-04) "Technical Specification - 3rd
Generation partnership Project; Technical Specification Group Generation partnership Project; Technical Specification Group
skipping to change at page 99, line 27 skipping to change at page 102, line 5
[23] RFC 2406, "IP Encapsulating Security Payload (ESP)", S.Kent and [23] RFC 2406, "IP Encapsulating Security Payload (ESP)", S.Kent and
R. Atkinson, November 1998. R. Atkinson, November 1998.
[24] RFC 2408, "Internet Security Association and Key Management [24] RFC 2408, "Internet Security Association and Key Management
Protocol", D. Maughan, M. Schertler, M. Schneider and J. Turner, Protocol", D. Maughan, M. Schertler, M. Schneider and J. Turner,
November 1998. November 1998.
[25] RFC 2434, "Guidelines for Writing an IANA Considerations Section [25] RFC 2434, "Guidelines for Writing an IANA Considerations Section
in RFCs", T. Narten and H. Alvestrand, October 1998 in RFCs", T. Narten and H. Alvestrand, October 1998
10. Bibliography [26] <draft-ietf-sigtran-m2ua-10.txt>, "MTP2-User Adaptation Layer",
K. Morneault et al, Sept 2001 (Work in Progress)
[26] <draft-ietf-sigtran-m2ua-09.txt>, "MTP2-User Adaptation Layer",
K. Morneault et al, July 2001 (Work in Progress)
[27]<draft-ietf-sigtran-m2pa-02.txt>, "SS7 MTP2-User Peer-to-Peer [27] <draft-ietf-sigtran-m2pa-03.txt>, "SS7 MTP2-User Peer-to-Peer
Adaptation Layer", Tom George et al (Work in Progress) Adaptation Layer", Tom George et al, July 2001 (Work in Progress)
11. Author's Addresses 10. Author's Addresses
Greg Sidebottom Greg Sidebottom
gregside consulting
Kanata, Ontario, Canada Kanata, Ontario, Canada
gregside@home.com EMail: gregside@home.com
Javier Pastor-Balb▀s
Ericsson Espa▒a S.A.
C/ Ombö 3
28045 Madrid - Spain
EMail: j.javier.pastor@ericsson.com
Guy Mousseau Guy Mousseau
Nortel Networks Nortel Networks
3685 Richmond Rd 3685 Richmond Rd
Nepean, Ontario, Canada K2H 5B7 EMail: Nepean, Ontario, Canada K2H 5B7
Lyndon Ong Lyndon Ong
Ciena Ciena
10480 Ridgeview Court 10480 Ridgeview Court
Cupertino, CA 95014 Cupertino, CA 95014
lyong@ciena.com EMail: lyong@ciena.com
Ian Rytina Ian Rytina
Ericsson Australia Ericsson Australia
37/360 Elizabeth Street 37/360 Elizabeth Street
Melbourne, Victoria 3000, Australia Melbourne, Victoria 3000, Australia
ian.rytina@ericsson.com.au EMail: ian.rytina@ericsson.com.au
Hanns Juergen Schwarzbauer Hanns Juergen Schwarzbauer
SIEMENS AG SIEMENS AG
Hofmannstr. 51 Hofmannstr. 51
81359 Munich, Germany 81359 Munich, Germany
HannsJuergen.Schwarzbauer@icn.siemens.de EMail: HannsJuergen.Schwarzbauer@icn.siemens.de
Klaus D. Gradischnig Klaus D. Gradischnig
NeuStar, Inc NeuStar, Inc
1120 Vermont Ave. N.W.Suite 400 1120 Vermont Ave. N.W.Suite 400
Washington D.C 20005 Washington D.C 20005
klaus.gradischnig@neustar.com EMail: klaus.gradischnig@neustar.com
Ken Morneault Ken Morneault
Cisco Systems Inc. Cisco Systems Inc.
13615 Dulles Technology Drive 13615 Dulles Technology Drive
Herndon, VA, USA 20171 Herndon, VA, USA 20171
EMail: EMail: kmorneau@cisco.com
Malleswar Kalla Malleswar Kalla
Telcordia Technologies Telcordia Technologies
MCC 1J211R MCC 1J211R
445 South Street 445 South Street
Morristown, NJ, USA 07960 Morristown, NJ, USA 07960
Email: kalla@research.telcordia.com Email: kalla@research.telcordia.com
Normand Glaude Normand Glaude
Performance Technologies Performance Technologies
150 Metcalf Sreet, Suite 1300 150 Metcalf Sreet, Suite 1300
Ottawa, Ontario, Canada K2P 1P1 Ottawa, Ontario, Canada K2P 1P1
EMail: nglaude@microlegend.com EMail: nglaude@microlegend.com
Brian Bidulock Brian Bidulock
OpenSS7 Corporation OpenSS7 Corporation
c/o #424, 4701 Preston Park Blvd. c/o #424, 4701 Preston Park Blvd.
Plano, TX, USA 75093 Plano, TX, USA 75093
EMail: bidulock@openss7.org EMail: bidulock@openss7.org
This draft expires December 2001. John Loughney
Nokia Research Center
PO Box 407
FIN-00045 Nokia Group
Finland
EMail: john.loughney@nokia.com
This draft expires April 2002.
 End of changes. 

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