CAMEL Feature1

DESCRIPTION
Prepared (also subject responsible if other)
1 ( 34 )
No
EAB/UG/BIF Richard Persson

Approved
173/19046-FAD 104 08 Uen

Checked
EAB/UG/BIF Mikael sterberg
Date
Rev
2002-04-26
PD2
Reference
Support of CAMEL
Abstract
The purpose of this document is to describe the function "Support of CAMEL"
from a Data Transcript point of view. It also descibes the main principles for
CAMEL independantly of CAMEL phase and what is unique for different
CAMEL phases (1, 2 and 3)
Contents
A4 XSEIF R2
Page
Revision Information . . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. .
2
2.1
2.2
2.3
2.4
2.5
2.6
2.7
2.8
2.9
2.10
Description .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 2
Abbreviations . . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 2
Concerned Nodes . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 3
Concepts . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 4
Prerequisites on the network . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 6
General .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 6
CAMEL in GMSC and MSC/VLR .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 8
CAMEL in HLR .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 8
Extended CAMEL . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 9
Triggering .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 9
Traffic cases .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 12
3
3.1
3.2
Data Transcript Impacts . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 17

General .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 17
AXE parameters . . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 31
4
4.1
Miscellaneous Information . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 33
Class . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 33
References . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 34
DESCRIPTION

Approved
173/19046-FAD 104 08 Uen

Checked
2 ( 34 )
No
Date
Rev
2002-04-26
PD2
Reference
Revision Information
Revision
Impacts
Prepared
Date
New Document
ERARDPN
00-05-30
Small update
ERATYDE
01-07-20
Reviewed for CN 1.5,

Minor update
ERATYDE
01-10-04
PD1
Update to CN2.0
status. CAMEL Phase
3 added
ERARDPN
02-03-22
PD2
Updated after internal

review
ERARDPN
020426
Description
2.1
Abbreviations
BCSM
Basic Call State Model
CAMEL
Customised Application for Mobile Enhanced Logic
CAP
CAMEL Application Part
CSI
CAMEL Subscription Information
CS1
Capability Set 1
CS1+
Enhanced Capability Set 1
DP
Detection Point
GMSC
Gateway Mobile services Switching Centre
GPRS
General Packet Radio Services
GSM
Global System for Mobile communications
gsmSCF
GSM Service Control Function
gsmSSF
GSM Service Switching Function
HLR
Home Location Register
HPLMN
Home PLMN
DESCRIPTION
173/19046-FAD 104 08 Uen
Approved
Checked
2.2
3 ( 34 )
No
Date
Rev
2002-04-26
PD2
Reference
IDP
Initial Detection Point
IN
Intelligent Network
INAP
IN Application Part
ISDN
Integrated Services Digital Network
IST
IN Service Trigger
ISUP
ISDN User Part
MSC
Mobile services Switching Centre
MTP
Message Transfer Part
O-CSI
Originating CAMEL Subscription Information
PLMN
Public Land Mobile Network
SCCP
Signalling Connection Control Part
SLP
Service Logic Program
SLPI
Service Logic Program Instance
SMS
Short Meassage Service
TCAP
Transaction Capabilities Application Part
TDP
Trigger Detection Point
T-CSI
Terminating CAMEL Subscriber Information
VLR
Visitor Location Register
VPLMN
Visited PLMN
Concerned Nodes
GMSC
MSC/VLR
HLR
SSF
SCF
DESCRIPTION

Approved
173/19046-FAD 104 08 Uen

Checked
2.3
4 ( 34 )
No
Date
Rev
2002-04-26
PD2
Reference
Concepts
This section aims to briefly describe some concepts in IN and CAMEL. It can
be used as a reference to the other sections.
Assisting gsmSSF
An assisting gsmSSF is used to provide remote user interaction required by the
Service Logic Program in the case when the initiating gsmSSF can not provide
it. Only that sub-set of possible CAMEL Application Part (CAP) Call related
operations applicable to user interaction is applicable in a dialogue between
this type of gsmSSF and SLPI running at an gsmSCF.
Basic Call State Model
The BCSM models the basic call handler process for IN calls. These are the
required activities necessary to establish and maintain communication paths for
users. It also determines when in the call process IN services in the gsmSCF
can interact with the call and how they can manipulate the call process.
Basic Call Handler
This is the part of the gsmSSF that handles the ISUP signalling and the
interconnections of subscribers or call parties.
Call Party
A call party represents a path between the gsmSSF and an addressable
network entity (e.g. an end user). Call connections created by the gsmSCF
are identified by a party identity. The call is initiated by the Calling party and is
received by the Called party.
CAMEL
CAMEL is a network feature which includes support in traditional GSM
functional entities (HLR, GMSC and MSC/VLR) as well as functional entities
originally defined in IN specifications (SSF and SCF). The feature addresses
especially the need for information exchange between the Home PLMN
(HPLMN) and the Visited PLMN (VPLMN) when a HPLMN specific service shall
be provided to a subscriber when roaming outside the HPLMN.
CAMEL Application Part
The CAMEL Application Part (CAP) defines the interface between a gsmSSF
and a gsmSCF.
CAMEL Subscription Information
The CSI is used to indicate that a subscriber has services which require
CAMEL support. It contains sequences with elements, each of them with the
following information:
DESCRIPTION
5 ( 34 )
No
173/19046-FAD 104 08 Uen
Approved
Checked
Date
Rev
2002-04-26
PD2
gsmSCF address
Service Key
Default call handling
BCSM Trigger Detection Point
DP Criteria
CAMEL Capability handling
Reference
Detection Point
A DP is a point in the Basic Call Handler process at which a processing event
can be reported to an gsmSCF or to internal parts in the gsmSSF. If the control
of the Basic Call Handler process is transferred to the gsmSCF when a DP is
reported, the call processing in the gsmSSF is suspended until the gsmSCF
returns the control of the Basic Call Handler process to the gsmSSF. The call
processing is retained by the gsmSSF until the next DP is encountered. All
possible DPs in the call process are shown in the BCSM.
GSM Service Control Function (gsmSCF)
A function in the GSM network that directs control functions in the processing of
supplementary and custom service requests. It is intended to store service
scripts and service data, and be able to execute the Service Logic Program
contained in these scripts towards the gsmSSF.
GSM Service Switching Function (gsmSSF)
A function that interfaces the MSC/GMSC to the gsmSCF. The concept of the
gsmSSF is derived from the IN SSF, but uses different triggering mechanisms
because of the nature of the mobile network.
Initiating gsmSSF
This is a gsmSSF used to allow full control of the call by the gsmSCF. All
gsmSCF initiated call related CAP operations are applicable within a dialogue
set up from an gsmSSF of this type to an SLPI running on an gsmSCF. For the
purpose of this specification, such a dialogue will be initiated as a result of an
Initial DP (IDP) CAP procedure being sent successfully to the gsmSCF.
Intelligent Network Service Trigger
Intelligent Network Service Trigger is a reference to the predefined data in the
gsmSSF which is needed for routing a call via IN.
Service Key
The Service Key can identify to the gsmSCF the service logic that it should
apply. The Service Key is administered by the HPLMN, and is passed by the
VPLMN/HPLMN to the gsmSCF. The Service Key is part of the CSI.
DESCRIPTION
6 ( 34 )
No

Approved
173/19046-FAD 104 08 Uen

Checked
Date
Rev
2002-04-26
PD2
Reference
Service Logic
Service Logic is a sequence of processes and functions used to provide a
specific service.
Service Logic Program
IN allows advanced network features to be provided to the parties in a call.
This is done via network services, which bundle one or more network features
together in a coherent manner. The services are provided by running a Service
Logic Program, capable of controlling the call.
Service Logic Program Instance
The invocation and application of a particular SLP, in providing a service or a
service feature for a specific call/service attempt.
Service Script
One or more service building blocks collected together to implement a Service
Logic Program.
Trigger Detection Point
When a DP is armed as a TDP (by CSI), and the DP is encountered, the
gsmSSF will open a new dialogue towards the gsmSCF. For CAMEL services
(using CAMEL Phase 1 or Phase 2) only the Collect Info and Terminating
Attempt Authorized Trigger Detection Points are valid. For CAMEL Phase 3, all
DP stated in the CS-1 BCSM are supported.
Triggering
Triggering is when an Initial DP (IDP) operation is formed using parameters
applicable to the SLP to be run.
2.4
Prerequisites on the network

