Mobile Terminating Roaming Forwarding

Description

Mobile Terminating Roaming Forwarding (MTRF) is a standardized 3GPP service designed to enhance call completion for roaming subscribers. It operates within the circuit-switched (CS) domain and is managed by the subscriber's Home Public Land Mobile Network (HPLMN). When a mobile-terminated call (an incoming call) is routed to a subscriber who is roaming in a Visited PLMN (VPLMN), and the VPLMN cannot successfully deliver the call (e.g., due to subscriber unreachable, network congestion, or service restrictions), the MTRF mechanism is invoked. The HPLMN, upon receiving a failure indication from the VPLMN, can forward the call to an alternative destination specified by the subscriber or network operator, such as a voicemail system, another telephone number, or an application server.

The architecture involves several core network nodes. The key entity is the Home Location Register (HLR) in the HPLMN, which stores the subscriber's MTRF service profile and the forwarding number. The Gateway MSC (GMSC) in the HPLMN is responsible for querying the HLR (via MAP Send Routing Information) to obtain routing instructions for the incoming call. When the call is routed to the VPLMN's Visited MSC (VMSC), and the VMSC determines it cannot terminate the call to the subscriber, it sends a MAP Provide Roaming Number failure or similar indication back to the HPLMN. This triggers the GMSC or a dedicated service control node to apply the MTRF logic, re-routing the call based on the subscriber's profile.

How MTRF works involves a specific signaling flow. Initially, the GMSC receives the incoming call and queries the HLR. The HLR provides a Mobile Station Roaming Number (MSRN) to route the call to the VMSC. The VMSC attempts to page the subscriber. If the paging fails (e.g., no response, subscriber in a non-covered area, or busy with another circuit-switched service), the VMSC sends a failure report to the GMSC. The GMSC, now aware of the termination failure, initiates a second query to the HLR specifically for MTRF instructions. The HLR then returns the forwarded-to number (e.g., the voicemail access number). The GMSC subsequently routes the call to this number, completing the call forwarding procedure transparently to the calling party.

MTRF's role is to improve service reliability and user experience for roaming subscribers, ensuring business continuity and customer satisfaction. It is a network-based service, meaning it does not require support on the User Equipment (UE). The feature is particularly valuable in scenarios with patchy international roaming agreements or technical limitations in certain visited networks. It complements other call completion services like Call Forwarding on Not Reachable (CFNRc) but is specifically tailored for the roaming context where the HPLMN maintains control over the forwarding decision.

Purpose & Motivation

MTRF was introduced to solve the problem of failed call deliveries to roaming subscribers, which was a significant pain point for both users and operators. Prior to MTRF, if a visited network could not terminate a call (due to reasons like temporary network outages, lack of paging response, or incompatibilities), the call would simply fail, leading to a poor customer experience and potential revenue loss for operators. Existing call forwarding services (like CFNRc) were typically anchored in the visited network, which might not always support them or apply them consistently for roamers.

The primary motivation was to give the home network operator greater control over the call completion process for their subscribers when they are abroad. This addresses limitations where the visited network's capabilities or policies might prevent successful call termination. By centralizing the forwarding logic in the HPLMN, MTRF ensures a consistent service experience regardless of the visited network's features. It also allows home operators to implement business rules, such as forwarding to a home-network voicemail system, which might be preferred for cost or service quality reasons.

Historically, MTRF was standardized in 3GPP Release 10 as part of ongoing enhancements to roaming services. Its creation was driven by operator demands for more robust and intelligent roaming mechanisms, especially with the growth of international travel. It filled a gap in the existing toolkit, providing a standardized, interoperable way to handle call delivery failures in a roaming scenario, thereby increasing overall network efficiency and subscriber satisfaction.