Description
The Messaging Framework Adaptor Function (MFAF) is a service-based architecture (SBA) component within the 5G Core (5GC) network, defined as a Network Function (NF). It acts as a central adaptor and exposure point for messaging services. Architecturally, the MFAF interfaces with other core network functions like the Network Exposure Function (NEF) and the Unified Data Management (UDM) to securely expose messaging capabilities. It also connects to external application servers and legacy messaging systems, such as IP Multimedia Subsystem (IMS) for SMS-over-IP (SMS-IP) or other messaging application servers. Its primary role is to abstract the underlying network complexities and provide a unified, standardized API framework for message delivery, enabling various messaging paradigms including person-to-person (P2P), application-to-person (A2P), and conversational messaging (e.g., RCS).
Operationally, the MFAF handles message routing, policy enforcement, and service logic execution. When a message is submitted from an external application provider, the MFAF authenticates and authorizes the request via the NEF, applies relevant policies (e.g., spam control, charging rules), and determines the optimal delivery path. It can interact with the UDM to retrieve subscriber data and routing information. For delivery to a UE, it may forward the message to the appropriate SMSC, IMS, or directly to the Access and Mobility Management Function (AMF) for NAS transport, depending on the message type and network configuration. It supports features like delivery reports, message prioritization, and bulk messaging operations.
The MFAF's internal architecture includes service-based interfaces (SBIs) like Nmfaf for northbound exposure and interfaces to other NFs. Key components include the Adaptor Logic, which translates between external API formats and internal network protocols; the Policy Enforcement Function, which applies operator-defined rules; and the Charging Trigger Function, which generates charging data records. Its introduction signifies a shift from monolithic, siloed messaging systems (like traditional SMSC) to a flexible, cloud-native framework that can easily integrate new messaging services and APIs, fostering innovation in the 5G messaging ecosystem.
Purpose & Motivation
The MFAF was created to address the evolving landscape of messaging in the 5G era, where traditional SMS and MMS coexist with rich communication services (RCS) and new application-to-person services. Prior to its introduction, messaging service exposure to third parties was often achieved through proprietary gateways or limited APIs, leading to fragmentation, security challenges, and inefficient network resource utilization. The MFAF provides a standardized, secure, and scalable framework within the 5G core to unify these access methods.
Its development was motivated by the need to support new business models, such as A2P messaging for enterprise verification, marketing, and notifications, which require robust policy control, charging, and quality of service. Furthermore, as networks evolve towards cloud-native, service-based architectures, a dedicated function was necessary to manage the complexity of interworking between legacy messaging systems and new 5G service-based interfaces. The MFAF solves these problems by offering a centralized adaptor that simplifies integration for application providers while giving network operators granular control over messaging traffic, security, and monetization.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (33 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, the Messaging Framework Adaptor Function (MFAF) was newly introduced as a Network Function that exhibits a service-based interface (Nmfaf). It was specified to be a potential receiver of User Plane Function event notifications and is defined with the capability to instruct a Messaging Framework for data delivery and formatting.
In Release 16, the Messaging Framework Adaptor Function (MFAF) was newly introduced as a dedicated Network Function that exhibits a service-based interface (Nmfaf). It was specified to operate within an enhanced framework for data exposure, specifically as a receiver for User Plane Function event notifications alongside functions like the NWDAF and DCCF. The MFAF's role includes instructing a messaging framework to format, process, and send data or notifications to consumers.
In Release 17, the Messaging Framework Adaptor Function (MFAF) saw enhancements to its service-based interface (Nmfaf), including improved support for callback functions and error response handling. The updates also involved corrections and cleanup to its APIs, such as the 3caDataManagement API, and refined its role in data collection and analytics exposure alongside the DCCF. Furthermore, specifications were clarified to remove the UDM from the list of MFAF service consumers.
- Resolve editor’s note in Analytics Exposure via DCCF and MFAF TS 29.552CR0007
- Reference to DCCF and MFAF Services description clause TS 23.501CR2808
- Cleanup for NWDAF, DCCF, MFAF and ADRF services TS 23.501CR3471
- Update Analytics Exposure via DCCF and MFAF TS 29.552CR0011
- Update Data Collection via Messaging Framework TS 29.552CR0015
- Adding 3XX and error response handling support for MFAF services TS 29.576CR0001
+ 4 more changes
In Release 18, the Messaging Framework Adaptor Function (MFAF) was formally integrated into the 5G service-based architecture, exposing its own service-based interface (Nmfaf). Key enhancements included defining MFAF as a valid consumer of network function services alongside the DCCF, and specifying its role in receiving User Plane Function event notifications. Furthermore, corrections and clarifications were made to its service APIs, including the 3daDataManagement and 3caDataManagement interfaces.
- MFAF service consumers TS 29.576CR0053
- MFAF API names corrections TS 29.576CR0054
- MFAF 3daDataManagement API corrections TS 29.576CR0057
- MFAF 3caDataManagement API corrections TS 29.576CR0058
- Adding DCCF and MFAF to the NF service consumers TS 29.517CR0093
- Adding DCCF and MFAF to the NF service consumers TS 29.591CR0106
In Release 19, the MFAF (Messaging Framework Adaptor Function) was enhanced with a new ContextManagement API service, including its associated data model and OpenAPI specification. The release also introduced specific support for MPS (Mission Critical Services) for Messaging, enabling priority treatment for services like SMS over NAS. Furthermore, updates were made to clarify and correct MFAF procedures, including configuration transfer, serving area definitions, and the use of Maps for configurations transfer.
- MPS support for Messaging TS 23.501CR5499
- MFAF ContextManagement API service descripiton TS 29.576CR0073
- MFAF ContextManagement API data model TS 29.576CR0074
- MFAF ContextManagement API OpenAPI TS 29.576CR0075
- MFAF 3daDataManagement updates to support MFAF transfer TS 29.576CR0076
- target MFAF Notification Information TS 29.576CR0078
+ 7 more changes
Explore further
Broader topics and technologies where MFAF plays a role.
Defining Specifications
3GPP specifications that define or reference MFAF, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.501 vk00 | 5G System Architecture Stage 2 | Rel-20 |
| TS 23.700 vk00 | XR Services Application Enablement Layer | Rel-20 |
| TS 29.517 vj40 | 5G AF Event Exposure Service Stage 3 | Rel-19 |
| TS 29.520 vj40 | 5G Network Data Analytics Services Stage 3 | Rel-19 |
| TS 29.552 vj40 | 5G Network Data Analytics Signalling Flows | Rel-19 |
| TS 29.564 vj50 | Nupf Service Based Interface Protocol | Rel-19 |
| TS 29.575 vj40 | 5G Analytics Data Repository Services Stage 3 | Rel-19 |
| TS 29.576 vj40 | 5G Messaging Framework Adaptor Services Stage 3 | Rel-19 |
| TS 29.591 vj40 | 5G NEF Southbound Services Stage 3 | Rel-19 |
| TS 29.889 vj10 | Study on UPF data collection for AI/ML | Rel-19 |