CAMEL requires MAP version 3.
2.5
General
2.5.1
Introduction
The Customized Applications for Mobile network Enhanced Logic (CAMEL)
feature is a GSM phase 2+ network feature providing the mechanisms to
support operator-specific services that are not covered by standardized GSM
services, even while roaming outside the Home PLMN (HPLMN). The feature
addresses in particular the need for information exchange between the HPLMN
and the VPLMN when a HPLMN specific service shall be provided to a
subscriber roaming outside the HPLMN.
DESCRIPTION
7 ( 34 )
No

Approved
173/19046-FAD 104 08 Uen

Checked
Date
Rev
2002-04-26
PD2
Reference
The operator-specific services are implemented using Intelligent Network (IN)

principles, whereby the CAMEL network feature provides the mechanisms
necessary for integrating GSM and IN functional entities, including support for
roaming. As CAMEL is based upon IN principles, it is possible to support a
large number of different services. Some examples of services possible with
CAMEL include:
Prepaid services.
Private Numbering Plan for example included abbreviated dialing for such
services as friends and family.
Incoming Call Screening where calls to a B-subscriber can be screened

according to certain conditions (such as A-subscriber number, B-subscriber
number, location, etc.).
Location and time dependent routing where calls from, or to, an end-user
are routed according to location and/or time.
Integration of Advice of Charge into CAMEL services.
CAMEL is a network feature including support in traditional GSM functional

entities (HLR, GMSC and MSC/VLR) as well as functional entities originally
defined in IN specifications (SSF and SCF).
2.5.2
Additions to CAMEL phase 2

The function Support of CAMEL phase 2 is an addition and enhancement on
the function Support of CAMEL phase 1. The major additions to the CAMEL
standard in phase 2 is:
2.5.3
The originating CAMEL Subscription Information (O-CSI) contains more

triggering criteria and the required CAMEL phase information is included.
The MSC supports the control of Advice of Charge by the gsmSCF. This
enables, for example, IN-controlled real time prepaid solutions.
Requirements to support short numbers for call forwarding (e.g. from a

private numbering plan).
Support for requesting and reporting of call start time, stop time, duration
etc. for charging purposes.
Support for writing free format data into MSC and GMSC charging records.
Additions to CAMEL phase 3

The funtion Support of CAMEL Phase 3 is an optional addition and
enhancement on the function Support of CAMEL Phase 2. The major
enhancements are listed here:
Support for mobile originated SMS in MSC as well as support for SMS-CSI
in the HLR. The MSC can notify the gsmSCF, if the subscriber originates
DESCRIPTION
8 ( 34 )
No

Approved
173/19046-FAD 104 08 Uen

Checked
Date
Rev
2002-04-26
PD2
Reference
a short message. The gsmSCF may change the destination address

and/or the service centre address.
2.6
Support of additional new trigger detection points. With CAMEL Phase 3

all CS1 trigger detection points are supported.
Ability to output service-specific free-format billing data directly to the call

data record in either HPLMN or VPLMN.
Support for GPRS-CSI in the HLR.
CAMEL in GMSC and MSC/VLR

When CAMEL is supported in GMSC, the GMSC may receive an Originating
and/or Terminating CAMEL Subscription Information (O/T-CSI) from the HLR
as part of terminating call handling.
In MSC/VLR the Originating CAMEL Subscriber Information (O-CSI) may be
received as part of the subscriber data from HLR in the Insert Subscriber Data
message (for example at Location Update or Update of subscriber data). The
MSC may also receive a SMS-CSI at the same time.
The presence of an O-CSI, T-CSI or SMS-CSI indicates that an instance of
the gsmSSF is to be invoked. The O-CSI is used when an originating CAMEL
service is to be invoked for mobile originating calls and forwarded calls.
Originating CAMEL services may be invoked in the MSC/VLR as well as in the
GMSC. The T-CSI is used when a terminating CAMEL service is to be invoked
in the GMSC for a terminating call. SMS-CSI is used when an originating
CAMEL service is to be invoked for an user originated SMS.
The MSC and the GMSC support conditional triggering of the originated
CAMEL service. The triggering can be dependent on the following conditions:
2.7
Call type (originating/forwarded)
Whether the leading digits of the called party number match one number
in the white (or black) list.
Whether the Basic Sevice Code matches one in a list of Basic Service
Codes.
Whether the called party number length matches a certain length.
CAMEL in HLR
The HLR stores the CAMEL Subscriber Information (CSI). The
O/T/SMS/GPRS-CSI contains the address of the service logic, a service key
(SK) which is sent transparently to the gsmSCF, and a default call handling
parameter indicating the required handling in case an error occurs in the
communication between the gsmSSF and the gsmSCF. It also contains the
CAMEL phase number and CAMEL Trigger Detection Point (TDP).
DESCRIPTION
9 ( 34 )
No

Approved
173/19046-FAD 104 08 Uen

Checked
Date
Rev
2002-04-26
PD2
Reference
The O-CSI and SMS-CSI is sent to the VLR at Location Update or if the CSI
data is updated in the HLR. The O-CSI and T-CSI is sent to the GMSC when
the HLR responds to the message Send Routing Information triggered by the
GRI route in the GMSC. GPRS-CSI is tranferred from the HLR to SGSN for a
GPRS subscriber on GPRS Location Update.
The HLR is able to bar the sending of CAMEL information based on the VPLMN.
The HLR supports the registration for a forwarded-to number which is not in
E.164 format from a CAMEL subscriber with O-CSI. The forwarded-to number
can be sent by the HLR towards the VLR (or GMSC). If the forwarded-to
number is not in E.164 format, it shall not be sent to a non-CAMEL phase 2
(or higher) node.
2.8
Extended CAMEL
The standardized CAP protocol has a limited number of messages compared
to CS1 and CS1+ and is therefor not as powerful. Extended CAMEL is an
enhancement of CAMEL with the ability to use CS1 or CS1+ signalling instead
of CAP. This increase the possibilities for the IN services, i.e. more advanced
services can be provided. If CS1 or CS1+ is used, the IN services will only work
within the network (PLMN) because there is no longer a standard protocol.
The CAMEL subscriber data consists of CSI plus an extension. This extension
exists as default values for standard CAMEL but is changeable with command
HGCEC for Extended CAMEL. There are several possibilities with this extended
information. For example can special CAMEL OICK/TICK- and OIN/TIN-values
be used in the same manner as ordinary OICK/TICK and OIN/TIN in standard
IN.
There are special function codes for Extended CAMEL in the block MIN, i.e.
assigned MIN routes with different route parameters will be used.
The support of Extended CAMEL in MSC/VLR and GMSC is controlled by AXE
parameters (see section chapter 3.2 ).
2.9
Triggering
2.9.1
Introduction
The basic call and connection process is modeled by means of the Basic Call
State Model (BCSM). The BCSM consists of detection points (DPs) in a call
where the gsmSCF can be invoked or the gsmSCF can influence the call
with related operations. Two BCSMs exist, one for originating (O_BCSM) and
one for terminating calls (T_BCSM).
IN triggering is used to hand over the control of the call to the IN service logic
(gsmSCF) at a certain point in the call. The initial conditions for call handling
are prepared at the time of invoking gsmSSF. An important part of this is arming
the applicable DPs. An armed DP is called Trigger Detection Point (TDP).
The arming of the TDPs is dependent on information received in the CSI. For
DESCRIPTION
10 ( 34 )
No

Approved
173/19046-FAD 104 08 Uen

