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

Glossary term · Core Network

MRFP

Multimedia Resource Function Processor

Core Network →

MRFP is the media processing component of an IMS network that executes real-time functions like audio/video mixing, transcoding, and media playback under the control of the MRFC.

Introduced
Rel-5
Where
Services › Codecs
Specifications
46 specs
Also in
Core Network, Management
MRFP Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The Multimedia Resource Function Processor (MRFP) is the user plane or media processing entity within the IMS Media Resource Function (MRF). It is responsible for the actual manipulation and processing of real-time media streams, including audio, video, and real-time text. Operating under the strict command of the Multimedia Resource Function Controller (MRFC), the MRFP executes media-related operations via the Mp interface, which is based on the H.248 (Megaco) protocol. The MRFP contains the physical or virtualized resources—such as digital signal processors (DSPs), general-purpose processors, and specialized hardware—that perform computationally intensive tasks like mixing multiple media streams into a conference, transcoding between different codecs (e.g., AMR to G.711), playing pre-recorded announcements, and detecting dual-tone multi-frequency (DTMF) signals.

Architecturally, the MRFP is a slave component that receives directives from the MRFC. The MRFC uses H.248 commands to create 'contexts' within the MRFP, which are logical containers for media sessions. Within these contexts, the MRFC adds 'terminations' that represent endpoints for media streams. The MRFP then connects these terminations and applies specified 'packages' of media processing functions. For example, in a three-way audio conference, the MRFP would create a context with three terminations (one for each participant), apply a mixing function that combines the audio from all parties, and send the mixed stream back to each termination. The MRFP is stateless from a service logic perspective; all intelligence and session state reside in the MRFC.

In practical operation, when a service requires media processing, the MRFC instructs the MRFP to allocate the necessary ports and processing power. The MRFP establishes bearer-level connections (over RTP/UDP/IP) with the user equipment (UE) or other network endpoints as directed. It then continuously processes the incoming media packets in real-time, performing the commanded functions and forwarding the resulting streams. The MRFP also generates reports and notifications (e.g., 'DTMF digit 1 detected') back to the MRFC via H.248, allowing the control plane to react to media events. This design allows for high-throughput, low-latency media handling that is completely decoupled from the complexity of signaling and service logic.

Purpose & Motivation

The MRFP was developed to provide a standardized, high-performance media processing platform for IMS-based services, separating the demanding task of real-time media manipulation from the signaling control functions. Before its definition, media processing was often integrated into monolithic switches or proprietary server platforms, leading to vendor lock-in, inefficient resource utilization, and difficulty in scaling media capacity independently of control intelligence. The MRFP, as the media plane counterpart to the MRFC, solves these problems by offering a dedicated, controllable resource pool for media functions.

Its creation was essential for enabling the commercial deployment of advanced, network-hosted multimedia services. Services like audio/video conferencing, multimedia ringback tones, and interactive voice response systems require consistent, reliable, and high-quality media processing that can scale to serve millions of subscribers. The MRFP provides this capability in a network-centric manner, offloading complex processing from end-user devices and ensuring service uniformity. By standardizing the H.248 control interface, 3GPP allowed operators to deploy MRFPs from different vendors than their MRFCs, fostering competition, innovation in media processing hardware/software, and cost-effective scaling of media resources to meet growing traffic demands.

What changed in its specifications

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

TS 23.127Rel-4 → Rel-5

Rel-5 added IMS provisioning with new network element definitions (HSS, IMS, ISC, MRF). It also added OSA enhancements covering HE-VASP support, policy management, presence, and removing User Profile Management.

Full comparison in TS 23.127 →
TS 23.198Rel-7 → Rel-8

Content management web service, parts 21 and 22, Part 10, and removal of standalone Part 4.

Full comparison in TS 23.198 →

Technology family

IMS functions · Services › IMS

  1. R99 OSA-SCS
  2. Rel-5 AS, BGCF, CSCF, I-CSCF, IM-MGW, IM-SSF, MGCF, MRFC, MRFP, P-CSCF, S-CSCF
  3. Rel-6 IBCF, IMS-ALG, TrGW
  4. Rel-7 E-CSCF, IMS-AGW
  5. Rel-8 MRB, SCC AS
  6. Rel-9 EATF
  7. Rel-10 ATCF, ATGW
  • MRFP used together with MRFC
    “Interprets information coming from an AS and S‑CSCF (e.g. session identifier) and control MRFP accordingly.” TS 23.002

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 15 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-5 introduced

