Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Protocol

CAP

CAMEL Application Part

Protocol →

CAP is the CAMEL Application Part signaling protocol that connects network elements like the SSF to external platforms to enable real-time, intelligent service control for features such as advanced prepaid services.

Introduced
R96
Where
Services › IMS
Specifications
26 specs
Also in
Core Network
CAP Description Purpose What changed Family Neighbours Detected Changes Specifications

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.

What changed in its specifications

The latest release-to-release comparison of specifications that define CAP. Each summary describes the whole specification, not only this term.

TR 21.905Rel-17 → Rel-18

Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TR 21.905 →
TS 23.127Rel-4 → Rel-5

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 →

Technology family

Core signalling protocols · Core Network

  1. Phase 1 MAP
  2. Phase 2 ISUP
  3. R96 CAP
  4. R99 GTP-C, GTP-U, GTPv1-C
  5. Rel-4 BICC
  6. Rel-5 Diameter, SIP
  7. Rel-8 GTPv2-C
  8. Rel-14 PFCP
  9. Rel-15 HTTP/2 SBI

Also in this family (introduction release not pinned to a single defining specification): INAP, M2PA, SIGTRAN

  • CAP builds on INAP
    “CAP is based on a sub-set of the ETSI Core INAP CS-2” TS 29.078

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 sources

Documented changes in 6 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.

R96 introduced

Introduced in R96 (release dating of the term; no individual change cited).

R99 specification text

The CAMEL Application Part (CAP) for CAMEL phase 3 is specified for the first time in TS 29.078 v3g0, defined as a ROSE user protocol based on a subset of ETSI Core INAP CS-2.

  • “The present document specifies the CAMEL Application Part (CAP) supporting the third phase of the network feature Customized Applications for Mobile network Enhanced Logic.” TS 29.078 v3.16.0
  • “The CAMEL Application Part (CAP) is a ROS Element (ROSE) user protocol” TS 29.078 v3.16.0
Rel-4 specification text

CAP gained support for transport over IP in accordance with SIGTRAN in Rel-4, and the handling of E-parameters across distinct CAP dialogues/TDPs was removed from 23.078.

Rel-5 specification text

CAP was extended for Rel-5 to its fourth phase, with new compatibility mechanisms, an IMS-specific CAP spec (TS 29.278) with a new Application Context, and call segment association handling in CAP dialogues.

  • “The present document specifies the CAMEL Application Part (CAP) supporting the fourth phase of the network feature Customized Applications for Mobile network Enhanced Logic.” TS 29.078 v5.9.0
  • “A new Application Context has been created for IMS for Release 5.” TS 29.278 v5.4.0
  • “There is a single CAP dialogue between the CSA and the gsmSCF.” TS 23.078 v5.12.0
Rel-6 2 CRs

CAP V4 specification was updated for Rel-6 with Rel-6 operation and package definitions, and CRs corrected CAP behaviour for calls with multiple CAP dialogues and ACM usage for ETC and CTR.

  • Correction to CAP SCI for calls with multiple CAP dialogues TS 23.078CR737
  • Correction to usage of ACM for CAP ETC and CAP CTR TS 29.078CR383
  • “the present module IMPORTS Rel-6 versions of the CAP Operation Package definitions.” TS 29.078 v6.6.0
Rel-7 1 CR

CAP was extended for trunk originated services, with additions and clarifications to its operations, and handling of CAP Disconnect Leg at Collected_Info was specified.

  • “Additions to CAP for trunk originated services” TS 29.078 v7.6.0
  • Additions and clarifications to CAP for trunk originated services TS 29.078CR393
  • “If CAP Disconnect Leg (leg 2) is received at the initial detection point (Collected_Info), then the call is not routed to the destination” TS 23.078 v7.10.0

Defining Specifications

3GPP specifications that define or reference CAP, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TR 21.978 v300 CAMEL Control of VoIP Services Feasibility Study R99 read
TS 22.121 v531 Virtual Home Environment Service Requirements Rel-5 read
TS 23.127 v610 Virtual Home Environment Stage 2 Specification Rel-6 read
TS 23.141 vj00 Presence Service Stage 2 Architecture Rel-19 read
TS 23.171 v390 LCS Stage 2 for UMTS R99 read
TS 23.218 vj00 IMS Call Model Specification Rel-19 read
TS 23.226 vj00 Global Text Telephony (GTT) Stage 2 Rel-19 read
TS 23.228 vk10 IP Multimedia Core Network Subsystem Rel-20 read
TS 23.271 vj00 LCS Stage 2 Specification Rel-19 read
TS 23.278 vj00 CAMEL for IMS Stage 2 Specification Rel-19 read
TS 23.806 v700 Voice Call Continuity between CS and IMS Rel-7 read
TS 24.206 v750 Voice Call Continuity Between CS and IMS Rel-7 read
TS 24.259 vj00 Personal Network Management (PNM) Protocol Details Rel-19 read
TR 26.917 vj00 TV Service Enhancements over 3GPP Rel-19 read
TS 29.078 vj00 CAMEL Phase 4 CAP Specification Rel-19 read
TS 29.198 v340 OSA R99 API Stage 3 Specification R99 read
TS 29.278 vj00 CAMEL Application Part (CAP) for IMS Phase 4 Rel-19 read
TS 32.240 vk10 3GPP Charging Architecture and Principles Rel-20 read
TS 32.272 vj00 Charging for Push-to-Talk over Cellular (PoC) Rel-19 read
TS 32.276 vj00 VCS Online Charging from Proxy Function Rel-19 read
TS 32.293 vj00 Proxy Function in Domestic Service Provider Rel-19 read
TS 32.296 vj00 Online Charging System (OCS) Architecture Rel-19 read
TS 32.808 v800 Common Profile Storage Framework for User Data Rel-8 read
TS 38.291 vj30 Ambient IoT Physical Layer Rel-19 read
TS 38.769 vk00 Ambient IoT Solutions in NR Rel-20 read