Description
The Multimedia Resource Function Controller (MRFC) is a critical signaling component within the IP Multimedia Subsystem (IMS) architecture. It functions as the controlling entity for the Multimedia Resource Function Processor (MRFP), with which it communicates using the H.248 (Megaco) protocol or its 3GPP profile, the Mp interface. The MRFC interprets service logic and SIP (Session Initiation Protocol) commands received from the Serving-Call Session Control Function (S-CSCF) via the Mr interface. Based on these commands, the MRFC instructs the MRFP to allocate, configure, and manage media processing resources. This includes initiating and controlling media streams, managing conference bridges, playing announcements, collecting tones (DTMF), and performing media transcoding and transrating.
Architecturally, the MRFC is part of the Media Resource Function (MRF), which is logically split into the controller (MRFC) and the processor (MRFP). This separation follows the control plane and user plane split principle, allowing for independent scaling and optimization. The MRFC contains the service logic and state for multimedia sessions, translating high-level service requests (e.g., 'add a participant to a conference') into specific, low-level commands for the MRFP to execute on the media streams. It manages the lifecycle of these resources, ensuring they are allocated when needed and released promptly after use to optimize network efficiency.
In operation, when an IMS application server or the S-CSCF determines a need for media processing—such as setting up a multiparty video call—it sends a SIP INVITE or other SIP method to the MRFC. The MRFC authenticates the request, selects an appropriate MRFP based on load and capability, and establishes an H.248 control association. It then sends H.248 commands to the MRFP to create contexts, add terminations (logical endpoints for media streams), and specify the required media processing functions (mixing, codec conversion). The MRFC remains in the signaling path, monitoring the session and dynamically modifying MRFP behavior in response to user actions or service logic, such as muting a participant or changing the video layout in a conference.
Purpose & Motivation
The MRFC was created to provide a standardized, scalable, and flexible control mechanism for multimedia resource processing within packet-switched networks, specifically the IMS. Prior to IMS and the MRF concept, advanced telephony services like conferencing or interactive voice response (IVR) were often implemented using proprietary, monolithic platforms that were tightly coupled to the circuit-switched network. These systems were difficult to integrate with IP-based services and limited innovation. The MRFC/MRFP separation addresses this by defining an open, protocol-based interface (H.248/Mp) between control and processing, enabling multivendor interoperability and independent evolution of signaling and media processing technologies.
Its creation was motivated by the need to support a wide array of rich, real-time multimedia services—beyond simple voice—over IP networks. Services like video conferencing, push-to-talk, multimedia announcements, and lawful interception for multimedia sessions require sophisticated, network-hosted media manipulation. The MRFC provides the intelligent control plane necessary to orchestrate these complex media functions on behalf of multiple applications and users, abstracting the complexity from both the service layer (Application Servers) and the core session control (CSCF). This allows service providers to rapidly deploy new multimedia features using a common, shared resource pool controlled by the MRFC.
What changed in its specifications
The latest release-to-release comparison of specifications that define MRFC. Each summary describes the whole specification, not only this term.
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 →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
- R99 OSA-SCS
- Rel-5 AS, BGCF, CSCF, I-CSCF, IM-MGW, IM-SSF, MGCF, MRFC, MRFP, P-CSCF, S-CSCF
- Rel-6 IBCF, IMS-ALG, TrGW
- Rel-7 E-CSCF, IMS-AGW
- Rel-8 MRB, SCC AS
- Rel-9 EATF
- Rel-10 ATCF, ATGW
- MRFC used together with MRFP
“Interprets information coming from an AS and S‑CSCF (e.g. session identifier) and control MRFP accordingly.” TS 23.002
- MRFC used together with AS
“In addition the Application Servers can also interact with the MRFC via the S-CSCF (ISC, Mr), directly via the Mr' interface and via the Cr interface in order to control Multimedia Resource Function processing” TS 23.218
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 sourcesDocumented changes in 13 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.
TS 24.229 in Rel-5 first specifies MRFC SIP behaviour: UA role, charging header handling, P-Asserted-Identity, and INVITE handling for tones/announcements, ad-hoc conferencing and transcoding.
- “The MRFC shall provide the UA role, with the exceptions and additional capabilities as described in subclause 5.8” TS 24.229 v5.26.0
- “The MRFC can receive INVITE requests to set up an ad-hoc conferencing session (e.g. Multiparty Call) or to add parties from the conference.” TS 24.229 v5.26.0
- “The MRFC may receive INVITE requests to set up transcoding between endpoints with incompatible codecs.” TS 24.229 v5.26.0
TS 24.147 first specifies the MRFC's conferencing role: it treats the MRFP as a mixer, acts as conference focus with the AS, and drives H.248 interactions to create and modify MRFP connections.
- “For the purpose of SIP based conferences, the MRFC shall regard the MRFP as a mixer, as described in RFC 4353 [8].” TS 24.147 v6.9.0
- “the conferencing AS/MRFC shall implement the role of a conference focus” TS 24.147 v6.9.0
- “The MRFC initiates a H.248 interaction to create an IMS connection point for UE#1 in MRFP” TS 24.147 v6.9.0
The MRFC gained new requirements: it must use a GRUU referring to itself in contact addresses and handle requests addressed to its valid GRUUs outside the original dialog.
- “The MRFC shall use a GRUU referring to itself (as specified in RFC 5627 [93]) when inserting a contact address” TS 24.229 v7.34.0
- “The MRFC shall handle requests addressed to its currently valid GRUUs when received outside of the dialog in which the GRUU was provided.” TS 24.229 v7.34.0
MRFC gained new requirements to request the MRFP to create messaging-conference resources, play or record multimedia with DTMF detection, and filter messages.
- “The MRFC shall request the MRFP to create resources for a messaging conference.” TS 23.333 v8.3.0
- “The MRFC may request DTMF detection while playing multimedia of synchronized audio and video.” TS 23.333 v8.3.0
- “The MRFC shall request the MRFP to start/stop message filtering.” TS 23.333 v8.3.0
The MRFC gained new requirements in TS 24.229: it can act as a transcoding server per RFC 4117, handles INVITEs for transcoding with a supplied codec, and supports media control procedures (subclause 10.3).
Compared with Rel-7: intermediate versions are not available, so this change may date from any release since Rel-7.
- “An AS may invoke transcoding at an MRFC by the use of RFC 4117 [166], if the MRFC supports acting as the transcoding server” TS 24.229 v9.31.0
- “When the MRFC receives an INVITE request for transcoding and a codec is supplied in SDP, the MRFC shall:” TS 24.229 v9.31.0
- “The MRFC shall also support the procedures and methods described in subclause 10.3 for media control.” TS 24.229 v9.31.0
MRFC gained ECN negotiation behaviour in SDP offer/answer, acting as an ECT endpoint and instructing the MRFP to apply ECN procedures, with ECN failure notification between MRFC and MRFP.
- “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 v10.5.0
- “When creating the SDP Offer the MRFC may initiate ECN negotiation (in accordance with 3GPP TS 26.114 [23]), indicating the capabilities of the MRFP.” TS 23.333 v10.5.0
- “When the MRFC receives a Notification indicating that an error has occurred it may trigger a new SDP offer to remove ECN.” TS 23.333 v10.5.0
MRFC gained MPS priority handling: it recognises priority sessions, sends Priority information to the MRFP, queues priority requests on congestion, and may support the RFC 6917 media server resource publish interface.
- “The MRFC shall recognise the call/session as having priority.” TS 23.333 v11.1.0
- “The MRFC shall send the Priority information for a context to the MRFP” TS 23.333 v11.1.0
- “The MRFC may support the media server resource publish interface as defined by RFC 6917 [192].” TS 24.229 v11.31.0
MRFC gained new requirements in Rel-12, including SDP codec parameter handling (ptime, maxptime) as offerer and answerer, and ICE and generic image attribute support over the Mp H.248 interface.
- “If the ptime parameter is included in the received SDP answer, the MRFC shall supply the parameter to the MRFP for the termination towards the answerer” TS 23.333 v12.12.0
- “In the local descriptor, the MRFC shall provide "a=ice-pwd", and "a=ice-ufrag" with wildcard sign "$" to request the allocation of a password” TS 29.333 v12.10.0
- “If the ptime parameter is included in the received SDP offer, the MRFC shall supply the parameter to the MRFP for the termination towards the offerer” TS 23.333 v12.12.0
MRFC procedures were added for SDP capability negotiation (reserving, updating and releasing MRFP resources per configuration) and for FECC and predefined ROI offer/answer handling, compared with the previous release.
- “On receipt of an SDP answer with SDPCapNeg, the MRFC shall request the MRFP to configure the resources for the selected configuration.” TS 23.333 v13.8.0
- “Before using SDP extensions for SDP capability negotiation as specified in IETF RFC 5939 [53] towards the MRFP, the MRFC shall perform the necessary checks” TS 23.333 v13.8.0
- “the MRFC shall determine based on the local policy and the ROI negotiation results on other call legs whether to accept this "FECC" offer.” TS 23.333 v13.8.0
MRFC procedures were extended in Rel-14 for simulcast format selection, compact concurrent codec capabilities signalling to the MRFP, RTCP CCM feedback handling, and charging header handling (fe-identifier).
- “The MRFC shall support separating simulcast formats through referencing separate RTP payload types for each simulcast format” TS 23.333 v14.5.0
- “the MRFC shall, when requesting the MRFP to configure resources, include the "CCM BASE" information element” TS 23.333 v14.5.0
- “When the MRFC receives a final response, the MRFC shall, based on local policy, include the stored "fe-identifier" header field parameter” TS 24.229 v14.21.0
Text describing the MRFC instructing the MRFP to apply ECN procedures and act as an ECT endpoint after a successful ECN SDP negotiation was removed in Rel-15.
- “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
MRFC gained Delay Budget Information (DBI) signalling behaviour: it handles SDP 3gpp-delay-budget offers/answers, and tells the MRFP to configure DBI resources and RTCP feedback, plus ECN handling.
- “the MRFC shall, when requesting the MRFP to configure resources, include the "DBI" information element” TS 23.333 v16.2.0
- “the MRFC shall include under each offered audio or video "m=" line the "a=rtcp-fb" attribute line with the "3gpp-delay-budget" parameter” TS 23.333 v16.2.0
MRFC/MRFP ICE support was updated to RFC 8445/8839, adding MRFC-requested and indicated Ta pacing values for connectivity checks and the a=ice-pacing attribute in the local descriptor.
- “This information element is present if MRFC requests a pacing value for connectivity checks (Ta timer value).” TS 23.333 v17.1.0
- “The MRFP shall compare the own desired Ta timer value with the Ta timer value provided by the MRFC and shall use the higher value” TS 23.333 v17.1.0
Defining Specifications
3GPP specifications that define or reference MRFC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| 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 |
| 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.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 |
| 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.962 vj00 | ITT4RT Operation and Usage Guidelines | 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.165 vk00 | Inter-IMS Network-to-Network Interface (II-NNI) | Rel-20 read |
| TS 29.278 vj00 | CAMEL Application Part (CAP) for IMS Phase 4 | Rel-19 read |
| TS 29.333 vj00 | MRFC-MRFP Mp Interface Protocol | Rel-19 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.240 vk10 | 3GPP Charging Architecture and Principles | Rel-20 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.422 vk30 | Trace, MDT and UE Measurement Control | Rel-20 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 |