The MRF is split into MRFC and MRFP, with MRFP defined as the media resource processor controlled by the MRFC, with its own tasks and interactions.

  • “The MRF is split into Multimedia Resource Function Controller (MRFC) and Multimedia Resource Function Processor (MRFP).” TS 23.228 v5.15.0
  • “Control the media stream resources in the MRFP.” TS 23.228 v5.15.0
  • “Tasks of the MRFP are the following:” TS 23.228 v5.15.0
Rel-6 specification text

MRFP gained new session-based messaging conference roles: establishing message connections with participants and distributing messages, with the MRFC–MRFP interface left unstandardised in this release.

  • “- MRFP must be able to establish message connections with all involved parties.” TS 23.228 v6.16.0
  • “- MRFC/MRFP must be able to receive messages from conference participants and to distribute messages to all or some of the participants.” TS 23.228 v6.16.0
  • “an MRFC/MRFP or an IMS AS shall be used to control the media resources.” TS 23.228 v6.16.0
Rel-7 specification text

MRFP gained new specified behaviour in Rel-7: announcement and SSML text playback, recording, DTMF reporting, ASR recognition against SRGS grammars, and error indication, plus Mp interface procedures.

  • “The MRFP shall execute the basic SSML elements and may ignore the SSML elements not supported.” TS 23.333 v7.3.1
  • “The MRFP shall report DTMF Digits detected as RTP Telephony Events” TS 23.333 v7.3.1
  • “The MRFP shall execute the recognition against the SRGS grammar and may ignore SRGS elements which are not supported.” TS 23.333 v7.3.1
Rel-8 specification text

MRFP gained messaging and floor control capabilities (MSRP transport, BFCP floor state, message statistics reporting, record and play of messages) and transcoding support in IMS.

  • “The MRFP shall utilize the Message Session Relay Protocol (MSRP) (see IETF RFC 4975 [18]) to transport messages carrying different media” TS 23.333 v8.3.0
  • “The MRFP shall maintain the state of the Floor(s), including which Floors exists, which terminations hold which Floors” TS 23.333 v8.3.0
  • “The MRFC controls functionality in the MRFP to perform media plane transcoding.” TS 23.228 v8.12.0
Rel-9 specification text

The MRFP's RTCP feedback support note was corrected to say support depends on RTCP-fb, with the MRFC sending the rtcp-fb SDP when applicable.

  • “Support is optional and dependent on RTCP-fb support as described in 3GPP TS 26.114 [41].” TS 29.333 v9.3.0
  • “The list of feedback messages supported by the MRFP is preconfigured in the MRFC.” TS 29.333 v9.3.0
Rel-10 specification text

MRFP gained ECN support in Rel-10: it acts as an ECN endpoint, sets the IP ECN field, triggers rate adaptation on ECN-CE, and is configured for ECN via the MRFC.

  • “Upon receipt of a request to apply Explicit Congestion Notification the MRFP shall set the ECN field of the IP header” TS 23.333 v10.5.0
  • “Upon receipt of any IP headers indicating Congestion Experienced (ECN-CE) the MRFP shall trigger rate adaptation” TS 23.333 v10.5.0
  • “This information element requests the MRFP to apply ECN.” TS 23.333 v10.5.0
Rel-11 specification text

MRFP gained Multimedia Priority Service support: it uses Priority information from the MRFC for resource allocation under congestion and applies MPS DSCP marking to user-plane packets.

  • “If the MRFP receives an indication to apply a specific MPS DSCP marking to the user data transport packets, it shall apply this DSCP marking” TS 23.333 v11.1.0
  • “The MRFP may then provide priority allocation of resources once a congestion threshold is reached.” TS 23.333 v11.1.0
  • “The MRFP shall then mark each IP packet header accordingly.” TS 23.333 v11.1.0
Rel-12 specification text