Checked
Date
Rev
2002-04-26
PD2
Reference
CAMEL services, some of the triggering data is received from the HLR in the
CSI, and some triggering data is defined in the trigger tables in the gsmSSF.
The armed TDPs will also be checked against the trigger criteria received from
the HLR and if certain conditions apply, the TDPs can be disarmed again. This
is known as conditional triggering and is done in the case of an O-CSI.
The dialogue set up between gsmSSF and gsmSCF may be either an Initiating
Dialogue or an Assisting Dialogue depending upon the role the gsmSSF is to
perform. An Initiating Dialogue is used when an association between a call
and a SLP running on a gsmSCF needs to be created. An Assisting Dialogue
is used when the gsmSCF orders the Initiating gsmSSF to link to another
gsmSSF (the Assisting gsmSSF) in order to provide additional resources that
the Initiating gsmSSF lacks.
2.9.2
Service invocation
If IN involvement is required in a call, an IN Service Trigger (IST) is pointed
out (outside the gsmSSF). For CAMEL, the IST is pointed out in the MIN route
data. When this happens, the gsmSSF is invoked by a routing case pointing to
a link towards the gsmSSF (an APC link for an integrated gsmSSF).
Trigger preparation
In order to enable and arm the TDPs received in the CSI, the data must be
set up in a trigger table that links IST and TDP (SHISTTOTDP). If this is not
properly done, the call will be released. The TDP to be armed for the CAMEL
service is received in the CSI, and only that TDP is armed (regardless of any
other TDPs defined in the trigger table). The only allowed TDPs for CAMEL
phase 1 and 2 is TDP2 (collect information) for originating calls and TDP12
(terminating attempt authorized) for terminating calls. For CAMEL Phase 3
additional TDPs are allowed.
It is also necessary to know what type of BCSM the gsmSSF should use
(originating or terminating). This data is held in the IST table (SHIST) together
with, for example gsmSSF type (initiating or assisting).
Once the applicable TDPs have been armed, the call progresses. The gsmSSF
will be informed by the Basic Call Handling when a DP is encountered during
the call. If the DP is armed as a TDP then the triggering function is informed.
The triggering function then reads a row from another data table (SHTDP).
This TDP data indicates whether the gsmSSF is to trigger the service as an
Initiating or an Assisting gsmSSF.
Triggering
The InitialDP (IDP) operation has only one mandatory parameter, which is
service key (SK) and is supplied as part of the CSI. This parameter identifies
the SLP to be run at the gsmSCF.
Some of the optional parameters in IDP must be fetched from the Basic Call
Handling by the triggering function. All optional parameters (including extension
fields) must be initiated from trigger tables (SHINS, SHEXLIST), and some
DESCRIPTION
11 ( 34 )
No

Approved
173/19046-FAD 104 08 Uen

Checked
Date
Rev
2002-04-26
PD2
Reference
mandatory parameters are always fetched. Apart from these parameters,

some parameters is also fetched as exchange properties, see AI SSFAM [11].
The exchange properties for the SSF can be viewed with command SHEPP
and changed with command SHEPC.
After the parameter fetching, a dialogue is opened to the gsmSCF and a query
(IDP) is sent from the gsmSSF to gsmSCF. Once the IDP has been sent, further
instructions for the gsmSSF will be received from the gsmSCF.
Routing
Different Service Logic Programs (SLPs) running on different gsmSCFs can be
associated with different SKs (supplied in CSI). The SK is required in order to
reach the correct SLP. To reach the correct gsmSCF, the gsmSCF address is
also needed. This address is provided in the CSI.
In the SHTDP trigger table, it is indicated which protocol and which type of
TCAP to be used in the communication between gsmSSF and gsmSCF. For
CAMEL, CAP protocol will be used.
In order to route between the gsmSCF and the gsmSSF, the SCCP called and
calling party address must be specified.
The SCCP called party address will be received in the CSI. It is also possible to
specify a SubSystem Number (SSN) to be used together with this address in
the SHTSD trigger table. Otherwise Global Title routing without SSN applies to
the information received from CSI.
The SCCP calling party address is defined in the SHTSO trigger table. This will
either be Signalling Point Code and SSN, Global Title and SSN or just Global
Title. If used, the Global Title address is explicitly defined in SHTSO table.
Trigger tables
The trigger tables are connected according to figure 1 . The connection
between different tables are made with special IDs. Then the tables are loaded
into the exchange, they should be loaded in reverse order compared to the flow
of information.
DESCRIPTION
12 ( 34 )
No

Approved
173/19046-FAD 104 08 Uen

Checked
Date
Rev
2002-04-26
PD2
Figure 1
Reference
Trigger tables
Note that the only input into the tables is the IST value. For CAMEL, IST
is set in the MIN route data. The output consists of a lot of data, see the
corresponding application information for each table.
2.10
Traffic cases
2.10.1
Originating CAMEL
Figure 2
2.10.1.1
Originating CAMEL
From Mobile Station to MSC/VLR

Step 1 (figure 2 ).
DESCRIPTION
13 ( 34 )
No

Approved
173/19046-FAD 104 08 Uen

Checked
Date
Rev
2002-04-26
PD2
Reference
A subscriber with originating CAMEL subscription dials a B-number. The

B-number is sent to the MSC/VLR via BSS.
When a call from a mobile subscriber is received at the incoming access and
the mobile subscribers data contains O-CSI then route data determines if, for
the intelligent network operator group connected to the subscribers IMSI, an
intelligent network service trigger and possibly a B-number origin are defined.
Example 1
MML Command
MGISI:IMSIS=240 01 9,
M=5-46 70,
! MODIFICATION+MSIN => NS (C7GSI)
NA=4,
! INTERNATIONAL NUMBER PLAN
ANRES=
OBA-30&
! BO FOR ORIGINATING CALLS
BO-30&
! ORIGIN FOR FORWARDED CALLS
CBA-46&
! CALL BARRING FOR OWN SUBSCRIBERS
CBAZ-146&
! ODB INTER-ZONAL CALLS
PLMN-0&
! ANNOUNCEMENT LANGUAGE INDICATOR
ERIS-0&
! ERICSSON SPECIFIED SERVICES
! Note: OICK/TICK requires MAP V2
! or MAP V3 with ERICSSON
! extensions, i.e. ERIS-0 must be
! used.
INOPER-2&
! IN OPERATOR GROUP 2 (CAMEL)
!
CAMEL-3&
! CAMEL VERSION 3 SUPPORTED
!
MAPVER-2&
! MAP VERSION 3
NRRG-0&
! ROAMING RESTRICTION GROUP
OWNMS&
! OWN PLMN
NATMS;
! NATIONAL PLMN
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
In example 1 , IMSI-series 240 01 9 is defined to use INOPER-2. Subscribers

within this range will use a MIN-route with miscellaneous information number 2
equals to 2 (MIS2=2). The parameter CAMEL indicates the CAMEL version
supported for the subscribers.
2.10.1.2
Connection of MSC/VLR and gsmSSF

Step 2 (figure 2 )
The MIN software route (see example 2 ) is seized. The B-number is
analyzed in the B-number origin defined by parameter BO in the MIN route.
Miscellaneous information number 5 (MIS5) indicates the IN service trigger
(IST) for the specific service.
Example 2
MML commands
EXROI:R=9MIN2, DETY=MIN, FNC=9;

EXRBC:R=9MIN2, BO=70, MIS1=1, MIS2=2, MIS5=210;
DESCRIPTION
14 ( 34 )
No

Approved
173/19046-FAD 104 08 Uen

Checked
Date
Rev
2002-04-26
PD2
Reference
The connection between the existing source system (XSS) and the gsmSSF
is made according to 66/190 46-FAD 104 08 [ref 8]. If an integrated SSF is
used, a APC-link (AM Protocol Carrier) handles the communication between
the two AMs (XSS-SSF).
2.10.1.3
Connection between gsmSSF and gsmSCF

Step 3 (figure 2 )
The desired service is triggered by the gsmSSF. The trigger functionality is
implemented in form of trigger tables. This process is described in section
chapter 2.9 . At the triggered detection point (TDP) the gsmSSF invokes the
gsmSCF. The TDP is part of the CAMEL subscription information (CSI) and
indicates where in the BCSM the gsmSCF is to be contacted. The dialogue
between the gsmSSF and gsmSCF is CAP messages (CAMEL Application
Protocol) and the gsmSCF is connected with its global title address which also
is a part of the CSI. This makes it possible to establish a control connection
with a gsmSCF which is not belonging to the same PLMN as the gsmSSF.
2.10.1.4
Connection between gsmSCF and gsmSSF/MSC/VLR

Step 4 (figure 2 )
The gsmSCF takes control over the call and runs a Service Logic Program
(SLP). The gsmSCF instructs the MSC via the gsmSSF how to handle the call
according to the SLP. This could for example result in a call forward number
or instructions to a IN-based prepaid system. If more analysis is needed,
the B-number is analyzed in a origin defined in the outgoing route from the
gsmSSF (see example 3 ).
Example 3
MML commands
SHRPI:OSR=OUTGOINGROUTE;
SHRSC:PAR=BO, VAL=74, SCAP=1;
SHRPE;
DESCRIPTION

