camel feature1

DESCRIPTION 1 ( 34 )

EAB/UG/BIF Richard Persson 173/19046-FAD 104 08 Uen

EAB/UG/BIF Mikael Österberg 2002-04-26 PD2

Prepared (also subject responsible if other) No

Approved Checked Date Rev Reference

E

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 forCAMEL independantly of CAMEL phase and what is unique for differentCAMEL phases (1, 2 and 3)

Contents Page

1 Revision Information . . .. . .. . . .. . .. . . . . . . . . .. . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 2

2 Description .. . .. . . .. . .. . .. . .. . . . . . . . . . . . . . . . .. . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 22.1 Abbreviations . . .. . . .. . .. . .. . . . . . . . . .. . . . . . . . . .. . .. . .. . . . . . . . . .. . . . . . . . . . . . . . . . . . .. . 22.2 Concerned Nodes . .. . .. . .. . . . . . .. . .. . . . . . . . . .. . .. . .. . . . . . . . . .. . . . . . . . . . . . . . . . . . .. . 32.3 Concepts . .. . .. . .. . . .. . . . . .. . . . . . . . . .. . . . . . . . . .. . .. . .. . . . . . . . . .. . . . . . . . . . . . . . . . . . .. . 42.4 Prerequisites on the network . .. . .. . .. . . . . . .. . .. . .. . . . . . . . . .. . . . . . . . . . . . . . . . . . .. . 62.5 General .. . .. . .. . .. . . . . . . . . .. . . . . . . . . .. . . . . . . . . .. . .. . .. . . . . . . . . .. . . . . . . . . . . . . . . . . . .. . 62.6 CAMEL in GMSC and MSC/VLR .. . .. . .. . . .. . .. . .. . . . . . . . . .. . . . . . . . . . . . . . . . . . .. . 82.7 CAMEL in HLR .. . . .. . .. . .. . .. . . . . . .. . . . . . . . . .. . .. . .. . . . . . . . . .. . . . . . . . . . . . . . . . . . .. . 82.8 Extended CAMEL ... . .. . .. . . . . . .. . .. . . . . . . . . .. . .. . .. . . . . . . . . .. . . . . . . . . . . . . . . . . . .. . 92.9 Triggering .. . .. . .. . . .. . .. . .. . . . . . . . . .. . . . . . . . . .. . .. . .. . . . . . . . . .. . . . . . . . . . . . . . . . . . .. . 92.10 Traffic cases .. . .. . . .. . .. . .. . . . . . . . . .. . . . . . . . . .. . .. . .. . . . . . . . . .. . . . . . . . . . . . . . . . . . .. . 12

3 Data Transcript Impacts . .. . . .. . .. . .. . .. . . .. . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 173.1 General .. . .. . .. . .. . . . . . . . . .. . . . . . . . . .. . . . . . . . . .. . .. . .. . . . . . . . . .. . . . . . . . . . . . . . . . . . .. . 173.2 AXE parameters . . . .. . .. . .. . .. . . . . . .. . . . . . . . . .. . .. . .. . . . . . . . . .. . . . . . . . . . . . . . . . . . .. . 31

4 Miscellaneous Information . . .. . .. . .. . . . . . .. . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 334.1 Class . . .. . .. . .. . . . . . . . . . . . .. . . . . . . . . .. . . . . . . . . .. . .. . .. . . . . . . . . .. . . . . . . . . . . . . . . . . . .. . 33

5 References . .. . .. . . .. . .. . .. . .. . . . . . . . . . . . . . . . .. . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 34

A4 XSEIF R2






E

1 Revision Information

Revision Impacts Prepared Date

A New Document ERARDPN 00-05-30

B Small update ERATYDE 01-07-20

C Reviewed for CN 1.5,Minor update

ERATYDE 01-10-04

PD1 Update to CN2.0status. CAMEL Phase3 added

ERARDPN 02-03-22

PD2 Updated after internalreview

ERARDPN 02–04–26

2 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






E

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

2.2 Concerned Nodes

• GMSC

• MSC/VLR

• HLR

• SSF

• SCF






E

2.3 Concepts

This section aims to briefly describe some concepts in IN and CAMEL. It canbe used as a reference to the other sections.

Assisting gsmSSF

