Description
CAMEL (Customised Applications for Mobile network Enhanced Logic) is a 3GPP standard that extends Intelligent Network (IN) concepts to mobile networks, specifically GSM, GPRS, UMTS, and IMS. It provides a standardized mechanism for network operators to offer operator-specific, value-added services to subscribers, even when they are roaming outside their home network. The core principle is the separation of service logic from the basic call and session control functions of the network switches (MSC/VLR, SGSN, GGSN). This separation allows for the centralized creation, deployment, and management of complex services without requiring upgrades to every network node.
The CAMEL architecture is built around the interaction between network entities using the CAMEL Application Part (CAP) protocol, which is an extension of SS7/SIGTRAN. Key functional components include the CAMEL Service Environment (CSE) or Service Control Function (SCF), which hosts the service logic, and the Service Switching Function (SSF) embedded in network switches like the MSC/VLR or GMSC. The SSF detects trigger points (Detection Points) during call or session processing and suspends the local processing to request instructions from the remote SCF via CAP. The SCF then returns instructions (e.g., connect, continue, play announcement, apply charging) to the SSF, which executes them, enabling real-time, event-driven service control.
CAMEL operates through a series of phases and trigger detection points defined for different types of calls and sessions, such as Mobile Originated, Mobile Terminated, and Forwarded calls. It supports multiple phases like call setup, alerting, answer, and disconnect. For packet-switched domains, CAMEL Phase 3 and later introduced control for GPRS sessions and SMS, allowing for services like prepaid data charging. The protocol defines a rich set of operations and parameters for charging control, event notification, and call manipulation, making it a comprehensive toolkit for IN-style services.
Its role in the network is foundational for monetization and service differentiation. It is the underlying technology enabling real-time prepaid billing, which is critical for many markets. It also supports advanced call control services like Freephone, Premium Rate, Virtual Private Networks (VPN), and location-based services. By providing a standardized interface, CAMEL ensures interoperability between equipment from different vendors and between different network operators, which is essential for seamless roaming and consistent service delivery.
Purpose & Motivation
CAMEL was created to address the limitations of traditional, switch-based service provisioning in mobile networks. Before CAMEL, advanced telephony services were implemented directly within the software of Mobile Switching Centers (MSCs), making them vendor-specific, difficult to create, and costly to deploy uniformly across a network. This approach also failed completely for roaming subscribers, as the visited network's MSCs had no knowledge of the home operator's custom services. There was a clear need for a standardized, network-wide platform to develop and execute custom service logic independently of the underlying switch infrastructure.
The primary problem CAMEL solves is enabling real-time, operator-specific service control for subscribers regardless of their location. This was driven by the commercial need for prepaid services, which require immediate credit checking and deduction during a call or data session. Without a system like CAMEL, implementing prepaid across a multi-vendor network and for roaming users was nearly impossible. CAMEL provided the architectural framework and protocol (CAP) to separate service logic (hosted in a centralized SCF) from call switching functions, allowing for centralized service creation and consistent execution at home and abroad.
Historically, CAMEL built upon fixed-line Intelligent Network (IN) standards like ITU-T's CS-1 but adapted them for the unique requirements of mobile networks, such as mobility management, handover, and roaming. Its introduction in 3GPP Release 99 (CAMEL Phase 3) marked a significant evolution, extending support to the packet-switched domain (GPRS) and SMS, thereby future-proofing the standard for data services. CAMEL addressed the limitations of previous proprietary IN solutions by creating a uniform, 3GPP-specified interface, fostering interoperability and accelerating the deployment of advanced revenue-generating services globally.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (6 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 17, the CAMEL function was updated to integrate the Packet Data Network Gateway (PGW) within the logical ubiquitous charging architecture using a service-based interface. This introduction was followed by its subsequent removal from the same architecture and interface, indicating a revision of the charging framework's components.
In Release 19, the primary update for CAMEL was the introduction of support for multiplexing multiple Diameter Credit-Control (DC) applications over a single SCTP connection, which was detailed across several service and protocol updates. This enhancement optimizes connection resource utilization within the logical architecture. The release also included a specific update to the CAPIF Logical Charging Architecture, aligning with broader framework and service enabler improvements.
- Support of multiplexing multiple DC applications over single SCTP connection TS 23.228CR1511
- Updates to support multiplexing multiple DC applications over single SCTP connection TS 23.228CR1552
- Service updates to support multiplexing multiple DC applications over single SCTP connection TS 23.228CR1586
- Rel-19 CR 32.240 CAPIF Logical Charging Architecture TS 32.240CR0511
Explore further
Broader topics and technologies where CAMEL plays a role.
Defining Specifications
3GPP specifications that define or reference CAMEL, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj00 | 3GPP Technical Terms and Definitions | Rel-19 |
| TR 21.978 v1300 | CAMEL Control of VoIP Services Feasibility Study | Rel-4 |
| TS 22.038 vj00 | USIM Application Toolkit (USAT) Stage 1 | Rel-19 |
| TS 22.105 vj00 | Telecommunication Services Framework | Rel-19 |
| TS 22.121 v1400 | Virtual Home Environment Requirements | Rel-5 |
| TS 22.127 v1900 | Open Service Access (OSA) Requirements | Rel-9 |
| TS 22.228 vj00 | IP Multimedia Service Requirements | Rel-19 |
| TS 23.031 vj00 | Fraud Information Gathering System (FIGS) - Stage 2 | Rel-19 |
| TS 23.078 vj00 | CAMEL Phase 4 Stage 2 Specification | Rel-19 |
| TS 23.127 v1600 | Virtual Home Environment Stage 2 Specification | Rel-6 |
| TS 23.141 vj00 | Presence Service Stage 2 Architecture | Rel-19 |
| TS 23.171 v1300 | LCS Stage 2 Specification for UMTS | Rel-4 |
| TS 23.172 vj00 | Service Change and UDI Fallback (SCUDIF) | Rel-19 |
| TS 23.218 vj00 | IMS Call Model Specification | Rel-19 |
| TS 23.226 vj00 | Global Text Telephony (GTT) Stage 2 | Rel-19 |
| TS 23.228 vj50 | IMS Stage-2 Service Description | Rel-19 |
| TS 23.271 vj00 | LCS Stage 2 Specification | Rel-19 |
| TS 23.278 vj00 | CAMEL for IMS Stage 2 Specification | Rel-19 |
| TS 23.417 v1700 | IMS Core Component for NGN Architecture | Rel-7 |
| TS 23.517 v1800 | IMS Core Component for NGN Architecture | Rel-8 |
| TS 23.806 v1700 | Voice Call Continuity between CS and IMS | Rel-7 |
| TR 23.923 v1300 | Mobile IP+ Feasibility Study for UMTS/GPRS | Rel-4 |
| TS 24.206 v1700 | Voice Call Continuity Between CS and IMS | Rel-7 |
| TS 24.259 vj00 | Personal Network Management (PNM) Protocol Details | Rel-19 |
| TS 24.292 vj00 | IMS Centralized Services (ICS) Protocol | Rel-19 |
| TS 25.305 vj00 | UTRAN UE Positioning Stage 2 | Rel-19 |
| TS 29.198 v1900 | OSA API Overview Specification | Rel-9 |
| TS 32.102 vj00 | Telecom Management Physical Architecture Framework | Rel-19 |
| TS 32.240 vj40 | Charging Management Architecture & Principles | Rel-19 |
| TS 32.250 vj00 | Circuit Switched Offline Charging | Rel-19 |
| TS 32.251 vj00 | PS Domain Charging Management | Rel-19 |
| TS 32.272 vj00 | Charging for Push-to-Talk over Cellular (PoC) | Rel-19 |
| TS 32.276 vj00 | VCS Online Charging from Proxy Function | Rel-19 |
| TS 32.280 vj00 | Advice of Charge (AoC) Framework | Rel-19 |
| TS 32.281 vj00 | Announcement Service for Online Charging | Rel-19 |
| TS 32.293 vj00 | Proxy Function in Domestic Service Provider | Rel-19 |
| TS 32.296 vj00 | Online Charging System (OCS) Architecture | Rel-19 |
| TS 32.297 vj00 | Charging Data Record File Transfer | Rel-19 |
| TS 32.408 vj00 | UMTS/GSM Performance Management Measurements | Rel-19 |
| TS 32.808 v1800 | Common User Profile Storage Framework | Rel-8 |
| TS 32.850 ve00 | IMS Charging Correlation Methods Study | Rel-14 |