Description
M2PA (Message Transfer Part 2 - User Peer-to-Peer Adaptation Layer) is a protocol defined by the IETF (SIGTRAN) and adopted by 3GPP for transporting SS7 MTP Level 2 (MTP2) signaling messages over IP networks. It operates as an adaptation layer, emulating the services of the traditional MTP2 link layer over a Stream Control Transmission Protocol (SCTP) association. The primary architectural role of M2PA is to allow MTP Level 3 (MTP3) to function as if it were communicating over a standard TDM-based MTP2 link, while the underlying physical transport is IP. This is achieved by mapping MTP2 primitives and messages to SCTP streams and ensuring in-sequence delivery, flow control, and error detection/correction mechanisms comparable to the original MTP2.
At its core, M2PA establishes a peer-to-peer connection between two Signaling Points (SPs) or Signaling Transfer Points (STPs) using SCTP, which provides a reliable, connection-oriented transport with multi-homing support. M2PA packets contain an adaptation layer header that identifies the message as M2PA and includes sequence numbers for link alignment and proving. The protocol handles link status management, including sending and receiving proving units to verify the integrity and alignment of the link, similar to the proving period in TDM MTP2. It also manages the changeover and changeback procedures to maintain signaling traffic during link failures or maintenance events.
Key components of an M2PA implementation include the M2PA User Adaptation (UA) layer interface to MTP3, the SCTP association management, and the link state control function. The M2PA layer receives MTP3 messages, encapsulates them with the M2PA header, and passes them to SCTP for transmission. Conversely, it receives packets from SCTP, strips the M2PA header, and delivers the MTP3 message in the correct order. Its role in the network is pivotal in Signaling Gateways (SGs) and IP-enabled Signal Transfer Points (IP-STPs), where it enables seamless interworking between legacy SS7 networks and IP-based signaling networks like IP Multimedia Subsystem (IMS) or 4G/5G core networks, ensuring backward compatibility and a smooth transition to all-IP architectures.
Purpose & Motivation
M2PA was created to address the industry's need to migrate traditional circuit-switched SS7 signaling networks to more cost-effective, scalable, and flexible IP-based infrastructures. Historically, SS7 signaling relied on Time-Division Multiplexing (TDM) links (e.g., E1/T1) using the MTP2 protocol for reliable link-layer signaling. These TDM networks were expensive to maintain, lacked bandwidth flexibility, and were not natively compatible with modern IP-based core networks. The limitations of TDM, including rigid capacity and high operational costs, motivated the development of adaptation layers to transport SS7 over IP.
The primary problem M2PA solves is enabling existing MTP3 network elements, such as Service Switching Points (SSPs) or STPs, to communicate over IP links without modifying the MTP3 layer itself. It provides a transparent replacement for the physical MTP2 layer, allowing network operators to leverage IP network benefits like statistical multiplexing, easier provisioning, and integration with IP security mechanisms. This facilitated the creation of IP Signaling Transfer Points (IP-STPs) and Signaling Gateways, which are essential components in hybrid and fully IP-based core networks.
Its creation was driven by the broader SIGTRAN (Signaling Transport) working group efforts within the IETF to define a suite of protocols for SS7 over IP. M2PA specifically caters to scenarios requiring a direct peer-to-peer replacement of an MTP2 link, often in national signaling networks or between adjacent signaling points. It complements other adaptation layers like M3UA, which is used for a different architectural model (IP-based Application Server communication).
Technology family
Core signalling protocols · Core Network
- Phase 1 MAP
- Phase 2 ISUP
- R96 CAP
- R99 GTP-C, GTP-U, GTPv1-C
- Rel-4 BICC
- Rel-5 Diameter, SIP
- Rel-8 GTPv2-C
- Rel-14 PFCP
- Rel-15 HTTP/2 SBI
Also in this family (introduction release not pinned to a single defining specification): INAP, M2PA, SIGTRAN
- M2PA builds on SIGTRAN (not stated verbatim in the specifications)
Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.
Detected Changes Across Releases
verified against 3GPP sourcesDocumented changes in 1 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.
M2PA is specified for the first time in 29.202 as an option on interface B between SRPs, with Annex B defining its use in 3GPP core networks per RFC 4165.
- “M2PA may be used between SRPs, i.e. interface B (refer to Figure 1 of Annex A).” TS 29.202 v8.1.1
- “The definition of the use of M2PA in 3GPP core network is provided in Annex B to this specification.” TS 29.202 v8.1.1
- “This annex defines the application of M2PA in 3GPP core networks as an option on interface B.” TS 29.202 v8.1.1
Defining Specifications
3GPP specifications that define or reference M2PA, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 29.202 vj00 | SS7 Signalling Transport Protocol Architectures | Rel-19 read |