Empty cells are descriptive text only
| Description | Compliance | Notes | |
|---|---|---|---|
1 |
Introduction |
||
1.1 |
Scope |
||
1.2 |
Terminology |
||
1.3 |
M3UA Overview |
||
1.3.1 |
Protocol Architecture |
||
1.3.2 |
Services Provided by the M3UA Layer |
||
1.3.2.1 |
Support for the Transport of MTP3-User Messages |
Full |
|
1.3.2.2 |
Native Management Functions |
Full |
|
1.3.2.3 |
Interworking with MTP3 Network Management Functions |
Partial |
SGP role is not supported. |
1.3.2.4 |
Support for the Management of SCTP Associations between SG and ASPs |
Full |
|
1.3.2.5 |
Support for the Management of Connections to Multiple SGs |
Full |
|
1.4 |
Functional Areas |
||
1.4.1 |
Signaling Point Code Representation |
||
1.4.2 |
Routing Contexts and Routing Keys |
||
1.4.2.1 |
Overview |
Full |
|
1.4.2.2 |
Routing Key Limitations |
Full |
|
1.4.2.3 |
Managing Routing Contexts and Routing Keys |
Partial |
Dynamic key registration is not supported. |
1.4.2.4 |
Message Distribution at the SGP |
None |
SGP role is not supported. |
1.4.2.5 |
Message Distribution at the ASP |
Full |
|
1.4.3 |
SS7 and M3UA Interworking |
||
1.4.3.1 |
Signaling Gateway SS7 Layers |
||
1.4.3.2 |
SS7 and M3UA Interworking at the SGC |
Partial |
Complied in areas regarding ASP. |
1.4.3.3 |
Application Server |
Full |
|
1.4.3.4 |
IPSP Considerations |
||
1.4.4 |
Redundancy Models |
||
1.4.4.1 |
Application Server Redundancy |
Partial |
n+0 model is supported. |
1.4.5 |
Flow Control |
Full |
|
1.4.6 |
Congestion Management |
None |
Congestion indication mechanism in M3UA layer is not supported. |
1.4.7 |
SCTP Stream Mapping |
Full |
|
1.4.8 |
SCTP Client/Server Model |
Full |
|
1.5 |
Sample Configurations |
||
1.5.1 |
Example 1: ISUP Message Transport |
None |
No M3UA user other than SCCP is supported. |
1.5.2 |
Example 2: SCCP Transport between IPSPs |
Full |
|
1.5.3 |
Example 3: SGC Resident SCCP Layer |
Partial |
Compliant in areas regarding ASP. |
1.6 |
Definition of M3UA Boundaries |
||
1.6.2 |
Definition of the Boundary between M3UA and SCTP |
||
1.6.3 |
Definition of the Boundary between M3UA and Layer Management |
||
2 |
Conventions |
||
3 |
M3UA Protocol Elements |
Full |
|
3.1 |
Common Message Header |
Full |
|
3.1.1 |
M3UA Protocol Versions: 8 bit (unsigned integer) |
Full |
|
3.1.2 |
Message Classes and Types |
Full |
|
3.1.3 |
Reserved: 8 bit |
Full |
|
3.1.4 |
Message Length: 32 bit (unsigned integer) |
Full |
|
3.2 |
Variable-Length Parameter Format |
Full |
|
3.3 |
Transfer Messages |
||
3.3.1 |
Payload Data Message (DATA) |
Full |
|
3.4 |
SS7 Signaling Network Management (SSNM) Messages |
||
3.4.1 |
Destination Unavailable (DUNA) |
Full |
|
3.4.2 |
Destination Available (DAVA) |
Full |
|
3.4.3 |
Destination State Audit (DAUD) |
Full |
|
3.4.4 |
Signaling Congestion (SCON) |
Full |
|
3.4.5 |
Destination User Part Unavailable (DUPU) |
Full |
|
3.4.6 |
Destination Restricted (DRST) |
Full |
|
3.5 |
ASP State Maintenance (ASPSM) Messages |
||
3.5.1 |
ASP Up |
Full |
|
3.5.2 |
ASP Up Acknowledgement (ASP Up Ack) |
Full |
|
3.5.3 |
ASP Down |
Full |
|
3.5.4 |
ASP Down Acknowledgement (ASP Down Ack) |
Full |
|
3.5.5 |
Heartbeat (BEAT) |
Partial |
BEAT message is only acknowledged, not sent. |
3.5.6 |
Heartbeat Acknowledgement (BEAT Ack) |
Full |
|
3.6 |
Routing Key Management (RKM) Messages (Optional) |
None |
Routing Key Management is not supported. |
3.6.1 |
Registration Request (REG REQ) |
None |
Routing Key Management is not supported. |
3.6.2 |
Registration Response (REG RSP) |
None |
Routing Key Management is not supported. |
3.6.3 |
Deregistration Request (DEREG REQ) |
None |
Routing Key Management is not supported. |
3.6.4 |
Deregistration Response (DEREG RSP) |
None |
Routing Key Management is not supported. |
3.7 |
ASP Traffic Maintenance (SPTM) Messages |
||
3.7.1 |
ASP Active |
Full |
|
3.7.2 |
ASP Active Acknowledgement (ASP Active Ack) |
Full |
|
3.7.3 |
ASP Inactive |
Full |
|
3.7.4 |
ASP Inactive Acknowledgement (ASP Inactive Ack) |
Full |
|
3.8 |
Management (MGMT) Messages |
||
3.8.1 |
Error |
Full |
|
3.8.2 |
Notify |
Full |
|
4 |
Procedures |
||
4.1 |
Procedures to Support the M3UA-User |
||
4.1.1 |
Receipt of Primitives from the M3UA-User |
Full |
|
4.2 |
Receipt of Primitives from Layer Management |
Full |
|
4.2.1 |
Receipt of M3UA Peer Management Messages |
Full |
|
4.3 |
AS and ASP/IPSP State Maintenance |
Partial |
IPSP DE model is not supported. |
4.3.1 |
ASP/IPSP States |
Full |
|
4.3.2 |
AS States |
Full |
|
4.3.3 |
M3UA Management Procedures for Primitives |
Full |
|
4.3.4 |
ASP Procedures for Peer-to-Peer Messages |
||
4.3.4.1 |
ASP Up Procedures |
Full |
|
4.3.4.1.1 |
M3UA Version Control and ASP Up |
Full |
|
4.3.4.1.2 |
IPSP Considerations (ASP Up) |
Full |
|
4.3.4.2 |
ASP Down Procedures |
Partial |
After reaching limit of unacknowledged ASP-DOWN requests, SCTP association is shut down. |
4.3.4.3 |
ASP Active Procedures |
Partial |
Only Loadshare traffic mode is supported. |
4.3.4.3.1 |
IPSP Consideration (ASP Active) |
Full |
|
4.3.4.4 |
ASP Inactive Procedures |
Full |
|
4.3.4.4 |
IPSP Considerations (ASP Inactive) |
Full |
|
4.3.4.5 |
Notify Procedures |
Full |
|
4.3.4.5.1 |
IPSP Considerations (NTFY) |
Full |
|
4.3.4.6 |
Heartbeat Procedures |
Partial |
Only reception of BEAT message is supported. |
4.4 |
Routing Key Management Procedures (Optional) |
||
4.4.1 |
Registration |
None |
Routing Key Management is not supported. |
4.4.2 |
Deregistration |
None |
Routing Key Management is not supported. |
4.4.3 |
IPSP Consideration (REG/DEREG) |
None |
Routing Key Management is not supported. |
4.5 |
Procedures to Support the Availability or Congestion Status of SS7 Destination |
||
4.5.1 |
At an SGP |
Partial |
Only ASP related procedures are supported. |
4.5.2 |
At an ASP |
||
4.5.2.1 |
Single SG Configurations |
Partial |
Congestion status is not supported. |
4.5.2.2 |
Multiple SG Configurations |
Partial |
Congestion status is not supported. |
4.6 |
MTP3 Restart |
Full |
|
4.7 |
NIF Not Available |
None |
SGP role is not supported |
4.8 |
M3UA Version Control |
Full |
|
4.9 |
M3UA Termination |
Full |
|
5 |
Examples of M3UA Procedures |
||
5.1 |
Establishment of Associations and Traffic between SGs and ASPs |
Full |
|
5.1.1 |
Single ASP in an Application Server (1+0 sparing) |
Full |
|
5.1.1.1 |
Single ASP/IPSP in an Application Server (1+0 sparing) No Registration |
Full |
|
5.1.1.2 |
Single ASP in an Application Server (1+0 sparing) Dynamic Registration |
None |
Routing Key Management is not supported. |
5.1.1.3 |
Single ASP in Multiple Application Servers (each with 1+0 sparing), Dynamic Registration (Case 1 - Multiple Registration Requests) |
None |
Routing Key Management is not supported. |
5.1.1.4 |
Multiple Servers (each with 1+0 sparing), Dynamic Registration (Case 1 - Multiple Registration Requests) |
None |
Routing Key Management is not supported. |
5.1.2 |
Two ASPs in Application Server (1+1 sparing) |
None |
1+1 sparing is not supported. |
5.1.3 |
Two ASPs in Application Server (1+1 sparing, loadsharing case) |
Full |
|
5.1.4 |
Three ASPs in Application Server (n+k sparing, loadsharing case) |
None |
n+k sparing is not supported. |
5.2 |
ASP/IPSP Traffic Failover Examples |
||
5.2.1 |
1+1 sparing", Withdrawal of ASP/IPSP, Backup Override |
None |
1+1 sparing is not supported. |
5.2.2 |
1+1 sparing", Backup Override |
None |
1+1 sparing is not supported. |
5.2.3 |
n+k" sparing, Loadsharing case, Withdrawal of ASP |
None |
n+k sparing is not supported. |
5.3 |
Normal Withdrawal of an ASP from an Application Server and Teardown of an Association Will Not be Sent/Received |
None |
Routing Key Management is not supported. |
5.4 |
Auditing Examples |
||
5.4.1 |
SG State: Uncongested/Available |
Full |
|
5.4.2 |
SG State: Congested (Congestion Level=2)/Available |
Full |
|
5.4.3 |
SG State: Unknown/Available |
Full |
|
5.5 |
M3UA/MTP3-User Boundary Examples |
||
5.5.1 |
At an ASP |
||
5.5.1.1 |
Support for MTP Transfer on the ASP |
||
5.5.1.1.1 |
Support for MTP Transfer Request Primitive |
Full |
|
5.5.1.1.2 |
Support for MTP Transfer Indication Primitive |
Full |
|
5.5.1.1.3 |
Support for ASP Querying of SS7 Destination States |
Full |
|
5.5.2 |
At an SGP |
Full |
|
5.5.2.1 |
Support for MTP Transfer Request Primitive |
Full |
|
5.5.2.2 |
Support for MTP Transfer Indication Primitive |
Full |
|
5.5.2.3 |
Resume MTP Status Indication Primitive |
||
5.5.2.3.1 |
Destination Unavailable |
Full |
|
5.5.2.3.2 |
Destination Available |
Full |
|
5.5.2.3.3 |
SS7 Network Congestion |
None |
Congestion levels are not interpreted at ASP. |
5.5.2.3.4 |
Destination User Part Available |
Full |
|
5.6 |
Examples of IPSP communication |
||
5.6.1 |
Single Exchange |
Full |
|
5.6.2 |
Double Exchange |
None |
Double Exchnage mode is not supported. |
6 |
Security Considerations |
None |
SIGTRAN over TLS is not supported. |
7 |
IANA Considerations |
||
7.1 |
SCTP Payload Protocol Identifier |
Full |
|
7.2 |
M3UA Port Number |
Full |
|
7.3 |
M3UA Protocol Extentions |
Full |
|
7.3.1 |
IETF Defined Message Classes |
||
7.3.2 |
IETF Defined Message Types |