MRFC and MRFP gained EVS speech codec transcoding support, with the MRFC checking MRFP-supported EVS parameters and RTCP APP adaptation messages, plus ICE, CVO and TLS-PSK handling and new NOTIFY reports.

  • “The MRFC and the MRFP may support transcoding to and from the EVS speech codec.” TS 23.333 v12.12.0
  • “The MRFP handling of EVS codec parameters shall follow table 5.13.3.3 in 3GPP TS 23.334 [41].” TS 23.333 v12.12.0
  • “If the MRFP supports the extended RTP header it shall pass any received extended RTP header with CVO bits on to succeeding RTP streams.” TS 29.333 v12.10.0
Rel-13 specification text

MRFP gained support in Rel-13 for SDP capability negotiation, video Region-of-Interest modes (FECC, predefined, arbitrary) and rate adaptation via enhanced bandwidth negotiation, including preserving ROI info during transcoding.

  • “the MRFP shall reserve resources for all of those configurations that it supports” TS 23.333 v13.8.0
  • “if the MRFP applies video transcoding, it shall keep the predefined ROI information unchanged during the transcoding” TS 23.333 v13.8.0
  • “The MRFP may use the "Additional Bandwidth Properties" information element indicating media bandwidth range for rate adaptation” TS 23.333 v13.8.0
Rel-14 specification text

The MRFP gained Multi-stream Multiparty Conferencing Media Handling: autonomous media mixing under an MMCMH policy, simulcast and RTP-level pause/resume support, and concurrent codec capability signalling from the MRFC.

  • “the MRFP shall mix media streams autonomously based on policies for MMCMH” TS 23.333 v14.5.0
  • “the MRFP shall detect voice activity on audio streams and that the MRFP shall forward the main video received from the active speaker” TS 23.333 v14.5.0
  • “Allows the MRFC to request that the MRFP issue a request to a remote endpoint to pause” TS 29.333 v14.3.0
Rel-15 specification text

Text requiring the MRFC to instruct the MRFP to apply ECN procedures and act as an ECT endpoint after successful ECN negotiation was removed in Rel-15.

  • “then it shall indicate to the MRFP that it shall apply the ECN procedures (according to 3GPP TS 26.114 [23]) and act as an ECT endpoint” TS 23.333 v15.2.0
Rel-16 specification text

The MRFP gained support for RTCP feedback "DBI" (delay budget information) signalling, with the MRFC instructing it via a new "DBI" information element, including use in conferencing.

  • “This information element indicates that the MRFP shall be prepared to receive and is allowed to send, respectively, the RTCP feedback messages for "DBI" signalling” TS 23.333 v16.2.0
  • “The MRFP supporting Audio or Multimedia Conferencing, as specified in clause 5.10 and 5.11 may use RTCP feedback messages for "DBI" signalling” TS 23.333 v16.2.0
Rel-17 specification text

MRFP ICE support was updated to RFC 8445/8839, adding ICE pacing: the MRFP calculates a Ta timer value (default 50 ms) and provides it to the MRFC for connectivity checks.

  • “the MRFP shall calculate Ta timer value based on the characteristics of the associated data or shall use the default value of 50 ms” TS 23.333 v17.1.0
  • “shall request the MRFP to provide the desired pacing value for connectivity checks (Ta timer value);” TS 23.333 v17.1.0
  • “The attributes "a=candidate", "a=ice-pwd", "a=ice-ufrag" and "a=ice-pacing" (see IETF RFC 8839 [78]) may be provided” TS 29.333 v17.0.0
Rel-18 specification text

MRFC/MRFP gained IVAS codec transcoding and SDP parameter handling requirements, plus NRF-based discovery and registration of the MRFP as a separate entity.

  • “The MRFC and the MRFP may support transcoding the IVAS speech codec to and from another (mono-format) codec (e.g. AMR-WB or EVS).” TS 23.333 v18.1.0
  • “In such cases the MRFP registers with the NRF using a NF profile that also includes a similar list of media services” TS 23.228 v18.12.0
  • “shall be provided when the MRFP is allowed to send RTCP APP messages.” TS 29.333 v18.1.0
Rel-19 1 CR