An assisting gsmSSF is used to provide remote user interaction required by theService Logic Program in the case when the initiating gsmSSF can not provideit. Only that sub-set of possible CAMEL Application Part (CAP) Call relatedoperations applicable to user interaction is applicable in a dialogue betweenthis 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 therequired activities necessary to establish and maintain communication paths forusers. It also determines when in the call process IN services in the gsmSCFcan 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 theinterconnections of subscribers or call parties.

Call Party

A call party represents a path between the gsmSSF and an addressablenetwork entity (e.g. an end user). Call connections created by the gsmSCFare identified by a party identity. The call is initiated by the Calling party and isreceived by the Called party.

CAMEL

CAMEL is a network feature which includes support in traditional GSMfunctional entities (HLR, GMSC and MSC/VLR) as well as functional entitiesoriginally defined in IN specifications (SSF and SCF). The feature addressesespecially the need for information exchange between the Home PLMN(HPLMN) and the Visited PLMN (VPLMN) when a HPLMN specific service shallbe provided to a subscriber when roaming outside the HPLMN.

CAMEL Application Part

The CAMEL Application Part (CAP) defines the interface between a gsmSSFand a gsmSCF.

CAMEL Subscription Information

The CSI is used to indicate that a subscriber has services which requireCAMEL support. It contains sequences with elements, each of them with thefollowing information:






E

• gsmSCF address

• Service Key

• Default call handling

• BCSM Trigger Detection Point

• DP Criteria

• CAMEL Capability handling

Detection Point

A DP is a point in the Basic Call Handler process at which a processing eventcan be reported to an gsmSCF or to internal parts in the gsmSSF. If the controlof the Basic Call Handler process is transferred to the gsmSCF when a DP isreported, the call processing in the gsmSSF is suspended until the gsmSCFreturns the control of the Basic Call Handler process to the gsmSSF. The callprocessing is retained by the gsmSSF until the next DP is encountered. Allpossible 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 ofsupplementary and custom service requests. It is intended to store servicescripts and service data, and be able to execute the Service Logic Programcontained in these scripts towards the gsmSSF.

GSM Service Switching Function (gsmSSF)

A function that interfaces the MSC/GMSC to the gsmSCF. The concept of thegsmSSF is derived from the IN SSF, but uses different triggering mechanismsbecause of the nature of the mobile network.

Initiating gsmSSF

This is a gsmSSF used to allow full control of the call by the gsmSCF. AllgsmSCF initiated call related CAP operations are applicable within a dialogueset up from an gsmSSF of this type to an SLPI running on an gsmSCF. For thepurpose of this specification, such a dialogue will be initiated as a result of anInitial 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 thegsmSSF which is needed for routing a call via IN.

Service Key

The Service Key can identify to the gsmSCF the service logic that it shouldapply. The Service Key is administered by the HPLMN, and is passed by theVPLMN/HPLMN to the gsmSCF. The Service Key is part of the CSI.






E

Service Logic

Service Logic is a sequence of processes and functions used to provide aspecific 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 featurestogether in a coherent manner. The services are provided by running a ServiceLogic Program, capable of controlling the call.

Service Logic Program Instance

The invocation and application of a particular SLP, in providing a service or aservice feature for a specific call/service attempt.

Service Script

One or more service building blocks collected together to implement a ServiceLogic Program.

Trigger Detection Point

When a DP is armed as a TDP (by CSI), and the DP is encountered, thegsmSSF will open a new dialogue towards the gsmSCF. For CAMEL services(using CAMEL Phase 1 or Phase 2) only the ’Collect Info’ and ’TerminatingAttempt Authorized Trigger Detection Points’ are valid. For CAMEL Phase 3, allDP stated in the CS-1 BCSM are supported.

Triggering

Triggering is when an Initial DP (IDP) operation is formed using parametersapplicable 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 tosupport operator-specific services that are not covered by standardized GSMservices, even while roaming outside the Home PLMN (HPLMN). The featureaddresses in particular the need for information exchange between the HPLMNand the VPLMN when a HPLMN specific service shall be provided to asubscriber roaming outside the HPLMN.






E

The operator-specific services are implemented using Intelligent Network (IN)principles, whereby the CAMEL network feature provides the mechanismsnecessary for integrating GSM and IN functional entities, including support forroaming. As CAMEL is based upon IN principles, it is possible to support alarge number of different services. Some examples of services possible withCAMEL include:

• Prepaid services.

• Private Numbering Plan for example included abbreviated dialing for suchservices as friends and family.

• Incoming Call Screening where calls to a B-subscriber can be screenedaccording to certain conditions (such as A-subscriber number, B-subscribernumber, location, etc.).

• Location and time dependent routing where calls from, or to, an end-userare 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 functionalentities (HLR, GMSC and MSC/VLR) as well as functional entities originallydefined 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 onthe function ’Support of CAMEL phase 1’. The major additions to the CAMELstandard in phase 2 is:

• The originating CAMEL Subscription Information (O-CSI) contains moretriggering criteria and the required CAMEL phase information is included.

• The MSC supports the control of Advice of Charge by the gsmSCF. Thisenables, for example, IN-controlled real time prepaid solutions.

• Requirements to support short numbers for call forwarding (e.g. from aprivate numbering plan).

• Support for requesting and reporting of call start time, stop time, durationetc. for charging purposes.

• Support for writing free format data into MSC and GMSC charging records.

2.5.3 Additions to CAMEL phase 3

The funtion ’Support of CAMEL Phase 3’ is an optional addition andenhancement on the function ’Support of CAMEL Phase 2’. The majorenhancements are listed here:

• Support for mobile originated SMS in MSC as well as support for SMS-CSIin the HLR. The MSC can notify the gsmSCF, if the subscriber originates






E

a short message. The gsmSCF may change the destination addressand/or the service centre address.

• Support of additional new trigger detection points. With CAMEL Phase 3all CS1 trigger detection points are supported.

• Ability to output service-specific free-format billing data directly to the calldata record in either HPLMN or VPLMN.

• Support for GPRS-CSI in the HLR.

2.6 CAMEL in GMSC and MSC/VLR

When CAMEL is supported in GMSC, the GMSC may receive an Originatingand/or Terminating CAMEL Subscription Information (O/T-CSI) from the HLRas part of terminating call handling.

In MSC/VLR the Originating CAMEL Subscriber Information (O-CSI) may bereceived as part of the subscriber data from HLR in the Insert Subscriber Datamessage (for example at Location Update or Update of subscriber data). TheMSC 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 ofthe gsmSSF is to be invoked. The O-CSI is used when an originating CAMELservice 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 theGMSC. The T-CSI is used when a terminating CAMEL service is to be invokedin the GMSC for a terminating call. SMS-CSI is used when an originatingCAMEL service is to be invoked for an user originated SMS.

The MSC and the GMSC support conditional triggering of the originatedCAMEL service. The triggering can be dependent on the following conditions:

• Call type (originating/forwarded)

• Whether the leading digits of the called party number match one numberin the white (or black) list.

• Whether the Basic Sevice Code matches one in a list of Basic ServiceCodes.

• Whether the called party number length matches a certain length.

2.7 CAMEL in HLR

The HLR stores the CAMEL Subscriber Information (CSI). TheO/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 handlingparameter indicating the required handling in case an error occurs in thecommunication between the gsmSSF and the gsmSCF. It also contains theCAMEL phase number and CAMEL Trigger Detection Point (TDP).






E

The O-CSI and SMS-CSI is sent to the VLR at Location Update or if the CSIdata is updated in the HLR. The O-CSI and T-CSI is sent to the GMSC whenthe HLR responds to the message Send Routing Information triggered by theGRI route in the GMSC. GPRS-CSI is tranferred from the HLR to SGSN for aGPRS 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 inE.164 format from a CAMEL subscriber with O-CSI. The forwarded-to numbercan be sent by the HLR towards the VLR (or GMSC). If the forwarded-tonumber 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 comparedto CS1 and CS1+ and is therefor not as powerful. Extended CAMEL is anenhancement of CAMEL with the ability to use CS1 or CS1+ signalling insteadof CAP. This increase the possibilities for the IN services, i.e. more advancedservices can be provided. If CS1 or CS1+ is used, the IN services will only workwithin the network (PLMN) because there is no longer a standard protocol.

