CAMEL Application Part: Difference between revisions

Revision as of 09:31, 14 August 2007

Latest revision as of 05:38, 17 April 2025

(29 intermediate revisions by 23 users not shown)

Line 1:

{{Short description|Signalling protocol used in the Intelligent Network architecture}}

{{Expand|date=January 2007}}

{{SS7stack}}

The '''[[Customised Applications for Mobile networks Enhanced Logic|CAMEL]] Application Part''' ('''CAP''') is a signalling protocol used in the [[intelligent network|Intelligent Network]] (IN)]] architecture. CAP is a [[remoteRemote operationsOperations serviceService elementElement protocol|Remote Operations Service Element]] (ROSE)]] user protocol, and as such is layered on top of the [[Transaction Capabilities Application Part]] (TCAP) of the [[Signaling System 7|SS#7]] protocol suite. CAP is based on a subset of the [[European Telecommunications Standards Institute|ETSI]] Core and allows for the implementation of carrier-grade, value added services such as unified messaging, prepaid, fraud control and Freephone in both the [[GSM]] voice and [[GPRS]] data networks. [[Customized Application of Mobile Enhanced Logic|CAMEL]] is a means of adding intelligent applications to mobile (rather than fixed) networks. It builds upon established practices in the fixed line telephony business that are generally classed under the heading of (Intelligent Network Application Part) or [[INAP]] CS-2 protocol.<ref name="29.078">[http://www.3gpp.org/ftp/Specs/html-info/29078.htm 3GPP TS 29.078] - The 3GPP specification for CAP</ref>

<br clear=all>

== Protocol specification ==

The CAMEL Application Part (CAP) portable, software provides mechanisms to support operator services beyond the standard GSM services for subscribers roaming within or outside the Home [[PLMN]] (HPLMN). The CAP product extends the IN framework to the GSM/3G networks for implementing IN-based services within GSM/3G networks.

As with CAMEL, CAP has been defined in 4 phases, each of which has an accompanying specification that builds upon the previous phase. Each CAP phase provides the message set and procedures needed to support the corresponding CAMEL phase requirements, as defined in [http://www.3gpp.org/ftp/Specs/html-info/22078.htm 3GPP TS 22.078] (service aspects) and [http://www.3gpp.org/ftp/Specs/html-info/23078.htm 3GPP TS 23.078] (technical realization).

CAMEL is used when the subscriber is roaming between networks, allowing the home network to monitor and control calls made by the subscriber. CAMEL provides services such as prepaid roaming services, fraud control, special numbers (e.g., 123 for voicemail that works everywhere) and closed user groups (e.g., office extension numbers that work everywhere).

The definition of the protocol may be considered to be split into 3 sections:

* the definition of the Single Association Control Function (SACF)/Multiple Association Control Function (MACF) rules for the protocol, defined within the prose of the specification;

* the definition of the operations transferred between entities, defined using [[Abstract Syntax Notation One]] (ASN.1);

* the definition of the actions taken at each entity, defined by means of state transition diagrams.

As with CAMEL, CAP has been defined in 4four phases, each of which has an accompanying specification that builds upon the previous phase. Each CAP phase provides the message set and procedures needed to support the corresponding CAMEL phase requirements, as defined in [http://www.3gpp.org/ftp/Specs/html-info/22078.htm 3GPP TS 22.078] (service aspects) and [http://www.3gpp.org/ftp/Specs/html-info/23078.htm 3GPP TS 23.078] (technical realization).

The definition of the protocol may be considered to be split into 3three sections:

== References ==

* the definition of the Single Association Control Function (SACF)/Multiple Association Control Function (MACF) rules for the protocol, defined within the prose of the specification;

<div class="references-small" style="-moz-column-count:2; column-count:2;">

* the definition of the operations transferred between entities, defined using [[Abstract Syntax Notation One]] (ASN.1);

<references/>

* the definition of the actions taken at each entity, defined by means ofthe state transition diagrams.

</div>

== References ==

{{Reflist}}

[[Category:Signaling System 7]]

[[Category:Application layer protocols]]

[[Category:Year of introduction missing]]

==External links==

* [http://www.ss7.net/ss7-forum/ SS7 including CAMEL discussion forums]