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.
Key Features
- Real-time service control for call and session handling
- Support for prepaid/postpaid charging via standardized charging operations
- Roaming transparency for home operator services
- Protocol (CAP) for communication between Service Control and Switching Functions
- Trigger Detection Points for event-driven logic invocation
- Support for circuit-switched (voice), packet-switched (GPRS), and IMS services
Evolution Across Releases
Introduced CAMEL Phase 3, which was a major expansion. It added support for the GPRS packet-switched domain, enabling prepaid data services and control of GPRS sessions and SMS. It also enhanced circuit-switched control with new detection points and capabilities for optimal routing and in-call modifications.
Enhanced CAMEL support for the evolving core network. Introduced capabilities for control in the evolving All-IP core network architecture, including interactions with the IP Multimedia Subsystem (IMS) foundations and support for Mobility Management events.
Integrated CAMEL with the initial IMS architecture. Defined how CAMEL interacts with IMS Service Control (ISC) interface, enabling CAMEL-based service control for IMS multimedia sessions and laying groundwork for combinational services.
Further refined IMS interworking and introduced CAMEL Phase 4. Added support for IP Multimedia Subsystem (IMS) sessions, enhanced messaging services, and introduced new charging scenarios and event notifications for more complex service logic.
Focused on optimizations and enhancements for existing domains. Improved efficiency of CAP dialogues, enhanced support for video telephony services, and introduced updates for better charging correlation and error handling.
Aligned CAMEL with the new EPS (LTE/SAE) architecture. Defined the role of CAMEL in the Evolved Packet System, particularly for interworking scenarios between EPS and legacy CS/GPRS domains for service continuity and charging.
Enhanced support for IMS Service Centralization and Continuity (SCC). Defined CAMEL procedures to support voice call continuity between CS and IMS domains, ensuring service logic could be maintained during domain transfers.
Introduced Machine-Type Communication (MTC) enhancements. Added CAMEL features to support triggering and charging for early IoT/MTC services, including low mobility and group-based service scenarios.
Continued evolution for MTC and network efficiency. Provided further optimizations for MTC device triggering via SMS and enhanced CAP procedures for reduced signaling load in large-scale service deployments.
Focus on network simplification and Proximity Services (ProSe). Updated CAMEL to support new service scenarios introduced with Device-to-Device communication and continued refinements for efficient service execution.
Enhanced support for Mission Critical Communication and Network Functions Virtualization (NFV). Defined CAMEL interactions for critical communication services and considered impacts of virtualized network function deployments on CAMEL architecture.
Extended support for new service enablers and architecture evolution. Updated CAMEL to work with new service capabilities defined in this release and ensured compatibility with ongoing core network evolution.
Defined CAMEL interworking with 5G Core network for service continuity. Specified how CAMEL-based services from legacy networks interact with the new 5G Core (5GC) Service Based Architecture, particularly for roaming and inter-system handovers.
Enhanced integration for 5G Phase 2, including support for network slicing interworking. Provided mechanisms for CAMEL to be aware of and interact with network slice selection and charging aspects in a 5G context.
Further evolution for 5G-Advanced scenarios and expanded IoT. Updated CAMEL support for enhanced Massive IoT and critical IoT use cases, ensuring legacy IN services can be delivered in new 5G deployment models.
Continued alignment with 5G-Advanced features and network automation. Focused on ensuring CAMEL service logic can cooperate with AI/ML-based network operations and more advanced edge computing architectures.
Ongoing maintenance and evolution for future network capabilities. Ensured CAMEL specifications remain viable and integrated with the latest 3GPP features, supporting legacy service migration paths in next-generation networks.
Defining Specifications
| Specification | Title |
|---|---|
| TS 21.905 | 3GPP TS 21.905 |
| TS 21.978 | 3GPP TS 21.978 |
| TS 22.038 | 3GPP TS 22.038 |
| TS 22.105 | 3GPP TS 22.105 |
| TS 22.121 | 3GPP TS 22.121 |
| TS 22.127 | 3GPP TS 22.127 |
| TS 22.228 | 3GPP TS 22.228 |
| TS 23.031 | 3GPP TS 23.031 |
| TS 23.078 | 3GPP TS 23.078 |
| TS 23.127 | 3GPP TS 23.127 |
| TS 23.141 | 3GPP TS 23.141 |
| TS 23.171 | 3GPP TS 23.171 |
| TS 23.172 | 3GPP TS 23.172 |
| TS 23.218 | 3GPP TS 23.218 |
| TS 23.226 | 3GPP TS 23.226 |
| TS 23.228 | 3GPP TS 23.228 |
| TS 23.271 | 3GPP TS 23.271 |
| TS 23.278 | 3GPP TS 23.278 |
| TS 23.417 | 3GPP TS 23.417 |
| TS 23.517 | 3GPP TS 23.517 |
| TS 23.806 | 3GPP TS 23.806 |
| TS 23.923 | 3GPP TS 23.923 |
| TS 24.206 | 3GPP TS 24.206 |
| TS 24.259 | 3GPP TS 24.259 |
| TS 24.292 | 3GPP TS 24.292 |
| TS 25.305 | 3GPP TS 25.305 |
| TS 29.198 | 3GPP TS 29.198 |
| TS 32.102 | 3GPP TR 32.102 |
| TS 32.240 | 3GPP TR 32.240 |
| TS 32.250 | 3GPP TR 32.250 |
| TS 32.251 | 3GPP TR 32.251 |
| TS 32.272 | 3GPP TR 32.272 |
| TS 32.276 | 3GPP TR 32.276 |
| TS 32.280 | 3GPP TR 32.280 |
| TS 32.281 | 3GPP TR 32.281 |
| TS 32.293 | 3GPP TR 32.293 |
| TS 32.296 | 3GPP TR 32.296 |
| TS 32.297 | 3GPP TR 32.297 |
| TS 32.408 | 3GPP TR 32.408 |
| TS 32.808 | 3GPP TR 32.808 |
| TS 32.850 | 3GPP TR 32.850 |