The CAMEL subscriber data consists of CSI plus an extension. This extensionexists as default values for standard CAMEL but is changeable with commandHGCEC for Extended CAMEL. There are several possibilities with this extendedinformation. For example can special CAMEL OICK/TICK- and OIN/TIN-valuesbe used in the same manner as ordinary OICK/TICK and OIN/TIN in standardIN.

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 AXEparameters (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 CallState Model (BCSM). The BCSM consists of detection points (DPs) in a callwhere the gsmSCF can be invoked or the gsmSCF can influence the callwith related operations. Two BCSMs exist, one for originating (O_BCSM) andone 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 handlingare prepared at the time of invoking gsmSSF. An important part of this is armingthe 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






E

CAMEL services, some of the triggering data is received from the HLR in theCSI, 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 fromthe HLR and if certain conditions apply, the TDPs can be disarmed again. Thisis 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 InitiatingDialogue or an Assisting Dialogue depending upon the role the gsmSSF is toperform. An Initiating Dialogue is used when an association between a calland a SLP running on a gsmSCF needs to be created. An Assisting Dialogueis used when the gsmSCF orders the Initiating gsmSSF to link to anothergsmSSF (the Assisting gsmSSF) in order to provide additional resources thatthe Initiating gsmSSF lacks.

2.9.2 Service invocation

If IN involvement is required in a call, an IN Service Trigger (IST) is pointedout (outside the gsmSSF). For CAMEL, the IST is pointed out in the MIN routedata. When this happens, the gsmSSF is invoked by a routing case pointing toa 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 beset up in a trigger table that links IST and TDP (SHISTTOTDP). If this is notproperly done, the call will be released. The TDP to be armed for the CAMELservice is received in the CSI, and only that TDP is armed (regardless of anyother TDPs defined in the trigger table). The only allowed TDPs for CAMELphase 1 and 2 is TDP2 (collect information) for originating calls and TDP12(terminating attempt authorized) for terminating calls. For CAMEL Phase 3additional 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) togetherwith, for example gsmSSF type (initiating or assisting).

Once the applicable TDPs have been armed, the call progresses. The gsmSSFwill be informed by the Basic Call Handling when a DP is encountered duringthe 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 anInitiating or an Assisting gsmSSF.

Triggering

The InitialDP (IDP) operation has only one mandatory parameter, which isservice key (SK) and is supplied as part of the CSI. This parameter identifiesthe SLP to be run at the gsmSCF.

Some of the optional parameters in IDP must be fetched from the Basic CallHandling by the triggering function. All optional parameters (including extensionfields) must be initiated from trigger tables (SHINS, SHEXLIST), and some






E

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 SHEPPand 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, furtherinstructions for the gsmSSF will be received from the gsmSCF.

Routing

Different Service Logic Programs (SLPs) running on different gsmSCFs can beassociated with different SKs (supplied in CSI). The SK is required in order toreach the correct SLP. To reach the correct gsmSCF, the gsmSCF address isalso needed. This address is provided in the CSI.

In the SHTDP trigger table, it is indicated which protocol and which type ofTCAP to be used in the communication between gsmSSF and gsmSCF. ForCAMEL, CAP protocol will be used.

In order to route between the gsmSCF and the gsmSSF, the SCCP called andcalling party address must be specified.

The SCCP called party address will be received in the CSI. It is also possible tospecify a SubSystem Number (SSN) to be used together with this address inthe SHTSD trigger table. Otherwise Global Title routing without SSN applies tothe information received from CSI.

The SCCP calling party address is defined in the SHTSO trigger table. This willeither be Signalling Point Code and SSN, Global Title and SSN or just GlobalTitle. If used, the Global Title address is explicitly defined in SHTSO table.

Trigger tables

The trigger tables are connected according to figure 1 . The connectionbetween different tables are made with special IDs. Then the tables are loadedinto the exchange, they should be loaded in reverse order compared to the flowof information.






E

Figure 1 Trigger tables

Note that the only input into the tables is the IST value. For CAMEL, ISTis set in the MIN route data. The output consists of a lot of data, see thecorresponding application information for each table.

2.10 Traffic cases

2.10.1 Originating CAMEL

Figure 2 Originating CAMEL

2.10.1.1 From Mobile Station to MSC/VLR

Step 1 (figure 2 ).






E

A subscriber with originating CAMEL subscription dials a B-number. TheB-number is sent to the MSC/VLR via BSS.