A correction was approved in Rel-19 to how the MRFP uses the ActivateTask message for asymmetric media in TS 33.128.

  • Minor Correction for MRFP using ActivateTask Message for Aysmmentric Media TS 33.128CR0803

Defining Specifications

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

SpecificationTitleRelease
TS 23.127 v610 Virtual Home Environment Stage 2 Specification Rel-6 read
TS 23.198 v900 Open Service Access (OSA) Stage 2 Rel-9 read
TS 23.218 vj00 IMS Call Model Specification Rel-19 read
TS 23.228 vk10 IP Multimedia Core Network Subsystem Rel-20 read
TS 23.279 vj00 Combined CS and IMS Services (CSI) Architecture Rel-19 read
TS 23.333 vj00 MRFC-MRFP Mp Interface Requirements Rel-19 read
TS 23.417 v700 IMS Core Component for NGN Architecture Rel-7 read
TS 23.517 v800 IMS Core Architecture for TISPAN NGN Rel-8 read
TS 23.849 vb00 IMS Roaming Resource Control Study Rel-11 read
TR 23.981 vj00 IPv4 IMS Interworking and Migration Study Rel-19 read
TS 24.103 vj00 Telepresence Protocol for IMS Rel-19 read
TS 24.147 vj00 IMS Conferencing Protocol Details Rel-19 read
TS 24.229 vk10 IMS SIP/SDP Call Control Protocol Rel-20 read
TS 24.247 vk00 IMS Messaging Protocol Specification Rel-20 read
TS 24.407 v830 OIP and OIR Simulation Services Protocol Rel-8 read
TS 24.428 v720 Common Basic Communication Procedures Rel-7 read
TS 24.508 v820 TIP and TIR Service Protocol Description Rel-8 read
TS 24.524 vj00 Hosted Enterprise Services Architecture Rel-19 read
TS 24.528 v830 Common Basic Communication Procedures for IMS Services Rel-8 read
TS 24.628 vj00 Common Basic Communication Procedures in IMS Rel-19 read
TS 24.819 v700 IMS Services via Fixed Broadband Access Rel-7 read
TS 24.880 v820 Media Server Control Protocol Study for IMS Rel-8 read
TR 24.930 vj00 IMS Session Setup Signalling Flows Rel-19 read
TS 26.114 vk11 IMS Multimedia Telephony Client Rel-20 read
TS 26.223 vj00 IMS Telepresence Client Specification Rel-19 read
TS 26.854 vj10 Haptics Enhanced Media Streaming and Communication Rel-19 read
TR 26.919 vj00 Study on 5G Conversational Media Handling Rel-19 read
TR 26.923 vj00 Study on IMS-based Telepresence Media Handling Rel-19 read
TR 26.948 vj00 Video enhancements for 3GPP Multimedia Services Rel-19 read
TS 28.702 vj00 Core Network NRM IRP Information Service Rel-19 read
TS 28.705 vj00 IMS NRM IRP Information Service Rel-19 read
TS 29.162 vj00 IMS-IP Network Interworking Rel-19 read
TS 29.163 vj00 Interworking between 3GPP IM CN and CS networks Rel-19 read
TS 29.165 vk00 Inter-IMS Network-to-Network Interface (II-NNI) Rel-20 read
TS 29.235 vj00 SIP-I CS Core Network Interworking Rel-19 read
TS 29.292 vj00 IMS Centralized Services (ICS) Interworking Rel-19 read
TS 29.333 vj00 MRFC-MRFP Mp Interface Protocol Rel-19 read
TS 29.421 v810 IMS Interworking with External IP Networks Rel-8 read
TR 29.949 vj00 VoLTE IMS Roaming Architecture & Procedures Rel-19 read
TS 32.102 vj00 Telecom Management Physical Architecture Framework Rel-19 read
TS 32.260 vk10 IMS Charging Management Rel-20 read
TS 32.272 vj00 Charging for Push-to-Talk over Cellular (PoC) Rel-19 read
TS 32.281 vj00 Announcement Service for Online Charging Rel-19 read
TS 32.632 vb00 Core Network Resources NRM Rel-11 read
TS 32.732 vb00 IMS Network Resource Model Information Service Rel-11 read
TS 33.127 vj80 Lawful Interception Architecture Rel-19 read