CAMEL Application Part

Description

The CAMEL Application Part (CAP) is a Transaction Capabilities Application Part (TCAP) based protocol, defined within the 3GPP standards, that facilitates the communication between network elements involved in the CAMEL service architecture. CAMEL enables the provision of operator-specific, intelligent network (IN) services across home and visited networks, independent of vendor equipment. CAP operates over the SS7 (Signaling System No. 7) or SIGTRAN (Signaling Transport) signaling networks, utilizing the TCAP layer for connection-oriented and connectionless dialogue management. Its primary role is to carry service logic instructions and event notifications between the Service Switching Function (SSF), typically integrated within MSC (Mobile Switching Center) or SGSN (Serving GPRS Support Node), and the Service Control Point (SCP) or Online Charging System (OCS). This allows for real-time control of call and session handling based on subscriber profiles and service logic.

Architecturally, CAP defines a set of operations and associated parameters that model the detection points (DPs) in a call or session state model, such as the Basic Call State Model (BCSM). When a trigger condition (e.g., call setup, answer, disconnect) is met at a Detection Point (DP) in the SSF, the SSF suspends call processing and formulates a CAP operation, like InitialDP, to report the event to the SCP. The SCP, hosting the CAMEL service logic, then analyzes the request, applies business rules (e.g., checking prepaid balance, applying number translation), and returns CAP instructions, such as ApplyCharging, Connect, or Continue, to guide the SSF on how to proceed with the call or data session. This interaction enables complex, stateful service control without modifying the core switching equipment.

Key components in the CAP dialogue include the gsmSCF (GSM Service Control Function), which is the SCP implementing the CAMEL service logic; the gsmSSF (GSM Service Switching Function), integrated into the MSC or GMSC; and for packet-switched services, the gprsSSF within the SGSN. CAP messages are encoded using ASN.1 (Abstract Syntax Notation One) and follow specific procedures for different phases of a call or session, ensuring interoperability between different network elements and vendors. The protocol supports various phases like call setup, mid-call, and call release, allowing for services like prepaid charging, fraud control, custom routing, and VPN (Virtual Private Network) services. Its design ensures that service logic is centralized in the SCP, promoting rapid service deployment and consistent subscriber experience across network boundaries.

In modern networks, especially with the evolution to 3G, 4G LTE, and 5G, CAP has been adapted to work with IP-based signaling via SIGTRAN, ensuring continued support for legacy CAMEL services while integrating with IMS (IP Multimedia Subsystem) and VoLTE (Voice over LTE). For instance, in 4G/5G networks, CAP is used between the MME (Mobility Management Entity) or SMF (Session Management Function) acting as an SSF and the OCS for online charging, demonstrating its enduring role in real-time service control and charging.

Purpose & Motivation

CAP was created to address the limitations of traditional, switch-based service provisioning in GSM and UMTS networks, which were inflexible and required lengthy, vendor-specific development cycles for new services. Before CAMEL and CAP, advanced services like prepaid calling, freephone numbers, or virtual private networks were implemented using proprietary IN solutions that often lacked interoperability between different network operators or when subscribers roamed. This hindered the rapid rollout of competitive, value-added services. The CAMEL framework, with CAP as its signaling protocol, standardized the interface between the switching function and the service control logic, enabling operators to deploy intelligent network services consistently across multi-vendor environments and supporting seamless service delivery when subscribers were roaming in visited networks.

The primary problem CAP solves is enabling real-time, event-driven control of calls and sessions by external application servers. This is crucial for services like prepaid billing, where the network must check a subscriber's balance in real-time before allowing a call to proceed and then deduct credit during the call. Without CAP, such services would require deep integration into every switch, making them costly and slow to update. CAP provides a standardized, abstracted signaling method that allows service logic to reside in centralized SCPs or OCS platforms, separating service creation from network infrastructure. This separation accelerates service innovation, reduces operational costs, and ensures that subscribers experience the same services regardless of their location or the underlying network technology.

Historically, CAP was introduced in 3GPP Release 99 as part of the CAMEL Phase 3 specifications, building on earlier phases (CAMEL Phase 1 and 2 defined in GSM standards) to support more complex services and additional network elements like the GPRS network. It addressed the growing demand for sophisticated prepaid and data services as mobile usage expanded. Over subsequent releases, CAP evolved to support new network architectures, such as IMS and LTE, ensuring backward compatibility while extending its capabilities to handle IP-based sessions and interworking with Diameter-based charging systems. Its continued relevance underscores its effectiveness in solving the fundamental need for flexible, real-time service control in telecommunications.