Camel Agreement


In a normal and traditional scenario, where several operators want their subscribers to receive mobile phone services on the other networks (partner network), they must enter into a roaming agreement between themselves in order to achieve a smooth deployment of roaming services for their subscribers on the partner network. Since there are so many operators in the world and subscribers of any operator can switch to any operator in the world, every operator must enter into such an agreement with almost any other operator in the world. This process is a very long process and creates a network of agreements between all these operators. Beyond these roaming agreements, a prepaid subscriber is subject to the obligation to go through camel trial cases with each of the operators. Due to the many incompatibilities in the CAMEL/phases version that are executed with these operators, this can lead to a mesh. Camel HUB therefore offers a centralised approach to the provision of CAMEL roaming services through its presence in a network comprising agreements with other existing network operators. The network in which a CAMEL HUB is installed is called a host network, and the network that has agreements on the use of CAMEL HUB for the provision of services to their roamers is called a partner network. Networks using the services of the CAMEL HUB node are called client networks. Partner networks are customer networks, as they will use all CAMEL HUB services. Figure 1 shows a 100 system with camel network architecture The CAMEL Part (CAP) application is a signaling protocol used in the Intelligent Network (IN) architecture. CAP is a Remote Operations Service Element (ROSE) user protocol and is, as such, besieged on the SS#7 protocol suite on the Capabilities Application Part (TCAP) transaction. CAP is based on a subset of the ETSI core and enables the implementation of carrier value-added services, such as unified messaging, prepayment, fraud control and freephones, both on the GSM-voice and GPRS data network.

CAMEL is a way to add smart apps to mobile (not fixed) networks. It is based on established practices in the fixed telephony sector, generally classified under the title (Intelligent Network Application Partie) or INAP CS-2 protocol. [1] The functional blocks to manage the information flow from the Phase3 network to the Phase2 network are: MS of the Phase3 310 network, SSF/MSC of the Phase2 610 network, CAMEL HUB 112, SCF of the Home Phase3 612 network, called Subs Gateway Mobile Switching Center / Mobile Switching Center / Service Switching Function (GMSC / MSC / SSF) of the Phase3 614 network, HLR of the Subs ρhase3 314 network and VLR / MSC of this 616 network. . . .

Pin It