The CAMEL Application Part (CAP) API Exposure Function is a communication engine that enables the access and control of CAMEL services by external applications.
The most common CAMEL (Customized Applications for Mobile networks Enhanced Logic) services include call control, charging, short message service (SMS), and location-based services. These services enable mobile operators to offer value-added functionalities such as real-time call handling, prepaid or postpaid billing, and personalized SMS features. Call control services allow for managing call setup, termination, and routing, while charging services handle real-time billing for voice and data usage. SMS services enable delivery reports, messaging, and premium SMS features, while location-based services help track subscribers for applications like geofencing or location-based advertising. CAMEL services are integral to providing enhanced mobile experiences and monetizing telecom services.
Here are some examples of common CAMEL (Customized Applications for Mobile networks Enhanced Logic) services:
These examples illustrate how CAMEL services provide advanced control over call routing, billing, messaging, and location-based functionalities within mobile networks.
One of the benefits of implementing IN services with CAMEL is that it allows service providers to create and deploy new services independently of the underlying network infrastructure. CAMEL enables service logic to be executed on an application server, rather than on the network switches, which reduces the complexity and cost of service development and maintenance. CAMEL also supports interoperability between different networks and protocols, such as GSM, UMTS, and SIP, by providing a common interface for service invocation and control. CAMEL can be used to implement various IN services, such as prepaid calling, number portability, call screening, and location-based services.
Standalone mode
MNO (Mobile Network Operator) would most typically expose APIs to MVNOs (Mobile Virtual Network Operator) to enable better integration and interoperability between their services. By exposing APIs, MNO can allow MVNO to access its network resources, such as billing, authentication, provisioning, and customer care. This can benefit both parties by reducing operational costs, improving customer satisfaction, and creating new revenue streams. For example, MVNO can offer customized plans and features to its subscribers using MNO’s network infrastructure, while MNO can leverage MVNO’s market reach and brand loyalty.
3rd Party API Exposure mode
| Software packaging | Docker image, RPM or DEB package. |
| SCTP | RFC2960 RFC3309 |
| M3UA | RFC3332 |
| SCCP | ITU-T Q.711 through Q.714 Connectionless Class 0 & 1 |
| TCAP | ITU-T Q.700 through Q.707, Q.781, Q.782, Q.791 |
| CAP | GSM 09.78 (ETSI TS101 046 - V5.6.0) CAMEL phase 1 GSM 09.78 (ETSI TS101 046 - V6.3.0) CAMEL phase 2 GSM 09.78 (ETSI TS129 078 - V4.6.0) CAMEL phase 3 3GPP TS 29.078 V7.3.0 R7 3GPP TS 29.278 V7.0.0 R7 (IMS) CAMEL phase 4 |
| Application interface | HTTP/1.1 HTTPS HTTP2 |
