Service Switching Function

Description

The Service Switching Function (SSF) is a fundamental component of the Intelligent Network (IN) architecture adopted and adapted within 3GPP systems for circuit-switched (CS) domain services. It is a functional entity typically co-located with and integrated into the Mobile Switching Center (MSC) or Gateway MSC (GMSC). The primary role of the SSF is to act as the intermediary or 'switch' between the basic call and connection control functions of the MSC and the advanced service logic hosted in a separate entity called the Service Control Function (SCF), which often resides in a Service Control Point (SCP). The SSF monitors call events and states within the MSC against a set of configured detection points (DPs).

How it works involves a continuous dialogue based on the IN Application Protocol (INAP). When a call setup or mid-call event (like a called party answering or a DTMF digit being pressed) matches a configured DP in the SSF, the SSF triggers and suspends the basic call processing. It then formulates an INAP message (e.g., an InitialDP operation) containing details about the call and the triggering event, and sends this query to the SCF. The SCF, which contains the service logic (e.g., for a prepaid service), processes the query, makes a decision (e.g., check balance, apply routing number), and sends back an INAP response to the SSF with instructions. These instructions, known as 'call control commands,' can direct the SSF to connect the call, play an announcement, collect digits, apply charging, or release the call. The SSF faithfully executes these commands within the MSC's switch fabric and then resumes basic call processing, potentially triggering further detection points later in the call.

Architecturally, the SSF is a key part of the IN conceptual model's physical plane. Its key components include the Call Control Function (CCF) for basic call handling, the Service Switching Function itself for IN interaction, and a specialized resource function (often part of a separate SRF) for playing announcements or collecting digits as commanded by the SCF. In 3GPP, the SSF's integration is specified in detail, defining how IN protocols like INAP (based on CAMEL for mobility) interface with the MSC's internal call model. The SSF's role is crucial for decoupling service intelligence from switching hardware, allowing operators to introduce and modify services centrally on SCPs without needing to upgrade every MSC in the network. It enables the realization of a vast array of standardized and operator-specific CS services.

Purpose & Motivation

The SSF was created to solve the fundamental problem of monolithic, inflexible telephone switches. In traditional telephony networks, new services (like call forwarding or toll-free numbers) required software upgrades to every switch in the network, a process that was slow, costly, and hindered innovation. The Intelligent Network concept, and by extension the SSF, was developed to separate service logic from switching functionality. The SSF's purpose is to embed 'service switching' intelligence directly into the switch (MSC) so it can recognize when a call requires advanced processing and delegate that processing to a centralized, powerful computer (the SCP).

This architecture addressed significant limitations. It allowed for the rapid creation and deployment of new value-added services from a central point. Operators could now implement services like prepaid cellular, virtual private networks (VPN) for businesses, or number translation services across their entire network by updating the service logic on their SCPs, while the MSCs, equipped with the SSF, simply followed commands. This dramatically reduced time-to-market for new services and enabled personalized offerings. The historical context is rooted in the fixed-line IN standards (like ITU-T's CS-1/CS-2), which 3GPP adapted for the mobile environment, primarily through the CAMEL protocol suite.

In 3GPP systems, the SSF solved the critical problem of providing advanced, network-controlled services to roaming subscribers. A subscriber's home network service logic (on the HPMN's SCP) could control calls for that subscriber even when they were roaming in a visited network, by having the visited MSC's SSF interact with the home SCP via CAMEL. This enabled global services like prepaid roaming, which was a major business and technical challenge before IN principles were applied to mobile networks. The SSF, therefore, was not just a convenience but an essential enabler for commercial mobility services beyond basic voice calling.

Key Features

• Integrated into the MSC/GMSC to interface basic call control with IN service logic
• Monitors call events and triggers based on configured Detection Points (DPs)
• Communicates with the Service Control Function (SCF) using the IN Application Protocol (INAP/CAMEL)
• Executes call control commands (connect, release, play announcement, collect digits) from the SCF
• Enables centralized service creation and deployment independent of switch hardware
• Fundamental for implementing standardized circuit-switched services like prepaid, freephone, and VPN

Evolution Across Releases

Defining Specifications