When a call from a mobile subscriber is received at the incoming access andthe mobile subscribers data contains O-CSI then route data determines if, forthe intelligent network operator group connected to the subscribers IMSI, anintelligent 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. Subscriberswithin this range will use a MIN-route with miscellaneous information number 2equals to 2 (MIS2=2). The parameter CAMEL indicates the CAMEL versionsupported 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 isanalyzed 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;






E

The connection between the existing source system (XSS) and the gsmSSFis made according to 66/190 46-FAD 104 08 [ref 8]. If an integrated SSF isused, a APC-link (AM Protocol Carrier) handles the communication betweenthe 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 isimplemented in form of trigger tables. This process is described in sectionchapter 2.9 . At the triggered detection point (TDP) the gsmSSF invokes thegsmSCF. The TDP is part of the CAMEL subscription information (CSI) andindicates where in the BCSM the gsmSCF is to be contacted. The dialoguebetween the gsmSSF and gsmSCF is CAP messages (CAMEL ApplicationProtocol) and the gsmSCF is connected with its global title address which alsois a part of the CSI. This makes it possible to establish a control connectionwith 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 callaccording to the SLP. This could for example result in a call forward numberor 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 thegsmSSF (see example 3 ).


SHRPI:OSR=OUTGOINGROUTE;SHRSC:PAR=BO, VAL=74, SCAP=1;SHRPE;






E

2.10.2 Terminating CAMEL

Figure 3 Terminating CAMEL

2.10.2.1 Incoming call in GMSC

Step 1 (figure 3 )

A call to a subscriber with terminating CAMEL subscription have reached theGMSC. 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-CSIand O-CSI is sent if both exist. A terminating CAMEL service could be callscreening 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 theIMSI-analysis (see example 4 ). The B-number is analyzed in the B-numberorigin defined by parameter BO in the MIN route. The IST is indicated by theMIS5 parameter in the route.






E


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 gsmSSFis made according to 66/190 46-FAD 104 08 [ref 8]. If an integrated SSF isused, a APC-link (AM Protocol Carrier) handles the communication betweenthe two AMs (XSS-SSF).

