Talk:Customised Applications for Mobile networks Enhanced Logic

From Wikipedia, the free encyclopedia

More details are available in http://www.c7.com/ss7/whitepapers/meskauskas_camel.pdf with the basic information on CAMEL information.

Contents

[edit] Phase 3 and 4

My understanding is that CAMEL ph3 was largely about adding SMS control support to the protocol (IDP for SMS, Continue SMS, Release SMS and so on). Phase 4, although I haven't looked hard at it, seems to be going in the direction of INAP CS2, with more advanced call control (initiate call attempt, merge call legs, and so on) - check out 3GPP Voice Call Continuity paper, which cites CAP ph4 as being a possible, but discounted, solution for VCC. Discounted, I would imagine, because CS2 never took off; little support in the switches.

[edit] =============

As per my understanding in the Camel 4, the call segment conception comes into picture. Before that the call segment conception was not there. So only two party call was possible.After the call segment conception, the multiparty call is possible now. That is the main improvemnet of INAP CS2 and CAMEL4 over INAP CS1 and CAMEL 3

[edit] Requested move

This page was moved from "Customised Applications for Mobile networks Enhanced Logic" on 30th Jan by Scully6x03, with move summary of "mis-spelling". I am proposing, and requesting, that it be moved back for 3 reasons:

  1. Customised is not a mis-spelling[sic] - check out -ise vs. -ize;
  2. The 3GPP recommendation uses "Customised", not "Customized";
  3. The original page used "Customised", and as per WP:MOS - "Follow the dialect of the first contributor".

I'll fix any links to the -ize version following the move. Carre 17:10, 15 May 2007 (UTC)

Move done - going to fix broken links now. Carre 21:02, 15 May 2007 (UTC)

[edit] IMEI in Camel phase 4 IDP

Camel phase 4 shall also report IMEI (Mobile Equipment ID) in IDP. This would enable handset specific services with CAMEL phase 4