Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Services

MFAF

Messaging Framework Adaptor Function

Services →

MFAF is a 5G core network function that provides a standardized framework for secure, policy-controlled message delivery and exposure to third-party application providers.

Introduced
Rel-17
Where
Core Network › 5G Core
Specifications
10 specs
MFAF Description Purpose What changed Family Neighbours Detected Changes Specifications

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.

What changed in its specifications

The latest release-to-release comparison of specifications that define MFAF. Each summary describes the whole specification, not only this term.

TS 23.501Rel-18 → Rel-19

Rel-19 added MPQUIC steering to multi-access PDU sessions, XR and media handling, and an Energy Information Function. It also added Local Offloading Management for edge computing, Vertical Federated Learning for AI/ML, and Ambient IoT text.

Full comparison in TS 23.501 →
TS 29.517Rel-18 → Rel-19

Rel-19 added data types, event types, and API attributes for application activation time, signalling info, and UE altitude. It also added the UeAltitudeInfo data type and related subscription changes for UAV UE altitude reporting.

Full comparison in TS 29.517 →

Technology family

Network exposure and analytics · Core Network

  1. Rel-11 SCS/AS
  2. Rel-13 IWK-SCEF, SCEF
  3. Rel-15 CAPIF, NEF, NWDAF
  4. Rel-16 SCEF+NEF
  5. Rel-17 ADRF, AnLF, DCCF, L-NEF, MDAF, MFAF, MTLF
  6. Rel-18 RE-NWDAF
  • MFAF used together with DCCF
    “The MFAF selection function is supported by the DCCF. The DCCF shall utilize the NRF to discover MFAF instance(s) unless MFAF information is available by other means, e.g. locally configured on the DCCF.” TS 23.501

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.

Release Timeline

Detected Changes Across Releases

verified against 3GPP sources

Documented changes in 4 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.

Rel-17 introduced

Rel-17 first defines the MFAF: its architecture role and functionality in TS 23.501/23.288, and the Nmfaf_3daDataManagement configure/deconfigure and 3caDataManagement notify/fetch services in TS 29.576.

  • “The Messaging Framework Adaptor Function (MFAF) supports the following functionality:” TS 23.501 v17.15.0
  • “Upon the reception of an HTTP POST request with: "{apiRoot}/nmfaf-3dadatamanagement/<apiVersion>/configurations" as Resource URI and MfafConfiguration data structure as request body, the MFAF shall:” TS 29.576 v17.6.0
  • MFAF services definition TS 23.288CR0309
Rel-18 specification text

MFAF gained relocation/reselection support (UE data subscription context transfer to a target MFAF), a fetch-instruction option and a notification endpoint correlation ID, plus corrections to its service APIs.

  • “Source DCCF uses the Nmfaf_3daDataManagement service to request transfer of UE MFAF data subscription context to the target MFAF.” TS 23.288 v18.13.0
  • “If the "notifCorrId" attribute within the NotifyEndpoint data type is absent, the MFAF shall generate a dummy identifier for this notification endpoint” TS 29.576 v18.8.0
  • “This service allows the transfer of an MFAF UE context to a consumer (e.g. a target MFAF).” TS 23.501 v18.12.0
Rel-19 1 CR

Rel-19 adds an Nmfaf_ContextManagement service to MFAF that transfers configurations between MFAFs, and generalises MFAF configuration beyond mapping data to out-bound notification endpoints.

  • “The MFAF Context Management service enables the transfer of configurations between MFAFs.” TS 29.576 v19.7.0
  • “the MFAF shall perform the transfer of the indicated configurations, i.e. respond with "200 OK" with the message body containing the ContextTransferResp data structure” TS 29.576 v19.7.0
  • MFAF 3daDataManagement updates to support MFAF transfer TS 29.576CR0076
Rel-20 1 CR

The Transferring MFAF configurations procedure in TS 29.576 was corrected in Rel-20.

  • Correction of Transferring MFAF configurations procedure TS 29.576CR0095

Defining Specifications

3GPP specifications that define or reference MFAF, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 23.501 vk30 5G System Architecture Rel-20 read
TS 23.700 vk10 AI/ML Application Layer Support Phase 2 Rel-20 read
TS 29.517 vk10 AF Event Exposure Service Rel-20 read
TS 29.520 vk10 5G NWDAF Services Rel-20 read
TS 29.552 vk10 5G Network Data Analytics Procedures Rel-20 read
TS 29.564 vk10 Nupf Service Based Interface Rel-20 read
TS 29.575 vk10 ADRF Service Based Interface Rel-20 read
TS 29.576 vk10 MFAF Service Based Interface Rel-20 read
TS 29.591 vk10 NEF Southbound Services Rel-20 read
TS 29.889 vj10 Study on UPF data collection for AI/ML Rel-19 read