The interrogation towards the gsmSSF is done in order to trigger theterminating CAMEL service at this stage. If also a originating service exists forthe 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 (seesection 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 chapter2.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. Anintegrated SSF will used a predefined APC-link for connection between the twoAMs (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 MAPmessage is sent for the second time.

If both T-CSI and O-CSI exists, another interrogation towards the gsmSSF willbe 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 sentto 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 )






E

The MSRN is returned back to the GMSC and is analyzed in the B-numberorigin 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 BSSto the CAMEL subscriber.

3 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 maximumnumber of parallel CAP dialogues.

SAAII:SAE=604,NI=100,BLOCK=SHPM2;SAAII:SAE=604,NI=100,BLOCK=SHPM3;SAAII:SAE=604,NI=100,BLOCK=SHPM4;

SAE 604 for block SHPM2, SHPM3 and SHPM4 is traffic sensitive and setsthe maximum number of parallel SSF-SCF dialogues using CAMEL Phase1 (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 HomeLocation 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 internalISUP messages from call legs or INAP operations from SCP.






E

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 mobilesubscribers. One individual is seized for each SMS-CSI data set received fromthe Home Location Register (HLR) for a visiting mobile subscriber.

SAAII:SAE=700,NI=100,BLOCK=SHSMS;SAAII:SAE=701,NI=100,BLOCK=SHSMS;SAAII:SAE=702,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 !EXRBC:R=10MIN2,BO=70,MIS1=1,MIS2=2;

EXROI:R=11MIN2,DETY=MIN, FNC=11; ! O-CAMEL IN GMSC CFU !EXRBC:R=11MIN2,BO=70,MIS1=1,MIS2=2;

EXROI:R=12MIN2,DETY=MIN, FNC=12; ! T-CAMEL IN GMSC !EXRBC:R=12MIN2,BO=73,MIS1=1,MIS2=2;

Definition of MIN routes for CAMEL at call from MS, at Call Forwardingconditional (in MSC/VLR), at Call Forwarding Unconditional (in GMSC) andterminating respectively. Observe that the parameter MIS5 (that is mandatoryfor CAMEL) can not be set before the trigger tables are loaded and is therefornot 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.






E

!* 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 theSSF exists. Note that B-number and charging origins after IN interrogation isset 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;






E

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;! Terminating Traffic !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 *!! Originating Traffic !DBTRI;DBTSI:TAB=SHTDP,TDPID=10,DIAGTYP=1,PROTI=2,TDPSID=10,

TINSID=10;DBTRE:COM;! Terminating Traffic !DBTRI;






E

DBTSI:TAB=SHTDP,TDPID=32,DIAGTYP=1,PROTI=2,TDPSID=32,TINSID=32;

DBTRE:COM;

!* TABLE SHTNS - SSF ROUTE AND CHARGING CASES *!! Originating Traffic !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;! Terminating Traffic !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 *!! Originating Traffic !DBTRI;DBTSI:TAB=SHIST,IST=210,TNSID=10,BCSMTYP=ORIG,SSFTYPE=I,NUMDIG=7;DBTRE:COM;! Terminating Traffic !DBTRI;DBTSI:TAB=SHIST,IST=232,TNSID=32,BCSMTYP=TERM,SSFTYPE=I;DBTRE:COM;

!* TABLE SHISTTOTDP - ASSOCIATE IST WITH TDP *!! Originating Traffic !DBTRI;DBTSI:TAB=SHISTTOTDP,IST=210,TDPNO=DP2,TDPID=10;DBTRE:COM;! Terminating Traffic !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;EXRBC:R=10MIN2,MIS5=210;EXRBC:R=11MIN2,MIS5=210;EXRBC:R=12MIN2,MIS5=232;

Subfile 15400: Route Analysis

ANRSI:RC=25,R=SSFDJO1,SP=MM1;






E

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. Aftermodification, the numbering plan indicator is set to E.164 and the nature ofaddress 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, L=5-20, RC=25;ANBSI:B=70-01, L=5-20, RC=25;ANBSI:B=70-02, L=5-20, RC=25;ANBSI:B=70-03, L=5-20, RC=25;ANBSI:B=70-04, L=5-20, RC=25;ANBSI:B=70-05, L=5-20, RC=25;ANBSI:B=70-06, L=5-20, RC=25;ANBSI:B=70-07, L=5-20, RC=25;ANBSI:B=70-08, L=5-20, RC=25;ANBSI:B=70-09, L=5-20, RC=25;ANBSI:B=70-10, L=5-20, RC=25;ANBSI:B=70-11, L=5-20, RC=25;ANBSI:B=70-111, L=5-20, RC=25;ANBSI:B=70-112, L=3, F=30;ANBSI:B=70-113, L=5-20, RC=25;ANBSI:B=70-114, L=5-20, RC=25;ANBSI:B=70-115, L=5-20, RC=25;ANBSI:B=70-116, L=5-20, RC=25;ANBSI:B=70-117, L=5-20, RC=25;ANBSI:B=50-118, L=5-20, RC=25;ANBSI:B=70-119, L=5-20, RC=25;ANBSI:B=70-13, L=5-20, RC=25;






E

ANBSI:B=70-14, L=5-20, RC=25;ANBSI:B=70-15, L=5-20, RC=25;ANBSI:B=70-16, L=5-20, RC=25;ANBSI:B=70-17, L=5-20, RC=25;ANBSI:B=70-18, L=5-20, RC=25;ANBSI:B=70-19, L=5-20, RC=25;ANBSI:B=70-2, L=5-20, RC=25;ANBSI:B=70-3, L=5-20, RC=25;ANBSI:B=70-4, L=5-20, RC=25;ANBSI:B=70-5, L=5-20, RC=25;ANBSI:B=70-6, L=5-20, RC=25;ANBSI:B=70-7, L=5-20, RC=25;ANBSI:B=70-8, L=5-20, RC=25;ANBSI:B=70-90, L=5, F=30;ANBSI:B=70-91, L=5-20, RC=25;ANBSI:B=70-92, L=5-20, RC=25;ANBSI:B=70-93, L=5-20, RC=25;ANBSI:B=70-93, L=5-20, RC=25;ANBSI:B=70-95, L=5-20, RC=25;ANBSI:B=70-96, L=5-20, RC=25;ANBSI:B=70-97, L=5-20, RC=25;ANBSI:B=70-98, L=5-20, RC=25;ANBSI:B=70-99, L=5-20, RC=25;

ANBSI:B=73-4670, RC=25;

ANBSI:B=74-00, M=2, BNT=1, F=32;ANBSI:B=74-01, BNT=2, F=30;ANBSI:B=74-02, BNT=2, F=30;ANBSI:B=74-03, BNT=2, F=30;ANBSI:B=74-04, BNT=2, F=30;ANBSI:B=74-05, BNT=2, F=30;ANBSI:B=74-06, BNT=2, F=30;ANBSI:B=74-07, BNT=2, F=30;ANBSI:B=74-08, BNT=2, F=30;ANBSI:B=74-09, BNT=2, F=30;ANBSI:B=74-1, BNT=2, F=30;ANBSI:B=74-2, BNT=2, F=30;ANBSI:B=74-3, BNT=2, F=30;ANBSI:B=74-4, BNT=2, F=30;ANBSI:B=74-5, BNT=2, F=30;ANBSI:B=74-6, BNT=2, F=30;ANBSI:B=74-7, BNT=2, F=30;ANBSI:B=74-8, BNT=2, F=30;ANBSI:B=74-9, BNT=2, F=30;

All calls except emergency calls are routed to SSF via RC 25. After INinterrogation, the calls is forwarded to standard trees.

Subfile 27000: Deblocking of Routes






E

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 SCCPlayer in the home network.

C7GCI:GTRC=8,PSP=OWNSP;C7GSI:TT=3,NP=1,NA=4,NS=467075709,GTRC=8;

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






E

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, BLOCK=HCSID, NI=15000;SAAII:SAE=603, BLOCK=HCSID, NI=15000;SAAII:SAE=604, BLOCK=HCSID, NI=15000;SAAII:SAE=605, BLOCK=HCSID, NI=15000;SAAII:SAE=606, BLOCK=HCSID, NI=15000;SAAII:SAE=607, BLOCK=HCSID, 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 PLMNshould be included here.






E

HGRCI:AREA=4-46 70, CHAR=OCSIPH1;HGRCI:AREA=4-46 70, CHAR=OCSIPH2;HGRCI:AREA=4-46 70, CHAR=OCSIPH3;HGRCI:AREA=4-46 70, CHAR=EXTCAMEL;

HGRCI:AREA=4-44, CHAR=OCSIPH1;HGRCI:AREA=4-44, CHAR=OCSIPH2;HGRCI:AREA=4-44, CHAR=OCSIPH3;

HGRCI:AREA=4-49, CHAR=OCSIPH1;HGRCI:AREA=4-49, CHAR=OCSIPH2;HGRCI:AREA=4-49, CHAR=OCSIPH3;

Roaming Area charactersitics for originating CAMEL subscriber data andextended CAMEL data.

Subfile 80000: Subscriber Data

HGSDC:MSISDN=46707679001,SUD=OCSI-1;HGSDC:MSISDN=46707679001,SUD=TCSI-1;HGSDC:MSISDN=46707679001,SUD=OSMCSI-1HGSDC: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 theconnection 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 ifconnection 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) isused. In case of error in the dialogue between GSM service control functionand 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 1indicates Detection Point attach. CAMEL Phase 3 is used (CCH=3) and in case






E

of error in the dialogue between GSM service control function and GSM serviceswitching function the call is released (DEH=0).

If Extended CAMEL is used, additional subscriber data is defined here withcommand HGCEC.

3.1.3 SCF


The size alterations described below is necessary for implementing CAMELPhase 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 !! - traffic sensitive - !!------------------------------------------------------!

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 !! - traffic sensitive - maxval=65535 !!------------------------------------------------------!

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 !! - traffic sensitive - !!------------------------------------------------------!






E

SAAII:SAE=670, NI= 200, BLOCK=SSCDO;! Number of single CDR’s opened EXT.min:0 !! for a SLPI. An SLPI can have max:500 !! up to 30 single CDR’s open at RED.min:0 !! any time (= 30 * SAE-500/SSCDO). max:500 !! - traffic sensitive - maxval=65535 !!------------------------------------------------------!

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 SLPI’s 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 !!------------------------------------------------------!






E

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 !! - traffic sensitive - max:65535 !!------------------------------------------------------!

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 !! - traffic sensitive - max:65535 !!------------------------------------------------------!

SAAII:SAE=760, NI= 10, BLOCK=SSTAB2;! Number of origin data indiv. EXT.min:0 !! associated with the data max:65535 !! modules for controltype RED.min:0 !! ’NRTAB2’. max:65535 !!------------------------------------------------------!

SAAII:SAE=761, NI= 10, BLOCK=SSTAB2;! Number of analysis tree indiv. EXT.min:0 !! associated with the data max:65535 !! modules for controltype 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 !! - traffic sensitive - max:65535 !!------------------------------------------------------!

The size alterations described below is introduced for CAMEL Phase 2.






E

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; !TERM IN OWN NODE !C7GCI:GTRC=2,PSP=3-300,PTERM; !TERM IN MSC1 !C7GCI:GTRC=3,PSP=3-300,PINTER; !MSC1 INTERMEDIATE!

Definition of SCCP routing case for terminating in own node, routing casetowards SSF in MSC1 and a routing case for access to the internationalnetwork.






E

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.

C7GSI:TT=0,NP=1,NA=4,NS=44,GTRC=3; !U.K. SSF !C7GSI:TT=0,NP=1,NA=4,NS=49,GTRC=3; !GERMAN SSF !C7GSI:TT=0,NP=1,NA=4,NS=61,GTRC=3; !AUSTRALIAN SSF !C7GSI:TT=0,NP=1,NA=4,NS=65,GTRC=3; !SINGAPORIAN SSF!

Definitions of number series for other operators with CAMEL roamingagreement.

3.2 AXE parameters

Some AXE parameters are password protected and can only be accessedwith 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 ofLocation Numbers.

DBTRI;DBTSC:TAB=AXEPARS,SETNAME=GSMMDSF,NAME=MSCNF336,VALUE=1;DBTRE:COM;

Parameter MSCNF336 indicates the availability of support related to Provisionof 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.






E


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 withintelligent network category key applies for all circuit switched basic servicesexcept emergency calls or only for telephony and auxiliary telephony.


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.


Parameter GMSCNF499 indicates if Extended CAMEL is supported. In thisexample only standard CAMEL is supported.


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 tobe barred in the SSF.

3.2.3 HLR

DBTRI;DBTSC:TAB=AXEPARS,SETNAME=GSMHRSF,NAME=HLRNF496,VALUE=1;DBTRE:COM;






E

Parameter HLRNF496 is the main switch for enabling CAMEL in the HLR.


Parameter HLRNF498 indicates support of extended CAMEL.


Parameter HLRNF746 indicates support of CAMEL phase 2.

4 Miscellaneous Information

4.1 Class

Support of CAMEL Phase 2 is a standard optional feature.






E

5 References

a Service Switching function CAMEL Phase 2, General[1] 118/155 17-APR 101 15 Uen

b Mobile Access Support for CAMEL in MSC/VLR[2] 87/155 17-ANT 292 01/5 Uen

c CAMEL Support in GMSC[3] 90/155 17-ANT 292 01/5 Uen

d CAMEL Phase 2 in HLR[4] 193/155 17-ANT 238 01 Uen

e CAMEL Phase 2 SS8.0 (CME20/CMS40)[5] LK/NX 1056-074 Uen

f Service Switching Function: CAMEL Phase 2, Basic Call Handling[6] 126/155 17-APR 101 15 Uen

g Service Switching Function CAMEL Phase 2, Triggering[7] 157/155 17-APR 101 15 Uen

h IN Service Triggering in GMSC/MSC/VLR and SSF[8] 66/190 46-FAD 104 08 Uen

i Home Location Register, CAMEL Subscription Data, Initiate (HGCMI)[9] 1/190 82-CNT 238 0124 Uen

j Home Location Register, CAMEL Extended Information, Change(HGCEC)[10] 5/190 82-CNT 238 0124 Uen

k SSFAM, Service Switching Function Changeable ExchangeAdaptation[11] 2/155 18-APR 101 15 Uen

camel feature1

Documents

extended camel

eabugbif richard persson

camel phase3 addederardpn

ueneabugbif mikael sterberg

date rev referencee2

data transcript impacts

concerned nodes

1cs1 enhanced capability