- This topic has 22 replies, 1 voice, and was last updated 2 years ago by Wallis Dudhnath.
17th October 2007 at 07:16 #49420AshokGuest
Can somebody just give a summary of the features supported by CAMEL Ph-1, 2 ,3 & 4 . Like CAMEL-2 would of course cover features fo CAMEL -1 + additional features. I Need to know the original features as in CAMEL -1 & then the additional features as offered in CAMEL-2, 3 & 4 .
It would be a great help24th October 2007 at 04:04 #49421MuckyGuest
Camel Phase 2 Feature,
o Online Charging Control
o Call Control
o Conditional Triggering
That’s I know…maybe somebody else could help?30th October 2007 at 16:38 #49422atifGuest
hi can you tell me the purpose of camel 3 and 428th November 2007 at 07:22 #49423Abhishek ChauhanGuest
The CAMEL Phase 3 & 4 have certain features, which were not available in CAP 1 & 2. The CAP 3 includes all featues of CAP1 and CAP2 plus additional features for Data charging. Other than this, there are certain other messages also, which were added in CAP 3, which could be useful from the services point of view.
CAP 4 includes some additional features like MT SMS triggereing. The main feature of CAP 4 is ICA (Initiate CAll Attempt), which was not there in old releases.
Through this feature, the SCF can initiate the dialougue on it’s own, without any triggering from the SSF.5th July 2015 at 12:01 #49424Wallis DudhnathGuest
CAMEL – Customised Application Enhanced Logic – has
an association with IN – Intelligent Networks.
As IN Services expanded with GSM there was an issue with Roaming.
The use-cases were not standardised and this meant IN Services in the
HPLMN could not be used in the VPLMN. The answer was to use the existing IN
protocols: CS-1 (or variants) and to update it so that HPLMN can be used in the
VLPMN. This led to CAMEL which is basically a Network feature based on CAP V2 (or later versions)
and MAP V3 (or 4, etc..). CAMEL also helps with interoperability. CSPs can interwork gsmSSF, gsmSCF,
gprsSSF, gsmSRF, IP, etc.. from different vendors. Traditional “lock-in” from IN systems is now
At the time of writing CAP V2 is well proven for Roaming PrePaid Voice (telephony) calls.
Data Traffic is now charged using Diameter (DCCA).
CAMEL as a standard that is no longer evolving. The last set of standards was done with
CAMEL Phase4 via 3GPP.
CAP V1: Proof of concept. Several messages were supported
CAP V2: Similar message set that INAP / CS-2 supports. Geared up for Mobility and allows calls to be “teared down” based
on rules set with the PrePaid application
CAP V3: MO-SMS and Volume Based GPRS Charging
CAP V4: Call Party Handling (add / remove callers – move_Legs)
Network-initiated call establishment (InitiateCallAttempt), Interaction with basic optimal routing, Alerting detection point
Mid-call detection point, Change of position detection point, Flexible warning tone and Tone injection and
Enhancement to call forwarding notification
With the rapid growth of the Internet, Web2.0/3.0, SIP, Diameter, etc.. it has reduced the role of CAMEL Phase 4 as a
Multimedia Standard for VHE / OSA (Virtual Home Environment).13th July 2016 at 13:21 #49425Prashant M HullattiGuest
Good14th July 2016 at 10:27 #49426Wallis DudhnathGuest
Please let me know if you need any further inputs for IN / CAMEL.
VBR/ Wallis Dudhnath29th October 2016 at 04:00 #49427Antoine EghoGuest
what is the use of CAPv3 for Data Charging when VPLMN SGSN will always contact HPLMN GGSN, which nowadays are connected to OCS thru Gy?29th October 2016 at 13:15 #49428Wallis DudhnathGuest
CAMEL Standards (Phase 1-4) were standardised well before Diameter (DCCA), Gy, Gx, Sy, Policy (PCRF), etc..
For online charging the basic functionality as now defined by IETF Diameter Credit Control Application (DCCA) is used. The basic structure follows a mechanism where the online client (CTF) requests resource allocation and reports credit control information to 3GPP OCS (Online Charging System).
CAP V3 can be used for MO-SMS Charging (CAP V4 supports MT-SMS).
VBR/ Wallis Dudhnath7th March 2017 at 06:08 #49429ASHEESH SHARMAGuest
PLESE UPDATE THE MOPRE INFORMATION ABOUT THE CAP 4.9th March 2017 at 14:38 #49430Wallis DudhnathGuest
Look at the following book from Wiley:
CAMEL: Intelligent Networks for the GSM, GPRS and UMTS Network.
It provides a very good overview of CAMEL – from Phase1 to Phase4.
CAMEL Phase4.0 was standardised so that it can work with IMS. Last major standardisation work that was done with CAMEL was during the early 2000s.
VBR/ Wallis Dudhnath15th March 2017 at 14:34 #49431Wallis DudhnathGuest
CAMEL Phase 4 Summary:-
– Interactions with Optimal Routing;
– Call Party Handling;
– DTMF Mid call procedure for Mobile Originated and Mobile Terminating calls;
– Inclusion of flexible tone injection;
– Provision of location information of called subscriber;
– Provide location information during ongoing call;
– CAMEL control over MT SMS;
– Notification of GPRS mobility management to CSE;
– Inclusion of ODB data in Any Time Modification;
– Enhancement of Any Time Interrogation and Provide Subscriber Information for PS Domain;
– Mobile Number Portability database interrogation;
– Criteria for the provision of location information during ongoing call;
– Enhanced Dialled Services;
– Enhancement to Establish Temporary Connection;
– CAMEL control of trunk originated calls.13th July 2017 at 11:38 #49432Nidhin KaladharanGuest
Can Real-Time Display Balance be achieved by CAP 4 capability?15th July 2017 at 09:40 #49433Wallis DudhnathGuest
Not many Markets have deployed CAMEL Phase 4.0. CAP V4 is the last major work that has been done with the CAMEL standard. You can link CAMEL with AOC type Services. For Realtime Display of Balance (before, during and after a session) it is better to use Diameter. It is geared up for MSCC bundles.
For Media/VoLTE/ViLTE/etc.., SIP/Diameter is now the way forward.
VBR/ Wallis Dudhnath4th May 2020 at 09:40 #72031ManuGuest
Can you confirm that the ICA can be use to knows the availability of one destination without alert on it (No ringing)?
Thanks by advance
- The forum ‘Telecom Design’ is closed to new topics and replies.