Vous êtes sur la page 1sur 26

INAP/CAMEL Overview

Proprietary and Confidential


Need of Intelligent Networks

Multi-vendor network of tremendously complex switching systems

Long development cycles and expensive switch software upgrades

Long and expensive process of network upgrade

Lack of ubiquity in terms of feature performance and availability

Proprietary and Confidential


What is Intelligent Network ?
An Intelligent Network is a telephone network architecture in which
the service logic handling of a call is located separately from the
switching facilities.

This allows services to be added or changed without having to redesign


switching equipment.

Historically, intelligence and switching functions were closely


integrated in the telephone exchange.

The Intelligent Network introduces the concept of separating these


two functions. The intelligence, or logic, to set up a call or to control a
service is separated from the switching.

Proprietary and Confidential


Advantages Of IN

Quick Development Time

Custom-made Services

Flexibility and adaptability

Cost-effectiveness

Standardized service logic

Modularity of network functions

Effective use of network resources

Repetitively using standard network functions to


create and implement new services
Proprietary and Confidential
Interfaces between different nodes

INAP

Proprietary and Confidential


IN Service Access
Subscribed Access –
This access is defined within the HLR profile of the subscriber.
The subscriber subscribes to CSI which is Camel Subscription Information.
When the subscriber makes a call, the HLR lookup happens where it is determined
whether the subscriber has CSI profile.
There are separate trigger points (or Detection Points) for Originating &
Terminating calls. For e.g. in case of a Originating call the trigger happens at
Detection Point 2.

Dialed Access –
This access is defined on dialing a particular B number e.g. 1802102.
When a subscriber (whether a CAMEL subscriber or otherwise) dials a particular
number for which a CAMEL trigger is defined, the IN Service Access is triggered.
This type of trigger is defined within the routing table of the SSP.
This could be used for services like Calling Card, Freephone, VPN, etc.

Proprietary and Confidential


Functional entities

Proprietary and Confidential


IN Protocols

Proprietary and Confidential


INAP - Intelligent Network Application
Protocol
The Intelligent Network Application Part (INAP) is a
signaling protocol used in the intelligent network
architecture.

It is part of the SS7 protocol suite, typically layered on top


of the TCAP protocol.

The ITU defines several "capability levels" for this protocol,


starting with Capability Set 1 (CS-1).
INAP I
S
U
TCAP P

SCCP

MTP

Proprietary and Confidential


Capability Set

•The ITU defines a Capability Set as the set of services and service features
supported in a given IN release.

• Capability Sets (CS) address requirements for:


–Service creation, management, and processing CS-3
(Q.1231)
–Network management and provisioning CS-2
(Q.1221)
–Services, Service Feature, and SIBs
CS-1
(Q.1211)

Proprietary and Confidential


Capability Set phase 1,2,3
Universal Mobile

B- ISDN CS-3
PSTN, ISDN CS-2
CS-1
•Mobile service •Fixed/mobile Networks
•Voice Services •Multimedia Services •IN/B-ISDN Integration
•INCM •CS-1 Extensions •IN/TMN Integration
•Basic Call Model •IN Service Creation •Special Resources
•IN Architecture •IN Management
•INAP •IN Intetworking

Proprietary and Confidential


CAMEL - Customized Applications for
Mobile Enhanced Logic

Extended form of INAP is Customized Applications for


Mobile Enhanced Logic.

CAMEL is an IN technology by the help of which value-


added services can be offered to the mobile subscribers who
are roaming.

Roaming in Home or Visiting PLMN.

Provided by the Home PLMN network operator

The utilized protocols are CAMEL Application Part (CAP)


and Mobile Application Part (MAP)

Proprietary and Confidential


CAMEL Phases

CAMEL P1 CAMEL P2 CAMEL P3


- Applicable to MO & MT - Charging Operations - GPRS Charging
calls - New call related DP Operations
- No Charging Announcements & tones - SCP-HLR Interface
Operations DTMF Reception - GPRS Prepaid
- No Announcements - MO-SMS Charging
- Limited Detection Operations
Points
Service examples Service examples Service examples
include Call Screening, include Prepaid, Free include GPRS Prepaid,
Call Forwarding & Call phone, Hunting, Multiple Subscriber
Routing Announcements & Profiles & Enhanced
Reverse Charging Prepaid

Commercial Use: 1998 Commercial Use: 2000 Commercial Use: 2001

Proprietary and Confidential


CAMEL architecture

CAMEL ROAMING IN GSM NETWORK

Proprietary and Confidential 14


Description

The home network represents the HPLMN of a CAMEL subscriber or a


