Resume Call Handling

Description

Resume Call Handling (RCH) is a circuit-switched supplementary service standardized in 3GPP that enables a subscriber to pause and later continue a voice call. During an active call, the served user can invoke RCH to place the call on hold at the network level and release the radio connection. The call context, including the connection to the other party, is maintained by the network. Subsequently, within a defined time limit, the user can originate a request to resume the suspended call. The network then re-establishes the connection to the original remote party, continuing the conversation from the point of suspension.

The service operation involves specific signaling between the UE and the core network, primarily the Mobile-services Switching Centre (MSC). When invoking suspension, the UE sends a FACILITY message containing a Resume Call Handling invoke component. The MSC acknowledges this and maintains the call leg toward the other party in a suspended state, often playing an announcement. The radio resources are released, and the UE may enter idle mode. To resume, the user initiates a call set-up procedure, indicating it is for RCH resumption via a specific parameter in the SETUP message. The MSC validates the request, correlates it with the suspended call context, and re-connects the parties.

Key architectural components include the HLR, which stores the subscriber's service profile indicating RCH subscription, and the MSC, which executes the service logic and maintains the suspended call state. The service includes timers to limit how long a call can remain suspended before being automatically cleared. RCH interacts with other supplementary services like Call Hold, but differs fundamentally as Call Hold keeps a radio connection active, while RCH releases it. This service provides a seamless user experience for managing interruptions without requiring the other party to redial.

Purpose & Motivation

RCH was created to address user needs for managing voice call interruptions in early GSM and UMTS circuit-switched networks. Before such features, if a user needed to interrupt a call (e.g., to answer another call, or due to entering an area with no coverage), the only options were to end the call or use basic Call Hold, which kept radio resources occupied. This was inefficient and limited user mobility and convenience.

The service solves the problem of call continuity in the face of temporary disruptions. It allows a user to intentionally suspend a call, freeing up the terminal and radio resources, and then reliably resume the same call later. This is particularly useful in scenarios like leaving a coverage area, switching devices, or needing to attend to a brief priority task. It enhances the basic telephony service by providing greater control and flexibility.

Historically, RCH was part of a suite of supplementary services defined in 3GPP Release 4 and beyond to enrich the basic telephony offering and compete with fixed-line features. It addressed limitations of previous approaches by integrating suspension/resumption logic directly into the network core (MSC), ensuring service reliability independent of the terminal's immediate radio condition. While its relevance has diminished with the rise of VoIP and rich communication services, it represented an important step in personalized network-based call control.

Key Features

• Allows suspension of an active circuit-switched call with network-based state retention
• Enables resumption of the same call from the same or a different UE (if subscribed)
• Releases radio resources during the suspension period
• Network-maintained timer limits suspension duration
• Requires subscription and support from the HLR and MSC
• Uses specific FACILITY and SETUP signaling for invocation and resumption

Evolution Across Releases

Defining Specifications