draft-ietf-sigtran-m3ua-04.txt   draft-ietf-sigtran-m3ua-05.txt 
skipping to change at page 1, line 15 skipping to change at page 1, line 15
Ericsson Ericsson
Hanns-Juergen Schwarzbauer, Klaus Gradischnig Hanns-Juergen Schwarzbauer, Klaus Gradischnig
Siemens Siemens
Ken Morneault Ken Morneault
Cisco Cisco
Mallesh Kalla Mallesh Kalla
Telcordia Telcordia
Normand Glaude Normand Glaude
Performance Technologies Performance Technologies
Expires in six months Sept 2000 Expires in six months Nov 2000
SS7 MTP3-User Adaptation Layer (M3UA) SS7 MTP3-User Adaptation Layer (M3UA)
<draft-ietf-sigtran-m3ua-04.txt> <draft-ietf-sigtran-m3ua-05.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
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
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
any SS7 MTP3-User signalling (e.g., ISUP and SCCP messages) over IP any SS7 MTP3-User signalling (e.g., ISUP and SCCP messages) over IP
skipping to change at page 2, line 37 skipping to change at page 2, line 37
5. Examples of M3UA Procedures.......................................54 5. Examples of M3UA Procedures.......................................54
5.1 Establishment of Association and Traffic 5.1 Establishment of Association and Traffic
Between SGs and ASPs.........................................54 Between SGs and ASPs.........................................54
5.2 ASP traffic Fail-over Examples...............................56 5.2 ASP traffic Fail-over Examples...............................56
5.3 M3UA/MTP3-User Boundary Examples.............................57 5.3 M3UA/MTP3-User Boundary Examples.............................57
6. Security..........................................................61 6. Security..........................................................61
6.1 Introduction.................................................61 6.1 Introduction.................................................61
6.2 Threats......................................................61 6.2 Threats......................................................61
6.3 Protecting Confidentiality...................................62 6.3 Protecting Confidentiality...................................62
7. IANA Considerations...............................................62 7. IANA Considerations...............................................62
7.1 SCTP Payload Protocol Identifier.............................62
7.2 M3UA Protocol Extensions.....................................62
8. Acknowledgements..................................................62 8. Acknowledgements..................................................62
9. References........................................................62 9. References........................................................62
10. Author's Addresses...............................................65 10. Author's Addresses...............................................65
1. Introduction 1. Introduction
1.1 Scope 1.1 Scope
There is a need for SCN signalling protocol delivery from an SS7 There is a need for SCN signalling protocol delivery from an SS7
Signalling Gateway (SG) to a Media Gateway Controller (MGC) or IP- Signalling Gateway (SG) to a Media Gateway Controller (MGC) or IP-
skipping to change at page 6, line 20 skipping to change at page 6, line 20
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 - Data - Resistance to flooding and masquerade attacks; and
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 necessary. redundancy requirements, the SCTP functions above may not be necessary.
In these cases, it is acceptable to use TCP as the underlying common In these cases, it is acceptable to use TCP as the underlying common
transport protocol. transport 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 provides the equivalent set of primitives at The M3UA Layer at an ASP provides the equivalent set of primitives at
its upper layer to the MTP3-Users as provided by the MTP Level 3 to its its upper layer to the MTP3-Users as provided by the MTP Level 3 to its
skipping to change at page 6, line 54 skipping to change at page 6, line 54
two IP Server Processes (IPSPs). In this case, the M3UA provides the two IP Server Processes (IPSPs). In this case, the M3UA provides the
same set of primitives and services at its upper layer as the MTP3. 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 SG. The MTP3 services are provided but the procedures remotely from an SG. The MTP3 services are provided but the procedures
to support these services are a subset of the MTP3 procedures due to to support these services are a subset of the MTP3 procedures due to
the simplified point-to-point nature of the IPSP to IPSP relationship. the simplified point-to-point nature of the IPSP to IPSP relationship.
1.3.2.1 Support for the transport of MTP3-User Messages 1.3.2.1 Support for the transport of MTP3-User Messages
The M3UA provides the transport of MTP-TRANSFER primitives across an The M3UA provides the transport of MTP-TRANSFER primitives across an
established SCTP association between an SG and an ASP and between established SCTP association between an SG and an ASP or between
IPSPs. IPSPs.
The MTP-TRANSFER primitives are encoded as MTP3-User messages with The MTP-TRANSFER primitive information is encoded as in MTP3-User
attached MTP3 Routing Labels as described in the message format messages. In this way, the SCCP and ISUP messages received from the
sections of the SCCP and ISUP recommendations. In this way, the SCCP SS7 network by the SG are not re-encoded into a different format for
and ISUP messages received from the SS7 network are not re-encoded into transport between the M3UA peers. The MTP3 Service Information Octet
a different format for transport to/from the server processes. As (SIO) and Routing Label (OPC, DPC, and SLS) are included, encoded as
well, all the required MTP3 Routing Label information (OPC, DPC, SIO) expected by the MTP3-User protocol layer.
is available at the ASP and the IPSP as is expected by the 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
SGs, the M3UA must also choose via which SG the message is to be routed SGs, the M3UA must also choose via which SG the message is to be routed
or support load balancing across the SGs, ensuring that no mis- or support load balancing across the SGs, ensuring that no mis-
sequencing occurs. sequencing occurs.
The M3UA does not impose a 272-octet user information block limit as The M3UA does not impose a 272-octet user information block limit as
specified by the SS7 MTP Level 3 protocol. Larger information blocks specified by the SS7 MTP Level 3 protocol. Larger information blocks
can be accommodated directly by M3UA/SCTP, without the need for an can be accommodated directly by M3UA/SCTP, without the need for an
upper layer segmentation/re-assembly procedure as specified in recent upper layer segmentation/re-assembly procedure as specified in recent
skipping to change at page 8, line 23 skipping to change at page 8, line 19
the congested state of remote SS7 destinations. This information is the congested state of remote SS7 destinations. This information is
requested from the M3UA at the SG. requested from the M3UA at the SG.
The M3UA layer at an ASP may also indicate to the SG that the M3UA The M3UA layer at an ASP may also indicate to the SG that the M3UA
itself or the ASP or the ASP's host is congested. itself or the ASP or the ASP's host is congested.
1.3.2.4 Support for the management of SCTP associations between the SG 1.3.2.4 Support for the management of SCTP associations between the SG
and ASPs. and ASPs.
The M3UA layer at the SG maintains the availability state of all The M3UA layer at the SG maintains the availability state of all
configured remote ASPs, in order to manage the SCTP Associations and configured local and remote ASPs, in order to manage the SCTP
the Associations and the traffic between the M3UA peers. As well, the
traffic between the SG and ASPs. As well, the active/inactive state of active/inactive state of local and remote ASPs is also maintained.
remote ASPs is also maintained - Active ASPs are those currently
receiving traffic from the SG.
The M3UA layer may be instructed by local management to establish an The M3UA layer may be instructed by local management to establish an
SCTP association to a peer M3UA node. This can be achieved using the SCTP association to a peer M3UA node. This can be achieved using the
M-SCTP ESTABLISH primitive to request, indicate and confirm the M-SCTP ESTABLISH primitive to request, indicate and confirm the
establishment of an SCTP association with a peer M3UA node. In order establishment of an SCTP association with a peer M3UA node. In order
to avoid multiple SCTP associations between two IPSPs, one side must be to avoid redundant SCTP associations between two M3UA peers, one side
designated to establish the association or the mutual SCTP endpoint must be designated to establish the SCTP association or the mutual SCTP
addresses must be pre-configured. endpoint addresses must be pre-configured.
The M3UA layer may also need to inform local management of the status The M3UA layer may also need to inform local management of the status
of the underlying SCTP associations using the M-SCTP STATUS request and of the underlying SCTP associations using the M-SCTP STATUS request and
indication primitive. For example, the M3UA may inform local management indication primitive. For example, the M3UA may inform local management
of the reason for the release of an SCTP association, determined either of the reason for the release of an SCTP association, determined either
locally within the M3UA layer or by a primitive from the SCTP. locally within the M3UA layer or by a primitive from the SCTP.
Also the M3UA layer may need to inform the local management of the Also the M3UA layer may need to inform the local management of the
change in status of an ASP or AS. This can be achieved using the M-ASP change in status of an ASP or AS. This may be achieved using the M-ASP
STATUS or M-AS STATUS primitives. STATUS request or M-AS STATUS request primitives.
1.3.2.5 Support for the management of connections to multiple SGs 1.3.2.5 Support for the management of connections to multiple SGs
As shown in Figure 1 an ASP may be connected to multiple SGs. In such a As shown in Figure 1 an ASP may be connected to multiple SGs. In such a
case a particular SS7 destination may be reachable via more than SG, case a particular SS7 destination may be reachable via more than SG,
i.e., via more than one route. As MTP3 users only maintain status on a i.e., via more than one route. As MTP3 users only maintain status on a
destination and not on a route basis M3UA must maintain the status destination and not on a route basis M3UA must maintain the status
(availability and/or congestion of route to destination) of the (availability and/or congestion of route to destination) of the
individual routes, derive the overall status of the destination from individual routes, derive the overall status of the destination from
the status of the individual routes, and inform the MTP3 users of this the status of the individual routes, and inform the MTP3 users of this
derived status whenever it changes. 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 of
distributed architecture and redundant networks does allow for a distributed architecture and redundant networks does allow for a
sufficiently reliable transport of signalling traffic over IP. The sufficiently reliable transport of signalling traffic over IP. The
M3UA protocol is flexible enough to allow its operation and management M3UA 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 to
meet their performance and reliability requirements. meet their performance and reliability requirements.
To meet the stringent SS7 signalling reliability and performance To meet the stringent SS7 signalling reliability and performance
skipping to change at page 9, line 35 skipping to change at page 9, line 27
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 SGs, This can typically be achieved through the use of redundant SGs,
redundant hosts, and the provision of redundant QOS-bounded IP network redundant hosts, and the provision of redundant QOS-bounded IP network
paths for SCTP Associations between SCTP End Points. Obviously, the paths for SCTP Associations between SCTP End Points. Obviously, the
reliability of the SG, the MGC and other IP-based functional elements reliability of the SG, the MGC and other IP-based functional elements
also needs to be taken into account. The distribution of ASPs within also needs to be taken into account. The distribution of ASPs within
the available Hosts must also be considered. As an example, for a the available Hosts must also be considered. As an example, for a
particular Application Server, the related ASPs should be distributed particular Application Server, the related ASPs should be distributed
over at least two Hosts. over at least two Hosts.
Here is one example of a physical network architecture relevant to SS7 One example of a physical network architecture relevant to SS7 carrier-
carrier-grade operation, in the IP network domain, shown in Figure 1 grade operation in the IP network domain is shown in Figure 1 below:
below:
SG MGC SG MGC
Host#1 ************** ************** Host#1 Host#1 ************** ************** Host#1
= * ********__*__________________________*__******** * = = * ********__*__________________________*__******** * =
SG1 * * SGP1 *__*_____ _______________*__* ASP1 * * MGC1 SG1 * * SGP1 *__*_____ _______________*__* ASP1 * * MGC1
* ******** * \ / * ******** * * ******** * \ / * ******** *
* ********__*______\__/________________*__******** * * ********__*______\__/________________*__******** *
* * SGP2 *__*_______\/______ _____*__* ASP2 * * * * SGP2 *__*_______\/______ _____*__* ASP2 * *
* ******** * /\ | | * ******** * * ******** * /\ | | * ******** *
skipping to change at page 24, line 43 skipping to change at page 24, line 43
Purpose: LM requests ASP to establish an SCTP association with an SG Purpose: LM requests ASP to establish an SCTP association with an SG
or IPSP. or IPSP.
M-STCP ESTABLISH confirm M-STCP ESTABLISH confirm
Direction: M3UA -> LM Direction: M3UA -> LM
Purpose: ASP confirms to LM that it has established an SCTP Purpose: ASP confirms to LM that it has established an SCTP
association with an SG or IPSP. association with an SG or IPSP.
M-SCTP ESTABLISH indication M-SCTP ESTABLISH indication
Direction: M3UA -> LM Direction: M3UA -> LM
Purpose: SG or IPSP informs LM that an ASP has established an SCTP Purpose: M3UA informs LM that a remote ASP has established an SCTP
association. association.
M-SCTP RELEASE request M-SCTP RELEASE request
Direction: LM -> M3UA Direction: LM -> M3UA
Purpose: LM requests ASP to release an SCTP association with SG or Purpose: LM requests ASP to release an SCTP association with SG or
IPSP. IPSP.
M-SCTP RELEASE confirm M-SCTP RELEASE confirm
Direction: M3UA -> LM Direction: M3UA -> LM
Purpose: ASP confirms to LM that it has released SCTP association Purpose: ASP confirms to LM that it has released SCTP association
with SG. with SG.
M-SCTP RELEASE indication M-SCTP RELEASE indication
Direction: M3UA -> LM Direction: M3UA -> LM
Purpose: SG or IPSP informs LM that ASP has released an SCTP Purpose: M3UA informs LM that a remote ASP has released an SCTP
association. Association or the SCTP association has failed.
M-SCTP STATUS request M-SCTP STATUS request
Direction: LM -> M3UA Direction: LM -> M3UA
Purpose: LM requests M3UA to report status of SCTP association. Purpose: LM requests M3UA to report the status of an SCTP
association.
M-SCTP STATUS indication M-SCTP STATUS confirm
Direction: M3UA -> LM Direction: M3UA -> LM
Purpose: M3UA reports status of SCTP association. Purpose: M3UA reports the status of an SCTP association.
M-ASP STATUS request M-ASP STATUS request
Direction: LM -> M3UA Direction: LM -> M3UA
Purpose: LM requests SG or IPSP to report status of remote ASP. Purpose: LM requests M3UA to report the status of a local or remote
ASP.
M-ASP STATUS indication M-ASP STATUS confirm
Direction: M3UA -> LM Direction: M3UA -> LM
Purpose: SG or IPSP reports status of remote ASP. Purpose: M3UA reports status of local or remote ASP.
M-AS-STATUS request M-AS STATUS request
Direction: LM -> M3UA Direction: LM -> M3UA
Purpose: LM requests SG or IPSP to report status of AS. Purpose: LM requests M3UA to report the status of an AS.
M-AS-STATUS indication M-AS STATUS confirm
Direction: M3UA -> LM Direction: M3UA -> LM
Purpose: SG or IPSP reports status of AS. Purpose: M3UA reports the status of an AS.
M-NOTIFY indication M-NOTIFY indication
Direction: M3UA -> LM Direction: M3UA -> LM
Purpose: ASP reports that it has received a NOTIFY message Purpose: M3UA reports that it has received a NOTIFY message
from its peer. from its peer.
M-ERROR indication M-ERROR indication
Direction: M3UA -> LM Direction: M3UA -> LM
Purpose: ASP, SG or IPSP reports that it has received an ERROR Purpose: M3UA reports that it has received an ERROR message from
message from its peer. its peer or that a local operation has been unsuccessful.
M-ASP-DOWN request M-ASP UP request
Direction: LM -> M3UA
Purpose: LM requests ASP to start its operation and send an ASP-UP
Message to its peer.
M-ASP UP confirm
Direction: M3UA -> LM
Purpose: M3UA confirms requested ASP-UP change has been successfully
acknowledged by the M3UA peer.
M-ASP UP indication
Direction: M3UA -> LM
Purpose: M3UA reports it has successfully processed an incoming ASP-
UP request from its peer.
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 the SG. Message to its peer.
M-ASP-UP request M-ASP DOWN confirm
Direction: M3UA -> LM
Purpose: M3UA confirms requested ASP-DOWN change has been
successfully acknowledged by the M3UA peer.
M-ASP DOWN indication
Direction: M3UA -> LM
Purpose: M3UA reports it has successfully processed an incoming ASP-
DOWN request from its peer.
M-ASP-ACTIVE request
Direction: LM -> M3UA Direction: LM -> M3UA
Purpose: LM requests ASP to start its operation and send an ASP-UP Purpose: LM requests ASP to send an ASP-ACTIVE message to its peer
message to the SG. and to start data transfer.
M-ASP ACTIVE confirm
Direction: M3UA -> LM
Purpose: LM confirms requested ASP-ACTIVE change has been
successfully acknowledged by the M3UA peer.
M-ASP ACTIVE indication
Direction: M3UA -> LM
Purpose: LM reports it has successfully processed an incoming ASP-
ACTIVE request from its peer.
M-ASP-INACTIVE request M-ASP-INACTIVE request
Direction: LM -> M3UA Direction: LM -> M3UA
Purpose: LM requests ASP to stop data transfer and send an ASP- Purpose: LM requests ASP to stop data transfer and send an ASP-
Inactive message to the SG. Inactive message to the SG.
M-ASP-ACTIVE request M-ASP INACTIVE confirm
Direction: LM -> M3UA Direction: LM -> M3UA
Purpose: LM requests ASP to start data transfer and send an ASP- Purpose: LM confirms requested ASP-INACTIVE change has been
Active message to the SG. successfully acknowledged by the M3UA peer.
M-ASP INACTIVE indication
Direction: M3UA -> LM
Purpose: LM reports it has successfully processed an incoming ASP-
INACTIVE request from its peer.
M-AS ACTIVE indication
Direction: M3UA -> LM
Purpose: LM reports that an AS has moved to the ACTIVE state.
M-AS INACTIVE indication
Direction: M3UA -> LM
Purpose: LM reports that an AS has moved to the INACTIVE state.
M-AS DOWN indication
Direction: M3UA -> LM
Purpose: LM reports that an AS has moved to the DOWN state.
2.0 Conventions 2.0 Conventions
The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD
NOT, RECOMMENDED, NOT RECOMMENDED, MAY, and OPTIONAL, when they appear NOT, RECOMMENDED, NOT RECOMMENDED, MAY, and OPTIONAL, when they appear
in this document, are to be interpreted as described in [RFC2119]. in this document, are to be interpreted as described in [RFC2119].
3.0 M3UA Protocol Elements 3.0 M3UA Protocol Elements
The general M3UA message format includes a Common Message Header The general M3UA message format includes a Common Message Header
skipping to change at page 30, line 35 skipping to change at page 31, line 35
the signalling traffic between the SG and the Application Server the signalling traffic between the SG and the Application Server
Process over a common SCTP Association. An example is where an SG Process over a common SCTP Association. An example is where an SG
is logically partitioned to appear as an element in four different is logically partitioned to appear as an element in four different
national SS7 networks. national SS7 networks.
In a Data message, the Network Appearance implicitly defines the SS7 In a Data message, the Network Appearance implicitly defines the SS7
Point Code format used, the SS7 Network Indicator value, and the Point Code format used, the SS7 Network Indicator value, and the
MTP3/MTP3-User protocol type/variant/version used within the SS7 MTP3/MTP3-User protocol type/variant/version used within the SS7
network partition. Where an SG operates in the context of a single network partition. Where an SG operates in the context of a single
SS7 network, or individual SCTP associations are dedicated to each SS7 network, or individual SCTP associations are dedicated to each
SS7 network context, or the Network Indicator in the SIO of the MTP- SS7 network context, the Network Appearance parameter is not
Transfer primitive is sufficient, the Network Appearance parameter required.
is not required.
The Network Appearance parameter value is of local significance The Network Appearance parameter value is of local significance
only, coordinated between the SG and ASP. only, coordinated between the SG and ASP.
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.
Protocol Data: variable length Protocol Data: variable length
The Protocol Data field contains the SS7 MTP3-User application The Protocol Data field contains the SS7 MTP3-User application
message, including the complete Routing Label. The Protocol Data message, including the Service Information Octet and Routing Label.
parameter contains the following fields: The Protocol Data parameter contains the following fields:
Service Information Octet. Includes: Service Information Octet. Includes:
Service Indicator, Service Indicator,
Network Indicator, Network Indicator,
and Spare/Priority codes and Spare/Priority codes
MTP Routing Label. Includes: Routing Label. Includes:
Destination Point Code, Destination Point Code,
Originating Point Code, Originating Point Code,
And Signalling Link Selection Code (SLS) And Signalling Link Selection Code (SLS)
User Protocol Data. Includes MTP3-User protocol elements: User Protocol Data. Includes MTP3-User protocol elements:
ISUP, SCCP, or TUP parameters ISUP, SCCP, or TUP parameters
The format is as defined in the relevant MTP standards for the SS7 The format is as defined in the relevant MTP standards for the SS7
protocol being transported. The format is either implicitly known protocol being transported. The format is either implicitly known
or identified by the Network Appearance parameter. or identified by the Network Appearance parameter.
skipping to change at page 34, line 46 skipping to change at page 35, line 46
|MSB--------------------LSB| |MSB--------------------LSB|
It is optional to send an Affected Destinations parameter with more It is optional to send an Affected Destinations parameter with more
than one Affected DPC but it is mandatory to receive and process it. than one Affected DPC but it is mandatory to receive and process it.
All the Affected DPCs included must be within the same Network All the Affected DPCs included must be within the same Network
Appearance. Including multiple Affected DPCs may be useful when Appearance. Including multiple Affected DPCs may be useful when
reception of an MTP3 management message or a linkset event reception of an MTP3 management message or a linkset event
simultaneously affects the availability status of a list of simultaneously affects the availability status of a list of
destinations at an SG. destinations at an SG.
Mask: 8-bit unsigned integer Mask: 8-bits (unsigned integer)
The Mask field associated with each Affected DPC in the Affected The Mask field associated with each Affected DPC in the Affected
Destinations parameter, 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. For example, if all DPCs in an ANSI cluster
are determined to be unavailable due to local linkset are determined to be unavailable due to local linkset
unavailability, the DUNA could identify potentially 256 Affected unavailability, the DUNA could identify potentially 256 Affected
skipping to change at page 36, line 17 skipping to change at page 37, line 17
Network Appearance Optional Network Appearance Optional
Affected Destinations Mandatory Affected Destinations 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 SS7 Network Congestion (SCON)
The SCON message can be sent from the SG to all concerned ASPs to The SCON message can be sent from the SG to all concerned ASPs to
indicate the congestion level in the SS7 network to one or more indicate congestion in the SS7 network to one or more destinations, or
destinations or in response to a DAUD message, if appropriate. For to an ASP in response to a DATA or DAUD message as appropriate. For
some MTP protocol variants (e.g., ANSI MTP) the SCON may be sent when some MTP protocol variants (e.g., ANSI MTP) the SCON may be sent when
the SS7 congestion level changes. The SCON message is also sent from the SS7 congestion level changes. The SCON message MAY also be sent
the M3UA of an ASP to the SG or IPSP indicating that the M3UA or the from the M3UA of an ASP to an M3UA peer indicating that the M3UA or the
ASP is congested. 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 Affected Destinations Mandatory
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 = 1 | Length =8 | | Tag = 1 | Length =8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Network Appearance* | | Network Appearance* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 5 | Length | | Tag = 5 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Cong. Level 1 | Affected DPC 1 | | Mask | Affected DPC 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ ... / / ... /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Cong. Level n | Affected DPC n | | Mask | Affected DPC n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 14 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | Cong. Level* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 4 | Length | | Tag = 4 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ INFO String* / / INFO String* /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Affected Destinations parameter differs from the Affected The format and description of the Network Appearance, Affected
Destinations parameter in the DUNA, DAVA, and DAUD in that a Congestion Destinations, and Info String parameters is the same as for the DUNA
Level field is included instead of a Mask field. Therefore ranges of message (See Section 3.4.1.)
congested Affected DPCs cannot be signaled, but this is consistent with
operation in the SS7 network.
The format and description of the Network Appearance and Info String The Affected Destinations parameter can be used to indicate congestion
parameters is the same as for the DUNA message (See Section 3.3.2.1.) of multiple destinations or ranges of destinations. However, an SCON
MUST not be delayed in order to "collect" individual congested
destinations into a single SCON as any delay might affect 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 cluster route
set to the SS7 network that becomes congested due to outgoing link set
congestion.
Congested Indications: 32-bits
The optional Congestion Indications parameter contains a Congestion
Level field. This optional parameter is used to communicate
congestion levels in national MTP networks with multiple congestion
thresholds, such as in ANSI MTP3. For MTP congestion methods
without multiple congestion levels (e.g., the ITU international
method) the parameter is not included.
Congestion Level field: 8-bits (unsigned integer) Congestion Level field: 8-bits (unsigned integer)
The Congestion Level field, associated with each Affected DPC in the The Congestion Level field, associated with all of the Affected
Affected Destinations parameter, contains one of the following DPC(s) in the Affected Destinations parameter, contains one of the
values: Following values:
0 No Congestion or Undefined 0 No Congestion or Undefined
1 Congestion Level 1 1 Congestion Level 1
2 Congestion Level 2 2 Congestion Level 2
3 Congestion Level 3 3 Congestion Level 3
The congestion levels are as defined in the national congestion The congestion levels are defined in the congestion method in the
method in the appropriate MTP recommendation [14,15]. For MTP appropriate national MTP recommendations [14,15].
congestion methods that do not employ congestion levels (e.g., the
ITU international method, the parameter is always "Undefined".
When an SCON is received at the SG, a TFC message is generated into the
SS7 network.
Editors Note: May need a different message type (ASPCON) and specify
more detailed procedures at the SG or IPSP upon reception.
3.4.5 Destination User Part Unavailable (DUPU) 3.4.5 Destination User Part Unavailable (DUPU)
The DUPU message is used by an SG to inform an ASP that a remote peer The DUPU message is used by an SG to inform an ASP that a remote peer
MTP3-User Part (e.g., ISUP or SCCP) at an SS7 node is unavailable. 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 Affected Destinations Mandatory
skipping to change at page 38, line 16 skipping to change at page 39, line 42
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 = 1 | Length | | Tag = 1 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Network Appearance* | | Network Appearance* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 5 | Length = 8 | | Tag = 5 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | Affected DPC | | Mask = 0 | Affected DPC |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 9 | Length = 8 | | Tag = 9 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Cause | User | | Cause | User |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 4 | Length | | Tag = 4 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ INFO String* / / INFO String* /
\ \ \ \
skipping to change at page 39, line 5 skipping to change at page 40, line 32
0 Unknown 0 Unknown
1 Unequipped Remote User 1 Unequipped Remote User
2 Inaccessible Remote User 2 Inaccessible Remote User
MTP3-User Identity field: 16-bits (unsigned integer) MTP3-User Identity field: 16-bits (unsigned integer)
The MTP3-User Identity describes the specific MTP3-User that is The MTP3-User Identity describes the specific MTP3-User that is
unavailable (e.g., ISUP, SCCP, ...). Some of the valid values for unavailable (e.g., ISUP, SCCP, ...). Some of the valid values for
the MTP3-User Identity are shown below. The values agree with those the MTP3-User Identity are shown below. The values agree with those
provided in the SS7 MTP3 User Part Unavailable message and Service provided in the SS7 MTP3 User Part Unavailable message and Service
Indicator. Depending on the MTP3 protocol used in the network Indicator. Depending on the MTP3 protocol variant/version used in
appearance, additional values may be used - the specification of the the network appearance, additional values may be used. The relevant
relevant MTP3 protocol variant/version recommendation is definitive. MTP3 protocol variant/version recommendation is definitive.
0 to 2 Reserved 0 to 2 Reserved
3 SCCP 3 SCCP
4 TUP 4 TUP
5 ISUP 5 ISUP
6 to 8 Reserved 6 to 8 Reserved
9 Broadband ISUP 9 Broadband ISUP
10 Satellite ISUP 10 Satellite ISUP
The Affected Destinations parameter differs from the Affected The Affected Destinations parameter in a DUPU message differs from the
Destinations parameter in the DUNA, DAVA, and DAUD in that a Reserved Affected Destinations parameter in the DUNA, DAVA, and DAUD in that the
field is included instead of a Mask field. Therefore, ranges of Mask field is not used and only a single Affected DPC is attached.
congested Affected DPCs cannot be signaled, but this is consistent with Ranges and lists of Affected DPCs cannot be signaled, but this is
operation in the SS7 network. The Affected Destinations parameter in consistent with operation in the SS7 network. The Affected Destinations
the DUPU message can only contain one Affected DPC. parameter in an MTP3 User Part Unavailable message (UPU) received by an
SG from the SS7 network contains only one destination.
The format and description of the Network Appearance and Info String The format and description of the Network Appearance and Info String
parameters is the same as for the DUNA message (See Section 3.4.1.). parameters is the same as for the DUNA message (See Section 3.4.1.).
3.5 Application Server Process Maintenance (ASPM) Messages 3.5 Application Server Process Maintenance (ASPM) Messages
3.5.1 ASP Up (ASPUP) 3.5.1 ASP Up (ASPUP)
The ASP UP (ASPUP) message is used to indicate to a remote M3UA peer The ASP UP (ASPUP) message is used to indicate to a remote M3UA peer
that the Adaptation layer is ready to receive SSNM or ASPM management that the Adaptation layer is ready to receive SSNM or ASPM management
messages for all Routing Keys that the ASP is configured to serve. messages for all Routing Keys that the ASP is configured to serve.
The ASPUP message contains the following parameters: The ASPUP message contains the following parameters:
Adaptation Layer Identifier Optional
INFO String Optional INFO String Optional
The format for ASPUP Message parameters is as follows: The format for ASPUP Message parameters is as follows:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Adaptation Layer Identifier* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 4 | Length | | Tag = 4 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ INFO String* / / INFO String* /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format and description of the optional Info String parameter is the The format and description of the optional Info String parameter is the
same as for the DUNA message (See Section 3.3.2.1.) same as for the DUNA message (See Section 3.4.1.)
Adaptation Layer Identifier: 32-bits
The optional Adaptation Layer Identifier (ALI) is a string that
identifies the adaptation layer. This string must be set to "M3UA"
which results in a length of 8. The ALI would normally only be used in
the initial ASP Up message across a new SCTP association to ensure both
peers are assuming the same adaptation layer protocol.
Editors Note: Info in SCTP (Payload Identifier) could be used - is
there any need for ALI anymore?
3.5.2 ASP Up Ack 3.5.2 ASP Up Ack
The ASP UP Ack message is used to acknowledge an ASP-Up message The ASP UP Ack message is used to acknowledge an ASP-Up message
received from a remote M3UA peer. received from a remote M3UA peer.
The ASPUP Ack message contains the following parameters: The ASPUP Ack message contains the following parameters:
Adaptation Layer Identifier (optional)
INFO String (optional) INFO String (optional)
The format for ASPUP Ack Message parameters is as follows: The format for ASPUP Ack Message parameters is as follows:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag =2 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ Adaptation Layer Identifier* /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag =4 | Length | | Tag =4 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ INFO String* / / INFO String* /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format and description of the optional Info String parameter is the The format and description of the optional Info String parameter is the
same as for the DUNA message (See Section 3.3.2.1.) same as for the DUNA message (See Section 3.4.1.)
The format and description of the optional Adaptation Layer Identifier
(ALI) parameter is the same as for the ASP-UP message. (See Section
3.4.1)
3.5.3 ASP Down (ASPDN) 3.5.3 ASP Down (ASPDN)
The ASP Down (ASPDN) message is used to indicate to a remote M3UA peer The ASP Down (ASPDN) message is used to indicate to a remote M3UA peer
that the adaptation layer is not ready to receive traffic or that the adaptation layer is not ready to receive traffic or management
maintenance messages. messages.
The ASPDN message contains the following parameters: The ASPDN message contains the following parameters:
Reason Mandatory Reason Mandatory
INFO String Optional INFO String Optional
The format for the ASPDN message parameters is as follows: The format for the ASPDN message parameters is as follows:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 10 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reason | | Reason |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag =4 | Length | | Tag =4 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ INFO String* / / INFO String* /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format and description of the optional Info String parameter is the The format and description of the optional Info String parameter is the
same as for the DUNA message (See Section 3.3.2.1.) same as for the DUNA message (See Section 3.4.1.)
Reason: 32-bit (unsigned integer) Reason: 32-bit (unsigned integer)
The Reason parameter indicates the reason that the remote M3UA The Reason parameter indicates the reason that the remote M3UA
adaptation layer is unavailable. The valid values for Reason are adaptation layer is unavailable. The valid values for Reason are
shown in the following table. shown in the following table.
0 Unspecified 0 Unspecified
1 User Unavailable 1 User Unavailable
2 Management Blocking 2 Management Blocking
skipping to change at page 42, line 10 skipping to change at page 43, line 15
The ASP Down Ack message contains the following parameters: The ASP Down Ack message contains the following parameters:
Reason Mandatory Reason Mandatory
INFO String Optional INFO String Optional
The format for the ASPDN Ack message parameters is as follows: The format for the ASPDN Ack message parameters is as follows:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 10 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reason | | Reason |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 4 | Length | | Tag = 4 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ INFO String* / / INFO String* /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format and description of the optional Info String parameter is the The format and description of the optional Info String parameter is the
same as for the DUNA message (See Section 3.3.2.1.) same as for the DUNA message (See Section 3.4.1.)
The format of the Reason parameter is the same as for the ASP-Down The format of the Reason parameter is the same as for the ASP-Down
message. (See Section 3.4.3) message. (See Section 3.4.3)
3.5.5 ASP Active (ASPAC) 3.5.5 ASP Active (ASPAC)
The ASPAC message is sent by an ASP to indicate to a remote M3UA peer The ASPAC message is sent by an ASP to indicate to a remote M3UA peer
that it is Active and ready to process signalling traffic for a that it is Active and ready to process signalling traffic for a
particular Application Server. The ASPAC affects only the ASP state particular Application Server. The ASPAC 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 ASPAC message contains the following parameters: The ASPAC message contains the following parameters:
Type Mandatory Traffic Mode Type Mandatory
Routing Context Optional Routing Context Optional
INFO String Optional INFO String Optional
The format for the ASPAC message is as follows: The format for the ASPAC 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | | Tag = 11 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Traffic Mode Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag =6 | Length | | Tag =6 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ Routing Context* / / Routing Context* /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 4 | Length | | Tag = 4 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ INFO String* / / INFO String* /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 32-bit (unsigned integer) Traffic Mode Type: 32-bit (unsigned integer)
The Type parameter identifies the traffic mode of operation of the The Traffic Mode Type parameter identifies the traffic mode of
ASP within an AS. The valid values for Type are shown in the operation of the ASP within an AS. The valid values for Type are
following table. shown in the following table.
1 Over-ride 1 Over-ride
2 Load-share 2 Load-share
3 Over-ride (Standby) 3 Over-ride (Standby)
4 Loadshare (Standby) 4 Load-share (Standby)
Within a particular Routing Context, Over-ride and Loadshare Types Within a particular Routing Context, Over-ride and Load-share Types
cannot be mixed. The Over-ride value indicates that the ASP is cannot be mixed. The Over-ride value indicates that the ASP is
operating in Over-ride mode, and the ASP wishes to take over all operating in Over-ride mode, and the ASP wishes to take over all
traffic in an Application Server (i.e., primary/back-up operation), traffic in an Application Server (i.e., primary/back-up operation),
over-riding any currently active ASP in the AS. In Load-share mode, over-riding any currently active ASP in the AS. In Load-share mode,
the ASP wishes to share in the traffic distribution with any other the ASP wishes to share in the traffic distribution with any other
currently active ASPs. The Standby versions of the Over-ride and currently active ASPs. The Standby versions of the Over-ride and
Loadshare Types indicate that the ASP is declaring itself ready to Load-share Types indicate that the ASP is declaring itself ready to
accept traffic but leaves it up to the sender as to when the traffic accept traffic but leaves it up to the sender as to when the traffic
is started. Over-ride (Standby) indicates that the traffic sender is started. Over-ride (Standby) indicates that the traffic sender
continues to use the currently active ASP until it can no longer continues to use the currently active ASP until it can no longer
send/receive traffic (i.e., the currently active ASP transitions to send/receive traffic (i.e., the currently active ASP transitions to
Down or Inactive). At this point the sender may immediately move Down or Inactive). At this point the sender may immediately move
the ASP to Active and commence traffic. Loadshare (Standby) is the ASP to Active and commence traffic. Load-share (Standby) is
similar - the sender continues to loadshare to the current ASPs similar - the sender continues to load-share to the current ASPs
until there it is determined that there is insufficient resources in until there it is determined that there is insufficient resources in
the Loadshare group. When there is insufficient ASPs, the sender the Load-share group. When there is insufficient ASPs, the sender
may immediately move the ASP to Active. may immediately move the ASP to Active.
Routing Context: Routing Context:
The optional Routing Context parameter contains (a list of) 4-byte The optional Routing Context parameter contains (a list of) 4-byte
unsigned integers indexing the Application Server traffic that the unsigned integers indexing the Application Server traffic that the
sending ASP is configured/registered to receive. sending ASP is configured/registered to receive.
There is one-to-one relationship between an index entry and an SG There is one-to-one relationship between an index entry and an SG
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
skipping to change at page 44, line 6 skipping to change at page 45, line 27
An Application Server Process may be configured to process traffic An Application Server Process may be configured to process traffic
for more than one logical Application Server. From the perspective for more than one logical Application Server. From the perspective
of an ASP, a Routing Context defines a range of signalling traffic of an ASP, a Routing Context defines a range of signalling traffic
that the ASP is currently configured to receive from the SG. For that the ASP is currently configured to receive from the SG. For
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.3.2.1.) same as for the DUNA message (See Section 3.4.1.)
3.5.6 ASP Active Ack 3.5.6 ASP Active Ack
The ASPAC Ack message is used to acknowledge an ASP-Active message The ASPAC Ack message is used to acknowledge an ASP-Active message
received from a remote M3UA peer. received from a remote M3UA peer.
The ASPAC Ack message contains the following parameters: The ASPAC Ack message contains the following parameters:
Type Mandatory Traffic Mode Type Mandatory
Routing Context Optional Routing Context Optional
INFO String Optional INFO String Optional
The format for the ASPAC Ack message is as follows: The format for the ASPAC 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | | Tag = 11 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Traffic Mode Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 6 | Length | | Tag = 6 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ Routing Context* / / Routing Context* /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 4 | Length | | Tag = 4 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ INFO String* / / INFO String* /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format and description of the optional Info String parameter is the The format and description of the optional Info String parameter is the
same as for the DUNA message (See Section 3.3.2.1.) same as for the DUNA message (See Section 3.3.2.1.)
The format of the Type and Routing Context parameters is the same as The format of the Traffic Mode Type and Routing Context parameters is
for the ASP-Active message. (See Section 3.4.5). the same as for the ASP-Active message. (See Section 3.4.5).
3.5.7 ASP Inactive (ASPIA) 3.5.7 ASP Inactive (ASPIA)
The ASPIA message is sent by an ASP to indicate to a remote M3UA peer The ASPIA message is sent by an ASP to indicate to a remote M3UA peer
that it is no longer processing signalling traffic within a particular that it is no longer processing signalling traffic within a particular
Application Server. The ASPIA affects only the ASP state in the Application Server. The ASPIA affects only the ASP state in the
Routing Keys identified by the Routing Contexts, if present. Routing Keys identified by the Routing Contexts, if present.
The ASPIA message contains the following parameters: The ASPIA message contains the following parameters:
Type Mandatory Traffic Mode Type Mandatory
Routing Context Optional Routing Context Optional
INFO String Optional INFO String Optional
The format for the ASPIA message parameters is as follows: The format for the ASPIA 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | | Tag = 11 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Traffic Mode Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 6 | Length | | Tag = 6 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ Routing Context* / / Routing Context* /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 4 | Length | | Tag = 4 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ INFO String* / / INFO String* /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 32-bit (unsigned integer) Traffic Mode Type: 32-bit (unsigned integer)
The Type parameter identifies the traffic mode of operation of the The Traffic Mode Type parameter identifies the traffic mode of
ASP within an AS. The valid values for Type are shown in the operation of the ASP within an AS. The valid values for Type are
following table. shown in the following table.
1 Over-ride 1 Over-ride
2 Load-share 2 Load-share
Within a particular Routing Context, only one Type can be used. The Within a particular Routing Context, only one Type can be used. The
Over-ride value indicates that the ASP is operating in Over-ride Over-ride value indicates that the ASP is operating in Over-ride
mode, and will no longer handle traffic within an Application Server mode, and will no longer handle traffic within an Application Server
(i.e., it is now a backup in a primary/back-up arrangement). The (i.e., it is now a backup in a primary/back-up arrangement). The
Load-share value indicates that the ASP is operating in Load-share Load-share value indicates that the ASP is operating in Load-share
mode and will no longer share in the traffic distribution with any mode and will no longer share in the traffic distribution with any
other currently active ASPs. other currently active ASPs.
A node that receives an ASPIA with an incorrect Type for a A node that receives an ASPIA with an incorrect Type for a
particular routing Context will respond with an Error Message particular routing Context will respond with an Error Message
(Cause: Invalid Traffic Handling Mode. (Cause: Invalid Traffic Handling Mode).
The format and description of the optional Routing Context and Info The format and description of the optional Routing Context and Info
String parameters is the same as for the ASPAC message (See Section String parameters is the same as for the ASPAC message (See Section
2.3.3.3.) 3.5.5.)
3.5.8 ASP Inactive Ack 3.5.8 ASP Inactive Ack
The ASPIA Ack message is used to acknowledge an ASP-Inactive message The ASPIA Ack message is used to acknowledge an ASP-Inactive message
received from a remote M3UA peer. received from a remote M3UA peer.
The ASPIA Ack message contains the following parameters: The ASPIA Ack message contains the following parameters:
Type Mandatory Traffic Mode Type Mandatory
Routing Context Optional Routing Context Optional
INFO String Optional INFO String Optional
The format for the ASPIA Ack message is as follows: The format for the ASPIA Ack message is as follows:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | | Tag = 11 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Traffic Mode Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 6 | Length | | Tag = 6 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ Routing Context* / / Routing Context* /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 4 | Length | | Tag = 4 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ INFO String* / / INFO String* /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format and description of the optional Info String parameter is the The format and description of the optional Info String parameter is the
same as for the DUNA message (See Section 3.3.2.1.) same as for the DUNA message (See Section 3.4.1.)
The format of the Type and Routing Context parameters is the same as The format of the Traffic Mode Type and Routing Context parameters is
for the ASP-Inactive message. (See Section 3.4.7). the same as for the ASP-Inactive message. (See Section 3.5.7).
3.5.9 Heartbeat (BEAT) 3.5.9 Heartbeat (BEAT)
The Heartbeat message is optionally used to ensure that the M3UA peers The Heartbeat 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:
skipping to change at page 47, line 48 skipping to change at page 50, line 10
The ERR message contains the following parameters: The ERR message contains the following parameters:
Error Code Mandatory Error Code Mandatory
Diagnostic Information Optional Diagnostic Information Optional
The format for the ERR message is as follows: The format for the ERR message is as follows:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 12 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Error Code | | Error Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 7 | Length | | Tag = 7 | 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 1 Invalid Version
2 Invalid Network Appearance 2 Invalid Network Appearance
3 Invalid Adaptation Layer Identifier 3 Unsupported Message Type
4 Invalid Message Type 4 Invalid Message Type
5 Invalid Traffic Handling Mode 5 Invalid Traffic Handling Mode
6 Unexpected Message Type 6 Unexpected Message
7 Protocol Error 7 Protocol Error
8 Invalid Routing Context 8 Invalid Routing Context
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, Adaptation Layer Identifier, Traffic Handling Network Appearance, Traffic Handling Mode or Routing Context, the
Mode or Invalid Routing Context, the Diagnostic information includes Diagnostic information includes the received parameter. In the
the received parameter. In the other cases, the Diagnostic other cases, the Diagnostic information may be the first 40 bytes of
information may be the first 40 bytes of the offending message. the offending message.
In the case of an Invalid Version Error Code, the Common Header In the case of an Invalid Version Error Code, the Common Header
contains the supported Version. contains the supported Version.
Error messages are not generated in response to other Error messages. Error messages are not generated in response to other Error messages.
3.6.2 Notify (NTFY) 3.6.2 Notify (NTFY)
The Notify message used to provide an autonomous indication of M3UA The Notify message used to provide an autonomous indication of M3UA
events to an M3UA peer. events to an M3UA peer.
The NTFY message contains the following parameters: The NTFY message contains the following parameters:
Status Type Mandatory Status Type/ID Mandatory
Status Identification Mandatory
Routing Context Optional Routing Context Optional
INFO String Optional INFO String Optional
The format for the NTFY message is as follows: The format for the NTFY 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 = 13 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Status Type | Status Identification | | Status Type | Status Identification |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 6 | Length | | Tag = 6 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \ \ \
/ Routing Context* / / Routing Context* /
\ \ \ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 4 | Length | | Tag = 4 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 51, line 16 skipping to change at page 53, line 16
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 the SCTP and M3UA-User layers and Layer Management as well as the from the SCTP and M3UA-User layers and Layer Management as well as the
messages that it receives from the peer M3UA layers. This section messages that it receives from the peer M3UA layers. This section
describes the M3UA procedures in response to these events. describes the M3UA procedures in response to these events.
4.1 Procedures to support the services of the M3UA layer 4.1 Procedures to support the services of the M3UA layer
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 primitive from an upper layer, or the On receiving an MTP-Transfer request primitive from an upper layer, or
nodal inter-working function at an SG, the M3UA layer will send a the nodal inter-working function at an SG, the M3UA layer sends a
corresponding DATA message (see Section 3) to its M3UA peer. The M3UA corresponding DATA message (see Section 3) to its M3UA peer. The M3UA
layer must fill in the fields of the common and specific headers peer receiving the Data message sends an MTP-Transfer indication
correctly. primitive to the upper layer.
At an SG, the M3UA address translation and mapping function determines The M3UA address translation and mapping function determines the
the Application Server (AS) based on the information in the incoming Application Server (AS) based on the information in the incoming
message. From the list of ASPs within the AS table, an Active ASP is message. From the list of ASPs within the AS table, an Active ASP is
selected and a DATA message is constructed and issued on the selected and a DATA message is constructed and issued on the
corresponding SCTP Association. If more than one ASP is active (i.e., corresponding SCTP Association. If more than one ASP is active (i.e.,
traffic is to be load-shared across all the active ASPs), one of the traffic is to be load-shared across all the active ASPs), one of the
active ASPs from the list is selected. The selection algorithm is active ASPs from the list is selected. The selection algorithm is
implementation dependent but could, for example, be round-robin or implementation dependent but could, for example, be round-robin or
based on, for example, the SLS or ISUP CIC. The appropriate selection based on, for example, the SLS or ISUP CIC. The appropriate selection
algorithm must be chosen carefully as it is dependent on application algorithm must be chosen carefully as it is dependent on application
assumptions and understanding of the degree of state coordination assumptions and understanding of the degree of state coordination
between the active ASPs in the AS. between the 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.
4.1.2 Receipt of primitives from the Layer Management 4.1.2 Receipt of primitives from the Layer Management
On receiving these primitives from the local Layer Management, the M3UA On receiving primitives from the local Layer Management, the M3UA
layer will provide the appropriate response primitive across the layer will take the requested action and provide a response to Layer
internal local Layer Management interface. Management.
An M-SCTP ESTABLISH request from Layer Management will initiate the An M-SCTP ESTABLISH request from Layer Management will initiate the
establishment of an SCTP association. An M-SCTP ESTABLISH confirm will establishment of an SCTP association. An M-SCTP ESTABLISH confirm will
be sent to Layer Management when the initiated association set-up is be sent to Layer Management when the initiated association set-up is
complete. An M-SCTP ESTABLISH indication is sent to Layer Management complete. An M-SCTP ESTABLISH indication is sent to Layer Management
upon successful completion of an incoming SCTP association set-up from upon successful completion of an incoming SCTP association set-up from
a peer M3UA node a peer M3UA node
An M-SCTP RELEASE request from Layer Management will initate the tear- An M-SCTP RELEASE request from Layer Management initates the tear-
down of an SCTP association. An M-SCTP RELEASE confirm will be sent by down of an SCTP association. An M-SCTP RELEASE confirm is sent to
Layer Management when the association teardown is complete. An M-SCTP Layer Management when the association teardown is complete. An M-SCTP
RELEASE indication is sent to Layer Management upon successful tear- RELEASE indication is sent to Layer Management upon successful tear-
down of an SCTP association initiated by a peer M3UA down of an SCTP association initiated by a peer M3UA
M-SCTP STATUS request and indication support a Layer Management query An M-SCTP STATUS request supports a Layer Management query of the local
of the local status of a particular SCTP association. status of a particular SCTP association. The M3UA responds with the
association status in an M-SCTP STATUS confirm. No peer protocol is
invoked.
M-NOTIFY indication and M-ERROR indication indicate to Layer Management An M-ASP STATUS request supports a Layer Management query of the status
the notification or error information contained in a received M3UA of a particular local or remote ASP. The M3UA responds with the status
Notify or Error message. These indications can also be generated based in an M-ASP STATUS confirm. No M3UA peer protocol is invoked.
on local M3UA events.
M-ASP STATUS request/indication and M-AS-STATUS request/indication An M-AS STATUS request supports a Layer Management query of the status
support a Layer Management query of the local status of a particular of a particular AS. The M3UA responds with an M-AS STATUS confirm. No
ASP or AS. No M3UA peer protocol is invoked. M3UA peer protocol is invoked.
M-ASP-UP request, M-ASP-DOWN request, M-ASP-INACTIVE request and M-ASP- M-ASP-UP request, M-ASP-DOWN request, M-ASP-ACTIVE request and M-ASP-
ACTIVE request allow Layer Management at an ASP to initiate state INACTIVE request primitives allow Layer Management at an ASP to
changes . These requests result in outgoing M3UA ASP-UP, ASP-DOWN, initiate state changes. Upon successful completion, a corresponding
ASP-INACTIVE and ASP-ACTIVE messages. confirm is provided by the M3UA to Layer Management. If the invocation
is unsuccessful, an Error indication is provided.
These requests result in outgoing M3UA ASP-UP, ASP-DOWN, ASP-ACTIVE and
ASP-INACTIVE messages to the remote M3UA peer at an SG or IPSP.
4.2 Receipt of M3UA Peer Management messages 4.2 Receipt of M3UA Peer Management messages
Upon receipt of M3UA Management messages, the M3UA layer must invoke Upon successful state changes resulting from reception of M3UA ASP-UP,
the corresponding Layer Management primitive indications (e.g., M-AS ASP-DOWN, ASP-ACTIVE and ASP-INACTIVE messages from a peer M3UA, the
Status ind., M-ASP Status ind., M-ERROR ind., ...) to the local layer M3UA layer invoke corresponding M-ASP UP, M-ASP DOWN, M-ASP ACTIVE and
management. M-ASP INACTIVE, M-AS ACTIVE, M-AS INACTIVE, and M-AS DOWN indications
as appropriate to the Layer Management.
M-NOTIFY indication and M-ERROR indication indicate to Layer Management M-NOTIFY indication and M-ERROR indication indicate to Layer Management
the notification or error information contained in a received M3UA the notification or error information contained in a received M3UA
Notify or Error message. These indications can also be generated based Notify or Error message. These indications can also be generated based
on local M3UA events. on local M3UA events.
4.3 Procedures to support the M3UA Management services 4.3 Procedures to support the M3UA Management services
These procedures support the M3UA management of SCTP Associations These procedures support the M3UA management of SCTP Associations
between SGs and ASPs. between SGs and ASPs.
skipping to change at page 56, line 12 skipping to change at page 58, line 12
Tr = Recovery Timer Tr = Recovery Timer
4.3.2 M3UA Management procedures for primitives 4.3.2 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 SG and ASP is assumed to be "Down". the SG and ASP is assumed to be "Down".
As the ASP is responsible for initiating the setup of an SCTP As the ASP is responsible for initiating the setup of an SCTP
association to an SG, the M3UA layer at an ASP receives an M-SCTP association to an SG, the M3UA layer at an ASP receives an M-SCTP
ESTABLISH request primitive from the Layer Management, the M3UA layer ESTABLISH request primitive from the Layer Management. the M3UA layer
will try to establish an SCTP association with the remote M3UA peer at will try to establish an SCTP association with the remote M3UA peer at
an SG. Upon reception of an eventual SCTP-Communication Up confirm an SG. Upon reception of an eventual SCTP-Communication Up confirm
primitive from the SCTP, the M3UA layer will invoke the primitive M- primitive from the SCTP, the M3UA layer will invoke the primitive M-
SCTP ESTABLISH confirm to the Layer Management. SCTP ESTABLISH confirm to the Layer Management.
The M3UA layers at the SG will receive an SCTP-CommunicationUp The M3UA layers at the SG will receive an SCTP-CommunicationUp
indication primitive from the SCTP when the association is successfully indication primitive from the SCTP when the association is successfully
set up. The M3UA layer will then invoke the primitive M-SCTP ESTABLISH set up. The M3UA layer will then invoke the primitive M-SCTP ESTABLISH
indication to the Layer Management. indication to the Layer Management.
skipping to change at page 56, line 52 skipping to change at page 58, line 52
4.3.3 M3UA Management procedures for peer-to-peer messages 4.3.3 M3UA Management procedures for peer-to-peer messages
All M3UA MGMT and ASP Maintenance messages are sent on a sequenced All M3UA MGMT and ASP Maintenance messages are sent on a sequenced
stream to ensure ordering. SCTP stream '0' is used. stream to ensure ordering. SCTP stream '0' is used.
4.3.3.1 ASP-Up 4.3.3.1 ASP-Up
After an ASP has successfully established an SCTP association to an SG After an ASP has successfully established an SCTP association to an SG
or IPSP, the SG or IPSP waits for the ASP to send an ASP-Up message, or IPSP, the SG or IPSP waits for the ASP to send an ASP-Up message,
indicating that the ASP M3UA peer is available. The ASP is always the indicating that the ASP M3UA peer is available. The ASP is always the
initiator of the ASP-Up exchange. initiator of the ASP-Up exchange. This action MAY be initiated at the
ASP by an M-ASP UP request primitive from Layer Management or may be
initiated automatically by an M3UA management function.
When an ASP-Up message is received at an SG or IPSP and internally the When an ASP-Up message is received at an SG or IPSP and internally the
remote ASP is not considered locked-out for local management reasons, remote ASP is not considered locked-out for local management reasons,
the SG marks the remote ASP as 'Inactive'. If the SG knows via the SG marks the remote ASP as 'Inactive' and informs Layer Management
with an M-ASP-Up indication primitive. If the SG knows via
configuration data which Application Servers that the ASP is configured configuration data which Application Servers that the ASP is configured
to operate in, it can update the ASP status to "Inactive" in each AS to operate in, it can update the ASP status to "Inactive" in each AS
pool that it is a member. Alternatively, the SG may move the ASP into pool that it is a member. Alternatively, the SG may move the ASP into
a pool of Inactive ASPs available for future activation in AS pool(s) a pool of Inactive ASPs available for future activation in AS pool(s)
denoted in the subsequent ASP-Active Routing Contexts. The SG responds denoted in the subsequent ASP-Active Routing Contexts. The SG responds
with an ASP-Up Ack message in acknowledgement. The SG sends an ASP-Up with an ASP-Up Ack message in acknowledgement. The SG sends an ASP-Up
Ack message in response to a received ASP-Up message even if the ASP is Ack message in response to a received ASP-Up message even if the ASP is
already marked as "Inactive" at the SG. already marked as "Inactive" at the SG.
If for any local reason (e.g., management lock-out) the SG cannot If for any local reason (e.g., management lock-out) the SG cannot
respond with an ASP-Up Ack, the SG responds to an ASP-Up with an ASP- respond with an ASP-Up Ack, the SG responds to an ASP-Up with an ASP-
Down Ack message with Reason "Management Blocking". Down Ack message with Reason "Management Blocking".
At the ASP, the ASP-Up Ack message received is not acknowledged. If At the ASP, the ASP-Up Ack message received is not acknowledged. Layer
the ASP does not receive a response , or an ASP-Down Ack is received, Management is informed with an M-ASP UP confirm primitive .
the ASP may resend ASP-Up messages every 2 seconds until it receives an
ASP-Up Ack message. The ASP may decide to reduce the frequency (say to When the Asp sends an ASP-Up it starts timer T(ack). If the ASP does
every 5 seconds) if an ASP-Up Ack is not received after a few tries. not receive a response to an ASP-Up within T(ack), the ASP MAY restart
T(ack) and resend ASP-Up messages until it receives an ASP-Up Ack
message. T(ack) is provisionable, with a default of 2 seconds.
Alternatively, retransmission of ASP-Up messages may be put under
control of Layer Management. In this method, expiry of T(ack) results
in a M-ASP-Up confirmation carrying a negative indication.
The ASP must wait for the ASP-Up Ack message before sending any ASP The ASP must wait for the ASP-Up Ack message before sending any ASP
traffic control messages (i.e., ASPAC). If the SG or IPSP receives any messages (e.g., ASPAC). If the remote peer receives any other M3UA
other M3UA messages before an ASP Up is received, the SG or IPSP should messages before an ASP Up is received, the remote peer should
discard them. discard them.
4.3.3.2 ASP-Down 4.3.3.2 ASP-Down
The ASP will send an ASP-Down to an SG or IPSP when the ASP wishes to The ASP will send an ASP-Down to an SG or IPSP when the ASP wishes to
be removed from service in all Application Servers that it is a member be removed from service in all Application Servers that it is a member
And no longer receive any M3UA traffic or management messages. And no longer receive any M3UA traffic or management messages. This
action MAY be initiated at the ASP by an M-ASP DOWN request primitive
from Layer Management or may be initiated automatically by an M3UA
management function.
Whether the ASP is permanently removed from any AS is a function of Whether the ASP is permanently removed from any AS is a function of
configuration management. configuration management.
The SG marks the ASP as "Down" and returns an ASP-Down Ack message to The SG marks the ASP as "Down", informs Layer Management with an M-ASP-
the ASP if one of the following events occur: Up indication primitive, and returns an ASP-Down Ack message to the ASP
if one of the following events occur:
- an ASP-Down message is received from the ASP, - an ASP-Down message is received from the ASP,
- another ASPM message is received from the ASP and the SG has - another ASPM message is received from the ASP and the SG has
locked out the ASP for management reasons. locked out the ASP for management reasons.
The SG sends an ASP-Down Ack message in response to a received ASP-Down The SG sends an ASP-Down Ack message in response to a received ASP-Down
message from the ASP even if the ASP is already marked as "Down" at the message from the ASP even if the ASP is already marked as "Down" at the
SG. SG.
If the ASP does not receive a response from the SG, the ASP may send At the ASP, the ASP-Down Ack message received is not acknowledged.
ASP-Down messages every 2 seconds until it receives an ASP-Down Ack Layer Management is informed with an M-ASP Down confirm primitive.
message from the SG or the SCTP association goes down. The ASP may
decide to reduce the frequency (say to every 5 seconds) if an ASP-Down When the Asp sends an ASP-Down it starts timer T(ack). If the ASP does
Ack is not received after a few tries. not receive a response to an ASP-Down within T(ack), the ASP MAY
restart T(ack) and resend ASP-Down messages until it receives an
ASP-Down Ack message. T(ack) is provisionable, with a default of 2
seconds. Alternatively, retransmission of ASP-Down messages may be put
under control of Layer Management. In this method, expiry of T(ack)
results in a M-ASP-Down confirmation carrying a negative indication.
4.3.3.3 M3UA Version Control 4.3.3.3 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 SG. would normally come from the SG.
4.3.3.4 ASP-Active 4.3.3.4 ASP-Active
Anytime after the ASP has received an ASP-Up Ack from the SG or IPSP, Anytime after the ASP has received an ASP-Up Ack from the SG or IPSP,
the ASP sends an ASP-Active (ASPAC) to the SG indicating that the ASP the ASP sends an ASP-Active (ASPAC) to the SG indicating that the ASP
is ready to start processing traffic. In the case where an ASP wishes is ready to start processing traffic. This action MAY be initiated at
to process the traffic for more than one Application Server across a the ASP by an M-ASP Active request primitive from Layer Management or
common SCTP association, the ASPAC contains a list of one or more may be initiated automatically by an M3UA management function. In the
Routing Contexts to indicate for which Application Servers the ASPAC case where an ASP wishes to process the traffic for more than one
applies. In the case where an ASP-Active message does not contain a Application Server across a common SCTP association, the ASPAC contains
Routing Context, the receiver must know, via configuration data, which a list of one or more Routing Contexts to indicate for which
AS pools the ASP will be a member. Application Servers the ASPAC applies. In the case where an ASP-Active
message does not contain a Routing Context, the receiver must know, via
configuration data, which AS pools the ASP will be a member.
When an ASP Active (ASPAC) message is received, the SG or IPSP responds When an ASP Active (ASPAC) message is received, the SG or IPSP responds
to the ASP with an ASPAC Ack message, acknowledging that the ASPAC was to the ASP with an ASPAC Ack message, acknowledging that the ASPAC was
received and, depending on the ASPAC Type value received, moves the ASP received and, depending on the ASPAC Type value received, moves the ASP
to the "Active" or "Standby" state within the associated Application to the "Active" or "Standby" state within the associated Application
Server(s). The ASP MUST not send Data messages before receiving an Server(s). Layer Management is informed with an ASP-Active indication
primitive. The ASP MUST not send Data messages before receiving an
ASPAC Ack. If the SG or IPSP receives any Data messages before an ASPAC Ack. If the SG or IPSP receives any Data messages before an
ASPAC is received, the SG or IPSP should discard them. ASPAC is received, the SG or IPSP should discard them.
The SG sends an ASP-Active Ack message in response to a received ASP-
Active message from the ASP even if the ASP is already marked as
"Active" at the SG.
At the ASP, the ASP-Active Ack message received is not acknowledged.
Layer Management is informed with an M-ASP Active confirm primitive.
When the ASP sends an ASP-Active it starts timer T(ack). If
the ASP does not receive a response to an ASP-Active within 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
default of 2 seconds. Alternatively, retransmission of ASP-Active
messages may be put under control of Layer Management. In this method,
expiry of T(ack) results in a M-ASP-Active confirmation carrying a
negative indication.
There are two modes of Application Server traffic handling in the SG There are two modes of Application Server traffic handling in the SG
M3UA - Over-ride and Load-share. The Type parameter in the ASPAC M3UA - Over-ride and Load-share. The Type parameter in the ASPAC
message indicates the traffic handling mode used in a particular message indicates the traffic handling mode used in a particular
Application Server. If the SG determines that the mode indicated in an Application Server. If the SG determines that the mode indicated in an
ASPAC is incompatible with the mode currently used in the AS, the SG ASPAC is incompatible with the mode currently used in the AS, the SG
responds with an Error message indicating "Invalid Traffic Handling responds with an Error message indicating "Invalid Traffic Handling
Mode". Mode".
In the case of an Over-ride mode AS, reception of an ASPAC message at In the case of an Over-ride mode AS, reception of an ASPAC message at
an SG causes the redirection of all traffic for the AS to the ASP that an SG causes the redirection of all traffic for the AS to the ASP that
skipping to change at page 59, line 16 skipping to change at page 62, line 5
not sent in this case. not sent in this case.
In the case of a Load-share mode AS, reception of an ASPAC message at In the case of a Load-share mode AS, reception of an ASPAC message at
an SG or IPSP causes the direction of traffic to the ASP sending the an SG or IPSP causes the direction of traffic to the ASP sending the
ASPAC, in addition to all the other ASPs that are currently active in ASPAC, in addition to all the other ASPs that are currently active in
the AS. The algorithm at the SG for load-sharing traffic within an AS the AS. The algorithm at the SG for load-sharing traffic within an AS
to all the active ASPs is implementation dependent. The algorithm to all the active ASPs is implementation dependent. The algorithm
could, for example be round-robin or based on information in the Data could, for example be round-robin or based on information in the Data
message (e.g., such as the SLS, SCCP SSN, ISUP CIC value). message (e.g., such as the SLS, SCCP SSN, ISUP CIC value).
Depending on the requirements of the application and the In the case of Load-share (Standby) mode, the actions are the same with
call/transaction state handling assumptions of the collection of ASPs the exception that the traffic is not started to the ASP until the SG
in the AS. The SG or IPSP responds to the ASPAC with an ASP-Active Ack or IPSP determines that there are insufficient resources available in
message to the ASP. N the case of Loadshare (Standby) mode, the the AS. This is likely due to one of the active load-sharing ASPs
actions are the same with the exception that the traffic is not started transitions to the "Inactive" or "Down" state. At this point the ASP
to the ASP until the SG or IPSP determines that there are insufficient that sent the Load-share (Standby) ASPAC s moved to the Active state
resources available in the AS. This is likely due to one of the active and traffic is started. A Notify message is not sent in this case.
loadsharing ASPs transitions to the "Inactive" or "Down" state. At
this point the ASP that sent the Loadshare (Standby) ASPAC s moved to
the Active state and traffic is started. A Notify message is not sent
in this case.
All ASPs within a loadsharing mode AS must be able to handle any All ASPs within a load-sharing mode AS must be able to handle any
traffic within the AS, in order to accommodate any potential fail-over traffic within the AS, in order to accommodate any potential fail-over
or rebalancing of the offered load. or rebalancing of the offered load.
A node that receives an ASPAC with an incorrect Type for a particular A node that receives an ASPAC with an incorrect Type for a particular
Routing Context will respond with an Error Message (Cause: Invalid Routing Context will respond with an Error Message (Cause: Invalid
Traffic Handling Mode). A node that receives an unknown Routing Traffic Handling Mode). A node that receives an unknown Routing
Context value responds with an Error message (Cause: Invalid Routing Context value responds with an Error message (Cause: Invalid Routing
Context). Context).
4.3.3.5 ASP Inactive 4.3.3.5 ASP Inactive
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 (ASPIA) to the SG or IPSP. In the case where ASP sends an ASP Inactive (ASPIA) to the SG or IPSP. This action MAY
an ASP is processing the traffic for more than one Application Server be initiated at the ASP by an M-ASP INACTIVE request primitive from
across a common SCTP association, the ASPIA contains one or more Layer Management or may be initiated automatically by an M3UA
Routing Contexts to indicate for which Application Servers the ASPIA management function. In the case where an ASP is processing the
applies. In the case where an ASP-Inactive message does not contain a traffic for more than one Application Server across a common SCTP
Routing Context, the receiver must know via configuration data which AS association, the ASPIA contains one or more Routing Contexts to
pools the ASP is a member and move the ASP to the "Inactive" state in indicate for which Application Servers the ASPIA applies. In the case
each AS. where an ASP-Inactive message does not contain a Routing Context, the
receiver must know via configuration data which AS pools the ASP is a
member and move the ASP to the "Inactive" state in each AS.
There are two modes of Application Server traffic handling in the SG or There are two modes of Application Server traffic handling in the SG or
IPSP M3UA when withdrawing an ASP from service - Over-ride and Load- IPSP M3UA when withdrawing an ASP from service - Over-ride and Load-
share. The Type parameter in the ASPIA message indicates the mode used share. The Type parameter in the ASPIA message indicates the mode used
in a particular Application Server. If the SG or IPSP determines that in a particular Application Server. If the SG or IPSP determines that
the mode indicates in an ASPIA is inconsistent with the traffic the mode indicates in an ASPIA is inconsistent with the traffic
handling mode currently used in the AS, a this is reported to local handling mode currently used in the AS, a this is reported to local
management indicating("Invalid Traffic Handling Mode"). The ASPIA is management indicating("Invalid Traffic Handling Mode"). The ASPIA is
still processed. still processed.
In the case of an Over-ride mode AS, where another ASP has already In the case of an Over-ride mode AS, where another ASP has already
taken over the traffic within the AS with an Over-ride ASPAC, the ASP taken over the traffic within the AS with an Over-ride ASPAC, the ASP
that sends the ASPIA is already considered by the SG to be "Inactive". that sends the ASPIA is already considered by the SG to be "Inactive".
An ASPIA Ack message is sent to the ASP, after ensuring that all An ASPIA Ack message is sent to the ASP, after ensuring that all
traffic is stopped to the ASP. In the case where another ASP has traffic is stopped to the ASP.
already sent an Over-ride (Standby) ASPAC, the ASP is moved to the
"Inactive state" and traffic s immediately started to the standby ASP.
In the case of a Load-share mode AS, the SG moves the ASP to the In the case of a Load-share mode AS, the SG moves the ASP to the
"Inactive" state and the AS traffic is re-allocated across the "Inactive" state and the AS traffic is re-allocated across the
remaining "active" ASPs per the load-sharing algorithm currently used remaining "active" ASPs per the load-sharing algorithm currently used
within the AS. A NTFY(Insufficient ASPs) may be sent to all inactive within the AS. A NTFY(Insufficient ASPs) may be sent to all inactive
ASPs, if required. However, if a Loadshare (Standby) ASP is available, ASPs, if required. However, if a Loadshare (Standby) ASP is available,
it may be now immediately included in the loadshare group and a Notify it may be now immediately included in the loadshare group and a Notify
message is not sent. An ASPIA Ack message is sent to the ASP after all message is not sent. An ASPIA Ack message is sent to the ASP after all
traffic is halted. traffic is halted and Layer Management is informed with an ASP-INACTIVE
indication primitive.
At the ASP, the ASP-INACTIVE Ack message received is not acknowledged.
Layer Management is informed with an M-ASP INACTIVE confirm primitive.
When the ASP sends an ASP-Inactive it starts timer T(ack). If the ASP
does not receive a response to an ASP-Inactive within T(ack), the ASP
MAY restart T(ack) and resend ASP-Inactive messages until it receives
an ASP-Inactive Ack message. T(ack) is provisionable, with a default
of 2 seconds. Alternatively, retransmission of ASP-Inactive messages
may be put under control of Layer Management. In this method, expiry
of T(ack) results in a M-ASP-Inactive confirmation carrying a negative
indication.
If no other ASPs are "Active" or "Standby" in the Application Server, If no other ASPs are "Active" or "Standby" in the Application Server,
the SG sends a NTFY(AS-Pending) to all inactive ASPs of the AS and the SG sends a NTFY(AS-Pending) to all inactive ASPs of the AS and
either discards all incoming messages for the AS or starts buffering either discards all incoming messages for the AS or starts buffering
the incoming messages for T(r)seconds, after which messages will be the incoming messages for T(r)seconds, after which messages will be
discarded. T(r) is configurable by the network operator. If the SG discarded. T(r) is configurable by the network operator. If the SG
receives an ASPAC from an ASP in the AS before expiry of T(r), the receives an ASPAC from an ASP in the AS before expiry of T(r), the
buffered traffic is directed to the ASP and the timer is cancelled. If buffered traffic is directed to the ASP and the timer is cancelled. If
T(r) expires, the AS is moved to the "Down" state. T(r) expires, the AS is moved to the "Down" state.
4.3.3.6 Notify 4.3.3.6 Notify
A Notify message reflecting a change in the AS state is sent to all A Notify message reflecting a change in the AS state is sent to all
ASPs in the AS, except those in the "Down" state, with appropriate ASPs in the AS, except those in the "Down" state, with appropriate
Status Identification. Status Identification. At the ASP, Layer Management is informed with
an M-NOTIFY indication primitive.
In the case where a Notify (AS-Pending) message is sent by an SG that In the case where a Notify (AS-Pending) message is sent by an SG that
now has no ASPs active to service the traffic, or a NTFY(Insufficient now has no ASPs active to service the traffic, or a NTFY(Insufficient
ASPs) is sent in the Loadshare mode, the Notify does not explicitly ASPs) is sent in the Loadshare mode, the Notify does not explicitly
force the ASP(s) receiving the message to become active. The ASPs force the ASP(s) receiving the message to become active. The ASPs
remain in control of what (and when) action is taken. remain in control of what (and when) action is taken.
4.3.3.7 Heartbeat 4.3.3.7 Heartbeat
The optional Heartbeat procedures may be used when operating over The optional Heartbeat procedures may be used when operating over
skipping to change at page 61, line 7 skipping to change at page 64, line 4
4.3.3.7 Heartbeat 4.3.3.7 Heartbeat
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 the detecting loss of the transport association (i.e., other than the
SCTP). SCTP).
After receiving an ASP-Up Ack message from an M3UA peer in response to After receiving an ASP-Up Ack message from an M3UA peer in response to
an ASP-Up message, an ASP may optionally send Beat messages an ASP-Up message, an ASP may optionally send Beat messages
periodically, subject to a provisionable timer T(beat). Upon receiving periodically, subject to a provisionable timer T(beat). Upon receiving
a BEAT message, the M3UA peer MUST respond with a BEAT ACK a BEAT message, the M3UA peer MUST respond with a BEAT ACK message. If
message. If no BEAT ACK message (or any other M3UA message), is no BEAT ACK message (or any other M3UA message), is received by the ASP
received by the ASP within the timer 2*T(beat), the ASP will consider within the timer 2*T(beat), the ASP will consider the remote M3UA peer
the remote M3UA peer as "Down". as "Down".
At the ASP, if no BEAT ACK message (or any other M3UA message) is At the ASP, if no BEAT ACK message (or any other M3UA message) is
received from the M3UA peer within 2*T(beat), the remote M3UA peer is received from the M3UA peer within 2*T(beat), the remote M3UA peer is
considered unavailable. Transmission of BEAT messages is stopped and considered unavailable. Transmission of BEAT messages is stopped and
ASP-Up procedures are used to re-establish communication with the SG ASP-Up procedures are used to re-establish communication with the SG
M3UA peer. M3UA peer.
The BEAT message may optionally contain an opaque Heartbeat Data The BEAT message may optionally contain an opaque Heartbeat Data
parameter that MUST be echoed back unchanged in the related Beat Ack parameter that MUST be echoed back unchanged in the related Beat Ack
message. The ASP upon examining the contents of the returned BEAT Ack message. The ASP upon examining the contents of the returned BEAT Ack
skipping to change at page 72, line 45 skipping to change at page 75, line 45
6.3 Protecting Confidentiality 6.3 Protecting Confidentiality
Particularly for mobile users, the requirement for confidentiality may Particularly for mobile users, the requirement for confidentiality may
include the masking of IP addresses and ports. In this case include the masking of IP addresses and ports. In this case
application level encryption is not sufficient; IPSEC ESP should be application level encryption is not sufficient; IPSEC ESP should be
used instead. Regardless of which level performs the encryption, the used instead. Regardless of which level performs the encryption, the
IPSEC ISAKMP service should be used for key management. IPSEC ISAKMP service should be used for key management.
7.0 IANA Considerations 7.0 IANA Considerations
7.1 SCTP Payload Protocol Identifier
A request will be made to IANA to assign an M3UA value for the Payload A request will be made to IANA to assign an M3UA value for the Payload
Protocol Identifier in SCTP Payload Data chunk. The following SCTP Protocol Identifier in SCTP Payload Data chunk. The following SCTP
Payload Protocol Identifier will be registered: Payload Protocol Identifier will be registered:
M3UA "3" M3UA "3"
The SCTP Payload Protocol Identifier is included in each SCTP Data The SCTP Payload Protocol Identifier is included in each SCTP Data
chunk, to indicate which protocol the SCTP is carrying. This Payload chunk, to indicate which protocol the SCTP is carrying. This Payload
Protocol Identifier is not directly used by SCTP but may be used by Protocol Identifier is not directly used by SCTP but MAY be used by
certain network entities to identify the type of information being certain network entities to identify the type of information being
carried in a Data chunk. carried in a Data chunk.
The User Adaptation peer may use the Payload Protocol Identifier as a The User Adaptation peer MAY use the Payload Protocol Identifier as a
way of determining additional information about the data being way of determining additional information about the data being
presented to it by SCTP. presented to it by SCTP.
7.2 M3UA Protocol Extensions
This protocol may also be extended through IANA in three ways:
-- through definition of additional message classes,
-- through definition of additional message types, and
-- through definition of additional message parameters
The definition and use of new message classes, types and parameters is
an integral part of SIGTRAN adaptation layers. Thus these extensions
are assigned by IANA through an IETF Consensus action as defined in
[RFC2434].
The proposed extension must in no way adversely affect the general
working of the protocol.
7.2.1 IETF Defined Message Classes
The documentation for a new message class MUST include the following
information:
(a) A long and short name for the new message class;
(b) A detailed description of the purpose of the message class.
7.2.2 IETF Defined Message Types
The documentation for a new message type MUST include the following
information:
(a) A long and short name for the new message type;
(b) A detailed description of the structure of the message.
(c) A detailed definition and description of intended use for each
field within the message.
(d) A detailed procedural description of the use of the new message
type within the operation of the protocol.
(e) A detailed description of error conditions when receiving this
message type.
When an implementation receives a message type which it does not
support, it MUST respond with an Error (ERR) message, with an Error
Code = Unsupported Message Type.
7.2.3 IETF-defined TLV Parameter extension
Documentation of the message parameter MUST contain the following
information:
(a) Name of the parameter type.
(b) Detailed description of the structure of the parameter field. This
structure MUST conform to the general type-length-value format
described in Section 3.1.5.
(c) Detailed definition of each component of the parameter value.
(d) Detailed description of the intended use of this parameter type,
and an indication of whether and under what circumstances multiple
instances of this parameter type may be found within the same
message.
8.0 Acknowledgements 8.0 Acknowledgements
The authors would like to thank John Loughney, Neil Olson, Michael The authors would like to thank John Loughney, Neil Olson, Michael
Tuexen, Nikhil Jain, Steve Lorusso, Dan Brendes, Joe Keller, Heinz Tuexen, Nikhil Jain, Steve Lorusso, Dan Brendes, Joe Keller, Heinz
Prantner, Barry Nagelberg, Naoto Makinae for their valuable comments Prantner, Barry Nagelberg, Naoto Makinae for their valuable comments
and suggestions. and suggestions.
9.0 References 9.0 References
[1] RFC 2719, "Framework Architecture for Signaling Transport" [1] RFC 2719, "Framework Architecture for Signaling Transport"
skipping to change at page 74, line 10 skipping to change at page 78, line 20
[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 V3.1.0 (2000-01) Technical Specification - 3rd [12] 3G TS 25.410 V3.1.0 (2000-01) Technical Specification - 3rd
Generation partnership Project; Technical Specification Group Generation partnership Project; Technical Specification Group
Radio Access Network; UTRAN Iu Interface: General Aspects and Radio Access Network; UTRAN Iu Interface: General Aspects and
Principles (3G TS 25.410 Version 3.1.0 Release 1999) Principles (3G TS 25.410 Version 3.1.0 Release 1999)
[13] Stream Control Transport Protocol <draft-ietf-sigtran-sctp- [13] RFC 2719, "Stream Control Transport Protocol", R. Stewart et al,
13.txt>, July 2000, Work in Progress October 2000.
[14] ITU-T Recommendations Q.701-Q.705, 'Signalling System No. 7 (SS7) [14] ITU-T Recommendations Q.701-Q.705, 'Signalling System No. 7 (SS7)
- Message Transfer Part (MTP)' - Message Transfer Part (MTP)'
[15] ANSI T1.111 'Signaling System Number 7 - Message Transfer Part' [15] ANSI T1.111 'Signaling System Number 7 - Message Transfer Part'
[16] ETSI ETS 300 008-1, "Integrated Services Digital Network (ISDN); [16] ETSI ETS 300 008-1, "Integrated Services Digital Network (ISDN);
Signalling System No.7; Message Transfer Part (MTP) to support Signalling System No.7; Message Transfer Part (MTP) to support
international interconnection; Part 1: Protocol specification" international interconnection; Part 1: Protocol specification"
skipping to change at page 74, line 41 skipping to change at page 79, line 7
[20] ITU-T Recommendation Q.2210 'B-ISDN MTP' [20] ITU-T Recommendation Q.2210 'B-ISDN MTP'
[21] RFC 2196, "Site Security Handbook", B. Fraser Ed., September 1997 [21] RFC 2196, "Site Security Handbook", B. Fraser Ed., September 1997
[22] RFC 2401, "Security Architecture for the Internet Protocol", S. [22] RFC 2401, "Security Architecture for the Internet Protocol", S.
Kent, R. Atkinson, November 1998. Kent, R. Atkinson, November 1998.
10.0 Author's Addresses 10.0 Author's Addresses
Lyndon Ong
Nortel Networks
4401 Great America Pkwy
Santa Clara, CA, USA 95054
long@nortelnetworks.com
Greg Sidebottom Greg Sidebottom
Nortel Networks Nortel Networks
3685 Richmond Rd, 3685 Richmond Rd,
Nepean, Ontario, Canada K2H 5B7 Nepean, Ontario, Canada K2H 5B7
gregside@nortelnetworks.com gregside@nortelnetworks.com
Guy Mousseau Guy Mousseau
Nortel Networks Nortel Networks
3685 Richmond Rd 3685 Richmond Rd
Nepean, Ontario, Canada K2H 5B7 Nepean, Ontario, Canada K2H 5B7
Lyndon Ong
Nortel Networks
4401 Great America Pkwy
Santa Clara, CA, USA 95054
long@nortelnetworks.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 ian.rytina@ericsson.com
Hanns Juergen Schwarzbauer Hanns Juergen Schwarzbauer
SIEMENS AG SIEMENS AG
Hofmannstr. 51 Hofmannstr. 51
81359 Munich, Germany 81359 Munich, Germany
skipping to change at page 75, line 39 skipping to change at page 79, line 53
Cisco Systems Inc. Cisco Systems Inc.
13615 Dulles Technology Drive 13615 Dulles Technology Drive
Herndon, VA, USA 20171 Herndon, VA, USA 20171
EMail: kmorneau@cisco.com 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
This draft expires March 2000. This draft expires May 2000.
 End of changes. 

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