| 1 |
<pre>Network Working Group G. Sidebottom |
| 2 |
Request for Comments: 3332 Signatus Technologies |
| 3 |
Category: Standards Track K. Morneault |
| 4 |
Cisco |
| 5 |
J. Pastor-Balbas |
| 6 |
Ericsson |
| 7 |
Editors |
| 8 |
September 2002 |
| 9 |
|
| 10 |
|
| 11 |
<span class="h1">Signaling System 7 (SS7) Message Transfer Part 3 (MTP3) -</span> |
| 12 |
<span class="h1">User Adaptation Layer (M3UA)</span> |
| 13 |
|
| 14 |
Status of this Memo |
| 15 |
|
| 16 |
This document specifies an Internet standards track protocol for the |
| 17 |
Internet community, and requests discussion and suggestions for |
| 18 |
improvements. Please refer to the current edition of the "Internet |
| 19 |
Official Protocol Standards" (STD 1) for the standardization state |
| 20 |
and status of this protocol. Distribution of this memo is unlimited. |
| 21 |
|
| 22 |
Copyright Notice |
| 23 |
|
| 24 |
Copyright (C) The Internet Society (2002). All Rights Reserved. |
| 25 |
|
| 26 |
Abstract |
| 27 |
|
| 28 |
This memo defines a protocol for supporting the transport of any SS7 |
| 29 |
MTP3-User signalling (e.g., ISUP and SCCP messages) over IP using the |
| 30 |
services of the Stream Control Transmission Protocol. Also, |
| 31 |
provision is made for protocol elements that enable a seamless |
| 32 |
operation of the MTP3-User peers in the SS7 and IP domains. This |
| 33 |
protocol would be used between a Signalling Gateway (SG) and a Media |
| 34 |
Gateway Controller (MGC) or IP-resident Database, or between two |
| 35 |
IP-based applications. It is assumed that the SG receives SS7 |
| 36 |
signalling over a standard SS7 interface using the SS7 Message |
| 37 |
Transfer Part (MTP) to provide transport. |
| 38 |
|
| 39 |
Table of Contents |
| 40 |
|
| 41 |
<a href="#section-1">1</a>. Introduction..................................................<a href="#page-3">3</a> |
| 42 |
<a href="#section-1.1">1.1</a> Scope.........................................................<a href="#page-3">3</a> |
| 43 |
<a href="#section-1.2">1.2</a> Terminology...................................................<a href="#page-4">4</a> |
| 44 |
<a href="#section-1.3">1.3</a> M3UA Overview.................................................<a href="#page-6">6</a> |
| 45 |
<a href="#section-1.4">1.4</a> Functional Areas.............................................<a href="#page-10">10</a> |
| 46 |
<a href="#section-1.5">1.5</a> Sample Configurations........................................<a href="#page-18">18</a> |
| 47 |
<a href="#section-1.6">1.6</a> Definition of M3UA Boundaries................................<a href="#page-21">21</a> |
| 48 |
<a href="#section-2">2</a>. Conventions..................................................<a href="#page-25">25</a> |
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 55 |
|
| 56 |
|
| 57 |
<a href="#section-3">3</a>. M3UA Protocol Elements.......................................<a href="#page-25">25</a> |
| 58 |
<a href="#section-3.1">3.1</a> Common Message Header........................................<a href="#page-26">26</a> |
| 59 |
<a href="#section-3.2">3.2</a> Variable Length Parameter....................................<a href="#page-29">29</a> |
| 60 |
<a href="#section-3.3">3.3</a> Transfer Messages............................................<a href="#page-31">31</a> |
| 61 |
<a href="#section-3.4">3.4</a> SS7 Signalling Network Management (SSNM) Messages............<a href="#page-35">35</a> |
| 62 |
<a href="#section-3.5">3.5</a> ASP State Maintenance (ASPSM) Messages.......................<a href="#page-45">45</a> |
| 63 |
<a href="#section-3.6">3.6</a> Routing Key Management (RKM) Messages........................<a href="#page-48">48</a> |
| 64 |
<a href="#section-3.7">3.7</a> ASP Traffic Maintenance (ASPTM) Messages.....................<a href="#page-59">59</a> |
| 65 |
<a href="#section-3.8">3.8</a> Management (MGMT) Messages...................................<a href="#page-63">63</a> |
| 66 |
<a href="#section-4">4</a>. Procedures...................................................<a href="#page-69">69</a> |
| 67 |
<a href="#section-4.1">4.1</a> Procedures to Support the M3UA-User .........................<a href="#page-69">69</a> |
| 68 |
<a href="#section-4.2">4.2</a> Procedures to Support the Management of SCTP Associations ...<a href="#page-70">70</a> |
| 69 |
<a href="#section-4.3">4.3</a> AS and ASP State Maintenance.................................<a href="#page-72">72</a> |
| 70 |
<a href="#section-4.4">4.4</a> Routing Key Management Procedures............................<a href="#page-87">87</a> |
| 71 |
4.5 Procedures to Support the Availability or Congestion Status |
| 72 |
of SS7 Destination...........................................<a href="#page-89">89</a> |
| 73 |
<a href="#section-4.6">4.6</a> MTP3 Restart.................................................<a href="#page-92">92</a> |
| 74 |
<a href="#section-5">5</a>. Examples of M3UA Procedures..................................<a href="#page-93">93</a> |
| 75 |
5.1 Establishment of Association and Traffic |
| 76 |
Between SGs and ASPs.........................................<a href="#page-93">93</a> |
| 77 |
<a href="#section-5.2">5.2</a> ASP traffic Failover Examples................................<a href="#page-99">99</a> |
| 78 |
5.3 Normal Withdrawal of an ASP from an Application Server |
| 79 |
and Teardown of an Association..............................<a href="#page-100">100</a> |
| 80 |
<a href="#section-5.4">5.4</a> M3UA/MTP3-User Boundary Examples............................<a href="#page-101">101</a> |
| 81 |
<a href="#section-5.5">5.5</a> Examples of IPSP communication..............................<a href="#page-105">105</a> |
| 82 |
<a href="#section-6">6</a>. Security Considerations.....................................<a href="#page-108">108</a> |
| 83 |
<a href="#section-6.1">6.1</a> Introduction................................................<a href="#page-108">108</a> |
| 84 |
<a href="#section-6.2">6.2</a> Threats.....................................................<a href="#page-108">108</a> |
| 85 |
<a href="#section-6.3">6.3</a> Protecting Confidentiality..................................<a href="#page-108">108</a> |
| 86 |
<a href="#section-7">7</a>. IANA Considerations.........................................<a href="#page-109">109</a> |
| 87 |
<a href="#section-7.1">7.1</a> SCTP Payload Protocol Identifier............................<a href="#page-109">109</a> |
| 88 |
<a href="#section-7.2">7.2</a> M3UA Port Number............................................<a href="#page-109">109</a> |
| 89 |
<a href="#section-7.3">7.3</a> M3UA Protocol Extensions....................................<a href="#page-109">109</a> |
| 90 |
<a href="#section-8">8</a>. References...................................................<a href="#page-111">111</a> |
| 91 |
<a href="#section-8.1">8.1</a> Normative References........................................<a href="#page-111">111</a> |
| 92 |
<a href="#section-8.2">8.2</a> Informative References......................................<a href="#page-111">111</a> |
| 93 |
<a href="#section-9">9</a>. Acknowledgements.............................................<a href="#page-113">113</a> |
| 94 |
<a href="#section-10">10</a>. Document Contributors.......................................<a href="#page-113">113</a> |
| 95 |
<a href="#appendix-A">Appendix A</a>......................................................<a href="#page-114">114</a> |
| 96 |
<a href="#appendix-A.1">A.1</a> Signalling Network Architecture.............................<a href="#page-114">114</a> |
| 97 |
<a href="#appendix-A.2">A.2</a> Redundancy Models...........................................<a href="#page-117">117</a> |
| 98 |
Editors' Addresses..............................................<a href="#page-119">119</a> |
| 99 |
Full Copyright Statement........................................<a href="#page-120">120</a> |
| 100 |
|
| 101 |
|
| 102 |
|
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 111 |
|
| 112 |
|
| 113 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 114 |
|
| 115 |
This memo defines a protocol for supporting the transport of any SS7 |
| 116 |
MTP3-User signalling (e.g., ISUP and SCCP messages) over IP using the |
| 117 |
services of the Stream Control Transmission Protocol [<a href="#ref-17" title=""Stream Control Transport Protocol"">17</a>]. Also, |
| 118 |
provision is made for protocol elements that enable a seamless |
| 119 |
operation of the MTP3-User peers in the SS7 and IP domains. This |
| 120 |
protocol would be used between a Signalling Gateway (SG) and a Media |
| 121 |
Gaway Controller (MGC) or IP-resident Database [<a href="#ref-11" title=""Framework Architecture for Signaling Transport"">11</a>], or between two |
| 122 |
IP-based applications. |
| 123 |
|
| 124 |
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a> Scope</span> |
| 125 |
|
| 126 |
There is a need for Switched Circuit Network (SCN) signalling |
| 127 |
protocol delivery from an SS7 Signalling Gateway (SG) to a Media |
| 128 |
Gateway Controller (MGC) or IP-resident Database as described in the |
| 129 |
Framework Architecture for Signalling Transport [<a href="#ref-11" title=""Framework Architecture for Signaling Transport"">11</a>]. The delivery |
| 130 |
mechanism should meet the following criteria: |
| 131 |
|
| 132 |
* Support for the transfer of all SS7 MTP3-User Part messages (e.g., |
| 133 |
ISUP [<a href="#ref-1">1</a>,<a href="#ref-2">2</a>,<a href="#ref-3">3</a>], SCCP [<a href="#ref-4">4</a>,<a href="#ref-5">5</a>,<a href="#ref-6">6</a>], TUP [<a href="#ref-12">12</a>], etc.) |
| 134 |
* Support for the seamless operation of MTP3-User protocol peers |
| 135 |
* Support for the management of SCTP transport associations and |
| 136 |
traffic between an SG and one or more MGCs or IP-resident |
| 137 |
Databases |
| 138 |
* Support for MGC or IP-resident Database process failover and load |
| 139 |
sharing |
| 140 |
* Support for the asynchronous reporting of status changes to |
| 141 |
management |
| 142 |
|
| 143 |
In simplistic transport terms, the SG will terminate SS7 MTP2 and |
| 144 |
MTP3 protocol layers [<a href="#ref-7">7</a>,<a href="#ref-8">8</a>,<a href="#ref-9">9</a>] and deliver ISUP, SCCP and/or any other |
| 145 |
MTP3-User protocol messages, as well as certain MTP network |
| 146 |
management events, over SCTP transport associations to MTP3-User |
| 147 |
peers in MGCs or IP-resident Databases. |
| 148 |
|
| 149 |
|
| 150 |
|
| 151 |
|
| 152 |
|
| 153 |
|
| 154 |
|
| 155 |
|
| 156 |
|
| 157 |
|
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 167 |
|
| 168 |
|
| 169 |
<span class="h3"><a class="selflink" id="section-1.2" href="#section-1.2">1.2</a> Terminology</span> |
| 170 |
|
| 171 |
Application Server (AS) - A logical entity serving a specific Routing |
| 172 |
Key. An example of an Application Server is a virtual switch element |
| 173 |
handling all call processing for a unique range of PSTN trunks, |
| 174 |
identified by an SS7 SIO/DPC/OPC/CIC_range. Another example is a |
| 175 |
virtual database element, handling all HLR transactions for a |
| 176 |
particular SS7 DPC/OPC/SCCP_SSN combination. The AS contains a set |
| 177 |
of one or more unique Application Server Processes, of which one or |
| 178 |
more is normally actively processing traffic. Note that there is a |
| 179 |
1:1 relationship between an AS and a Routing Key. |
| 180 |
|
| 181 |
Application Server Process (ASP) - A process instance of an |
| 182 |
Application Server. An Application Server Process serves as an active |
| 183 |
or backup process of an Application Server (e.g., part of a |
| 184 |
distributed virtual switch or database). Examples of ASPs are |
| 185 |
processes (or process instances) of MGCs, IP SCPs or IP HLRs. An ASP |
| 186 |
contains an SCTP endpoint and may be configured to process signalling |
| 187 |
traffic within more than one Application Server. |
| 188 |
|
| 189 |
Association - An association refers to an SCTP association. The |
| 190 |
association provides the transport for the delivery of MTP3-User |
| 191 |
protocol data units and M3UA adaptation layer peer messages. |
| 192 |
|
| 193 |
IP Server Process (IPSP) - A process instance of an IP-based |
| 194 |
application. An IPSP is essentially the same as an ASP, except that |
| 195 |
it uses M3UA in a point-to-point fashion. Conceptually, an IPSP does |
| 196 |
not use the services of a Signalling Gateway node. |
| 197 |
|
| 198 |
Failover - The capability to reroute signalling traffic as required |
| 199 |
to an alternate Application Server Process, or group of ASPs, within |
| 200 |
an Application Server in the event of failure or unavailability of a |
| 201 |
currently used Application Server Process. Failover also applies |
| 202 |
upon the return to service of a previously unavailable Application |
| 203 |
Server Process. |
| 204 |
|
| 205 |
Host - The computing platform that the process (SGP, ASP or IPSP) is |
| 206 |
running on. |
| 207 |
|
| 208 |
Layer Management - Layer Management is a nodal function that handles |
| 209 |
the inputs and outputs between the M3UA layer and a local management |
| 210 |
entity. |
| 211 |
|
| 212 |
|
| 213 |
|
| 214 |
|
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 223 |
|
| 224 |
|
| 225 |
Linkset - A number of signalling links that directly interconnect two |
| 226 |
signalling points, which are used as a module. |
| 227 |
|
| 228 |
MTP - The Message Transfer Part of the SS7 protocol. |
| 229 |
|
| 230 |
MTP3 - MTP Level 3, the signalling network layer of SS7 |
| 231 |
|
| 232 |
MTP3-User - Any protocol normally using the services of the SS7 MTP3 |
| 233 |
(e.g., ISUP, SCCP, TUP, etc.). |
| 234 |
|
| 235 |
Network Appearance - The Network Appearance is a M3UA local reference |
| 236 |
shared by SG and AS (typically an integer) that together with an |
| 237 |
Signaling Point Code uniquely identifies an SS7 node by indicating |
| 238 |
the specific SS7 network it belongs to. It can be used to distinguish |
| 239 |
between signalling traffic associated with different networks being |
| 240 |
sent between the SG and the ASP over a common SCTP association. An |
| 241 |
example scenario is where an SG appears as an element in multiple |
| 242 |
separate national SS7 networks and the same Signaling Point Code |
| 243 |
value may be reused in different networks. |
| 244 |
|
| 245 |
Network Byte Order: Most significant byte first, a.k.a Big Endian. |
| 246 |
|
| 247 |
Routing Key: A Routing Key describes a set of SS7 parameters and |
| 248 |
parameter values that uniquely define the range of signalling traffic |
| 249 |
to be handled by a particular Application Server. Parameters within |
| 250 |
the Routing Key cannot extend across more than a single Signalling |
| 251 |
Point Management Cluster. |
| 252 |
|
| 253 |
Routing Context - A value that uniquely identifies a Routing Key. |
| 254 |
Routing Context values are either configured using a configuration |
| 255 |
management interface, or by using the routing key management |
| 256 |
procedures defined in this document. |
| 257 |
|
| 258 |
Signalling Gateway Process (SGP) - A process instance of a Signalling |
| 259 |
Gateway. It serves as an active, backup, load-sharing or broadcast |
| 260 |
process of a Signalling Gateway. |
| 261 |
|
| 262 |
Signalling Gateway - An SG is a signaling agent that receives/sends |
| 263 |
SCN native signaling at the edge of the IP network [<a href="#ref-11" title=""Framework Architecture for Signaling Transport"">11</a>]. An SG |
| 264 |
appears to the SS7 network as an SS7 Signalling Point. An SG |
| 265 |
contains a set of one or more unique Signalling Gateway Processes, of |
| 266 |
which one or more is normally actively processing traffic. Where an |
| 267 |
SG contains more than one SGP, the SG is a logical entity and the |
| 268 |
contained SGPs are assumed to be coordinated into a single management |
| 269 |
view to the SS7 network and to the supported Application Servers. |
| 270 |
|
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 279 |
|
| 280 |
|
| 281 |
Signalling Process - A process instance that uses M3UA to communicate |
| 282 |
with other signalling processes. An ASP, an SGP and an IPSP are all |
| 283 |
signalling processes. |
| 284 |
|
| 285 |
Signalling Point Management Cluster (SPMC) - The complete set of |
| 286 |
Application Servers represented to the SS7 network under a single MTP |
| 287 |
entity (Signalling Point) in one specific Network Appearance. SPMCs |
| 288 |
are used to aggregate the availability, congestion, and user part |
| 289 |
status of an MTP entity (Signalling Point) that is distributed in the |
| 290 |
IP domain, for the purpose of supporting MTP3 management procedures |
| 291 |
towards the SS7 network. In some cases, the SG itself may also be a |
| 292 |
member of the SPMC. In this case, the SG availability /congestion |
| 293 |
/User_Part status should also be taken into account when considering |
| 294 |
any supporting MTP3 management actions. |
| 295 |
|
| 296 |
Stream - A stream refers to an SCTP stream; a unidirectional logical |
| 297 |
channel established from one SCTP endpoint to another associated SCTP |
| 298 |
endpoint, within which all user messages are delivered in-sequence |
| 299 |
except for those submitted to the unordered delivery service. |
| 300 |
|
| 301 |
<span class="h3"><a class="selflink" id="section-1.3" href="#section-1.3">1.3</a> M3UA Overview</span> |
| 302 |
|
| 303 |
<span class="h4"><a class="selflink" id="section-1.3.1" href="#section-1.3.1">1.3.1</a> Protocol Architecture</span> |
| 304 |
|
| 305 |
The framework architecture that has been defined for SCN signalling |
| 306 |
transport over IP [<a href="#ref-11" title=""Framework Architecture for Signaling Transport"">11</a>] uses multiple components, including a common |
| 307 |
signalling transport protocol and an adaptation module to support the |
| 308 |
services expected by a particular SCN signalling protocol from its |
| 309 |
underlying protocol layer. |
| 310 |
|
| 311 |
Within the framework architecture, this document defines an MTP3-User |
| 312 |
adaptation module suitable for supporting the transfer of messages of |
| 313 |
any protocol layer that is identified to the MTP Level 3 as an MTP |
| 314 |
User. The list of these protocol layers includes, but is not limited |
| 315 |
to, ISDN User Part (ISUP) [<a href="#ref-1">1</a>,<a href="#ref-2">2</a>,<a href="#ref-3">3</a>], Signalling Connection Control Part |
| 316 |
(SCCP) [<a href="#ref-4">4</a>,<a href="#ref-5">5</a>,<a href="#ref-6">6</a>] and Telephone User Part (TUP) [<a href="#ref-12">12</a>]. TCAP [<a href="#ref-13">13</a>,<a href="#ref-14">14</a>,<a href="#ref-15">15</a>] |
| 317 |
or RANAP [<a href="#ref-16">16</a>] messages are transferred transparently by the M3UA |
| 318 |
protocol as SCCP payload, as they are SCCP-User protocols. |
| 319 |
|
| 320 |
It is recommended that M3UA use the services of the Stream Control |
| 321 |
Transmission Protocol (SCTP) [<a href="#ref-17" title=""Stream Control Transport Protocol"">17</a>] as the underlying reliable common |
| 322 |
signalling transport protocol. This is to take advantage of various |
| 323 |
SCTP features such as: |
| 324 |
|
| 325 |
|
| 326 |
|
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 335 |
|
| 336 |
|
| 337 |
- Explicit packet-oriented delivery (not stream-oriented), |
| 338 |
- Sequenced delivery of user messages within multiple streams, |
| 339 |
with an option for order-of-arrival delivery of individual |
| 340 |
user messages, |
| 341 |
- Optional multiplexing of user messages into SCTP datagrams, |
| 342 |
- Network-level fault tolerance through support of multi-homing |
| 343 |
at either or both ends of an association, |
| 344 |
- Resistance to flooding and masquerade attacks, and |
| 345 |
- Data segmentation to conform to discovered path MTU size. |
| 346 |
|
| 347 |
Under certain scenarios, such as back-to-back connections without |
| 348 |
redundancy requirements, the SCTP functions above might not be a |
| 349 |
requirement and TCP MAY be used as the underlying common transport |
| 350 |
protocol. |
| 351 |
|
| 352 |
<span class="h4"><a class="selflink" id="section-1.3.2" href="#section-1.3.2">1.3.2</a> Services Provided by the M3UA Layer</span> |
| 353 |
|
| 354 |
The M3UA Layer at an ASP or IPSP provides the equivalent set of |
| 355 |
primitives at its upper layer to the MTP3-Users as provided by the |
| 356 |
MTP Level 3 to its local MTP3-Users at an SS7 SEP. In this way, the |
| 357 |
ISUP and/or SCCP layer at an ASP or IPSP is unaware that the expected |
| 358 |
MTP3 services are offered remotely from an MTP3 Layer at an SGP, and |
| 359 |
not by a local MTP3 layer. The MTP3 layer at an SGP may also be |
| 360 |
unaware that its local users are actually remote user parts over |
| 361 |
M3UA. In effect, the M3UA extends access to the MTP3 layer services |
| 362 |
to a remote IP-based application. The M3UA layer does not itself |
| 363 |
provide the MTP3 services. However, in the case where an ASP is |
| 364 |
connected to more than one SG, the M3UA layer at an ASP should |
| 365 |
maintain the status of configured SS7 destinations and route messages |
| 366 |
according to the availability and congestion status of the routes to |
| 367 |
these destinations via each SG. |
| 368 |
|
| 369 |
The M3UA layer may also be used for point-to-point signalling between |
| 370 |
two IP Server Processes (IPSPs). In this case, the M3UA layer |
| 371 |
provides the same set of primitives and services at its upper layer |
| 372 |
as the MTP3. However, in this case the expected MTP3 services are not |
| 373 |
offered remotely from an SGP. The MTP3 services are provided but the |
| 374 |
procedures to support these services are a subset of the MTP3 |
| 375 |
procedures due to the simplified point-to-point nature of the IPSP to |
| 376 |
IPSP relationship. |
| 377 |
|
| 378 |
|
| 379 |
|
| 380 |
|
| 381 |
|
| 382 |
|
| 383 |
|
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 391 |
|
| 392 |
|
| 393 |
<span class="h5"><a class="selflink" id="section-1.3.2.1" href="#section-1.3.2.1">1.3.2.1</a> Support for the Transport of MTP3-User Messages</span> |
| 394 |
|
| 395 |
The M3UA layer provides the transport of MTP-TRANSFER primitives |
| 396 |
across an established SCTP association between an SGP and an ASP or |
| 397 |
between IPSPs. |
| 398 |
|
| 399 |
At an ASP, in the case where a destination is reachable via multiple |
| 400 |
SGPs, the M3UA layer must also choose via which SGP the message is to |
| 401 |
be routed or support load balancing across the SGPs, minimizing |
| 402 |
missequencing. |
| 403 |
|
| 404 |
The M3UA layer does not impose a 272-octet signalling information |
| 405 |
field (SIF) length limit as specified by the SS7 MTP Level 2 protocol |
| 406 |
[<a href="#ref-7">7</a>,<a href="#ref-8">8</a>,<a href="#ref-9">9</a>]. Larger information blocks can be accommodated directly by |
| 407 |
M3UA/SCTP, without the need for an upper layer segmentation/re- |
| 408 |
assembly procedure as specified in recent SCCP or ISUP versions. |
| 409 |
However, in the context of an SG, the maximum 272-octet block size |
| 410 |
must be followed when interworking to a SS7 network that does not |
| 411 |
support the transfer of larger information blocks to the final |
| 412 |
destination. This avoids potential ISUP or SCCP fragmentation |
| 413 |
requirements at the SGPs. The provisioning and configuration of the |
| 414 |
SS7 network determines the restriction placed on the maximum block |
| 415 |
size. Some configurations (e.g., Broadband MTP [<a href="#ref-21">21</a>]) may permit |
| 416 |
larger block sizes. |
| 417 |
|
| 418 |
<span class="h5"><a class="selflink" id="section-1.3.2.2" href="#section-1.3.2.2">1.3.2.2</a> Native Management Functions</span> |
| 419 |
|
| 420 |
The M3UA layer provides the capability to indicate errors associated |
| 421 |
with received M3UA messages and to notify, as appropriate, local |
| 422 |
management and/or the peer M3UA. |
| 423 |
|
| 424 |
<span class="h5"><a class="selflink" id="section-1.3.2.3" href="#section-1.3.2.3">1.3.2.3</a> Interworking with MTP3 Network Management Functions</span> |
| 425 |
|
| 426 |
At the SGP, the M3UA layer provides interworking with MTP3 management |
| 427 |
functions to support seamless operation of the user SCN signalling |
| 428 |
applications in the SS7 and IP domains. This includes: |
| 429 |
|
| 430 |
- Providing an indication to MTP3-Users at an ASP that a destination |
| 431 |
in the SS7 network is not reachable. |
| 432 |
|
| 433 |
- Providing an indication to MTP3-Users at an ASP that a destination |
| 434 |
in the SS7 network is now reachable. |
| 435 |
|
| 436 |
- Providing an indication to MTP3-Users at an ASP that messages to a |
| 437 |
destination in the SS7 network are experiencing SS7 congestion. |
| 438 |
|
| 439 |
|
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 447 |
|
| 448 |
|
| 449 |
- Providing an indication to the M3UA layer at an ASP that the routes |
| 450 |
to a destination in the SS7 network are restricted. |
| 451 |
|
| 452 |
- Providing an indication to MTP3-Users at an ASP that a MTP3-User |
| 453 |
peer is unavailable. |
| 454 |
|
| 455 |
The M3UA layer at an ASP keeps the state of the routes to remote SS7 |
| 456 |
destinations and may initiate an audit of the availability, the |
| 457 |
restricted or the congested state of remote SS7 destinations. This |
| 458 |
information is requested from the M3UA layer at the SGP. |
| 459 |
|
| 460 |
The M3UA layer at an ASP may also indicate to the SG that the M3UA |
| 461 |
layer itself or the ASP or the ASP's Host is congested. |
| 462 |
|
| 463 |
<span class="h5"><a class="selflink" id="section-1.3.2.4" href="#section-1.3.2.4">1.3.2.4</a> Support for the Management of SCTP Associations between the SGP</span> |
| 464 |
<span class="h5"> and ASPs.</span> |
| 465 |
|
| 466 |
The M3UA layer at the SGP maintains the availability state of all |
| 467 |
configured remote ASPs, to manage the SCTP Associations and the |
| 468 |
traffic between the M3UA peers. As well, the active/inactive and |
| 469 |
congestion state of remote ASPs is maintained. |
| 470 |
|
| 471 |
The M3UA layer MAY be instructed by local management to establish an |
| 472 |
SCTP association to a peer M3UA node. This can be achieved using the |
| 473 |
M-SCTP_ESTABLISH primitives (See <a href="#section-1.6.3">Section 1.6.3</a> for a description of |
| 474 |
management primitives.) to request, indicate and confirm the |
| 475 |
establishment of an SCTP association with a peer M3UA node. In order |
| 476 |
to avoid redundant SCTP associations between two M3UA peers, one side |
| 477 |
(client) SHOULD be designated to establish the SCTP association, or |
| 478 |
M3UA configuration information maintained to detect redundant |
| 479 |
associations (e.g., via knowledge of the expected local and remote |
| 480 |
SCTP endpoint addresses). |
| 481 |
|
| 482 |
Local management MAY request from the M3UA layer the status of the |
| 483 |
underlying SCTP associations using the M-SCTP_STATUS request and |
| 484 |
confirm primitives. Also, the M3UA MAY autonomously inform local |
| 485 |
management of the reason for the release of an SCTP association, |
| 486 |
determined either locally within the M3UA layer or by a primitive |
| 487 |
from the SCTP. |
| 488 |
|
| 489 |
Also the M3UA layer MAY inform the local management of the change in |
| 490 |
status of an ASP or AS. This MAY be achieved using the M-ASP_STATUS |
| 491 |
request or M-AS_STATUS request primitives. |
| 492 |
|
| 493 |
|
| 494 |
|
| 495 |
|
| 496 |
|
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 503 |
|
| 504 |
|
| 505 |
<span class="h5"><a class="selflink" id="section-1.3.2.5" href="#section-1.3.2.5">1.3.2.5</a> Support for the Management of Connections to Multiple SGPs</span> |
| 506 |
|
| 507 |
As shown in Figure 1 an ASP may be connected to multiple SGPs. In |
| 508 |
such a case a particular SS7 destination may be reachable via more |
| 509 |
than one SGP and/or SG, i.e., via more than one route. As MTP3 users |
| 510 |
only maintain status on a destination and not on a route basis, the |
| 511 |
M3UA layer must maintain the status (availability, restriction, |
| 512 |
and/or congestion of route to destination) of the individual routes, |
| 513 |
derive the overall availability or congestion status of the |
| 514 |
destination from the status of the individual routes, and inform the |
| 515 |
MTP3 users of this derived status whenever it changes. |
| 516 |
|
| 517 |
<span class="h3"><a class="selflink" id="section-1.4" href="#section-1.4">1.4</a> Functional Areas</span> |
| 518 |
|
| 519 |
<span class="h4"><a class="selflink" id="section-1.4.1" href="#section-1.4.1">1.4.1</a> Signalling Point Code Representation</span> |
| 520 |
|
| 521 |
For example, within an SS7 network, a Signalling Gateway might be |
| 522 |
charged with representing a set of nodes in the IP domain into the |
| 523 |
SS7 network for routing purposes. The SG itself, as a signalling |
| 524 |
point in the SS7 network, might also be addressable with an SS7 Point |
| 525 |
Code for MTP3 Management purposes. The SG Point Code might also be |
| 526 |
used for addressing any local MTP3-Users at the SG such as a local |
| 527 |
SCCP layer. |
| 528 |
|
| 529 |
An SG may be logically partitioned to operate in multiple SS7 network |
| 530 |
appearances. In such a case, the SG could be addressable with a |
| 531 |
Point Code in each network appearance, and represents a set of nodes |
| 532 |
in the IP domain into each SS7 network. Alias Point Codes [<a href="#ref-8">8</a>] may |
| 533 |
also be used within an SG network appearance. |
| 534 |
|
| 535 |
Where an SG contains more than one SGP, the MTP3 routeset, SPMC and |
| 536 |
remote AS/ASP states of each SGP SHOULD be coordinated across all the |
| 537 |
SGPs. Rerouting of traffic between the SGPs MAY also be supported. |
| 538 |
|
| 539 |
Application Servers can be represented under the same Point Code of |
| 540 |
the SG, their own individual Point Codes or grouped with other |
| 541 |
Application Servers for Point Code preservation purposes. A single |
| 542 |
Point Code may be used to represent the SG and all the Application |
| 543 |
Servers together, if desired. |
| 544 |
|
| 545 |
If an ASP or group of ASPs is available to the SS7 network via more |
| 546 |
than one SG, each with its own Point Code, the ASP(s) will typically |
| 547 |
be represented by a Point Code that is separate from any SG Point |
| 548 |
Code. This allows, for example, these SGs to be viewed from the SS7 |
| 549 |
network as "STPs", each having an ongoing "route" to the same ASP(s). |
| 550 |
Under failure conditions where the ASP(s) become(s) unavailable from |
| 551 |
one of the SGs, this approach enables MTP3 route management messaging |
| 552 |
between the SG and SS7 network, allowing simple SS7 rerouting through |
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 559 |
|
| 560 |
|
| 561 |
an alternate SG without changing the Destination Point Code Address |
| 562 |
of SS7 traffic to the ASP(s). |
| 563 |
|
| 564 |
Where a particular AS can be reached via more than one SGP, the |
| 565 |
corresponding Routing Keys in the SGPs should be identical. (Note: |
| 566 |
It is possible for the SGP Routing Key configuration data to be |
| 567 |
temporarily out-of-sync during configuration updates). |
| 568 |
|
| 569 |
+--------+ |
| 570 |
| | |
| 571 |
+------------+ SG 1 +--------------+ |
| 572 |
+-------+ | SS7 links | "STP" | IP network | ---- |
| 573 |
| SEP +---+ +--------+ +---/ \ |
| 574 |
| or | |* | ASPs | |
| 575 |
| STP +---+ +--------+ +---\ / |
| 576 |
+-------+ | | | | ---- |
| 577 |
+------------+ SG 2 +--------------+ |
| 578 |
| "STP" | |
| 579 |
+--------+ |
| 580 |
|
| 581 |
Figure 1 Example with mated SGs |
| 582 |
|
| 583 |
* Note:. SG-to-SG communication (i.e., "C-links") is recommended for |
| 584 |
carrier grade networks, using an MTP3 linkset or an equivalent, to |
| 585 |
allow rerouting between the SGs in the event of route failures. Where |
| 586 |
SGPs are used, inter-SGP communication might be used. Inter-SGP |
| 587 |
protocol is outside of the scope of this document. |
| 588 |
|
| 589 |
The following example shows a signalling gateway partitioned into two |
| 590 |
network appearances. |
| 591 |
|
| 592 |
SG |
| 593 |
+-------+ +---------------+ |
| 594 |
| SEP +--------------| SS7 Ntwk |M3UA| ---- |
| 595 |
+-------+ SS7 links | "A" | | / \ |
| 596 |
|__________| +-----------+ ASPs | |
| 597 |
| | | \ / |
| 598 |
+-------+ | SS7 Ntwk | | ---- |
| 599 |
| SEP +--------------+ "B" | | |
| 600 |
+-------+ +---------------+ |
| 601 |
|
| 602 |
Figure 2 Example with multiple Network |
| 603 |
|
| 604 |
|
| 605 |
|
| 606 |
|
| 607 |
|
| 608 |
|
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 615 |
|
| 616 |
|
| 617 |
<span class="h4"><a class="selflink" id="section-1.4.2" href="#section-1.4.2">1.4.2</a> Routing Contexts and Routing Keys</span> |
| 618 |
|
| 619 |
<span class="h5"><a class="selflink" id="section-1.4.2.1" href="#section-1.4.2.1">1.4.2.1</a> Overview</span> |
| 620 |
|
| 621 |
The distribution of SS7 messages between the SGP and the Application |
| 622 |
Servers is determined by the Routing Keys and their associated |
| 623 |
Routing Contexts. A Routing Key is essentially a set of SS7 |
| 624 |
parameters used to filter SS7 messages, whereas the Routing Context |
| 625 |
parameter is a 4-byte value (integer) that is associated to that |
| 626 |
Routing Key in a 1:1 relationship. The Routing Context therefore can |
| 627 |
be viewed as an index into a sending node's Message Distribution |
| 628 |
Table containing the Routing Key entries. |
| 629 |
|
| 630 |
Possible SS7 address/routing information that comprise a Routing Key |
| 631 |
entry includes, for example, the OPC, DPC, SIO found in the MTP3 |
| 632 |
routing label, or MTP3-User specific fields (such as the ISUP CIC, |
| 633 |
SCCP subsystem number). Some example Routing Keys are: the DPC |
| 634 |
alone, the DPC/OPC combination, the DPC/OPC/CIC combination, or the |
| 635 |
DPC/SSN combination. The particular information used to define an |
| 636 |
M3UA Routing Key is application and network dependent, and none of |
| 637 |
the above examples are mandated. |
| 638 |
|
| 639 |
An Application Server Process may be configured to process signalling |
| 640 |
traffic related to more than one Application Server, over a single |
| 641 |
SCTP Association. In ASP Active and ASP Inactive management |
| 642 |
messages, the signalling traffic to be started or stopped is |
| 643 |
discriminated by the Routing Context parameter. At an ASP, the |
| 644 |
Routing Context parameter uniquely identifies the range of signalling |
| 645 |
traffic associated with each Application Server that the ASP is |
| 646 |
configured to receive. |
| 647 |
|
| 648 |
<span class="h5"><a class="selflink" id="section-1.4.2.2" href="#section-1.4.2.2">1.4.2.2</a> Routing Key Limitations</span> |
| 649 |
|
| 650 |
Routing Keys SHOULD be unique in the sense that each received SS7 |
| 651 |
signalling message SHOULD have a full or partial match to a single |
| 652 |
routing result. It is not necessary for the parameter range values |
| 653 |
within a particular Routing Key to be contiguous. For example, an AS |
| 654 |
could be configured to support call processing for multiple ranges of |
| 655 |
PSTN trunks that are not represented by contiguous CIC values. |
| 656 |
|
| 657 |
<span class="h5"><a class="selflink" id="section-1.4.2.3" href="#section-1.4.2.3">1.4.2.3</a> Managing Routing Contexts and Routing Keys</span> |
| 658 |
|
| 659 |
There are two ways to provision a Routing Key at an SGP. A Routing |
| 660 |
Key may be configured statically using an implementation dependent |
| 661 |
management interface, or dynamically using the M3UA Routing Key |
| 662 |
registration procedure. |
| 663 |
|
| 664 |
|
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 12]</span></pre> |
| 669 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 670 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 671 |
|
| 672 |
|
| 673 |
When using a management interface to configure Routing Keys, the |
| 674 |
message distribution function within the SGP is not limited to the |
| 675 |
set of parameters defined in this document. Other implementation |
| 676 |
dependent distribution algorithms may be used. |
| 677 |
|
| 678 |
<span class="h5"><a class="selflink" id="section-1.4.2.4" href="#section-1.4.2.4">1.4.2.4</a> Message Distribution at the SGP</span> |
| 679 |
|
| 680 |
To direct messages received from the SS7 MTP3 network to the |
| 681 |
appropriate IP destination, the SGP must perform a message |
| 682 |
distribution function using information from the received MTP3-User |
| 683 |
message. |
| 684 |
|
| 685 |
To support this message distribution, the SGP might, for example, |
| 686 |
maintain the equivalent of a network address translation table, |
| 687 |
mapping incoming SS7 message information to an Application Server for |
| 688 |
a particular application and range of traffic. This could be |
| 689 |
accomplished by comparing elements of the incoming SS7 message to |
| 690 |
currently defined Routing Keys in the SGP. |
| 691 |
|
| 692 |
These Routing Keys could in turn map directly to an Application |
| 693 |
Server that is enabled by one or more ASPs. These ASPs provide |
| 694 |
dynamic status information regarding their availability, traffic |
| 695 |
handling capability and congestion to the SGP using various |
| 696 |
management messages defined in the M3UA protocol. |
| 697 |
|
| 698 |
The list of ASPs in an AS is assumed to be dynamic, taking into |
| 699 |
account the availability, traffic handling capability and congestion |
| 700 |
status of the individual ASPs in the list, as well as configuration |
| 701 |
changes and possible failover mechanisms. |
| 702 |
|
| 703 |
Normally, one or more ASPs are active (i.e., currently processing |
| 704 |
traffic) in the AS but in certain failure and transition cases it is |
| 705 |
possible that there may be no active ASP available. Broadcast, |
| 706 |
loadsharing and backup scenarios are supported. |
| 707 |
|
| 708 |
When there is no matching Routing Key entry for an incoming SS7 |
| 709 |
message, a default treatment MAY be specified. Possible solutions |
| 710 |
are to provide a default Application Server at the SGP that directs |
| 711 |
all unallocated traffic to a (set of) default ASP(s), or to drop the |
| 712 |
message and provide a notification to layer management. The |
| 713 |
treatment of unallocated traffic is implementation dependent. |
| 714 |
|
| 715 |
|
| 716 |
|
| 717 |
|
| 718 |
|
| 719 |
|
| 720 |
|
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 13]</span></pre> |
| 725 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 726 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 727 |
|
| 728 |
|
| 729 |
<span class="h5"><a class="selflink" id="section-1.4.2.5" href="#section-1.4.2.5">1.4.2.5</a> Message Distribution at the ASP</span> |
| 730 |
|
| 731 |
The ASP must choose an SGP to direct a message to the SS7 network. |
| 732 |
This is accomplished by observing the Destination Point Code (and |
| 733 |
possibly other elements of the outgoing message such as the SLS |
| 734 |
value). The ASP must also take into account whether the related |
| 735 |
Routing Context is active or not (See <a href="#section-4.3.4.3">Section 4.3.4.3</a>). |
| 736 |
|
| 737 |
Implementation Note: Where more than one route (or SGP) is possible |
| 738 |
for routing to the SS7 network, the ASP could, for example, maintain |
| 739 |
a dynamic table of available SGP routes for the SS7 destinations, |
| 740 |
taking into account the SS7 destination |
| 741 |
availability/restricted/congestion status received from the SGP(s), |
| 742 |
the availability status of the individual SGPs and configuration |
| 743 |
changes and failover mechanisms. There is, however, no M3UA messaging |
| 744 |
to manage the status of an SGP (e.g., SGP-Up/Down/Active/Inactive |
| 745 |
messaging). |
| 746 |
|
| 747 |
Whenever an SCTP association to an SGP exists, the SGP is assumed to |
| 748 |
be ready for the purposes of responding to M3UA ASPSM messages (Refer |
| 749 |
to <a href="#section-3">Section 3</a>). |
| 750 |
|
| 751 |
<span class="h4"><a class="selflink" id="section-1.4.3" href="#section-1.4.3">1.4.3</a> SS7 and M3UA Interworking</span> |
| 752 |
|
| 753 |
In the case of SS7 and M3UA interworking, the M3UA adaptation layer |
| 754 |
is designed to provide an extension of the MTP3 defined user |
| 755 |
primitives. |
| 756 |
|
| 757 |
<span class="h5"><a class="selflink" id="section-1.4.3.1" href="#section-1.4.3.1">1.4.3.1</a> Signalling Gateway SS7 Layers</span> |
| 758 |
|
| 759 |
The SG is responsible for terminating MTP Level 3 of the SS7 |
| 760 |
protocol, and offering an IP-based extension to its users. |
| 761 |
|
| 762 |
From an SS7 perspective, it is expected that the Signalling Gateway |
| 763 |
transmits and receives SS7 Message Signalling Units (MSUs) to and |
| 764 |
from the PSTN over a standard SS7 network interface, using the SS7 |
| 765 |
Message Transfer Part (MTP) [<a href="#ref-7">7</a>,<a href="#ref-8">8</a>,<a href="#ref-9">9</a>] to provide reliable transport of |
| 766 |
the messages. |
| 767 |
|
| 768 |
As a standard SS7 network interface, the use of MTP Level 2 |
| 769 |
signalling links is not the only possibility. ATM-based High Speed |
| 770 |
Links can also be used with the services of the Signalling ATM |
| 771 |
Adaptation Layer (SAAL) [<a href="#ref-18">18</a>,<a href="#ref-19">19</a>]. |
| 772 |
|
| 773 |
Note: It is also possible for IP-based interfaces to be present, |
| 774 |
using the services of the MTP2-User Adaptation Layer (M2UA) [<a href="#ref-27" title=""Signaling System 7 (SS7) Message Transfer Part 2 (MTP2) - User Adaptation Layer"">27</a>] or |
| 775 |
M2PA [<a href="#ref-28" title=""SS7 MTP2-User Peer-to-Peer Adaptation Layer"">28</a>]. |
| 776 |
|
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 14]</span></pre> |
| 781 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span> |
| 782 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 783 |
|
| 784 |
|
| 785 |
These could be terminated at a Signalling Transfer Point (STP) or |
| 786 |
Signalling End Point (SEP). Using the services of MTP3, the SG could |
| 787 |
be capable of communicating with remote SS7 SEPs in a quasi- |
| 788 |
associated fashion, where STPs may be present in the SS7 path between |
| 789 |
the SEP and the SG. |
| 790 |
|
| 791 |
<span class="h5"><a class="selflink" id="section-1.4.3.2" href="#section-1.4.3.2">1.4.3.2</a> SS7 and M3UA Interworking at the SG</span> |
| 792 |
|
| 793 |
The SGP provides a functional interworking of transport functions |
| 794 |
between the SS7 network and the IP network by also supporting the |
| 795 |
M3UA adaptation layer. It allows the transfer of MTP3-User |
| 796 |
signalling messages to and from an IP-based Application Server |
| 797 |
Process where the peer MTP3-User protocol layer exists. |
| 798 |
|
| 799 |
For SS7 user part management, it is required that the MTP3-User |
| 800 |
protocols at ASPs receive indications of SS7 signalling point |
| 801 |
availability, SS7 network congestion, and remote User Part |
| 802 |
unavailability as would be expected in an SS7 SEP node. To |
| 803 |
accomplish this, the MTP-PAUSE, MTP-RESUME and MTP-STATUS indication |
| 804 |
primitives received at the MTP3 upper layer interface at the SG need |
| 805 |
to be propagated to the remote MTP3-User lower layer interface at the |
| 806 |
ASP. |
| 807 |
|
| 808 |
MTP3 management messages (such as TFPs or TFAs received from the SS7 |
| 809 |
network) MUST NOT be encapsulated as Data message Payload Data and |
| 810 |
sent either from SG to ASP or from ASP to SG. The SG MUST terminate |
| 811 |
these messages and generate M3UA messages as appropriate. |
| 812 |
|
| 813 |
<span class="h5"><a class="selflink" id="section-1.4.3.3" href="#section-1.4.3.3">1.4.3.3</a> Application Server</span> |
| 814 |
|
| 815 |
A cluster of application servers is responsible for providing the |
| 816 |
overall support for one or more SS7 upper layers. From an SS7 |
| 817 |
standpoint, a Signalling Point Management Cluster (SPMC) provides |
| 818 |
complete support for the upper layer service for a given point code. |
| 819 |
As an example, an SPMC providing MGC capabilities could provide |
| 820 |
complete support for ISUP (and any other MTP3 user located at the |
| 821 |
point code of the SPMC) for a given point code. |
| 822 |
|
| 823 |
In the case where an ASP is connected to more than one SGP, the M3UA |
| 824 |
layer must maintain the status of configured SS7 destinations and |
| 825 |
route messages according to availability/congestion/restricted status |
| 826 |
of the routes to these SS7 destinations. |
| 827 |
|
| 828 |
<span class="h5"><a class="selflink" id="section-1.4.3.4" href="#section-1.4.3.4">1.4.3.4</a> IPSP Considerations</span> |
| 829 |
|
| 830 |
Since IPSPs use M3UA in a point-to-point fashion, there is no concept |
| 831 |
of routing of messages beyond the remote end. Therefore, SS7 and |
| 832 |
M3UA interworking is not necessary for this model. |
| 833 |
|
| 834 |
|
| 835 |
|
| 836 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 15]</span></pre> |
| 837 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span> |
| 838 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 839 |
|
| 840 |
|
| 841 |
<span class="h4"><a class="selflink" id="section-1.4.4" href="#section-1.4.4">1.4.4</a> Redundancy Models</span> |
| 842 |
|
| 843 |
<span class="h5"><a class="selflink" id="section-1.4.4.1" href="#section-1.4.4.1">1.4.4.1</a> Application Server Redundancy</span> |
| 844 |
|
| 845 |
All MTP3-User messages (e.g., ISUP, SCCP) which match a provisioned |
| 846 |
Routing Key at an SGP are mapped to an Application Server. |
| 847 |
|
| 848 |
The Application Server is the set of all ASPs associated with a |
| 849 |
specific Routing Key. Each ASP in this set may be active, inactive or |
| 850 |
unavailable. Active ASPs handle traffic; inactive ASPs might be used |
| 851 |
when active ASPs become unavailable. |
| 852 |
|
| 853 |
The failover model supports an "n+k" redundancy model, where "n" ASPs |
| 854 |
is the minimum number of redundant ASPs required to handle traffic |
| 855 |
and "k" ASPs are available to take over for a failed or unavailable |
| 856 |
ASP. A "1+1" active/backup redundancy is a subset of this model. A |
| 857 |
simplex "1+0" model is also supported as a subset, with no ASP |
| 858 |
redundancy. |
| 859 |
|
| 860 |
<span class="h4"><a class="selflink" id="section-1.4.5" href="#section-1.4.5">1.4.5</a> Flow Control</span> |
| 861 |
|
| 862 |
Local Management at an ASP may wish to stop traffic across an SCTP |
| 863 |
association to temporarily remove the association from service or to |
| 864 |
perform testing and maintenance activity. The function could |
| 865 |
optionally be used to control the start of traffic on to a newly |
| 866 |
available SCTP association. |
| 867 |
|
| 868 |
<span class="h4"><a class="selflink" id="section-1.4.6" href="#section-1.4.6">1.4.6</a> Congestion Management</span> |
| 869 |
|
| 870 |
The M3UA layer is informed of local and IP network congestion by |
| 871 |
means of an implementation-dependent function (e.g., an |
| 872 |
implementation dependent indication from the SCTP of IP network |
| 873 |
congestion). |
| 874 |
|
| 875 |
At an ASP or IPSP, the M3UA layer indicates congestion to local |
| 876 |
MTP3-Users by means of an MTP-STATUS primitive, as per current MTP3 |
| 877 |
procedures, to invoke appropriate upper layer responses. |
| 878 |
|
| 879 |
When an SG determines that the transport of SS7 messages to a |
| 880 |
Signalling Point Management Cluster (SPMC) is encountering |
| 881 |
congestion, the SG MAY trigger SS7 MTP3 Transfer Controlled |
| 882 |
management messages to originating SS7 nodes, per the congestion |
| 883 |
procedures of the relevant MTP3 standard. The triggering of SS7 MTP3 |
| 884 |
Management messages from an SG is an implementation-dependent |
| 885 |
function. |
| 886 |
|
| 887 |
|
| 888 |
|
| 889 |
|
| 890 |
|
| 891 |
|
| 892 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 16]</span></pre> |
| 893 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span> |
| 894 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 895 |
|
| 896 |
|
| 897 |
The M3UA layer at an ASP or IPSP MAY indicate local congestion to an |
| 898 |
M3UA peer with an SCON message. When an SG receives a congestion |
| 899 |
message (SCON) from an ASP, and the SG determines that an SPMC is now |
| 900 |
encountering congestion, it MAY trigger SS7 MTP3 Transfer Controlled |
| 901 |
management messages to concerned SS7 destinations according to |
| 902 |
congestion procedures of the relevant MTP3 standard. |
| 903 |
|
| 904 |
<span class="h4"><a class="selflink" id="section-1.4.7" href="#section-1.4.7">1.4.7</a> SCTP Stream Mapping.</span> |
| 905 |
|
| 906 |
The M3UA layer at both the SGP and ASP also supports the assignment |
| 907 |
of signalling traffic into streams within an SCTP association. |
| 908 |
Traffic that requires sequencing SHOULD be assigned to the same |
| 909 |
stream. To accomplish this, MTP3-User traffic may be assigned to |
| 910 |
individual streams based on, for example, the SLS value in the MTP3 |
| 911 |
Routing Label or the ISUP CIC assignment, subject of course to the |
| 912 |
maximum number of streams supported by the underlying SCTP |
| 913 |
association. |
| 914 |
|
| 915 |
<span class="h4"><a class="selflink" id="section-1.4.8" href="#section-1.4.8">1.4.8</a> Client/Server Model</span> |
| 916 |
|
| 917 |
It is recommended that the SGP and ASP be able to support both client |
| 918 |
and server operation. The peer endpoints using M3UA SHOULD be |
| 919 |
configured so that one always takes on the role of client and the |
| 920 |
other the role of server for initiating SCTP associations. The |
| 921 |
default orientation would be for the SGP to take on the role of |
| 922 |
server while the ASP is the client. In this case, ASPs SHOULD |
| 923 |
initiate the SCTP association to the SGP. |
| 924 |
|
| 925 |
In the case of IPSP to IPSP communication, the peer endpoints using |
| 926 |
M3UA SHOULD be configured so that one always takes on the role of |
| 927 |
client and the other the role of server for initiating SCTP |
| 928 |
associations. |
| 929 |
|
| 930 |
The SCTP and TCP Registered User Port Number Assignment for M3UA is |
| 931 |
2905. |
| 932 |
|
| 933 |
|
| 934 |
|
| 935 |
|
| 936 |
|
| 937 |
|
| 938 |
|
| 939 |
|
| 940 |
|
| 941 |
|
| 942 |
|
| 943 |
|
| 944 |
|
| 945 |
|
| 946 |
|
| 947 |
|
| 948 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 17]</span></pre> |
| 949 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span> |
| 950 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 951 |
|
| 952 |
|
| 953 |
<span class="h3"><a class="selflink" id="section-1.5" href="#section-1.5">1.5</a> Sample Configuration</span> |
| 954 |
|
| 955 |
<span class="h4"><a class="selflink" id="section-1.5.1" href="#section-1.5.1">1.5.1</a> Example 1: ISUP Message Transport</span> |
| 956 |
|
| 957 |
******** SS7 ***************** IP ******** |
| 958 |
* SEP *---------* SGP *--------* ASP * |
| 959 |
******** ***************** ******** |
| 960 |
|
| 961 |
+------+ +---------------+ +------+ |
| 962 |
| ISUP | | (NIF) | | ISUP | |
| 963 |
+------+ +------+ +------+ +------+ |
| 964 |
| MTP3 | | MTP3 | | M3UA | | M3UA | |
| 965 |
+------| +------+-+------+ +------+ |
| 966 |
| MTP2 | | MTP2 | | SCTP | | SCTP | |
| 967 |
+------+ +------+ +------+ +------+ |
| 968 |
| L1 | | L1 | | IP | | IP | |
| 969 |
+------+ +------+ +------+ +------+ |
| 970 |
|_______________| |______________| |
| 971 |
|
| 972 |
|
| 973 |
SEP - SS7 Signalling End Point |
| 974 |
SCTP - Stream Control Transmission Protocol |
| 975 |
NIF - Nodal Interworking Function |
| 976 |
|
| 977 |
In this example, the SGP provides an implementation-dependent nodal |
| 978 |
interworking function (NIF) that allows the MGC to exchange SS7 |
| 979 |
signalling messages with the SS7-based SEP. The NIF within the SGP |
| 980 |
serves as the interface within the SGP between the MTP3 and M3UA. |
| 981 |
This nodal interworking function has no visible peer protocol with |
| 982 |
either the MGC or SEP. It also provides network status information |
| 983 |
to one or both sides of the network. |
| 984 |
|
| 985 |
For internal SGP modeling purposes, at the NIF level, SS7 signalling |
| 986 |
messages that are destined to the MGC are received as MTP-TRANSFER |
| 987 |
indication primitives from the MTP Level 3 upper layer interface, |
| 988 |
translated to MTP-TRANSFER request primitives, and sent to the local |
| 989 |
M3UA-resident message distribution function for ongoing routing to |
| 990 |
the final IP destination. Messages received from the local M3UA |
| 991 |
network address translation and mapping function as MTP-TRANSFER |
| 992 |
indication primitives are sent to the MTP Level 3 upper layer |
| 993 |
interface as MTP-TRANSFER request primitives for ongoing MTP Level 3 |
| 994 |
routing to an SS7 SEP. For the purposes of providing SS7 network |
| 995 |
status information the NIF also delivers MTP-PAUSE, MTP-RESUME and |
| 996 |
MTP-STATUS indication primitives received from the MTP Level 3 upper |
| 997 |
layer interface to the local M3UA-resident management function. In |
| 998 |
addition, as an implementation and network option, restricted |
| 999 |
destinations are communicated from MTP network management to the |
| 1000 |
local M3UA-resident management function. |
| 1001 |
|
| 1002 |
|
| 1003 |
|
| 1004 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 18]</span></pre> |
| 1005 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span> |
| 1006 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 1007 |
|
| 1008 |
|
| 1009 |
<span class="h4"><a class="selflink" id="section-1.5.2" href="#section-1.5.2">1.5.2</a> Example 2: SCCP Transport between IPSPs</span> |
| 1010 |
|
| 1011 |
******** IP ******** |
| 1012 |
* IPSP * * IPSP * |
| 1013 |
******** ******** |
| 1014 |
|
| 1015 |
+------+ +------+ |
| 1016 |
|SCCP- | |SCCP- | |
| 1017 |
| User | | User | |
| 1018 |
+------+ +------+ |
| 1019 |
| SCCP | | SCCP | |
| 1020 |
+------+ +------+ |
| 1021 |
| M3UA | | M3UA | |
| 1022 |
+------+ +------+ |
| 1023 |
| SCTP | | SCTP | |
| 1024 |
+------+ +------+ |
| 1025 |
| IP | | IP | |
| 1026 |
+------+ +------+ |
| 1027 |
|________________| |
| 1028 |
|
| 1029 |
This example shows an architecture where no Signalling Gateway is |
| 1030 |
used. In this example, SCCP messages are exchanged directly between |
| 1031 |
two IP-resident IPSPs with resident SCCP-User protocol instances, |
| 1032 |
such as RANAP or TCAP. SS7 network interworking is not required, |
| 1033 |
therefore there is no MTP3 network management status information for |
| 1034 |
the SCCP and SCCP-User protocols to consider. Any MTP-PAUSE, MTP- |
| 1035 |
RESUME or MTP-STATUS indications from the M3UA layer to the SCCP |
| 1036 |
layer should consider the status of the SCTP Association and |
| 1037 |
underlying IP network and any congestion information received from |
| 1038 |
the remote site. |
| 1039 |
|
| 1040 |
|
| 1041 |
|
| 1042 |
|
| 1043 |
|
| 1044 |
|
| 1045 |
|
| 1046 |
|
| 1047 |
|
| 1048 |
|
| 1049 |
|
| 1050 |
|
| 1051 |
|
| 1052 |
|
| 1053 |
|
| 1054 |
|
| 1055 |
|
| 1056 |
|
| 1057 |
|
| 1058 |
|
| 1059 |
|
| 1060 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 19]</span></pre> |
| 1061 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span> |
| 1062 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 1063 |
|
| 1064 |
|
| 1065 |
<span class="h4"><a class="selflink" id="section-1.5.3" href="#section-1.5.3">1.5.3</a> Example 3: SGP Resident SCCP Layer, with Remote ASP</span> |
| 1066 |
|
| 1067 |
******** SS7 ***************** IP ******** |
| 1068 |
* SEP *---------* *--------* * |
| 1069 |
* or * * SGP * * ASP * |
| 1070 |
* STP * * * * * |
| 1071 |
******** ***************** ******** |
| 1072 |
|
| 1073 |
+------+ +---------------+ +------+ |
| 1074 |
| SCCP-| | SCCP | | SCCP-| |
| 1075 |
| User | +---------------+ | User | |
| 1076 |
+------+ | _____ | +------+ |
| 1077 |
| SCCP | | | | | | SCCP | |
| 1078 |
+------+ +------+-+------+ +------+ |
| 1079 |
| MTP3 | | MTP3 | | M3UA | | M3UA | |
| 1080 |
+------| +------+ +------+ +------+ |
| 1081 |
| MTP2 | | MTP2 | | SCTP | | SCTP | |
| 1082 |
+------+ +------+ +------+ +------+ |
| 1083 |
| L1 | | L1 | | IP | | IP | |
| 1084 |
+------+ +------+ +------+ +------+ |
| 1085 |
|_______________| |______________| |
| 1086 |
|
| 1087 |
STP - SS7 Signalling Transfer Point |
| 1088 |
|
| 1089 |
In this example, the SGP contains an instance of the SS7 SCCP |
| 1090 |
protocol layer that may, for example, perform the SCCP Global Title |
| 1091 |
Translation (GTT) function for messages logically addressed to the SG |
| 1092 |
SCCP. If the result of a GTT for an SCCP message yields an SS7 DPC |
| 1093 |
or DPC/SSN address of an SCCP peer located in the IP domain, the |
| 1094 |
resulting MTP-TRANSFER request primitive is sent to the local M3UA- |
| 1095 |
resident network address translation and mapping function for ongoing |
| 1096 |
routing to the final IP destination. |
| 1097 |
|
| 1098 |
Similarly, the SCCP instance in an SGP can perform the SCCP GTT |
| 1099 |
service for messages logically addressed to it from SCCP peers in the |
| 1100 |
IP domain. In this case, MTP-TRANSFER indication primitives are sent |
| 1101 |
from the local M3UA-resident network address translation and mapping |
| 1102 |
function to the SCCP for GTT. If the result of the GTT yields the |
| 1103 |
address of an SCCP peer in the SS7 network then the resulting MTP- |
| 1104 |
TRANSFER request primitive is given to the MTP3 for delivery to an |
| 1105 |
SS7-resident node. |
| 1106 |
|
| 1107 |
It is possible that the above SCCP GTT at the SGP could yield the |
| 1108 |
address of an SCCP peer in the IP domain and the resulting MTP- |
| 1109 |
TRANSFER request primitive would be sent back to the M3UA layer for |
| 1110 |
delivery to an IP destination. |
| 1111 |
|
| 1112 |
|
| 1113 |
|
| 1114 |
|
| 1115 |
|
| 1116 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 20]</span></pre> |
| 1117 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span> |
| 1118 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 1119 |
|
| 1120 |
|
| 1121 |
For internal SGP modeling purposes, this may be accomplished with the |
| 1122 |
use of an implementation-dependent nodal interworking function within |
| 1123 |
the SGP that effectively sits below the SCCP and routes MTP-TRANSFER |
| 1124 |
request/indication messages to/from both the MTP3 and the M3UA layer, |
| 1125 |
based on the SS7 DPC or DPC/SSN address information. This nodal |
| 1126 |
interworking function has no visible peer protocol with either the |
| 1127 |
ASP or SEP. |
| 1128 |
|
| 1129 |
Note that the services and interface provided by the M3UA layer are |
| 1130 |
the same as in Example 1 and the functions taking place in the SCCP |
| 1131 |
entity are transparent to the M3UA layer. The SCCP protocol |
| 1132 |
functions are not reproduced in the M3UA protocol. |
| 1133 |
|
| 1134 |
<span class="h3"><a class="selflink" id="section-1.6" href="#section-1.6">1.6</a> Definition of M3UA Boundaries</span> |
| 1135 |
|
| 1136 |
<span class="h4"><a class="selflink" id="section-1.6.1" href="#section-1.6.1">1.6.1</a> Definition of the Boundary between M3UA and an MTP3-User.</span> |
| 1137 |
|
| 1138 |
From ITU Q.701 [<a href="#ref-7">7</a>]: |
| 1139 |
|
| 1140 |
MTP-TRANSFER request |
| 1141 |
MTP-TRANSFER indication |
| 1142 |
MTP-PAUSE indication |
| 1143 |
MTP-RESUME indication |
| 1144 |
MTP-STATUS indication |
| 1145 |
|
| 1146 |
<span class="h4"><a class="selflink" id="section-1.6.2" href="#section-1.6.2">1.6.2</a> Definition of the Boundary between M3UA and SCTP</span> |
| 1147 |
|
| 1148 |
An example of the upper layer primitives provided by the SCTP are |
| 1149 |
provided in Reference [<a href="#ref-17" title=""Stream Control Transport Protocol"">17</a>] <a href="#section-10">Section 10</a>. |
| 1150 |
|
| 1151 |
<span class="h4"><a class="selflink" id="section-1.6.3" href="#section-1.6.3">1.6.3</a> Definition of the Boundary between M3UA and Layer Management</span> |
| 1152 |
|
| 1153 |
M-SCTP_ESTABLISH request |
| 1154 |
Direction: LM -> M3UA |
| 1155 |
Purpose: LM requests ASP to establish an SCTP association with its |
| 1156 |
peer. |
| 1157 |
|
| 1158 |
M-STCP_ESTABLISH confirm |
| 1159 |
Direction: M3UA -> LM |
| 1160 |
Purpose: ASP confirms to LM that it has established an SCTP |
| 1161 |
association with its peer. |
| 1162 |
|
| 1163 |
M-SCTP_ESTABLISH indication |
| 1164 |
Direction: M3UA -> LM |
| 1165 |
Purpose: M3UA informs LM that a remote ASP has established an SCTP |
| 1166 |
association. |
| 1167 |
|
| 1168 |
|
| 1169 |
|
| 1170 |
|
| 1171 |
|
| 1172 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 21]</span></pre> |
| 1173 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span> |
| 1174 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 1175 |
|
| 1176 |
|
| 1177 |
M-SCTP_RELEASE request |
| 1178 |
Direction: LM -> M3UA |
| 1179 |
Purpose: LM requests ASP to release an SCTP association with its |
| 1180 |
peer. |
| 1181 |
|
| 1182 |
M-SCTP_RELEASE confirm |
| 1183 |
Direction: M3UA -> LM |
| 1184 |
Purpose: ASP confirms to LM that it has released SCTP association |
| 1185 |
with its peer. |
| 1186 |
|
| 1187 |
M-SCTP_RELEASE indication |
| 1188 |
Direction: M3UA -> LM |
| 1189 |
Purpose: M3UA informs LM that a remote ASP has released an SCTP |
| 1190 |
Association or the SCTP association has failed. |
| 1191 |
|
| 1192 |
M-SCTP_RESTART indication |
| 1193 |
Direction: M3UA -> LM |
| 1194 |
Purpose: M3UA informs LM that an SCTP restart indication has been |
| 1195 |
received. |
| 1196 |
|
| 1197 |
M-SCTP_STATUS request |
| 1198 |
Direction: LM -> M3UA |
| 1199 |
Purpose: LM requests M3UA to report the status of an SCTP |
| 1200 |
association. |
| 1201 |
|
| 1202 |
M-SCTP_STATUS confirm |
| 1203 |
Direction: M3UA -> LM |
| 1204 |
Purpose: M3UA responds with the status of an SCTP association. |
| 1205 |
|
| 1206 |
|
| 1207 |
M-SCTP STATUS indication |
| 1208 |
Direction: M3UA -> LM |
| 1209 |
Purpose: M3UA reports the status of an SCTP association. |
| 1210 |
|
| 1211 |
M-ASP_STATUS request |
| 1212 |
Direction: LM -> M3UA |
| 1213 |
Purpose: LM requests M3UA to report the status of a local or remote |
| 1214 |
ASP. |
| 1215 |
|
| 1216 |
M-ASP_STATUS confirm |
| 1217 |
Direction: M3UA -> LM |
| 1218 |
Purpose: M3UA reports status of local or remote ASP. |
| 1219 |
|
| 1220 |
M-AS_STATUS request |
| 1221 |
Direction: LM -> M3UA |
| 1222 |
Purpose: LM requests M3UA to report the status of an AS. |
| 1223 |
|
| 1224 |
|
| 1225 |
|
| 1226 |
|
| 1227 |
|
| 1228 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 22]</span></pre> |
| 1229 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span> |
| 1230 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 1231 |
|
| 1232 |
|
| 1233 |
M-AS_STATUS confirm |
| 1234 |
Direction: M3UA -> LM |
| 1235 |
Purpose: M3UA reports the status of an AS. |
| 1236 |
|
| 1237 |
M-NOTIFY indication |
| 1238 |
Direction: M3UA -> LM |
| 1239 |
Purpose: M3UA reports that it has received a Notify message |
| 1240 |
from its peer. |
| 1241 |
|
| 1242 |
M-ERROR indication |
| 1243 |
Direction: M3UA -> LM |
| 1244 |
Purpose: M3UA reports that it has received an Error message from |
| 1245 |
its peer or that a local operation has been unsuccessful. |
| 1246 |
|
| 1247 |
M-ASP_UP request |
| 1248 |
Direction: LM -> M3UA |
| 1249 |
Purpose: LM requests ASP to start its operation and send an ASP Up |
| 1250 |
message to its peer. |
| 1251 |
|
| 1252 |
M-ASP_UP confirm |
| 1253 |
Direction: M3UA -> LM |
| 1254 |
Purpose: ASP reports that is has received an ASP UP Ack message from |
| 1255 |
its peer. |
| 1256 |
|
| 1257 |
M-ASP_UP indication |
| 1258 |
Direction: M3UA -> LM |
| 1259 |
Purpose: M3UA reports it has successfully processed an incoming ASP |
| 1260 |
Up message from its peer. |
| 1261 |
|
| 1262 |
M-ASP_DOWN request |
| 1263 |
Direction: LM -> M3UA |
| 1264 |
Purpose: LM requests ASP to stop its operation and send an ASP Down |
| 1265 |
message to its peer. |
| 1266 |
|
| 1267 |
M-ASP_DOWN confirm |
| 1268 |
Direction: M3UA -> LM |
| 1269 |
Purpose: ASP reports that is has received an ASP Down Ack message |
| 1270 |
from its peer. |
| 1271 |
|
| 1272 |
M-ASP_DOWN indication |
| 1273 |
Direction: M3UA -> LM |
| 1274 |
Purpose: M3UA reports it has successfully processed an incoming ASP |
| 1275 |
Down message from its peer, or the SCTP association has |
| 1276 |
been lost/reset. |
| 1277 |
|
| 1278 |
|
| 1279 |
|
| 1280 |
|
| 1281 |
|
| 1282 |
|
| 1283 |
|
| 1284 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 23]</span></pre> |
| 1285 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span> |
| 1286 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 1287 |
|
| 1288 |
|
| 1289 |
M-ASP_ACTIVE request |
| 1290 |
Direction: LM -> M3UA |
| 1291 |
Purpose: LM requests ASP to send an ASP Active message to its peer. |
| 1292 |
|
| 1293 |
M-ASP_ACTIVE confirm |
| 1294 |
Direction: M3UA -> LM |
| 1295 |
Purpose: ASP reports that is has received an ASP Active |
| 1296 |
Ack message from its peer. |
| 1297 |
|
| 1298 |
M-ASP_ACTIVE indication |
| 1299 |
Direction: M3UA -> LM |
| 1300 |
Purpose: M3UA reports it has successfully processed an incoming ASP |
| 1301 |
Active message from its peer. |
| 1302 |
|
| 1303 |
M-ASP_INACTIVE request |
| 1304 |
Direction: LM -> M3UA |
| 1305 |
Purpose: LM requests ASP to send an ASP Inactive message to its |
| 1306 |
peer. |
| 1307 |
|
| 1308 |
M-ASP_INACTIVE confirm |
| 1309 |
Direction: LM -> M3UA |
| 1310 |
Purpose: ASP reports that is has received an ASP Inactive |
| 1311 |
Ack message from its peer. |
| 1312 |
|
| 1313 |
M-ASP_INACTIVE indication |
| 1314 |
Direction: M3UA -> LM |
| 1315 |
Purpose: M3UA reports it has successfully processed an incoming ASP |
| 1316 |
Inactive message from its peer. |
| 1317 |
|
| 1318 |
M-AS_ACTIVE indication |
| 1319 |
Direction: M3UA -> LM |
| 1320 |
Purpose: M3UA reports that an AS has moved to the AS-ACTIVE state. |
| 1321 |
|
| 1322 |
M-AS_INACTIVE indication |
| 1323 |
Direction: M3UA -> LM |
| 1324 |
Purpose: M3UA reports that an AS has moved to the AS-INACTIVE state. |
| 1325 |
|
| 1326 |
M-AS_DOWN indication |
| 1327 |
Direction: M3UA -> LM |
| 1328 |
Purpose: M3UA reports that an AS has moved to the AS-DOWN state. |
| 1329 |
|
| 1330 |
If dynamic registration of RK is supported by the M3UA layer, the |
| 1331 |
layer MAY support the following additional primitives: |
| 1332 |
|
| 1333 |
M-RK_REG request |
| 1334 |
Direction: LM -> M3UA |
| 1335 |
Purpose: LM requests ASP to register RK(s) with its peer by sending |
| 1336 |
REG REQ message |
| 1337 |
|
| 1338 |
|
| 1339 |
|
| 1340 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 24]</span></pre> |
| 1341 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span> |
| 1342 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 1343 |
|
| 1344 |
|
| 1345 |
M-RK_REG confirm |
| 1346 |
Direction: M3UA -> LM |
| 1347 |
Purpose: ASP reports that it has received REG RSP message with |
| 1348 |
registration status as successful from its peer. |
| 1349 |
|
| 1350 |
M-RK_REG indication |
| 1351 |
Direction: M3UA -> LM |
| 1352 |
Purpose: M3UA informs LM that it has successfully processed an |
| 1353 |
incoming REG REQ message. |
| 1354 |
|
| 1355 |
M-RK_DEREG request |
| 1356 |
Direction: LM -> M3UA |
| 1357 |
Purpose: LM requests ASP to deregister RK(s) with its peer by |
| 1358 |
sending DEREG REQ message. |
| 1359 |
|
| 1360 |
M-RK_DEREG confirm |
| 1361 |
Direction: M3UA -> LM |
| 1362 |
Purpose: ASP reports that it has received DEREG REQ message with |
| 1363 |
deregistration status as successful from its peer. |
| 1364 |
|
| 1365 |
M-RK_DEREG indication |
| 1366 |
Direction: M3UA -> LM |
| 1367 |
Purpose: M3UA informs LM that it has successfully processed an |
| 1368 |
incoming DEREG REQ from its peer. |
| 1369 |
|
| 1370 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Conventions</span> |
| 1371 |
|
| 1372 |
The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, |
| 1373 |
SHOULD NOT, RECOMMENDED, NOT RECOMMENDED, MAY, and OPTIONAL, when |
| 1374 |
they appear in this document, are to be interpreted as described in |
| 1375 |
[<a href="#ref-20" title=""Key words for use in RFCs to Indicate Requirement Levels"">20</a>]. |
| 1376 |
|
| 1377 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. M3UA Protocol Elements</span> |
| 1378 |
|
| 1379 |
The general M3UA message format includes a Common Message Header |
| 1380 |
followed by zero or more parameters as defined by the Message Type. |
| 1381 |
For forward compatibility, all Message Types may have attached |
| 1382 |
parameters even if none are specified in this version. |
| 1383 |
|
| 1384 |
|
| 1385 |
|
| 1386 |
|
| 1387 |
|
| 1388 |
|
| 1389 |
|
| 1390 |
|
| 1391 |
|
| 1392 |
|
| 1393 |
|
| 1394 |
|
| 1395 |
|
| 1396 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 25]</span></pre> |
| 1397 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span> |
| 1398 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 1399 |
|
| 1400 |
|
| 1401 |
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a> Common Message Header</span> |
| 1402 |
|
| 1403 |
The protocol messages for MTP3-User Adaptation require a message |
| 1404 |
header which contains the adaptation layer version, the message type, |
| 1405 |
and message length. |
| 1406 |
|
| 1407 |
0 1 2 3 |
| 1408 |
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 |
| 1409 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1410 |
| Version | Reserved | Message Class | Message Type | |
| 1411 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1412 |
| Message Length | |
| 1413 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1414 |
\ \ |
| 1415 |
/ / |
| 1416 |
|
| 1417 |
All fields in an M3UA message MUST be transmitted in the network byte |
| 1418 |
order, unless otherwise stated. |
| 1419 |
|
| 1420 |
<span class="h4"><a class="selflink" id="section-3.1.1" href="#section-3.1.1">3.1.1</a> M3UA Protocol Version: 8 bits (unsigned integer)</span> |
| 1421 |
|
| 1422 |
The version field contains the version of the M3UA adaptation layer. |
| 1423 |
|
| 1424 |
The supported versions are the following: |
| 1425 |
|
| 1426 |
1 Release 1.0 |
| 1427 |
|
| 1428 |
<span class="h4"><a class="selflink" id="section-3.1.2" href="#section-3.1.2">3.1.2</a> Message Classes and Types</span> |
| 1429 |
|
| 1430 |
The following list contains the valid Message Classes: |
| 1431 |
|
| 1432 |
Message Class: 8 bits (unsigned integer) |
| 1433 |
|
| 1434 |
The following list contains the valid Message Type Classes: |
| 1435 |
|
| 1436 |
0 Management (MGMT) Messages |
| 1437 |
1 Transfer Messages |
| 1438 |
2 SS7 Signalling Network Management (SSNM) Messages |
| 1439 |
3 ASP State Maintenance (ASPSM) Messages |
| 1440 |
4 ASP Traffic Maintenance (ASPTM) Messages |
| 1441 |
5 Reserved for Other Sigtran Adaptation Layers |
| 1442 |
6 Reserved for Other Sigtran Adaptation Layers |
| 1443 |
7 Reserved for Other Sigtran Adaptation Layers |
| 1444 |
8 Reserved for Other Sigtran Adaptation Layers |
| 1445 |
9 Routing Key Management (RKM) Messages |
| 1446 |
10 to 127 Reserved by the IETF |
| 1447 |
128 to 255 Reserved for IETF-Defined Message Class extensions |
| 1448 |
|
| 1449 |
|
| 1450 |
|
| 1451 |
|
| 1452 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 26]</span></pre> |
| 1453 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span> |
| 1454 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 1455 |
|
| 1456 |
|
| 1457 |
Message Type: 8 bits (unsigned integer) |
| 1458 |
|
| 1459 |
The following list contains the message types for the defined |
| 1460 |
messages. |
| 1461 |
|
| 1462 |
Management (MGMT) Messages (See <a href="#section-3.8">Section 3.8</a>) |
| 1463 |
|
| 1464 |
0 Error (ERR) |
| 1465 |
1 Notify (NTFY) |
| 1466 |
2 to 127 Reserved by the IETF |
| 1467 |
128 to 255 Reserved for IETF-Defined MGMT extensions |
| 1468 |
|
| 1469 |
Transfer Messages (See <a href="#section-3.3">Section 3.3</a>) |
| 1470 |
|
| 1471 |
0 Reserved |
| 1472 |
1 Payload Data (DATA) |
| 1473 |
2 to 127 Reserved by the IETF |
| 1474 |
128 to 255 Reserved for IETF-Defined Transfer extensions |
| 1475 |
|
| 1476 |
SS7 Signalling Network Management (SSNM) Messages (See <a href="#section-3.4">Section</a> |
| 1477 |
<a href="#section-3.4">3.4</a>) |
| 1478 |
|
| 1479 |
0 Reserved |
| 1480 |
1 Destination Unavailable (DUNA) |
| 1481 |
2 Destination Available (DAVA) |
| 1482 |
3 Destination State Audit (DAUD) |
| 1483 |
4 Signalling Congestion (SCON) |
| 1484 |
5 Destination User Part Unavailable (DUPU) |
| 1485 |
6 Destination Restricted (DRST) |
| 1486 |
7 to 127 Reserved by the IETF |
| 1487 |
128 to 255 Reserved for IETF-Defined SSNM extensions |
| 1488 |
|
| 1489 |
ASP State Maintenance (ASPSM) Messages (See <a href="#section-3.5">Section 3.5</a>) |
| 1490 |
|
| 1491 |
0 Reserved |
| 1492 |
1 ASP Up (ASPUP) |
| 1493 |
2 ASP Down (ASPDN) |
| 1494 |
3 Heartbeat (BEAT) |
| 1495 |
4 ASP Up Acknowledgement (ASPUP ACK) |
| 1496 |
5 ASP Down Acknowledgement (ASPDN ACK) |
| 1497 |
6 Heartbeat Acknowledgement (BEAT ACK) |
| 1498 |
7 to 127 Reserved by the IETF |
| 1499 |
128 to 255 Reserved for IETF-Defined ASPSM extensions |
| 1500 |
|
| 1501 |
|
| 1502 |
|
| 1503 |
|
| 1504 |
|
| 1505 |
|
| 1506 |
|
| 1507 |
|
| 1508 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 27]</span></pre> |
| 1509 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span> |
| 1510 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 1511 |
|
| 1512 |
|
| 1513 |
ASP Traffic Maintenance (ASPTM) Messages (See <a href="#section-3.7">Section 3.7</a>) |
| 1514 |
|
| 1515 |
0 Reserved |
| 1516 |
1 ASP Active (ASPAC) |
| 1517 |
2 ASP Inactive (ASPIA) |
| 1518 |
3 ASP Active Acknowledgement (ASPAC ACK) |
| 1519 |
4 ASP Inactive Acknowledgement (ASPIA ACK) |
| 1520 |
5 to 127 Reserved by the IETF |
| 1521 |
128 to 255 Reserved for IETF-Defined ASPTM extensions |
| 1522 |
|
| 1523 |
Routing Key Management (RKM) Messages (See <a href="#section-3.6">Section 3.6</a>) |
| 1524 |
|
| 1525 |
0 Reserved |
| 1526 |
1 Registration Request (REG REQ) |
| 1527 |
2 Registration Response (REG RSP) |
| 1528 |
3 Deregistration Request (DEREG REQ) |
| 1529 |
4 Deregistration Response (DEREG RSP) |
| 1530 |
5 to 127 Reserved by the IETF |
| 1531 |
128 to 255 Reserved for IETF-Defined RKM extensions |
| 1532 |
|
| 1533 |
<span class="h4"><a class="selflink" id="section-3.1.3" href="#section-3.1.3">3.1.3</a> Reserved: 8 bits</span> |
| 1534 |
|
| 1535 |
The Reserved field SHOULD be set to all '0's and ignored by the |
| 1536 |
receiver. |
| 1537 |
|
| 1538 |
<span class="h4"><a class="selflink" id="section-3.1.4" href="#section-3.1.4">3.1.4</a> Message Length: 32-bits (unsigned integer)</span> |
| 1539 |
|
| 1540 |
The Message Length defines the length of the message in octets, |
| 1541 |
including the Common Header. The Message Length MUST include |
| 1542 |
parameter padding bytes, if any. |
| 1543 |
|
| 1544 |
Note: A receiver SHOULD accept the message whether or not the final |
| 1545 |
parameter padding is included in the message length. |
| 1546 |
|
| 1547 |
|
| 1548 |
|
| 1549 |
|
| 1550 |
|
| 1551 |
|
| 1552 |
|
| 1553 |
|
| 1554 |
|
| 1555 |
|
| 1556 |
|
| 1557 |
|
| 1558 |
|
| 1559 |
|
| 1560 |
|
| 1561 |
|
| 1562 |
|
| 1563 |
|
| 1564 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 28]</span></pre> |
| 1565 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span> |
| 1566 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 1567 |
|
| 1568 |
|
| 1569 |
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a> Variable Length Parameter Format</span> |
| 1570 |
|
| 1571 |
M3UA messages consist of a Common Header followed by zero or more |
| 1572 |
variable length parameters, as defined by the message type. All the |
| 1573 |
parameters contained in a message are defined in a Tag Length-Value |
| 1574 |
format as shown below. |
| 1575 |
|
| 1576 |
0 1 2 3 |
| 1577 |
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 |
| 1578 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1579 |
| Parameter Tag | Parameter Length | |
| 1580 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1581 |
\ \ |
| 1582 |
/ Parameter Value / |
| 1583 |
\ \ |
| 1584 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1585 |
|
| 1586 |
Where more than one parameter is included in a message, the |
| 1587 |
parameters may be in any order, except where explicitly mandated. A |
| 1588 |
receiver SHOULD accept the parameters in any order. |
| 1589 |
|
| 1590 |
Parameter Tag: 16 bits (unsigned integer) |
| 1591 |
|
| 1592 |
The Tag field is a 16-bit identifier of the type of parameter. It |
| 1593 |
takes a value of 0 to 65534. Common parameters used by adaptation |
| 1594 |
layers are in the range of 0x00 to 0x3f. M3UA-specific |
| 1595 |
parameters have Tags in the range 0x0200 to 0x02ff. The parameter |
| 1596 |
Tags defined are as follows: |
| 1597 |
|
| 1598 |
Common Parameters. These TLV parameters are common across the |
| 1599 |
different adaptation layers: |
| 1600 |
|
| 1601 |
Parameter Name Parameter ID |
| 1602 |
============== ============ |
| 1603 |
Reserved 0x0000 |
| 1604 |
Not Used in M3UA 0x0001 |
| 1605 |
Not Used in M3UA 0x0002 |
| 1606 |
Not Used in M3UA 0x0003 |
| 1607 |
INFO String 0x0004 |
| 1608 |
Not Used in M3UA 0x0005 |
| 1609 |
Routing Context 0x0006 |
| 1610 |
Diagnostic Information 0x0007 |
| 1611 |
Not Used in M3UA 0x0008 |
| 1612 |
Heartbeat Data 0x0009 |
| 1613 |
Not Used in M3UA 0x000a |
| 1614 |
Traffic Mode Type 0x000b |
| 1615 |
Error Code 0x000c |
| 1616 |
Status 0x000d |
| 1617 |
|
| 1618 |
|
| 1619 |
|
| 1620 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 29]</span></pre> |
| 1621 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span> |
| 1622 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 1623 |
|
| 1624 |
|
| 1625 |
Not Used in M3UA 0x000e |
| 1626 |
Not Used in M3UA 0x000f |
| 1627 |
Not Used in M3UA 0x0010 |
| 1628 |
ASP Identifier 0x0011 |
| 1629 |
Affected Point Code 0x0012 |
| 1630 |
Correlation ID 0x0013 |
| 1631 |
|
| 1632 |
M3UA-Specific parameters. These TLV parameters are specific to |
| 1633 |
the M3UA protocol: |
| 1634 |
|
| 1635 |
Network Appearance 0x0200 |
| 1636 |
Reserved 0x0201 |
| 1637 |
Reserved 0x0202 |
| 1638 |
Reserved 0x0203 |
| 1639 |
User/Cause 0x0204 |
| 1640 |
Congestion Indications 0x0205 |
| 1641 |
Concerned Destination 0x0206 |
| 1642 |
Routing Key 0x0207 |
| 1643 |
Registration Result 0x0208 |
| 1644 |
Deregistration Result 0x0209 |
| 1645 |
Local_Routing Key Identifier 0x020a |
| 1646 |
Destination Point Code 0x020b |
| 1647 |
Service Indicators 0x020c |
| 1648 |
Reserved 0x020d |
| 1649 |
Originating Point Code List 0x020e |
| 1650 |
Circuit Range 0x020f |
| 1651 |
Protocol Data 0x0210 |
| 1652 |
Reserved 0x0211 |
| 1653 |
Registration Status 0x0212 |
| 1654 |
Deregistration Status 0x0213 |
| 1655 |
|
| 1656 |
Reserved by the IETF 0x0214 to 0xffff |
| 1657 |
|
| 1658 |
The value of 65535 is reserved for IETF-defined extensions. |
| 1659 |
Values other than those defined in specific parameter description |
| 1660 |
are reserved for use by the IETF. |
| 1661 |
|
| 1662 |
Parameter Length: 16 bits (unsigned integer) |
| 1663 |
|
| 1664 |
The Parameter Length field contains the size of the parameter in |
| 1665 |
bytes, including the Parameter Tag, Parameter Length, and |
| 1666 |
Parameter Value fields. Thus, a parameter with a zero-length |
| 1667 |
Parameter Value field would have a Length field of 4. The |
| 1668 |
Parameter Length does not include any padding bytes. |
| 1669 |
|
| 1670 |
|
| 1671 |
|
| 1672 |
|
| 1673 |
|
| 1674 |
|
| 1675 |
|
| 1676 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 30]</span></pre> |
| 1677 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span> |
| 1678 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 1679 |
|
| 1680 |
|
| 1681 |
Parameter Value: variable length. |
| 1682 |
|
| 1683 |
The Parameter Value field contains the actual information to be |
| 1684 |
transferred in the parameter. |
| 1685 |
|
| 1686 |
The total length of a parameter (including Tag, Parameter Length |
| 1687 |
and Value fields) MUST be a multiple of 4 bytes. If the length of |
| 1688 |
the parameter is not a multiple of 4 bytes, the sender pads the |
| 1689 |
Parameter at the end (i.e., after the Parameter Value field) with |
| 1690 |
all zero bytes. The length of the padding is NOT included in the |
| 1691 |
parameter length field. A sender SHOULD NOT pad with more than 3 |
| 1692 |
bytes. The receiver MUST ignore the padding bytes. |
| 1693 |
|
| 1694 |
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a> Transfer Messages</span> |
| 1695 |
|
| 1696 |
The following section describes the Transfer messages and parameter |
| 1697 |
contents. |
| 1698 |
|
| 1699 |
<span class="h4"><a class="selflink" id="section-3.3.1" href="#section-3.3.1">3.3.1</a> Payload Data Message (DATA)</span> |
| 1700 |
|
| 1701 |
The DATA message contains the SS7 MTP3-User protocol data, which is |
| 1702 |
an MTP-TRANSFER primitive, including the complete MTP3 Routing Label. |
| 1703 |
The DATA message contains the following variable length parameters: |
| 1704 |
|
| 1705 |
Network Appearance Optional |
| 1706 |
Routing Context Optional |
| 1707 |
Protocol Data Mandatory |
| 1708 |
Correlation Id Optional |
| 1709 |
|
| 1710 |
|
| 1711 |
|
| 1712 |
|
| 1713 |
|
| 1714 |
|
| 1715 |
|
| 1716 |
|
| 1717 |
|
| 1718 |
|
| 1719 |
|
| 1720 |
|
| 1721 |
|
| 1722 |
|
| 1723 |
|
| 1724 |
|
| 1725 |
|
| 1726 |
|
| 1727 |
|
| 1728 |
|
| 1729 |
|
| 1730 |
|
| 1731 |
|
| 1732 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 31]</span></pre> |
| 1733 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span> |
| 1734 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 1735 |
|
| 1736 |
|
| 1737 |
The following format MUST be used for the Data Message: |
| 1738 |
|
| 1739 |
0 1 2 3 |
| 1740 |
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 |
| 1741 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1742 |
| Tag = 0x0200 | Length = 8 | |
| 1743 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1744 |
| Network Appearance | |
| 1745 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1746 |
| Tag = 0x0006 | Length = 8 | |
| 1747 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1748 |
| Routing Context | |
| 1749 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1750 |
| Tag = 0x0210 | Length | |
| 1751 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1752 |
\ \ |
| 1753 |
/ Protocol Data / |
| 1754 |
\ \ |
| 1755 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1756 |
| Tag = 0x0013 | Length = 8 | |
| 1757 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1758 |
| Correlation Id | |
| 1759 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1760 |
|
| 1761 |
Network Appearance: 32-bits (unsigned integer) |
| 1762 |
|
| 1763 |
The Network Appearance parameter identifies the SS7 network |
| 1764 |
context for the message and implicitly identifies the SS7 Point |
| 1765 |
Code format used, the SS7 Network Indicator value, and the MTP3 |
| 1766 |
and possibly the MTP3-User protocol type/variant/version used |
| 1767 |
within the specific SS7 network. Where an SG operates in the |
| 1768 |
context of a single SS7 network, or individual SCTP associations |
| 1769 |
are dedicated to each SS7 network context, the Network Appearance |
| 1770 |
parameter is not required. In other cases the parameter may be |
| 1771 |
configured to be present for the use of the receiver. |
| 1772 |
|
| 1773 |
The Network Appearance parameter value is of local significance |
| 1774 |
only, coordinated between the SGP and ASP. Therefore, in the case |
| 1775 |
where an ASP is connected to more than one SGP, the same SS7 |
| 1776 |
network context may be identified by different Network Appearance |
| 1777 |
values depending over which SGP a message is being |
| 1778 |
transmitted/received. |
| 1779 |
|
| 1780 |
Where the optional Network Appearance parameter is present, it |
| 1781 |
must be the first parameter in the message as it defines the |
| 1782 |
format of the Protocol Data field. |
| 1783 |
|
| 1784 |
|
| 1785 |
|
| 1786 |
|
| 1787 |
|
| 1788 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 32]</span></pre> |
| 1789 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span> |
| 1790 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 1791 |
|
| 1792 |
|
| 1793 |
IMPLEMENTATION NOTE: For simplicity of configuration it may be |
| 1794 |
desirable to use the same NA value across all nodes sharing a |
| 1795 |
particular network context. |
| 1796 |
|
| 1797 |
Routing Context: 32-bits (unsigned integer) |
| 1798 |
|
| 1799 |
The Routing Context parameter contains the Routing Context value |
| 1800 |
associated with the DATA message. Where a Routing Key has not |
| 1801 |
been coordinated between the SGP and ASP, sending of Routing |
| 1802 |
Context is not required. Where multiple Routing Keys and Routing |
| 1803 |
Contexts are used across a common association, the Routing Context |
| 1804 |
MUST be sent to identify the traffic flow, assisting in the |
| 1805 |
internal distribution of Data messages. |
| 1806 |
|
| 1807 |
Protocol Data: variable length |
| 1808 |
|
| 1809 |
The Protocol Data parameter contains the original SS7 MTP3 |
| 1810 |
message, including the Service Information Octet and Routing |
| 1811 |
Label. |
| 1812 |
|
| 1813 |
The Protocol Data parameter contains the following fields: |
| 1814 |
|
| 1815 |
Service Indicator, |
| 1816 |
Network Indicator, |
| 1817 |
Message Priority. |
| 1818 |
|
| 1819 |
Destination Point Code, |
| 1820 |
Originating Point Code, |
| 1821 |
|
| 1822 |
Signalling Link Selection Code (SLS). |
| 1823 |
|
| 1824 |
User Protocol Data. Includes: |
| 1825 |
|
| 1826 |
MTP3-User protocol elements (e.g., ISUP, SCCP, or TUP |
| 1827 |
parameters). |
| 1828 |
|
| 1829 |
|
| 1830 |
|
| 1831 |
|
| 1832 |
|
| 1833 |
|
| 1834 |
|
| 1835 |
|
| 1836 |
|
| 1837 |
|
| 1838 |
|
| 1839 |
|
| 1840 |
|
| 1841 |
|
| 1842 |
|
| 1843 |
|
| 1844 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 33]</span></pre> |
| 1845 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-34" ></span> |
| 1846 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 1847 |
|
| 1848 |
|
| 1849 |
The Protocol Data parameter is encoded as follows: |
| 1850 |
|
| 1851 |
0 1 2 3 |
| 1852 |
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 |
| 1853 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1854 |
| Originating Point Code | |
| 1855 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1856 |
| Destination Point Code | |
| 1857 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1858 |
| SI | NI | MP | SLS | |
| 1859 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1860 |
\ \ |
| 1861 |
/ User Protocol Data / |
| 1862 |
\ \ |
| 1863 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1864 |
|
| 1865 |
Originating Point Code: 32 bits (unsigned integer) |
| 1866 |
Destination Point Code: 32 bits (unsigned integer) |
| 1867 |
|
| 1868 |
The Originating and Destination Point Code fields contains the OPC |
| 1869 |
and DPC from the routing label of the original SS7 message in Network |
| 1870 |
Byte Order, justified to the least significant bit. Unused bits are |
| 1871 |
coded `0'. |
| 1872 |
|
| 1873 |
Service Indicator: 8 bits (unsigned integer) |
| 1874 |
|
| 1875 |
The Service Indicator field contains the SI field from the original |
| 1876 |
SS7 message justified to the least significant bit. Unused bits are |
| 1877 |
coded `0'. |
| 1878 |
|
| 1879 |
Network Indicator: 8-bits (unsigned integer) |
| 1880 |
|
| 1881 |
The Network Indicator contains the NI field from the original SS7 |
| 1882 |
message justified to the least significant bit. Unused bits are |
| 1883 |
coded `0'. |
| 1884 |
|
| 1885 |
Message Priority: 8 bits (unsigned integer) |
| 1886 |
|
| 1887 |
The Message Priority field contains the MP bits (if any) from the |
| 1888 |
original SS7 message, both for ANSI-style and TTC-style [<a href="#ref-29" title=""Message Transfer Part Signaling Network Functions"">29</a>] message |
| 1889 |
priority bits. The MP bits are aligned to the least significant bit. |
| 1890 |
Unused bits are coded `0'. |
| 1891 |
|
| 1892 |
|
| 1893 |
|
| 1894 |
|
| 1895 |
|
| 1896 |
|
| 1897 |
|
| 1898 |
|
| 1899 |
|
| 1900 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 34]</span></pre> |
| 1901 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-35" ></span> |
| 1902 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 1903 |
|
| 1904 |
|
| 1905 |
Signalling Link Selection: 8 bits (unsigned integer) |
| 1906 |
|
| 1907 |
The Signalling Link Selection field contains the SLS bits from the |
| 1908 |
routing label of the original SS7 message justified to the least |
| 1909 |
significant bit and in Network Byte Order. Unused bits are coded |
| 1910 |
`0'. |
| 1911 |
|
| 1912 |
User Protocol Data: (byte string) |
| 1913 |
|
| 1914 |
The User Protocol Data field contains a byte string of MTP-User |
| 1915 |
information from the original SS7 message starting with the first |
| 1916 |
byte of the original SS7 message following the Routing Label. |
| 1917 |
|
| 1918 |
Correlation Id: 32-bits (unsigned integer) |
| 1919 |
|
| 1920 |
The Correlation Id parameter uniquely identifies the MSU carried in |
| 1921 |
the Protocol Data within an AS. This Correlation Id parameter is |
| 1922 |
assigned by the sending M3UA. |
| 1923 |
|
| 1924 |
<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a> SS7 Signalling Network Management (SSNM) Messages</span> |
| 1925 |
|
| 1926 |
<span class="h4"><a class="selflink" id="section-3.4.1" href="#section-3.4.1">3.4.1</a> Destination Unavailable (DUNA)</span> |
| 1927 |
|
| 1928 |
The DUNA message is sent from an SGP in an SG to all concerned ASPs |
| 1929 |
to indicate that the SG has determined that one or more SS7 |
| 1930 |
destinations are unreachable. It is also sent by an SGP in response |
| 1931 |
to a message from the ASP to an unreachable SS7 destination. As an |
| 1932 |
implementation option the SG may suppress the sending of subsequent |
| 1933 |
"response" DUNA messages regarding a certain unreachable SS7 |
| 1934 |
destination for a certain period to give the remote side time to |
| 1935 |
react. If there is no alternate route via another SG, the MTP3-User |
| 1936 |
at the ASP is expected to stop traffic to the affected destination |
| 1937 |
via the SG as per the defined MTP3-User procedures. |
| 1938 |
|
| 1939 |
|
| 1940 |
|
| 1941 |
|
| 1942 |
|
| 1943 |
|
| 1944 |
|
| 1945 |
|
| 1946 |
|
| 1947 |
|
| 1948 |
|
| 1949 |
|
| 1950 |
|
| 1951 |
|
| 1952 |
|
| 1953 |
|
| 1954 |
|
| 1955 |
|
| 1956 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 35]</span></pre> |
| 1957 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-36" ></span> |
| 1958 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 1959 |
|
| 1960 |
|
| 1961 |
The DUNA message contains the following parameters: |
| 1962 |
|
| 1963 |
Network Appearance Optional |
| 1964 |
Routing Context Optional |
| 1965 |
Affected Point Code Mandatory |
| 1966 |
INFO String Optional |
| 1967 |
|
| 1968 |
The format for DUNA Message parameters is as follows: |
| 1969 |
|
| 1970 |
0 1 2 3 |
| 1971 |
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 |
| 1972 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1973 |
| Tag = 0x0200 | Length = 8 | |
| 1974 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1975 |
| Network Appearance | |
| 1976 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1977 |
| Tag = 0x0006 | Length | |
| 1978 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1979 |
\ \ |
| 1980 |
/ Routing Context / |
| 1981 |
\ \ |
| 1982 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1983 |
| Tag = 0x0012 | Length | |
| 1984 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1985 |
| Mask | Affected PC 1 | |
| 1986 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1987 |
\ \ |
| 1988 |
/ ... / |
| 1989 |
\ \ |
| 1990 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1991 |
| Mask | Affected PC n | |
| 1992 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1993 |
| Tag = 0x0004 | Length | |
| 1994 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1995 |
\ \ |
| 1996 |
/ INFO String / |
| 1997 |
\ \ |
| 1998 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1999 |
|
| 2000 |
Network Appearance: 32-bit unsigned integer |
| 2001 |
|
| 2002 |
See <a href="#section-3.3.1">Section 3.3.1</a> |
| 2003 |
|
| 2004 |
Routing Context: n x 32-bits (unsigned integer) |
| 2005 |
|
| 2006 |
The optional Routing Context parameter contains the Routing |
| 2007 |
Context values associated with the DUNA message. Where a Routing |
| 2008 |
Key has not been coordinated between the SGP and ASP, sending of |
| 2009 |
|
| 2010 |
|
| 2011 |
|
| 2012 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 36]</span></pre> |
| 2013 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-37" ></span> |
| 2014 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 2015 |
|
| 2016 |
|
| 2017 |
Routing Context is not required. Where multiple Routing Keys and |
| 2018 |
Routing Contexts are used across a common association, the Routing |
| 2019 |
Context(s) MUST be sent to identify the concerned traffic flows |
| 2020 |
for which the DUNA message applies, assisting in outgoing traffic |
| 2021 |
management and internal distribution of MTP-PAUSE indications to |
| 2022 |
MTP3-Users at the receiver. |
| 2023 |
|
| 2024 |
Affected Point Code: n x 32-bits |
| 2025 |
|
| 2026 |
The Affected Point Code parameter contains a list of Affected |
| 2027 |
Destination Point Code fields, each a three-octet parameter to |
| 2028 |
allow for 14-, 16- and 24-bit binary formatted SS7 Point Codes. |
| 2029 |
Affected Point Codes that are less than 24-bits, are padded on the |
| 2030 |
left to the 24-bit boundary. The encoding is shown below for ANSI |
| 2031 |
and ITU Point Code examples. |
| 2032 |
|
| 2033 |
ANSI 24-bit Point Code: |
| 2034 |
|
| 2035 |
0 1 2 3 |
| 2036 |
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 |
| 2037 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2038 |
| Mask | Network | Cluster | Member | |
| 2039 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2040 |
|
| 2041 |
|MSB-----------------------------------------LSB| |
| 2042 |
|
| 2043 |
ITU 14-bit Point Code: |
| 2044 |
|
| 2045 |
0 1 2 3 |
| 2046 |
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 |
| 2047 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2048 |
| Mask |0 0 0 0 0 0 0 0 0 0|Zone | Region | SP | |
| 2049 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2050 |
|
| 2051 |
|MSB--------------------LSB| |
| 2052 |
|
| 2053 |
It is optional to send an Affected Point Code parameter with more |
| 2054 |
than one Affected PC but it is mandatory to receive it. Including |
| 2055 |
multiple Affected PCs may be useful when reception of an MTP3 |
| 2056 |
management message or a linkset event simultaneously affects the |
| 2057 |
availability status of a list of destinations at an SG. |
| 2058 |
|
| 2059 |
|
| 2060 |
|
| 2061 |
|
| 2062 |
|
| 2063 |
|
| 2064 |
|
| 2065 |
|
| 2066 |
|
| 2067 |
|
| 2068 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 37]</span></pre> |
| 2069 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-38" ></span> |
| 2070 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 2071 |
|
| 2072 |
|
| 2073 |
Mask: 8-bits (unsigned integer) |
| 2074 |
|
| 2075 |
The Mask field can be used to identify a contiguous range of |
| 2076 |
Affected Destination Point Codes. Identifying a contiguous range |
| 2077 |
of Affected DPCs may be useful when reception of an MTP3 |
| 2078 |
management message or a linkset event simultaneously affects the |
| 2079 |
availability status of a series of destinations at an SG. |
| 2080 |
|
| 2081 |
The Mask parameter is an integer representing a bit mask that can |
| 2082 |
be applied to the related Affected PC field. The bit mask |
| 2083 |
identifies how many bits of the Affected PC field are significant |
| 2084 |
and which are effectively "wildcarded". For example, a mask of |
| 2085 |
"8" indicates that the last eight bits of the PC is "wildcarded". |
| 2086 |
For an ANSI 24-bit Affected PC, this is equivalent to signalling |
| 2087 |
that all PCs in an ANSI Cluster are unavailable. A mask of "3" |
| 2088 |
indicates that the last three bits of the PC is "wildcarded". For |
| 2089 |
a 14-bit ITU Affected PC, this is equivalent to signaling that an |
| 2090 |
ITU |
| 2091 |
|
| 2092 |
Region is unavailable. A mask value equal (or greater than) the |
| 2093 |
number of bits in the PC indicates that the entire network |
| 2094 |
appearance is affected - this is used to indicate network |
| 2095 |
isolation to the ASP. |
| 2096 |
|
| 2097 |
INFO String: variable length |
| 2098 |
|
| 2099 |
The optional INFO String parameter can carry any meaningful UTF-8 |
| 2100 |
[<a href="#ref-10" title=""UTF-8, a transformation format of ISO 10646"">10</a>] character string along with the message. Length of the INFO |
| 2101 |
String parameter is from 0 to 255 octets. No procedures are |
| 2102 |
presently identified for its use but the INFO String MAY be used |
| 2103 |
for debugging purposes. |
| 2104 |
|
| 2105 |
<span class="h4"><a class="selflink" id="section-3.4.2" href="#section-3.4.2">3.4.2</a> Destination Available (DAVA)</span> |
| 2106 |
|
| 2107 |
The DAVA message is sent from an SGP to all concerned ASPs to |
| 2108 |
indicate that the SG has determined that one or more SS7 destinations |
| 2109 |
are now reachable (and not restricted), or in response to a DAUD |
| 2110 |
message if appropriate. If the ASP M3UA layer previously had no |
| 2111 |
routes to the affected destinations the ASP MTP3-User protocol is |
| 2112 |
informed and may now resume traffic to the affected destination. The |
| 2113 |
ASP M3UA layer now routes the MTP3-user traffic through the SG |
| 2114 |
initiating the DAVA message. |
| 2115 |
|
| 2116 |
|
| 2117 |
|
| 2118 |
|
| 2119 |
|
| 2120 |
|
| 2121 |
|
| 2122 |
|
| 2123 |
|
| 2124 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 38]</span></pre> |
| 2125 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-39" ></span> |
| 2126 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 2127 |
|
| 2128 |
|
| 2129 |
The DAVA message contains the following parameters: |
| 2130 |
|
| 2131 |
Network Appearance Optional |
| 2132 |
Routing Context Optional |
| 2133 |
Affected Point Code Mandatory |
| 2134 |
INFO String Optional |
| 2135 |
|
| 2136 |
The format and description of the Network Appearance, Routing |
| 2137 |
Context, Affected Point Code and INFO String parameters is the same |
| 2138 |
as for the DUNA message (See <a href="#section-3.4.1">Section 3.4.1</a>). |
| 2139 |
|
| 2140 |
<span class="h4"><a class="selflink" id="section-3.4.3" href="#section-3.4.3">3.4.3</a> Destination State Audit (DAUD)</span> |
| 2141 |
|
| 2142 |
The DAUD message MAY be sent from the ASP to the SGP to audit the |
| 2143 |
availability/congestion state of SS7 routes from the SG to one or |
| 2144 |
more affected destinations. |
| 2145 |
|
| 2146 |
The DAUD message contains the following parameters: |
| 2147 |
|
| 2148 |
Network Appearance Optional |
| 2149 |
Routing Context Optional |
| 2150 |
Affected Point Code Mandatory |
| 2151 |
INFO String Optional |
| 2152 |
|
| 2153 |
The format and description of DAUD Message parameters is the same as |
| 2154 |
for the DUNA message (See <a href="#section-3.4.1">Section 3.4.1</a>). |
| 2155 |
|
| 2156 |
<span class="h4"><a class="selflink" id="section-3.4.4" href="#section-3.4.4">3.4.4</a> Signalling Congestion (SCON)</span> |
| 2157 |
|
| 2158 |
The SCON message can be sent from an SGP to all concerned ASPs to |
| 2159 |
indicate that an SG has determined that there is congestion in the |
| 2160 |
SS7 network to one or more destinations, or to an ASP in response to |
| 2161 |
a DATA or DAUD message as appropriate. For some MTP protocol |
| 2162 |
variants (e.g., ANSI MTP) the SCON message may be sent when the SS7 |
| 2163 |
congestion level changes. The SCON message MAY also be sent from the |
| 2164 |
M3UA layer of an ASP to an M3UA peer indicating that the M3UA layer |
| 2165 |
or the ASP is congested. |
| 2166 |
|
| 2167 |
The SCON message contains the following parameters: |
| 2168 |
|
| 2169 |
Network Appearance Optional |
| 2170 |
Routing Context Optional |
| 2171 |
Affected Point Code Mandatory |
| 2172 |
Concerned Destination Optional |
| 2173 |
Congestion Indications Optional |
| 2174 |
INFO String Optional |
| 2175 |
|
| 2176 |
|
| 2177 |
|
| 2178 |
|
| 2179 |
|
| 2180 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 39]</span></pre> |
| 2181 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-40" ></span> |
| 2182 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 2183 |
|
| 2184 |
|
| 2185 |
The format for SCON Message parameters is as follows: |
| 2186 |
|
| 2187 |
0 1 2 3 |
| 2188 |
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 |
| 2189 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2190 |
| Tag = 0x0200 | Length = 8 | |
| 2191 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2192 |
| Network Appearance | |
| 2193 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2194 |
| Tag = 0x0006 | Length | |
| 2195 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2196 |
\ \ |
| 2197 |
/ Routing Context / |
| 2198 |
\ \ |
| 2199 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2200 |
| Tag = 0x0012 | Length | |
| 2201 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2202 |
| Mask | Affected PC 1 | |
| 2203 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2204 |
\ \ |
| 2205 |
/ ... / |
| 2206 |
\ \ |
| 2207 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2208 |
| Mask | Affected PC n | |
| 2209 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2210 |
| Tag = 0x0206 | Length = 8 | |
| 2211 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2212 |
| reserved | Concerned DPC | |
| 2213 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2214 |
| Tag = 0x0205 | Length = 8 | |
| 2215 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2216 |
| Reserved | Cong. Level | |
| 2217 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2218 |
| Tag = 0x0004 | Length | |
| 2219 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2220 |
\ \ |
| 2221 |
/ INFO String / |
| 2222 |
\ \ |
| 2223 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2224 |
|
| 2225 |
|
| 2226 |
|
| 2227 |
|
| 2228 |
|
| 2229 |
|
| 2230 |
|
| 2231 |
|
| 2232 |
|
| 2233 |
|
| 2234 |
|
| 2235 |
|
| 2236 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 40]</span></pre> |
| 2237 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-41" ></span> |
| 2238 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 2239 |
|
| 2240 |
|
| 2241 |
The format and description of the Network Appearance, Routing |
| 2242 |
Context, Affected Point Code, and INFO String parameters is the same |
| 2243 |
as for the DUNA message (See <a href="#section-3.4.1">Section 3.4.1</a>). |
| 2244 |
|
| 2245 |
The Affected Point Code parameter can be used to indicate congestion |
| 2246 |
of multiple destinations or ranges of destinations. |
| 2247 |
|
| 2248 |
Concerned Destination: 32-bits |
| 2249 |
|
| 2250 |
The optional Concerned Destination parameter is only used if the |
| 2251 |
SCON message is sent from an ASP to the SGP. It contains the point |
| 2252 |
code of the originator of the message that triggered the SCON |
| 2253 |
message. The Concerned Destination parameter contains one |
| 2254 |
Concerned Destination Point Code field, a three-octet parameter to |
| 2255 |
allow for 14-, 16- and 24-bit binary formatted SS7 Point Codes. A |
| 2256 |
Concerned Point Code that is less than 24-bits is padded on the |
| 2257 |
left to the 24-bit boundary. Any resulting Transfer Controlled |
| 2258 |
(TFC) message from the SG is sent to the Concerned Point Code |
| 2259 |
using the single Affected DPC contained in the SCON message to |
| 2260 |
populate the (affected) Destination field of the TFC message |
| 2261 |
|
| 2262 |
Congested Indications: 32-bits |
| 2263 |
|
| 2264 |
The optional Congestion Indications parameter contains a |
| 2265 |
Congestion Level field. This optional parameter is used to |
| 2266 |
communicate congestion levels in national MTP networks with |
| 2267 |
multiple congestion thresholds, such as in ANSI MTP3. For MTP |
| 2268 |
congestion methods without multiple congestion levels (e.g., the |
| 2269 |
ITU international method) the parameter is not included. |
| 2270 |
|
| 2271 |
Congestion Level field: 8-bits (unsigned integer) |
| 2272 |
|
| 2273 |
The Congestion Level field, associated with all of the Affected |
| 2274 |
DPC(s) in the Affected Destinations parameter, contains one of the |
| 2275 |
following values: |
| 2276 |
|
| 2277 |
0 No Congestion or Undefined |
| 2278 |
1 Congestion Level 1 |
| 2279 |
2 Congestion Level 2 |
| 2280 |
3 Congestion Level 3 |
| 2281 |
|
| 2282 |
|
| 2283 |
|
| 2284 |
|
| 2285 |
|
| 2286 |
|
| 2287 |
|
| 2288 |
|
| 2289 |
|
| 2290 |
|
| 2291 |
|
| 2292 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 41]</span></pre> |
| 2293 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-42" ></span> |
| 2294 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 2295 |
|
| 2296 |
|
| 2297 |
The congestion levels are defined in the congestion method in the |
| 2298 |
appropriate national MTP recommendations [<a href="#ref-7">7</a>,<a href="#ref-8">8</a>]. |
| 2299 |
|
| 2300 |
<span class="h4"><a class="selflink" id="section-3.4.5" href="#section-3.4.5">3.4.5</a> Destination User Part Unavailable (DUPU)</span> |
| 2301 |
|
| 2302 |
The DUPU message is used by an SGP to inform concerned ASPs that a |
| 2303 |
remote peer MTP3-User Part (e.g., ISUP or SCCP) at an SS7 node is |
| 2304 |
unavailable. |
| 2305 |
|
| 2306 |
The DUPU message contains the following parameters: |
| 2307 |
|
| 2308 |
Network Appearance Optional |
| 2309 |
Routing Context Optional |
| 2310 |
Affected Point Code Mandatory |
| 2311 |
User/Cause Mandatory |
| 2312 |
INFO String Optional |
| 2313 |
|
| 2314 |
The format for DUPU message parameters is as follows: |
| 2315 |
|
| 2316 |
0 1 2 3 |
| 2317 |
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 |
| 2318 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2319 |
| Tag = 0x0200 | Length = 8 | |
| 2320 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2321 |
| Network Appearance | |
| 2322 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2323 |
| Tag = 0x0006 | Length | |
| 2324 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2325 |
\ \ |
| 2326 |
/ Routing Context / |
| 2327 |
\ \ |
| 2328 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2329 |
| Tag = 0x0012 | Length = 8 | |
| 2330 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2331 |
| Mask = 0 | Affected PC | |
| 2332 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2333 |
| Tag = 0x0204 | Length = 8 | |
| 2334 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2335 |
| Cause | User | |
| 2336 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2337 |
| Tag = 0x0004 | Length | |
| 2338 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2339 |
\ \ |
| 2340 |
/ INFO String / |
| 2341 |
\ \ |
| 2342 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2343 |
|
| 2344 |
|
| 2345 |
|
| 2346 |
|
| 2347 |
|
| 2348 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 42]</span></pre> |
| 2349 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-43" ></span> |
| 2350 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 2351 |
|
| 2352 |
|
| 2353 |
User/Cause: 32-bits |
| 2354 |
|
| 2355 |
The Unavailability Cause and MTP3-User Identity fields, associated |
| 2356 |
with the Affected PC in the Affected Point Code parameter, are |
| 2357 |
encoded as follows: |
| 2358 |
|
| 2359 |
Unavailability Cause field: 16-bits (unsigned integer) |
| 2360 |
|
| 2361 |
The Unavailability Cause parameter provides the reason for the |
| 2362 |
unavailability of the MTP3-User. The valid values for the |
| 2363 |
Unavailability Cause parameter are shown in the following table. |
| 2364 |
The values agree with those provided in the SS7 MTP3 User Part |
| 2365 |
Unavailable message. Depending on the MTP3 protocol used in the |
| 2366 |
Network Appearance, additional values may be used - the |
| 2367 |
specification of the relevant MTP3 protocol variant/version |
| 2368 |
recommendation is definitive. |
| 2369 |
|
| 2370 |
0 Unknown |
| 2371 |
1 Unequipped Remote User |
| 2372 |
2 Inaccessible Remote User |
| 2373 |
|
| 2374 |
MTP3-User Identity field: 16-bits (unsigned integer) |
| 2375 |
|
| 2376 |
The MTP3-User Identity describes the specific MTP3-User that is |
| 2377 |
unavailable (e.g., ISUP, SCCP, ...). Some of the valid values for |
| 2378 |
the MTP3-User Identity are shown below. The values align with |
| 2379 |
those provided in the SS7 MTP3 User Part Unavailable message and |
| 2380 |
Service Indicator. Depending on the MTP3 protocol variant/version |
| 2381 |
used in the network appearance, additional values may be used. |
| 2382 |
The relevant MTP3 protocol variant/version recommendation is |
| 2383 |
definitive. |
| 2384 |
|
| 2385 |
0 to 2 Reserved |
| 2386 |
3 SCCP |
| 2387 |
4 TUP |
| 2388 |
5 ISUP |
| 2389 |
6 to 8 Reserved |
| 2390 |
9 Broadband ISUP |
| 2391 |
10 Satellite ISUP |
| 2392 |
11 Reserved |
| 2393 |
12 AAL type 2 Signalling |
| 2394 |
13 Bearer Independent Call Control (BICC) |
| 2395 |
14 Gateway Control Protocol |
| 2396 |
15 Reserved |
| 2397 |
|
| 2398 |
The format and description of the Affected Point Code parameter is |
| 2399 |
the same as for the DUNA message (See <a href="#section-3.4.1">Section 3.4.1</a>.) except that |
| 2400 |
the Mask field is not used and only a single Affected DPC is |
| 2401 |
|
| 2402 |
|
| 2403 |
|
| 2404 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 43]</span></pre> |
| 2405 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-44" ></span> |
| 2406 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 2407 |
|
| 2408 |
|
| 2409 |
included. Ranges and lists of Affected DPCs cannot be signaled in |
| 2410 |
a DUPU message, but this is consistent with UPU operation in the |
| 2411 |
SS7 network. The Affected Destinations parameter in an MTP3 User |
| 2412 |
Part Unavailable message (UPU) received by an SGP from the SS7 |
| 2413 |
network contains only one destination. |
| 2414 |
|
| 2415 |
The format and description of the Network Appearance, Routing |
| 2416 |
Context, and INFO String parameters is the same as for the DUNA |
| 2417 |
message (See <a href="#section-3.4.1">Section 3.4.1</a>). |
| 2418 |
|
| 2419 |
<span class="h4"><a class="selflink" id="section-3.4.6" href="#section-3.4.6">3.4.6</a> Destination Restricted (DRST)</span> |
| 2420 |
|
| 2421 |
The DRST message is optionally sent from the SGP to all concerned |
| 2422 |
ASPs to indicate that the SG has determined that one or more SS7 |
| 2423 |
destinations are now restricted from the point of view of the SG, or |
| 2424 |
in response to a DAUD message if appropriate. The M3UA layer at the |
| 2425 |
ASP is expected to send traffic to the affected destination via an |
| 2426 |
alternate SG with route(s) of equal priority, but only if such an |
| 2427 |
alternate route exists and is available. If the affected destination |
| 2428 |
is currently considered unavailable by the ASP, The MTP3-User should |
| 2429 |
be informed that traffic to the affected destination can be resumed. |
| 2430 |
In this case, the M3UA layer should route the traffic through the SG |
| 2431 |
initiating the DRST message. |
| 2432 |
|
| 2433 |
This message is optional for the SG to send and it is optional for |
| 2434 |
the ASP to act on any information received in the message. It is for |
| 2435 |
use in the "STP" case described in <a href="#section-1.4.1">Section 1.4.1</a>. |
| 2436 |
|
| 2437 |
The DRST message contains the following parameters: |
| 2438 |
|
| 2439 |
Network Appearance Optional |
| 2440 |
Routing Context Optional |
| 2441 |
Affected Point Code Mandatory |
| 2442 |
INFO String Optional |
| 2443 |
|
| 2444 |
The format and description of the Network Appearance, Routing |
| 2445 |
Context, Affected Point Code and INFO String parameters is the same |
| 2446 |
as for the DUNA message (See <a href="#section-3.4.1">Section 3.4.1</a>). |
| 2447 |
|
| 2448 |
|
| 2449 |
|
| 2450 |
|
| 2451 |
|
| 2452 |
|
| 2453 |
|
| 2454 |
|
| 2455 |
|
| 2456 |
|
| 2457 |
|
| 2458 |
|
| 2459 |
|
| 2460 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 44]</span></pre> |
| 2461 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-45" ></span> |
| 2462 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 2463 |
|
| 2464 |
|
| 2465 |
<span class="h3"><a class="selflink" id="section-3.5" href="#section-3.5">3.5</a> ASP State Maintenance (ASPSM) Messages</span> |
| 2466 |
|
| 2467 |
<span class="h4"><a class="selflink" id="section-3.5.1" href="#section-3.5.1">3.5.1</a> ASP Up</span> |
| 2468 |
|
| 2469 |
The ASP Up message is used to indicate to a remote M3UA peer that the |
| 2470 |
adaptation layer is ready to receive any ASPSM/ASPTM messages for all |
| 2471 |
Routing Keys that the ASP is configured to serve. |
| 2472 |
|
| 2473 |
The ASP Up message contains the following parameters: |
| 2474 |
|
| 2475 |
ASP Identifier Optional |
| 2476 |
INFO String Optional |
| 2477 |
|
| 2478 |
The format for ASP Up message parameters is as follows: |
| 2479 |
|
| 2480 |
0 1 2 3 |
| 2481 |
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 |
| 2482 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2483 |
| Tag = 0x0011 | Length = 8 | |
| 2484 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2485 |
| ASP Identifier | |
| 2486 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2487 |
| Tag = 0x0004 | Length | |
| 2488 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2489 |
\ \ |
| 2490 |
/ INFO String / |
| 2491 |
\ \ |
| 2492 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2493 |
|
| 2494 |
ASP Identifier: 32-bit unsigned integer |
| 2495 |
|
| 2496 |
The optional ASP Identifier parameter contains a unique value that |
| 2497 |
is locally significant among the ASPs that support an AS. The SGP |
| 2498 |
should save the ASP Identifier to be used, if necessary, with the |
| 2499 |
Notify message (see <a href="#section-3.8.2">Section 3.8.2</a>). |
| 2500 |
|
| 2501 |
The format and description of the optional INFO String parameter |
| 2502 |
is the same as for the DUNA message (See <a href="#section-3.4.1">Section 3.4.1</a>). |
| 2503 |
|
| 2504 |
|
| 2505 |
|
| 2506 |
|
| 2507 |
|
| 2508 |
|
| 2509 |
|
| 2510 |
|
| 2511 |
|
| 2512 |
|
| 2513 |
|
| 2514 |
|
| 2515 |
|
| 2516 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 45]</span></pre> |
| 2517 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-46" ></span> |
| 2518 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 2519 |
|
| 2520 |
|
| 2521 |
<span class="h4"><a class="selflink" id="section-3.5.2" href="#section-3.5.2">3.5.2</a> ASP Up Acknowledgement (ASP Up Ack)</span> |
| 2522 |
|
| 2523 |
The ASP UP Ack message is used to acknowledge an ASP Up message |
| 2524 |
received from a remote M3UA peer. |
| 2525 |
|
| 2526 |
The ASP Up Ack message contains the following parameters: |
| 2527 |
|
| 2528 |
INFO String (optional) |
| 2529 |
|
| 2530 |
The format for ASP Up Ack message parameters is as follows: |
| 2531 |
|
| 2532 |
0 1 2 3 |
| 2533 |
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 |
| 2534 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2535 |
| Tag =0x0004 | Length | |
| 2536 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2537 |
\ \ |
| 2538 |
/ INFO String / |
| 2539 |
\ \ |
| 2540 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2541 |
|
| 2542 |
The format and description of the optional INFO String parameter is |
| 2543 |
the same as for the DUNA message (See <a href="#section-3.4.1">Section 3.4.1</a>). The INFO |
| 2544 |
String in an ASP Up Ack message is independent from the INFO String |
| 2545 |
in the ASP Up message (i.e., it does not have to echo back the INFO |
| 2546 |
String received). |
| 2547 |
|
| 2548 |
<span class="h4"><a class="selflink" id="section-3.5.3" href="#section-3.5.3">3.5.3</a> ASP Down</span> |
| 2549 |
|
| 2550 |
The ASP Down message is used to indicate to a remote M3UA peer that |
| 2551 |
the adaptation layer is NOT ready to receive DATA, SSNM, RKM or ASPTM |
| 2552 |
messages. |
| 2553 |
|
| 2554 |
The ASP Down message contains the following parameters: |
| 2555 |
|
| 2556 |
INFO String Optional |
| 2557 |
|
| 2558 |
|
| 2559 |
|
| 2560 |
|
| 2561 |
|
| 2562 |
|
| 2563 |
|
| 2564 |
|
| 2565 |
|
| 2566 |
|
| 2567 |
|
| 2568 |
|
| 2569 |
|
| 2570 |
|
| 2571 |
|
| 2572 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 46]</span></pre> |
| 2573 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-47" ></span> |
| 2574 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 2575 |
|
| 2576 |
|
| 2577 |
The format for the ASP Down message parameters is as follows: |
| 2578 |
|
| 2579 |
0 1 2 3 |
| 2580 |
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 |
| 2581 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2582 |
| Tag =0x0004 | Length | |
| 2583 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2584 |
\ \ |
| 2585 |
/ INFO String / |
| 2586 |
\ \ |
| 2587 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2588 |
|
| 2589 |
The format and description of the optional INFO String parameter is |
| 2590 |
the same as for the DUNA message (See <a href="#section-3.4.1">Section 3.4.1</a>). |
| 2591 |
|
| 2592 |
<span class="h4"><a class="selflink" id="section-3.5.4" href="#section-3.5.4">3.5.4</a> ASP Down Acknowledgement (ASP Down Ack)</span> |
| 2593 |
|
| 2594 |
The ASP Down Ack message is used to acknowledge an ASP Down message |
| 2595 |
received from a remote M3UA peer. |
| 2596 |
|
| 2597 |
The ASP Down Ack message contains the following parameters: |
| 2598 |
|
| 2599 |
INFO String Optional |
| 2600 |
|
| 2601 |
The format for the ASP Down Ack message parameters is as follows: |
| 2602 |
|
| 2603 |
0 1 2 3 |
| 2604 |
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 |
| 2605 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2606 |
| Tag = 0x0004 | Length | |
| 2607 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2608 |
\ \ |
| 2609 |
/ INFO String / |
| 2610 |
\ \ |
| 2611 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2612 |
|
| 2613 |
The format and description of the optional INFO String parameter is |
| 2614 |
the same as for the DUNA message (See <a href="#section-3.4.1">Section 3.4.1</a>). |
| 2615 |
|
| 2616 |
The INFO String in an ASP Down Ack message is independent from the |
| 2617 |
INFO String in the ASP Down message (i.e., it does not have to echo |
| 2618 |
back the INFO String received). |
| 2619 |
|
| 2620 |
|
| 2621 |
|
| 2622 |
|
| 2623 |
|
| 2624 |
|
| 2625 |
|
| 2626 |
|
| 2627 |
|
| 2628 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 47]</span></pre> |
| 2629 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-48" ></span> |
| 2630 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 2631 |
|
| 2632 |
|
| 2633 |
<span class="h4"><a class="selflink" id="section-3.5.5" href="#section-3.5.5">3.5.5</a> Heartbeat (BEAT)</span> |
| 2634 |
|
| 2635 |
The BEAT message is optionally used to ensure that the M3UA peers are |
| 2636 |
still available to each other. It is recommended for use when the |
| 2637 |
M3UA runs over a transport layer other than the SCTP, which has its |
| 2638 |
own heartbeat. |
| 2639 |
|
| 2640 |
The BEAT message contains the following parameters: |
| 2641 |
|
| 2642 |
Heartbeat Data Optional |
| 2643 |
|
| 2644 |
The format for the BEAT message is as follows: |
| 2645 |
|
| 2646 |
0 1 2 3 |
| 2647 |
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 |
| 2648 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2649 |
| Tag = 0x0009 | Length | |
| 2650 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2651 |
\ \ |
| 2652 |
/ Heartbeat Data / |
| 2653 |
\ \ |
| 2654 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2655 |
|
| 2656 |
The Heartbeat Data parameter contents are defined by the sending |
| 2657 |
node. The Heartbeat Data could include, for example, a Heartbeat |
| 2658 |
Sequence Number and/or Timestamp. The receiver of a BEAT message |
| 2659 |
does not process this field as it is only of significance to the |
| 2660 |
sender. The receiver MUST respond with a BEAT Ack message. |
| 2661 |
|
| 2662 |
<span class="h4"><a class="selflink" id="section-3.5.6" href="#section-3.5.6">3.5.6</a> Heartbeat Acknowledgement (BEAT Ack)</span> |
| 2663 |
|
| 2664 |
The BEAT Ack message is sent in response to a received BEAT message. |
| 2665 |
It includes all the parameters of the received BEAT message, without |
| 2666 |
any change. |
| 2667 |
|
| 2668 |
<span class="h3"><a class="selflink" id="section-3.6" href="#section-3.6">3.6</a> Routing Key Management (RKM) Messages [Optional]</span> |
| 2669 |
|
| 2670 |
<span class="h4"><a class="selflink" id="section-3.6.1" href="#section-3.6.1">3.6.1</a> Registration Request (REG REQ)</span> |
| 2671 |
|
| 2672 |
The REG REQ message is sent by an ASP to indicate to a remote M3UA |
| 2673 |
peer that it wishes to register one or more given Routing Keys with |
| 2674 |
the remote peer. Typically, an ASP would send this message to an |
| 2675 |
SGP, and expects to receive a REG RSP message in return with an |
| 2676 |
associated Routing Context value. |
| 2677 |
|
| 2678 |
|
| 2679 |
|
| 2680 |
|
| 2681 |
|
| 2682 |
|
| 2683 |
|
| 2684 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 48]</span></pre> |
| 2685 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-49" ></span> |
| 2686 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 2687 |
|
| 2688 |
|
| 2689 |
The REG REQ message contains the following parameters: |
| 2690 |
|
| 2691 |
Routing Key Mandatory |
| 2692 |
|
| 2693 |
One or more Routing Key parameters MAY be included. The format for |
| 2694 |
the REG REQ message is as follows: |
| 2695 |
|
| 2696 |
0 1 2 3 |
| 2697 |
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 |
| 2698 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2699 |
| Tag = 0x0207 | Length | |
| 2700 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2701 |
\ \ |
| 2702 |
/ Routing Key 1 / |
| 2703 |
\ \ |
| 2704 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2705 |
\ \ |
| 2706 |
/ ... / |
| 2707 |
\ \ |
| 2708 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2709 |
| Tag = 0x0207 | Length | |
| 2710 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2711 |
\ \ |
| 2712 |
/ Routing Key n / |
| 2713 |
\ \ |
| 2714 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2715 |
|
| 2716 |
Routing Key: variable length |
| 2717 |
|
| 2718 |
The Routing Key parameter is mandatory. The sender of this message |
| 2719 |
expects that the receiver of this message will create a Routing |
| 2720 |
Key entry and assign a unique Routing Context value to it, if the |
| 2721 |
Routing Key entry does not already exist. |
| 2722 |
|
| 2723 |
The Routing Key parameter may be present multiple times in the |
| 2724 |
same message. This is used to allow the registration of multiple |
| 2725 |
Routing Keys in a single message. |
| 2726 |
|
| 2727 |
|
| 2728 |
|
| 2729 |
|
| 2730 |
|
| 2731 |
|
| 2732 |
|
| 2733 |
|
| 2734 |
|
| 2735 |
|
| 2736 |
|
| 2737 |
|
| 2738 |
|
| 2739 |
|
| 2740 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 49]</span></pre> |
| 2741 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-50" ></span> |
| 2742 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 2743 |
|
| 2744 |
|
| 2745 |
The format of the Routing Key parameter is as follows. |
| 2746 |
|
| 2747 |
0 1 2 3 |
| 2748 |
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 |
| 2749 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2750 |
| Local-RK-Identifier | |
| 2751 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2752 |
| Traffic Mode Type (optional) | |
| 2753 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2754 |
| Destination Point Code | |
| 2755 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2756 |
| Network Appearance (optional) | |
| 2757 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2758 |
| Service Indicators (optional) | |
| 2759 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2760 |
| Originating Point Code List (optional) | |
| 2761 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2762 |
| Circuit Range List (optional) | |
| 2763 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2764 |
\ \ |
| 2765 |
/ ... / |
| 2766 |
\ \ |
| 2767 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2768 |
| Destination Point Code | |
| 2769 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2770 |
| Service Indicators (optional) | |
| 2771 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2772 |
| Originating Point Code List (optional) | |
| 2773 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2774 |
| Circuit Range List (optional) | |
| 2775 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2776 |
|
| 2777 |
Note: The Destination Point Code, Service Indicators, Originating |
| 2778 |
Point Code List and Circuit Range List parameters MAY be repeated |
| 2779 |
as a grouping within the Routing Key parameter, in the structure |
| 2780 |
shown above. |
| 2781 |
|
| 2782 |
Local-RK-Identifier: 32-bit unsigned integer |
| 2783 |
|
| 2784 |
The mandatory Local-RK-Identifier field is used to uniquely |
| 2785 |
identify the registration request. The Identifier value is |
| 2786 |
assigned by the ASP, and is used to correlate the response in an |
| 2787 |
REG RSP message with the original registration request. The |
| 2788 |
Identifier value must remain unique until the REG RSP message is |
| 2789 |
received. |
| 2790 |
|
| 2791 |
|
| 2792 |
|
| 2793 |
|
| 2794 |
|
| 2795 |
|
| 2796 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 50]</span></pre> |
| 2797 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-51" ></span> |
| 2798 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 2799 |
|
| 2800 |
|
| 2801 |
The format of the Local-RK-Identifier field is as follows: |
| 2802 |
|
| 2803 |
0 1 2 3 |
| 2804 |
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 |
| 2805 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2806 |
| Tag = 0x020a | Length = 8 | |
| 2807 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2808 |
| Local-RK-Identifier value | |
| 2809 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2810 |
|
| 2811 |
Traffic Mode Type: 32-bit (unsigned integer) |
| 2812 |
|
| 2813 |
The optional Traffic Mode Type parameter identifies the traffic mode |
| 2814 |
of operation of the ASP(s) within an Application Server. The format |
| 2815 |
of the Traffic Mode Type Identifier is as follows: |
| 2816 |
|
| 2817 |
0 1 2 3 |
| 2818 |
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 |
| 2819 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2820 |
| Tag = 0x000b | Length = 8 | |
| 2821 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2822 |
| Traffic Mode Type | |
| 2823 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2824 |
|
| 2825 |
The valid values for Traffic Mode Type are shown in the following |
| 2826 |
table: |
| 2827 |
|
| 2828 |
1 Override |
| 2829 |
2 Loadshare |
| 2830 |
3 Broadcast |
| 2831 |
|
| 2832 |
Destination Point Code: |
| 2833 |
|
| 2834 |
The Destination Point Code parameter is mandatory, and identifies |
| 2835 |
the Destination Point Code of incoming SS7 traffic for which the |
| 2836 |
ASP is registering. The format is the same as described for the |
| 2837 |
Affected Destination parameter in the DUNA message (See <a href="#section-3.4.1">Section</a> |
| 2838 |
<a href="#section-3.4.1">3.4.1</a>). Its format is: |
| 2839 |
|
| 2840 |
0 1 2 3 |
| 2841 |
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 |
| 2842 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2843 |
| Tag = 0x020b | Length = 8 | |
| 2844 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2845 |
| Mask = 0 | Destination Point Code | |
| 2846 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2847 |
|
| 2848 |
|
| 2849 |
|
| 2850 |
|
| 2851 |
|
| 2852 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 51]</span></pre> |
| 2853 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-52" ></span> |
| 2854 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 2855 |
|
| 2856 |
|
| 2857 |
Network Appearance: |
| 2858 |
|
| 2859 |
The optional Network Appearance parameter field identifies the SS7 |
| 2860 |
network context for the Routing Key, and has the same format as in |
| 2861 |
the DATA message (See <a href="#section-3.3.1">Section 3.3.1</a>). The absence of the Network |
| 2862 |
Appearance parameter in the Routing Key indicates the use of any |
| 2863 |
Network Appearance value. Its format is: |
| 2864 |
|
| 2865 |
0 1 2 3 |
| 2866 |
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 |
| 2867 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2868 |
| Tag = 0x0200 | Length = 8 | |
| 2869 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2870 |
| Network Appearance | |
| 2871 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2872 |
|
| 2873 |
Service Indicators (SI): n X 8-bit integers |
| 2874 |
|
| 2875 |
The optional SI [<a href="#ref-7">7</a>,<a href="#ref-8">8</a>] field contains one or more Service |
| 2876 |
Indicators from the values as described in the MTP3-User Identity |
| 2877 |
field of the DUPU message. The absence of the SI parameter in the |
| 2878 |
Routing Key indicates the use of any SI value, excluding of course |
| 2879 |
MTP management. Where an SI parameter does not contain a multiple |
| 2880 |
of four SIs, the parameter is padded out to 32-byte alignment. |
| 2881 |
|
| 2882 |
The SI format is: |
| 2883 |
|
| 2884 |
0 1 2 3 |
| 2885 |
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 |
| 2886 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2887 |
| Tag = 0x020c | Length | |
| 2888 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2889 |
| SI #1 | SI #2 | SI #3 | SI #4 | |
| 2890 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2891 |
/ ... / |
| 2892 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2893 |
| SI #n | 0 Padding, if necessary | |
| 2894 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2895 |
|
| 2896 |
OPC List: |
| 2897 |
|
| 2898 |
The Originating Point Code List parameter contains one or more SS7 |
| 2899 |
OPC entries, and its format is the same as the Destination Point |
| 2900 |
Code parameter. The absence of the OPC List parameter in the |
| 2901 |
Routing Key indicates the use of any OPC value, |
| 2902 |
|
| 2903 |
|
| 2904 |
|
| 2905 |
|
| 2906 |
|
| 2907 |
|
| 2908 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 52]</span></pre> |
| 2909 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-53" ></span> |
| 2910 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 2911 |
|
| 2912 |
|
| 2913 |
0 1 2 3 |
| 2914 |
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 |
| 2915 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2916 |
| Tag = 0x020e | Length | |
| 2917 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2918 |
| Mask = 0 | Origination Point Code #1 | |
| 2919 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2920 |
| Mask = 0 | Origination Point Code #2 | |
| 2921 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2922 |
/ ... / |
| 2923 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2924 |
| Mask = 0 | Origination Point Code #n | |
| 2925 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2926 |
|
| 2927 |
Circuit Range: |
| 2928 |
|
| 2929 |
An ISUP controlled circuit is uniquely identified by the SS7 OPC, |
| 2930 |
DPC and CIC value. For the purposes of identifying Circuit Ranges |
| 2931 |
in an M3UA Routing Key, the optional Circuit Range parameter |
| 2932 |
includes one or more circuit ranges, each identified by an OPC and |
| 2933 |
Upper/Lower CIC value. The DPC is implicit as it is mandatory and |
| 2934 |
already included in the DPC parameter of the Routing Key. The |
| 2935 |
absence of the Circuit Range parameter in the Routing Key |
| 2936 |
indicates the use of any Circuit Range values, in the case of |
| 2937 |
ISUP/TUP traffic. The Origination Point Code is encoded the same |
| 2938 |
as the Destination Point Code parameter, while the CIC values are |
| 2939 |
16-bit integers. |
| 2940 |
|
| 2941 |
|
| 2942 |
|
| 2943 |
|
| 2944 |
|
| 2945 |
|
| 2946 |
|
| 2947 |
|
| 2948 |
|
| 2949 |
|
| 2950 |
|
| 2951 |
|
| 2952 |
|
| 2953 |
|
| 2954 |
|
| 2955 |
|
| 2956 |
|
| 2957 |
|
| 2958 |
|
| 2959 |
|
| 2960 |
|
| 2961 |
|
| 2962 |
|
| 2963 |
|
| 2964 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 53]</span></pre> |
| 2965 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-54" ></span> |
| 2966 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 2967 |
|
| 2968 |
|
| 2969 |
The Circuit Range format is as follows: |
| 2970 |
|
| 2971 |
0 1 2 3 |
| 2972 |
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 |
| 2973 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2974 |
| Tag = 0x020f | Length | |
| 2975 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2976 |
| Mask = 0 | Origination Point Code #1 | |
| 2977 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2978 |
| Lower CIC Value #1 | Upper CIC Value #1 | |
| 2979 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2980 |
| Mask = 0 | Origination Point Code #2 | |
| 2981 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2982 |
| Lower CIC Value #2 | Upper CIC Value #2 | |
| 2983 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2984 |
/ ... / |
| 2985 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2986 |
| Mask = 0 | Origination Point Code #n | |
| 2987 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2988 |
| Lower CIC Value #n | Upper CIC Value #n | |
| 2989 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2990 |
|
| 2991 |
<span class="h4"><a class="selflink" id="section-3.6.2" href="#section-3.6.2">3.6.2</a> Registration Response (REG RSP)</span> |
| 2992 |
|
| 2993 |
The REG RSP message is used as a response to the REG REQ message from |
| 2994 |
a remote M3UA peer. It contains indications of success/failure for |
| 2995 |
registration requests and returns a unique Routing Context value for |
| 2996 |
successful registration requests, to be used in subsequent M3UA |
| 2997 |
Traffic Management protocol. |
| 2998 |
|
| 2999 |
The REG RSP message contains the following parameters: |
| 3000 |
|
| 3001 |
Registration Result Mandatory |
| 3002 |
|
| 3003 |
One or more Registration Result parameters MUST be included. The |
| 3004 |
format for the REG RSP message is as follows: |
| 3005 |
|
| 3006 |
|
| 3007 |
|
| 3008 |
|
| 3009 |
|
| 3010 |
|
| 3011 |
|
| 3012 |
|
| 3013 |
|
| 3014 |
|
| 3015 |
|
| 3016 |
|
| 3017 |
|
| 3018 |
|
| 3019 |
|
| 3020 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 54]</span></pre> |
| 3021 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-55" ></span> |
| 3022 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 3023 |
|
| 3024 |
|
| 3025 |
0 1 2 3 |
| 3026 |
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 |
| 3027 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3028 |
| Tag = 0x0208 | Length | |
| 3029 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3030 |
| Registration Result 1 | |
| 3031 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3032 |
\ \ |
| 3033 |
/ ... / |
| 3034 |
\ \ |
| 3035 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3036 |
| Tag = 0x0208 | Length | |
| 3037 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3038 |
| Registration Result n | |
| 3039 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3040 |
|
| 3041 |
Registration Results: |
| 3042 |
|
| 3043 |
The Registration Result parameter contains the registration result |
| 3044 |
for a single Routing Key in an REG REQ message. The number of |
| 3045 |
results in a single REG RSP message MUST be anywhere from one to |
| 3046 |
the total number of number of Routing Key parameters found in the |
| 3047 |
corresponding REG REQ message. Where multiple REG RSP messages |
| 3048 |
are used in reply to REG REQ message, a specific result SHOULD be |
| 3049 |
in only one REG RSP message. The format of each result is as |
| 3050 |
follows: |
| 3051 |
|
| 3052 |
0 1 2 3 |
| 3053 |
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 |
| 3054 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3055 |
| Tag = 0x020a | Length = 8 | |
| 3056 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3057 |
| Local-RK-Identifier value | |
| 3058 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3059 |
| Tag = 0x0212 | Length = 8 | |
| 3060 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3061 |
| Registration Status | |
| 3062 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3063 |
| Tag = 0x0006 | Length = 8 | |
| 3064 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3065 |
| Routing Context | |
| 3066 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3067 |
|
| 3068 |
Local-RK-Identifier: 32-bit integer |
| 3069 |
|
| 3070 |
The Local-RK-Identifier contains the same value as found in the |
| 3071 |
matching Routing Key parameter found in the REG REQ message (See |
| 3072 |
<a href="#section-3.6.1">Section 3.6.1</a>). |
| 3073 |
|
| 3074 |
|
| 3075 |
|
| 3076 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 55]</span></pre> |
| 3077 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-56" ></span> |
| 3078 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 3079 |
|
| 3080 |
|
| 3081 |
Registration Status: 32-bit integer |
| 3082 |
|
| 3083 |
The Registration Result Status field indicates the success or the |
| 3084 |
reason for failure of a registration request. |
| 3085 |
|
| 3086 |
Its values may be: |
| 3087 |
|
| 3088 |
0 Successfully Registered |
| 3089 |
1 Error - Unknown |
| 3090 |
2 Error - Invalid DPC |
| 3091 |
3 Error - Invalid Network Appearance |
| 3092 |
4 Error - Invalid Routing Key |
| 3093 |
5 Error - Permission Denied |
| 3094 |
6 Error - Cannot Support Unique Routing |
| 3095 |
7 Error - Routing Key not Currently Provisioned |
| 3096 |
8 Error - Insufficient Resources |
| 3097 |
9 Error - Unsupported RK parameter Field |
| 3098 |
10 Error - Unsupported/Invalid Traffic Handling Mode |
| 3099 |
|
| 3100 |
Routing Context: 32-bit integer |
| 3101 |
|
| 3102 |
The Routing Context field contains the Routing Context value for |
| 3103 |
the associated Routing Key if the registration was successful. It |
| 3104 |
is set to "0" if the registration was not successful. |
| 3105 |
|
| 3106 |
<span class="h4"><a class="selflink" id="section-3.6.3" href="#section-3.6.3">3.6.3</a> Deregistration Request (DEREG REQ)</span> |
| 3107 |
|
| 3108 |
The DEREG REQ message is sent by an ASP to indicate to a remote M3UA |
| 3109 |
peer that it wishes to deregister a given Routing Key. Typically, an |
| 3110 |
ASP would send this message to an SGP, and expects to receive a DEREG |
| 3111 |
RSP message in return with the associated Routing Context value. |
| 3112 |
|
| 3113 |
The DEREG REQ message contains the following parameters: |
| 3114 |
|
| 3115 |
Routing Context Mandatory |
| 3116 |
|
| 3117 |
The format for the DEREG REQ message is as follows: |
| 3118 |
|
| 3119 |
|
| 3120 |
|
| 3121 |
|
| 3122 |
|
| 3123 |
|
| 3124 |
|
| 3125 |
|
| 3126 |
|
| 3127 |
|
| 3128 |
|
| 3129 |
|
| 3130 |
|
| 3131 |
|
| 3132 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 56]</span></pre> |
| 3133 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-57" ></span> |
| 3134 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 3135 |
|
| 3136 |
|
| 3137 |
0 1 2 3 |
| 3138 |
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 |
| 3139 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3140 |
| Tag = 0x0006 | Length | |
| 3141 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3142 |
\ \ |
| 3143 |
/ Routing Context / |
| 3144 |
\ \ |
| 3145 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3146 |
|
| 3147 |
Routing Context: n X 32-bit integers |
| 3148 |
|
| 3149 |
The Routing Context parameter contains (a list of) integers |
| 3150 |
indexing the Application Server traffic that the sending ASP is |
| 3151 |
currently registered to receive from the SGP but now wishes to |
| 3152 |
deregister. |
| 3153 |
|
| 3154 |
<span class="h4"><a class="selflink" id="section-3.6.4" href="#section-3.6.4">3.6.4</a> Deregistration Response (DEREG RSP)</span> |
| 3155 |
|
| 3156 |
The DEREG RSP message is used as a response to the DEREG REQ message |
| 3157 |
from a remote M3UA peer. |
| 3158 |
|
| 3159 |
The DEREG RSP message contains the following parameters: |
| 3160 |
|
| 3161 |
Deregistration Result Mandatory |
| 3162 |
|
| 3163 |
One or more Deregistration Result parameters MUST be included. The |
| 3164 |
format for the DEREG RSP message is as follows: |
| 3165 |
|
| 3166 |
0 1 2 3 |
| 3167 |
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 |
| 3168 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3169 |
| Tag = 0x0209 | Length | |
| 3170 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3171 |
| Deregistration Result 1 | |
| 3172 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3173 |
\ \ |
| 3174 |
/ ... / |
| 3175 |
\ \ |
| 3176 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3177 |
| Tag = 0x0209 | Length | |
| 3178 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3179 |
| Deregistration Result n | |
| 3180 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3181 |
|
| 3182 |
|
| 3183 |
|
| 3184 |
|
| 3185 |
|
| 3186 |
|
| 3187 |
|
| 3188 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 57]</span></pre> |
| 3189 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-58" ></span> |
| 3190 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 3191 |
|
| 3192 |
|
| 3193 |
Deregistration Results: |
| 3194 |
|
| 3195 |
The Deregistration Result parameter contains the deregistration |
| 3196 |
status for a single Routing Context in a DEREG REQ message. The |
| 3197 |
number of results in a single DEREG RSP message MAY be anywhere |
| 3198 |
from one to the total number of number of Routing Context values |
| 3199 |
found in the corresponding DEREG REQ message. |
| 3200 |
|
| 3201 |
Where multiple DEREG RSP messages are used in reply to DEREG REQ |
| 3202 |
message, a specific result SHOULD be in only one DEREG RSP |
| 3203 |
message. The format of each result is as follows: |
| 3204 |
|
| 3205 |
0 1 2 3 |
| 3206 |
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 |
| 3207 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3208 |
| Tag = 0x0006 | Length = 8 | |
| 3209 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3210 |
| Routing Context | |
| 3211 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3212 |
| Tag = 0x0213 | Length = 8 | |
| 3213 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3214 |
| Deregistration Status | |
| 3215 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3216 |
|
| 3217 |
Routing Context: 32-bit integer |
| 3218 |
|
| 3219 |
The Routing Context field contains the Routing Context value of |
| 3220 |
the matching Routing Key to deregister, as found in the DEREG REQ |
| 3221 |
message. |
| 3222 |
|
| 3223 |
Deregistration Status: 32-bit integer |
| 3224 |
|
| 3225 |
The Deregistration Result Status field indicates the success or |
| 3226 |
the reason for failure of the deregistration. |
| 3227 |
|
| 3228 |
Its values may be: |
| 3229 |
|
| 3230 |
0 Successfully Deregistered |
| 3231 |
1 Error - Unknown |
| 3232 |
2 Error - Invalid Routing Context |
| 3233 |
3 Error - Permission Denied |
| 3234 |
4 Error - Not Registered |
| 3235 |
5 Error - ASP Currently Active for Routing Context |
| 3236 |
|
| 3237 |
|
| 3238 |
|
| 3239 |
|
| 3240 |
|
| 3241 |
|
| 3242 |
|
| 3243 |
|
| 3244 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 58]</span></pre> |
| 3245 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-59" ></span> |
| 3246 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 3247 |
|
| 3248 |
|
| 3249 |
<span class="h3"><a class="selflink" id="section-3.7" href="#section-3.7">3.7</a> ASP Traffic Maintenance (ASPTM) Messages</span> |
| 3250 |
|
| 3251 |
<span class="h4"><a class="selflink" id="section-3.7.1" href="#section-3.7.1">3.7.1</a> ASP Active</span> |
| 3252 |
|
| 3253 |
The ASP Active message is sent by an ASP to indicate to a remote M3UA |
| 3254 |
peer that it is ready to process signalling traffic for a particular |
| 3255 |
Application Server. The ASP Active message affects only the ASP |
| 3256 |
state for the Routing Keys identified by the Routing Contexts, if |
| 3257 |
present. |
| 3258 |
|
| 3259 |
The ASP Active message contains the following parameters: |
| 3260 |
|
| 3261 |
Traffic Mode Type Optional |
| 3262 |
Routing Context Optional |
| 3263 |
INFO String Optional |
| 3264 |
|
| 3265 |
The format for the ASP Active message is as follows: |
| 3266 |
|
| 3267 |
0 1 2 3 |
| 3268 |
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 |
| 3269 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3270 |
| Tag = 0x000b | Length = 8 | |
| 3271 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3272 |
| Traffic Mode Type | |
| 3273 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3274 |
| Tag = 0x0006 | Length | |
| 3275 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3276 |
\ \ |
| 3277 |
/ Routing Context / |
| 3278 |
\ \ |
| 3279 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3280 |
| Tag = 0x0004 | Length | |
| 3281 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3282 |
\ \ |
| 3283 |
/ INFO String / |
| 3284 |
\ \ |
| 3285 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3286 |
|
| 3287 |
Traffic Mode Type: 32-bit (unsigned integer) |
| 3288 |
|
| 3289 |
The Traffic Mode Type parameter identifies the traffic mode of |
| 3290 |
operation of the ASP within an AS. The valid values for Traffic |
| 3291 |
Mode Type are shown in the following table: |
| 3292 |
|
| 3293 |
1 Override |
| 3294 |
2 Loadshare |
| 3295 |
3 Broadcast |
| 3296 |
|
| 3297 |
|
| 3298 |
|
| 3299 |
|
| 3300 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 59]</span></pre> |
| 3301 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-60" ></span> |
| 3302 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 3303 |
|
| 3304 |
|
| 3305 |
Within a particular Routing Context, Override, Loadshare and |
| 3306 |
Broadcast SHOULD NOT be mixed. The Override value indicates that |
| 3307 |
the ASP is operating in Override mode, and the ASP takes over all |
| 3308 |
traffic in an Application Server (i.e., primary/backup operation), |
| 3309 |
overriding any currently active ASPs in the AS. In Loadshare |
| 3310 |
mode, the ASP will share in the traffic distribution with any |
| 3311 |
other currently active ASPs. In Broadcast mode, the ASP will |
| 3312 |
receive the same messages as any other currently active ASP. |
| 3313 |
|
| 3314 |
Routing Context: n X 32-bit integers |
| 3315 |
|
| 3316 |
The optional Routing Context parameter contains (a list of) |
| 3317 |
integers indexing the Application Server traffic that the sending |
| 3318 |
ASP is configured/registered to receive. |
| 3319 |
|
| 3320 |
There is one-to-one relationship between an index entry and an SGP |
| 3321 |
Routing Key or AS Name. Because an AS can only appear in one |
| 3322 |
Network Appearance, the Network Appearance parameter is not |
| 3323 |
required in the ASP Active message. |
| 3324 |
|
| 3325 |
An Application Server Process may be configured to process traffic |
| 3326 |
for more than one logical Application Server. From the |
| 3327 |
perspective of an ASP, a Routing Context defines a range of |
| 3328 |
signalling traffic that the ASP is currently configured to receive |
| 3329 |
from the SGP. For example, an ASP could be configured to support |
| 3330 |
call processing for multiple ranges of PSTN trunks and therefore |
| 3331 |
receive related signalling traffic, identified by separate SS7 |
| 3332 |
DPC/OPC/CIC ranges. |
| 3333 |
|
| 3334 |
The format and description of the optional INFO String parameter is |
| 3335 |
the same as for the DUNA message (See <a href="#section-3.4.1">Section 3.4.1</a>). |
| 3336 |
|
| 3337 |
<span class="h4"><a class="selflink" id="section-3.7.2" href="#section-3.7.2">3.7.2</a> ASP Active Acknowledgement (ASP Active Ack)</span> |
| 3338 |
|
| 3339 |
The ASP Active Ack message is used to acknowledge an ASP Active |
| 3340 |
message received from a remote M3UA peer. |
| 3341 |
|
| 3342 |
The ASP Active Ack message contains the following parameters: |
| 3343 |
|
| 3344 |
Traffic Mode Type Optional |
| 3345 |
Routing Context Optional |
| 3346 |
INFO String Optional |
| 3347 |
|
| 3348 |
|
| 3349 |
|
| 3350 |
|
| 3351 |
|
| 3352 |
|
| 3353 |
|
| 3354 |
|
| 3355 |
|
| 3356 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 60]</span></pre> |
| 3357 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-61" ></span> |
| 3358 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 3359 |
|
| 3360 |
|
| 3361 |
The format for the ASP Active Ack message is as follows: |
| 3362 |
|
| 3363 |
0 1 2 3 |
| 3364 |
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 |
| 3365 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3366 |
| Tag = 0x000b | Length = 8 | |
| 3367 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3368 |
| Traffic Mode Type | |
| 3369 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3370 |
| Tag = 0x0006 | Length | |
| 3371 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3372 |
\ \ |
| 3373 |
/ Routing Context / |
| 3374 |
\ \ |
| 3375 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3376 |
| Tag = 0x0004 | Length | |
| 3377 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3378 |
\ \ |
| 3379 |
/ INFO String / |
| 3380 |
\ \ |
| 3381 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3382 |
|
| 3383 |
The format and description of the optional INFO String parameter is |
| 3384 |
the same as for the DUNA message (See <a href="#section-3.4.1">Section 3.4.1</a>). |
| 3385 |
|
| 3386 |
The INFO String in an ASP Active Ack message is independent from the |
| 3387 |
INFO String in the ASP Active message (i.e., it does not have to echo |
| 3388 |
back the INFO String received). |
| 3389 |
|
| 3390 |
The format of the Traffic Mode Type and Routing Context parameters is |
| 3391 |
the same as for the ASP Active message. (See <a href="#section-3.7.1">Section 3.7.1</a>). |
| 3392 |
|
| 3393 |
<span class="h4"><a class="selflink" id="section-3.7.3" href="#section-3.7.3">3.7.3</a> ASP Inactive</span> |
| 3394 |
|
| 3395 |
The ASP Inactive message is sent by an ASP to indicate to a remote |
| 3396 |
M3UA peer that it is no longer an active ASP to be used from within a |
| 3397 |
list of ASPs. The ASP Inactive message affects only the ASP state in |
| 3398 |
the Routing Keys identified by the Routing Contexts, if present. |
| 3399 |
|
| 3400 |
The ASP Inactive message contains the following parameters: |
| 3401 |
|
| 3402 |
Routing Context Optional |
| 3403 |
INFO String Optional |
| 3404 |
|
| 3405 |
|
| 3406 |
|
| 3407 |
|
| 3408 |
|
| 3409 |
|
| 3410 |
|
| 3411 |
|
| 3412 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 61]</span></pre> |
| 3413 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-62" ></span> |
| 3414 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 3415 |
|
| 3416 |
|
| 3417 |
The format for the ASP Inactive message parameters is as follows: |
| 3418 |
|
| 3419 |
0 1 2 3 |
| 3420 |
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 |
| 3421 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3422 |
| Tag = 0x0006 | Length | |
| 3423 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3424 |
\ \ |
| 3425 |
/ Routing Context / |
| 3426 |
\ \ |
| 3427 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3428 |
| Tag = 0x0004 | Length | |
| 3429 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3430 |
\ \ |
| 3431 |
/ INFO String / |
| 3432 |
\ \ |
| 3433 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3434 |
|
| 3435 |
The format and description of the optional Routing Context and INFO |
| 3436 |
String parameters is the same as for the ASP Active message (See |
| 3437 |
<a href="#section-3.5.5">Section 3.5.5</a>.) |
| 3438 |
|
| 3439 |
<span class="h4"><a class="selflink" id="section-3.7.4" href="#section-3.7.4">3.7.4</a> ASP Inactive Acknowledgement (ASP Inactive Ack)</span> |
| 3440 |
|
| 3441 |
The ASP Inactive Ack message is used to acknowledge an ASP Inactive |
| 3442 |
message received from a remote M3UA peer. |
| 3443 |
|
| 3444 |
The ASP Inactive Ack message contains the following parameters: |
| 3445 |
|
| 3446 |
Routing Context Optional |
| 3447 |
INFO String Optional |
| 3448 |
|
| 3449 |
|
| 3450 |
|
| 3451 |
|
| 3452 |
|
| 3453 |
|
| 3454 |
|
| 3455 |
|
| 3456 |
|
| 3457 |
|
| 3458 |
|
| 3459 |
|
| 3460 |
|
| 3461 |
|
| 3462 |
|
| 3463 |
|
| 3464 |
|
| 3465 |
|
| 3466 |
|
| 3467 |
|
| 3468 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 62]</span></pre> |
| 3469 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-63" ></span> |
| 3470 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 3471 |
|
| 3472 |
|
| 3473 |
The format for the ASP Inactive Ack message is as follows: |
| 3474 |
|
| 3475 |
0 1 2 3 |
| 3476 |
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 |
| 3477 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3478 |
| Tag = 0x0006 | Length | |
| 3479 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3480 |
\ \ |
| 3481 |
/ Routing Context / |
| 3482 |
\ \ |
| 3483 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3484 |
| Tag = 0x0004 | Length | |
| 3485 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3486 |
\ \ |
| 3487 |
/ INFO String / |
| 3488 |
\ \ |
| 3489 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3490 |
|
| 3491 |
The format and description of the optional INFO String parameter is |
| 3492 |
the same as for the DUNA message (See <a href="#section-3.4.1">Section 3.4.1</a>.) |
| 3493 |
|
| 3494 |
The INFO String in an ASP Inactive Ack message is independent from |
| 3495 |
the INFO String in the ASP Inactive message (i.e., it does not have |
| 3496 |
to echo back the INFO String received). |
| 3497 |
|
| 3498 |
The format of the Routing Context parameter is the same as for the |
| 3499 |
ASP Inactive message. (See <a href="#section-3.7.3">Section 3.7.3</a>). |
| 3500 |
|
| 3501 |
<span class="h3"><a class="selflink" id="section-3.8" href="#section-3.8">3.8</a> Management (MGMT) Messages</span> |
| 3502 |
|
| 3503 |
<span class="h4"><a class="selflink" id="section-3.8.1" href="#section-3.8.1">3.8.1</a> Error</span> |
| 3504 |
|
| 3505 |
The Error message is used to notify a peer of an error event |
| 3506 |
associated with an incoming message. For example, the message type |
| 3507 |
might be unexpected given the current state, or a parameter value |
| 3508 |
might be invalid. |
| 3509 |
|
| 3510 |
The Error message contains the following parameters: |
| 3511 |
|
| 3512 |
Error Code Mandatory |
| 3513 |
Routing Context Mandatory* |
| 3514 |
Network Appearance Mandatory* |
| 3515 |
Affected Point Code Mandatory* |
| 3516 |
Diagnostic Information Optional |
| 3517 |
|
| 3518 |
(*) Only mandatory for specific Error Codes |
| 3519 |
|
| 3520 |
|
| 3521 |
|
| 3522 |
|
| 3523 |
|
| 3524 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 63]</span></pre> |
| 3525 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-64" ></span> |
| 3526 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 3527 |
|
| 3528 |
|
| 3529 |
The format for the Error message is as follows: |
| 3530 |
|
| 3531 |
0 1 2 3 |
| 3532 |
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 |
| 3533 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3534 |
| Tag = 0x000c | Length = 8 | |
| 3535 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3536 |
| Error Code | |
| 3537 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3538 |
| Tag = 0x0006 | Length | |
| 3539 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3540 |
\ \ |
| 3541 |
/ Routing Context / |
| 3542 |
\ \ |
| 3543 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3544 |
| Tag - 0x0012 | Length | |
| 3545 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3546 |
| Mask | Affected Point Code 1 | |
| 3547 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3548 |
\ \ |
| 3549 |
/ ... / |
| 3550 |
\ \ |
| 3551 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3552 |
| Mask | Affected Point Code n | |
| 3553 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3554 |
| Tag = 0x0200 | Length = 8 | |
| 3555 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3556 |
| Network Appearance | |
| 3557 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3558 |
| Tag = 0x0007 | Length | |
| 3559 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3560 |
\ \ |
| 3561 |
/ Diagnostic Information / |
| 3562 |
\ \ |
| 3563 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3564 |
|
| 3565 |
Error Code: 32-bits (unsigned integer) |
| 3566 |
|
| 3567 |
The Error Code parameter indicates the reason for the Error |
| 3568 |
Message. The Error parameter value can be one of the following |
| 3569 |
values: |
| 3570 |
|
| 3571 |
0x01 Invalid Version |
| 3572 |
0x02 Not Used in M3UA |
| 3573 |
0x03 Unsupported Message Class |
| 3574 |
0x04 Unsupported Message Type |
| 3575 |
0x05 Unsupported Traffic Mode Type |
| 3576 |
0x06 Unexpected Message |
| 3577 |
|
| 3578 |
|
| 3579 |
|
| 3580 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 64]</span></pre> |
| 3581 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-65" ></span> |
| 3582 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 3583 |
|
| 3584 |
|
| 3585 |
0x07 Protocol Error |
| 3586 |
0x08 Not used in M3UA |
| 3587 |
0x09 Invalid Stream Identifier |
| 3588 |
0x0a Not used in M3UA |
| 3589 |
0x0b Not used in M3UA |
| 3590 |
0x0c Not used in M3UA |
| 3591 |
0x0d Refused - Management Blocking |
| 3592 |
0x0e ASP Identifier Required |
| 3593 |
0x0f Invalid ASP Identifier |
| 3594 |
0x10 Not Used in M3UA |
| 3595 |
0x11 Invalid Parameter Value |
| 3596 |
0x12 Parameter Field Error |
| 3597 |
0x13 Unexpected Parameter |
| 3598 |
0x14 Destination Status Unknown |
| 3599 |
0x15 Invalid Network Appearance |
| 3600 |
0x16 Missing Parameter |
| 3601 |
0x17 Not Used in M3UA |
| 3602 |
0x18 Not Used in M3UA |
| 3603 |
0x19 Invalid Routing Context |
| 3604 |
0x1a No Configured AS for ASP |
| 3605 |
|
| 3606 |
The "Invalid Stream Identifier" error is sent if a message is |
| 3607 |
received on an unexpected SCTP stream (e.g., a MGMT message was |
| 3608 |
received on a stream other than "0"). Error messages MUST NOT be |
| 3609 |
generated in response to other Error messages. |
| 3610 |
|
| 3611 |
The "Unsupported Message Class" error is sent if a message with an |
| 3612 |
unexpected or unsupported Message Class is received. |
| 3613 |
|
| 3614 |
The "Unsupported Message Type" error is sent if a message with an |
| 3615 |
unexpected or unsupported Message Type is received. |
| 3616 |
|
| 3617 |
The "Unsupported Traffic Mode Type" error is sent by a SGP if an ASP |
| 3618 |
sends an ASP Active message with an unsupported Traffic Mode Type or |
| 3619 |
a Traffic Mode Type that is inconsistent with the presently |
| 3620 |
configured mode for the Application Server. An example would be a |
| 3621 |
case in which the SGP did not support loadsharing. |
| 3622 |
|
| 3623 |
The "Unexpected Message" error MAY be sent if a defined and |
| 3624 |
recognized message is received that is not expected in the current |
| 3625 |
state (in some cases the ASP may optionally silently discard the |
| 3626 |
message and not send an Error message). For example, silent discard |
| 3627 |
is used by an ASP if it received a DATA message from an SGP while it |
| 3628 |
was in the ASP-INACTIVE state. If the Unexpected message contained |
| 3629 |
Routing Context(s), the Routing Context(s) SHOULD be included in the |
| 3630 |
Error message. |
| 3631 |
|
| 3632 |
|
| 3633 |
|
| 3634 |
|
| 3635 |
|
| 3636 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 65]</span></pre> |
| 3637 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-66" ></span> |
| 3638 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 3639 |
|
| 3640 |
|
| 3641 |
The "Protocol Error" error is sent for any protocol anomaly (i.e., |
| 3642 |
reception of a parameter that is syntactically correct but unexpected |
| 3643 |
in the current situation. |
| 3644 |
|
| 3645 |
The "Invalid Stream Identifier" error is sent if a message is |
| 3646 |
received on an unexpected SCTP stream (e.g., a Management message was |
| 3647 |
received on a stream other than "0"). |
| 3648 |
|
| 3649 |
The "Refused - Management Blocking" error is sent when an ASP Up or |
| 3650 |
ASP Active message is received and the request is refused for |
| 3651 |
management reasons (e.g., management lockout"). If this error is in |
| 3652 |
response to an ASP Active message, the Routing Context(s) in the ASP |
| 3653 |
Active message SHOULD be included in the Error message. |
| 3654 |
|
| 3655 |
The "ASP Identifier Required" is sent by a SGP in response to an ASP |
| 3656 |
Up message which does not contain an ASP Identifier parameter when |
| 3657 |
the SGP requires one. The ASP SHOULD resend the ASP Up message with |
| 3658 |
an ASP Identifier. |
| 3659 |
|
| 3660 |
The "Invalid ASP Identifier" is sent by an SGP in response to an ASP |
| 3661 |
Up message with an invalid (i.e., non-unique) ASP Identifier. |
| 3662 |
|
| 3663 |
The "Invalid Parameter Value " error is sent if a message is received |
| 3664 |
with an invalid parameter value (e.g., a DUPU message was received |
| 3665 |
with a Mask value other than "0". |
| 3666 |
|
| 3667 |
The "Parameter Field Error" would be sent if a message is received |
| 3668 |
with a parameter having a wrong length field. |
| 3669 |
|
| 3670 |
The "Unexpected Parameter" error would be sent if a message contains |
| 3671 |
an invalid parameter. |
| 3672 |
|
| 3673 |
The "Destination Status Unknown" Error MAY be sent if a DAUD is |
| 3674 |
received at an SG enquiring of the availability/congestion status of |
| 3675 |
a destination, and the SG does not wish to provide the status (e.g., |
| 3676 |
the sender is not authorized to know the status). For this error, |
| 3677 |
the invalid or unauthorized Point Code(s) MUST be included along with |
| 3678 |
the Network Appearance and/or Routing Context associated with the |
| 3679 |
Point Code(s). |
| 3680 |
|
| 3681 |
The "Invalid Network Appearance" error is sent by a SGP if an ASP |
| 3682 |
sends a message with an invalid (unconfigured) Network Appearance |
| 3683 |
value. For this error, the invalid (unconfigured) Network Appearance |
| 3684 |
MUST be included in the Network Appearance parameter. |
| 3685 |
|
| 3686 |
|
| 3687 |
|
| 3688 |
|
| 3689 |
|
| 3690 |
|
| 3691 |
|
| 3692 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 66]</span></pre> |
| 3693 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-67" ></span> |
| 3694 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 3695 |
|
| 3696 |
|
| 3697 |
The "Missing Parameter" error would be sent if a mandatory parameter |
| 3698 |
were not included in a message. |
| 3699 |
|
| 3700 |
The "Invalid Routing Context" error is sent if a message is received |
| 3701 |
from a peer with an invalid (unconfigured) Routing Context value. |
| 3702 |
For this error, the invalid Routing Context(s) MUST be included in |
| 3703 |
the Error message. |
| 3704 |
|
| 3705 |
The "No Configured AS for ASP" error is sent if a message is received |
| 3706 |
from a peer without a Routing Context parameter and it is not known |
| 3707 |
by configuration data which Application Servers are referenced. |
| 3708 |
|
| 3709 |
Diagnostic Information: variable length |
| 3710 |
|
| 3711 |
When included, the optional Diagnostic information can be any |
| 3712 |
information germane to the error condition, to assist in |
| 3713 |
identification of the error condition. The Diagnostic information |
| 3714 |
SHOULD contain the offending message. |
| 3715 |
|
| 3716 |
<span class="h4"><a class="selflink" id="section-3.8.2" href="#section-3.8.2">3.8.2</a> Notify</span> |
| 3717 |
|
| 3718 |
The Notify message used to provide an autonomous indication of M3UA |
| 3719 |
events to an M3UA peer. |
| 3720 |
|
| 3721 |
The Notify message contains the following parameters: |
| 3722 |
|
| 3723 |
Status Mandatory |
| 3724 |
ASP Identifier Optional |
| 3725 |
Routing Context Optional |
| 3726 |
INFO String Optional |
| 3727 |
|
| 3728 |
|
| 3729 |
|
| 3730 |
|
| 3731 |
|
| 3732 |
|
| 3733 |
|
| 3734 |
|
| 3735 |
|
| 3736 |
|
| 3737 |
|
| 3738 |
|
| 3739 |
|
| 3740 |
|
| 3741 |
|
| 3742 |
|
| 3743 |
|
| 3744 |
|
| 3745 |
|
| 3746 |
|
| 3747 |
|
| 3748 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 67]</span></pre> |
| 3749 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-68" ></span> |
| 3750 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 3751 |
|
| 3752 |
|
| 3753 |
The format for the Notify message is as follows: |
| 3754 |
|
| 3755 |
0 1 2 3 |
| 3756 |
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 |
| 3757 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3758 |
| Tag = 0x000d | Length = 8 | |
| 3759 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3760 |
| Status Type | Status Information | |
| 3761 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3762 |
| Tag = 0x0011 | Length = 8 | |
| 3763 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3764 |
| ASP Identifier | |
| 3765 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3766 |
| Tag = 0x0006 | Length | |
| 3767 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3768 |
\ \ |
| 3769 |
/ Routing Context / |
| 3770 |
\ \ |
| 3771 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3772 |
| Tag = 0x0004 | Length | |
| 3773 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3774 |
\ \ |
| 3775 |
/ INFO String / |
| 3776 |
\ \ |
| 3777 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 3778 |
|
| 3779 |
Status Type: 16-bits (unsigned integer) |
| 3780 |
|
| 3781 |
The Status Type parameter identifies the type of the Notify |
| 3782 |
message. The following are the valid Status Type values: |
| 3783 |
|
| 3784 |
1 Application Server State Change (AS-State_Change) |
| 3785 |
2 Other |
| 3786 |
|
| 3787 |
Status Information: 16-bits (unsigned integer) |
| 3788 |
|
| 3789 |
The Status Information parameter contains more detailed |
| 3790 |
information for the notification, based on the value of the Status |
| 3791 |
Type. If the Status Type is AS-State_Change the following Status |
| 3792 |
Information values are used: |
| 3793 |
|
| 3794 |
1 reserved |
| 3795 |
2 Application Server Inactive (AS-INACTIVE) |
| 3796 |
3 Application Server Active (AS-ACTIVE) |
| 3797 |
4 Application Server Pending (AS-PENDING) |
| 3798 |
|
| 3799 |
|
| 3800 |
|
| 3801 |
|
| 3802 |
|
| 3803 |
|
| 3804 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 68]</span></pre> |
| 3805 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-69" ></span> |
| 3806 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 3807 |
|
| 3808 |
|
| 3809 |
These notifications are sent from an SGP to an ASP upon a change |
| 3810 |
in status of a particular Application Server. The value reflects |
| 3811 |
the new state of the Application Server. |
| 3812 |
|
| 3813 |
If the Status Type is Other, then the following Status Information |
| 3814 |
values are defined: |
| 3815 |
|
| 3816 |
1 Insufficient ASP Resources Active in AS |
| 3817 |
2 Alternate ASP Active |
| 3818 |
3 ASP Failure |
| 3819 |
|
| 3820 |
These notifications are not based on the SGP reporting the state |
| 3821 |
change of an ASP or AS. In the Insufficient ASP Resources case, the |
| 3822 |
SGP is indicating to an ASP_INACTIVE ASP in the AS that another ASP |
| 3823 |
is required to handle the load of the AS (Loadsharing or Broadcast |
| 3824 |
mode). For the Alternate ASP Active case, an ASP is informed when an |
| 3825 |
alternate ASP transitions to the ASP-ACTIVE state in Override mode. |
| 3826 |
The ASP Identifier (if available) of the Alternate ASP MUST be placed |
| 3827 |
in the message. For the ASP Failure case, the SGP is indicating to |
| 3828 |
ASP(s) in the AS that one of the ASPs has transitioned to ASP-DOWN. |
| 3829 |
The ASP Identifier (if available) of the failed ASP MUST be placed in |
| 3830 |
the message. |
| 3831 |
|
| 3832 |
The format and description of the optional ASP Identifier is the same |
| 3833 |
as for the ASP Up message (See <a href="#section-3.5.1">Section 3.5.1</a>). The format and |
| 3834 |
description of the Routing Context and Info String parameters is the |
| 3835 |
same as for the ASP Active message (See <a href="#section-3.7.1">Section 3.7.1</a>) |
| 3836 |
|
| 3837 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Procedures</span> |
| 3838 |
|
| 3839 |
The M3UA layer needs to respond to various local primitives it |
| 3840 |
receives from other layers as well as the messages that it receives |
| 3841 |
from the peer M3UA layer. This section describes the M3UA procedures |
| 3842 |
in response to these events. |
| 3843 |
|
| 3844 |
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a> Procedures to Support the M3UA-User</span> |
| 3845 |
|
| 3846 |
<span class="h4"><a class="selflink" id="section-4.1.1" href="#section-4.1.1">4.1.1</a> Receipt of Primitives from the M3UA-User</span> |
| 3847 |
|
| 3848 |
On receiving an MTP-TRANSFER request primitive from an upper layer at |
| 3849 |
an ASP/IPSP, or the nodal interworking function at an SGP, the M3UA |
| 3850 |
layer sends a corresponding DATA message (see <a href="#section-3">Section 3</a>) to its M3UA |
| 3851 |
peer. The M3UA peer receiving the DATA message sends an MTP-TRANSFER |
| 3852 |
indication primitive to the upper layer. |
| 3853 |
|
| 3854 |
|
| 3855 |
|
| 3856 |
|
| 3857 |
|
| 3858 |
|
| 3859 |
|
| 3860 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 69]</span></pre> |
| 3861 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-70" ></span> |
| 3862 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 3863 |
|
| 3864 |
|
| 3865 |
The M3UA message distribution function (see <a href="#section-1.4.2.1">Section 1.4.2.1</a>) |
| 3866 |
determines the Application Server (AS) based on comparing the |
| 3867 |
information in the MTP-TRANSFER request primitive with a provisioned |
| 3868 |
Routing Key. |
| 3869 |
|
| 3870 |
From the list of ASPs within the AS table, an ASP in the ASP-ACTIVE |
| 3871 |
state is selected and a DATA message is constructed and issued on the |
| 3872 |
corresponding SCTP association. If more than one ASP is in the ASP- |
| 3873 |
ACTIVE state (i.e., traffic is to be loadshared across more than one |
| 3874 |
ASP), one of the ASPs in the ASP-ACTIVE state is selected from the |
| 3875 |
list. If the ASPs are in Broadcast Mode, all active ASPs will be |
| 3876 |
selected and the message sent to each of the active ASPs. The |
| 3877 |
selection algorithm is implementation dependent but could, for |
| 3878 |
example, be round robin or based on the SLS or ISUP CIC. The |
| 3879 |
appropriate selection algorithm must be chosen carefully as it is |
| 3880 |
dependent on application assumptions and understanding of the degree |
| 3881 |
of state coordination between the ASP-ACTIVE ASPs in the AS. |
| 3882 |
|
| 3883 |
In addition, the message needs to be sent on the appropriate SCTP |
| 3884 |
stream, again taking care to meet the message sequencing needs of the |
| 3885 |
signalling application. DATA messages MUST be sent on an SCTP stream |
| 3886 |
other than stream '0'. |
| 3887 |
|
| 3888 |
When there is no Routing Key match, or only a partial match, for an |
| 3889 |
incoming SS7 message, a default treatment MAY be specified. Possible |
| 3890 |
solutions are to provide a default Application Server at the SGP that |
| 3891 |
directs all unallocated traffic to a (set of) default ASP(s), or to |
| 3892 |
drop the message and provide a notification to Layer Management in an |
| 3893 |
M-ERROR indication primitive. The treatment of unallocated traffic |
| 3894 |
is implementation dependent. |
| 3895 |
|
| 3896 |
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a> Receipt of Primitives from the Layer Management</span> |
| 3897 |
|
| 3898 |
On receiving primitives from the local Layer Management, the M3UA |
| 3899 |
layer will take the requested action and provide an appropriate |
| 3900 |
response primitive to Layer Management. |
| 3901 |
|
| 3902 |
An M-SCTP_ESTABLISH request primitive from Layer Management at an ASP |
| 3903 |
or IPSP will initiate the establishment of an SCTP association. The |
| 3904 |
M3UA layer will attempt to establish an SCTP association with the |
| 3905 |
remote M3UA peer by sending an SCTP-ASSOCIATE primitive to the local |
| 3906 |
SCTP layer. |
| 3907 |
|
| 3908 |
When an SCTP association has been successfully established, the SCTP |
| 3909 |
will send an SCTP-COMMUNICATION_UP notification primitive to the |
| 3910 |
local M3UA layer. At the SGP or IPSP that initiated the request, the |
| 3911 |
M3UA layer will send an M-SCTP_ESTABLISH confirm primitive to Layer |
| 3912 |
Management when the association setup is complete. At the peer M3UA |
| 3913 |
|
| 3914 |
|
| 3915 |
|
| 3916 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 70]</span></pre> |
| 3917 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-71" ></span> |
| 3918 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 3919 |
|
| 3920 |
|
| 3921 |
layer, an M-SCTP_ESTABLISH indication primitive is sent to Layer |
| 3922 |
Management upon successful completion of an incoming SCTP association |
| 3923 |
setup. |
| 3924 |
|
| 3925 |
An M-SCTP_RELEASE request primitive from Layer Management initiates |
| 3926 |
the teardown of an SCTP association. The M3UA layer accomplishes a |
| 3927 |
graceful shutdown of the SCTP association by sending an SCTP-SHUTDOWN |
| 3928 |
primitive to the SCTP layer. |
| 3929 |
|
| 3930 |
When the graceful shutdown of the SCTP association has been |
| 3931 |
accomplished, the SCTP layer returns an SCTP-SHUTDOWN_COMPLETE |
| 3932 |
notification primitive to the local M3UA layer. At the M3UA Layer |
| 3933 |
that initiated the request, the M3UA layer will send an M- |
| 3934 |
SCTP_RELEASE confirm primitive to Layer Management when the |
| 3935 |
association shutdown is complete. At the peer M3UA Layer, an M- |
| 3936 |
SCTP_RELEASE indication primitive is sent to Layer Management upon |
| 3937 |
abort or successful shutdown of an SCTP association. |
| 3938 |
|
| 3939 |
An M-SCTP_STATUS request primitive supports a Layer Management query |
| 3940 |
of the local status of a particular SCTP association. The M3UA layer |
| 3941 |
simply maps the M-SCTP_STATUS request primitive to an SCTP-STATUS |
| 3942 |
primitive to the SCTP layer. When the SCTP responds, the M3UA layer |
| 3943 |
maps the association status information to an M-SCTP_STATUS confirm |
| 3944 |
primitive. No peer protocol is invoked. |
| 3945 |
|
| 3946 |
Similar LM-to-M3UA-to-SCTP and/or SCTP-to-M3UA-to-LM primitive |
| 3947 |
mappings can be described for the various other SCTP Upper Layer |
| 3948 |
primitives in <a href="./rfc2960">RFC2960</a> [<a href="#ref-17" title=""Stream Control Transport Protocol"">17</a>] such as INITIALIZE, SET PRIMARY, CHANGE |
| 3949 |
HEARTBEAT, REQUEST HEARTBEAT, GET SRTT REPORT, SET FAILURE THRESHOLD, |
| 3950 |
SET PROTOCOL PARAMETERS, DESTROY SCTP INSTANCE, SEND FAILURE, AND |
| 3951 |
NETWORK STATUS CHANGE. Alternatively, these SCTP Upper Layer |
| 3952 |
primitives (and Status as well) can be considered for modeling |
| 3953 |
purposes as a Layer Management interaction directly with the SCTP |
| 3954 |
Layer. |
| 3955 |
|
| 3956 |
M-NOTIFY indication and M-ERROR indication primitives indicate to |
| 3957 |
Layer Management the notification or error information contained in a |
| 3958 |
received M3UA Notify or Error message respectively. These |
| 3959 |
indications can also be generated based on local M3UA events. |
| 3960 |
|
| 3961 |
An M-ASP_STATUS request primitive supports a Layer Management query |
| 3962 |
of the status of a particular local or remote ASP. The M3UA layer |
| 3963 |
responds with the status in an M-ASP_STATUS confirm primitive. No |
| 3964 |
M3UA peer protocol is invoked. |
| 3965 |
|
| 3966 |
|
| 3967 |
|
| 3968 |
|
| 3969 |
|
| 3970 |
|
| 3971 |
|
| 3972 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 71]</span></pre> |
| 3973 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-72" ></span> |
| 3974 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 3975 |
|
| 3976 |
|
| 3977 |
An M-AS_STATUS request supports a Layer Management query of the |
| 3978 |
status of a particular AS. The M3UA responds with an M-AS_STATUS |
| 3979 |
confirm primitive. No M3UA peer protocol is invoked. |
| 3980 |
|
| 3981 |
M-ASP_UP request, M-ASP_DOWN request, M-ASP_ACTIVE request and M- |
| 3982 |
ASP_INACTIVE request primitives allow Layer Management at an ASP to |
| 3983 |
initiate state changes. Upon successful completion, a corresponding |
| 3984 |
confirm primitive is provided by the M3UA layer to Layer Management. |
| 3985 |
If an invocation is unsuccessful, an Error indication primitive is |
| 3986 |
provided in the primitive. These requests result in outgoing ASP Up, |
| 3987 |
ASP Down, ASP Active and ASP Inactive messages to the remote M3UA |
| 3988 |
peer at an SGP or IPSP. |
| 3989 |
|
| 3990 |
<span class="h4"><a class="selflink" id="section-4.2.1" href="#section-4.2.1">4.2.1</a> Receipt of M3UA Peer Management Messages</span> |
| 3991 |
|
| 3992 |
Upon successful state changes resulting from reception of ASP Up, ASP |
| 3993 |
Down, ASP Active and ASP Inactive messages from a peer M3UA, the M3UA |
| 3994 |
layer MAY invoke corresponding M-ASP_UP, M-ASP_DOWN, M-ASP_ACTIVE and |
| 3995 |
M-ASP_INACTIVE, M-AS_ACTIVE, M-AS_INACTIVE, and M-AS_DOWN indication |
| 3996 |
primitives to the local Layer Management. |
| 3997 |
|
| 3998 |
M-NOTIFY indication and M-ERROR indication primitives indicate to |
| 3999 |
Layer Management the notification or error information contained in a |
| 4000 |
received M3UA Notify or Error message. These indications can also be |
| 4001 |
generated based on local M3UA events. |
| 4002 |
|
| 4003 |
All non-Transfer and non-SSNM, messages, except BEAT and BEAT Ack, |
| 4004 |
SHOULD be sent with sequenced delivery to ensure ordering. ASPTM |
| 4005 |
messages MAY be sent on one of the streams used to carry the data |
| 4006 |
traffic related to the Routing Context(s), to minimize possible |
| 4007 |
message loss. BEAT and BEAT Ack messages MAY be sent using out-of- |
| 4008 |
order delivery, and MAY be sent on any stream. |
| 4009 |
|
| 4010 |
<span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a> AS and ASP State Maintenance</span> |
| 4011 |
|
| 4012 |
The M3UA layer on the SGP maintains the state of each remote ASP, in |
| 4013 |
each Application Server that the ASP is configured to receive |
| 4014 |
traffic, as input to the M3UA message distribution function. |
| 4015 |
Similarly, where IPSPs use M3UA in a point-to-point fashion, the M3UA |
| 4016 |
layer in an IPSP maintains the state of remote IPSPs. For the |
| 4017 |
purposes of the following procedures, only the SGP/ASP case is |
| 4018 |
described but the SGP side of the procedures also apply to an IPSP |
| 4019 |
sending traffic to an AS consisting of a set of remote IPSPs. |
| 4020 |
|
| 4021 |
|
| 4022 |
|
| 4023 |
|
| 4024 |
|
| 4025 |
|
| 4026 |
|
| 4027 |
|
| 4028 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 72]</span></pre> |
| 4029 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-73" ></span> |
| 4030 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 4031 |
|
| 4032 |
|
| 4033 |
<span class="h4"><a class="selflink" id="section-4.3.1" href="#section-4.3.1">4.3.1</a> ASP States</span> |
| 4034 |
|
| 4035 |
The state of each remote ASP, in each AS that it is configured to |
| 4036 |
operate, is maintained in the M3UA layer in the SGP. The state of a |
| 4037 |
particular ASP in a particular AS changes due to events. The events |
| 4038 |
include: |
| 4039 |
|
| 4040 |
* Reception of messages from the peer M3UA layer at the ASP; |
| 4041 |
* Reception of some messages from the peer M3UA layer at other ASPs |
| 4042 |
in the AS (e.g., ASP Active message indicating "Override"); |
| 4043 |
* Reception of indications from the SCTP layer; or |
| 4044 |
* Local Management intervention. |
| 4045 |
|
| 4046 |
The ASP state transition diagram is shown in Figure 3. The possible |
| 4047 |
states of an ASP are: |
| 4048 |
|
| 4049 |
ASP-DOWN: The remote M3UA peer at the ASP is unavailable and/or the |
| 4050 |
related SCTP association is down. Initially all ASPs will be in this |
| 4051 |
state. An ASP in this state SHOULD NOT be sent any M3UA messages, |
| 4052 |
with the exception of Heartbeat, ASP Down Ack and Error messages. |
| 4053 |
|
| 4054 |
ASP-INACTIVE: The remote M3UA peer at the ASP is available (and the |
| 4055 |
related SCTP association is up) but application traffic is stopped. |
| 4056 |
In this state the ASP SHOULD NOT be sent any DATA or SSNM messages |
| 4057 |
for the AS for which the ASP is inactive. |
| 4058 |
|
| 4059 |
ASP-ACTIVE: The remote M3UA peer at the ASP is available and |
| 4060 |
application traffic is active (for a particular Routing Context or |
| 4061 |
set of Routing Contexts). |
| 4062 |
|
| 4063 |
SCTP CDI: The SCTP CDI denotes the local SCTP layer's Communication |
| 4064 |
Down Indication to the Upper Layer Protocol (M3UA) on an SGP. The |
| 4065 |
local SCTP layer will send this indication when it detects the loss |
| 4066 |
of connectivity to the ASP's peer SCTP layer. SCTP CDI is understood |
| 4067 |
as either a SHUTDOWN_COMPLETE notification or COMMUNICATION_LOST |
| 4068 |
notification from the SCTP layer. |
| 4069 |
|
| 4070 |
SCTP RI: The local SCTP layer's Restart indication to the upper layer |
| 4071 |
protocol (M3UA) on an SG. The local SCTP will send this indication |
| 4072 |
when it detects a restart from the ASP's peer SCTP layer. |
| 4073 |
|
| 4074 |
|
| 4075 |
|
| 4076 |
|
| 4077 |
|
| 4078 |
|
| 4079 |
|
| 4080 |
|
| 4081 |
|
| 4082 |
|
| 4083 |
|
| 4084 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 73]</span></pre> |
| 4085 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-74" ></span> |
| 4086 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 4087 |
|
| 4088 |
|
| 4089 |
Figure 3: ASP State Transition Diagram, per AS |
| 4090 |
|
| 4091 |
+--------------+ |
| 4092 |
| | |
| 4093 |
+----------------------| ASP-ACTIVE | |
| 4094 |
| Other +-------| | |
| 4095 |
| ASP in AS | +--------------+ |
| 4096 |
| Overrides | ^ | |
| 4097 |
| | ASP | | ASP |
| 4098 |
| | Active | | Inactive |
| 4099 |
| | | v |
| 4100 |
| | +--------------+ |
| 4101 |
| | | | |
| 4102 |
| +------>| ASP-INACTIVE | |
| 4103 |
| +--------------+ |
| 4104 |
| ^ | |
| 4105 |
ASP Down/ | ASP | | ASP Down / |
| 4106 |
SCTP CDI/ | Up | | SCTP CDI/ |
| 4107 |
SCTP RI | | v SCTP RI |
| 4108 |
| +--------------+ |
| 4109 |
| | | |
| 4110 |
+--------------------->| ASP-DOWN | |
| 4111 |
| | |
| 4112 |
+--------------+ |
| 4113 |
|
| 4114 |
<span class="h4"><a class="selflink" id="section-4.3.2" href="#section-4.3.2">4.3.2</a> AS States</span> |
| 4115 |
|
| 4116 |
The state of the AS is maintained in the M3UA layer on the SGPs. The |
| 4117 |
state of an AS changes due to events. These events include: |
| 4118 |
|
| 4119 |
* ASP state transitions |
| 4120 |
* Recovery timer triggers |
| 4121 |
|
| 4122 |
The possible states of an AS are: |
| 4123 |
|
| 4124 |
AS-DOWN: The Application Server is unavailable. This state implies |
| 4125 |
that all related ASPs are in the ASP-DOWN state for this AS. |
| 4126 |
Initially the AS will be in this state. An Application Server is in |
| 4127 |
the AS-DOWN state when it is removed from a configuration. |
| 4128 |
|
| 4129 |
AS-INACTIVE: The Application Server is available but no application |
| 4130 |
traffic is active (i.e., one or more related ASPs are in the ASP- |
| 4131 |
INACTIVE state, but none in the ASP-ACTIVE state). The recovery |
| 4132 |
timer T(r) is not running or has expired. |
| 4133 |
|
| 4134 |
|
| 4135 |
|
| 4136 |
|
| 4137 |
|
| 4138 |
|
| 4139 |
|
| 4140 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 74]</span></pre> |
| 4141 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-75" ></span> |
| 4142 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 4143 |
|
| 4144 |
|
| 4145 |
AS-ACTIVE: The Application Server is available and application |
| 4146 |
traffic is active. This state implies that at least one ASP is in |
| 4147 |
the ASP-ACTIVE state. |
| 4148 |
|
| 4149 |
AS-PENDING: An active ASP has transitioned to ASP-INACTIVE or ASP- |
| 4150 |
DOWN and it was the last remaining active ASP in the AS. A recovery |
| 4151 |
timer T(r) SHOULD be started and all incoming signalling messages |
| 4152 |
SHOULD be queued by the SGP. If an ASP becomes ASP-ACTIVE before T(r) |
| 4153 |
expires, the AS is moved to the AS-ACTIVE state and all the queued |
| 4154 |
messages will be sent to the ASP. |
| 4155 |
|
| 4156 |
If T(r) expires before an ASP becomes ASP-ACTIVE, and the SGP has no |
| 4157 |
alternative, the SGP may stops queuing messages and discards all |
| 4158 |
previously queued messages. The AS will move to the AS-INACTIVE |
| 4159 |
state. |
| 4160 |
|
| 4161 |
If at least one ASP is in ASP-INACTIVE state, otherwise it will move |
| 4162 |
to AS-DOWN state. |
| 4163 |
|
| 4164 |
Figure 4 shows an example AS state machine for the case where the |
| 4165 |
AS/ASP data is preconfigured. For other cases where the AS/ASP |
| 4166 |
configuration data is created dynamically, there would be differences |
| 4167 |
in the state machine, especially at creation of the AS. |
| 4168 |
|
| 4169 |
|
| 4170 |
|
| 4171 |
|
| 4172 |
|
| 4173 |
|
| 4174 |
|
| 4175 |
|
| 4176 |
|
| 4177 |
|
| 4178 |
|
| 4179 |
|
| 4180 |
|
| 4181 |
|
| 4182 |
|
| 4183 |
|
| 4184 |
|
| 4185 |
|
| 4186 |
|
| 4187 |
|
| 4188 |
|
| 4189 |
|
| 4190 |
|
| 4191 |
|
| 4192 |
|
| 4193 |
|
| 4194 |
|
| 4195 |
|
| 4196 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 75]</span></pre> |
| 4197 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-76" ></span> |
| 4198 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 4199 |
|
| 4200 |
|
| 4201 |
Figure 4: AS State Transition Diagram |
| 4202 |
|
| 4203 |
+----------+ one ASP trans to ACTIVE +-------------+ |
| 4204 |
| AS- |---------------------------->| AS- | |
| 4205 |
| INACTIVE | | ACTIVE | |
| 4206 |
| |<--- | | |
| 4207 |
+----------+ \ +-------------+ |
| 4208 |
^ | \ Tr Expiry, ^ | |
| 4209 |
| | \ at least one | | |
| 4210 |
| | \ ASP in ASP-INACTIVE | | |
| 4211 |
| | \ | | |
| 4212 |
| | \ | | |
| 4213 |
| | \ | | |
| 4214 |
one ASP | | all ASP \ one ASP | | Last ACTIVE |
| 4215 |
trans | | trans to \ trans to | | ASP trans to |
| 4216 |
to | | ASP-DOWN -------\ ASP- | | ASP-INACTIVE |
| 4217 |
ASP- | | \ ACTIVE | | or ASP-DOWN |
| 4218 |
INACTIVE| | \ | | (start Tr) |
| 4219 |
| | \ | | |
| 4220 |
| | \ | | |
| 4221 |
| v \ | v |
| 4222 |
+----------+ \ +-------------+ |
| 4223 |
| | --| | |
| 4224 |
| AS-DOWN | | AS-PENDING | |
| 4225 |
| | | (queuing) | |
| 4226 |
| |<----------------------------| | |
| 4227 |
+----------+ Tr Expiry and no ASP +-------------+ |
| 4228 |
in ASP-INACTIVE state) |
| 4229 |
|
| 4230 |
Tr = Recovery Timer |
| 4231 |
|
| 4232 |
For example, where the AS/ASP configuration data is not created until |
| 4233 |
Registration of the first ASP, the AS-INACTIVE state is entered |
| 4234 |
directly upon the first successful REG REQ from an ASP. Another |
| 4235 |
example is where the AS/ASP configuration data is not created until |
| 4236 |
the first ASP successfully enters the ASP-ACTIVE state. In this case |
| 4237 |
the AS-ACTIVE state is entered directly. |
| 4238 |
|
| 4239 |
<span class="h4"><a class="selflink" id="section-4.3.3" href="#section-4.3.3">4.3.3</a> M3UA Management Procedures for Primitives</span> |
| 4240 |
|
| 4241 |
Before the establishment of an SCTP association the ASP state at both |
| 4242 |
the SGP and ASP is assumed to be in the state ASP-DOWN. |
| 4243 |
|
| 4244 |
Once the SCTP association is established (see <a href="#section-4.2">Section 4.2</a>) and |
| 4245 |
assuming that the local M3UA-User is ready, the local M3UA ASP |
| 4246 |
Maintenance (ASPM) function will initiate the relevant procedures, |
| 4247 |
using the ASP Up/ASP Down/ASP Active/ASP Inactive messages to convey |
| 4248 |
the ASP state to the SGP (see <a href="#section-4.3.4">Section 4.3.4</a>). |
| 4249 |
|
| 4250 |
|
| 4251 |
|
| 4252 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 76]</span></pre> |
| 4253 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-77" ></span> |
| 4254 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 4255 |
|
| 4256 |
|
| 4257 |
If the M3UA layer subsequently receives an SCTP-COMMUNICATION_DOWN or |
| 4258 |
SCTP-RESTART indication primitive from the underlying SCTP layer, it |
| 4259 |
will inform the Layer Management by invoking the M-SCTP_STATUS |
| 4260 |
indication primitive. The state of the ASP will be moved to ASP-DOWN. |
| 4261 |
At an ASP, the MTP3-User will be informed of the unavailability of |
| 4262 |
any affected SS7 destinations through the use of MTP-PAUSE indication |
| 4263 |
primitives. |
| 4264 |
|
| 4265 |
In the case of SCTP-COMMUNICATION_DOWN, the SCTP client MAY try to |
| 4266 |
re-establish the SCTP Association. This MAY be done by the M3UA |
| 4267 |
layer automatically, or Layer Management MAY re-establish using the |
| 4268 |
M-SCTP_ESTABLISH request primitive. |
| 4269 |
|
| 4270 |
In the case of an SCTP-RESTART indication at an ASP, the ASP is now |
| 4271 |
considered by its M3UA peer to be in the ASP-DOWN state. The ASP, if |
| 4272 |
it is to recover, must begin any recovery with the ASP-Up procedure. |
| 4273 |
|
| 4274 |
<span class="h4"><a class="selflink" id="section-4.3.4" href="#section-4.3.4">4.3.4</a> ASPM Procedures for Peer-to-Peer Messages</span> |
| 4275 |
|
| 4276 |
<span class="h5"><a class="selflink" id="section-4.3.4.1" href="#section-4.3.4.1">4.3.4.1</a> ASP Up Procedures</span> |
| 4277 |
|
| 4278 |
After an ASP has successfully established an SCTP association to an |
| 4279 |
SGP, the SGP waits for the ASP to send an ASP Up message, indicating |
| 4280 |
that the ASP M3UA peer is available. The ASP is always the initiator |
| 4281 |
of the ASP Up message. This action MAY be initiated at the ASP by an |
| 4282 |
M-ASP_UP request primitive from Layer Management or MAY be initiated |
| 4283 |
automatically by an M3UA management function. |
| 4284 |
|
| 4285 |
When an ASP Up message is received at an SGP and internally the |
| 4286 |
remote ASP is in the ASP-DOWN state and not considered locked out for |
| 4287 |
local management reasons, the SGP marks the remote ASP in the state |
| 4288 |
ASP-INACTIVE and informs Layer Management with an M-ASP_Up indication |
| 4289 |
primitive. If the SGP is aware, via current configuration data, |
| 4290 |
which Application Servers the ASP is configured to operate in, the |
| 4291 |
SGP updates the ASP state to ASP-INACTIVE in each AS that it is a |
| 4292 |
member. |
| 4293 |
|
| 4294 |
Alternatively, the SGP may move the ASP into a pool of Inactive ASPs |
| 4295 |
available for future configuration within Application Server(s), |
| 4296 |
determined in a subsequent Registration Request or ASP Active |
| 4297 |
procedure. If the ASP Up message contains an ASP Identifier, the SGP |
| 4298 |
should save the ASP Identifier for that ASP. The SGP MUST send an ASP |
| 4299 |
Up Ack message in response to a received ASP Up message even if the |
| 4300 |
ASP is already marked as ASP-INACTIVE at the SGP. |
| 4301 |
|
| 4302 |
|
| 4303 |
|
| 4304 |
|
| 4305 |
|
| 4306 |
|
| 4307 |
|
| 4308 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 77]</span></pre> |
| 4309 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-78" ></span> |
| 4310 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 4311 |
|
| 4312 |
|
| 4313 |
If for any local reason (e.g., management lockout) the SGP cannot |
| 4314 |
respond with an ASP Up Ack message, the SGP responds to an ASP Up |
| 4315 |
message with an Error message with reason "Refused - Management |
| 4316 |
Blocking". |
| 4317 |
|
| 4318 |
At the ASP, the ASP Up Ack message received is not acknowledged. |
| 4319 |
Layer Management is informed with an M-ASP_UP confirm primitive. |
| 4320 |
|
| 4321 |
When the ASP sends an ASP Up message it starts timer T(ack). If the |
| 4322 |
ASP does not receive a response to an ASP Up message within T(ack), |
| 4323 |
the ASP MAY restart T(ack) and resend ASP Up messages until it |
| 4324 |
receives an ASP Up Ack message. T(ack) is provisionable, with a |
| 4325 |
default of 2 seconds. Alternatively, retransmission of ASP Up |
| 4326 |
messages MAY be put under control of Layer Management. In this |
| 4327 |
method, expiry of T(ack) results in an M-ASP_UP confirm primitive |
| 4328 |
carrying a negative indication. |
| 4329 |
|
| 4330 |
The ASP must wait for the ASP Up Ack message before sending any other |
| 4331 |
M3UA messages (e.g., ASP Active or REG REQ). If the SGP receives any |
| 4332 |
other M3UA messages before an ASP Up message is received (other than |
| 4333 |
ASP Down - see <a href="#section-4.3.4.2">Section 4.3.4.2</a>), the SGP MAY discard them. |
| 4334 |
|
| 4335 |
If an ASP Up message is received and internally the remote ASP is in |
| 4336 |
the ASP-ACTIVE state, an ASP Up Ack message is returned, as well as |
| 4337 |
an Error message ("Unexpected Message), and the remote ASP state is |
| 4338 |
changed to ASP-INACTIVE in all relevant Application Servers. |
| 4339 |
|
| 4340 |
If an ASP Up message is received and internally the remote ASP is |
| 4341 |
already in the ASP-INACTIVE state, an ASP Up Ack message is returned |
| 4342 |
and no further action is taken. |
| 4343 |
|
| 4344 |
<span class="h6"><a class="selflink" id="section-4.3.4.1.1" href="#section-4.3.4.1.1">4.3.4.1.1</a> M3UA Version Control</span> |
| 4345 |
|
| 4346 |
If an ASP Up message with an unsupported version is received, the |
| 4347 |
receiving end responds with an Error message, indicating the version |
| 4348 |
the receiving node supports and notifies Layer Management. |
| 4349 |
|
| 4350 |
This is useful when protocol version upgrades are being performed in |
| 4351 |
a network. A node upgraded to a newer version should support the |
| 4352 |
older versions used on other nodes it is communicating with. Because |
| 4353 |
ASPs initiate the ASP Up procedure it is assumed that the Error |
| 4354 |
message would normally come from the SGP. |
| 4355 |
|
| 4356 |
|
| 4357 |
|
| 4358 |
|
| 4359 |
|
| 4360 |
|
| 4361 |
|
| 4362 |
|
| 4363 |
|
| 4364 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 78]</span></pre> |
| 4365 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-79" ></span> |
| 4366 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 4367 |
|
| 4368 |
|
| 4369 |
<span class="h6"><a class="selflink" id="section-4.3.4.1.2" href="#section-4.3.4.1.2">4.3.4.1.2</a> IPSP Considerations (ASP Up)</span> |
| 4370 |
|
| 4371 |
An IPSP may be considered in the ASP-INACTIVE state after an ASP Up |
| 4372 |
or ASP Up Ack has been received from it. An IPSP can be considered |
| 4373 |
in the ASP-DOWN state after an ASP Down or ASP Down Ack has been |
| 4374 |
received from it. The IPSP may inform Layer Management of the change |
| 4375 |
in state of the remote IPSP using M-ASP_UP or M-ASP_DN indication or |
| 4376 |
confirmation primitives. |
| 4377 |
|
| 4378 |
Alternatively, an interchange of ASP Up messages from each end can be |
| 4379 |
performed. This option follows the ASP state transition diagram. It |
| 4380 |
would need four messages for completion. |
| 4381 |
|
| 4382 |
If for any local reason (e.g., management lockout) an IPSP cannot |
| 4383 |
respond to an ASP Up message with an ASP Up Ack message, it responds |
| 4384 |
to an ASP Up message with an Error message with reason "Refused |
| 4385 |
Management Blocking" and leaves the remote IPSP in the ASP-DOWN |
| 4386 |
state. |
| 4387 |
|
| 4388 |
<span class="h5"><a class="selflink" id="section-4.3.4.2" href="#section-4.3.4.2">4.3.4.2</a> ASP-Down Procedures</span> |
| 4389 |
|
| 4390 |
The ASP will send an ASP Down message to an SGP when the ASP wishes |
| 4391 |
to be removed from service in all Application Servers that it is a |
| 4392 |
member and no longer receive any DATA, SSNM or ASPTM messages. This |
| 4393 |
action MAY be initiated at the ASP by an M-ASP_DOWN request primitive |
| 4394 |
from Layer Management or MAY be initiated automatically by an M3UA |
| 4395 |
management function. |
| 4396 |
|
| 4397 |
Whether the ASP is permanently removed from any AS is a function of |
| 4398 |
configuration management. In the case where the ASP previously used |
| 4399 |
the Registration procedures (see <a href="#section-4.4.1">Section 4.4.1</a>) to register within |
| 4400 |
Application Servers but has not deregistered from all of them prior |
| 4401 |
to sending the ASP Down message, the SGP MUST consider the ASP as |
| 4402 |
Deregistered in all Application Servers that it is still a member. |
| 4403 |
|
| 4404 |
The SGP marks the ASP as ASP-DOWN, informs Layer Management with an |
| 4405 |
M-ASP_Down indication primitive, and returns an ASP Down Ack message |
| 4406 |
to the ASP. |
| 4407 |
|
| 4408 |
The SGP MUST send an ASP Down Ack message in response to a received |
| 4409 |
ASP Down message from the ASP even if the ASP is already marked as |
| 4410 |
ASP-DOWN at the SGP. |
| 4411 |
|
| 4412 |
At the ASP, the ASP Down Ack message received is not acknowledged. |
| 4413 |
Layer Management is informed with an M-ASP_DOWN confirm primitive. |
| 4414 |
If the ASP receives an ASP Down Ack without having sent an ASP Down |
| 4415 |
message, the ASP should now consider itself as in the ASP-DOWN state. |
| 4416 |
|
| 4417 |
|
| 4418 |
|
| 4419 |
|
| 4420 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 79]</span></pre> |
| 4421 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-80" ></span> |
| 4422 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 4423 |
|
| 4424 |
|
| 4425 |
If the ASP was previously in the ASP-ACTIVE or ASP-INACTIVE state, |
| 4426 |
the ASP should then initiate procedures to return itself to its |
| 4427 |
previous state. |
| 4428 |
|
| 4429 |
When the ASP sends an ASP Down message it starts timer T(ack). If |
| 4430 |
the ASP does not receive a response to an ASP Down message within |
| 4431 |
T(ack), the ASP MAY restart T(ack) and resend ASP Down messages until |
| 4432 |
it receives an ASP Down Ack message. T(ack) is provisionable, with a |
| 4433 |
default of 2 seconds. Alternatively, retransmission of ASP Down |
| 4434 |
messages MAY be put under control of Layer Management. In this |
| 4435 |
method, expiry of T(ack) results in an M-ASP_DOWN confirm primitive |
| 4436 |
carrying a negative indication. |
| 4437 |
|
| 4438 |
<span class="h5"><a class="selflink" id="section-4.3.4.3" href="#section-4.3.4.3">4.3.4.3</a> ASP Active Procedures</span> |
| 4439 |
|
| 4440 |
Anytime after the ASP has received an ASP Up Ack message from the SGP |
| 4441 |
or IPSP, the ASP MAY send an ASP Active message to the SGP indicating |
| 4442 |
that the ASP is ready to start processing traffic. This action MAY |
| 4443 |
be initiated at the ASP by an M-ASP_ACTIVE request primitive from |
| 4444 |
Layer Management or MAY be initiated automatically by an M3UA |
| 4445 |
management function. In the case where an ASP wishes to process the |
| 4446 |
traffic for more than one Application Server across a common SCTP |
| 4447 |
association, the ASP Active message(s) SHOULD contain a list of one |
| 4448 |
or more Routing Contexts to indicate for which Application Servers |
| 4449 |
the ASP Active message applies. It is not necessary for the ASP to |
| 4450 |
include all Routing Contexts of interest in a single ASP Active |
| 4451 |
message, thus requesting to become active in all Routing Contexts at |
| 4452 |
the same time. Multiple ASP Active messages MAY be used to activate |
| 4453 |
within the Application Servers independently, or in sets. In the |
| 4454 |
case where an ASP Active message does not contain a Routing Context |
| 4455 |
parameter, the receiver must know, via configuration data, which |
| 4456 |
Application Server(s) the ASP is a member. |
| 4457 |
|
| 4458 |
For the Application Servers that the ASP can be successfully |
| 4459 |
activated, the SGP or IPSP responds with one or more ASP Active Ack |
| 4460 |
messages, including the associated Routing Context(s) and reflecting |
| 4461 |
any Traffic Mode Type value present in the related ASP Active |
| 4462 |
message. The Routing Context parameter MUST be included in the ASP |
| 4463 |
Active Ack message(s) if the received ASP Active message contained |
| 4464 |
any Routing Contexts. Depending on any Traffic Mode Type request in |
| 4465 |
the ASP Active message, or local configuration data if there is no |
| 4466 |
request, the SGP moves the ASP to the correct ASP traffic state |
| 4467 |
within the associated Application Server(s). Layer Management is |
| 4468 |
informed with an M-ASP_Active indication. If the SGP or IPSP receives |
| 4469 |
any Data messages before an ASP Active message is received, the SGP |
| 4470 |
or IPSP MAY discard them. By sending an ASP Active Ack message, the |
| 4471 |
SGP or IPSP is now ready to receive and send traffic for the related |
| 4472 |
|
| 4473 |
|
| 4474 |
|
| 4475 |
|
| 4476 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 80]</span></pre> |
| 4477 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-81" ></span> |
| 4478 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 4479 |
|
| 4480 |
|
| 4481 |
Routing Context(s). The ASP SHOULD NOT send Data or SSNM messages |
| 4482 |
for the related Routing Context(s) before receiving an ASP Active Ack |
| 4483 |
message, or it will risk message loss. |
| 4484 |
|
| 4485 |
Multiple ASP Active Ack messages MAY be used in response to an ASP |
| 4486 |
Active message containing multiple Routing Contexts, allowing the SGP |
| 4487 |
or IPSP to independently acknowledge the ASP Active message for |
| 4488 |
different (sets of) Routing Contexts. The SGP or IPSP MUST send an |
| 4489 |
Error message ("Invalid Routing Context") for each Routing Context |
| 4490 |
value that the ASP cannot be successfully activated . |
| 4491 |
|
| 4492 |
In the case where an "out-of-the-blue" ASP Active message is received |
| 4493 |
(i.e., the ASP has not registered with the SG or the SG has no static |
| 4494 |
configuration data for the ASP), the message MAY be silently |
| 4495 |
discarded. |
| 4496 |
|
| 4497 |
The SGP MUST send an ASP Active Ack message in response to a received |
| 4498 |
ASP Active message from the ASP, if the ASP is already marked in the |
| 4499 |
ASP-ACTIVE state at the SGP. |
| 4500 |
|
| 4501 |
At the ASP, the ASP Active Ack message received is not acknowledged. |
| 4502 |
Layer Management is informed with an M-ASP_ACTIVE confirm primitive. |
| 4503 |
It is possible for the ASP to receive Data message(s) before the ASP |
| 4504 |
Active Ack message as the ASP Active Ack and Data messages from an SG |
| 4505 |
or IPSP may be sent on different SCTP streams. Message loss is |
| 4506 |
possible as the ASP does not consider itself in the ASP-ACTIVE state |
| 4507 |
until reception of the ASP Active Ack message. |
| 4508 |
|
| 4509 |
When the ASP sends an ASP Active message it starts timer T(ack). If |
| 4510 |
the ASP does not receive a response to an ASP Active message within |
| 4511 |
T(ack), the ASP MAY restart T(ack) and resend ASP Active messages |
| 4512 |
until it receives an ASP Active Ack message. T(ack) is |
| 4513 |
provisionable, with a default of 2 seconds. Alternatively, |
| 4514 |
retransmission of ASP Active messages MAY be put under control of |
| 4515 |
Layer Management. In this method, expiry of T(ack) results in an M- |
| 4516 |
ASP_ACTIVE confirm primitive carrying a negative indication. |
| 4517 |
|
| 4518 |
There are three modes of Application Server traffic handling in the |
| 4519 |
SGP M3UA layer: Override, Loadshare and Broadcast. When included, |
| 4520 |
the Traffic Mode Type parameter in the ASP Active message indicates |
| 4521 |
the traffic handling mode to be used in a particular Application |
| 4522 |
Server. If the SGP determines that the mode indicated in an ASP |
| 4523 |
Active message is unsupported or incompatible with the mode currently |
| 4524 |
configured for the AS, the SGP responds with an Error message |
| 4525 |
("Unsupported / Invalid Traffic Handling Mode"). If the traffic |
| 4526 |
handling mode of the Application Server is not already known via |
| 4527 |
|
| 4528 |
|
| 4529 |
|
| 4530 |
|
| 4531 |
|
| 4532 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 81]</span></pre> |
| 4533 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-82" ></span> |
| 4534 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 4535 |
|
| 4536 |
|
| 4537 |
configuration data, then the traffic handling mode indicated in the |
| 4538 |
first ASP Active message causing the transition of the Application |
| 4539 |
Server state to AS-ACTIVE MAY be used to set the mode. |
| 4540 |
|
| 4541 |
In the case of an Override mode AS, reception of an ASP Active |
| 4542 |
message at an SGP causes the (re)direction of all traffic for the AS |
| 4543 |
to the ASP that sent the ASP Active message. Any previously active |
| 4544 |
ASP in the AS is now considered to be in state ASP-INACTIVE and |
| 4545 |
SHOULD no longer receive traffic from the SGP within the AS. The SGP |
| 4546 |
or IPSP then MUST send a Notify message ("Alternate ASP_Active") to |
| 4547 |
the previously active ASP in the AS, and SHOULD stop traffic to/from |
| 4548 |
that ASP. The ASP receiving this Notify MUST consider itself now in |
| 4549 |
the ASP-INACTIVE state, if it is not already aware of this via |
| 4550 |
inter-ASP communication with the Overriding ASP. |
| 4551 |
|
| 4552 |
In the case of a Loadshare mode AS, reception of an ASP Active |
| 4553 |
message at an SGP or IPSP causes the direction of traffic to the ASP |
| 4554 |
sending the ASP Active message, in addition to all the other ASPs |
| 4555 |
that are currently active in the AS. The algorithm at the SGP for |
| 4556 |
loadsharing traffic within an AS to all the active ASPs is |
| 4557 |
implementation dependent. The algorithm could, for example, be |
| 4558 |
round-robin or based on information in the Data message (e.g., the |
| 4559 |
SLS, SCCP SSN, ISUP CIC value). |
| 4560 |
|
| 4561 |
An SGP or IPSP, upon reception of an ASP Active message for the first |
| 4562 |
ASP in a Loadshare AS, MAY choose not to direct traffic to a newly |
| 4563 |
active ASP until it determines that there are sufficient resources to |
| 4564 |
handle the expected load (e.g., until there are "n" ASPs in state |
| 4565 |
ASP-ACTIVE in the AS). In this case, the SGP or IPSP SHOULD withhold |
| 4566 |
the Notify (AS-ACTIVE) until there are sufficient resources. |
| 4567 |
|
| 4568 |
For the n+k redundancy case, ASPs which are in that AS should |
| 4569 |
coordinate among themselves the number of active ASPs in the AS, and |
| 4570 |
should start sending traffic only after n ASPs are active. |
| 4571 |
|
| 4572 |
All ASPs within a loadsharing mode AS must be able to process any |
| 4573 |
Data message received for the AS, to accommodate any potential |
| 4574 |
failover or rebalancing of the offered load. |
| 4575 |
|
| 4576 |
In the case of a Broadcast mode AS, reception of an ASP Active |
| 4577 |
message at an SGP or IPSP causes the direction of traffic to the ASP |
| 4578 |
sending the ASP Active message, in addition to all the other ASPs |
| 4579 |
that are currently active in the AS. The algorithm at the SGP for |
| 4580 |
broadcasting traffic within an AS to all the active ASPs is a simple |
| 4581 |
broadcast algorithm, where every message is sent to each of the |
| 4582 |
active ASPs. |
| 4583 |
|
| 4584 |
|
| 4585 |
|
| 4586 |
|
| 4587 |
|
| 4588 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 82]</span></pre> |
| 4589 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-83" ></span> |
| 4590 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 4591 |
|
| 4592 |
|
| 4593 |
An SGP or IPSP, upon reception of an ASP Active message for the first |
| 4594 |
ASP in a Broadcast AS, MAY choose not to direct traffic to a newly |
| 4595 |
active ASP until it determines that there are sufficient resources to |
| 4596 |
handle the expected load (e.g., until there are "n" ASPs in state |
| 4597 |
ASP-ACTIVE in the AS). In this case, the SGP or IPSP SHOULD withhold |
| 4598 |
the Notify (AS-ACTIVE) until there are sufficient resources. |
| 4599 |
|
| 4600 |
For the n+k redundancy case, ASPs which are in that AS should |
| 4601 |
coordinate among themselves the number of active ASPs in the AS, and |
| 4602 |
should start sending traffic only after n ASPs are active. |
| 4603 |
|
| 4604 |
Whenever an ASP in a Broadcast mode AS becomes ASP-ACTIVE, the SGP |
| 4605 |
MUST tag the first DATA message broadcast in each traffic flow with |
| 4606 |
|
| 4607 |
a unique Correlation Id parameter. The purpose of this Id is to |
| 4608 |
permit the newly active ASP to synchronize its processing of traffic |
| 4609 |
in each traffic flow with the other ASPs in the broadcast group. |
| 4610 |
|
| 4611 |
<span class="h6"><a class="selflink" id="section-4.3.4.3.1" href="#section-4.3.4.3.1">4.3.4.3.1</a> IPSP Considerations (ASP Active)</span> |
| 4612 |
|
| 4613 |
Either of the IPSPs can initiate communication. When an IPSP receives |
| 4614 |
an ASP Active, it should mark the peer as ASP-ACTIVE and return an |
| 4615 |
ASP Active Ack message. An ASP receiving an ASP Active Ack message |
| 4616 |
may mark the peer as ASP-Active, if it is not already in the ASP- |
| 4617 |
ACTIVE state. |
| 4618 |
|
| 4619 |
Alternatively, an interchange of ASP Active messages from each end |
| 4620 |
can be performed. This option follows the ASP state transition |
| 4621 |
diagram and gives the additional advantage of selecting a particular |
| 4622 |
AS to be activated from each end. It is especially useful when an |
| 4623 |
IPSP is serving more than one AS. It would need four messages for |
| 4624 |
completion. |
| 4625 |
|
| 4626 |
<span class="h5"><a class="selflink" id="section-4.3.4.4" href="#section-4.3.4.4">4.3.4.4</a> ASP Inactive Procedures</span> |
| 4627 |
|
| 4628 |
When an ASP wishes to withdraw from receiving traffic within an AS, |
| 4629 |
the ASP sends an ASP Inactive message to the SGP or IPSP. This |
| 4630 |
action MAY be initiated at the ASP by an M-ASP_INACTIVE request |
| 4631 |
primitive from Layer Management or MAY be initiated automatically by |
| 4632 |
an M3UA management function. In the case where an ASP is processing |
| 4633 |
the traffic for more than one Application Server across a common SCTP |
| 4634 |
association, the ASP Inactive message contains one or more Routing |
| 4635 |
Contexts to indicate for which Application Servers the ASP Inactive |
| 4636 |
message applies. In the case where an ASP Inactive message does not |
| 4637 |
contain a Routing Context parameter, the receiver must know, via |
| 4638 |
configuration data, which Application Servers the ASP is a member and |
| 4639 |
move the ASP to the ASP-INACTIVE state in all Application Servers. In |
| 4640 |
the case of an Override mode AS, where another ASP has already taken |
| 4641 |
|
| 4642 |
|
| 4643 |
|
| 4644 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 83]</span></pre> |
| 4645 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-84" ></span> |
| 4646 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 4647 |
|
| 4648 |
|
| 4649 |
over the traffic within the AS with an ASP Active ("Override") |
| 4650 |
message, the ASP that sends the ASP Inactive message is already |
| 4651 |
considered by the SGP to be in state ASP-INACTIVE. An ASP Inactive |
| 4652 |
Ack message is sent to the ASP, after ensuring that all traffic is |
| 4653 |
stopped to the ASP. |
| 4654 |
|
| 4655 |
In the case of a Loadshare mode AS, the SGP moves the ASP to the |
| 4656 |
ASP-INACTIVE state and the AS traffic is reallocated across the |
| 4657 |
remaining ASPs in the state ASP-ACTIVE, as per the loadsharing |
| 4658 |
algorithm currently used within the AS. A Notify message |
| 4659 |
("Insufficient ASP resources active in AS") MAY be sent to all |
| 4660 |
inactive ASPs, if required. An ASP Inactive Ack message is sent to |
| 4661 |
the ASP after all traffic is halted and Layer Management is informed |
| 4662 |
with an M-ASP_INACTIVE indication primitive. |
| 4663 |
|
| 4664 |
In the case of a Broadcast mode AS, the SGP moves the ASP to the |
| 4665 |
ASP-INACTIVE state and the AS traffic is broadcast only to the |
| 4666 |
remaining ASPs in the state ASP-ACTIVE. A Notify message |
| 4667 |
("Insufficient ASP resources active in AS") MAY be sent to all |
| 4668 |
inactive ASPs, if required. An ASP Inactive Ack message is sent to |
| 4669 |
the ASP after all traffic is halted and Layer Management is informed |
| 4670 |
with an M-ASP_INACTIVE indication primitive. |
| 4671 |
|
| 4672 |
Multiple ASP Inactive Ack messages MAY be used in response to an ASP |
| 4673 |
Inactive message containing multiple Routing Contexts, allowing the |
| 4674 |
SGP or IPSP to independently acknowledge for different (sets of) |
| 4675 |
Routing Contexts. The SGP or IPSP sends an Error message ("Invalid |
| 4676 |
Routing Context") message for each invalid or unconfigured Routing |
| 4677 |
Context value in a received ASP Inactive message. |
| 4678 |
|
| 4679 |
The SGP MUST send an ASP Inactive Ack message in response to a |
| 4680 |
received ASP Inactive message from the ASP and the ASP is already |
| 4681 |
marked as ASP-INACTIVE at the SGP. |
| 4682 |
|
| 4683 |
At the ASP, the ASP Inactive Ack message received is not |
| 4684 |
acknowledged. Layer Management is informed with an M-ASP_INACTIVE |
| 4685 |
confirm primitive. If the ASP receives an ASP Inactive Ack without |
| 4686 |
having sent an ASP Inactive message, the ASP should now consider |
| 4687 |
itself as in the ASP-INACTIVE state. If the ASP was previously in |
| 4688 |
the ASP-ACTIVE state, the ASP should then initiate procedures to |
| 4689 |
return itself to its previous state. |
| 4690 |
|
| 4691 |
When the ASP sends an ASP Inactive message it starts timer T(ack). |
| 4692 |
If the ASP does not receive a response to an ASP Inactive message |
| 4693 |
within T(ack), the ASP MAY restart T(ack) and resend ASP Inactive |
| 4694 |
messages until it receives an ASP Inactive Ack message. T(ack) is |
| 4695 |
provisionable, with a default of 2 seconds. Alternatively, |
| 4696 |
|
| 4697 |
|
| 4698 |
|
| 4699 |
|
| 4700 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 84]</span></pre> |
| 4701 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-85" ></span> |
| 4702 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 4703 |
|
| 4704 |
|
| 4705 |
retransmission of ASP Inactive messages MAY be put under control of |
| 4706 |
Layer Management. In this method, expiry of T(ack) results in a M- |
| 4707 |
ASP_Inactive confirm primitive carrying a negative indication. |
| 4708 |
|
| 4709 |
If no other ASPs in the Application Server are in the state ASP- |
| 4710 |
ACTIVE, the SGP MUST send a Notify message ("AS-Pending") to all of |
| 4711 |
the ASPs in the AS which are in the state ASP-INACTIVE. The SGP |
| 4712 |
SHOULD start buffering the incoming messages for T(r) seconds, after |
| 4713 |
which messages MAY be discarded. T(r) is configurable by the network |
| 4714 |
operator. If the SGP receives an ASP Active message from an ASP in |
| 4715 |
the AS before expiry of T(r), the buffered traffic is directed to |
| 4716 |
that ASP and the timer is cancelled. If T(r) expires, the AS is moved |
| 4717 |
to the AS-INACTIVE state. |
| 4718 |
|
| 4719 |
<span class="h6"><a class="selflink" id="section-4.3.4.4.1" href="#section-4.3.4.4.1">4.3.4.4.1</a> IPSP Considerations (ASP Inactive)</span> |
| 4720 |
|
| 4721 |
An IPSP may be considered in the ASP-INACTIVE state by a remote IPSP |
| 4722 |
after an ASP Inactive or ASP Inactive Ack message has been received |
| 4723 |
from it. |
| 4724 |
|
| 4725 |
Alternatively, an interchange of ASP Inactive messages from each end |
| 4726 |
can be performed. This option follows the ASP state transition |
| 4727 |
diagram and gives the additional advantage of selecting a particular |
| 4728 |
AS to be deactivated from each end. It is especially useful when an |
| 4729 |
IPSP is serving more than one AS. It would need four messages for |
| 4730 |
completion. |
| 4731 |
|
| 4732 |
<span class="h5"><a class="selflink" id="section-4.3.4.5" href="#section-4.3.4.5">4.3.4.5</a> Notify Procedures</span> |
| 4733 |
|
| 4734 |
A Notify message reflecting a change in the AS state MUST be sent to |
| 4735 |
all ASPs in the AS, except those in the ASP-DOWN state, with |
| 4736 |
appropriate Status Information and any ASP Identifier of the failed |
| 4737 |
ASP. At the ASP, Layer Management is informed with an M-NOTIFY |
| 4738 |
indication primitive. The Notify message must be sent whether the AS |
| 4739 |
state change was a result of an ASP failure or reception of an ASP |
| 4740 |
State management (ASPSM) / ASP Traffic Management (ASPTM) message. |
| 4741 |
In the second case, the Notify message MUST be sent after any related |
| 4742 |
acknowledgement messages (e.g., ASP Up Ack, ASP Down Ack, ASP Active |
| 4743 |
Ack, or ASP Inactive Ack). |
| 4744 |
|
| 4745 |
In the case where a Notify message ("AS-PENDING") message is sent by |
| 4746 |
an SGP that now has no ASPs active to service the traffic, or where a |
| 4747 |
Notify ("Insufficient ASP resources active in AS") message is sent in |
| 4748 |
the Loadshare or Broadcast mode, the Notify message does not |
| 4749 |
explicitly compel the ASP(s) receiving the message to become active. |
| 4750 |
The ASPs remain in control of what (and when) traffic action is |
| 4751 |
taken. |
| 4752 |
|
| 4753 |
|
| 4754 |
|
| 4755 |
|
| 4756 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 85]</span></pre> |
| 4757 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-86" ></span> |
| 4758 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 4759 |
|
| 4760 |
|
| 4761 |
In the case where a Notify message does not contain a Routing Context |
| 4762 |
parameter, the receiver must know, via configuration data, of which |
| 4763 |
Application Servers the ASP is a member and take the appropriate |
| 4764 |
action in each AS. |
| 4765 |
|
| 4766 |
<span class="h6"><a class="selflink" id="section-4.3.4.5.1" href="#section-4.3.4.5.1">4.3.4.5.1</a> IPSP Considerations (NTFY)</span> |
| 4767 |
|
| 4768 |
Notify works in the same manner as in the SG-AS case. One of the |
| 4769 |
IPSPs can send this message to any remote IPSP that is not in the |
| 4770 |
ASP-DOWN state. |
| 4771 |
|
| 4772 |
<span class="h5"><a class="selflink" id="section-4.3.4.6" href="#section-4.3.4.6">4.3.4.6</a> Heartbeat Procedures</span> |
| 4773 |
|
| 4774 |
The optional Heartbeat procedures MAY be used when operating over |
| 4775 |
transport layers that do not have their own heartbeat mechanism for |
| 4776 |
detecting loss of the transport association (i.e., other than SCTP). |
| 4777 |
|
| 4778 |
Either M3UA peer may optionally send Heartbeat messages periodically, |
| 4779 |
subject to a provisionable timer T(beat). Upon receiving a Heartbeat |
| 4780 |
message, the M3UA peer MUST respond with a Heartbeat Ack message. |
| 4781 |
|
| 4782 |
If no Heartbeat Ack message (or any other M3UA message) is received |
| 4783 |
from the M3UA peer within 2*T(beat), the remote M3UA peer is |
| 4784 |
considered unavailable. Transmission of Heartbeat messages is |
| 4785 |
stopped and the signalling process SHOULD attempt to re-establish |
| 4786 |
communication if it is configured as the client for the disconnected |
| 4787 |
M3UA peer. |
| 4788 |
|
| 4789 |
The Heartbeat message may optionally contain an opaque Heartbeat Data |
| 4790 |
parameter that MUST be echoed back unchanged in the related Heartbeat |
| 4791 |
Ack message. The sender, upon examining the contents of the returned |
| 4792 |
Heartbeat Ack message, MAY choose to consider the remote M3UA peer as |
| 4793 |
unavailable. The contents/format of the Heartbeat Data parameter is |
| 4794 |
implementation-dependent and only of local interest to the original |
| 4795 |
sender. The contents may be used, for example, to support a |
| 4796 |
Heartbeat sequence algorithm (to detect missing Heartbeats), and/or a |
| 4797 |
timestamp mechanism (to evaluate delays). |
| 4798 |
|
| 4799 |
Note: Heartbeat related events are not shown in Figure 3 "ASP state |
| 4800 |
transition diagram". |
| 4801 |
|
| 4802 |
|
| 4803 |
|
| 4804 |
|
| 4805 |
|
| 4806 |
|
| 4807 |
|
| 4808 |
|
| 4809 |
|
| 4810 |
|
| 4811 |
|
| 4812 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 86]</span></pre> |
| 4813 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-87" ></span> |
| 4814 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 4815 |
|
| 4816 |
|
| 4817 |
<span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a> Routing Key Management Procedures [Optional]</span> |
| 4818 |
|
| 4819 |
<span class="h4"><a class="selflink" id="section-4.4.1" href="#section-4.4.1">4.4.1</a> Registration</span> |
| 4820 |
|
| 4821 |
An ASP MAY dynamically register with an SGP as an ASP within an |
| 4822 |
Application Server using the REG REQ message. A Routing Key |
| 4823 |
parameter in the REG REQ message specifies the parameters associated |
| 4824 |
with the Routing Key. |
| 4825 |
|
| 4826 |
The SGP examines the contents of the received Routing Key parameter |
| 4827 |
and compares it with the currently provisioned Routing Keys. If the |
| 4828 |
received Routing Key matches an existing SGP Routing Key entry, and |
| 4829 |
the ASP is not currently included in the list of ASPs for the related |
| 4830 |
Application Server, the SGP MAY authorize the ASP to be added to the |
| 4831 |
AS. Or, if the Routing Key does not currently exist and the received |
| 4832 |
Routing Key data is valid and unique, an SGP supporting dynamic |
| 4833 |
configuration MAY authorize the creation of a new Routing Key and |
| 4834 |
related Application Server and add the ASP to the new AS. In either |
| 4835 |
case, the SGP returns a Registration Response message to the ASP, |
| 4836 |
containing the same Local-RK-Identifier as provided in the initial |
| 4837 |
request, and a Registration Result "Successfully Registered". A |
| 4838 |
unique Routing Context value assigned to the SGP Routing Key is |
| 4839 |
included. The method of Routing Context value assignment at the SGP |
| 4840 |
is implementation dependent but must be guaranteed to be unique for |
| 4841 |
each Application Server or Routing Key supported by the SGP. |
| 4842 |
|
| 4843 |
If the SGP does not support the registration procedure, the SGP |
| 4844 |
returns an Error message to the ASP, with an error code of |
| 4845 |
"Unsupported Message Type". |
| 4846 |
|
| 4847 |
If the SGP determines that the received Routing Key data is invalid, |
| 4848 |
or contains invalid parameter values, the SGP returns a Registration |
| 4849 |
Response message to the ASP, containing a Registration Result "Error |
| 4850 |
Invalid Routing Key", "Error - Invalid DPC", "Error - Invalid Network |
| 4851 |
Appearance" as appropriate. |
| 4852 |
|
| 4853 |
If the SGP determines that a unique Routing Key cannot be created, |
| 4854 |
the SGP returns a Registration Response message to the ASP, with a |
| 4855 |
Registration Status of "Error - "Cannot Support Unique Routing" An |
| 4856 |
incoming signalling message received at an SGP should not match |
| 4857 |
against more than one Routing Key. |
| 4858 |
|
| 4859 |
If the SGP does not authorize an otherwise valid registration |
| 4860 |
request, the SGP returns a REG RSP message to the ASP containing the |
| 4861 |
Registration Result "Error - Permission Denied". |
| 4862 |
|
| 4863 |
|
| 4864 |
|
| 4865 |
|
| 4866 |
|
| 4867 |
|
| 4868 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 87]</span></pre> |
| 4869 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-88" ></span> |
| 4870 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 4871 |
|
| 4872 |
|
| 4873 |
If an SGP determines that a received Routing Key does not currently |
| 4874 |
exist and the SGP does not support dynamic configuration, the SGP |
| 4875 |
returns a Registration Response message to the ASP, containing a |
| 4876 |
Registration Result "Error - Routing Key not Currently Provisioned". |
| 4877 |
|
| 4878 |
If an SGP determines that a received Routing Key does not currently |
| 4879 |
exist and the SGP supports dynamic configuration but does not have |
| 4880 |
the capacity to add new Routing Key and Application Server entries, |
| 4881 |
the SGP returns a Registration Response message to the ASP, |
| 4882 |
containing a Registration Result "Error - Insufficient Resources". |
| 4883 |
|
| 4884 |
If an SGP determines that one or more of the Routing Key parameters |
| 4885 |
are not supported for the purpose of creating new Routing Key |
| 4886 |
entries, the SGP returns a Registration Response message to the ASP, |
| 4887 |
containing a Registration Result "Error - Unsupported RK parameter |
| 4888 |
field". This result MAY be used if, for example, the SGP does not |
| 4889 |
support RK Circuit Range Lists in a Routing Key because the SGP does |
| 4890 |
not support ISUP traffic, or does not provide CIC range granularity. |
| 4891 |
|
| 4892 |
A Registration Response "Error - Unsupported Traffic Handling Mode" |
| 4893 |
is returned if the Routing Key in the REG REQ contains an Traffic |
| 4894 |
Handling Mode that is inconsistent with the presently configured mode |
| 4895 |
for the matching Application Server. |
| 4896 |
|
| 4897 |
An ASP MAY register multiple Routing Keys at once by including a |
| 4898 |
number of Routing Key parameters in a single REG REQ message. The |
| 4899 |
SGP MAY respond to each registration request in a single REG RSP |
| 4900 |
message, indicating the success or failure result for each Routing |
| 4901 |
Key in a separate Registration Result parameter. Alternatively the |
| 4902 |
SGP MAY respond with multiple REG RSP messages, each with one or more |
| 4903 |
Registration Result parameters. The ASP uses the Local-RK-Identifier |
| 4904 |
parameter to correlate the requests with the responses. |
| 4905 |
|
| 4906 |
Upon successful registration of an ASP in an AS, the SGP can now send |
| 4907 |
related SS7 Signalling Network Management messaging, if this did not |
| 4908 |
previously start upon the ASP transitioning to state ASP-INACTIVE |
| 4909 |
|
| 4910 |
<span class="h4"><a class="selflink" id="section-4.4.2" href="#section-4.4.2">4.4.2</a> Deregistration</span> |
| 4911 |
|
| 4912 |
An ASP MAY dynamically deregister with an SGP as an ASP within an |
| 4913 |
Application Server using the DEREG REQ message. A Routing Context |
| 4914 |
parameter in the DEREG REQ message specifies which Routing Keys to |
| 4915 |
deregister. An ASP SHOULD move to the ASP-INACTIVE state for an |
| 4916 |
Application Server before attempting to deregister the Routing Key |
| 4917 |
(i.e., deregister after receiving an ASP Inactive Ack). Also, an ASP |
| 4918 |
SHOULD deregister from all Application Servers that it is a member |
| 4919 |
before attempting to move to the ASP-Down state. |
| 4920 |
|
| 4921 |
|
| 4922 |
|
| 4923 |
|
| 4924 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 88]</span></pre> |
| 4925 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-89" ></span> |
| 4926 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 4927 |
|
| 4928 |
|
| 4929 |
The SGP examines the contents of the received Routing Context |
| 4930 |
parameter and validates that the ASP is currently registered in the |
| 4931 |
Application Server(s) related to the included Routing Context(s). If |
| 4932 |
validated, the ASP is deregistered as an ASP in the related |
| 4933 |
Application Server. |
| 4934 |
|
| 4935 |
The deregistration procedure does not necessarily imply the deletion |
| 4936 |
of Routing Key and Application Server configuration data at the SG. |
| 4937 |
Other ASPs may continue to be associated with the Application Server, |
| 4938 |
in which case the Routing Key data SHOULD NOT be deleted. If a |
| 4939 |
Deregistration results in no more ASPs in an Application Server, an |
| 4940 |
SG MAY delete the Routing Key data. |
| 4941 |
|
| 4942 |
The SGP acknowledges the deregistration request by returning a DEREG |
| 4943 |
RSP message to the requesting ASP. The result of the deregistration |
| 4944 |
is found in the Deregistration Result parameter, indicating success |
| 4945 |
or failure with cause. |
| 4946 |
|
| 4947 |
An ASP MAY deregister multiple Routing Contexts at once by including |
| 4948 |
a number of Routing Contexts in a single DEREG REQ message. The SGP |
| 4949 |
MAY respond to each deregistration request in a single DEREG RSP |
| 4950 |
message, indicating the success or failure result for each Routing |
| 4951 |
Context in a separate Deregistration Result parameter. |
| 4952 |
|
| 4953 |
<span class="h4"><a class="selflink" id="section-4.4.3" href="#section-4.4.3">4.4.3</a> IPSP Considerations (REG/DEREG)</span> |
| 4954 |
|
| 4955 |
The Registration/Deregistration procedures work in the IPSP cases in |
| 4956 |
the same way as in AS-SG cases. An IPSP may register an RK in the |
| 4957 |
remote IPSP. An IPSP is responsible for deregistering the RKs that |
| 4958 |
it has registered. |
| 4959 |
|
| 4960 |
<span class="h3"><a class="selflink" id="section-4.5" href="#section-4.5">4.5</a> Procedures to Support the Availability or Congestion Status of SS7</span> |
| 4961 |
<span class="h3"> Destination</span> |
| 4962 |
|
| 4963 |
<span class="h4"><a class="selflink" id="section-4.5.1" href="#section-4.5.1">4.5.1</a> At an SGP</span> |
| 4964 |
|
| 4965 |
On receiving an MTP-PAUSE, MTP-RESUME or MTP-STATUS indication |
| 4966 |
primitive from the nodal interworking function at an SGP, the SGP |
| 4967 |
M3UA layer will send a corresponding SS7 Signalling Network |
| 4968 |
Management (SSNM) DUNA, DAVA, SCON, or DUPU message (see <a href="#section-3.4">Section 3.4</a>) |
| 4969 |
to the M3UA peers at concerned ASPs. The M3UA layer must fill in |
| 4970 |
various fields of the SSNM messages consistently with the information |
| 4971 |
received in the primitives. |
| 4972 |
|
| 4973 |
The SGP M3UA layer determines the set of concerned ASPs to be |
| 4974 |
informed based on the specific SS7 network for which the primitive |
| 4975 |
indication is relevant. In this way, all ASPs configured to |
| 4976 |
|
| 4977 |
|
| 4978 |
|
| 4979 |
|
| 4980 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 89]</span></pre> |
| 4981 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-90" ></span> |
| 4982 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 4983 |
|
| 4984 |
|
| 4985 |
send/receive traffic within a particular network appearance are |
| 4986 |
informed. If the SGP operates within a single SS7 network |
| 4987 |
appearance, then all ASPs are informed. |
| 4988 |
|
| 4989 |
DUNA, DAVA, SCON, and DRST messages may be sent sequentially and |
| 4990 |
processed at the receiver in the order sent. |
| 4991 |
|
| 4992 |
Sequencing is not required for the DUPU or DAUD messages, which MAY |
| 4993 |
be sent unsequenced. |
| 4994 |
|
| 4995 |
<span class="h4"><a class="selflink" id="section-4.5.2" href="#section-4.5.2">4.5.2</a> At an ASP</span> |
| 4996 |
|
| 4997 |
<span class="h5"><a class="selflink" id="section-4.5.2.1" href="#section-4.5.2.1">4.5.2.1</a> Single SG Configurations</span> |
| 4998 |
|
| 4999 |
At an ASP, upon receiving an SS7 Signalling Network Management (SSNM) |
| 5000 |
message from the remote M3UA Peer, the M3UA layer invokes the |
| 5001 |
appropriate primitive indications to the resident M3UA-Users. Local |
| 5002 |
management is informed. |
| 5003 |
|
| 5004 |
In the case where a local event has caused the unavailability or |
| 5005 |
congestion status of SS7 destinations, the M3UA layer at the ASP |
| 5006 |
SHOULD pass up appropriate indications in the primitives to the M3UA |
| 5007 |
User, as though equivalent SSNM messages were received. For example, |
| 5008 |
the loss of an SCTP association to an SGP may cause the |
| 5009 |
unavailability of a set of SS7 destinations. MTP-PAUSE indication |
| 5010 |
primitives to the M3UA User are appropriate. |
| 5011 |
|
| 5012 |
<span class="h5"><a class="selflink" id="section-4.5.2.2" href="#section-4.5.2.2">4.5.2.2</a> Multiple SG Configurations</span> |
| 5013 |
|
| 5014 |
At an ASP, upon receiving a Signalling Network Management message |
| 5015 |
from the remote M3UA Peer, the M3UA layer updates the status of the |
| 5016 |
affected route(s) via the originating SG and determines, whether or |
| 5017 |
not the overall availability or congestion status of the effected |
| 5018 |
destination(s) has changed. If so, the M3UA layer invokes the |
| 5019 |
appropriate primitive indications to the resident M3UA-Users. Local |
| 5020 |
management is informed. |
| 5021 |
|
| 5022 |
Implementation Note: To accomplish this, the M3UA layer at an ASP |
| 5023 |
maintains the status of routes via the SG, much like an MTP3 layer |
| 5024 |
maintains route-set status. |
| 5025 |
|
| 5026 |
<span class="h4"><a class="selflink" id="section-4.5.3" href="#section-4.5.3">4.5.3</a> ASP Auditing</span> |
| 5027 |
|
| 5028 |
An ASP may optionally initiate an audit procedure to enquire of an |
| 5029 |
SGP the availability and, if the national congestion method with |
| 5030 |
multiple congestion levels and message priorities is used, congestion |
| 5031 |
status of an SS7 destination or set of destinations. A Destination |
| 5032 |
|
| 5033 |
|
| 5034 |
|
| 5035 |
|
| 5036 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 90]</span></pre> |
| 5037 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-91" ></span> |
| 5038 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 5039 |
|
| 5040 |
|
| 5041 |
Audit (DAUD) message is sent from the ASP to the SGP requesting the |
| 5042 |
current availability and congestion status of one or more SS7 |
| 5043 |
Destination Point Codes. |
| 5044 |
|
| 5045 |
The DAUD message MAY be sent unsequenced. The DAUD MAY be sent by the |
| 5046 |
ASP in the following cases: |
| 5047 |
|
| 5048 |
- Periodic. A Timer originally set upon reception of a DUNA, SCON |
| 5049 |
or DRST message has expired without a subsequent |
| 5050 |
DAVA, DUNA, SCON or DRST message updating the |
| 5051 |
availability/congestion status of the affected |
| 5052 |
Destination Point Codes. The Timer is reset upon |
| 5053 |
issuing a DAUD. In this case the DAUD is sent to the |
| 5054 |
SGP that originally sent the SSNM message. |
| 5055 |
|
| 5056 |
- Isolation. The ASP is newly ASP-ACTIVE or has been |
| 5057 |
isolated from an SGP for an extended period. The ASP |
| 5058 |
MAY request the availability/congestion status of one |
| 5059 |
or more SS7 destinations to which it expects to |
| 5060 |
communicate. |
| 5061 |
|
| 5062 |
IMPLEMENTATION NOTE: In the first of the cases above, the auditing |
| 5063 |
procedure must not be invoked for the case of a received SCON message |
| 5064 |
containing a congestion level value of "no congestion" or undefined" |
| 5065 |
(i.e., congestion Level = "0"). This is because the value indicates |
| 5066 |
either congestion abatement or that the ITU MTP3 international |
| 5067 |
congestion method is being used. In the international congestion |
| 5068 |
method, the MTP3 layer at the SGP does not maintain the congestion |
| 5069 |
status of any destinations and therefore the SGP cannot provide any |
| 5070 |
congestion information in response to the DAUD. For the same reason, |
| 5071 |
in the second of the cases above a DAUD message cannot reveal any |
| 5072 |
congested destination(s). |
| 5073 |
|
| 5074 |
The SGP SHOULD respond to a DAUD message with the MTP3 |
| 5075 |
availability/congested status of the routeset associated with each |
| 5076 |
Destination Point Code(s) in the DAUD message. The status of each |
| 5077 |
SS7 destination requested is indicated in a DUNA message (if |
| 5078 |
unavailable), a DAVA message (if available), or a DRST (if restricted |
| 5079 |
and the SGP supports this feature). Where the SGP maintains the |
| 5080 |
congestion status of the SS7 destination, and the SS7 destination is |
| 5081 |
congested, the SGP MUST additionally respond with an SCON message |
| 5082 |
before the DAVA or DRST message. If the SS7 destination is available |
| 5083 |
and congested, the SGP MUST respond with an SCON message and then a |
| 5084 |
DAVA message. If the SS7 destination is restricted and congested, |
| 5085 |
the SGP MUST respond with an SCON message immediately followed by a |
| 5086 |
DRST message. If the SGP has no information on the availability |
| 5087 |
|
| 5088 |
|
| 5089 |
|
| 5090 |
|
| 5091 |
|
| 5092 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 91]</span></pre> |
| 5093 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-92" ></span> |
| 5094 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 5095 |
|
| 5096 |
|
| 5097 |
status of the SS7 destination, the SGP responds with a DUNA message, |
| 5098 |
as it has no routing information to allow it to route traffic to this |
| 5099 |
destination. |
| 5100 |
|
| 5101 |
Any DUNA or DAVA message in response to a DAUD message MAY contain a |
| 5102 |
list of Affected Point Codes. |
| 5103 |
|
| 5104 |
An SG MAY refuse to provide the availability or congestion status of |
| 5105 |
a destination if, for example, the ASP is not authorized to know the |
| 5106 |
status of the destination. The SG MAY respond with an Error Message |
| 5107 |
(Error Code = "Destination Status Unknown") |
| 5108 |
|
| 5109 |
<span class="h3"><a class="selflink" id="section-4.6" href="#section-4.6">4.6</a> MTP3 Restart</span> |
| 5110 |
|
| 5111 |
In the case where the MTP3 in the SG undergoes an MTP restart, event |
| 5112 |
communication SHOULD be handled as follows: |
| 5113 |
|
| 5114 |
When the SG discovers SS7 network isolation, the SGPs send an |
| 5115 |
indication to all concerned available ASPs (i.e., ASPs in the ASP- |
| 5116 |
ACTIVE state) using DUNA messages for the concerned destinations. |
| 5117 |
|
| 5118 |
When the SG has completed the MTP Restart procedure, the M3UA layers |
| 5119 |
at the SGPs inform all concerned ASPs in the ASP-ACTIVE state of any |
| 5120 |
available/restricted SS7 destinations using the DAVA/DRST messages. |
| 5121 |
No message is necessary for those destinations still unavailable |
| 5122 |
after the restart procedure. |
| 5123 |
|
| 5124 |
When the M3UA layer at an ASP receives a DUNA message indicating SS7 |
| 5125 |
destination unavailability at an SG, MTP Users will receive an MTP- |
| 5126 |
PAUSE indication and will stop any affected traffic to this |
| 5127 |
destination. When the M3UA receives a DAVA/DRST message, MTP Users |
| 5128 |
will receive an MTP-RESUME indication and can resume traffic to the |
| 5129 |
newly available SS7 destination, provided the ASP is in the ASP- |
| 5130 |
ACTIVE state towards this SGP. |
| 5131 |
|
| 5132 |
The ASP MAY choose to audit the availability of unavailable |
| 5133 |
destinations by sending DAUD messages. This would be for example the |
| 5134 |
case when an AS becomes active at an ASP and does not have current |
| 5135 |
destination statuses. If MTP restart is in progress at the SG, the |
| 5136 |
SGP returns a DUNA message for that destination, even if it received |
| 5137 |
an indication that the destination became available or restricted. |
| 5138 |
|
| 5139 |
In the IPSP case, MTP restart could be considered if the IPSP also |
| 5140 |
has connection to an SS7 network. In that case, the same behavior as |
| 5141 |
described above for the SGP would apply to the restarting IPSP. This |
| 5142 |
would also be the case if the IPSPs were perceived as exchanging MTP |
| 5143 |
Peer PDUs, instead of MTP primitives between MTP User and MTP |
| 5144 |
Provider. In other words, M3UA does not provide the equivalent to |
| 5145 |
|
| 5146 |
|
| 5147 |
|
| 5148 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 92]</span></pre> |
| 5149 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-93" ></span> |
| 5150 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 5151 |
|
| 5152 |
|
| 5153 |
Traffic Restart Allowed messages indicating the end of the restart |
| 5154 |
procedure between peer IPSPs that would also be connected to an SS7 |
| 5155 |
network. |
| 5156 |
|
| 5157 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Examples of M3UA Procedures</span> |
| 5158 |
|
| 5159 |
NOTE: Not all the Notify messages that are appropriate per the Notify |
| 5160 |
procedures are shown in these examples. |
| 5161 |
|
| 5162 |
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a> Establishment of Association and Traffic between SGPs and ASPs</span> |
| 5163 |
|
| 5164 |
These scenarios show the example M3UA message flows for the |
| 5165 |
establishment of traffic between an SGP and an ASP or between two |
| 5166 |
IPSPs. In all cases it is assumed that the SCTP association is |
| 5167 |
already set up. |
| 5168 |
|
| 5169 |
<span class="h4"><a class="selflink" id="section-5.1.1" href="#section-5.1.1">5.1.1</a> Single ASP in an Application Server ("1+0" sparing),</span> |
| 5170 |
|
| 5171 |
These scenarios show the example M3UA message flows for the |
| 5172 |
establishment of traffic between an SGP and an ASP where only one ASP |
| 5173 |
is configured within an AS (no backup). |
| 5174 |
|
| 5175 |
<span class="h5"><a class="selflink" id="section-5.1.1.1" href="#section-5.1.1.1">5.1.1.1</a> Single ASP in an Application Server ("1+0" sparing),</span> |
| 5176 |
<span class="h5"> No Registration</span> |
| 5177 |
|
| 5178 |
SGP ASP1 |
| 5179 |
| | |
| 5180 |
|<-------------ASP Up-----------| |
| 5181 |
|-----------ASP Up Ack--------->| |
| 5182 |
| | |
| 5183 |
|<------- ASP Active(RCn)-------| RC: Routing Context |
| 5184 |
|-----ASP Active Ack (RCn)----->| (optional) |
| 5185 |
| | |
| 5186 |
|-----NTFY(AS-ACTIVE)(RCn)----->| |
| 5187 |
| | |
| 5188 |
|
| 5189 |
Note: If the ASP Active message contains an optional Routing Context |
| 5190 |
parameter, the ASP Active message only applies for the specified RC |
| 5191 |
value(s). For an unknown RC value, the SGP responds with an Error |
| 5192 |
message. |
| 5193 |
|
| 5194 |
|
| 5195 |
|
| 5196 |
|
| 5197 |
|
| 5198 |
|
| 5199 |
|
| 5200 |
|
| 5201 |
|
| 5202 |
|
| 5203 |
|
| 5204 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 93]</span></pre> |
| 5205 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-94" ></span> |
| 5206 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 5207 |
|
| 5208 |
|
| 5209 |
<span class="h5"><a class="selflink" id="section-5.1.1.2" href="#section-5.1.1.2">5.1.1.2</a> Single ASP in Application Server ("1+0" sparing),</span> |
| 5210 |
<span class="h5"> Dynamic Registration</span> |
| 5211 |
|
| 5212 |
This scenario is the same as for 5.1.1.1 but with the optional |
| 5213 |
exchange of registration information. In this case the Registration |
| 5214 |
is accepted by the SGP. |
| 5215 |
|
| 5216 |
SGP ASP1 |
| 5217 |
| | |
| 5218 |
|<------------ASP Up------------| |
| 5219 |
|----------ASP Up Ack---------->| |
| 5220 |
| | |
| 5221 |
|<----REGISTER REQ(LRCn,RKn)----| LRC: Local Routing |
| 5222 |
| | Context |
| 5223 |
|----REGISTER RESP(LRCn,RCn)--->| RK: Routing Key |
| 5224 |
| | RC: Routing Context |
| 5225 |
| | |
| 5226 |
|<------- ASP Active(RCn)-------| |
| 5227 |
|-----ASP Active Ack (RCn)----->| |
| 5228 |
| | |
| 5229 |
|-----NTFY(AS-ACTIVE)(RCn)----->| |
| 5230 |
| | |
| 5231 |
|
| 5232 |
Note: In the case of an unsuccessful registration attempt (e.g., |
| 5233 |
invalid RKn), the Register Response message will contain an |
| 5234 |
unsuccessful indication and the ASP will not subsequently send an ASP |
| 5235 |
Active message. |
| 5236 |
|
| 5237 |
|
| 5238 |
|
| 5239 |
|
| 5240 |
|
| 5241 |
|
| 5242 |
|
| 5243 |
|
| 5244 |
|
| 5245 |
|
| 5246 |
|
| 5247 |
|
| 5248 |
|
| 5249 |
|
| 5250 |
|
| 5251 |
|
| 5252 |
|
| 5253 |
|
| 5254 |
|
| 5255 |
|
| 5256 |
|
| 5257 |
|
| 5258 |
|
| 5259 |
|
| 5260 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 94]</span></pre> |
| 5261 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-95" ></span> |
| 5262 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 5263 |
|
| 5264 |
|
| 5265 |
<span class="h5"><a class="selflink" id="section-5.1.1.3" href="#section-5.1.1.3">5.1.1.3</a> Single ASP in Multiple Application Servers (each</span> |
| 5266 |
<span class="h5"> with "1+0" sparing), Dynamic Registration (Case 1 - Multiple</span> |
| 5267 |
Registration Requests) |
| 5268 |
|
| 5269 |
SGP ASP1 |
| 5270 |
| | |
| 5271 |
|<------------ASP Up------------| |
| 5272 |
|----------ASP Up Ack---------->| |
| 5273 |
| | |
| 5274 |
|<----REGISTER REQ(LRC1,RK1)----| LRC: Local Routing |
| 5275 |
| | Context |
| 5276 |
|----REGISTER RESP(LRC1,RC1)--->| RK: Routing Key |
| 5277 |
| | RC: Routing Context |
| 5278 |
| | |
| 5279 |
|<------- ASP Active(RC1)-------| |
| 5280 |
|-----ASP Active Ack (RC1)----->| |
| 5281 |
| | |
| 5282 |
| | |
| 5283 |
|<----REGISTER REQ(LRCn,RKn)----| |
| 5284 |
| | |
| 5285 |
|----REGISTER RESP(LRCn,RCn)--->| |
| 5286 |
| | |
| 5287 |
| | |
| 5288 |
|<------- ASP Active(RCn)-------| |
| 5289 |
|-----ASP Active Ack (RCn)----->| |
| 5290 |
| | |
| 5291 |
|
| 5292 |
Note: In the case of an unsuccessful registration attempt (e.g., |
| 5293 |
invalid RKn), the Register Response message will contain an |
| 5294 |
unsuccessful indication and the ASP will not subsequently send an ASP |
| 5295 |
Active message. Each LRC/RK pair registration is considered |
| 5296 |
independently. |
| 5297 |
|
| 5298 |
It is not necessary to follow a Registration Request/Response message |
| 5299 |
pair with an ASP Active message before sending the next Registration |
| 5300 |
Request. The ASP Active message can be sent at any time after the |
| 5301 |
related successful registration. |
| 5302 |
|
| 5303 |
|
| 5304 |
|
| 5305 |
|
| 5306 |
|
| 5307 |
|
| 5308 |
|
| 5309 |
|
| 5310 |
|
| 5311 |
|
| 5312 |
|
| 5313 |
|
| 5314 |
|
| 5315 |
|
| 5316 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 95]</span></pre> |
| 5317 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-96" ></span> |
| 5318 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 5319 |
|
| 5320 |
|
| 5321 |
<span class="h5"><a class="selflink" id="section-5.1.1.4" href="#section-5.1.1.4">5.1.1.4</a> Single ASP in Multiple Application Servers (each</span> |
| 5322 |
<span class="h5"> with "1+0" sparing), Dynamic Registration (Case 2 - Single</span> |
| 5323 |
Registration Request) |
| 5324 |
|
| 5325 |
SGP ASP1 |
| 5326 |
| | |
| 5327 |
|<------------ASP Up------------| |
| 5328 |
|----------ASP Up Ack---------->| |
| 5329 |
| | |
| 5330 |
|<---REGISTER REQ({LRC1,RK1},---| |
| 5331 |
| ..., | |
| 5332 |
| {LRCn,RKn}),--| |
| 5333 |
| | |
| 5334 |
|---REGISTER RESP({LRC1,RC1},-->| |
| 5335 |
| ..., | |
| 5336 |
| (LRCn,RCn}) | |
| 5337 |
| | |
| 5338 |
|<------- ASP Active(RC1)-------| |
| 5339 |
|-----ASP Active Ack (RC1)----->| |
| 5340 |
| | |
| 5341 |
: : |
| 5342 |
: : |
| 5343 |
| | |
| 5344 |
|<------- ASP Active(RCn)-------| |
| 5345 |
|-----ASP Active Ack (RCn)----->| |
| 5346 |
| | |
| 5347 |
|
| 5348 |
Note: In the case of an unsuccessful registration attempt (e.g., |
| 5349 |
Invalid RKn), the Register Response message will contain an |
| 5350 |
unsuccessful indication and the ASP will not subsequently send an ASP |
| 5351 |
Active message. Each LRC/RK pair registration is considered |
| 5352 |
independently. |
| 5353 |
|
| 5354 |
The ASP Active message can be sent at any time after the related |
| 5355 |
successful registration, and may have more than one RC. |
| 5356 |
|
| 5357 |
<span class="h4"><a class="selflink" id="section-5.1.2" href="#section-5.1.2">5.1.2</a> Two ASPs in Application Server ("1+1" sparing)</span> |
| 5358 |
|
| 5359 |
This scenario shows the example M3UA message flows for the |
| 5360 |
establishment of traffic between an SGP and two ASPs in the same |
| 5361 |
Application Server, where ASP1 is configured to be in the ASP-ACTIVE |
| 5362 |
state and ASP2 is to be a "backup" in the event of communication |
| 5363 |
failure or the withdrawal from service of ASP1. ASP2 may act as a |
| 5364 |
hot, warm, or cold backup depending on the extent to which ASP1 and |
| 5365 |
ASP2 share call/transaction state or can communicate call state under |
| 5366 |
failure/withdrawal events. The example message flow is the same |
| 5367 |
|
| 5368 |
|
| 5369 |
|
| 5370 |
|
| 5371 |
|
| 5372 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 96]</span></pre> |
| 5373 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-97" ></span> |
| 5374 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 5375 |
|
| 5376 |
|
| 5377 |
whether the ASP Active messages indicate "Override", "Loadshare" or |
| 5378 |
"Broadcast" mode, although typically this example would use an |
| 5379 |
Override mode. |
| 5380 |
|
| 5381 |
SGP ASP1 ASP2 |
| 5382 |
| | | |
| 5383 |
|<--------ASP Up---------| | |
| 5384 |
|-------ASP Up Ack------>| | |
| 5385 |
| | | |
| 5386 |
|<----------------------------ASP Up----------------| |
| 5387 |
|----------------------------ASP Up Ack------------>| |
| 5388 |
| | | |
| 5389 |
| | | |
| 5390 |
|<-------ASP Active------| | |
| 5391 |
|------ASP Active Ack--->| | |
| 5392 |
| | | |
| 5393 |
|
| 5394 |
<span class="h4"><a class="selflink" id="section-5.1.3" href="#section-5.1.3">5.1.3</a> Two ASPs in an Application Server ("1+1" sparing,</span> |
| 5395 |
<span class="h4"> loadsharing case)</span> |
| 5396 |
|
| 5397 |
This scenario shows a similar case to <a href="#section-5.1.2">Section 5.1.2</a> but where the two |
| 5398 |
ASPs are brought to the state ASP-ACTIVE and subsequently loadshare |
| 5399 |
the traffic. In this case, one ASP is sufficient to handle the total |
| 5400 |
traffic load. |
| 5401 |
|
| 5402 |
SGP ASP1 ASP2 |
| 5403 |
| | | |
| 5404 |
|<---------ASP Up--------| | |
| 5405 |
|--------ASP Up Ack----->| | |
| 5406 |
| | | |
| 5407 |
|<-----------------------------ASP Up---------------| |
| 5408 |
|----------------------------ASP Up Ack------------>| |
| 5409 |
| | | |
| 5410 |
| | | |
| 5411 |
|<--ASP Active (Ldshr)---| | |
| 5412 |
|-----ASP-Active Ack---->| | |
| 5413 |
| | | |
| 5414 |
|---NOTIFY (AS-ACTIVE)-->| | |
| 5415 |
|---------------------------NOTIFY (AS-ACTIVE------>| |
| 5416 |
| | | |
| 5417 |
|<---------------------------ASP Active (Ldshr)-----| |
| 5418 |
|------------------------------ASP Active Ack------>| |
| 5419 |
| | | |
| 5420 |
|
| 5421 |
|
| 5422 |
|
| 5423 |
|
| 5424 |
|
| 5425 |
|
| 5426 |
|
| 5427 |
|
| 5428 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 97]</span></pre> |
| 5429 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-98" ></span> |
| 5430 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 5431 |
|
| 5432 |
|
| 5433 |
<span class="h4"><a class="selflink" id="section-5.1.4" href="#section-5.1.4">5.1.4</a> Three ASPs in an Application Server ("n+k" sparing,</span> |
| 5434 |
<span class="h4"> loadsharing case)</span> |
| 5435 |
|
| 5436 |
This scenario shows the example M3UA message flows for the |
| 5437 |
establishment of traffic between an SGP and three ASPs in the same |
| 5438 |
Application Server, where two of the ASPs are brought to the state |
| 5439 |
ASP-ACTIVE and subsequently share the load. In this case, a minimum |
| 5440 |
of two ASPs are required to handle the total traffic load (2+1 |
| 5441 |
sparing). |
| 5442 |
|
| 5443 |
SGP ASP1 ASP2 ASP3 |
| 5444 |
| | | | |
| 5445 |
|<------ASP Up------| | | |
| 5446 |
|-----ASP Up Ack--->| | | |
| 5447 |
| | | | |
| 5448 |
|<-------------------------ASP Up-------| | |
| 5449 |
|------------------------ASP Up Ack---->| | |
| 5450 |
| | | | |
| 5451 |
|<--------------------------------------------ASP Up--------| |
| 5452 |
|--------------------------------------------ASP Up Ack---->| |
| 5453 |
| | | | |
| 5454 |
| | | | |
| 5455 |
|<--ASP Act (Ldshr)-| | | |
| 5456 |
|----ASP Act Ack--->| | | |
| 5457 |
| | | | |
| 5458 |
| | | | |
| 5459 |
|<-------------------ASP Act. (Ldshr)---| | |
| 5460 |
|----------------------ASP Act Ack----->| | |
| 5461 |
| | | | |
| 5462 |
|---------Notify (AS-ACTIVE)----------->| | |
| 5463 |
|----------------------Notify (AS-ACTIVE)------------------>| |
| 5464 |
|
| 5465 |
|
| 5466 |
|
| 5467 |
|
| 5468 |
|
| 5469 |
|
| 5470 |
|
| 5471 |
|
| 5472 |
|
| 5473 |
|
| 5474 |
|
| 5475 |
|
| 5476 |
|
| 5477 |
|
| 5478 |
|
| 5479 |
|
| 5480 |
|
| 5481 |
|
| 5482 |
|
| 5483 |
|
| 5484 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 98]</span></pre> |
| 5485 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-99" ></span> |
| 5486 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 5487 |
|
| 5488 |
|
| 5489 |
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a> ASP Traffic Failover Examples</span> |
| 5490 |
|
| 5491 |
<span class="h4"><a class="selflink" id="section-5.2.1" href="#section-5.2.1">5.2.1</a> (1+1 Sparing, Withdrawal of ASP, Backup Override)</span> |
| 5492 |
|
| 5493 |
Following on from the example in <a href="#section-5.1.2">Section 5.1.2</a>, and ASP1 withdraws |
| 5494 |
from service: |
| 5495 |
|
| 5496 |
SGP ASP1 ASP2 |
| 5497 |
| | | |
| 5498 |
|<-----ASP Inactive------| | |
| 5499 |
|----ASP Inactive Ack--->| | |
| 5500 |
| | | |
| 5501 |
|----NTFY(AS-PENDING)--->| | |
| 5502 |
|-----------------------NTFY(AS-PENDING)----------->| |
| 5503 |
| | | |
| 5504 |
|<----------------------------- ASP Active----------| |
| 5505 |
|-----------------------------ASP Active Ack------->| |
| 5506 |
| | | |
| 5507 |
|----NTFY(AS-ACTIVE)---->| | |
| 5508 |
|-----------------------NTFY(AS-ACTIVE)------------>| |
| 5509 |
|
| 5510 |
Note: If the SGP M3UA layer detects the loss of the M3UA peer (e.g., |
| 5511 |
M3UA heartbeat loss or detection of SCTP failure), the initial ASP |
| 5512 |
Inactive message exchange (i.e., SGP to ASP1) would not occur. |
| 5513 |
|
| 5514 |
<span class="h4"><a class="selflink" id="section-5.2.2" href="#section-5.2.2">5.2.2</a> (1+1 Sparing, Backup Override)</span> |
| 5515 |
|
| 5516 |
Following on from the example in <a href="#section-5.1.2">Section 5.1.2</a>, ASP2 wishes to |
| 5517 |
Override ASP1 and take over the traffic: |
| 5518 |
|
| 5519 |
SGP ASP1 ASP2 |
| 5520 |
| | | |
| 5521 |
|<----------------------------- ASP Active----------| |
| 5522 |
|------------------------------ASP Active Ack------>| |
| 5523 |
|----NTFY(Alt ASP-Act)-->| |
| 5524 |
| | | |
| 5525 |
|
| 5526 |
|
| 5527 |
|
| 5528 |
|
| 5529 |
|
| 5530 |
|
| 5531 |
|
| 5532 |
|
| 5533 |
|
| 5534 |
|
| 5535 |
|
| 5536 |
|
| 5537 |
|
| 5538 |
|
| 5539 |
|
| 5540 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 99]</span></pre> |
| 5541 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-100" ></span> |
| 5542 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 5543 |
|
| 5544 |
|
| 5545 |
<span class="h4"><a class="selflink" id="section-5.2.3" href="#section-5.2.3">5.2.3</a> (n+k Sparing, Loadsharing case, Withdrawal of ASP)</span> |
| 5546 |
|
| 5547 |
Following on from the example in <a href="#section-5.1.4">Section 5.1.4</a>, and ASP1 withdraws |
| 5548 |
from service: |
| 5549 |
|
| 5550 |
SGP ASP1 ASP2 ASP3 |
| 5551 |
| | | | |
| 5552 |
|<----ASP Inact.----| | | |
| 5553 |
|---ASP Inact Ack-->| | | |
| 5554 |
| | | | |
| 5555 |
|--------------------------------NTFY(Ins. ASPs)----------->| |
| 5556 |
| | | | |
| 5557 |
|<----------------------------------------ASP Act (Ldshr)---| |
| 5558 |
|------------------------------------------ASP Act (Ack)--->| |
| 5559 |
| | | | |
| 5560 |
|
| 5561 |
For the Notify message to be sent, the SG maintains knowledge of the |
| 5562 |
minimum ASP resources required (e.g., if the SG knows that "n+k" = |
| 5563 |
"2+1" for a Loadshare AS and "n" currently equals "1"). |
| 5564 |
|
| 5565 |
Note: If the SGP detects loss of the ASP1 M3UA peer (e.g., M3UA |
| 5566 |
heartbeat loss or detection of SCTP failure), the initial ASP |
| 5567 |
Inactive message exchange (i.e., SGP-ASP1) would not occur. |
| 5568 |
|
| 5569 |
<span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a> Normal Withdrawal of an ASP from an Application Server</span> |
| 5570 |
<span class="h3"> and Teardown of an Association</span> |
| 5571 |
|
| 5572 |
An ASP which is now confirmed in the state ASP-INACTIVE (i.e., the |
| 5573 |
ASP has received an ASP Inactive Ack message) may now proceed to the |
| 5574 |
ASP-DOWN state, if it is to be removed from service. Following on |
| 5575 |
from <a href="#section-5.2.1">Section 5.2.1</a> or 5.2.3, where ASP1 has moved to the "Inactive" |
| 5576 |
state: |
| 5577 |
|
| 5578 |
|
| 5579 |
|
| 5580 |
|
| 5581 |
|
| 5582 |
|
| 5583 |
|
| 5584 |
|
| 5585 |
|
| 5586 |
|
| 5587 |
|
| 5588 |
|
| 5589 |
|
| 5590 |
|
| 5591 |
|
| 5592 |
|
| 5593 |
|
| 5594 |
|
| 5595 |
|
| 5596 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 100]</span></pre> |
| 5597 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-101" ></span> |
| 5598 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 5599 |
|
| 5600 |
|
| 5601 |
SGP ASP1 |
| 5602 |
| | |
| 5603 |
|<-----ASP Inactive (RCn)------| RC: Routing Context |
| 5604 |
|----ASP Inactive Ack (RCn)--->| |
| 5605 |
| | |
| 5606 |
|<-----DEREGISTER REQ(RCn)-----| See Notes |
| 5607 |
| | |
| 5608 |
|---DEREGISTER RESP(LRCn,RCn)->| |
| 5609 |
| | |
| 5610 |
: : |
| 5611 |
| | |
| 5612 |
|<-----------ASP Down----------| |
| 5613 |
|---------ASP Down Ack-------->| |
| 5614 |
| | |
| 5615 |
|
| 5616 |
Note: The Deregistration procedure will typically be used if the ASP |
| 5617 |
previously used the Registration procedures for configuration within |
| 5618 |
the Application Server. ASP Inactive and Deregister messages |
| 5619 |
exchanges may contain multiple Routing Contexts. |
| 5620 |
|
| 5621 |
The ASP should be in the ASP-INACTIVE state and should have |
| 5622 |
deregistered in all its Routing Contexts before attempting to move to |
| 5623 |
the ASP-DOWN state. |
| 5624 |
|
| 5625 |
<span class="h3"><a class="selflink" id="section-5.4" href="#section-5.4">5.4</a> M3UA/MTP3-User Boundary Examples</span> |
| 5626 |
|
| 5627 |
<span class="h4"><a class="selflink" id="section-5.4.1" href="#section-5.4.1">5.4.1</a> At an ASP</span> |
| 5628 |
|
| 5629 |
This section describes the primitive mapping between the MTP3 User |
| 5630 |
and the M3UA layer at an ASP. |
| 5631 |
|
| 5632 |
<span class="h5"><a class="selflink" id="section-5.4.1.1" href="#section-5.4.1.1">5.4.1.1</a> Support for MTP-TRANSFER Primitives at the ASP</span> |
| 5633 |
|
| 5634 |
<span class="h6"><a class="selflink" id="section-5.4.1.1.1" href="#section-5.4.1.1.1">5.4.1.1.1</a> Support for MTP-TRANSFER Request Primitive</span> |
| 5635 |
|
| 5636 |
When the MTP3-User on the ASP has data to send to a remote MTP3-User, |
| 5637 |
it uses the MTP-TRANSFER request primitive. The M3UA layer at the |
| 5638 |
ASP will do the following when it receives an MTP-TRANSFER request |
| 5639 |
primitive from the M3UA user: |
| 5640 |
|
| 5641 |
- Determine the correct SGP; |
| 5642 |
|
| 5643 |
- Determine the correct association to the chosen SGP; |
| 5644 |
|
| 5645 |
- Determine the correct stream in the association (e.g., |
| 5646 |
based on SLS); |
| 5647 |
|
| 5648 |
|
| 5649 |
|
| 5650 |
|
| 5651 |
|
| 5652 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 101]</span></pre> |
| 5653 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-102" ></span> |
| 5654 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 5655 |
|
| 5656 |
|
| 5657 |
- Determine whether to complete the optional fields of the DATA |
| 5658 |
message; |
| 5659 |
|
| 5660 |
- Map the MTP-TRANSFER request primitive into the Protocol Data |
| 5661 |
field of a DATA message; |
| 5662 |
|
| 5663 |
- Send the DATA message to the remote M3UA peer at the SGP, |
| 5664 |
over the SCTP association. |
| 5665 |
|
| 5666 |
SGP ASP |
| 5667 |
| | |
| 5668 |
|<-----DATA Message-------|<--MTP-TRANSFER req. |
| 5669 |
| | |
| 5670 |
|
| 5671 |
<span class="h6"><a class="selflink" id="section-5.4.1.1.2" href="#section-5.4.1.1.2">5.4.1.1.2</a> Support for the MTP-TRANSFER Indication Primitive</span> |
| 5672 |
|
| 5673 |
When the M3UA layer on the ASP receives a DATA message from the M3UA |
| 5674 |
peer at the remote SGP, it will do the following: |
| 5675 |
|
| 5676 |
- Evaluate the optional fields of the DATA message, if present; |
| 5677 |
|
| 5678 |
- Map the Protocol Data field of a DATA message into the |
| 5679 |
MTP-TRANSFER indication primitive; |
| 5680 |
|
| 5681 |
- Pass the MTP-TRANSFER indication primitive to the user part. In |
| 5682 |
case of multiple user parts, the optional fields of the Data |
| 5683 |
message are used to determine the concerned user part. |
| 5684 |
|
| 5685 |
SGP ASP |
| 5686 |
| | |
| 5687 |
|------Data Message------>|-->MTP-Transfer ind. |
| 5688 |
| | |
| 5689 |
|
| 5690 |
<span class="h6"><a class="selflink" id="section-5.4.1.1.3" href="#section-5.4.1.1.3">5.4.1.1.3</a> Support for ASP Querying of SS7 Destination States</span> |
| 5691 |
|
| 5692 |
There are situations such as temporary loss of connectivity to the |
| 5693 |
SGP that may cause the M3UA layer at the ASP to audit SS7 destination |
| 5694 |
availability/congestion states. Note: there is no primitive for the |
| 5695 |
MTP3-User to request this audit from the M3UA layer as this is |
| 5696 |
initiated by an internal M3UA management function. |
| 5697 |
|
| 5698 |
|
| 5699 |
|
| 5700 |
|
| 5701 |
|
| 5702 |
|
| 5703 |
|
| 5704 |
|
| 5705 |
|
| 5706 |
|
| 5707 |
|
| 5708 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 102]</span></pre> |
| 5709 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-103" ></span> |
| 5710 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 5711 |
|
| 5712 |
|
| 5713 |
SGP ASP |
| 5714 |
| | |
| 5715 |
|<----------DAUD-----------| |
| 5716 |
|<----------DAUD-----------| |
| 5717 |
|<----------DAUD-----------| |
| 5718 |
| | |
| 5719 |
| | |
| 5720 |
|
| 5721 |
<span class="h4"><a class="selflink" id="section-5.4.2" href="#section-5.4.2">5.4.2</a> At an SGP</span> |
| 5722 |
|
| 5723 |
This section describes the primitive mapping between the MTP3-User |
| 5724 |
and the M3UA layer at an SGP. |
| 5725 |
|
| 5726 |
<span class="h5"><a class="selflink" id="section-5.4.2.1" href="#section-5.4.2.1">5.4.2.1</a> Support for MTP-TRANSFER Request Primitive at the SGP</span> |
| 5727 |
|
| 5728 |
When the M3UA layer at the SGP has received DATA messages from its |
| 5729 |
peer destined to the SS7 network it will do the following: |
| 5730 |
|
| 5731 |
- Evaluate the optional fields of the DATA message, if present, to |
| 5732 |
determine the Network Appearance; |
| 5733 |
|
| 5734 |
- Map the Protocol data field of the DATA message into an |
| 5735 |
MTP-TRANSFER request primitive; |
| 5736 |
|
| 5737 |
- Pass the MTP-TRANSFER request primitive to the MTP3 of the |
| 5738 |
concerned Network Appearance. |
| 5739 |
|
| 5740 |
SGP ASP |
| 5741 |
| | |
| 5742 |
<---MTP-TRANSFER req.|<---------DATA -----------| |
| 5743 |
| | |
| 5744 |
|
| 5745 |
<span class="h5"><a class="selflink" id="section-5.4.2.2" href="#section-5.4.2.2">5.4.2.2</a> Support for MTP-TRANSFER Indication Primitive at the SGP</span> |
| 5746 |
|
| 5747 |
When the MTP3 layer at the SGP has data to pass its user parts, it |
| 5748 |
will use the MTP-TRANSFER indication primitive. The M3UA layer at |
| 5749 |
the SGP will do the following when it receives an MTP-TRANSFER |
| 5750 |
indication primitive: |
| 5751 |
|
| 5752 |
- Determine the correct AS using the distribution function; |
| 5753 |
|
| 5754 |
- Select an ASP in the ASP-ACTIVE state |
| 5755 |
|
| 5756 |
- Determine the correct association to the chosen ASP; |
| 5757 |
|
| 5758 |
- Determine the correct stream in the SCTP association (e.g., |
| 5759 |
based on SLS); |
| 5760 |
|
| 5761 |
|
| 5762 |
|
| 5763 |
|
| 5764 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 103]</span></pre> |
| 5765 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-104" ></span> |
| 5766 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 5767 |
|
| 5768 |
|
| 5769 |
- Determine whether to complete the optional fields of the DATA |
| 5770 |
message; |
| 5771 |
|
| 5772 |
- Map the MTP-TRANSFER indication primitive into the Protocol Data |
| 5773 |
field of a DATA message; |
| 5774 |
|
| 5775 |
- Send the DATA message to the remote M3UA peer in the ASP, over |
| 5776 |
the SCTP association |
| 5777 |
|
| 5778 |
SGP ASP |
| 5779 |
| | |
| 5780 |
--MTP-TRANSFER ind.->|-----------DATA --------->| |
| 5781 |
| | |
| 5782 |
|
| 5783 |
<span class="h5"><a class="selflink" id="section-5.4.2.3" href="#section-5.4.2.3">5.4.2.3</a> Support for MTP-PAUSE, MTP-RESUME, MTP-STATUS Indication</span> |
| 5784 |
<span class="h5"> Primitives</span> |
| 5785 |
|
| 5786 |
The MTP-PAUSE, MTP-RESUME and MTP-STATUS indication primitives from |
| 5787 |
the MTP3 upper layer interface at the SGP need to be made available |
| 5788 |
to the remote MTP3 User Part lower layer interface at the concerned |
| 5789 |
ASP(s). |
| 5790 |
|
| 5791 |
<span class="h6"><a class="selflink" id="section-5.4.2.3.1" href="#section-5.4.2.3.1">5.4.2.3.1</a> Destination Unavailable</span> |
| 5792 |
|
| 5793 |
The MTP3 layer at the SGP will generate an MTP-PAUSE indication |
| 5794 |
primitive when it determines locally that an SS7 destination is |
| 5795 |
unreachable. The M3UA layer will map this primitive to a DUNA |
| 5796 |
message. The SGP M3UA layer determines the set of concerned ASPs to |
| 5797 |
be informed based on internal SS7 network information associated with |
| 5798 |
the MTP-PAUSE indication primitive indication. |
| 5799 |
|
| 5800 |
SGP ASP |
| 5801 |
| | |
| 5802 |
--MTP-PAUSE ind.-->|---------DUNA----------->|--MTP-PAUSE ind.--> |
| 5803 |
| | |
| 5804 |
|
| 5805 |
<span class="h6"><a class="selflink" id="section-5.4.2.3.2" href="#section-5.4.2.3.2">5.4.2.3.2</a> Destination Available</span> |
| 5806 |
|
| 5807 |
The MTP3 at the SGP will generate an MTP-RESUME indication primitive |
| 5808 |
when it determines locally that an SS7 destination that was |
| 5809 |
previously unreachable is now reachable. The M3UA layer will map |
| 5810 |
this primitive to a DAVA message. The SGP M3UA determines the set of |
| 5811 |
concerned ASPs to be informed based on internal SS7 network |
| 5812 |
information associated with the MTP-RESUME indication primitive. |
| 5813 |
|
| 5814 |
|
| 5815 |
|
| 5816 |
|
| 5817 |
|
| 5818 |
|
| 5819 |
|
| 5820 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 104]</span></pre> |
| 5821 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-105" ></span> |
| 5822 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 5823 |
|
| 5824 |
|
| 5825 |
SGP ASP |
| 5826 |
| | |
| 5827 |
--MTP-RESUME ind.-->|-----------DAVA--------->|--MTP-RESUME ind.--> |
| 5828 |
| | |
| 5829 |
|
| 5830 |
<span class="h6"><a class="selflink" id="section-5.4.2.3.3" href="#section-5.4.2.3.3">5.4.2.3.3</a> SS7 Network Congestion</span> |
| 5831 |
|
| 5832 |
The MTP3 layer at the SGP will generate an MTP-STATUS indication |
| 5833 |
primitive when it determines locally that the route to an SS7 |
| 5834 |
destination is congested. The M3UA layer will map this primitive to |
| 5835 |
a SCON message. It will determine which ASP(s) to send the SCON |
| 5836 |
message to, based on the intended Application Server. |
| 5837 |
|
| 5838 |
SGP ASP |
| 5839 |
| | |
| 5840 |
--MTP-STATUS ind.-->|-----------SCON--------->|--MTP-STATUS ind.--> |
| 5841 |
| | |
| 5842 |
|
| 5843 |
<span class="h6"><a class="selflink" id="section-5.4.2.3.4" href="#section-5.4.2.3.4">5.4.2.3.4</a> Destination User Part Unavailable</span> |
| 5844 |
|
| 5845 |
The MTP3 layer at the SGP will generate an MTP-STATUS indication |
| 5846 |
primitive when it receives an UPU message from the SS7 network. The |
| 5847 |
M3UA layer will map this primitive to a DUPU message. It will |
| 5848 |
determine which ASP(s) to send the DUPU based on the intended |
| 5849 |
Application Server. |
| 5850 |
|
| 5851 |
SGP ASP |
| 5852 |
| | |
| 5853 |
--MTP-STATUS ind.-->|----------DUPU---------->|--MTP-STATUS ind.--> |
| 5854 |
| | |
| 5855 |
|
| 5856 |
<span class="h3"><a class="selflink" id="section-5.5" href="#section-5.5">5.5</a> Examples for IPSP communication.</span> |
| 5857 |
|
| 5858 |
These scenarios show a basic example for IPSP communication for the |
| 5859 |
three phases of the connection (establishment, data exchange, |
| 5860 |
disconnection). It is assumed that the SCTP association is already |
| 5861 |
set up. Both single exchange and double exchange behavior are |
| 5862 |
included for illustrative purposes. |
| 5863 |
|
| 5864 |
|
| 5865 |
|
| 5866 |
|
| 5867 |
|
| 5868 |
|
| 5869 |
|
| 5870 |
|
| 5871 |
|
| 5872 |
|
| 5873 |
|
| 5874 |
|
| 5875 |
|
| 5876 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 105]</span></pre> |
| 5877 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-106" ></span> |
| 5878 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 5879 |
|
| 5880 |
|
| 5881 |
<span class="h4"><a class="selflink" id="section-5.5.1" href="#section-5.5.1">5.5.1</a> Single exchange:</span> |
| 5882 |
|
| 5883 |
IPSP-A IPSP-B |
| 5884 |
| | |
| 5885 |
|-------------ASP Up------------>| |
| 5886 |
|<----------ASP Up Ack-----------| |
| 5887 |
| | |
| 5888 |
|<------- ASP Active(RCb)--------| RC: Routing Context |
| 5889 |
|-----ASP Active Ack (RCb)------>| (optional) |
| 5890 |
| | |
| 5891 |
| | |
| 5892 |
|<========= DATA (RCb) ========>| |
| 5893 |
| | |
| 5894 |
|<-----ASP Inactive (RCb)--------| RC: Routing Context |
| 5895 |
|----ASP Inactive Ack (RCb)----->| (optional) |
| 5896 |
| | |
| 5897 |
|<-----------ASP Down------------| |
| 5898 |
|---------ASP Down Ack---------->| |
| 5899 |
| | |
| 5900 |
|
| 5901 |
Routing Context are previously agreed to be the same in both |
| 5902 |
directions. |
| 5903 |
|
| 5904 |
|
| 5905 |
|
| 5906 |
|
| 5907 |
|
| 5908 |
|
| 5909 |
|
| 5910 |
|
| 5911 |
|
| 5912 |
|
| 5913 |
|
| 5914 |
|
| 5915 |
|
| 5916 |
|
| 5917 |
|
| 5918 |
|
| 5919 |
|
| 5920 |
|
| 5921 |
|
| 5922 |
|
| 5923 |
|
| 5924 |
|
| 5925 |
|
| 5926 |
|
| 5927 |
|
| 5928 |
|
| 5929 |
|
| 5930 |
|
| 5931 |
|
| 5932 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 106]</span></pre> |
| 5933 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-107" ></span> |
| 5934 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 5935 |
|
| 5936 |
|
| 5937 |
<span class="h4"><a class="selflink" id="section-5.5.2" href="#section-5.5.2">5.5.2</a> Double exchange:</span> |
| 5938 |
|
| 5939 |
IPSP-A IPSP-B |
| 5940 |
| | |
| 5941 |
|<-------------ASP Up------------| |
| 5942 |
|-----------ASP Up Ack---------->| |
| 5943 |
| | |
| 5944 |
|-------------ASP Up------------>| (optional) |
| 5945 |
|<----------ASP Up Ack-----------| (optional) |
| 5946 |
| | |
| 5947 |
|<------- ASP Active(RCb)--------| RC: Routing Context |
| 5948 |
|-----ASP Active Ack (RCb)------>| (optional) |
| 5949 |
| | |
| 5950 |
|------- ASP Active(RCa)-------->| RC: Routing Context |
| 5951 |
|<-----ASP Active Ack (RCa)------| (optional) |
| 5952 |
| | |
| 5953 |
|<========= DATA (RCa) =========| |
| 5954 |
|========== DATA (RCb) ========>| |
| 5955 |
| | |
| 5956 |
|<-----ASP Inactive (RCb)--------| RC: Routing Context |
| 5957 |
|----ASP Inactive Ack (RCb)----->| |
| 5958 |
| | |
| 5959 |
|------ASP Inactive (RCa)------->| RC: Routing Context |
| 5960 |
|<----ASP Inactive Ack (RCa)-----| |
| 5961 |
| | |
| 5962 |
|<-----------ASP Down------------| |
| 5963 |
|---------ASP Down Ack---------->| |
| 5964 |
| | |
| 5965 |
|------------ASP Down----------->| (optional) |
| 5966 |
|<--------ASP Down Ack-----------| (optional) |
| 5967 |
| | |
| 5968 |
|
| 5969 |
In this approach, only one single exchange of ASP Up message can be |
| 5970 |
considered as enough since the response by the other peer can be |
| 5971 |
considered as a notice that it is in ASP_UP state. |
| 5972 |
|
| 5973 |
For the same reason, only one ASP Down message is needed since once |
| 5974 |
that an IPSP receives ASP_Down ack message it is itself considered as |
| 5975 |
being in the ASP_Down state and not allowed to receive ASPSM |
| 5976 |
messages. |
| 5977 |
|
| 5978 |
|
| 5979 |
|
| 5980 |
|
| 5981 |
|
| 5982 |
|
| 5983 |
|
| 5984 |
|
| 5985 |
|
| 5986 |
|
| 5987 |
|
| 5988 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 107]</span></pre> |
| 5989 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-108" ></span> |
| 5990 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 5991 |
|
| 5992 |
|
| 5993 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span> |
| 5994 |
|
| 5995 |
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a> Introduction</span> |
| 5996 |
|
| 5997 |
M3UA is designed to carry signalling messages for telephony services. |
| 5998 |
As such, M3UA must involve the security needs of several parties: the |
| 5999 |
end users of the services; the network providers and the applications |
| 6000 |
involved. Additional requirements may come from local regulation. |
| 6001 |
While having some overlapping security needs, any security solution |
| 6002 |
should fulfill all of the different parties' needs. |
| 6003 |
|
| 6004 |
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a> Threats</span> |
| 6005 |
|
| 6006 |
There is no quick fix, one-size-fits-all solution for security. As a |
| 6007 |
transport protocol, M3UA has the following security objectives: |
| 6008 |
|
| 6009 |
* Availability of reliable and timely user data transport. |
| 6010 |
* Integrity of user data transport. |
| 6011 |
* Confidentiality of user data. |
| 6012 |
|
| 6013 |
M3UA is recommended to be transported on SCTP. SCTP [<a href="#ref-17" title=""Stream Control Transport Protocol"">17</a>] provides |
| 6014 |
certain transport related security features, such as some protection |
| 6015 |
against: |
| 6016 |
|
| 6017 |
* Blind Denial of Service Attacks |
| 6018 |
* Flooding |
| 6019 |
* Masquerade |
| 6020 |
* Improper Monopolization of Services |
| 6021 |
|
| 6022 |
When M3UA is running in professionally managed corporate or service |
| 6023 |
provider network, it is reasonable to expect that this network |
| 6024 |
includes an appropriate security policy framework. The "Site |
| 6025 |
Security Handbook" [<a href="#ref-22" title=""Site Security Handbook"">22</a>] should be consulted for guidance. |
| 6026 |
|
| 6027 |
When the network in which M3UA runs in involves more than one party, |
| 6028 |
it may not be reasonable to expect that all parties have implemented |
| 6029 |
security in a sufficient manner. In such a case, it is recommended |
| 6030 |
that IPSEC is used to ensure confidentiality of user payload. |
| 6031 |
Consult [<a href="#ref-23" title=""Security Architecture for the Internet Protocol"">23</a>] for more information on configuring IPSEC services. |
| 6032 |
|
| 6033 |
<span class="h3"><a class="selflink" id="section-6.3" href="#section-6.3">6.3</a> Protecting Confidentiality</span> |
| 6034 |
|
| 6035 |
Particularly for mobile users, the requirement for confidentiality |
| 6036 |
may include the masking of IP addresses and ports. In this case |
| 6037 |
application level encryption is not sufficient; IPSEC ESP [<a href="#ref-24" title=""IP Encapsulating Security Payload (ESP)"">24</a>] SHOULD |
| 6038 |
be used instead. Regardless of which level performs the encryption, |
| 6039 |
the IPSEC ISAKMP [<a href="#ref-25" title=""Internet Security Association and Key Management Protocol"">25</a>] service SHOULD be used for key management. |
| 6040 |
|
| 6041 |
|
| 6042 |
|
| 6043 |
|
| 6044 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 108]</span></pre> |
| 6045 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-109" ></span> |
| 6046 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 6047 |
|
| 6048 |
|
| 6049 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. IANA Considerations</span> |
| 6050 |
|
| 6051 |
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a> SCTP Payload Protocol Identifier</span> |
| 6052 |
|
| 6053 |
IANA has assigned an M3UA value for the Payload Protocol Identifier |
| 6054 |
in the SCTP DATA chunk. The following SCTP Payload Protocol |
| 6055 |
Identifier is registered: |
| 6056 |
|
| 6057 |
M3UA "3" |
| 6058 |
|
| 6059 |
The SCTP Payload Protocol Identifier value "3" SHOULD be included in |
| 6060 |
each SCTP DATA chunk, to indicate that the SCTP is carrying the M3UA |
| 6061 |
protocol. The value "0" (unspecified) is also allowed but any other |
| 6062 |
values MUST not be used. This Payload Protocol Identifier is not |
| 6063 |
directly used by SCTP but MAY be used by certain network entities to |
| 6064 |
identify the type of information being carried in a DATA chunk. |
| 6065 |
|
| 6066 |
The User Adaptation peer MAY use the Payload Protocol Identifier as a |
| 6067 |
way of determining additional information about the data being |
| 6068 |
presented to it by SCTP. |
| 6069 |
|
| 6070 |
<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a> M3UA Port Number</span> |
| 6071 |
|
| 6072 |
IANA has registered SCTP (and UDP/TCP) Port Number 2905 for M3UA. It |
| 6073 |
is recommended that SGPs use this SCTP port number for listening for |
| 6074 |
new connections. SGPs MAY also use statically configured SCTP port |
| 6075 |
numbers instead. |
| 6076 |
|
| 6077 |
<span class="h3"><a class="selflink" id="section-7.3" href="#section-7.3">7.3</a> M3UA Protocol Extensions</span> |
| 6078 |
|
| 6079 |
This protocol may also be extended through IANA in three ways: |
| 6080 |
|
| 6081 |
-- through definition of additional message classes, |
| 6082 |
-- through definition of additional message types, and |
| 6083 |
-- through definition of additional message parameters |
| 6084 |
|
| 6085 |
The definition and use of new message classes, types and parameters |
| 6086 |
is an integral part of SIGTRAN adaptation layers. Thus these |
| 6087 |
extensions are assigned by IANA through an IETF Consensus action as |
| 6088 |
defined in Guidelines for Writing an IANA Considerations Section in |
| 6089 |
RFCs (25] |
| 6090 |
|
| 6091 |
The proposed extension must in no way adversely affect the general |
| 6092 |
working of the protocol. |
| 6093 |
|
| 6094 |
|
| 6095 |
|
| 6096 |
|
| 6097 |
|
| 6098 |
|
| 6099 |
|
| 6100 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 109]</span></pre> |
| 6101 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-110" ></span> |
| 6102 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 6103 |
|
| 6104 |
|
| 6105 |
<span class="h4"><a class="selflink" id="section-7.3.1" href="#section-7.3.1">7.3.1</a> IETF Defined Message Classes</span> |
| 6106 |
|
| 6107 |
The documentation for a new message class MUST include the following |
| 6108 |
information: |
| 6109 |
|
| 6110 |
(a) A long and short name for the new message class; |
| 6111 |
(b) A detailed description of the purpose of the message class. |
| 6112 |
|
| 6113 |
<span class="h4"><a class="selflink" id="section-7.3.2" href="#section-7.3.2">7.3.2</a> IETF Defined Message Types</span> |
| 6114 |
|
| 6115 |
The documentation for a new message type MUST include the following |
| 6116 |
information: |
| 6117 |
|
| 6118 |
(a) A long and short name for the new message type; |
| 6119 |
(b) A detailed description of the structure of the message;. |
| 6120 |
(c) A detailed definition and description of intended use for each |
| 6121 |
field within the message; |
| 6122 |
(d) A detailed procedural description of the use of the new |
| 6123 |
message type within the operation of the protocol; |
| 6124 |
(e) A detailed description of error conditions when receiving this |
| 6125 |
message type. |
| 6126 |
|
| 6127 |
When an implementation receives a message type which it does not |
| 6128 |
support, it MUST respond with an Error (ERR) message ("Unsupported |
| 6129 |
Message Type"). |
| 6130 |
|
| 6131 |
<span class="h4"><a class="selflink" id="section-7.3.3" href="#section-7.3.3">7.3.3</a> IETF Defined Parameter Extension</span> |
| 6132 |
|
| 6133 |
Documentation of the message parameter MUST contain the following |
| 6134 |
information: |
| 6135 |
|
| 6136 |
(a) Name of the parameter type; |
| 6137 |
(b) Detailed description of the structure of the parameter field. |
| 6138 |
This structure MUST conform to the general type-length-value |
| 6139 |
format described in <a href="#section-3.2">Section 3.2</a>; |
| 6140 |
(c) Detailed definition of each component of the parameter value; |
| 6141 |
(d) Detailed description of the intended use of this parameter |
| 6142 |
type, and an indication of whether and under what |
| 6143 |
circumstances multiple instances of this parameter type may be |
| 6144 |
found within the same message. |
| 6145 |
|
| 6146 |
|
| 6147 |
|
| 6148 |
|
| 6149 |
|
| 6150 |
|
| 6151 |
|
| 6152 |
|
| 6153 |
|
| 6154 |
|
| 6155 |
|
| 6156 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 110]</span></pre> |
| 6157 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-111" ></span> |
| 6158 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 6159 |
|
| 6160 |
|
| 6161 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. References</span> |
| 6162 |
|
| 6163 |
<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a> Normative References</span> |
| 6164 |
|
| 6165 |
[<a id="ref-1">1</a>] ITU-T Recommendations Q.761 to Q.767, "Signalling System No.7 |
| 6166 |
(SS7) - ISDN User Part (ISUP)" |
| 6167 |
|
| 6168 |
[<a id="ref-2">2</a>] ANSI T1.113 - "Signaling System Number 7 - ISDN User Part" |
| 6169 |
|
| 6170 |
[<a id="ref-3">3</a>] ETSI ETS 300 356-1 "Integrated Services Digital Network (ISDN); |
| 6171 |
Signalling System No.7; ISDN User Part (ISUP) version 2 for the |
| 6172 |
international interface; Part 1: Basic services" |
| 6173 |
|
| 6174 |
[<a id="ref-4">4</a>] ITU-T Recommendations Q.711 to Q.715, "Signalling System No. 7 |
| 6175 |
(SS7) - Signalling Connection Control Part (SCCP)" |
| 6176 |
|
| 6177 |
[<a id="ref-5">5</a>] ANSI T1.112 "Signaling System Number 7 - Signaling Connection |
| 6178 |
Control Part" |
| 6179 |
|
| 6180 |
[<a id="ref-6">6</a>] ETSI ETS 300 009-1, "Integrated Services Digital Network (ISDN); |
| 6181 |
Signalling System No.7; Signalling Connection Control Part |
| 6182 |
(SCCP) (connectionless and connection-oriented class 2) to |
| 6183 |
support international interconnection; Part 1: Protocol |
| 6184 |
specification" |
| 6185 |
|
| 6186 |
[<a id="ref-7">7</a>] ITU-T Recommendations Q.701 to Q.705, "Signalling System No. 7 |
| 6187 |
(SS7) - Message Transfer Part (MTP)" |
| 6188 |
|
| 6189 |
[<a id="ref-8">8</a>] ANSI T1.111 "Signaling System Number 7 - Message Transfer Part" |
| 6190 |
|
| 6191 |
[<a id="ref-9">9</a>] ETSI ETS 300 008-1, "Integrated Services Digital Network (ISDN); |
| 6192 |
Signalling System No.7; Message Transfer Part (MTP) to support |
| 6193 |
international interconnection; Part 1: Protocol specification" |
| 6194 |
|
| 6195 |
[<a id="ref-10">10</a>] Yergeau, F., "UTF-8, a transformation format of ISO 10646", <a href="./rfc2279">RFC</a> |
| 6196 |
<a href="./rfc2279">2279</a>, January 1998. |
| 6197 |
|
| 6198 |
<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a> Informative References</span> |
| 6199 |
|
| 6200 |
[<a id="ref-11">11</a>] Ong, L., Rytina, M., Garcia, H., Schwarzbauer, L., Coene, H., |
| 6201 |
Lin, I., Juhasz, M. and C. Holdrege, "Framework Architecture for |
| 6202 |
Signaling Transport", <a href="./rfc2719">RFC 2719</a>, October 1999. |
| 6203 |
|
| 6204 |
[<a id="ref-12">12</a>] ITU-T Recommendation Q.720, "Telephone User Part" |
| 6205 |
|
| 6206 |
|
| 6207 |
|
| 6208 |
|
| 6209 |
|
| 6210 |
|
| 6211 |
|
| 6212 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 111]</span></pre> |
| 6213 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-112" ></span> |
| 6214 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 6215 |
|
| 6216 |
|
| 6217 |
[<a id="ref-13">13</a>] ITU-T Recommendations Q.771 to Q.775 "Signalling System No. 7 |
| 6218 |
(SS7) - Transaction Capabilities (TCAP)" |
| 6219 |
|
| 6220 |
[<a id="ref-14">14</a>] ANSI T1.114 "Signaling System Number 7 - Transaction |
| 6221 |
Capabilities Application Part" |
| 6222 |
|
| 6223 |
[<a id="ref-15">15</a>] ETSI ETS 300 287-1, "Integrated Services Digital Network (ISDN); |
| 6224 |
Signalling System No.7; Transaction Capabilities (TC) version 2; |
| 6225 |
Part 1: Protocol specification" |
| 6226 |
|
| 6227 |
[<a id="ref-16">16</a>] 3G TS 25.410 V4.0.0 (2001-04) "Technical Specification - 3rd |
| 6228 |
Generation partnership Project; Technical Specification Group |
| 6229 |
Radio Access Network; UTRAN Iu Interface: General Aspects and |
| 6230 |
Principles" |
| 6231 |
|
| 6232 |
[<a id="ref-17">17</a>] Stewart, R., Xie, Q., Mornmeault, K., Sharp, H., Taylor, T., |
| 6233 |
Rytina, I., Kalla, M., Zhang, L. and V. Paxson, "Stream Control |
| 6234 |
Transport Protocol", <a href="./rfc2960">RFC 2960</a>, October 2000. |
| 6235 |
|
| 6236 |
[<a id="ref-18">18</a>] ITU-T Recommendation Q.2140 "B-ISDN ATM Adaptation Layer - |
| 6237 |
Service Specific Coordination Function for signalling at the |
| 6238 |
Network Node Interface (SSCF at NNI)" |
| 6239 |
|
| 6240 |
[<a id="ref-19">19</a>] ITU-T Recommendation Q.2110 "B-ISDN ATM Adaptation Layer - |
| 6241 |
Service Specific Connection Oriented Protocol (SSCOP)" |
| 6242 |
|
| 6243 |
[<a id="ref-20">20</a>] Bradner, S., "Key words for use in RFCs to Indicate Requirement |
| 6244 |
Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997. |
| 6245 |
|
| 6246 |
[<a id="ref-21">21</a>] ITU-T Recommendation Q.2210 "Message Transfer Part Level 3 |
| 6247 |
functions and messages using the services of ITU Recommendation |
| 6248 |
Q.2140" |
| 6249 |
|
| 6250 |
[<a id="ref-22">22</a>] Fraser, B., "Site Security Handbook", FYI 8, <a href="./rfc2196">RFC 2196</a>, September |
| 6251 |
1997. |
| 6252 |
|
| 6253 |
[<a id="ref-23">23</a>] Ramakrishnan, S., Floyd, S. and D. Black, "Security Architecture |
| 6254 |
for the Internet Protocol", <a href="./rfc3168">RFC 3168</a>, November 1998. |
| 6255 |
|
| 6256 |
[<a id="ref-24">24</a>] Kent, S. and R. Atkinson, "IP Encapsulating Security Payload |
| 6257 |
(ESP)", <a href="./rfc2406">RFC 2406</a>, November 1998. |
| 6258 |
|
| 6259 |
[<a id="ref-25">25</a>] Maughan, D., Schertler, M., Schneider, M. and J. Turner, |
| 6260 |
"Internet Security Association and Key Management Protocol", <a href="./rfc2408">RFC</a> |
| 6261 |
<a href="./rfc2408">2408</a>, November 1998. |
| 6262 |
|
| 6263 |
[<a id="ref-26">26</a>] Narten, T. and H. Alverstrand, "Guidelines for Writing an IANA |
| 6264 |
Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc2434">RFC 2434</a>, October 1998. |
| 6265 |
|
| 6266 |
|
| 6267 |
|
| 6268 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 112]</span></pre> |
| 6269 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-113" ></span> |
| 6270 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 6271 |
|
| 6272 |
|
| 6273 |
[<a id="ref-27">27</a>] Morneault, K., Dantu, R., Sidebottom, G., Bidulock, B. and J. |
| 6274 |
Heitz, "Signaling System 7 (SS7) Message Transfer Part 2 (MTP2) |
| 6275 |
- User Adaptation Layer", <a href="./rfc3331">RFC 3331</a>, August 2002. |
| 6276 |
|
| 6277 |
[<a id="ref-28">28</a>] George, T., et. al., "SS7 MTP2-User Peer-to-Peer Adaptation |
| 6278 |
Layer", Work in Progress. |
| 6279 |
|
| 6280 |
[<a id="ref-29">29</a>] Telecommunication Technology Committee (TTC) Standard JT-Q704, |
| 6281 |
"Message Transfer Part Signaling Network Functions", April 28, |
| 6282 |
1992. |
| 6283 |
|
| 6284 |
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Acknowledgements</span> |
| 6285 |
|
| 6286 |
The authors would like to thank Antonio Roque Alvarez, Joyce |
| 6287 |
Archibald, Tolga Asveren, Maria-Cruz Bartolome-Rodrigo, Dan Brendes, |
| 6288 |
Antonio Caete, Nikhil Jain, Roland Jesske, Joe Keller, Kurt Kite, |
| 6289 |
Ming Lin, Steve Lorusso, Naoto Makinae, Howard May, Francois |
| 6290 |
Mouillaud, Barry Nagelberg, Neil Olson, Heinz Prantner, Shyamal |
| 6291 |
Prasad, Mukesh Punhani, Selvam Rengasami, John Schantz, Ray Singh, |
| 6292 |
Michael Tuexen, Nitin Tomar, Gery Verwimp, Tim Vetter, Kazuo |
| 6293 |
Watanabe, Ben Wilson and many others for their valuable comments and |
| 6294 |
suggestions. |
| 6295 |
|
| 6296 |
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Document Contributors</span> |
| 6297 |
|
| 6298 |
Ian Rytina - Ericsson |
| 6299 |
Guy Mousseau - Nortel Networks |
| 6300 |
Lyndon Ong - Ciena |
| 6301 |
Hanns Juergen Schwarzbauer - Siemens |
| 6302 |
Klaus Gradischnig - Detecon Inc. |
| 6303 |
Mallesh Kalla - Telcordia |
| 6304 |
Normand Glaude - Performance Technologies |
| 6305 |
Brian Bidulock - OpenSS7 |
| 6306 |
John Loughney - Nokia |
| 6307 |
|
| 6308 |
|
| 6309 |
|
| 6310 |
|
| 6311 |
|
| 6312 |
|
| 6313 |
|
| 6314 |
|
| 6315 |
|
| 6316 |
|
| 6317 |
|
| 6318 |
|
| 6319 |
|
| 6320 |
|
| 6321 |
|
| 6322 |
|
| 6323 |
|
| 6324 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 113]</span></pre> |
| 6325 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-114" ></span> |
| 6326 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 6327 |
|
| 6328 |
|
| 6329 |
Appendix A |
| 6330 |
|
| 6331 |
<span class="h3"><a class="selflink" id="appendix-A.1" href="#appendix-A.1">A.1</a> Signalling Network Architecture</span> |
| 6332 |
|
| 6333 |
A Signalling Gateway is used to support the transport of MTP3-User |
| 6334 |
signalling traffic received from the SS7 network to multiple |
| 6335 |
distributed ASPs (e.g., MGCs and IP Databases). Clearly, the M3UA |
| 6336 |
protocol is not designed to meet the performance and reliability |
| 6337 |
requirements for such transport by itself. However, the conjunction |
| 6338 |
of distributed architecture and redundant networks provides support |
| 6339 |
for reliable transport of signalling traffic over IP. The M3UA |
| 6340 |
protocol is flexible enough to allow its operation and management in |
| 6341 |
a variety of physical configurations, enabling Network Operators to |
| 6342 |
meet their performance and reliability requirements. |
| 6343 |
|
| 6344 |
To meet the stringent SS7 signalling reliability and performance |
| 6345 |
requirements for carrier grade networks, Network Operators might |
| 6346 |
require that no single point of failure is present in the end-to-end |
| 6347 |
network architecture between an SS7 node and an IP-based application. |
| 6348 |
This can typically be achieved through the use of redundant SGPs or |
| 6349 |
SGs, redundant hosts, and the provision of redundant QOS-bounded IP |
| 6350 |
network paths for SCTP Associations between SCTP End Points. |
| 6351 |
Obviously, the reliability of the SG, the MGC and other IP-based |
| 6352 |
functional elements also needs to be taken into account. The |
| 6353 |
distribution of ASPs and SGPs within the available Hosts MAY also be |
| 6354 |
considered. As an example, for a particular Application Server, the |
| 6355 |
related ASPs could be distributed over at least two Hosts. |
| 6356 |
|
| 6357 |
|
| 6358 |
|
| 6359 |
|
| 6360 |
|
| 6361 |
|
| 6362 |
|
| 6363 |
|
| 6364 |
|
| 6365 |
|
| 6366 |
|
| 6367 |
|
| 6368 |
|
| 6369 |
|
| 6370 |
|
| 6371 |
|
| 6372 |
|
| 6373 |
|
| 6374 |
|
| 6375 |
|
| 6376 |
|
| 6377 |
|
| 6378 |
|
| 6379 |
|
| 6380 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 114]</span></pre> |
| 6381 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-115" ></span> |
| 6382 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 6383 |
|
| 6384 |
|
| 6385 |
One example of a physical network architecture relevant to SS7 |
| 6386 |
carrier grade operation in the IP network domain is shown in Figure 5 |
| 6387 |
below: |
| 6388 |
|
| 6389 |
SGs MGCs |
| 6390 |
|
| 6391 |
Host#1 ************** ************** Host#3 |
| 6392 |
* ********__*__________________________*__******** * = |
| 6393 |
* *SGP1.1*__*_____ _______________*__* ASP1 * * MGC1 |
| 6394 |
* ******** * \ / * ******** * |
| 6395 |
* ********__*______\__/________________*__******** * |
| 6396 |
* *SGP2.1*__*_______\/______ _____*__* ASP2 * * |
| 6397 |
* ******** * /\ | | * ******** * |
| 6398 |
* : * / \ | | * : * |
| 6399 |
* ******** * / \ | | * ******** * |
| 6400 |
* * SGPn * * | | | | * * ASPn * * |
| 6401 |
* ******** * | | | | * ******** * |
| 6402 |
************** | | | | ************** |
| 6403 |
| | \ / |
| 6404 |
Host#2 ************** | | \ / ************** Host#4 |
| 6405 |
* ********__*_____| |______\/_______*__******** * = |
| 6406 |
* *SGP1.2*__*_________________/\_______*__* ASP1 * * MGC2 |
| 6407 |
* ******** * / \ * ******** * |
| 6408 |
* ********__*_______________/ \_____*__******** * |
| 6409 |
* *SGP2.2*__*__________________________*__* ASP2 * * |
| 6410 |
* ******** * * ******** * |
| 6411 |
* : * SCTP Associations * : * |
| 6412 |
* ******** * * ******** * |
| 6413 |
* * SGPn * * * * ASPn * * |
| 6414 |
* ******** * * ******** * |
| 6415 |
************** ************** |
| 6416 |
|
| 6417 |
SGP1.1 and SGP1.2 are part of SG1 |
| 6418 |
SGP2.1 and SGP2.2 are part of SG2 |
| 6419 |
|
| 6420 |
Figure 5 - Physical Model |
| 6421 |
|
| 6422 |
In this model, each host may have many application processes. In the |
| 6423 |
case of the MGC, an ASP may provide service to one or more |
| 6424 |
Application Servers, and is identified as an SCTP end point. One or |
| 6425 |
more Signalling Gateway Processes make up a single Signalling |
| 6426 |
Gateway. |
| 6427 |
|
| 6428 |
This example model can also be applied to IPSP-IPSP signalling. In |
| 6429 |
this case, each IPSP may have its services distributed across 2 hosts |
| 6430 |
or more, and may have multiple server processes on each host. |
| 6431 |
|
| 6432 |
|
| 6433 |
|
| 6434 |
|
| 6435 |
|
| 6436 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 115]</span></pre> |
| 6437 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-116" ></span> |
| 6438 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 6439 |
|
| 6440 |
|
| 6441 |
In the example above, each signalling process (SGP, ASP or IPSP) is |
| 6442 |
the end point to more than one SCTP association, leading to more than |
| 6443 |
one other signalling processes. To support this, a signalling |
| 6444 |
process must be able to support distribution of M3UA messages to many |
| 6445 |
simultaneous active associations. This message distribution function |
| 6446 |
is based on the status of provisioned Routing Keys, the status of the |
| 6447 |
signalling routes to signalling points in the SS7 network, and the |
| 6448 |
redundancy model (active-standby, load sharing, broadcast, n+k) of |
| 6449 |
the remote signalling processes. |
| 6450 |
|
| 6451 |
For carrier grade networks, the failure or isolation of a particular |
| 6452 |
signalling process should not cause stable calls or transactions to |
| 6453 |
be lost. This implies that signalling processes need, in some cases, |
| 6454 |
to share the call/transaction state or be able to pass the call state |
| 6455 |
information between each other. In the case of ASPs performing call |
| 6456 |
processing, coordination may also be required with the related Media |
| 6457 |
Gateway to transfer the MGC control for a particular trunk |
| 6458 |
termination. However, this sharing or communication of |
| 6459 |
call/transaction state information is outside the scope of this |
| 6460 |
document. |
| 6461 |
|
| 6462 |
This model serves as an example. M3UA imposes no restrictions as to |
| 6463 |
the exact layout of the network elements, the message distribution |
| 6464 |
algorithms and the distribution of the signalling processes. |
| 6465 |
Instead, it provides a framework and a set of messages that allow for |
| 6466 |
a flexible and scalable signalling network architecture, aiming to |
| 6467 |
provide reliability and performance. |
| 6468 |
|
| 6469 |
|
| 6470 |
|
| 6471 |
|
| 6472 |
|
| 6473 |
|
| 6474 |
|
| 6475 |
|
| 6476 |
|
| 6477 |
|
| 6478 |
|
| 6479 |
|
| 6480 |
|
| 6481 |
|
| 6482 |
|
| 6483 |
|
| 6484 |
|
| 6485 |
|
| 6486 |
|
| 6487 |
|
| 6488 |
|
| 6489 |
|
| 6490 |
|
| 6491 |
|
| 6492 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 116]</span></pre> |
| 6493 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-117" ></span> |
| 6494 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 6495 |
|
| 6496 |
|
| 6497 |
<span class="h3"><a class="selflink" id="appendix-A.2" href="#appendix-A.2">A.2</a> Redundancy Models</span> |
| 6498 |
|
| 6499 |
<span class="h4"><a class="selflink" id="appendix-A.2.1" href="#appendix-A.2.1">A.2.1</a> Application Server Redundancy</span> |
| 6500 |
|
| 6501 |
At the SGP, an Application Server list contains active and inactive |
| 6502 |
ASPs to support ASP broadcast, loadsharing and failover procedures. |
| 6503 |
The list of ASPs within a logical Application Server is kept updated |
| 6504 |
in the SGP to reflect the active Application Server Process(es). |
| 6505 |
|
| 6506 |
For example, in the network shown in Figure 1, all messages to DPC x |
| 6507 |
could be sent to ASP1 in Host3 or ASP1 in Host4. The AS list at SGP1 |
| 6508 |
in Host 1 might look like the following: |
| 6509 |
|
| 6510 |
Routing Key {DPC=x) - "Application Server #1" |
| 6511 |
ASP1/Host3 - State = Active |
| 6512 |
ASP1/Host4 - State = Inactive |
| 6513 |
|
| 6514 |
In this "1+1" redundancy case, ASP1 in Host3 would be sent any |
| 6515 |
incoming message with DPC=x. ASP1 in Host4 would normally be brought |
| 6516 |
to the "active" state upon failure of, or loss of connectivity to, |
| 6517 |
ASP1/Host1. |
| 6518 |
|
| 6519 |
The AS List at SGP1 in Host1 might also be set up in loadshare mode: |
| 6520 |
|
| 6521 |
Routing Key {DPC=x) - "Application Server #1" |
| 6522 |
ASP1/Host3 - State = Active |
| 6523 |
ASP1/Host4 - State = Active |
| 6524 |
|
| 6525 |
In this case, both the ASPs would be sent a portion of the traffic. |
| 6526 |
For example the two ASPs could together form a database, where |
| 6527 |
incoming queries may be sent to any active ASP. |
| 6528 |
|
| 6529 |
Care might need to be exercised by a Network Operator in the |
| 6530 |
selection of the routing information to be used as the Routing Key |
| 6531 |
for a particular AS. |
| 6532 |
|
| 6533 |
For example, where Application Servers are defined using ranges of |
| 6534 |
ISUP CIC values, the Operator is implicitly splitting up control of |
| 6535 |
the related circuit groups. Some CIC value range assignments may |
| 6536 |
interfere with ISUP circuit group management procedures. |
| 6537 |
|
| 6538 |
In the process of failover, it is recommended that in the case of |
| 6539 |
ASPs supporting call processing, stable calls do not fail. It is |
| 6540 |
possible that calls in "transition" may fail, although measures of |
| 6541 |
communication between the ASPs involved can be used to mitigate this. |
| 6542 |
For example, the two ASPs may share call state via shared memory, or |
| 6543 |
|
| 6544 |
|
| 6545 |
|
| 6546 |
|
| 6547 |
|
| 6548 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 117]</span></pre> |
| 6549 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-118" ></span> |
| 6550 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 6551 |
|
| 6552 |
|
| 6553 |
may use an ASP to ASP protocol to pass call state information. Any |
| 6554 |
ASP-to-ASP protocol to support this function is outside the scope of |
| 6555 |
this document. |
| 6556 |
|
| 6557 |
<span class="h4"><a class="selflink" id="appendix-A.2.2" href="#appendix-A.2.2">A.2.2</a> Signalling Gateway Redundancy</span> |
| 6558 |
|
| 6559 |
Signalling Gateways may also be distributed over multiple hosts. |
| 6560 |
Much like the AS model, SGs may comprise one or more SG Processes |
| 6561 |
(SGPs), distributed over one or more hosts, using an active/backup or |
| 6562 |
a loadsharing model. Should an SGP lose all or partial SS7 |
| 6563 |
connectivity and other SGPs exist, the SGP may terminate the SCTP |
| 6564 |
associations to the concerned ASPs. |
| 6565 |
|
| 6566 |
It is therefore possible for an ASP to route signalling messages |
| 6567 |
destined to the SS7 network using more than one SGP. In this model, |
| 6568 |
a Signalling Gateway is deployed as a cluster of hosts acting as a |
| 6569 |
single SG. A primary/backup redundancy model is possible, where the |
| 6570 |
unavailability of the SCTP association to a primary SGP could be used |
| 6571 |
to reroute affected traffic to an alternate SGP. A loadsharing model |
| 6572 |
is possible, where the signalling messages are loadshared between |
| 6573 |
multiple SGPs. A broadcast model is also possible, where signalling |
| 6574 |
messages are sent to each active SGP in the SG. The distribution of |
| 6575 |
the MTP3-user messages over the SGPs should be done in such a way to |
| 6576 |
minimize message missequencing, as required by the SS7 User Parts. |
| 6577 |
|
| 6578 |
It may also be possible for an ASP to use more than one SG to access |
| 6579 |
a specific SS7 end point, in a model that resembles an SS7 STP mated |
| 6580 |
pair. Typically, SS7 STPs are deployed in mated pairs, with traffic |
| 6581 |
loadshared between them. Other models are also possible, subject to |
| 6582 |
the limitations of the local SS7 network provisioning guidelines. |
| 6583 |
|
| 6584 |
From the perspective of the M3UA layer at an ASP, a particular SG is |
| 6585 |
capable of transferring traffic to a provisioned SS7 destination X if |
| 6586 |
an SCTP association with at least one SGP of the SG is established, |
| 6587 |
the SGP has returned an acknowledgement to the ASP to indicate that |
| 6588 |
the ASP is actively handling traffic for that destination X, the SGP |
| 6589 |
has not indicated that the destination X is inaccessible and the SGP |
| 6590 |
has not indicated MTP Restart. When an ASP is configured to use |
| 6591 |
multiple SGPs for transferring traffic to the SS7 network, the ASP |
| 6592 |
must maintain knowledge of the current capability of the SGPs to |
| 6593 |
|
| 6594 |
handle traffic to destinations of interest. This information is |
| 6595 |
crucial to the overall reliability of the service, for active/backup, |
| 6596 |
loadsharing and broadcast models, in the event of failures, recovery |
| 6597 |
and maintenance activities. The ASP M3UA may also use this |
| 6598 |
information for congestion avoidance purposes. The distribution of |
| 6599 |
the MTP3-user messages over the SGPs should be done in such a way to |
| 6600 |
minimize message missequencing, as required by the SS7 User Parts. |
| 6601 |
|
| 6602 |
|
| 6603 |
|
| 6604 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 118]</span></pre> |
| 6605 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-119" ></span> |
| 6606 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 6607 |
|
| 6608 |
|
| 6609 |
Editors' Addresses |
| 6610 |
|
| 6611 |
Greg Sidebottom |
| 6612 |
Signatus Technologies |
| 6613 |
Kanata, Ontario, Canada |
| 6614 |
|
| 6615 |
EMail: [email protected] |
| 6616 |
|
| 6617 |
|
| 6618 |
Ken Morneault |
| 6619 |
Cisco Systems Inc. |
| 6620 |
13615 Dulles Technology Drive |
| 6621 |
Herndon, VA, USA 20171 |
| 6622 |
|
| 6623 |
EMail: [email protected] |
| 6624 |
|
| 6625 |
|
| 6626 |
Javier Pastor-Balbas |
| 6627 |
Ericsson Espana S.A. |
| 6628 |
C/ Retama 1 |
| 6629 |
28045 Madrid - Spain |
| 6630 |
|
| 6631 |
EMail: [email protected] |
| 6632 |
|
| 6633 |
|
| 6634 |
|
| 6635 |
|
| 6636 |
|
| 6637 |
|
| 6638 |
|
| 6639 |
|
| 6640 |
|
| 6641 |
|
| 6642 |
|
| 6643 |
|
| 6644 |
|
| 6645 |
|
| 6646 |
|
| 6647 |
|
| 6648 |
|
| 6649 |
|
| 6650 |
|
| 6651 |
|
| 6652 |
|
| 6653 |
|
| 6654 |
|
| 6655 |
|
| 6656 |
|
| 6657 |
|
| 6658 |
|
| 6659 |
|
| 6660 |
<span class="grey">Sidebottom, et. al. Standards Track [Page 119]</span></pre> |
| 6661 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-120" ></span> |
| 6662 |
<span class="grey"><a href="./rfc3332">RFC 3332</a> SS7 MTP3-User Adaptation Layer September 2002</span> |
| 6663 |
|
| 6664 |
|
| 6665 |
Full Copyright Statement |
| 6666 |
|
| 6667 |
Copyright (C) The Internet Society (2002). All Rights Reserved. |
| 6668 |
|
| 6669 |
This document and translations of it may be copied and furnished to |
| 6670 |
others, and derivative works that comment on or otherwise explain it |
| 6671 |
or assist in its implementation may be prepared, copied, published |
| 6672 |
and distributed, in whole or in part, without restriction of any |
| 6673 |
kind, provided that the above copyright notice and this paragraph are |
| 6674 |
included on all such copies and derivative works. However, this |
| 6675 |
document itself may not be modified in any way, such as by removing |
| 6676 |
the copyright notice or references to the Internet Society or other |
| 6677 |
Internet organizations, except as needed for the purpose of |
| 6678 |
developing Internet standards in which case the procedures for |
| 6679 |
copyrights defined in the Internet Standards process must be |
| 6680 |
followed, or as required to translate it into languages other |
| 6681 |
than English. |
| 6682 |
|
| 6683 |
The limited permissions granted above are perpetual and will not be |
| 6684 |
revoked by the Internet Society or its successors or assigns. |
| 6685 |
|
| 6686 |
This document and the information contained herein is provided on an |
| 6687 |
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING |
| 6688 |
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING |
| 6689 |
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION |
| 6690 |
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF |
| 6691 |
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. |
| 6692 |
|
| 6693 |
Acknowledgement |
| 6694 |
|
| 6695 |
Funding for the RFC Editor function is currently provided by the |
| 6696 |
Internet Society. |
| 6697 |
|
| 6698 |
|
| 6699 |
|
| 6700 |
|
| 6701 |
|
| 6702 |
|
| 6703 |
|
| 6704 |
|
| 6705 |
|
| 6706 |
|
| 6707 |
|
| 6708 |
|
| 6709 |
|
| 6710 |
|
| 6711 |
|
| 6712 |
|
| 6713 |
|
| 6714 |
|
| 6715 |
|
| 6716 |
Sidebottom, et. al. Standards Track [Page 120] |
| 6717 |
</pre> |