Approved
173/19046-FAD 104 08 Uen

Checked
2.10.2
Date
Rev
2002-04-26
PD2
Reference
Terminating CAMEL
Figure 3
2.10.2.1
15 ( 34 )
No
Terminating CAMEL
Incoming call in GMSC

Step 1 (figure 3 )
A call to a subscriber with terminating CAMEL subscription have reached the
GMSC. The B-number is analyzed and a GRI software route is seized.
2.10.2.2
Connection between GMSC and HLR

Step 2 (figure 3 )
The GMSC requests routing information from the HLR.
2.10.2.3
Connection between HLR and GMSC

Step 3 (figure 3 )
The HLR is returning the CAMEL subscription information. Both T-CSI
and O-CSI is sent if both exist. A terminating CAMEL service could be call
screening and an example of an originating could be call forwarding.
2.10.2.4
Connection between GMSC and gsmSSF

Step 4 (figure 3 )
A MIN software route is seized according to the INOPER parameter from the
IMSI-analysis (see example 4 ). The B-number is analyzed in the B-number
origin defined by parameter BO in the MIN route. The IST is indicated by the
MIS5 parameter in the route.
DESCRIPTION
16 ( 34 )
No

Approved
173/19046-FAD 104 08 Uen

Checked
Example 4
Date
Rev
2002-04-26
PD2
Reference
MML commands
EXROI:R=12MIN2, DETY=MIN, FNC=12;

EXRBC:R=12MIN2, BO=73, MIS1=1, MIS2=2, MIS5=232;
The connection between the existing source system (XSS) and the gsmSSF
is made according to 66/190 46-FAD 104 08 [ref 8]. If an integrated SSF is
used, a APC-link (AM Protocol Carrier) handles the communication between
the two AMs (XSS-SSF).
The interrogation towards the gsmSSF is done in order to trigger the
terminating CAMEL service at this stage. If also a originating service exists for
the subscriber, another gsmSSF interrogation will be done later on (step 8).
2.10.2.5
Connection between gsmSSF and gsmSCF

Step 5 (figure 3 )
The gsmSCF is invoked in the same way as in the originating case (see
section chapter 2.10.1.3 ).
2.10.2.6
Connection between gsmSCF and gsmSSF

Step 6 (figure 3 )
The gsmSCF takes control as in the originating case (see section chapter
2.10.1.4 )
2.10.2.7
Connection between gsmSSF and GMSC

Step 7 (figure 3 )
A T-CSI suppression indicator is set by the gsmSSF to prevent looping. An
integrated SSF will used a predefined APC-link for connection between the two
AMs (SCF and SSF).
2.10.2.8
Connection between GMSC and HLR

Step 8 (figure 3 )
Once again is routing information required by the GMSC and the SRI MAP
message is sent for the second time.
If both T-CSI and O-CSI exists, another interrogation towards the gsmSSF will
be performed instead of the SRI message (e.g. in case of call forwarding).
That means that step 4-7 will be repeated for O-CSI before the SRI is sent
to the HLR.
2.10.2.9
Connection between HLR and MSC/VLR

Step 9 and step 10 (figure 3 )
A roaming number is fetched at the MSC/VLR and is sent back to the HLR.
2.10.2.10
Connection between HLR and GMSC

Step 11 (figure 3 )
DESCRIPTION
17 ( 34 )
No

Approved
173/19046-FAD 104 08 Uen

Checked
Date
Rev
2002-04-26
PD2
Reference
The MSRN is returned back to the GMSC and is analyzed in the B-number
origin defined in the GRI-route used for the interrogation.
2.10.2.11
Connection between GMSC and MSC/VLR

Step 12 (figure 3 )
The call is routed to the MSC/VLR by the MSRN and is terminated via BSS
to the CAMEL subscriber.
Data Transcript Impacts
3.1
General
3.1.1
(G)MSC/VLR/SSF
Subfile 10000: APT Size Alterations
SAAII:SAE=500,BLOCK=SSCAMEL,NI=2000;
SAAII:SAE=500,BLOCK=SSCAMEL,NI=3000;
SAE 500 for block SSCAMEL is a traffic sensitive SAE and sets the maximum
number of parallel CAP dialogues.
SAAII:SAE=604,NI=100,BLOCK=SHPM2;
SAE 604 for block SHPM2, SHPM3 and SHPM4 is traffic sensitive and sets
the maximum number of parallel SSF-SCF dialogues using CAMEL Phase
1 (SHPM2), CAMEL Phase 2 (SHPM3) and CAMEL Phase 3 (SHPM4)
application protocol respectively.
SAII:SAE=602,NI=1000,BLOCK=MTVIN;
SAE 602 is used to store data related to O-CSI for visiting mobile subscribers.
One individual is seized for each O-CSI data set received from the Home
Location Register (HLR) for a visiting mobile subscriber.
SAII:SAE=604,NI=10000,BLOCK=SHGTCU;
SAAII:SAE=604,NI=100,BLOCK=SHCC;
SAAII:SAE=605,NI=500,BLOCK=SHCC;
SAE 604 and 605 for block SHCC sets the maximum number of queued internal
ISUP messages from call legs or INAP operations from SCP.
DESCRIPTION
18 ( 34 )
No

Approved
173/19046-FAD 104 08 Uen

Checked
Date
Rev
2002-04-26
PD2
Reference
SAAII:SAE=605,NI=100,BLOCK=SCFCAP2;
SAAII:SAE=605,NI=500,BLOCK=SCFCS1P;
SAII:SAE=606,NI=500,BLOCK=SCFCS1P;
SAII:SAE=629,NI=500,BLOCK=MTVIN;
SAE 629 is used to store data related to SMS-CSI for visiting mobile
subscribers. One individual is seized for each SMS-CSI data set received from
the Home Location Register (HLR) for a visiting mobile subscriber.
SAAII:SAE=700,NI=100,BLOCK=SHSMS;
Subfile 13000: Exchange Properties
!* CHECK EXCHANGE PROPERTIES IN SSF *!
SHEPP:PROP=ALL;
Subfile 15300: ECP, Route And APC Characteristics

! ROUTES FOR IN OPERATOR GROUP 2, CAMEL SUBSCRIBERS !
EXROI:R=9MIN2,DETY=MIN, FNC=9;
! O-CAMEL IN MSC/VLR !
EXRBC:R=9MIN2,BO=70,MIS1=1,MIS2=2;
EXROI:R=10MIN2,DETY=MIN,FNC=10; ! O-CAMEL IN MSC/VLR CFC !
EXROI:R=11MIN2,DETY=MIN, FNC=11; ! O-CAMEL IN GMSC CFU !
EXROI:R=12MIN2,DETY=MIN, FNC=12; ! T-CAMEL IN GMSC !
Definition of MIN routes for CAMEL at call from MS, at Call Forwarding
conditional (in MSC/VLR), at Call Forwarding Unconditional (in GMSC) and
terminating respectively. Observe that the parameter MIS5 (that is mandatory
for CAMEL) can not be set before the trigger tables are loaded and is therefor
not included here.
!* APPLICATION PROTOCOL CARRIER LINKS *!
EXROI:R=SSFDJO1&SSFDJI1,DETY=TRACO,FNC=3;
ARLII:APCLNK=SSFTRAM,EPO1=TRACO,EPO2=SHCM,PID=30,SMAX=50;
EXRBC:R=SSFDJO1,APCLNK=SSFTRAM;
EXRBC:R=SSFDJI1,APCLNK=SSFTRAM;
Definition of APC links and routes between XSS (MSC/VLR) and SSF AM.
DESCRIPTION
19 ( 34 )
No

Approved
173/19046-FAD 104 08 Uen

Checked
Date
Rev
2002-04-26
PD2
Reference
!* APPLICATION MODULE ROUTES *!

SHRPI:OSR=OUTGOINGROUTE;
SHRSC:APC=SSFTRAM;
SHRSC:PAR=BO, VAL=74,SCAP=1;
SHRSC:PAR=CO, VAL=0,SCAP=1;
SHRPE;
SHRPI:ISR=INCOMINGROUTE;
SHRSC:APC=SSFTRAM;
SHRPE;
The definition of new AM-routes for CAMEL requires that APC links towards the
SSF exists. Note that B-number and charging origins after IN interrogation is
set with parameter BO and CO in the outgoing route.
Subfile 15330: Trigger Tables in SSF-AM
!* TABLE SHTSO - SSF OWN ADDRESS *!
DBTRI;
DBTSI:TAB=SHTSO,TSOID=32,FORGADR=0,ORGNAME=SSF300,OGTTRAN=3,
OGTNAPI=1,OGTNOA=4,OGLT=46707570900;
DBTRE:COM;
!* TABLE SHTSD - SCF DESTINATION ADDRESS *!