CAMEL-enabled roamer.
i) At HPLMN, the HLR and the gsmSCF are two functional entities involved in CAMEL procedures.
The HLR stores CAMEL subscriber information (CSI) and transfers it to other entities that take part
in enabling CAMEL services.

ii) The gsmSSF functionality, which resides in the VPLMN or interrogating network, communicates
with gsmSCF by using the CAMEL application protocol (CAP)

The PLMN where the CAMEL subscriber is currently roaming is called


the visiting network, i.e., VPLMN.
i) The VPLMN handles all the services invoked by the roamers.

ii) The VLR stores CAMEL subscription information received from an HLR during the update location
procedure or at any other time as a result of changes in the roamer’s data and also provides the
roamer status if interrogated by other entities.

iii) The gsmSSF and gsmSCF communicate to each other by using the CAMEL application protocol.

Proprietary and Confidential 15


Cont…

The PLMN that interrogates the HPLMN for information to handle


mobile terminating call is termed the interrogating network (IPLMN).
i) The GMSC and the gsmSSF are the IPLMN entities, which interact with the HPLMN HLR and the
gsmSCF to get further instructions on how to handle the terminating call.

ii) The MAP protocol is used on the GMSC-HLR interface.

iii) The interface is used to exchange routing information, subscriber status, location information,
subscription information, and suppression of announcements. In addition, CAMEL-related
subscriber data that is passed to the IPLMN is sent over this interface.

Proprietary and Confidential 16


CAMEL functional architecture to
support GPRS

Proprietary and Confidential 17


CAMEL functional architecture to
support MO-SMS MT-SMS

Proprietary and Confidential 18


Basic Call State Model - BCSM

The BCSM is a kind of state transition diagram which


shows the different states a call can reach while it is
processed on the switch

It is a high level state machine

The BCSM is described using the following elements:

- Points in Call

- Detection points

- Transitions

- Events

Proprietary and Confidential


Points In Call - PIC
Calls progress through a series of states that correspond to
Points in Call (PICs).

The PICs provide a view of a state or an event in which


call processing logic within the MSC/VLR/SGSN may
initiate an appropriate action.

The service logic that is loaded in the network nodes to


carry out the call processing on encountering the
detection points is termed a trigger.

Proprietary and Confidential


Detection Points - DP
DP operate between PICs

The DP can be armed or disarmed. “Arming” a DP means that the gsmSSF


must notify the gsmSCF on encountering it. If the DP is not armed, the
processing node continues processing of a call on its own, without
involvement of the gsmSCF. The DPs can be armed statically or
dynamically.

The CAMEL specifications identify three different types of DP:-

Trigger detection point–request (TDP-R)

Event detection point–request (EDP-R)

Event detection point–notification (EDP-N)

Proprietary and Confidential


Trigger detection point–request (TDP-R): The DP is statically
armed. The processing is suspended when the TDP is encountered.

Event detection point–request (EDP-R): The DP is dynamically


armed within the context of a CAMEL-controlled relationship. The
processing is suspended on encountering the EDP. The gsmSSF then
processes the call according to the instructions from the gsmSCF.

Event detection point–notification (EDP-N): Like EDP-R, this DP is


also dynamically armed within the context of a CAMEL-controlled
relationship. However, the processing of the call continues without
suspension on encountering an EDP-N

Proprietary and Confidential 22


Messages in the CAMEL Call Flow
Init DP - This operation is sent by the SSF after detection of a TDP-R in the
BCSM to request the SCF for instructions to complete the call.

Request Report BCSM (RRBE) - This operation is used to request the SSF to
monitor for a call-related event (e.g., BCSM events such as busy or no-answer),
then send a notification back to the SCF when the event is detected.

Apply Charging (AC) - This operation is used for interacting from the SCF with
the SSF charging mechanisms. The ApplyChargingReport operation provides the
feedback from the SSF to the SCF.

Furnish Charging Information (FCI) - This operation is used to request the


SSF to generate, register a call record, or include some information in the default
call record. The registered call record is intended for offline charging of the call.
The FCI operation can be invoked multiple times.

Proprietary and Confidential


Messages in the CAMEL Call Flow
Cont…..

Continue - This operation requests that the SSF proceed with call processing
at the DP at which it previously suspended call processing to await SCF
instructions. The SSF continues call processing without substituting new data
from the SCF.

Event Report BCSM (ERB) - This operation is used to notify the SCF of a call
related event previously requested by the SCF in an RRBCSM Event operation.
The monitoring of more than one event can be requested with a
RequestReportBCSMEvent operation. Each requested event is reported in a
separate EventReportBCSM operation.

Proprietary and Confidential


Procedure for a roamer-originated call

Proprietary and Confidential 25


Thank You

Queries:

Arshe.alam@syniverse.com

Proprietary and Confidential

Vous aimerez peut-être aussi