draft-ietf-sigtran-m2ua-08.txt   draft-ietf-sigtran-m2ua-09.txt 
skipping to change at page 1, line 14 skipping to change at page 1, line 14
Cisco Systems Cisco Systems
Greg Sidebottom Greg Sidebottom
Nortel Networks Nortel Networks
Tom George Tom George
Alcatel Alcatel
Brian Bidulock Brian Bidulock
OpenSS7 OpenSS7
Jacob Heitz Jacob Heitz
Lucent Lucent
Expires in six months June 2001 Expires in six months July 2001
SS7 MTP2-User Adaptation Layer SS7 MTP2-User Adaptation Layer
<draft-ietf-sigtran-m2ua-08.txt> <draft-ietf-sigtran-m2ua-09.txt>
Status of This Memo Status of This Memo
This document is an Internet-Draft and is in full conformance with all This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 of RFC 2026. Internet-Drafts are working provisions of Section 10 of RFC 2026. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, documents of the Internet Engineering Task Force (IETF), its areas,
and its working groups. Note that other groups MAY also distribute and its working groups. Note that other groups MAY also distribute
working documents as Internet-Drafts. working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
skipping to change at page 3, line 26 skipping to change at page 3, line 26
and MGC and MGC
* Support for management of SCTP active associations between the SG and * Support for management of SCTP active associations between the SG and
MGC MGC
The SG will terminate up to MTP Level 2 and the MGC will terminate The SG will terminate up to MTP Level 2 and the MGC will terminate
MTP Level 3 and above. In other words, the SG will transport MTP MTP Level 3 and above. In other words, the SG will transport MTP
Level 3 messages over an IP network to a MGC or IPSP. Level 3 messages over an IP network to a MGC or IPSP.
1.2 Terminology 1.2 Terminology
MTP2-User - A protocol that uses the services of MTP Level 2
(i.e. MTP3).
Interface - For the purposes of this document, an interface is a SS7
signaling link.
Backhaul - Refers to the transport of signaling from the point of
interface for the associated data stream (i.e., SG function in the MGU)
back to the point of call processing (i.e., the MGCU), if this is not
local [4].
Association - An association refers to a SCTP association. The
association will provide the transport for the delivery of protocol
data units for one or more interfaces.
Stream - A stream refers to an SCTP stream; a uni-directional logical
channel established from one SCTP endpoint to another associated SCTP
endpoint, within which all user messages are delivered in-sequence
except for those submitted to the un-ordered delivery service.
Interface Identifier - The Interface Identifier identifies the physical
interface at the SG for which the signaling messages are sent/received.
The format of the Interface Identifier parameter can be text or integer,
the values of which are assigned according to network operator policy.
The values used are of local significance only, coordinated between the
SG and ASP.
Application Server (AS) - A logical entity serving a specific application Application Server (AS) - A logical entity serving a specific application
instance. An example of an Application Server is a MGC handling the instance. An example of an Application Server is a MGC handling the
MTP Level 3 and call processing for SS7 links terminated by the MTP Level 3 and call processing for SS7 links terminated by the
Signaling Gateways. Practically speaking, an AS is modeled at the SG Signaling Gateways. Practically speaking, an AS is modeled at the SG
as an ordered list of one or more related Application Server Processes as an ordered list of one or more related Application Server Processes
(e.g., primary, secondary, tertiary, ...). (e.g., primary, secondary, tertiary, ...).
Application Server Process (ASP) - A process instance of an Application Application Server Process (ASP) - A process instance of an Application
Server. Examples of Application Server Processes are primary or backup Server. Examples of Application Server Processes are primary or backup
MGC instances. MGC instances.
Association - An association refers to a SCTP association. The
association will provide the transport for the delivery of protocol
data units for one or more interfaces.
Backhaul - Refers to the transport of signaling from the point of
interface for the associated data stream (i.e., SG function in the MGU)
back to the point of call processing (i.e., the MGCU), if this is not
local [4].
Fail-over - The capability to re-route signaling traffic as required Fail-over - The capability to re-route signaling traffic as required
to an alternate Application Server Process within an Application Server to an alternate Application Server Process within an Application Server
in the event of failure or unavailability of a currently used Application in the event of failure or unavailability of a currently used Application
Server Process. Fail-back MAY apply upon the return to service of a Server Process. Fail-back MAY apply upon the return to service of a
previously unavailable Application Server Process. previously unavailable Application Server Process.
Signaling Link Terminal (SLT) - Refers to the means of performing all Host - The computing platform that the ASP process is running on.
of the functions defined at MTP level 2 regardless of their
implementation [2]. Interface - For the purposes of this document, an interface is a SS7
signaling link.
Interface Identifier - The Interface Identifier identifies the physical
interface at the SG for which the signaling messages are sent/received.
The format of the Interface Identifier parameter can be text or integer,
the values of which are assigned according to network operator policy.
The values used are of local significance only, coordinated between the
SG and ASP.
Layer Management - Layer Management is a nodal function in an SG or Layer Management - Layer Management is a nodal function in an SG or
ASP that handles the inputs and outputs between the M2UA layer and a ASP that handles the inputs and outputs between the M2UA layer and a
local management entity. local management entity.
Link Key - The link key is a locally unique (between ASP and SG)
value that identifies a registration request for a particular Signaling
Data Link and Signaling Terminal pair.
MTP - The Message Transfer Part of the SS7 protocol. MTP - The Message Transfer Part of the SS7 protocol.
MTP2 - MTP Level 2, the signalling datalink layer of SS7 MTP2 - MTP Level 2, the signalling datalink layer of SS7
MTP3 - MTP Level 3, the signalling network layer of SS7 MTP3 - MTP Level 3, the signalling network layer of SS7
MTP2-User - A protocol that uses the services of MTP Level 2
(i.e. MTP3).
Network Byte Order: Most significant byte first, a.k.a Big Endian. Network Byte Order: Most significant byte first, a.k.a Big Endian.
Host - The computing platform that the ASP process is running on. Signaling Link Terminal (SLT) - Refers to the means of performing all
of the functions defined at MTP level 2 regardless of their
implementation [2].
Stream - A stream refers to an SCTP stream; a uni-directional logical
channel established from one SCTP endpoint to another associated SCTP
endpoint, within which all user messages are delivered in-sequence
except for those submitted to the un-ordered delivery service.
1.3 M2UA Overview 1.3 M2UA Overview
The framework architecture that has been defined for SCN signaling The framework architecture that has been defined for SCN signaling
transport over IP [6] uses two components: a signaling common transport over IP [6] uses two components: a signaling common
transport protocol and an adaptation module to support the services transport protocol and an adaptation module to support the services
expected by a particular SCN signaling protocol from its underlying expected by a particular SCN signaling protocol from its underlying
protocol layer. protocol layer.
Within this framework architecture, this document defines a SCN Within this framework architecture, this document defines a SCN
skipping to change at page 5, line 64 skipping to change at page 5, line 64
and ASPs and ASPs
The M2UA layer at the SG maintains the availability state of all The M2UA layer at the SG maintains the availability state of all
configured ASPs, in order to manage the SCTP associations and the configured ASPs, in order to manage the SCTP associations and the
traffic between the SG and ASPs. As well, the active/inactive state traffic between the SG and ASPs. As well, the active/inactive state
of remote ASP(s) are also maintained. The Active ASP(s) are the one(s) of remote ASP(s) are also maintained. The Active ASP(s) are the one(s)
currently receiving traffic from the SG. currently receiving traffic from the SG.
The M2UA layer MAY be instructed by local management to establish an The M2UA layer MAY be instructed by local management to establish an
SCTP association to a peer M2UA node. This can be achieved using the SCTP association to a peer M2UA node. This can be achieved using the
M-SCTP ESTABLISH primitive to request, indicate and confirm the M-SCTP_ESTABLISH primitive to request, indicate and confirm the
establishment of an SCTP association with a peer M2UA node. establishment of an SCTP association with a peer M2UA node.
The M2UA layer MAY also need to inform local management of the status of The M2UA layer MAY also need to inform local management of the status of
the underlying SCTP associations using the M-SCTP STATUS request and the underlying SCTP associations using the M-SCTP_STATUS request and
indication primitive. For example, the M2UA MAY inform local management indication primitive. For example, the M2UA MAY inform local management
of the reason for the release of an SCTP association, determined either of the reason for the release of an SCTP association, determined either
locally within the M2UA layer or by a primitive from the SCTP. locally within the M2UA layer or by a primitive from the SCTP.
Also the M3UA layer may need to inform the local management of the Also the M2UA layer may need to inform the local management of the
change in status of an ASP or AS. This may be achieved using the M-ASP change in status of an ASP or AS. This may be achieved using the M-ASP
STATUS request or M-AS STATUS request primitives. STATUS request or M-AS_STATUS request primitives.
1.3.3 Signaling Network Architecture 1.3.3 Signaling Network Architecture
A Signaling Gateway will support the transport of MTP2-User signaling A Signaling Gateway will support the transport of MTP2-User signaling
traffic received from the SS7 network to one or more distributed ASPs traffic received from the SS7 network to one or more distributed ASPs
(e.g., MGCs). Clearly, the M2UA protocol description cannot in itself (e.g., MGCs). Clearly, the M2UA protocol description cannot in itself
meet any performance and reliability requirements for such transport. meet any performance and reliability requirements for such transport.
A physical network architecture is required, with data on the A physical network architecture is required, with data on the
availability and transfer performance of the physical nodes involved in availability and transfer performance of the physical nodes involved in
any particular exchange of information. However, the M2UA protocol MUST any particular exchange of information. However, the M2UA protocol MUST
skipping to change at page 6, line 48 skipping to change at page 6, line 48
1.3.4 ASP Fail-over Model and Terminology 1.3.4 ASP Fail-over Model and Terminology
The M2UA layer supports ASP fail-over functions in order to support a The M2UA layer supports ASP fail-over functions in order to support a
high availability of call and transaction processing capability. All high availability of call and transaction processing capability. All
MTP2-User messages incoming to a SG from the SS7 network are assigned MTP2-User messages incoming to a SG from the SS7 network are assigned
to the unique Application Server, based on the Interface Identifier of to the unique Application Server, based on the Interface Identifier of
the message. the message.
The M2UA layer supports a n+k redundancy model (active-standby, The M2UA layer supports a n+k redundancy model (active-standby,
loadsharing, broadcast) where 1 ASP is the minimum number of redundant loadsharing, broadcast) where n ASP is the minimum number of redundant
ASPs required to handle traffic and k ASPs are available to take over ASPs required to handle traffic and k ASPs are available to take over
for a failed or unavailable ASP. Note that 1+1 active/standby redundancy for a failed or unavailable ASP. Note that 1+1 active/standby redundancy
is a subset of this model. A simplex 1+0 model is also supported as a is a subset of this model. A simplex 1+0 model is also supported as a
subset, with no ASP redundancy. subset, with no ASP redundancy.
To avoid a single point of failure, it is recommended that a minimum of To avoid a single point of failure, it is recommended that a minimum of
two ASPs be configured in an AS list, resident in separate hosts and, two ASPs be configured in an AS list, resident in separate hosts and,
therefore, available over different SCTP associations. For example, in therefore, available over different SCTP associations. For example, in
the network shown in Figure 2, all messages for the Interface Identifiers the network shown in Figure 2, all messages for the Interface Identifiers
could be sent to ASP1 in Host1 or ASP2 in Host2. The AS list at SG1 could be sent to ASP1 in Host1 or ASP2 in Host2. The AS list at SG1
skipping to change at page 8, line 30 skipping to change at page 8, line 30
1.4.3 Support for management of active associations between SG and MGC 1.4.3 Support for management of active associations between SG and MGC
As discussed in Section 1.3.2, the M2UA layer on the SG keeps the state As discussed in Section 1.3.2, the M2UA layer on the SG keeps the state
of the configured ASPs. A set of primitives between M2UA layer and the of the configured ASPs. A set of primitives between M2UA layer and the
Layer Management are defined below to help the Layer Management manage Layer Management are defined below to help the Layer Management manage
the association(s) between the SG and the MGC. The M2UA layer can be the association(s) between the SG and the MGC. The M2UA layer can be
instructed by the Layer Management to establish a SCTP association to instructed by the Layer Management to establish a SCTP association to
a peer M2UA node. This procedure can be achieved using the M-SCTP a peer M2UA node. This procedure can be achieved using the M-SCTP
ESTABLISH primitive. ESTABLISH primitive.
M-SCTP ESTABLISH M-SCTP_ESTABLISH
The M-SCTP ESTABLISH primitive is used to request, indicate and confirm The M-SCTP_ESTABLISH primitive is used to request, indicate and confirm
the establishment of a SCTP association to a peer M2UA node. the establishment of a SCTP association to a peer M2UA node.
M-SCTP RELEASE M-SCTP_RELEASE
The M-SCTP RELEASE primitives are used to request, indicate, and The M-SCTP_RELEASE primitives are used to request, indicate, and
confirm the release of a SCTP association to a peer M2UA node. confirm the release of a SCTP association to a peer M2UA node.
The M2UA layer MAY also need to inform the status of the SCTP The M2UA layer MAY also need to inform the status of the SCTP
association(s) to the Layer Management. This can be achieved using association(s) to the Layer Management. This can be achieved using
the following primitive. the following primitive.
M-SCTP STATUS M-SCTP_STATUS
The M-SCTP STATUS primitive is used to request and indicate the status The M-SCTP_STATUS primitive is used to request and indicate the status
of underlying SCTP association(s). of underlying SCTP association(s).
The Layer Management MAY need to inform the M2UA layer of an AS/ASP The Layer Management MAY need to inform the M2UA layer of an AS/ASP
status (i.e., failure, active, etc.), so that messages can be exchanged status (i.e., failure, active, etc.), so that messages can be exchanged
between M2UA layer peers to stop traffic to the local M2UA user. This between M2UA layer peers to stop traffic to the local M2UA user. This
can be achieved using the following primitive. can be achieved using the following primitive.
M-ASP STATUS M-ASP_STATUS
The ASP status is stored inside M2UA layer on both the SG and MGC The ASP status is stored inside M2UA layer on both the SG and MGC
sides. The M-ASP STATUS primitive can be used by Layer Management to sides. The M-ASP_STATUS primitive can be used by Layer Management to
request the status of the Application Server Process from the M2UA request the status of the Application Server Process from the M2UA
layer. This primitive can also be used to indicate the status of the layer. This primitive can also be used to indicate the status of the
Application Server Process. Application Server Process.
M-ASP MODIFY M-ASP_MODIFY
The M-ASP MODIFY primitive can be used by Layer Management to modify The M-ASP_MODIFY primitive can be used by Layer Management to modify
the status of the Application Server Process. In other words, the the status of the Application Server Process. In other words, the
Layer Management on the ASP side uses this primitive to initiate Layer Management on the ASP side uses this primitive to initiate
the ASPM procedures. the ASPM procedures.
M-AS STATUS M-AS_STATUS
The M-AS STATUS primitive can be used by Layer Management to request The M-AS_STATUS primitive can be used by Layer Management to request
the status of the Application Server. This primitive can also be the status of the Application Server. This primitive can also be
used to indicate the status of the Application Server. used to indicate the status of the Application Server.
1.5 Functions Provided by the M2UA Layer 1.5 Functions Provided by the M2UA Layer
1.5.1 Mapping 1.5.1 Mapping
The M2UA layer MUST maintain a map of a Interface ID to a physical The M2UA layer MUST maintain a map of a Interface ID to a physical
interface on the Signaling Gateway. A physical interface would be a interface on the Signaling Gateway. A physical interface would be a
V.35 line, T1 line/timeslot, E1 line/timeslot, etc. The M2UA layer V.35 line, T1 line/timeslot, E1 line/timeslot, etc. The M2UA layer
skipping to change at page 9, line 90 skipping to change at page 9, line 90
At a SG, an Application Server list MAY contain active and inactive At a SG, an Application Server list MAY contain active and inactive
ASPs to support ASP fail-over procedures. When, for example, both ASPs to support ASP fail-over procedures. When, for example, both
a primary and a back-up ASP are available, M2UA peer protocol is a primary and a back-up ASP are available, M2UA peer protocol is
required to control which ASP is currently active. The ordered required to control which ASP is currently active. The ordered
list of ASPs within a logical Application Server is kept updated in list of ASPs within a logical Application Server is kept updated in
the SG to reflect the active Application Server Process. the SG to reflect the active Application Server Process.
Also the M2UA layer MAY need to inform the local management of the Also the M2UA layer MAY need to inform the local management of the
change in status of an ASP or AS. This can be achieved using the M-ASP change in status of an ASP or AS. This can be achieved using the M-ASP
STATUS or M-AS STATUS primitives. STATUS or M-AS_STATUS primitives.
1.5.3 SCTP Specifics 1.5.3 SCTP Specifics
1.5.3.1 SCTP Stream Management 1.5.3.1 SCTP Stream Management
SCTP allows a user specified number of streams to be opened during SCTP allows a user specified number of streams to be opened during
initialization of the association. It is the responsibility of the initialization of the association. It is the responsibility of the
M2UA layer to ensure proper management of these streams. Because of M2UA layer to ensure proper management of these streams. Because of
the unidirectional nature of streams, a M2UA layer is not aware of the the unidirectional nature of streams, a M2UA layer is not aware of the
stream information from its peer M2UA layer. Instead, the Interface stream information from its peer M2UA layer. Instead, the Interface
skipping to change at page 9, line 120 skipping to change at page 9, line 120
sequence number is 16-bits. sequence number is 16-bits.
SCTP Stream '0' SHOULD not be used for MTP2 User Adaptation (MAUP) SCTP Stream '0' SHOULD not be used for MTP2 User Adaptation (MAUP)
messages (see Section 3) since stream '0' SHOULD onlt be used for ASP messages (see Section 3) since stream '0' SHOULD onlt be used for ASP
Management (ASPM) messages (see Section 4.3.3). Management (ASPM) messages (see Section 4.3.3).
1.5.4 Seamless SS7 Network Management Interworking 1.5.4 Seamless SS7 Network Management Interworking
The M2UA layer on the SG SHOULD pass an indication of unavailability of The M2UA layer on the SG SHOULD pass an indication of unavailability of
the M2UA-User (MTP3) to the local Layer Management, if the currently the M2UA-User (MTP3) to the local Layer Management, if the currently
active ASP moves from the ACTIVE state. If the AS moves to the DOWN active ASP moves from the ACTIVE state. The actions taken by M2UA
state while SS7 links are in-service, the SG SHOULD follow the MTP 2 on the SG with regards to MTP Level 2 should be in accordance with
processor outage procedures [2]. the appropriate MTP specifications.
1.5.5 Flow Control / Congestion 1.5.5 Flow Control / Congestion
It is possible for the M2UA layer to be informed of IP network It is possible for the M2UA layer to be informed of IP network
congestion onset and abatement by means of an implementation-dependent congestion onset and abatement by means of an implementation-dependent
function (i.e. an indication from the SCTP). The handling of function (i.e. an indication from the SCTP). The handling of
this congestion indication by M2UA is implementation dependent. this congestion indication by M2UA is implementation dependent.
1.5.6 Audit of Link State 1.5.6 Audit of Link State
skipping to change at page 10, line 32 skipping to change at page 10, line 32
DATA RETRIEVAL DATA RETRIEVAL
DATA RETRIEVAL COMPLETE DATA RETRIEVAL COMPLETE
1.6.3 Definition of the Lower Layer Boundary between M2UA and SCTP 1.6.3 Definition of the Lower Layer Boundary between M2UA and SCTP
The upper layer and layer management primitives provided by SCTP are The upper layer and layer management primitives provided by SCTP are
provided in Reference [5] Section 9. provided in Reference [5] Section 9.
1.6.4 Definition of Layer Management / M2UA Boundary 1.6.4 Definition of Layer Management / M2UA Boundary
M-SCTP ESTABLISH request M-SCTP_ESTABLISH request
Direction: LM -> M2UA Direction: LM -> M2UA
Purpose: LM requests ASP to establish an SCTP association with an SG. Purpose: LM requests ASP to establish an SCTP association with an SG.
M-STCP ESTABLISH confirm M-SCTP_ESTABLISH confirm
Direction: M2UA -> LM Direction: M2UA -> LM
Purpose: ASP confirms to LM that it has established an SCTP Purpose: ASP confirms to LM that it has established an SCTP
association with an SG. association with an SG.
M-SCTP ESTABLISH indication M-SCTP_ESTABLISH indication
Direction: M2UA -> LM Direction: M2UA -> LM
Purpose: SG informs LM that an ASP has established an SCTP Purpose: SG informs LM that an ASP has established an SCTP
association. association.
M-SCTP RELEASE request M-SCTP_RELEASE request
Direction: LM -> M2UA Direction: LM -> M2UA
Purpose: LM requests ASP to release an SCTP association with SG. Purpose: LM requests ASP to release an SCTP association with SG.
M-SCTP RELEASE confirm M-SCTP_RELEASE confirm
Direction: M2UA -> LM Direction: M2UA -> LM
Purpose: ASP confirms to LM that it has released SCTP association Purpose: ASP confirms to LM that it has released SCTP association
with SG. with SG.
M-SCTP RELEASE indication M-SCTP_RELEASE indication
Direction: M2UA -> LM Direction: M2UA -> LM
Purpose: SG or IPSP informs LM that ASP has released an SCTP Purpose: SG or IPSP informs LM that ASP has released an SCTP
association. association.
M-SCTP STATUS request M-SCTP_RESTART indication
Direction: M2UA -> LM
Purpose: SG or IPSP informs LM that a SCTP Restart indication has
been received
M-SCTP_STATUS request
Direction: LM -> M2UA Direction: LM -> M2UA
Purpose: LM requests M2UA to report status of SCTP association. Purpose: LM requests M2UA to report status of SCTP association.
M-SCTP STATUS indication M-SCTP_STATUS indication
Direction: M2UA -> LM Direction: M2UA -> LM
Purpose: M2UA reports status of SCTP association. Purpose: M2UA reports status of SCTP association.
M-ASP STATUS request M-ASP_STATUS request
Direction: LM -> M2UA Direction: LM -> M2UA
Purpose: LM requests SG to report status of remote ASP. Purpose: LM requests SG to report status of remote ASP.
M-ASP STATUS indication M-ASP_STATUS indication
Direction: M2UA -> LM Direction: M2UA -> LM
Purpose: SG reports status of remote ASP. Purpose: SG reports status of remote ASP.
M-AS-STATUS request M-AS_STATUS request
Direction: LM -> M2UA Direction: LM -> M2UA
Purpose: LM requests SG to report status of AS. Purpose: LM requests SG to report status of AS.
M-AS-STATUS indication M-AS_STATUS indication
Direction: M2UA -> LM Direction: M2UA -> LM
Purpose: SG reports status of AS. Purpose: SG reports status of AS.
M-NOTIFY indication M-NOTIFY indication
Direction: M2UA -> LM Direction: M2UA -> LM
Purpose: ASP reports that it has received a NOTIFY message Purpose: ASP reports that it has received a NOTIFY message
from its peer. from its peer.
M-ERROR indication M-ERROR indication
Direction: M2UA -> LM Direction: M2UA -> LM
Purpose: ASP or SG reports that it has received an ERROR Purpose: ASP or SG reports that it has received an ERROR
message from its peer. message from its peer.
M-ASP-UP request M-ASP_UP request
Direction: LM -> M2UA Direction: LM -> M2UA
Purpose: LM requests ASP to start its operation and send an ASP UP Purpose: LM requests ASP to start its operation and send an ASP UP
message to the SG. message to the SG.
M-ASP-UP confirm M-ASP_UP confirm
Direction: M2UA -> LM Direction: M2UA -> LM
Purpose: ASP reports that it has received an ASP UP Acknowledgement Purpose: ASP reports that it has received an ASP UP Acknowledgement
message from the SG. message from the SG.
M-ASP-DOWN request M-ASP_DOWN request
Direction: LM -> M2UA Direction: LM -> M2UA
Purpose: LM requests ASP to stop its operation and send an ASP DOWN Purpose: LM requests ASP to stop its operation and send an ASP DOWN
message to the SG. message to the SG.
M-ASP-DOWN confirm M-ASP_DOWN confirm
Direction: M2UA -> LM Direction: M2UA -> LM
Purpose: ASP reports that is has received an ASP DOWN Acknowledgement Purpose: ASP reports that is has received an ASP DOWN Acknowledgement
message from the SG. message from the SG.
M-ASP-ACTIVE request M-ASP_ACTIVE request
Direction: LM -> M2UA Direction: LM -> M2UA
Purpose: LM requests ASP to send an ASP ACTIVE message to the SG. Purpose: LM requests ASP to send an ASP ACTIVE message to the SG.
M-ASP-ACTIVE confirm M-ASP_ACTIVE confirm
Direction: M2UA -> LM Direction: M2UA -> LM
Purpose: ASP reports that is has received an ASP ACTIVE Acknowledgement Purpose: ASP reports that is has received an ASP ACTIVE Acknowledgement
message from the SG. message from the SG.
M-ASP-INACTIVE request M-ASP_INACTIVE request
Direction: LM -> M2UA Direction: LM -> M2UA
Purpose: LM requests ASP to send an ASP INACTIVE message to the SG. Purpose: LM requests ASP to send an ASP INACTIVE message to the SG.
M-ASP-INACTIVE confirm M-ASP_INACTIVE confirm
Direction: M2UA -> LM Direction: M2UA -> LM
Purpose: ASP reports that is has received an ASP INACTIVE Acknowledgement Purpose: ASP reports that is has received an ASP INACTIVE Acknowledgement
message from the SG. message from the SG.
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].
skipping to change at page 11, line 40 skipping to change at page 11, line 40
Value Version Value Version
----- ------- ----- -------
1 Release 1.0 1 Release 1.0
3.1.2 Message Type 3.1.2 Message Type
The following List contains the valid Message Classes: The following List contains the valid Message Classes:
Message Class: 8 bits (unsigned integer) Message Class: 8 bits (unsigned integer)
0 Management (MGMT) Message [IUA/M2UA/M3UA/SUA] 0 Management (MGMT) Message [IUA/M2UA/M2UA/SUA]
1 Transfer Messages [M3UA] 1 Transfer Messages [M2UA]
2 SS7 Signalling Network Management (SSNM) Messages [M3UA/SUA] 2 SS7 Signalling Network Management (SSNM) Messages [M2UA/SUA]
3 ASP State Maintenance (ASPSM) Messages [IUA/M2UA/M3UA/SUA] 3 ASP State Maintenance (ASPSM) Messages [IUA/M2UA/M2UA/SUA]
4 ASP Traffic Maintenance (ASPTM) Messages [IUA/M2UA/M3UA/SUA] 4 ASP Traffic Maintenance (ASPTM) Messages [IUA/M2UA/M2UA/SUA]
5 Q.921/Q.931 Boundary Primitives Tranport (QPTM) 5 Q.921/Q.931 Boundary Primitives Tranport (QPTM)
Messages [IUA] Messages [IUA]
6 MTP2 User Adaptatation (MAUP) Messages [M2UA] 6 MTP2 User Adaptatation (MAUP) Messages [M2UA]
7 Connectionless Messages [SUA] 7 Connectionless Messages [SUA]
8 Connection-Oriented Messages [SUA] 8 Connection-Oriented Messages [SUA]
9 to 127 Reserved by the IETF 9 Routing Key Management (RKM) Messages (M2UA)
10 Interface Identifier Management (IIM) Messages (M2UA)
11 to 127 Reserved by the IETF
128 to 255 Reserved for IETF-Defined Message Class extensions 128 to 255 Reserved for IETF-Defined Message Class extensions
The following list contains the message types for the defined messages. The following list contains the message types for the defined messages.
MTP2 User Adaptatation (MAUP) Messages MTP2 User Adaptatation (MAUP) Messages
0 Reserved 0 Reserved
1 Data 1 Data
2 Establish Request 2 Establish Request
3 Establish Confirm 3 Establish Confirm
skipping to change at page 11, line 72 skipping to change at page 11, line 74
5 Release Confirm 5 Release Confirm
6 Release Indication 6 Release Indication
7 State Request 7 State Request
8 State Confirm 8 State Confirm
9 State Indication 9 State Indication
10 Data Retrieval Request 10 Data Retrieval Request
11 Data Retrieval Confirm 11 Data Retrieval Confirm
12 Data Retrieval Indication 12 Data Retrieval Indication
13 Data Retrieval Complete Indication 13 Data Retrieval Complete Indication
14 Congestion Indication 14 Congestion Indication
15 to 127 Reserved by the IETF 15 Data Acknowledge
16 to 127 Reserved by the IETF
128 to 255 Reserved for IETF-Defined MAUP extensions 128 to 255 Reserved for IETF-Defined MAUP extensions
Application Server Process State Maintenance (ASPSM) messages Application Server Process State Maintenance (ASPSM) messages
0 Reserved 0 Reserved
1 ASP Up (UP) 1 ASP Up (UP)
2 ASP Down (DOWN) 2 ASP Down (DOWN)
3 Reserved 3 Reserved
4 ASP Up Ack (UP ACK) 4 ASP Up Ack (UP ACK)
5 ASP Down Ack (DOWN ACK) 5 ASP Down Ack (DOWN ACK)
6 Reserved 6 Reserved
skipping to change at page 12, line 33 skipping to change at page 12, line 33
5 to 127 Reserved by the IETF 5 to 127 Reserved by the IETF
128 to 255 Reserved for IETF-Defined ASPTM extensions 128 to 255 Reserved for IETF-Defined ASPTM extensions
Management (MGMT) Messages Management (MGMT) Messages
0 Error (ERR) 0 Error (ERR)
1 Notify (NTFY) 1 Notify (NTFY)
2 to 127 Reserved by the IETF 2 to 127 Reserved by the IETF
128 to 255 Reserved for IETF-Defined MGMT extensions 128 to 255 Reserved for IETF-Defined MGMT extensions
Interface Identifier Management (IIM) Messages
0 Reserved
1 Registration Request (REG REQ)
2 Registration Response (REG RSP)
3 Deregistration Request (DEREG REQ)
4 Deregistration Response (DEREG RSP)
5 to 127 Reserved by the IETF
128 to 255 Reserved for IETF-Defined IIM extensions
3.1.3 Reserved 3.1.3 Reserved
The Reserved field is 8-bits. It SHOULD be set to all '0's and The Reserved field is 8-bits. It SHOULD be set to all '0's and
ignored by the receiver. ignored by the receiver.
3.1.4 Message Length 3.1.4 Message Length
The Message Length defines the length of the message in octets, The Message Length defines the length of the message in octets,
including the header. The Message Length includes parameter including the header. The Message Length includes parameter
padding bytes, if any. padding bytes, if any.
skipping to change at page 12, line 80 skipping to change at page 12, line 90
Parameter Value Parameter Name Parameter Value Parameter Name
--------------- -------------- --------------- --------------
0 (0x0) Reserved 0 (0x0) Reserved
1 (0x1) Interface Identifier (Integer) 1 (0x1) Interface Identifier (Integer)
2 (0x2) Interface Identifier (Integer Range) 2 (0x2) Interface Identifier (Integer Range)
3 (0x3) Interface Identifier (Text) 3 (0x3) Interface Identifier (Text)
4 (0x4) Info String 4 (0x4) Info String
5 (0x5) Unused 5 (0x5) Unused
6 (0x6) Unused 6 (0x6) Unused
7 (0x7) Diagnostic Information 7 (0x7) Diagnostic Information
8 (0x8) Heartbeat Data 8 (0x8) Unused
9 (0x9) Unused 9 (0x9) Heartbeat Data
10 (0xa) Reason 10 (0xa) Reason
11 (0xb) Traffic Mode Type 11 (0xb) Traffic Mode Type
12 (0xc) Error Code 12 (0xc) Error Code
13 (0xd) Status Type/Information 13 (0xd) Status Type/Information
14 (0xe) ASP Identifier 14 (0xe) ASP Identifier
The M2UA specific parameter Tags defined are as follows: The M2UA specific parameter Tags defined are as follows:
Parameter Value Parameter Name Parameter Value Parameter Name
--------------- -------------- --------------- --------------
768 (0x0300) Protocol Data 1 768 (0x0300) Protocol Data 1
769 (0x0301) Protocol Data 2 (TTC) 769 (0x0301) Protocol Data 2 (TTC)
770 (0x0302) State Request 770 (0x0302) State Request
771 (0x0303) State Result 771 (0x0303) State Event
772 (0x0304) State Event 772 (0x0304) Congestion Status
773 (0x0305) Congestion Status 773 (0x0305) Discard Status
774 (0x0306) Discard Status 774 (0x0306) Action
775 (0x0307) Action 775 (0x0307) Sequence Number
776 (0x0308) Sequence Number 776 (0x0309) Retrieval Result
777 (0x0309) Retrieval Result 777 (0x030a) Link Key
778 (0x030b) Local-LK-Identifier
779 (0x030c) Signaling Data Terminal (SDT) Identifier
780 (0x030d) Signailng Data Link (SDL) Identifier
781 (0x030e) Registration Result
782 (0x030f) Registration Status
783 (0x0310) De-Registration Result
784 (0x0311) De-Registration Status
785 (0x0312) Correlation Id
786 (0x0313) Correlation Id Ack
Parameter Length: 16 bits (unsigned integer) Parameter Length: 16 bits (unsigned integer)
The Parameter Length field contains the size of the parameter in bytes, The Parameter Length field contains the size of the parameter in bytes,
including the Parameter Tag, Parameter Length, and Parameter Value including the Parameter Tag, Parameter Length, and Parameter Value
fields. The Parameter Length does not include any padding bytes. fields. The Parameter Length does not include any padding bytes.
Parameter Value: variable-length. Parameter Value: variable-length.
The Parameter Value field contains the actual information to be The Parameter Value field contains the actual information to be
skipping to change at page 13, line 4 skipping to change at page 12, line 201
M2UA message header (Figure 4). M2UA message header (Figure 4).
3.3.1 MTP2 User Adaptation Messages 3.3.1 MTP2 User Adaptation Messages
3.3.1.1 Data 3.3.1.1 Data
The Data message contains an SS7 MTP2-User Protocol Data Unit (PDU). The The Data message contains an SS7 MTP2-User Protocol Data Unit (PDU). The
Data message contains the following parameter: Data message contains the following parameter:
Protocol Data (mandatory) Protocol Data (mandatory)
Correlation ID (optional)
The format for the Data Message parameters is as follows: The format for the Data Message parameters is as follows:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x312) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Correlation Id |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x300) | Length | | Tag (0x300) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
| Protocol Data | \ Protocol Data /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Protocol Data field contains the MTP2-User application message in The Protocol Data field contains the MTP2-User application message in
network byte order starting with the Signaling Information Octet (SIO). network byte order starting with the Signaling Information Octet (SIO).
The Correlation Id parameter uniquely identifies the MSU carried in the
Protocol Data within a Routing Context. This Correlation Id parameter
is assigned by the sending M3UA.
The format for a Data Message with TTC PDU parameters is as follows: The format for a Data Message with TTC PDU parameters is as follows:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x312) | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Correlation Id |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x301) | Length | | Tag (0x301) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ \
| Protocol Data | \ Protocol Data /
/ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Protocol Data field contains the MTP2-User application message in The Protocol Data field contains the MTP2-User application message in
network byte order starting with the Length Indicator (LI) octet. network byte order starting with the Length Indicator (LI) octet.
The Japanese TTC variant uses the spare bits of the LI octet for The Japanese TTC variant uses the spare bits of the LI octet for
priority. priority.
3.3.3 Data Acknowledge Message
The Data Acknowlege message contains the Correlation Id of the Data
message which the sending M2UA is acknowledging as successfully
processed to the peer M2UA. The Data Acknowlege message contains the
following parameter:
Correlation Id Ack Mandatory
The following format MUST be used for the Data Ack Message:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x313 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Correlation Id Ack |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Correlation Id Ack parameter acknowledges to the perr the receipt
and processing of the MSU to which the Correlation Id Ack parameter
corresponds.
3.3.1.2 Establish (Request, Confirmation) 3.3.1.2 Establish (Request, Confirmation)
The Establish Request message is used to establish the link or to The Establish Request message is used to establish the link or to
indicate that the channel has been established. The MGC controls the indicate that the channel has been established. The MGC controls the
state of the SS7 link. When the MGC desires the SS7 link to be state of the SS7 link. When the MGC desires the SS7 link to be
in-service, it will send the Establish Request message. Note that the in-service, it will send the Establish Request message. Note that the
gateway MAY already have the SS7 link established at its layer. If so, gateway MAY already have the SS7 link established at its layer. If so,
upon receipt of an Establish Request, the gateway takes no action except upon receipt of an Establish Request, the gateway takes no action except
to send an Establish Confirm. to send an Establish Confirm.
skipping to change at page 13, line 91 skipping to change at page 13, line 125
The valid values for State are shown in the following table. The valid values for State are shown in the following table.
Define Value Description Define Value Description
STATUS_LPO_SET 0x0 Request local processor outage STATUS_LPO_SET 0x0 Request local processor outage
STATUS_LPO_CLEAR 0x1 Request local processor outage STATUS_LPO_CLEAR 0x1 Request local processor outage
recovered recovered
STATUS_EMER_SET 0x2 Request emergency alignment STATUS_EMER_SET 0x2 Request emergency alignment
procedure procedure
STATUS_EMER_CLEAR 0x3 Request normal alignment (cancel STATUS_EMER_CLEAR 0x3 Request normal alignment (cancel
emergency) procedure emergency) procedure
STATUS_FLUSH_BUFFERS 0x4 Flush receive, transmit and retransmit STATUS_FLUSH_BUFFERS 0x4 Flush or clear receive, transmit and
queues retransmit queues
STATUS_CONTINUE 0x5 Continue STATUS_CONTINUE 0x5 Continue or Resume
STATUS_AUDIT 0x6 Audit state of link STATUS_CLEAR_RTB 0x6 Clear the retransmit queue
STATUS_CONG_CLEAR 0x7 Congestion cleared STATUS_AUDIT 0x7 Audit state of link
STATUS_CONG_ACCEPT 0x8 Congestion accept STATUS_CONG_CLEAR 0x8 Congestion cleared
STATUS_CONG_DISCARD 0x9 Congestion discard STATUS_CONG_ACCEPT 0x9 Congestion accept
STATUS_CONG_DISCARD 0xa Congestion discard
3.3.1.5 State Confirm 3.3.1.5 State Confirm
The State Confirm message will be sent by the SG in response to a State The State Confirm message will be sent by the SG in response to a State
Request from the MGC. The State Confirm reflects that state value Request from the MGC. The State Confirm reflects that state value
received in the State Request message. There is also a field to indicate received in the State Request message.
whether or not the the State Request was successfully completed.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x302) | Length | | Tag (0x302) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| State | | State |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x303) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Result |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The valid values for State are shown in the following table. The value The valid values for State are shown in the following table. The value
of the State field should reflect the value received in the State Request of the State field should reflect the value received in the State Request
message. message.
Define Value Description Define Value Description
STATUS_LPO_SET 0x0 Request local processor outage STATUS_LPO_SET 0x0 Request local processor outage
STATUS_LPO_CLEAR 0x1 Request local processor outage STATUS_LPO_CLEAR 0x1 Request local processor outage
recovered recovered
STATUS_EMER_SET 0x2 Request emergency alignment STATUS_EMER_SET 0x2 Request emergency alignment
procedure procedure
STATUS_EMER_CLEAR 0x3 Request normal alignment (cancel STATUS_EMER_CLEAR 0x3 Request normal alignment (cancel
emergency) procedure emergency) procedure
STATUS_FLUSH_BUFFERS 0x4 Flush receive, transmit and retransmit STATUS_FLUSH_BUFFERS 0x4 Flush or clear receive, transmit and
queues retransmit queues
STATUS_CONTINUE 0x5 Continue STATUS_CONTINUE 0x5 Continue or Resume
STATUS_AUDIT 0x6 Audit state of link STATUS_CLEAR_RTB 0x6 Clear the retransmit queue
STATUS_AUDIT 0x7 Audit state of link
The valid values for the Result field are shown in the following table. STATUS_CONG_CLEAR 0x8 Congestion cleared
STATUS_CONG_ACCEPT 0x9 Congestion accept
Define Value Description STATUS_CONG_DISCARD 0xa Congestion discard
STATUS_SUCCESS 0x0 Successfully completed Request
STATUS_FAILURE 0x1 Failed to complete Request
3.3.1.6 State Indication 3.3.1.6 State Indication
The MTP2 State Indication message can be sent from a gateway to an The MTP2 State Indication message can be sent from a gateway to an
ASP to indicate a condition on a link. ASP to indicate a condition on a link.
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 (0x304) | Length | | Tag (0x303) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Event | | Event |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The valid values for Event are shown in the following table. The valid values for Event are shown in the following table.
Define Value Description Define Value Description
EVENT_RPO_ENTER 0x1 Remote entered processor outage EVENT_RPO_ENTER 0x1 Remote entered processor outage
EVENT_RPO_EXIT 0x2 Remote exited processor outage EVENT_RPO_EXIT 0x2 Remote exited processor outage
EVENT_LPO_ENTER 0x3 Link entered processor outage
EVENT_LPO_EXIT 0x4 Link exited processor outage
3.3.1.7 Congestion Indication 3.3.1.7 Congestion Indication
The Congestion Indication message can be sent from a Signaling Gateway The Congestion Indication message can be sent from a Signaling Gateway
to an ASP to indicate the congestion status and discard status of a link. to an ASP to indicate the congestion status and discard status of a link.
When the MSU buffer fill increases above an Onset threshold or decreases When the MSU buffer fill increases above an Onset threshold or decreases
below an Abatement threshold or crosses a Discard threshold in either below an Abatement threshold or crosses a Discard threshold in either
direction, the SG SHALL send a congestion indication message. direction, the SG SHALL send a congestion indication message.
The SG shall send the message only when there is actually a change The SG shall send the message only when there is actually a change
skipping to change at page 14, line 85 skipping to change at page 14, line 81
[12] for more details). [12] for more details).
The Congestion Indication message contains the following parameters: The Congestion Indication message contains the following parameters:
Congestion Status (mandatory) Congestion Status (mandatory)
Discard Status (optional) Discard Status (optional)
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 (0x305) | Length | | Tag (0x304) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Congestion Status | | Congestion Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x306) | Length | | Tag (0x305) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Discard Status | | Discard Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The valid values for Congestion Status and Discard Status are shown in The valid values for Congestion Status and Discard Status are shown in
the following table. the following table.
Define Value Description Define Value Description
LEVEL_NONE 0x0 No congestion. LEVEL_NONE 0x0 No congestion.
LEVEL_1 0x1 Congestion Level 1 LEVEL_1 0x1 Congestion Level 1
LEVEL_2 0x2 Congestion Level 2 LEVEL_2 0x2 Congestion Level 2
LEVEL_3 0x3 Congestion Level 3 LEVEL_3 0x3 Congestion Level 3
LEVEL_4 0x4 Discarding LEVEL_4 0x4 Congestion Level 4 - Discarding
For networks that do not support multiple levels of congestion, only the For networks that do not support multiple levels of congestion, only the
LEVEL_NONE and LEVEL_3 values will be used. For networks that support LEVEL_NONE and LEVEL_3 values will be used. For networks that support
multiple levels of congestion, it is possible for all values to be used. multiple levels of congestion, it is possible for all values to be used.
Refer to [2] and [9] for more details. Refer to [2] and [9] for more details.
When the SG runs out of buffer space for MSUs received from the MGC, the When the SG runs out of buffer space for MSUs received from the MGC, the
SG shall send a Congestion Indication message with Congestion Status and SG MAY send a Congestion Indication message with Congestion Status and
Discard Status set to LEVEL_DISCARDING and discard MSUs received from the Discard Status set to LEVEL_4 and discard MSUs received from the MGC.
MGC.
3.3.1.8 Retrieval Request 3.3.1.8 Retrieval Request
The MTP2 Retrieval Request message is used during the MTP Level 3 The MTP2 Retrieval Request message is used during the MTP Level 3
changeover procedure to request the BSN, to retrieve PDUs from the changeover procedure to request the BSN, to retrieve PDUs from the
transmit and retransmit queues or to flush PDUs from the retransmit transmit and retransmit queues or to flush PDUs from the retransmit
queue. queue.
The Retrieval Request message contains the following parameters: The Retrieval Request message contains the following parameters:
Action (mandatory) Action (mandatory)
Sequence Number (optional) Sequence Number (optional)
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 (0x307) | Length | | Tag (0x306) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Action | | Action |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x308) | Length | | Tag (0x307) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number | | Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The valid values for Action are shown in the following table. The valid values for Action are shown in the following table.
Define Value Description Define Value Description
ACTION_RTRV_BSN 0x1 Retrieve the backward sequence number ACTION_RTRV_BSN 0x1 Retrieve the backward sequence number
ACTION_RTRV_MSGS 0x2 Retrieve the PDUs from the retransmit ACTION_RTRV_MSGS 0x2 Retrieve the PDUs from the transmit
queue and retransmit queues
ACTION_DROP_MSGS 0x3 Drop the PDUs in the retransmit queue
ACTION_RTRV_TRANS 0x4 Retrieve the PDUs from the transmit
queue
In the Retrieval Request message, the Sequence Number field SHOULD NOT In the Retrieval Request message, the Sequence Number field SHOULD NOT
be present if the Action field is ACTION_RTRV_BSN, ACTION_DROP_MSGS or be present if the Action field is ACTION_RTRV_BSN, ACTION_DROP_MSGS or
ACTION_RTRV_TRANS. The Sequence Number field contains the Forward ACTION_RTRV_TRANS. The Sequence Number field contains the Forward
Sequnce Number (FSN) of the far end if the Action is ACTION_RTRV_MSGS. Sequnce Number (FSN) of the far end if the Action is ACTION_RTRV_MSGS.
3.3.1.9 Retrieval Confirm 3.3.1.9 Retrieval Confirm
The MTP2 Retrieval Confirm message is sent by the Signaling Gateway The MTP2 Retrieval Confirm message is sent by the Signaling Gateway
in response to a Retrieval Request message. in response to a Retrieval Request message.
The Retrieval Confirm message contains the following parameters: The Retrieval Confirm message contains the following parameters:
Action (mandatory) Action (mandatory)
Result (mandatory) Result (mandatory)
Sequence Number (optional) Sequence Number (optional)
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x307) | Length | | Tag (0x306) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Action | | Action |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x309) | Length | | Tag (0x308) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Result | | Result |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x308) | Length | | Tag (0x307) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number | | Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The valid values for Action are the same as in Retrieval Request. The valid values for Action are the same as in Retrieval Request.
The values for Result are shown below: in the following table. The values for Result are shown below: in the following table.
Define Value Description Define Value Description
RESULT_SUCCESS 0x0 Action successful RESULT_SUCCESS 0x0 Action successful
skipping to change at page 15, line 58 skipping to change at page 15, line 58
PDU from the transmit or retransmit queue. The Retrieval Indication PDU from the transmit or retransmit queue. The Retrieval Indication
message does not contain the Action or seq_num fields, just a MTP3 message does not contain the Action or seq_num fields, just a MTP3
Protocol Data Unit (PDU) from the transmit or retransmit queue. Protocol Data Unit (PDU) from the transmit or retransmit queue.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x300) | Length | | Tag (0x300) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PDU from transmit or retransmit queue | | PDU |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
For TTC Data messages, the following parameter will be used to indicate For TTC Data messages, the following parameter will be used to indicate
a TTC PDU which starts at LI. a TTC PDU which starts at LI.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x301) | Length | | Tag (0x301) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TTC PDU from transmit or retransmit queue | | TTC PDU |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The M2UA implementation MAY consider the use of the bundling feature The M2UA implementation MAY consider the use of the bundling feature
of SCTP for Retrieval Indication messages. of SCTP for Retrieval Indication messages.
3.3.1.11 Retrieval Complete Indication 3.3.1.11 Retrieval Complete Indication
The MTP2 Retrieval Complete Indication message is exactly the same as The MTP2 Retrieval Complete Indication message is exactly the same as
the MTP2 Retrieval Indication message except that it also indicates that the MTP2 Retrieval Indication message except that it also indicates that
it contains the last PDU from the transmit or retransmit queue. it contains the last PDU from the transmit or retransmit queue.
3.3.2 Application Server Process Maintenance (ASPM) Messages 3.3.2 Application Server Process Maintenance (ASPM) Messages
The ASPM messages will only use the common message header. The ASPM messages will only use the common message header.
3.3.2.1 ASP UP (ASPUP) 3.3.2.1 ASP Up (ASPUP)
The ASP UP (ASPUP) message is used to indicate to a remote M2UA peer The ASP Up (ASPUP) message is used to indicate to a remote M2UA peer
that the Adaptation layer is ready to receive traffic or maintenance that the Adaptation layer is ready to receive traffic or maintenance
messages. messages.
The ASPUP message contains the following parameters The ASPUP message contains the following parameters
ASP Identifier (optional) ASP Identifier (optional)
Info String (optional) Info String (optional)
The format for ASPUP Message parameters is as follows: The format for ASPUP Message parameters is as follows:
skipping to change at page 16, line 27 skipping to change at page 16, line 27
| ASP Identifier* | | ASP Identifier* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length | | Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| INFO String* | | INFO String* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The optional ASP Identifier parameter would contain a unique value The optional ASP Identifier parameter would contain a unique value
that is locally significant to the ASPs that support an AS. The SG that is locally significant among the ASPs that support an AS. The
would save the ASP Identifier to be used, if necessary, with the SG should save the ASP Identifier to be used, if necessary, with the
Notify message (see Section 3.3.3.2). Notify message (see Section 3.3.3.2).
The optional INFO String parameter can carry any meaningful 8-bit ASCII The optional INFO String parameter can carry any meaningful 8-bit ASCII
character string along with the message. Length of the INFO String character string along with the message. Length of the INFO String
parameter is from 0 to 255 characters. No procedures are presently parameter is from 0 to 255 characters. No procedures are presently
identified for its use but the INFO String MAY be used for debugging identified for its use but the INFO String MAY be used for debugging
purposes. purposes.
3.3.2.2 ASP Up Ack 3.3.2.2 ASP Up Ack
The ASP UP Ack message is used to acknowledge an ASP Up message received The ASP Up Ack message is used to acknowledge an ASP Up message received
from a remote M2UA peer. from a remote M2UA peer.
The ASPUP Ack message contains the following parameters: The ASPUP Ack message contains the following parameters:
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
skipping to change at page 17, line 61 skipping to change at page 17, line 61
| INFO String* | | INFO String* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format and description of the optional Info String parameter is the The format and description of the optional Info String parameter is the
same as for the ASP Up message (See Section 3.3.2.1). same as for the ASP Up message (See Section 3.3.2.1).
The Reason parameter indicates the reason that the remote M2UA The Reason parameter indicates the reason that the remote M2UA
adaptation layer is unavailable. The valid values for Reason are shown adaptation layer is unavailable. The valid values for Reason are shown
in the following table. in the following table:
Value Description Value Description
0x1 Management 0x1 Management
3.3.2.4 ASP Down Ack 3.3.2.4 ASP Down Ack
The ASP Down Ack message is used to acknowledge an ASP Down message The ASP Down Ack message is used to acknowledge an ASP Down message
received from a remote M2UA peer. received from a remote M2UA peer.
The ASP Down Ack message contains the following parameters: The ASP Down Ack message contains the following parameters:
skipping to change at page 19, line ? skipping to change at page 19, line ?
An SG that receives an ASPAC with an incorrect or unsupported Traffic An SG that receives an ASPAC with an incorrect or unsupported Traffic
Mode Type for a particular Interface Identifier will respond with an Mode Type for a particular Interface Identifier will respond with an
Error Message (Cause: Unsupported Traffic Handling Mode). Error Message (Cause: Unsupported Traffic Handling Mode).
The format and description of the optional Info String parameter is the The format and description of the optional Info String parameter is the
same as for the ASP UP message (See Section 3.3.2.1). same as for the ASP UP message (See Section 3.3.2.1).
3.3.2.6 ASP Active Ack 3.3.2.6 ASP Active Ack
The ASPAC Ack message is used to acknowledge an ASP-Active message The ASP Active (ASPAC) Ack message is used to acknowledge an ASP Active
received from a remote M2UA peer. message received from a remote M2UA peer.
The ASPAC Ack message contains the following parameters: The ASPAC Ack message contains the following parameters:
Traffic Mode Type (mandatory) Traffic Mode Type (mandatory)
Interface Identifier (optional) Interface Identifier (optional)
- Combination of integer and integer ranges, OR - Combination of integer and integer ranges, OR
- string (text formatted) - string (text formatted)
INFO String (optional) INFO String (optional)
The format for the ASPAC Ack message with Integer-formatted Interface The format for the ASPAC Ack message with Integer-formatted Interface
skipping to change at page 19, line ? skipping to change at page 19, line ?
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format and description of the optional Info String parameter is the The format and description of the optional Info String parameter is the
same as for the ASP UP message (See Section 3.3.2.1.) same as for the ASP UP message (See Section 3.3.2.1.)
The format of the Type and Interface Identifier parameters is the same The format of the Type and Interface Identifier parameters is the same
as for the ASP Active message (See Section 3.3.2.5). as for the ASP Active message (See Section 3.3.2.5).
3.3.2.7 ASP Inactive (ASPIA) 3.3.2.7 ASP Inactive (ASPIA)
The ASPIA message is sent by an ASP to indicate to an SG that it is no The ASP Inactive (ASPIA) message is sent by an ASP to indicate to an SG
longer an active ASP to be used from within a list of ASPs. The SG will that it is no longer an active ASP to be used from within a list of ASPs.
respond with an ASPIA Ack message and either discard incoming messages The SG will respond with an ASPIA Ack message and either discard incoming
or buffer for a timed period and then discard. messages or buffer for a timed period and then discard.
The ASPIA message contains the following parameters The ASPIA message contains the following parameters:
Traffic Mode Type (mandatory)
Interface Identifiers (optional) Interface Identifiers (optional)
- Combination of integer and integer ranges, OR - Combination of integer and integer ranges, OR
- string (text formatted) - string (text formatted)
INFO String (optional) INFO String (optional)
The format for the ASP Inactive message parameters using Integer The format for the ASP Inactive message parameters using Integer
formatted Interface Identifiers is as follows: formatted Interface Identifiers is as follows:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0xb) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Traffic Mode Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x1=integer) | Length | | Tag (0x1=integer) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifiers* | | Interface Identifiers* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x8=integer range) | Length | | Tag (0x8=integer range) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Start1* | | Interface Identifier Start1* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 19, line ? skipping to change at page 19, line ?
| INFO String* | | INFO String* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format for the ASP Inactive message using text formatted (string) The format for the ASP Inactive message using text formatted (string)
Interface Identifiers is as follows: Interface Identifiers is as follows:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0xb) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Traffic Mode Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x3=string) | Length | | Tag (0x3=string) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier* | | Interface Identifier* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Additional Interface Identifiers | | Additional Interface Identifiers |
| of Tag Type 0x3 | | of Tag Type 0x3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length | | Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| INFO String* | | INFO String* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Traffic Mode Type parameter identifies the traffic mode of
operation of the ASP within an AS. The valid values for Traffic Mode
Type are shown in the following table:
Value Description
0x1 Over-ride
The format and description of the optional Interface Identifiers and The format and description of the optional Interface Identifiers and
Info String parameters is the same as for the ASP Active message (See Info String parameters is the same as for the ASP Active message (See
Section 3.3.2.3.) Section 3.3.2.3).
The optional Interface Identifiers parameter contains a list of The optional Interface Identifiers parameter contains a list of
Interface Identifier integers indexing the Application Server traffic Interface Identifier integers indexing the Application Server traffic
that the sending ASP is configured/registered to receive, but does not that the sending ASP is configured/registered to receive, but does not
want to receive at this time. want to receive at this time.
3.3.2.8 ASP Inactive Ack 3.3.2.8 ASP Inactive Ack
The ASPIA Ack message is used to acknowledge an ASP-Inactive message The ASP Inactive (ASPIA) Ack message is used to acknowledge an ASP Inactive
received from a remote M2UA peer. message received from a remote M2UA peer.
The ASPIA Ack message contains the following parameters: The ASPIA Ack message contains the following parameters:
Traffic Mode Type (mandatory)
Interface Identifiers (optional) Interface Identifiers (optional)
- Combination of integer and integer ranges, OR - Combination of integer and integer ranges, OR
- string (text formatted) - string (text formatted)
INFO String (optional) INFO String (optional)
The format for the ASPIA Ack message is as follows: The format for the ASPIA Ack message is as follows:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0xb) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Traffic Mode Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x1=integer) | Length | | Tag (0x1=integer) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifiers* | | Interface Identifiers* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x8=integer range) | Length | | Tag (0x8=integer range) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier Start1* | | Interface Identifier Start1* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 19, line ? skipping to change at page 19, line ?
| INFO String* | | INFO String* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format for the ASP Inactive Ack message using text formatted The format for the ASP Inactive Ack message using text formatted
(string) Interface Identifiers is as follows: (string) Interface Identifiers is as follows:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0xb) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Traffic Mode Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x3=string) | Length | | Tag (0x3=string) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier* | | Interface Identifier* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Additional Interface Identifiers | | Additional Interface Identifiers |
| of Tag Type 0x3 | | of Tag Type 0x3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag (0x4) | Length | | Tag (0x4) | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| INFO String* | | INFO String* |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The format of the Traffic Mode Type and Interface Identifier The format of the Interface Identifier parameter is the same as for the
parameters is the same as for the ASP Inactive message ASP Inactive message (See Section 3.3.2.7).
(See Section 3.3.2.7).
The format and description of the optional Info String parameter is The format and description of the optional Info String parameter is
the same as for the ASP Up message (See Section 3.3.2.1). the same as for the ASP Up message (See Section 3.3.2.1).
3.3.3 Layer Management (MGMT) Messages 3.3.3 Layer Management (MGMT) Messages
3.3.3.1 Error (ERR) 3.3.3.1 Error (ERR)
The Error message is used to notify a peer of an error event The Error (ERR) message is used to notify a peer of an error event
associated with an incoming message. For example, the message type associated with an incoming message. For example, the message type
might be unexpected given the current state, or a parameter value might might be unexpected given the current state, or a parameter value might
be invalid. be invalid.
The ERR message contains the following parameters: The ERR message contains the following parameters:
Error Code (mandatory) Error Code (mandatory)
Diagnostic Information (optional) Diagnostic Information (optional)
The format for the ERR message is as follows: The format for the ERR message is as follows:
skipping to change at page 19, line ? skipping to change at page 19, line ?
Invalid Version 0x1 Invalid Version 0x1
Invalid Interface Identifier 0x2 Invalid Interface Identifier 0x2
Unsupported Message Class 0x3 Unsupported Message Class 0x3
Unsupported Message Type 0x4 Unsupported Message Type 0x4
Unsupported Traffic Handling Mode 0x5 Unsupported Traffic Handling Mode 0x5
Unexpected Message 0x6 Unexpected Message 0x6
Protocol Error 0x7 Protocol Error 0x7
Unsupported Interface Identifier Type 0x8 Unsupported Interface Identifier Type 0x8
Invalid Stream Identifier 0x9 Invalid Stream Identifier 0x9
Invalid Parameter Value 0xa
Refused - Management Blocking 0xb
The "Invalid Version" error would be sent if a message was The "Invalid Version" error would be sent if a message was
received with an invalid or unsupported version. The Error message received with an invalid or unsupported version. The Error message
would contain the supported version in the Common header. The would contain the supported version in the Common header. The
Error message could optionally provide the supported version in Error message could optionally provide the supported version in
the Diagnostic Information area. the Diagnostic Information area.
The "Invalid Interface Identifier" error would be sent by a SG if The "Invalid Interface Identifier" error would be sent by a SG if
an ASP sends a message with an invalid (unconfigured) Interface an ASP sends a message with an invalid (unconfigured) Interface
Identifier value. Identifier value.
skipping to change at page 19, line ? skipping to change at page 19, line ?
The "Unsupported Message Class" error would be sent if a message with The "Unsupported Message Class" error would be sent if a message with
an unexpected or unsupported Message Class is received. an unexpected or unsupported Message Class is received.
The "Unsupported Interface Identifier Type" error would be sent by The "Unsupported Interface Identifier Type" error would be sent by
a SG if an ASP sends a Text formatted Interface Identifier and the a SG if an ASP sends a Text formatted Interface Identifier and the
SG only supports Integer formatted Interface Identifiers. When SG only supports Integer formatted Interface Identifiers. When
the ASP receives this error, it will need to resend its message with the ASP receives this error, it will need to resend its message with
an Integer formatted Interface Identifier. an Integer formatted Interface Identifier.
The "Invalid Parameter Value" error is sent if a message is received
with an invalid parameter value.
The "Refused - Management Blocking" error is sent when an ASP Up or
ASP Active message is received and the request is refused for
management reasons (e.g., management lock-out").
The optional Diagnostic information can be any information germain to The optional Diagnostic information can be any information germain to
the error condition, to assist in identification of the error condition. the error condition, to assist in identification of the error condition.
In the case of an Invalid Version Error Code the Diagnostic information In the case of an Invalid Version Error Code the Diagnostic information
includes the supported Version parameter. In the other cases, the includes the supported Version parameter. In the other cases, the
Diagnostic information MAY be the first 40 bytes of the offending message. Diagnostic information MAY be the first 40 bytes of the offending message.
3.3.3.2 Notify (NTFY) 3.3.3.2 Notify (NTFY)
The Notify message is used to provide an autonomous indication of M2UA The Notify message is used to provide an autonomous indication of M2UA
events to an M2UA peer. events to an M2UA peer.
skipping to change at page 20, line 131 skipping to change at page 20, line 131
If the Status Type is Other, then the following Status Information values If the Status Type is Other, then the following Status Information values
are defined: are defined:
Value Description Value Description
1 Insufficient ASP resources active in AS 1 Insufficient ASP resources active in AS
2 Alternate ASP Active 2 Alternate ASP Active
3 ASP Failure 3 ASP Failure
In the Insufficent ASP Resources case, the SG is indicating to an In the Insufficent ASP Resources case, the SG is indicating to an
"Inactive" ASP(s) in the AS that another ASP is required in order to ASP-INACTIVE ASP(s) in the AS that another ASP is required in order to
handle the load of the AS (Load-sharing mode). For the Alternate ASP handle the load of the AS (Load-sharing mode). For the Alternate ASP
Active case, the formerly Active ASP is informed when an alternate Active case, the formerly Active ASP is informed when an alternate
ASP transitions to the ASP-Active state in Over-ride mode. The ASP ASP transitions to the ASP Active state in Over-ride mode. The ASP
ID (if available) of the Alternate ASP MUST be placed in the message. ID (if available) of the Alternate ASP MUST be placed in the message.
For the ASP Failure case, the SG is indicating to ASP(s) in the AS For the ASP Failure case, the SG is indicating to ASP(s) in the AS
that one of the ASPs has failed (i.e. the ASP Transition to Down due that one of the ASPs has failed (i.e. the ASP Transition to Down due
to SCTP Communication Down Indication). The ASP ID (if available) of to SCTP Communication Down Indication). The ASP ID (if available) of
the failed ASP MUST be placed in the message. the failed ASP MUST be placed in the message.
For each of the Status Information values in Status Type Other, the For each of the Status Information values in Status Type Other, the
Interface Identifiers of the affected AS MAY be placed in the message Interface Identifiers of the affected AS MAY be placed in the message
if desired. if desired.
The format and description of the optional Interface Identifiers and The format and description of the optional Interface Identifiers and
Info String parameters is the same as for the ASP Active message Info String parameters is the same as for the ASP Active message
(See Section 3.3.2.3). (See Section 3.3.2.3).
3.3.4 Interface Identifier Management (IIM) Messages
The Interface Identifier Managmement messages are optional. They are
used to support automatic allocation of Signaling Terminals or
Signaling Data Links [2][3].
3.3.4.1 Registration Request (REG REQ)
The REG REQ message is sent by an ASP to indicate to a remote M2UA
peer that it wishes to register one or more given Link Keys with the
remote peer. Typically, an ASP would send this message to an SGP,
and expectes to receive a REG RSP in return with an associated
Interface Identifier value.
The REG REQ message contains the following parameter:
Link Key (mandatory)
The format for the REG REQ message is as follows
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x030a | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ Link Key 1 /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ ... /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x030a | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ Link Key n /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Link Key: fixed length
The Link Key parameter is mandatory. The sender of this message
expects the receiver of this message will create a Link Key entry
and assign a unique Interface Identifier value to it, if the Link
Key entry does not yet exist.
The Link Key parameter may be present multiple times in the same
message. This is used to allow the registration of multiple Link
Keys in a single message.
The format of the Link Key parameter is as follows:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local-LK-Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Signalling Data Terminal Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Signalling Data Link Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Local-LK-Identifier: 32-bit integer
The mandatory Local-LK-Identifier field is used to uniquely
(between ASP and SG) identify the registration request. The
Identifier value is assigned by the ASP, and is used to correlate
the response in a REG RSP message with the original registration
request. The Identifier value must remain unique until the REG
RSP is received.
The format of the Local-LK-Identifier field is as follows:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x030b | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local-LK-Identifier value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Signalling Data Terminal Identifier
The Signalling Data Terminal Identifier parameter is mandatory.
It identifies the Signalling Data Terminal associated with the
SS7 link for which the ASP is registering. The format is as
follows:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x030c | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | SDT Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The SDT Identifier is a 32-bit unsigned value which may only be
significant to 12 or 14 bits depending on the SS7 variant which
is supported by the MTP Level 3 at the ASP. Insignificant SDTI
bits are coded 0.
Signalling Data Link Identifier
The Signalling Data Link Identifier parameter is mandatory. It
identifies the Siganlling Data Link Identifier associated with
the SS7 link for which the ASP is registering. The format is as
follows:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x030d | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | SDL Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The SDL Identifier is a 32-bit unsigned value which may only be
significant to 12 or 14 bits depending on the SS7 variant which
is supported by the MTP Level 3 at the ASP. Insignificant SDLI
bits are coded 0.
3.3.4.2 Registration Response (REG RSP)
The REG RSP message is used as a response to the REG REQ message
from a remote M2UA peer. It contains indications of success/failure
for registration requests and returns a unique Interface Identifier
value for successful registration requests, to be used in subsequent
M2UA Traffic Management protocol.
The REG RSP message contains the following parameter:
Registration Results (mandatory)
The format for the REG RSP message is as follows:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x030e | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ Registration Result 1 /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ ... /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x030e | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ Registration Result n /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Registration Results: fixed length
The Registration Results parameter contains one or more results,
each containing the registration status for a single Link Key in
the REG REQ message. The number of results in a single REG RSP
message MAY match the number of Link Key parameters found in the
corresponding REG REQ message. The format of each result is as
follows:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local-LK-Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Registration Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Local-LK-Identifier: 32-bit integer
The Local-LK-Identifier contains the same value as found in the
matching Link Key parameter found in the REG REQ message. The
format of the Local-LK-Identifier is shown in Section 3.3.4.1.
Registration Status: 32-bit integer
The Registration Result Status field indicates the success or the
reason for failure of a registration request.
Its values may be one of the following:
0 Successfully Registered
1 Error - Unknown
2 Error - Invalid SDLI
3 Error - Invalid SDTI
4 Error - Invalid Link Key
5 Error - Permission Denied
6 Error - Overlapping (Non-unique) Link Key
7 Error - Link Key not Provisioned
8 Error - Insufficient Resources
The format of the Registration Status field is as follows:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x030f | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Registration Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Interface Identifier: 32-bit integer
The Interface Identifier field contains the Interface Identifier
for the associated Link Key if the registration is successful.
It is set to "0" if the registration was not successful. The
format of integer-based and text-based Interface Identifier
parameters are shown in Section 3.2.
3.3.4.3 De-Registration Request (DEREG REQ)
The DEREG REQ message is sent by an ASP to indicate to a remote M2UA
peer that it wishes to de-register a given Interface Identifier.
Typically, an ASP would send this message to an SGP, and expects to
receive a DEREG RSP in return reflecting the Interface Identifier
and containing a de-registration status.
The DEREG REQ message contains the following parameter:
Interface Identifier (mandatory)
The format for the DEREG REQ message is as follows:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x1 or 0x3 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ Interface Identifer 1 /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ ... /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x1 or 0x3 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ Interface Identifier n /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Interface Identifier
The Interface Identifier parameter contains a Interface Identifier
indexing the Application Server traffic that the sending ASP is
currently registered to receive from the SG but now wishes to
deregister. The format of integer-based and text-based Interface
Identifier parameters are shown in Section 3.2.
3.3.4.4 De-Registration Response (DEREG RSP)
The DEREG RSP message is used as a response to the DEREG REQ message
from a remote M2UA peer.
The DEREG RSP message contains the following parameter:
De-Registration Results (mandatory)
The format for the DEREG RSP message is as follows:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0310 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ De-Registration Result 1 /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ ... /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0310 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
\ \
/ De-Registration Result n /
\ \
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
De-Registration Results: fixed length
The De-Registration Results parameter contains one or more results,
each containing the de-registration status for a single Interface
Identifier in the DEREG REQ message. The number of results in a
single DEREG RSP message MAY match the number of Interface Identifer
parameters found in the corresponding DEREG REQ message. The format
of each result is as follows:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| De-Registration Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Interface Identifier: 32-bit integer
The Interface Identifier field contains the Interface Identifier
value of the matching Link Key to deregister, as found in the
DEREG REQ. The format of integer-based and text-based Interface
Identifier parameters are shown in Section 3.2.
De-Registration Status: 32-bit integer
The De-Registration Result Status field indicates the success or
the reason for failure of the de-registration.
Its values may be one of the following:
0 Successfully De-registered
1 Error - Unknown
2 Error - Invalid Interface Identifier
3 Error - Permission Denied
4 Error - Not Registered
The format of the De-Registration Status field is as follows:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tag = 0x0311 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| De-Registration Status |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
4.0 Procedures 4.0 Procedures
The M2UA layer needs to respond to various primitives it receives from The M2UA layer needs to respond to various primitives it receives from
other layers as well as messages it receives from the peer-to-peer other layers as well as messages it receives from the peer-to-peer
messages. This section describes various procedures involved in messages. This section describes various procedures involved in
response to these events. response to these events.
4.1 Procedures to Support Service in Section 1.4.1 4.1 Procedures to Support Service in Section 1.4.1
These procedures achieve the M2UA layer's "Transport of MTP Level 2 / These procedures achieve the M2UA layer's "Transport of MTP Level 2 /
skipping to change at page 22, line 16 skipping to change at page 22, line 16
These procedures achieve the M2UA layer's "Support for Communication These procedures achieve the M2UA layer's "Support for Communication
between Layer Managements" service. between Layer Managements" service.
4.2.1 Layer Management Primitives Procedure 4.2.1 Layer Management Primitives Procedure
On receiving primitives from the local Layer Management, the M2UA layer On receiving primitives from the local Layer Management, the M2UA layer
will take the requested action and provide an appropriate response will take the requested action and provide an appropriate response
primitive to Layer Management. primitive to Layer Management.
An M-SCTP ESTABLISH request from Layer Management will initiate the An M-SCTP_ESTABLISH request primitive from Layer Management at an ASP
establishment of an SCTP association. An M-SCTP ESTABLISH confirm or IPSP will initiate the establishment of an SCTP association. The
will be sent to Layer Management when the initiated association set-up M2UA layer will attempt to establish an SCTP association with the
is complete. An M-SCTP ESTABLISH indication is sent to Layer remote M2UA peer by sending an SCTP-ASSOCIATE primitive to the local
SCTP layer.
When an SCTP association has been successfully established, the SCTP
will send an SCTP-COMMUNICATION_UP notification primitive to the local
M2UA layer. At the SGP or IPSP that initiated the request, the M2UA
layer will send an M-SCTP_ESTABLISH confirm primitive to Layer
Management when the association set-up is complete. At the peer M2UA
layer, an M-SCTP_ESTABLISH indication primitive is sent to Layer
Management upon successful completion of an incoming SCTP association Management upon successful completion of an incoming SCTP association
set-up from a peer M2UA node set-up.
An M-SCTP RELEASE request from Layer Management will initiate the An M-SCTP_RELEASE request primitive from Layer Management initates the
tear-down of an SCTP association. An M-SCTP RELEASE confirm will tear-down of an SCTP association. The M2UA layer accomplishes a
be sent by Layer Management when the association teardown is complete. graceful shutdown of the SCTP association by sending an SCTP-SHUTDOWN
An M-SCTP RELEASE indication is sent to Layer Management upon primitive to the SCTP layer.
successful tear-down of an SCTP association initiated by a peer M2UA.
M-SCTP STATUS request and indication support a Layer Management When the graceful shutdown of the SCTP association has been
query of the local status of a particular SCTP association. accomplished, the SCTP layer returns an SCTP-SHUTDOWN_COMPLETE
notification primitive to the local M2UA layer. At the M2UA Layer that
initiated the request, the M2UA layer will send an M-SCTP_RELEASE
confirm primitive to Layer Management when the association teardown is
complete. At the peer M2UA Layer, an M-SCTP_RELEASE indication
primitive is sent to Layer Management upon successful tear-down of an
SCTP association.
An M-SCTP_STATUS request primitive supports a Layer Management query of
the local status of a particular SCTP association. The M2UA layer
simply maps the M-SCTP_STATUS request primitive to an SCTP-STATUS
primitive to the SCTP layer. When the SCTP responds, the M2UA layer
maps the association status information to an M-SCTP_STATUS confirm
primitive. No peer protocol is invoked.
M-NOTIFY indication and M-ERROR indication indicate to Layer M-NOTIFY indication and M-ERROR indication indicate to Layer
Management the notification or error information contained in a Management the notification or error information contained in a
received M2UA Notify or Error message respectively. These indications received M2UA Notify or Error message respectively. These indications
can also be generated based on local M2UA events. can also be generated based on local M2UA events.
M-ASP STATUS request/indication and M-AS-STATUS request/indication An M-ASP_STATUS request primitive supports a Layer Management query of
support a Layer Management query of the local status of a particular the status of a particular local or remote ASP. The M2UA layer
ASP or AS. No M2UA peer protocol is invoked. responds with the status in an M-ASP_STATUS confirm primitive. No M2UA
peer protocol is invoked.
M-ASP Up request, M-ASP Down request, M-ASP-INACTIVE request and An M-AS_STATUS request supports a Layer Management query of the status
M-ASP-ACTIVE request allow Layer Management at an ASP to initiate of a particular AS. The M2UA responds with an M-AS_STATUS confirm
state changes. These requests result in outgoing M2UA ASP UP, primitive. No M2UA peer protocol is invoked.
ASP DOWN, ASP INACTIVE and ASP ACTIVE messages.
M-ASP Up confirmation, M-ASP Down confirmation, M-ASP-INACTIVE M-ASP_UP request, M-ASP_DOWN request, M-ASP_ACTIVE request and M-ASP_
confirmation and M-ASP-ACTIVE confirmation indicate to Layer INACTIVE request primitives allow Layer Management at an ASP to
Management that the previous request has been confirmed. initiate state changes. Upon successful completion, a corresponding
confirm primitive is provided by the M2UA layer to Layer Management.
If an invocation is unsuccessful, an Error indication primitive is
provided in the primitive. These requests result in outgoing ASP Up,
ASP Down, ASP Active and ASP Inactive messages to the remote M2UA peer
at an SGP or IPSP.
All MGMT messages are sent on a sequenced stream to ensure ordering. All MGMT messages are sent on a sequenced stream to ensure ordering.
SCTP stream '0' SHOULD be used. SCTP stream '0' SHOULD be used.
4.2.2 MGMT message procedures 4.2.2 MGMT message procedures
Upon receipt of MGMT messages the M2UA layer MUST invoke the corresponding Upon successful state changes resulting from reception of ASP Up,
Layer Management primitives indications (e.g., M-AS Status ind., M-ASP ASP Down, ASP Active and ASP Inactive messages from a peer M2UA, the
Status ind., M-ERROR ind...) to the local layer management. M2UA layer SHOULD invoke corresponding M-ASP_UP, M-ASP_DOWN, M-
ASP_ACTIVE and M-ASP_INACTIVE, M-AS_ACTIVE, M-AS_INACTIVE, and M-
AS_DOWN indication primitives to the local Layer Management.
M-NOTIFY indication and M-ERROR indication indicate to Layer Management M-NOTIFY indication and M-ERROR indication indicate to Layer Management
the notification or error information contained in a received M2UA the notification or error information contained in a received M2UA
Notify or Error message. These indications can also be generated Notify or Error message. These indications can also be generated
based on local M2UA events. based on local M2UA events.
All MGMT messages are sent on a sequenced stream to ensure ordering. All MGMT messages are sent on a sequenced stream to ensure ordering.
SCTP stream '0' SHOULD be used. SCTP stream '0' SHOULD be used.
4.3 Procedures to Support Service in Section 1.4.3 4.3 Procedures to Support Service in Section 1.4.3
skipping to change at page 22, line 104 skipping to change at page 22, line 131
ASP-INACTIVE: The remote M2UA peer at the ASP is available (and the ASP-INACTIVE: The remote M2UA peer at the ASP is available (and the
related SCTP association is up) but application traffic is stopped. related SCTP association is up) but application traffic is stopped.
In this state the ASP can be sent any non-MAUP M2UA messages. In this state the ASP can be sent any non-MAUP M2UA messages.
ASP-ACTIVE: The remote M2UA peer at the ASP is available and ASP-ACTIVE: The remote M2UA peer at the ASP is available and
application traffic is active. application traffic is active.
Figure 6 ASP State Transition Diagram Figure 6 ASP State Transition Diagram
+-------------+ +----------------+
+----------------------| | +----------------------| |
| Alternate +-------| ASP-ACTIVE | | Alternate +-------| ASP-ACTIVE |
| ASP | +-------------+ | ASP | | |
| Takeover | ^ | | Takeover | +----------------+
| | ^ |
| | ASP | | ASP | | ASP | | ASP
| | Active | | Inactive | | Active | | Inactive
| | | v | | | v
| | +-------------+ | | +----------------+
| | | | | | | |
| +------>| ASP-INACT | | +------>| ASP-INACTIVE |
| +-------------+ | | |
| +----------------+
| ^ | | ^ |
ASP Down/ | ASP | | ASP Down / ASP Down/ | ASP | | ASP Down /
SCTP CDI | Up | | SCTP CDI SCTP CDI/ | Up | | SCTP CDI /
| | v SCTP RI | | v SCTP RI
| +-------------+ | +----------------+
+--------------------->| | +--------------------->| |
| ASP Down | | ASP-DOWN |
+-------------+ | |
+----------------+
SCTP CDI: The local SCTP layer's Communication Down Indication to the SCTP CDI: The local SCTP layer's Communication Down Indication to the
Upper Layer Protocol (M2UA) on an SG. The local SCTP will send this Upper Layer Protocol (M2UA) on an SG. The local SCTP will send this
indication when it detects the loss of connectivity to the ASP's peer indication when it detects the loss of connectivity to the ASP's peer
SCTP layer. SCTP CDI is understood as either a SHUTDOWN COMPLETE SCTP layer. SCTP CDI is understood as either a SHUTDOWN COMPLETE
notification and COMMUNICATION LOST notification from the SCTP. notification and COMMUNICATION LOST notification from the SCTP.
SCTP RI: The local SCTP layer's Restart Indication to the Upper
Layer Protocol (M2UA) on an SG. The local SCTP will send this
indication when it detects a restart from the ASP's peer SCTP layer.
When an SCTP association fails at the SG, M2UA shall change the states When an SCTP association fails at the SG, M2UA shall change the states
of all ASPs reached through the aborted SCTP association to ASP-DOWN. of all ASPs reached through the aborted SCTP association to ASP-DOWN.
4.3.1.2 AS States 4.3.1.2 AS States
The state of the AS is maintained in the M2UA layer on the SG. The state of the AS is maintained in the M2UA layer on the SG.
The state of an AS changes due to events. These events include the The state of an AS changes due to events. These events include the
following: following:
skipping to change at page 23, line 24 skipping to change at page 23, line 24
The possible states of an AS are the following: The possible states of an AS are the following:
AS-DOWN: The Application Server is unavailable. This state implies AS-DOWN: The Application Server is unavailable. This state implies
that all related ASPs are in the ASP Down state for this AS. When that all related ASPs are in the ASP Down state for this AS. When
the AS transitions to the AS-DOWN state, all of the SS7 links (Interface the AS transitions to the AS-DOWN state, all of the SS7 links (Interface
Identifiers) for this AS should be taken out-of-service. Initially the Identifiers) for this AS should be taken out-of-service. Initially the
AS will be in this state. AS will be in this state.
AS-INACTIVE: The Application Server is available but no application AS-INACTIVE: The Application Server is available but no application
traffic is active (i.e., one or more related ASPs are in the ASP-Inactive traffic is active (i.e., one or more related ASPs are in the ASP-INACTIVE
state, but none in the ASP-Active state). state, but none in the ASP-ACTIVE state).
AS-ACTIVE: The Application Server is available and application traffic AS-ACTIVE: The Application Server is available and application traffic
is active. This state implies that one ASP is in the ASP-ACTIVE state. is active. This state implies that one ASP is in the ASP-ACTIVE state.
AS-PENDING: An active ASP has transitioned from active to inactive or AS-PENDING: An active ASP has transitioned from active to inactive or
down and it was the last remaining active ASP in the AS. A recovery down and it was the last remaining active ASP in the AS. A recovery
timer T(r) will be started and all incoming SCN messages will be timer T(r) will be started and all incoming SCN messages will be
queued by the SG. If an ASP becomes active before T(r) expires, the queued by the SG. If an ASP becomes active before T(r) expires, the
AS will move to AS-ACTIVE state and all the queued messages will be AS will move to AS-ACTIVE state and all the queued messages will be
sent to the active ASP. sent to the active ASP.
If T(r) expires before an ASP becomes active, the SG stops queueing If T(r) expires before an ASP becomes active, the SG stops queueing
messages and discards all previously queued messages. In addition, messages and discards all previously queued messages. In addition,
the SG SHALL send the Stop primitive to MTP2 to take the link out of the SG MAY send the Stop primitive to MTP2 to take the link out of
service. The AS will move to AS-Inactive if at least one ASP is in service. Note that the actions taken by the SG should be accordance
ASP-Inactive state, otherwise it will move to AS-DOWN state. with the appropriate MTP specifications. The AS will move to AS-Inactive
if at least one ASP is in ASP-INACTIVE state, otherwise it will move to
AS-DOWN state.
If an ASP transitions to the ASP-DOWN state and all ASPs in the AS are If an ASP transitions to the ASP-DOWN state and all ASPs in the AS are
in the ASP-DOWN state, then the SG SHALL send the Stop primitive to MTP2 in the ASP-DOWN state, then the SG SHALL send the Stop primitive to MTP2
to take the link out of service and moves the AS to the AS-DOWN state. to take the link out of service and moves the AS to the AS-DOWN state.
Figure 7 AS State Transition Diagram Figure 7 AS State Transition Diagram
+----------+ one ASP trans ACTIVE +-------------+ +----------+ one ASP trans ACTIVE +-------------+
| |------------------------>| | | |------------------------>| |
| AS-INACT | | AS-ACTIVE | | AS-INACT | | AS-ACTIVE |
skipping to change at page 24, line 8 skipping to change at page 24, line 8
| | | (queueing) | | | | (queueing) |
| |<------------------------| | | |<------------------------| |
+----------+ Tr Expiry and no +-------------+ +----------+ Tr Expiry and no +-------------+
ASP in INACTIVE state ASP in INACTIVE state
Tr = Recovery Timer Tr = Recovery Timer
4.3.2 ASPM procedures for primitives 4.3.2 ASPM 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 in the state ASP-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 M2UA layer at an ASP receives an M-SCTP association to an SG, the M2UA layer at an ASP receives an M-SCTP
ESTABLISH request primitive from the Layer Management, the M2UA layer ESTABLISH request primitive from the Layer Management, the M2UA layer
will try to establish an SCTP association with the remote M2UA peer at will try to establish an SCTP association with the remote M2UA 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 M2UA layer will invoke the primitive primitive from the SCTP, the M2UA layer will invoke the primitive
M-SCTP ESTABLISH confirm to the Layer Management. M-SCTP_ESTABLISH confirm to the Layer Management.
At the SG, the M2UA layer will receive an SCTP Communication Up At the SG, the M2UA layer will receive an SCTP-COMMUNICATION_UP
indication primitive from the SCTP. The M2UA layer will then invoke indication primitive from the SCTP. The M2UA layer will then invoke
the primitive M-SCTP ESTABLISH indication to the Layer Management. the primitive M-SCTP_ESTABLISH indication to the Layer Management.
Once the SCTP association is established and assuming that the local Once the SCTP association is established and assuming that the local
M2UA-User is ready, the local ASP M2UA Application Server Process M2UA-User is ready, the local ASP M2UA Application Server Process
Maintenance (ASPM) function will initiate the ASPM procedures, using Maintenance (ASPM) function will initiate the ASPM procedures, using
the ASP Up/-Down/-Active/-Inactive messages to convey the ASP-state to the ASP Up/Down/Active/Inactive messages to convey the ASP state to
the SG - see Section 4.3.3. the SG - see Section 4.3.3.
The Layer Management and the M2UA layer on SG can communicate the The Layer Management and the M2UA layer on SG can communicate the
status of the application server using the M-AS STATUS primitives. status of the application server using the M-AS_STATUS primitives.
The Layer Managements and the M2UA layers on both the SG and ASP The Layer Managements and the M2UA layers on both the SG and ASP
can communicate the status of an SCTP association using the can communicate the status of an SCTP association using the
M-SCTP STATUS primitives. M-SCTP_STATUS primitives.
If the Layer Management on SG or ASP wants to bring down an SCTP If the Layer Management on SG or ASP wants to bring down an SCTP
association for management reasons, they would send M-SCTP RELEASE association for management reasons, they would send M-SCTP_RELEASE
request primitive to the local M2UA layer. The M2UA layer would release request primitive to the local M2UA layer. The M2UA layer would
the SCTP association and upon receiving the SCTP Communication Down release the SCTP association and upon receiving the SCTP Communication
indication from the underlying SCTP layer, it would inform the local Down indication from the underlying SCTP layer, it would inform the
Layer Management using M-SCTP RELEASE confirm primitive. local Layer Management using M-SCTP_RELEASE confirm primitive.
If the M2UA layer receives an SCTP-Communication Down or Restart If the M2UA layer receives an SCTP-COMMUNICATION_DOWN or Restart
indication from the underlying SCTP layer, it will inform the Layer indication from the underlying SCTP layer, it will inform the Layer
Management by invoking the M-SCTP RELEASE indication primitive. At the Management by invoking the M-SCTP_RELEASE indication primitive. At the
SG, M2UA shall change the states of all ASPs reached through the aborted SG, M2UA shall change the states of all ASPs reached through the aborted
SCTP association to ASP-DOWN. Athe ASP, M2UA shall either cause other SCTP association to ASP DOWN. At the ASP, the M2UA layer will take
ASPs to become active or send link-out-of-service primitives to MTP3. action based on the appropriate MTP specification. The ASP may indicate
to another ASP that it should become active. However, the ASP to ASP
communication is out of the scope of this document.
At an ASP, the Layer Management MAY try to reestablish the SCTP At an ASP, the Layer Management MAY try to reestablish the SCTP
association using M-SCTP ESTABLISH request primitive. association using M-SCTP_ESTABLISH request primitive.
4.3.3 ASPM procedures for peer-to-peer messages 4.3.3 ASPM procedures for peer-to-peer messages
All ASPM messages are sent on a sequenced stream to ensure ordering. All ASPM messages are sent on a sequenced stream to ensure ordering.
SCTP stream '0' SHOULD be used. SCTP stream '0' SHOULD be used.
4.3.3.1 ASP-Inactive 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,
the SG waits for the ASP to send an ASP Up message, indicating that the the SG waits for the ASP to send an ASP Up message, indicating that the
ASP M2UA peer is available. The ASP is always the initiator of the ASP M2UA peer is available. The ASP is always the initiator of the
ASP Up exchange. ASP Up exchange.
When an ASP Up message is received at an SG and internally the ASP is When an ASP Up message is received at an SG and internally the ASP is
not considered locked-out for local management reasons, the SG marks not considered locked-out for local management reasons, the SG marks
the remote ASP as Inactive. If the ASP UP message contains an ASP the remote ASP as Inactive. If the ASP UP message contains an ASP
Identifier, the SG saves the ASP Identifier for that ASP. The SG Identifier, the SG should save the ASP Identifier for that ASP. The
responds with an ASP Up Ack message in acknowledgement. The SG sends SG responds with an ASP Up Ack message in acknowledgement. The SG
an ASP Up Ack message in response to a received ASP Up message even if sends an ASP Up Ack message in response to a received ASP Up message
the ASP is already marked as "Inactive" at the SG. even if the ASP is already marked as ASP-INACTIVE at the SG.
If for any local reason the SG cannot respond with an ASP Up Ack, the If for any local reason (e.g., management lock-out) the SGP cannot
SG responds to the ASP Up with a ASP Down Ack message. respond with an ASP Up Ack message, the SGP responds to an ASP Up
message with an Error message with Reason "Refused - Management
Blocking".
When the ASP sends an ASP Up it starts timer T(ack). If the ASP does When the ASP sends an ASP Up it starts timer T(ack). If the ASP does
not receive a response to an ASP Up within T(ack), the ASP MAY restart 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 T(ack) and resend ASP Up messages until it receives an ASP Up Ack
message. T(ack) SHOULD be provisionable, with a default of 2 seconds. or ASP Down Ack message. T(ack) SHOULD be provisionable, with a default
Alternatively, retransmission of ASP Up messages MAY be put under of 2 seconds. Alternatively, retransmission of ASP Up messages MAY be
control of Layer Management. In this method, expiry of T(ack) results put under control of Layer Management. In this method, expiry of T(ack)
in a M-ASP-Up confirmation carrying a negative indication. results in a M-ASP_UP confirmation carrying a negative indication.
The ASP MUST wait for the ASP Up Ack message from the SG before The ASP MUST wait for the ASP Up Ack message from the SG before
sending any ASP traffic control messages (ASPAC or ASPIA) or MAUP sending any ASP traffic control messages (ASPAC or ASPIA) or MAUP
messages or it will risk message loss. If the SG receives MAUP messages or it will risk message loss. If the SG receives MAUP
messages before an ASP Up is received, the SG SHOULD discard them. messages before an ASP Up is received, the SG SHOULD discard them.
4.3.3.2 ASP Down If an ASP Up message is received and internally the remote ASP is in
the ASP-ACTIVE or ASP-STANDBY state, an ASP-Up Ack message is returned,
as well as an Error message ("Unexpected Message), and the remote ASP
state is changed to ASP-INACTIVE in all relevant Application Servers.
The ASP will send an ASP Down to a SG when the ASP is to be removed If an ASP Up message is received and internally the remote ASP is
from the list of ASPs in the Application Server that it is a member already in the ASP-INACTIVE state, an ASP Up Ack message is returned
and no longer receive any M2UA traffic or management messages. and no further action is taken.
Whether the ASP is permanently removed from an AS is a function of 4.3.3.2 ASP Down
configuration management.
The SG marks the ASP as "Down" and returns an ASP Down Ack message to The ASP will send an ASP Down message to an SG when the ASP wishes to
the ASP if one of the following events occur: be removed from service in all Application Servers that it is a member
and no longer receive any DATA, SSNM or ASPTM messages. This action
MAY be initiated at the ASP by an M-ASP_DOWN request primitive from Layer
Management or MAY be initiated automatically by an M2UA management
function.
- to acknowledge an ASP Down message received from a remote M2UA The SG marks the ASP as ASP-DOWN, informs Layer Management with an M-
peer ASP_Down indication primitive, and returns an ASP Down Ack message to
- to reply to an ASPM message from an ASP which is locked out the ASP. has locked out the ASP for management reasons.
for management reasons.
The SG sends an ASP Down Ack message in response to a received ASP Down The SG MUST send an ASP Down Ack message in response to a received ASP-
message from the ASP even if the ASP is already marked as "Down" at Down message from the ASP even if the ASP is already marked as ASP-DOWN
the SG. at the SGP. The SG MUST send an ASP Down Ack message even if the reason
in the received ASP Down message is considered invalid.
At the ASP, the ASP Down Ack message received is not acknowledged. At the ASP, the ASP Down Ack message received is not acknowledged.
Layer Management is informed with an M-ASP Down confirm primitive. Layer Management is informed with an M-ASP_DOWN confirm primitive. If
the ASP receives an ASP Down Ack without having sent an ASP Down
message, the ASP should now consider itself as in the ASP-DOWN state.
If the ASP was previously in the ASP-ACTIVE or ASP_INACTIVE state, the
ASP should then initiate procedures to return itself to its previous
state.
When the ASP sends an ASP Down it starts timer T(ack). If the ASP does When the ASP sends an ASP Down it starts timer T(ack). If the ASP does
not receive a response to an ASP Down within T(ack), the ASP MAY 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 restart T(ack) and resend ASP Down messages until it receives an
ASP Down Ack message. T(ack) SHOULD be provisionable, with a default ASP Down Ack message. T(ack) SHOULD be provisionable, with a default
of 2 seconds. Alternatively, retransmission of ASP Down messages MAY of 2 seconds. Alternatively, retransmission of ASP Down messages MAY
be put under control of Layer Management. In this method, expiry of be put under control of Layer Management. In this method, expiry of
T(ack) results in a M-ASP-Down confirmation carrying a negative T(ack) results in a M-ASP_DOWN confirmation carrying a negative
indication. indication.
4.3.3.3 M2UA Version Control 4.3.3.3 M2UA Version Control
If a ASP Up message with an unsupported version is received, the If a 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. the receiving node supports.
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
Any time after the ASP has received a ASP Up Ack from the SG, the ASP Any time after the ASP has received a ASP Up Ack from the SG, the ASP
can send an ASP Active (ASPAC) to the SG indicating that the ASP is can send an ASP Active (ASPAC) to the SG indicating that the ASP is
ready to start processing traffic. ready to start processing traffic. This action MAY be initiated at the
ASP by an M-ASP_ACTIVE request primitive from Layer Management or MAY be
initiated automatically by an M2UA management function.
When an ASP Active (ASPAC) message is received, the SG responds to the When an ASP Active (ASPAC) message is received, the SG responds to the
ASP with a ASPAC Ack message acknowledging that the ASPAC was received ASP with a ASPAC Ack message acknowledging that the ASPAC was received
and starts sending traffic for the associated Application Server and starts sending traffic for the associated Application Server
to that ASP. Note that the SG sends an ASP Active Ack message in to that ASP. Note that the SG sends an ASP Active Ack message in
response to a received ASP Active message even if the ASP is already response to a received ASP Active message even if the ASP is already
marked as "Active" at the SG. marked as "Active" at the SG.
The ASP MUST wait for the ASP Active Ack message from the SG before The ASP MUST wait for the ASP Active Ack message from the SG before
sending any Data messages or it will risk message loss. If the SG sending any Data messages or it will risk message loss. If the SG
receives MAUP messages before an ASP Active is received, the SG SHOULD receives MAUP messages before an ASP Active is received, the SG SHOULD
discard these messages. discard these messages.
At the ASP, the ASP-Active Ack message received is not acknowledged. At the ASP, the ASP Active Ack message received is not acknowledged.
Layer Management is informed with an M-ASP Active confirm primitive. Layer Management is informed with an M-ASP_ACTIVE confirm primitive.
When the ASP sends an ASP Active it starts timer T(ack). If 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 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 ASP MAY restart T(ack) and resend ASP Active messages until it
receives an ASP Active Ack message. T(ack) SHOULD be provisionable, with receives an ASP Active Ack message. T(ack) SHOULD be provisionable, with
a default of 2 seconds. Alternatively, retransmission of ASP Active a default of 2 seconds. Alternatively, retransmission of ASP Active
messages may be put under control of Layer Management. In this method, messages may be put under control of Layer Management. In this method,
expiry of T(ack) results in a M-ASP-Active confirmation carrying a expiry of T(ack) results in a M-ASP_ACTIVE confirmation carrying a
negative indication. negative indication.
There are three modes of Application Server traffic handling in the SG There are three modes of Application Server traffic handling in the SG
M2UA - Over-ride, Load-share and Broadcast. The Traffic Mode Type M2UA: Over-ride, Load-share and Broadcast. The Traffic Mode Type
parameter in the ASPAC messge indicates the mode used in a particular parameter in the ASPAC messge indicates the mode used in a particular
Application Server. If the SG determines that the mode indicates in Application Server. If the SG determines that the mode indicates in
an ASPAC is incompatible with the traffic handling mode currently used an ASPAC is incompatible with the traffic handling mode currently used
in the AS, the SG responds with an Error message indicating Unsupported in the AS, the SG responds with an Error message indicating Unsupported
Traffic Handling Mode. Traffic Handling Mode.
For Over-ride mode AS, the reception of an ASPAC message at an SG causes For Over-ride mode AS, the reception of an ASPAC message at an SG causes
the redirection of all traffic for the AS to the ASP that sent the ASPAC. the redirection of all traffic for the AS to the ASP that sent the ASPAC.
The SG responds to the ASPAC with an ASP Active Ack message to the ASP. The SG responds to the ASPAC with an ASP Active Ack message to the ASP.
Any previously active ASP in the AS is now considered Inactive and will Any previously active ASP in the AS is now considered Inactive and will
no longer receive traffic from the SG within the AS. The SG sends a no longer receive traffic from the SG within the AS. The SG MUST send a
Notify (Alternate ASP-Active) to the previously active ASP in the AS, Notify (Alternate ASP-Active) to the previously active ASP in the AS,
after stopping all traffic to that ASP. after stopping all traffic to that ASP.
In the case of a Load-share mode AS, reception of an ASPAC message at In the case of a Load-share mode AS, reception of an ASPAC message at
an SG causes the redirection of some traffic to the ASP sending the an SG causes the redirection of some traffic to the ASP sending the
ASPAC. The algorithm at the SG for load-sharing traffic within an AS ASPAC. 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 in the Routing Label). message (e.g., such as the SLS in the Routing Label).
In the case of a Broadcast mode AS, reception of an ASPAC message at In the case of a Broadcast mode AS, reception of an ASPAC message at
an SG causes the traffic to be sent to the ASP sending the ASPAC and an SG causes the traffic to be sent to the ASP sending the ASPAC and
the same traffic continues to be sent to the other Active ASP(s). the same traffic continues to be sent to the other Active ASP(s). The
ASPs within a broadcast mode AS must coordinate between themselves to
determine which portion of the broadcast traffic they will handle.
Whenever an ASP in a Broadcast mode AS becomes ASP-ACTIVE, the SG MUST
tag the first DATA message broadcast in each SCTP stream with a
unique Correlation Id parameter. The purpose of this Correlation Id
is to permite the newly active ASP to synchronize its processing of
the traffic in each ordered stream with other ASPs in the broadcast
group.
4.3.3.5 ASP Inactive 4.3.3.5 ASP Inactive
When an ASP wishes to withdraw from receiving traffic within an AS, When an ASP wishes to withdraw from receiving traffic within an AS,
the ASP sends an ASP Inactive (ASPIA) to the SG. the ASP sends an ASP Inactive (ASPIA) to the SG. This action MAY
be initiated at the ASP by an M-ASP_INACTIVE request primitive from
Layer Management or MAY be initiated automatically by an M2UA
management function.
There are three modes of Application Server traffic handling in the SG There are three modes of Application Server traffic handling in the SG
M2UA when withdrawing an ASP from service - Over-ride, Load-share and M2UA when withdrawing an ASP from service - Over-ride, Load-share and
Broadcast. The Traffic Mode Type parameter in the ASPIA messge indicates Broadcast. The Traffic Mode Type parameter in the ASPIA messge indicates
the mode used in a particular Application Server. If the SG determines the mode used in a particular Application Server. If the SG determines
that the mode indicates in an ASPAC is incompatible with the traffic that the mode indicates in an ASPAC is incompatible with the traffic
handling mode currently used in the AS, the SG responds with an Error handling mode currently used in the AS, the SG responds with an Error
message indicating Unsupported Traffic Handling Mode. message indicating Unsupported Traffic Handling Mode.
In the case of an Over-ride mode AS, where normally another ASP has In the case of an Over-ride mode AS, where normally another ASP has
already taken over the traffic within the AS with an Over-ride ASPAC, already taken over the traffic within the AS with an Over-ride ASPAC,
the ASP which sends the ASPIA is already considered by the SG to be the ASP which sends the ASPIA is already considered by the SG to be
"Inactive" (i.e., in the "Inactive" state). An ASPIA Ack message is in the ASP-INACTIVE state. An ASPIA Ack message is sent to the ASP,
sent to the ASP, after ensuring that all traffic is stopped to the ASP. after ensuring that all traffic is stopped to the 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 ASP-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 ASP resources active in AS) may be within the AS. A NTFY(Insufficient ASP resources active in AS) MAY be
sent to all inactive ASPs, if required. An ASPIA Ack message is sent sent to all inactive ASPs, if required. An ASPIA Ack message MUST be
to the ASP after all traffic is halted and Layer Management is informed sent to the ASP after all traffic is halted and Layer Management is
with an ASP-INACTIVE indication primitive. informed with an ASP-INACTIVE indication primitive.
In the case of a Broadcast mode AS, the SG moves the ASP to the In the case of a Broadcast mode AS, the SG moves the ASP to the
"Inactive" state and stops sending the AS traffic to the ASP. The ASP-INACTIVE state and stops sending the AS traffic to the ASP. The
SG continues to send the AS traffic to the remaining "active" ASPs. SG continues to send the AS traffic to the remaining "active" ASPs.
A NTFY(Insufficient ASP resources active in AS) may be sent to all A NTFY(Insufficient ASP resources active in AS) MAY be sent to all
inactive ASPs, if required. An ASPIA Ack message is sent to the ASP inactive ASPs, if required. An ASPIA Ack message MUST be sent to
after all traffic is halted and Layer Management is informed with an the ASP after all traffic is halted and Layer Management is informed
ASP-INACTIVE indication primitive. with an ASP-INACTIVE indication primitive.
When the ASP sends an ASP Inactive it starts timer T(ack). If the ASP 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 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 MAY restart T(ack) and resend ASP Inactive messages until it receives
an ASP Inactive Ack message. T(ack) SHOULD be provisionable, with a an ASP Inactive Ack message. T(ack) SHOULD be provisionable, with a
default of 2 seconds. Alternatively, retransmission of ASP Inactive default of 2 seconds. Alternatively, retransmission of ASP Inactive
messages may be put under control of Layer Management. In this method, messages may be put under control of Layer Management. In this method,
expiry of T(ack) results in a M-ASP-Inactive confirmation carrying a expiry of T(ack) results in a M-ASP-Inactive confirmation carrying a
negative indication. negative indication.
If no other ASPs are Active in the Application Server, the SG either If no other ASPs are Active in the Application Server, the SG either
discards all incoming messages for the AS or starts buffering the discards all incoming messages for the AS or starts buffering the
incoming messages for T(r) seconds, after which messages will be 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. buffered traffic is directed to the ASP and the timer is cancelled.
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 MUST be sent to all
ASP(s) in the AS, except those in the "Down" state, with appropriate ASP(s) in the AS, except those in the ASP-DOWN state, with appropriate
Status Information. Status Information.
In the case where a Notify (AS-Pending) message is sent by an SG In the case where a Notify (AS-Pending) message is sent by an SG
that now has no ASP(s) active to service the traffic, the Notify does that now has no ASP(s) active to service the traffic, the Notify does
not explicitly force the ASP(s) receiving the message to become not explicitly force the ASP(s) receiving the message to become
active. The ASP remain in control of what (and when) action is active. The ASP remain in control of what (and when) action is
taken. taken.
In addition, the Notify message will be sent to all ASP(s) in the In addition, the Notify message MUST be sent to all ASP(s) in the
AS, except those in the "Down" state, when an ASP fails with the AS, except those in the ASP-DOWN state, when an ASP fails with the
ASP Identifier of the failed ASP. ASP Identifier of the failed ASP.
4.4 Link Key Management Procedures
The Interface Identifer Management procedures can be used to support
automatic allocation of Signaling Terminals or Signaling Data
Links [2][3].
4.4.1 Registration
An ASP MAY dynamically register with an SG as an ASP within an
Application Server using the REG REQ message. A Link Key parameter
in the REG REQ specifies the parameters associated with the Link
Key.
The SG examines the contents of the received Link Key parameters (SDLI
and SDTI) and compares them with the currently provisioned Interface
Identifiers. If the received Link Key matches an existing SG Link Key
entry, and the ASP is not currently included in the list of ASPs for
the related Application Server, the SG MAY authorize the ASP to be added
to the AS. Or, if the Link Key does not currently exist and the
received Link Key data is valid and unique, an SG supporting dynamic
configuration MAY authorize the creation of a new Interface Identifier
and related Application Server and add the ASP to the new AS. In either
case, the SG returns a Registration Response message to the ASP,
containing the same Local-LK-Identifier as provided in the initial
request, a Registration Result "Successfully Registered" and the
Interface Identifier. A unique method of Interface Identifier valid
assignment at the SG/SGP is implementation dependent but must be
guaranteed to be unique across all SGPs in an SG.
If the SG determins that the received Link Key data is invalid, or
contains invalid parameter values, the SG returns a Registration
Response message to the ASP, containing a Registration Result "Error
- Invalid Link Key", "Error - Invalid SDTI", "Error - Invalid SDLI"
as appropriate.
If the SG determins that the Link Key parameter overlaps with an
existing Link Key entry, the SG returns a Registration Response
message to the ASP, with a Registration Status of "Error -
Overlapping (Non-Unique) Link Key". An incoming signalling message
received at an SG cannot match against more than one Link Key.
If the SG does not authorize the registration request, the SG
returns a REG RSP message to the ASP containing the Registration
Result "Error - Permission Denied".
If an SG determines that a received Link Key does not currently
exist and the SG does not support dynamic configuration, the SG
returns a Registration Response message to the ASP, containing a
Registration Result "Error - Link Key not Provisioned".
If an SG determines that a received Link Key does not currently
exist and the SG supports dynamic reconfiguration but does not have
the capacity to add new Link Key and Application Server entries, the
SG returns a Registration Response message to the ASP, containing a
Registration Result "Error - Insufficient Resources".
An ASP MAY register multiple Link Keys at once by including a number
of Link Key parameters in a single REG REQ message. The SG MAY
response to each registration request in a single REG RSP message,
indicating the success or failure result for each Link Key in a
separate Registration Result parameter. Alternatively, the SG MAY
respond with multiple REG RSP messages, each with one or more
Registration Result parameters. The ASP uses the Local-LK-Identifier
parameter to correlate the requests with the responses.
4.4.2 Deregistration
An ASP MAY dynamically deregister with an SG as an ASP within an
Application Server for particular Interface Identifier(s) using
the DEREG REQ message. A Interface Identifier parameter in the
DEREG REQ specifies which Inteface Identifer to de-register.
The SG examines the contents of the received Interface Identifier
parameter and validates that the ASP is currently registered in the
Application Server(s) related to the included Interface
Identifier(s). If validated, the ASP is de-registered as an ASP in
the related Application Server.
The deregistration procedure does not necessarily imply the deletion
of Link Key and Application Server configuration data at the SG.
Other ASPs may continue to be associated with the Application
Server, in which case the Link Key data CANNOT be deleted. If a
Deregistration results in no more ASPs in an Application Server, an
SG MAY delte the Link Key data.
The SG acknowledges the de-registration requres by returning a DEREG
RSP to the requesting ASP. The result of the de-registration is
found in the Deregistration Result paraemeter, indicating success or
faliure with cause.
An ASP MAY deregister multiple Interface Identifiers at once by
including a number of Interface Identifiers in a single DEREG REQ
message. The SG MUST response to each deregistration request in a
single DEREG RSP message, indicating the success or failure result
for each Interface Identifier in a separate Deregistration Result
parameter.
5.0 Examples of MTP2 User Adaptation (M2UA) Procedures 5.0 Examples of MTP2 User Adaptation (M2UA) Procedures
5.1 Establishment of associations between SG and MGC examples 5.1 Establishment of associations between SG and MGC examples
5.1.1 Single ASP in an Application Server (1+0 sparing) 5.1.1 Single ASP in an Application Server (1+0 sparing)
This scenario shows the example M2UA message flows for the establishment This scenario shows the example M2UA message flows for the establishment
of traffic between an SG and an ASP, where only one ASP is configured of traffic between an SG and an ASP, where only one ASP is configured
within an AS (no backup). It is assumed that the SCTP association is within an AS (no backup). It is assumed that the SCTP association is
already set-up. already set-up.
SG ASP1 SG ASP1
| |
|<---------ASP Up----------| |<---------ASP Up----------|
|--------ASP Up Ack------->| |--------ASP Up Ack------->|
| | | |
|<-------ASP Active--------| |<-------ASP Active--------|
|------ASP_Active Ack----->| |------ASP_Active Ack----->|
| | | |
5.1.2 Two ASPs in Application Server (1+1 sparing) 5.1.2 Single ASP in an Application Server (1+0 sparing) with Dynamic
Registration
This scenario is the same as the one shown in Section 5.1.1 except
with a dynamic registration (automatic allocation) of Interface
Identifier(s).
SG ASP1
|
|<---------ASP Up----------|
|--------ASP Up Ack------->|
| |
|<--------REG REQ----------|
|------REG REQ RESP------->|
| |
|<-------ASP Active--------|
|------ASPActive Ack----->|
| |
5.1.3 Two ASPs in Application Server (1+1 sparing)
This scenario shows the example M2UA message flows for the establishment This scenario shows the example M2UA message flows for the establishment
of traffic between an SG and two ASPs in the same Application Server, of traffic between an SG and two ASPs in the same Application Server,
where ASP1 is configured to be active and ASP2 to be standby in the event where ASP1 is configured to be active and ASP2 to be standby in the event
of communication failure or the withdrawal from service of ASP1. ASP2 MAY of communication failure or the withdrawal from service of ASP1. ASP2 MAY
act as a hot, warm, or cold standby depending on the extent to which ASP1 act as a hot, warm, or cold standby depending on the extent to which ASP1
and ASP2 share call/transaction state or can communicate call state under and ASP2 share call/transaction state or can communicate call state under
failure/withdrawal events. failure/withdrawal events.
SG ASP1 ASP2 SG ASP1 ASP2
| | | | | |
|<--------ASP Up----------| | |<--------ASP Up----------| |
|-------ASP Up Ack------->| | |-------ASP Up Ack------->| |
| | | | | |
|<-----------------------------ASP Up----------------| |<-----------------------------ASP Up----------------|
|----------------------------ASP Up Ack------------->| |----------------------------ASP Up Ack------------->|
| | | | | |
| | | | | |
|<-------ASP Active-------| | |<-------ASP Active-------| |
|-----ASP-Active Ack----->| | |-----ASP Active Ack----->| |
| | | | | |
5.2 ASP Traffic Fail-over Examples 5.2 ASP Traffic Fail-over Examples
5.2.1 (1+1 Sparing, withdrawal of ASP, Back-up Over-ride) 5.2.1 (1+1 Sparing, withdrawal of ASP, Back-up Over-ride)
Following on from the example in Section 5.1.2, and ASP withdraws from Following on from the example in Section 5.1.2, and ASP withdraws from
service: service:
SG ASP1 ASP2 SG ASP1 ASP2
| | | | | |
|<-----ASP Inactive-------| | |<-----ASP Inactive-------| |
|----ASP Inactive Ack---->| | |----ASP Inactive Ack---->| |
|--------------------NTFY(AS-Down) (Optional)------->| |--------------------NTFY(AS-Down) (Optional)------->|
| | | | | |
|<------------------------------ ASP Active----------| |<------------------------------ ASP Active----------|
|-----------------------------ASP-Active Ack)------->| |-----------------------------ASP Active Ack)------->|
| | | |
In this case, the SG notifies ASP2 that the AS has moved to the In this case, the SG notifies ASP2 that the AS has moved to the
Down state. The SG could have also (optionally) sent a Notify AS-DOWN state. The SG could have also (optionally) sent a Notify
message when the AS moved to the Pending state. message when the AS moved to the AS-PEND state.
Note: If the SG detects loss of the M2UA peer (through a detection Note: If the SG detects loss of the M2UA peer (through a detection
of SCTP failure), the initial SG-ASP1 ASP Inactive message exchange of SCTP failure), the initial SG-ASP1 ASP Inactive message exchange
would not occur. would not occur.
5.2.2 (1+1 Sparing, Back-up Over-ride) 5.2.2 (1+1 Sparing, Back-up Over-ride)
Following on from the example in Section 5.1.2, and ASP2 wishes to over- Following on from the example in Section 5.1.2, and ASP2 wishes to over-
ride ASP1 and take over the traffic: ride ASP1 and take over the traffic:
SG ASP1 ASP2 SG ASP1 ASP2
| | | | | |
|<------------------------------ ASP Active----------| |<-------------------------------ASP Active----------|
|-----------------------------ASP-Active Ack-------->| |-----------------------------ASP Active Ack-------->|
|----NTFY( Alt ASP-Act)-->| |----NTFY( Alt ASP-Act)-->|
| (optional) | | | (optional) | |
In this case, the SG notifies ASP1 that an alternative ASP has In this case, the SG notifies ASP1 that an alternative ASP has
overridden it. overridden it.
5.3 SG to MGC, MTP Level 2 to MTP Level 3 Boundary Procedures 5.3 SG to MGC, MTP Level 2 to MTP Level 3 Boundary Procedures
When the M2UA layer on the ASP has a MAUP message to send to the SG, it When the M2UA layer on the ASP has a MAUP message to send to the SG, it
will do the following: will do the following:
skipping to change at page 31, line 116 skipping to change at page 31, line 116
The flows below show an example of the request and all the potential The flows below show an example of the request and all the potential
responses. responses.
Below is an example in which the SS7 link is out-of-service. Below is an example in which the SS7 link is out-of-service.
MTP2 M2UA M2UA MGMT MTP2 M2UA M2UA MGMT
SG SG ASP ASP SG SG ASP ASP
|<----State Req (STATUS_AUDIT)----|<----Audit------- |<----State Req (STATUS_AUDIT)----|<----Audit-------
|-----State Cfm (STATUS_AUDIT)--->|
MTP3 MTP3
ASP ASP
|-----------Release Ind---------->|-Out of Serv Ind-> |-----------Release Ind---------->|-Out of Serv Ind->
MGMT
ASP
|-----State Cfm (STATUS_AUDIT)--->|----Audit Cfm--->
Below is an example in which the SS7 link is in-service. Below is an example in which the SS7 link is in-service.
MTP2 M2UA M2UA MGMT MTP2 M2UA M2UA MGMT
SG SG ASP ASP SG SG ASP ASP
|<----State Req (STATUS_AUDIT)----|<----Audit------- |<----State Req (STATUS_AUDIT)----|<----Audit-------
|-----State Cfm (STATUS_AUDIT)--->|
MTP3 MTP3
ASP ASP
|-----------Establish Cfm-------->|---In Serv Ind--> |-----------Establish Cfm-------->|---In Serv Ind-->
MGMT
ASP
|-----State Cfm (STATUS_AUDIT)--->|----Audit Cfm--->
Below is an example in which the SS7 link is in-service, but congested. Below is an example in which the SS7 link is in-service, but congested.
MTP2 M2UA M2UA MGMT MTP2 M2UA M2UA MGMT
SG SG ASP ASP SG SG ASP ASP
|<----State Req (STATUS_AUDIT)----|<----Audit------- |<----State Req (STATUS_AUDIT)----|<----Audit-------
|-----State Cfm (STATUS_AUDIT)--->|
MTP3 MTP3
ASP ASP
|-----------Establish Cfm-------->|---In Serv Ind--> |-----------Establish Cfm-------->|---In Serv Ind-->
|----------Congestion Ind-------->|---Cong Ind-----> |----------Congestion Ind-------->|---Cong Ind----->
MGMT
ASP
|-----State Cfm (STATUS_AUDIT)--->|----Audit Cfm--->
Below is an example in which the SS7 link is in-service, but in Remote Below is an example in which the SS7 link is in-service, but in Remote
Processor Outage. Processor Outage.
MTP2 M2UA M2UA MGMT MTP2 M2UA M2UA MGMT
SG SG ASP ASP SG SG ASP ASP
|<----State Req (STATUS_AUDIT)----|<----Audit------- |<----State Req (STATUS_AUDIT)----|<---Audit Req----
|-----State Cfm (STATUS_AUDIT)--->|
MTP3 MTP3
ASP ASP
|-----------Establish Ind-------->|---In Serv Ind--> |-----------Establish Ind-------->|---In Serv Ind-->
|---State Ind (EVENT_RPO_ENTER)-->|----RPO Enter---> |---State Ind (EVENT_RPO_ENTER)-->|----RPO Enter--->
MGMT
ASP
|-----State Cfm (STATUS_AUDIT)--->|----Audit Cfm--->
6.0 Timer Values 6.0 Timer Values
The recommended default values for M2UA timers are: The recommended default values for M2UA timers are:
T(r) 2 seconds T(r) 2 seconds
T(ack) 2 seconds T(ack) 2 seconds
7.0 Security 7.0 Security
M2UA is designed to carry signaling messages for telephony services. M2UA is designed to carry signaling messages for telephony services.
skipping to change at page 33, line 38 skipping to change at page 33, line 38
Recommendation Q.2140', August 1995 Recommendation Q.2140', August 1995
[9] ITU-T Recommendation Q.751.1, 'Network Element Management Information [9] ITU-T Recommendation Q.751.1, 'Network Element Management Information
Model for the Messsage Transfer Part', October 1995 Model for the Messsage Transfer Part', October 1995
[10] Site Security Handbook, RFC 2196, September 1997 [10] Site Security Handbook, RFC 2196, September 1997
[11] Security Architecture for the Internet Protocol, RFC 2401 [11] Security Architecture for the Internet Protocol, RFC 2401
[12] SCTP Dynamic Addition of IP addresses, draft-ietf-tsvwg-addip- [12] SCTP Dynamic Addition of IP addresses, draft-ietf-tsvwg-addip-
sctp-00.txt, May 7, 2001 sctp-00.txt, Work In Progress
11.0 Author's Addresses 11.0 Author's Addresses
Ken Morneault Tel: +1-703-484-3323 Ken Morneault Tel: +1-703-484-3323
Cisco Systems Inc. EMail: kmorneau@cisco.com Cisco Systems Inc. EMail: kmorneau@cisco.com
13615 Dulles Technology Drive 13615 Dulles Technology Drive
Herndon, VA. 20171 Herndon, VA. 20171
USA USA
Ram Dantu, Ph.D. Tel +1-469-255-0716 Ram Dantu, Ph.D. Tel +1-469-255-0716
 End of changes. 

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