DBTRI;
DBTSI:TAB=SHTSD,TSDID=10,FDSTADR=7,DSTNAME=SCFCAP,GTTRAN=0,DPCLTH=14;
DBTRE:COM
!* TABLE SHTDPS - TRIGGER DETECTION POINT SPECIFIC DATA *!

! Originating traffic !
DBTRI;
DBTSI:TAB=SHTDPS,TDPSID=10,TSDID=10,CESS=CSI,CTMP=CSI,
EVTYPE=NO,TSOID=32,SHR=1,SHS=1,USI=CSI;
DBTRE:COM;
! Terminating Traffic !
DBTRI;
DBTSI:TAB=SHTDPS,TDPSID=32,TSDID=10,CESS=CSI,CTMP=CSI,
EVTYPE=NO,TSOID=32,SHR=1,SHS=1,USI=CSI;
DBTRE:COM;
!* TABLE SHINS - INITIAL DETECTION POINT PARAMETERS *!
! Originating Traffic !
DBTRI;
DBTSI:TAB=SHINS,INSID=10,CDN=OPT,CGCAT=OPT;
DBTRE:COM;
DBTRI;
DBTSC:TAB=SHINS,INSID=10,BCAP=OPT,ACGN=OPT;
DBTRE:COM;
DBTRI;
DESCRIPTION
20 ( 34 )
No

Approved
173/19046-FAD 104 08 Uen

Checked
Date
Rev
2002-04-26
PD2
Reference
DBTSC:TAB=SHINS,INSID=10,BGVNS=NO,CPN=OPT;
DBTRE:COM;
DBTRI;
DBTSC:TAB=SHINS,INSID=10,FWCI=NO,LN=OPT;
DBTRE:COM;
DBTRI;
DBTSC:TAB=SHINS,INSID=10,OCDN=OPT,RDI=OPT;
DBTRE:COM;
DBTRI;
DBTSC:TAB=SHINS,INSID=10,GDS=NO,GNS=NO;
DBTRE:COM;
DBTRI;
DBTSC:TAB=SHINS,INSID=10,CAUSE=NO,SII=NO;
DBTRE:COM;
DBTRI;
DBTSC:TAB=SHINS,INSID=10,HLC=OPT,RGN=OPT,RO=NO;
DBTRE:COM;
DBTRI;
DBTSI:TAB=SHINS,INSID=32,CDN=OPT,CGCAT=OPT;
DBTRE:COM;
DBTRI;
DBTSC:TAB=SHINS,INSID=32,BCAP=OPT,ACGN=OPT;
DBTRE:COM;
DBTRI;
DBTSC:TAB=SHINS,INSID=32,BGVNS=NO,CPN=OPT;
DBTRE:COM;
DBTRI;
DBTSC:TAB=SHINS,INSID=32,FWCI=NO,LN=OPT;
DBTRE:COM;
DBTRI;
DBTSC:TAB=SHINS,INSID=32,OCDN=OPT,RDI=OPT;
DBTRE:COM;
DBTRI;
DBTSC:TAB=SHINS,INSID=32,GDS=NO,GNS=NO;
DBTRE:COM;
DBTRI;
DBTSC:TAB=SHINS,INSID=32,CAUSE=NO,SII=NO;
DBTRE:COM;
DBTRI;
DBTSC:TAB=SHINS,INSID=32,HLC=OPT,RGN=OPT,RO=NO;
DBTRE:COM;
!* TABLE SHTDP - TRIGGER DETECTION POINT PARAMETERS *!

DBTRI;
DBTSI:TAB=SHTDP,TDPID=10,DIAGTYP=1,PROTI=2,TDPSID=10,
TINSID=10;
DBTRE:COM;
DBTRI;
DESCRIPTION
21 ( 34 )
No

Approved
173/19046-FAD 104 08 Uen

Checked
Date
Rev
2002-04-26
PD2
Reference
DBTSI:TAB=SHTDP,TDPID=32,DIAGTYP=1,PROTI=2,TDPSID=32,
TINSID=32;
DBTRE:COM;
!* TABLE SHTNS - SSF ROUTE AND CHARGING CASES *!

DBTRI;
DBTSI:TAB=SHTNS,TNSID=10,BRISRID=5,DRISRID=5,BROSRID=6,
DROSRID=6,ROUTTYP=DR,ISCC=8,OSBCC=0,
OSDCC=0,CLIDTYP=2,SCFIDTY=3,CLIDATA=0;
DBTRE:COM;
DBTRI;
DBTSI:TAB=SHTNS,TNSID=32,BRISRID=5,DRISRID=5,BROSRID=6,
DROSRID=6,ROUTTYP=DR,ISCC=8,OSBCC=0,
OSDCC=0,CLIDTYP=2,SCFIDTY=3,CLIDATA=0;
DBTRE:COM;
!* TABLE SHIST - ASSOCIATE IN SERVICE WITH SHTNS *!

DBTRI;
DBTSI:TAB=SHIST,IST=210,TNSID=10,BCSMTYP=ORIG,SSFTYPE=I,NUMDIG=7;
DBTRE:COM;
DBTRI;
DBTSI:TAB=SHIST,IST=232,TNSID=32,BCSMTYP=TERM,SSFTYPE=I;
DBTRE:COM;
!* TABLE SHISTTOTDP - ASSOCIATE IST WITH TDP *!

DBTRI;
DBTSI:TAB=SHISTTOTDP,IST=210,TDPNO=DP2,TDPID=10;
DBTRE:COM;
DBTRI;
DBTSI:TAB=SHISTTOTDP,IST=232,TDPNO=DP12,TDPID=32;
DBTRE:COM;
!* IST VALUE IS ADDED TO MIN ROUTES FOR CAMEL *!
EXRBC:R=9MIN2,MIS5=210;
Subfile 15400: Route Analysis
ANRSI:RC=25,R=SSFDJO1,SP=MM1;
DESCRIPTION
22 ( 34 )
No
173/19046-FAD 104 08 Uen
Approved
Checked
Date
Rev
2002-04-26
PD2
Reference
Routing case 25 is defined towards SSF using software route SSFDJO1.

Subfile 15600: B-Number Analysis
For IN calls, the called number is modified by the system (SW modification).
How the number is modified depends on the nature of address indicator (NAI)
received for the B-number. See table 1 .
Table 1
Modification of B-number for IN calls
NAI
Modification of B-number
1 (international)
(EOICK) + international prefix + B-number
2 (unknown)
(EOICK) + B-number
4 (national)
(EOICK) + national trunk prefix + B-number
EOICK is only added if Extended CAMEL with IN Category Key is used. After
modification, the numbering plan indicator is set to E.164 and the nature of
address indicator is set to unknown format.
!*****************************************************!
!***
USED B-NUMBER ORIGINS FOR CAMEL
***!
!*****************************************************!
!*
B=70
ORIGINATING CAMEL, UNKNOWN FORMAT
*!
!*
B=73
TERMINATING CAMEL, UNKNOWN FORMAT
*!
!*
B=74
CAMEL CALLS AFTER SCF INTERROGATION
*!
!*****************************************************!
ANBSI:B=70-00,
ANBSI:B=70-01,
ANBSI:B=70-02,
ANBSI:B=70-03,
ANBSI:B=70-04,
ANBSI:B=70-05,
ANBSI:B=70-06,
ANBSI:B=70-07,
ANBSI:B=70-08,
ANBSI:B=70-09,
ANBSI:B=70-10,
ANBSI:B=70-11,
ANBSI:B=70-111,
ANBSI:B=70-112,
ANBSI:B=70-113,
ANBSI:B=70-114,
ANBSI:B=70-115,
ANBSI:B=70-116,
ANBSI:B=70-117,
ANBSI:B=50-118,
ANBSI:B=70-119,
ANBSI:B=70-13,
L=5-20, RC=25;
L=5-20, RC=25;
L=5-20, RC=25;
L=5-20, RC=25;
L=5-20, RC=25;
L=5-20, RC=25;
L=5-20, RC=25;
L=5-20, RC=25;
L=5-20, RC=25;
L=5-20, RC=25;
L=5-20, RC=25;
L=5-20, RC=25;
L=5-20, RC=25;
L=3, F=30;
L=5-20, RC=25;
L=5-20, RC=25;
L=5-20, RC=25;
L=5-20, RC=25;
L=5-20, RC=25;
L=5-20, RC=25;
L=5-20, RC=25;
L=5-20, RC=25;
DESCRIPTION
23 ( 34 )
No

Approved
173/19046-FAD 104 08 Uen

Checked
ANBSI:B=70-14,
ANBSI:B=70-15,
ANBSI:B=70-16,
ANBSI:B=70-17,
ANBSI:B=70-18,
ANBSI:B=70-19,
ANBSI:B=70-2,
ANBSI:B=70-3,
ANBSI:B=70-4,
ANBSI:B=70-5,
ANBSI:B=70-6,
ANBSI:B=70-7,
ANBSI:B=70-8,
ANBSI:B=70-90,
ANBSI:B=70-91,
ANBSI:B=70-92,
ANBSI:B=70-93,
ANBSI:B=70-93,
ANBSI:B=70-95,
ANBSI:B=70-96,
ANBSI:B=70-97,
ANBSI:B=70-98,
ANBSI:B=70-99,
Date
Rev
2002-04-26
PD2
Reference
L=5-20, RC=25;
L=5-20, RC=25;
L=5-20, RC=25;
L=5-20, RC=25;
L=5-20, RC=25;
L=5-20, RC=25;
L=5-20, RC=25;
L=5-20, RC=25;
L=5-20, RC=25;
L=5-20, RC=25;
L=5-20, RC=25;
L=5-20, RC=25;
L=5-20, RC=25;
L=5, F=30;
L=5-20, RC=25;
L=5-20, RC=25;
L=5-20, RC=25;
L=5-20, RC=25;
L=5-20, RC=25;
L=5-20, RC=25;
L=5-20, RC=25;
L=5-20, RC=25;
L=5-20, RC=25;
ANBSI:B=73-4670, RC=25;
ANBSI:B=74-00,
ANBSI:B=74-01,
ANBSI:B=74-02,
ANBSI:B=74-03,
ANBSI:B=74-04,
ANBSI:B=74-05,
ANBSI:B=74-06,
ANBSI:B=74-07,
ANBSI:B=74-08,
ANBSI:B=74-09,
ANBSI:B=74-1,
ANBSI:B=74-2,
ANBSI:B=74-3,
ANBSI:B=74-4,
ANBSI:B=74-5,
ANBSI:B=74-6,
ANBSI:B=74-7,
ANBSI:B=74-8,
ANBSI:B=74-9,
M=2, BNT=1, F=32;

BNT=2, F=30;
BNT=2, F=30;
BNT=2, F=30;
BNT=2, F=30;
BNT=2, F=30;
BNT=2, F=30;
BNT=2, F=30;
BNT=2, F=30;
BNT=2, F=30;
BNT=2, F=30;
BNT=2, F=30;
BNT=2, F=30;
BNT=2, F=30;
BNT=2, F=30;
BNT=2, F=30;
BNT=2, F=30;
BNT=2, F=30;
BNT=2, F=30;
All calls except emergency calls are routed to SSF via RC 25. After IN
interrogation, the calls is forwarded to standard trees.
Subfile 27000: Deblocking of Routes
DESCRIPTION
24 ( 34 )
No

Approved
173/19046-FAD 104 08 Uen

Checked
Date
Rev
2002-04-26
PD2
Reference
BLORE:R=SSFDJO1;
BLORE:R=SSFDJI1;
ARLBE:APCLNK=SSFTRAM;
Deblocking of routes and APC-links.
Subfile 75400: Node Addresses (SCCP GT)
PHGTI:GTA=707570900;
Defines the GT address for the SSF.
Subfile 75500: SCCP Data
C7NPI:SP=3-900, CON;
C7NSI:SP=3-900, SSN=252;
Definition of the SCP in the SCCP ntework.
C7GCI:GTRC=12, PSP=3-900, PTERM;
C7GSI:TT=0,NP=1,NA=4,NS=467070300,GTRC=12;
Definition of a GTRC towards the own SCP for node communication on SCCP
layer in the home network.
C7GCI:GTRC=8,PSP=OWNSP;
Termination in the own exchange of messages sent on SCCP layer to the SSF.
Which TT to use is set in trigger table SHTSO.
Subfile 76000: IMSI Number Analysis
DESCRIPTION
25 ( 34 )
No

Approved
173/19046-FAD 104 08 Uen

Checked
Date
Rev
2002-04-26
PD2
Reference
MGISI:IMSIS=240 01 9,
M=5-46 70,
! MODIFICATION+MSIN => NS (C7GSI)
NA=4,
! INTERNATIONAL NUMBER PLAN
ANRES=
OBA-30&
! BO FOR ORIGINATING CALLS
BO-30&
! ORIGIN FOR FORWARDED CALLS
CBA-46&
! CALL BARRING FOR OWN SUBSCRIBERS
CBAZ-146&
! ODB INTER-ZONAL CALLS
PLMN-0&
! ANNOUNCEMENT LANGUAGE INDICATOR
ERIS-0&
! ERICSSON SPECIFIED SERVICES
! Note: OICK/TICK requires MAP V2
! or MAP V3 with ERICSSON
! extensions, i.e. ERIS-0 must be
! used.
INOPER-2&
! IN OPERATOR GROUP 2 (OWN CAMEL)
CAMEL-3&
! CAMEL VERSION 3 SUPPORTED
MAPVER-2&
! MAP VERSION 3
NRRG-0&
! ROAMING RESTRICTION GROUP
OWNMS&
! OWN PLMN
NATMS;
! NATIONAL PLMN
3.1.2
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
HLR
SAAII:SAE=602,
SAAII:SAE=603,
SAAII:SAE=604,
SAAII:SAE=605,
SAAII:SAE=606,
SAAII:SAE=607,
BLOCK=HCSID,
BLOCK=HCSID,
BLOCK=HCSID,
BLOCK=HCSID,
BLOCK=HCSID,
BLOCK=HCSID,
NI=15000;
NI=15000;
NI=15000;
NI=15000;
NI=15000;
NI=15000;
Size alterations for block HCSID is used for storing of CAMEL subscriber data.
Subfile 75400: Address information and Roaming Area characteristics
HGGSI:GSA=46707030000;
Definition of own gsmSCF addresses. All SCF addresses within the PLMN
should be included here.
DESCRIPTION
26 ( 34 )
No

Approved
173/19046-FAD 104 08 Uen

Checked
HGRCI:AREA=4-46
HGRCI:AREA=4-46
HGRCI:AREA=4-46
HGRCI:AREA=4-46
70,
70,
70,
70,
Date
Rev
2002-04-26
PD2
Reference
CHAR=OCSIPH1;
CHAR=OCSIPH2;
CHAR=OCSIPH3;
CHAR=EXTCAMEL;
HGRCI:AREA=4-44, CHAR=OCSIPH1;
Roaming Area charactersitics for originating CAMEL subscriber data and
extended CAMEL data.
Subfile 80000: Subscriber Data
HGSDC:MSISDN=46707679001,SUD=OCSI-1;
HGSDC:MSISDN=46707679001,SUD=TCSI-1;
HGSDC:MSISDN=46707679001,SUD=OSMCSI-1
HGSDC:MSISDN=46707679001,SUD=GPRCSI-1
HGCMI:MSISDN=46707679001,OCTDP=2,SK=10,
GSA=46707030000,DEH=0,CCH=3;
Subscription to originating CAMEL service with SK=10 (originating prepaid).
The default error handling indicates that the call should be released if the
connection to the SCF fails. Trigger Detection Point 2 (collected information)
is used.
HGCMI:MSISDN=46707679001,TCTDP=12,SK=32,
GSA=46707030000,DEH=1,CCH=3;
Subscription to terminating CAMEL service with SK=32 (PN incoming calls).
The default error handling in this case indicates that the call should continue if
connection to the SCF fails. TDP 12 is used.
HGCMI:MSISDN=46707679001,OSMSTDP=1,SK=200,
GSA=46707030000,DEH=0,CCH=3;
Subscription to originating SMS service (SK=200) using CAMEL Phase 3
(CCH=3). The Originating SMS TDP 1 (DP Originating SMS collected info) is
used. In case of error in the dialogue between GSM service control function
and GSM service switching function the call is released (DEH=0).
HGCMI:MSISDN=46707679001,GPRSTDP=1,SK=123,
GSA=46707030000,DEH=0,CCH=3;
Subscription to CAMEL GPRS function with Service Key 123. GPRSTDP 1
indicates Detection Point attach. CAMEL Phase 3 is used (CCH=3) and in case
DESCRIPTION
27 ( 34 )
No

Approved
173/19046-FAD 104 08 Uen

Checked
Date
Rev
2002-04-26
PD2
Reference
of error in the dialogue between GSM service control function and GSM service
switching function the call is released (DEH=0).
If Extended CAMEL is used, additional subscriber data is defined here with
command HGCEC.
3.1.3
SCF
The size alterations described below is necessary for implementing CAMEL
Phase 1.
SAAII:SAE=500, NI= 100, BLOCK=SCFCOD;
! Number of traffic task indiv.
EXT.min:0
!
! at invocation of encoding/
max:65535
!
! decoding function by the
RED.min:0
!
! protocol indpendent engine.
max:65535
!
!
- traffic sensitive !
!------------------------------------------------------!
SAAII:SAE=500, NI= 100, BLOCK=SSCCS;
! Number of active controltype
EXT.min:0
!
! encoding instances in SCP <-> ,
max:65535
!
! CCS dialogues.
RED.min:0
!
! CCS: Call Center (billing) Service max:65535
!
!
!------------------------------------------------------!
SAAII:SAE=500, NI=
20, BLOCK=SSCDO;
! Number of global information
EXT.min:0
!
! individuals at invocation of
max:500
!
! SLPI charging from SCP, i.e.
RED.min:0
!
! charging data output (CDO).
max:500
!
!
- traffic sensitive maxval=65535
!
!------------------------------------------------------!
SAAII:SAE=604, NI=
20, BLOCK=SSCDO;
! Number of Basic Encoded Rule
EXT.min:0
!
! (BER) encoded charging data
max:500
!
! from SLPI prior to transfer it RED.min:0
!
! to the CDR (= SAE-500/SSCDO).
max:500
!
!
!
!------------------------------------------------------!
SAAII:SAE=617, NI= 100, BLOCK=SSI;
! Number of additional call
EXT.min:1
!
! related monitor requests not
max:300
!
! being stored in the standard , RED.min:1
!
! call individuals.
max:300
!
!
!------------------------------------------------------!
DESCRIPTION
28 ( 34 )
No

Approved
173/19046-FAD 104 08 Uen

Checked
Date
Rev
2002-04-26
PD2
Reference
SAAII:SAE=670, NI= 200, BLOCK=SSCDO;

! Number of single CDRs opened
EXT.min:0
!
! for a SLPI. An SLPI can have
max:500
!
! up to 30 single CDRs open at
RED.min:0
!
! any time (= 30 * SAE-500/SSCDO).
max:500
!
!
!
!------------------------------------------------------!
SAAII:SAE=671, NI= 100, BLOCK=SCFCOD;
! Number of mapping table indiv. EXT.min:1
!
! used to correlate PIE handled
max:300
!
! operation parameters with data, RED.min:1
!
! to be used in encoding process.
max:300
!
!------------------------------------------------------!
SAAII:SAE=671, NI=
10, BLOCK=SSTAB2;
! Number of entry data indiv.
EXT.min:0
!
! associated with the data
max:65535
!
! modules for controltype
RED.min:0
!
! NRTAB2.
max:65535
!
!------------------------------------------------------!
SAAII:SAE=671, NI=
20, BLOCK=SSCDO;
! Number of data modules (DM)
EXT.min:0
!
! for WRTCDR (Write CDR) defined
max:500
!
! in SLPIs by command SSDTI.
RED.min:0
!
! SSDTE releases those individuals. max:500
!
!
maxval=65535
!
!------------------------------------------------------!
SAAII:SAE=671, NI= 100, BLOCK=SSCCS;
! Number of data modules (DM)
EXT.min:0
!
! for Controltypes:
max:500
!
! CCSNOTE/CCSRSUM/CCSSTAI/
RED.min:0
!
! CCSSTAO/CCSSTOP
max:500
!
!
maxval=65535
!
!------------------------------------------------------!
SAAII:SAE=673, NI=
20, BLOCK=SCFCOD;
! Number of parameter module data EXT.min:1
!
! individuals used as an extension
max:300
!
! to the mapping table to store
RED.min:1
!
! service data numbers.
max:300
!
!------------------------------------------------------!
SAAII:SAE=760, NI= 300, BLOCK=SCFPIAM;
! Number of active SCF - TCAP
EXT.min:0
!
! dialogues towards a remote
max:65535
!
! functional entity.
RED.min:0
!
!
- traffic sensitive max:65535
!
!------------------------------------------------------!
DESCRIPTION
29 ( 34 )
No

Approved
173/19046-FAD 104 08 Uen

Checked
Date
Rev
2002-04-26
PD2
Reference
SAAII:SAE=760, NI=
10, BLOCK=CAMPM01;
! Number of active SSF-SCF
EXT.min:1
!
! dialogues using CAMEL
max:65535
!
! APPLICATION PROTOCOL
RED.min:1
!
!
!
!------------------------------------------------------!
SAAII:SAE=760, NI=
10, BLOCK=CAMPM02;
! Number of active SSF-SCF
EXT.min:1
!
! dialogues using CAMEL
max:65535
!
! APPLICATION PROTOCOL
RED.min:1
!
!
!
!------------------------------------------------------!
SAAII:SAE=760, NI=
10, BLOCK=SSTAB2;
! Number of origin data indiv.
EXT.min:0
!
max:65535
!
RED.min:0
!
! NRTAB2.
max:65535
!
!------------------------------------------------------!
SAAII:SAE=761, NI=
10, BLOCK=SSTAB2;
! Number of analysis tree indiv. EXT.min:0
!
max:65535
!
RED.min:0
!
! NRTAB2.
max:65535
!
!------------------------------------------------------!
SAAII:SAE=770, NI= 100, BLOCK=SSI;
! Number of call data and lookup EXT.min:0
!
! table individuals.
max:65535
!
!
RED.min:0
!
!
!
!------------------------------------------------------!
The size alterations described below is introduced for CAMEL Phase 2.
DESCRIPTION
30 ( 34 )
No

Approved
173/19046-FAD 104 08 Uen

Checked
Date
Rev
2002-04-26
PD2
Reference
SAAII:SAE=500, NI= 100, BLOCK=SSINAP3;

! Traffic Task individuals (TTI) EXT.min:1
!
! containing the operation
max:-1000
!
! data encoding & sending
RED.min:1
!
! related to the control type
max:-1000
!
! CONTARG.
!
! Supported Protocol: CAP Ph2
!
!------------------------------------------------------!
SAAII:SAE=500, NI= 100, BLOCK=SSCAMEL;
! Traffic Task individuals (TTI) EXT.min:1
!
! containing the operation
max:-65535
!
! data encoding & sending
RED.min:1
!
! related to the control types:
max:-65535
!
! CHARAPP / CHARINF
!
! Supported Protocol: CAP Ph2
!
!------------------------------------------------------!
SAAII:SAE=671, NI= 100, BLOCK=SSINAP3;
! DM-CTR and ARGUMENT MODULE
EXT.min:1
!
! files belonging to the
max:-1000
!
! controltype supported in
RED.min:1
!
! SSINAP3 to build operations.
max:-1000
!
!------------------------------------------------------!
SAAII:SAE=671, NI= 100, BLOCK=SSCAMEL;
! DM-CTR and ARGUMENT MODULE
EXT.min:1
!
! files belonging to the
max:-1000
!
! controltype supported in
RED.min:1
!
! SSINAP3 to build operations.
max:-1000
!
!------------------------------------------------------!
Subfile 75400: Node Addresses (SCCP GT)
PHGTI:GTA=707030000;
Defines the GT address for the SCF.
Subfile 75500: SCCP Data
C7NPI:SP=3-300, CON;
C7NSI:SP=3-300, SSN=251;
Definition of the SSF in MSC1 in the SCCP layer.
C7GCI:GTRC=1,PSP=OWNSP;
C7GCI:GTRC=2,PSP=3-300,PTERM;
C7GCI:GTRC=3,PSP=3-300,PINTER;
!TERM IN OWN NODE !

!TERM IN MSC1
!
!MSC1 INTERMEDIATE!
Definition of SCCP routing case for terminating in own node, routing case
towards SSF in MSC1 and a routing case for access to the international
network.
DESCRIPTION
31 ( 34 )
No

Approved
173/19046-FAD 104 08 Uen

Checked
Date
Rev
2002-04-26
PD2
Reference
C7GSI:TT=0,NP=1,NA=4,NS=46 707 0300,GTRC=1; !OWN NODE!

C7GSI:TT=0,NP=1,NA=4,NS=46 707 5709,GTRC=2; !SSF MSC1!
Definition of addresses for own node and SSF in MSC1.
!U.K. SSF
!
!GERMAN SSF
!
!AUSTRALIAN SSF !
!SINGAPORIAN SSF!
Definitions of number series for other operators with CAMEL roaming

agreement.
3.2
AXE parameters
Some AXE parameters are password protected and can only be accessed
with command SYPAC.
3.2.1
MSC/VLR
DBTRI;
DBTSC:TAB=AXEPARS,SETNAME=GSM1APTF,NAME=MSCNF384,VALUE=1;
DBTRE:COM;
Parameter MSCNF384 indicates CAMEL Phase 1 feature activation in the node.
DBTRI;
DBTSC:TAB=AXEPARS,SETNAME=GSMMSSF,NAME=MSCNF499,VALUE=0;
DBTRE:COM;
Parameter MSCNF499 indicates extended CAMEL activation. In this example,
extended CAMEL will not be used.
DBTRI;
DBTSC:TAB=AXEPARS,SETNAME=GSMMMSF,NAME=MSCNF132,VALUE=1;
DBTRE:COM;
Parameter MSCNF132 indicates the availability of the administration of
Location Numbers.
DBTRI;
DBTSC:TAB=AXEPARS,SETNAME=GSMMDSF,NAME=MSCNF336,VALUE=1;
DBTRE:COM;
Parameter MSCNF336 indicates the availability of support related to Provision
of Subscriber Information towards the HLR.
DBTRI;
DBTSC:TAB=AXEPARS,SETNAME=GSMMSSF,NAME=MSCNF15,VALUE=1;
DBTRE:COM;
Parameter MSCNF15 indicates the support of Advice of Charge.
DESCRIPTION
32 ( 34 )
No

Approved
173/19046-FAD 104 08 Uen

Checked
Date
Rev
2002-04-26
PD2
Reference
DBTRI;
DBTRE:COM;
Parameter MSCNF618 indicates the support of CAMEL phase 2.
DBTRI;
DBTSC:TAB=AXEPARS,SETNAME=PGSMMSSC,NAME=ECAMELRESTRICT,VALUE=0;
DBTRE:COM;
Parameter ECAMELRESTRICT determines whether Extended CAMEL with
intelligent network category key applies for all circuit switched basic services
except emergency calls or only for telephony and auxiliary telephony.
DBTRI;
DBTRE:COM;
Parameter MSCNF6182 indicates the support of CAMEL phase 3.
3.2.2
GMSC
DBTRI;
DBTSC:TAB=AXEPARS,SETNAME=GSMMSSF,NAME=GMSCNF384,VALUE=1;
DBTRE:COM;
Parameter GMSCNF384 indicates if CAMEL phase 1 is supported.
DBTRI;
DBTRE:COM;
Parameter GMSCNF499 indicates if Extended CAMEL is supported. In this
example only standard CAMEL is supported.
DBTRI;
DBTRE:COM;
Parameter GMSCNF618 indicates if CAMEL phase 2 is supported.
DBTRI;
DBTSC:TAB=AXEPARS,SETNAME=GSMMSSC,NAME=CAMELCUGBAR,VALUE=1;
DBTRE:COM;
Parameter CAMELCUGBAR indicates if Closed User Group (CUG) calls is to
be barred in the SSF.
3.2.3
HLR
DBTRI;
DBTSC:TAB=AXEPARS,SETNAME=GSMHRSF,NAME=HLRNF496,VALUE=1;
DBTRE:COM;
DESCRIPTION
33 ( 34 )
No

Approved
173/19046-FAD 104 08 Uen

Checked
Date
Rev
2002-04-26
PD2
Reference
Parameter HLRNF496 is the main switch for enabling CAMEL in the HLR.
DBTRI;
DBTRE:COM;
Parameter HLRNF498 indicates support of extended CAMEL.
DBTRI;
DBTRE:COM;
Parameter HLRNF746 indicates support of CAMEL phase 2.
Miscellaneous Information
4.1
Class
Support of CAMEL Phase 2 is a standard optional feature.
DESCRIPTION

Approved
173/19046-FAD 104 08 Uen

Checked
34 ( 34 )
No
Date
Rev
2002-04-26
PD2
Reference
References
a
Service Switching function CAMEL Phase 2, General

[1] 118/155 17-APR 101 15 Uen
Mobile Access Support for CAMEL in MSC/VLR

[2] 87/155 17-ANT 292 01/5 Uen
CAMEL Support in GMSC

[3] 90/155 17-ANT 292 01/5 Uen
CAMEL Phase 2 in HLR

[4] 193/155 17-ANT 238 01 Uen
CAMEL Phase 2 SS8.0 (CME20/CMS40)

[5] LK/NX 1056-074 Uen
Service Switching Function: CAMEL Phase 2, Basic Call Handling

[6] 126/155 17-APR 101 15 Uen
Service Switching Function CAMEL Phase 2, Triggering

[7] 157/155 17-APR 101 15 Uen
IN Service Triggering in GMSC/MSC/VLR and SSF

[8] 66/190 46-FAD 104 08 Uen
Home Location Register, CAMEL Subscription Data, Initiate (HGCMI)

[9] 1/190 82-CNT 238 0124 Uen
Home Location Register, CAMEL Extended Information, Change

(HGCEC)
[10] 5/190 82-CNT 238 0124 Uen
SSFAM, Service Switching Function Changeable Exchange

Adaptation
[11] 2/155 18-APR 101 15 Uen

CAMEL Feature1

Uploaded by

Copyright:

Available Formats

CAMEL Feature1

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CAMEL Feature1

Uploaded by

Copyright:

Available Formats

DESCRIPTION

Prepared (also subject responsible if other)

EAB/UG/BIF Richard Persson

173/19046-FAD 104 08 Uen

EAB/UG/BIF Mikael sterberg

Data Transcript Impacts . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 17

EAB/UG/BIF Richard Persson

173/19046-FAD 104 08 Uen

EAB/UG/BIF Mikael sterberg

Reviewed for CN 1.5,

Updated after internal

Basic Call State Model

Customised Application for Mobile Enhanced Logic

CAMEL Application Part

CAMEL Subscription Information

Enhanced Capability Set 1

Gateway Mobile services Switching Centre

General Packet Radio Services

Global System for Mobile communications

GSM Service Control Function

GSM Service Switching Function

Home Location Register

EAB/UG/BIF Richard Persson

173/19046-FAD 104 08 Uen

EAB/UG/BIF Mikael sterberg

Initial Detection Point

Integrated Services Digital Network

ISDN User Part

Mobile services Switching Centre

Message Transfer Part

Originating CAMEL Subscription Information

Public Land Mobile Network

Signalling Connection Control Part

Service Logic Program

Service Logic Program Instance

Short Meassage Service

Transaction Capabilities Application Part

Trigger Detection Point

Terminating CAMEL Subscriber Information

Visitor Location Register

EAB/UG/BIF Richard Persson

173/19046-FAD 104 08 Uen

EAB/UG/BIF Mikael sterberg

EAB/UG/BIF Richard Persson

173/19046-FAD 104 08 Uen

EAB/UG/BIF Mikael sterberg

Default call handling

BCSM Trigger Detection Point

CAMEL Capability handling

EAB/UG/BIF Richard Persson

173/19046-FAD 104 08 Uen

EAB/UG/BIF Mikael sterberg

Prerequisites on the network

EAB/UG/BIF Richard Persson

173/19046-FAD 104 08 Uen

EAB/UG/BIF Mikael sterberg

The operator-specific services are implemented using Intelligent Network (IN)

Incoming Call Screening where calls to a B-subscriber can be screened

Integration of Advice of Charge into CAMEL services.