Customer Product Information 1/155 42-HSC

120 06/2 Uen PA9

Adaptation Directions Charging System 2.0
Copyright

© Ericsson AB 2003 - All rights reserved

Disclaimer

No part of this material may be reproduced in any form without the written
permission of the copyright owner.

The contents of these documents are subject to revision without notice due to
continued progress in methodology, design and manufacturing. Ericsson shall have
no liability for any error or damage of any kind resulting from the use of these
documents.

Contents
1 Introduction
1.1 Purpose and Scope

2 General
2.1 Charging System basic concepts

3 Charging System Traffic Cases

3.1 PrePaid Originating Traffic Case
3.2 PrePaid Terminating Traffic Case
3.3 PrePaid Roaming Originating Call (CAMEL PH2)
3.4 Prepaid Roaming Forwarding Call handled by the MSC
3.5 PrePaid Roaming Forwarding Call handled by the GMSC
3.6 PrePaid Roaming Terminating Call
3.7 PrePaid Roaming Call (CAMEL PH1)
3.8 Charging System Originating SMS
3.9 Charging System Terminating SMS
3.10 USSD Callback
3.11 USSD User Account Refill

4 Charging System Core

4.1 Introduction
4.2 MSC/SSF Exchange Data
4.3 HLR Exchange Data
4.4 SCP/gsmSCF Exchange Data

5 USSD
5.1 Introduction
5.2 MSC Exchange Data
5.3 HLR Exchange Data
6 SMS charging
6.1 Introduction
6.2 MSC Exchange Data
6.3 Parameter settings in MSC
6.4 HLR Exchange Data
6.5 SCP Exchange Data

7 Roaming with USSD Call back

7.1 Introduction
7.2 MSC/SSF Exchange Data
7.3 HLR Exchange Data

8 Roaming with CAMEL (PH1 & PH2)

8.1 Introduction
8.2 MSC/gsmSSF-(HPLMN) Exchange Data
8.3 MSC/gsmSSF-(VPLMN) Exchange Data
8.4 HLR-(HPLMN) Exchange Data
8.5 HLR-(VPLMN) Exchange Data
8.6 SCP/gmSCF-(HPLMN) Exchange Data

9 AIR
9.1 Introduction
9.2 SCP Exchange Data
9.3 MSC Exchange Data
9.4 HLR Exchange Data

10 Optimized Signalling for Bonus on Incoming Calls (BIC)

10.1 Introduction
10.2 MSC/SSF Exchange Data
10.3 HLR Exchange Data

11 Mobile Number Portability

11.1 Introduction
11.2 SCP Node Exchange Data.
11.3 FNR/MSC Node Exchange Data

12 Glossary

13 Reference List

1 Introduction

1.1 Purpose and Scope

The purpose of this Adaptation Directions is to provide an exchange data guide when
putting Charging System 2.0 into operation.

This document will also describe the main requirements for the integration of other
systems. The mobile systems included in this document are CME20/CMS40.
The following is included:

 Exchange data in MSC/VLR and SCP for GSM R9.1.

 Exchange data needed in HPLMN HLR, MSC/SSF and SCP/gsmSCF for feature
related functions such as Roaming with USSD Call back.
 Old functions such as USSD Balance on Demand, USSD voucher Refill
and SMS triggering are also described.
 Charging of a PrePaid System, installation of size alterations, end of
selections and announcements.
 Exchange data needed in HPLMN and VPLMN MSC/VLR/gsmSSF related to the
Roaming feature (CAMEL PH1 & PH2).

2 General
The purpose of the Adaptation Directions documentation is to help the operators to
adapt their existing GSM AXE network when taking Charging System into operation.
It will also describe the main requirements for the integration of other network
elements with the AXE network elements.

Note:
This Adaptation Directions is based on a test plant with specific data
loaded and specific Network Plan. Since data in each exchange and
networks can be different, a data transcript scenario is needed as a reference
guide in order to find all parameters mentioned from now on into ADI.

A diagram with an overview picture over Charging System nodes,

signalling and protocols used within Charging System service can be
found in System Description, Reference [1].

2.1 Charging System basic concepts

Charging System is a system that provides real time charging of

subscribers in mobile telephony networks. The system allows roaming in
the home network as well as roaming in a visiting network. Charging
System also offers the possibility of post processing services.

For a higher understanding in the next chapters, several concepts

widely used in this document must be known.

2.1.1 Size Alteration Data

Size alteration is the name of the function used to change the file
sizes in the data store of the central processor. The changes are
normally initiated by a change in the size of the exchange or in the
traffic intensity of the exchange. Examples of these changes in the
exchange are addition of more subscribers, more services or more trunk
lines added.
 When a Charging System solution is being set up, some Size Alterations
are necessary in HLR, SCF and SSF to support the service function. The
affected part of the AXE system is the data store in the CP.

In order to find the block or the blocks that are affected by a size
alteration, the AXE system uses a numbering of the size alteration
cases. This number is referred to as "size alteration event" or just SAE.
There are two different types of size alterations in the AXE:

 Global size alteration event. These events will affect files in

more than one block.
 Local size alteration event. These events will only affect one
block in the exchange.

More details about SAEs for all nodes can be found in the suitable
MODEL DT for respective node, Model DT for MSC/SSF, Reference [2],
Model DT for stand alone SCP, Reference [3], Model DT for HLR,
Reference [4].

2.1.2 Charging Data

This chapter describes the principles for charging in PrePaid. The

complexity of the given information is graded from general to more
detailed

Note:
A description of the charging function in GSM 900/1800 UMTS from a data
transcript point of view can be found in Charging, Reference [5] (document
can be found in DT INFOMODEL).

2.1.2.1 Charging Principles

The main difference for the charging in a service like

PrePaid from a normal post paid system is that charging
has to be performed in real time. In most of the cases the
PrePaid subscriber is unknown for the operator and the
charging of these calls are based on an amount of money
paid in advance.

This allows the PrePaid subscriber to make and receive

calls as long as their PrePaid account is provisioned. When
a CS account expires it can be either refilled or
terminated.

2.1.2.2 PrePaid Charging (SDP)

The SDP controls the charging. All tariffs and charging data
are stored in a Tariff-structure in the SDP . T here can be
up to 10 000 Subscr iber Ser vice Classes and 100 Tariff-
structures.
The following call and service types can be charged:

 originating
 terminating
 originating forwarded
 roaming originating
 roaming forwarded
 roaming terminating
 SMS originating
 SMS terminating

In order to do that, the state of the account is checked in

the SDP. The PrePaid subscription contains an amount of
money which is converted into time in the interrogation
between the SCP and SDP. It is up to the service operator
to decide how this conversion should be executed. For
more information, see User Guide for Mobile SSF Charging,
Reference [6].

2.1.2.3 PrePaid charging (SSF)

When a PrePaid user makes a call, the SSF will receive the
charging information, that is, money converted into time.
This information is received with an Apply charging (ACH)
INAP operation from SCF. Basically, SSF will receive two
parameters, Accumulated Time and a Time Limit, were the
Time Limit corresponds to the Deduction Time defined
in the Service Class in SDP. SCF will expect an answer
(with Apply Changing Report, ACR) in the two following
cases:

The call is finished:

In this case the number of used seconds are sent back to

the SCF in the ACR operation. The SCF then sends a
final report to the SDP and it will update the subscriber
account.

The Time Limit is reached:

In this case the SSF sends to the SCF an ACR, indicating

that the Time Limit is reached. The SCF sends an
interrogation to the SDP asking for more time.

If there is enough money on the account, the SCF sends a

new ACH containing a new Time Limit to the SSF.

If there is not enough money on the account, the

subscriber will be warned by an announcement that is
heard by the subscriber only, not by the called party. The
subscriber will then have time to terminate the
conversation in a controlled way. If the subscriber decides
to continue talking there will be another announcement
after the call has been disconnected (Call cut off in SCF).
See Figure 1, Operations between SSF-SCF.

If CAMEL Phase 2 is used a tone is played 30 seconds

before the balance reaches zero.

Figure 1 Operations between SSF-SCF

Function interworking

At call set up, when an Apply Charging info is received in

SSF, the block for charging purpose in SSF is seized
(SHCHM: SSF charging manager).

Basic charging units are generated continuously in block

CHUPAT (subsystem CHSS). When a call is initiated, a CDR
is seiz ed in CHUPAT. If the seizure was successful,
CHUPAT will be informed about the CU method generation,
CU duration, and the need of real time charging (Signal
STORECHUDATA). According to this inf o, CHUPAT will
gener ate the CU and send them to SHCHM with signal
CHUNITS.

As long as SHCHM is receiving CU, it checks if the offset or

remaining CU limit is reached and if it is the case, the
corresponding INAP operation is sent to SCP.

This function has been very simplified. If more

information is needed, please see User guide for traffic
Setup of IN calls in AXE 106 Mobile System, Reference [7].
2.1.2.4 Charging with Toll T icketing Records

The charging information written in TT Records is not

directly used for charging of the PrePaid subscriber. The
main reason to this is that PrePaid in the SDP will not be
informed in real time about the contents of these TT
Records. Nevertheless, it can be very useful to produce
them, because they can be a proof for the operator in case
of complaints on call charging. The TT Records can be
interesting as well for statistic purposes even if statistics
exist already in SDP; a lot of information in these records,
particularly the ones related to MSC, is not available in SCP
node.

Charging Solution for PrePaid (TT Records)

It is up to the operator to decide what kind of information

should be in the TT Record. But the operator should be
aware that it will be almost impossible to have a charging
analysis corresponding exactly to the analysis done in SDP.
The main reason is that each subscription is related to a
particular service class with a tariff depending on
parameters unobtainable from MSC side. For example, in
the SDP there is a list containing free numbers, which are
unknown in MSC.

For all these reasons, it is wise to simplify the charging in

MSC, as much as possible. For example, a CC related to a
traffic case for all the PrePaid calls can be reserved
and it is up to the post processing system to calculate how
much the call has really cost according to service class, B-
number, the duration and the time where the call has been
done (in fact, according to the SDP calculation).

When a call data record has been generated, it is sent to

the application module FOAM (Formatting and output
application module). The FOAM consists of two functions,
Common Charging Output (CCO) for output of data to IOG
or Adjunct Processor and the Source Filtering Function
providing possibility to filter the charging data. If the
data are supposed to be output to the IOG, files will
have to be defined on the hard drive for storage of the
call data records. Two sequential files are created f or
this pur pose.

 Define TTFILEs for the CDRs:

< INMCT:SPG=0;

<
INFII:FILE=TTFILE00,VOL=EXCHVOLUME,RLENGTH
 =2048,TYPE=SEQ,SIZE=200,EXP=200,FCLASS=CM
P;

<
INFII:FILE=TTFILE01,VOL=EXCHVOLUME,RLENGTH
=2048,TYPE=SEQ,SIZE=200,EXP=200,FCLASS=CM
P;

< END;

 Infinite Sequential Sub &filig;les are de&filig;ned to

guarantee effective &filig;le handling. Different
parameter settings are required depending on
whether the &filig;les are supposed to be stored on
magnetic tape or output on a data link. Parameter
MAXSIZE means that as soon as the size of maxsize
records is reached, the &filig;le is closed and
reported to the FPU (File Processing Utility) for
output. Parameter MAXTIME means that the same
thing occurs after maxtime (MAXTIME is the
maximum active time for a sub&filig;le in minutes).
Parameter NSUB speci&filig;es the maximum
number of simultaneously existing sub&filig;les
within the original TTFILE. Notice that the
in&filig;nite &filig;le function is using circular
logging.

< IOIFI:FILE=TTFILE00, NSUB=9999,

MAXSIZE=maxsize;

< IOIFI:FILE=TTFILE01, NSUB=9999,

MAXSIZE=maxsize;

or

< IOIFI:FILE=TTFILE00, NSUB=9999,

MAXTIME=maxtime;

< IOIFI:FILE=TTFILE01, NSUB=9999,

MAXTIME=maxtime;

 Next, the FPU function is speci&filig;ed. It will be

done in different ways depending on whether the
data is to be output to external media or data link.
For output, parameter DESTis a user de&filig;ned
identi&filig;er to which the &filig;les are tied to
when being output; EQUIP speci&filig;es output
equipment (NOLINK means external media and MTP
is protocol for data link transfer); FILEID2 is a
&filig;le identi&filig;er used to change the name of a
sub &filig;le when dumping it on external &filig;le;
 RULE2 decides how the sub &filig;les should be
named on it; REMOVE (expressed as hhhmm)
means the time that must pass between the
moment the &filig;les are dumped or transferred
and the moment they are removed from the hard
disk. Parameters FILEID1 and RULE1 are used
instead when data link output is chosen; in that
case, TRANSCOND=AUTO means that the &filig;les
are transmitted automatically on the data link.

< INMCT:SPG=0; TT output over external media

<
INFDI:FILE=TTFILE00,DEST=dest,EQUIP=NOLINK,
FILEID2=TTFILE00,RULE2=1;

<
INFCC:FILE=TTFILE00,DUMPCOND=DUPL,REMOVE=
12000;

<
INFDI:FILE=TTFILE01,DEST=dest,EQUIP=NOLINK,
FILEID2=TTFILE01,RULE2=1;

< INFICC:FILE=TTFILE01,DUMPCOND=DUPL,
REMOVE=12000; !120 hours, 0 minutes!

or

TT output over Data Link

< INFDI:FILE=TTFILE00,DEST=dest,EQUIP=MTP,
FILEID1=TTFILE00,RULE1=1;

<
INFCC:FILE=TTFILE00,TRANSCOND=AUTO,REMOVE
=4800;

< INFDI:FILE=TTFILE01,DEST=dest,EQUIP=MTP,
FILEID1=TTFILE01,RULE1=1;

< INFICC:FILE=TTFILE01,TRANSCOND=AUTO,
REMOVE=4800; !48 hours, 0 minutes!

< END;

 A number of commands are provided to de&filig;ne

the common Charging Output function. These are
the most common settings:

< CHOIC:INTERF=IOG;
 < CHOTC:FN=TT,IO=IOG11,CAP=HIGH,BNUM=10;

<
CHOUC:FN=TT,PRIORITY=HIGH,PBC=5,CONV=ASN
1;

< CHOLC:LIMIT=BANS,ELIMIT=0;

< CHOFI:FN=TT,FILEID=00;

< CHOFI:FN=TT,FILEID=01;

< CHOBE:FN=TT,FILEID=00;

< CHOBE:FN=TT,FILEID=01;

For more information please see respective

Command Description.

2.1.2.5 SSF Charging Analysis

SSF charging analysis is performed for the incoming call

component when a set-up message is received and for the
outgoing call component when the outgoing call connection
is established. It provides the possibility to charge IN
services. The input to SSF charging analysis is SSF
charging case and routing type. The output from SSF
charging analysis is SSF charging program.

No commands are used for the SSF charging analysis.

Instead of them, permanent exchange parameters (block
SHCA) are used to de&filig;ne Charging Cases (CC). Those
CC point to Charging Programs. In case of the SSF
Charging Analysis, the CC are treated as input for the
analysis in which the output contains Charging Programs.
See User Guide for Mobile SSF Charging, Reference [6].

SSF Charging Cases are de&filig;ned in the SHTNS table for

each combination of service and access type (for each IST
parameter).

The CC to be de&filig;ned on an incoming leg is known as

Incoming SSF Charging Case (ISCC) and the CC to be
de&filig;ned on an outgoing leg is called Outgoing SSF
Basic routing Charging Case (OSBCC) or Outgoing SSF
Direct routing Charging Case (OSDCC) respectively.

The Charging Program resulting from the SSF charging

analysis is a combination of the three following
parameters:
  Associated Call Data - ACD.

Basically this parameter decides whether

INIncomingCall and INOutcomingCall components
(together with their corresponding
INServiceDataEventModule) will be generated as
individual single CDR or composite CDR.

 Output Function - OF.

It de&filig;nes if INOutgoingCall component will be

generated.

 Reduced Call Data Output - RCDO.

It de&filig;nes whether the outgoing side should

generate reduced output of call data. This is
basically the parameter which decides whether
transit or transitINOutgoingCall is generated.

This means that a Charging Program speci&filig;es

whenever and how the TT output is generated for an IN
call.

The SSF Charging Program can be built according to the

following tables so that all the possible parameter
combinations are covered. However, it is up to the operator
how to set up the tables and the default values for the
Charging Programs.

Table 1 Incoming leg Charging Table for SSF Charging Analysis

INPUT (CC) OUTPUT (OF)

CC1 / ISCC=8 YES

CC2 / ISCC=9 NO

default value YES

Table 2 Outgoing leg Charging Table for SSF Charging Analysis (Param. list S

OSBCC/ CC ACD OF RCDO

OSDCC take
n

0 CC1 YES YES YES

1 CC2 YES YES NO

2 CC3 YES NO YES

3 CC4 YES NO NO

4 CC5 NO YES YES

5 CC6 NO YES NO

6 CC7 NO NO YES

7 CC8 NO NO NO

Chargeable call data records (TT Records) for SSF charging

analysis are produced by the following charging functions:

 SSF IN Incoming Service Charging

 SSF IN Outgoing Service Charging

Those SSF IN charging functions are responsible for IN

service speci&filig;c charging.

Incoming leg

According to parameter list of SHCA:

BLOCK=SHCA (CAAZ 107 0243)

 ISCC=8, means CC1 is taken, which means

output=yes:

INIncomingCall is generated.

 ISCC=9, means CC2 is taken, which means

output=no:

INIncomingCall is not generated.

The service speci&filig;c data that can be inserted in the

CDR is described in Detail Record Parameter List Charging
System IN CDR, Reference [8].

2.1.2.6 MSC Charging Analysis

Charging of a mobile call is terminated according to the
conditions speci&filig;ed by Charging Case. The Charging
Case is pointed out by the B-number analysis performed in
the MSC.

By appropriate parameter setting in the B-number analysis

and/or de&filig;ning the subscriber categories and route
data, it is possible to differentiate an IN call from an
ordinary call. As a result of that, the charging can be
terminated in different ways depending on if it is an IN call
or a mobile call.

As a result of Charging Case de&filig;nition, TT Records are

generated by the following charging function:

 MSC IN Incoming Call Charging

 MSC IN Outgoing Call Charging

MSC IN Call Charging handles call related charging

(ordinary call possibly modi&filig;ed by IN), where the SSF
IN Call Charging carries only IN service speci &filig;c
charging.

The SSF and MSC Incoming Call Charging function build

Incoming IN Call Component. TT Records produced by
these functions can be used to charge a calling subscriber.

The SSF and MSC Outgoing Call Charging function build

Outgoing IN Call Component and data produced by this
component can be used to charge for the call from IN. For
more information please see User Guide for Charging of
Mobile IN Calls in GMSC/MSC/SSF node, Reference [9].

Using the data on all produced records for IN call, a billing

system outside AXE can examine the required data in order
to produce a bill for a subscriber.

MSC IN Incoming Call Charging

Normally all the calls made by a PrePaid subscriber are IN

calls and should be routed to the SCP, with the exception of
emergency calls. A charging case can be reserved for this
purpose.

< CHASI:CC=cc1,CD=3,TT,AP,TC=tc; !PrePaid

Originating!

< CHAAI:CC=cc1;

CD Charging determination code, 3=own node

 TT Toll ticketing

AP A-party charging

TC Tariff Class

Tariff and Tar iff Class ha ve to be de&filig;ned to complete

the charging analysis .

The tariff class can be, for example, the PrePaid trigger
for the service provider's TT post processing computer.

MSC IN terminating Call Charging

If the service provider wants to charge the terminating

PrePaid calls, the following Charging Case, CC can be
de&filig;ned

< CHASI:CC=cc2,CD=3,TT,BP,TC=tc; !PrePaid

Terminating!

< CHAAI:CC=cc2;

BP B-party charging

Tariff and Tar iff Class ha ve to be de&filig;ned to complete

the charging analysis .

2.1.2.7 SCP Charging Analysis

Function Block SSCDO is part of System Module SCFAM.

SSCDO offers the possibility to create Call Detail Records
(CDRs) within the SCP and to write charging data to them.
Charging data can be created dynamically during script
execution or can be de&filig;ned by the operator.

Note:
The operator can choose if the CDRs should be generated in SCP or in
MSC/SSF, see Installation/Upgrade Instruction IN Service using MML,
Reference [10]. That is achieved by means of GDM CS20_MSCCDR_TIME.

For CS1+ calls it is possible to collect CDRs from SCP or from MSC/SSF. For
CAPv2 calls the CDRs are always collected from SCP.

Charging data can be output to a CDR at

anymoment during script execution. SSCDO
contains control types MANCDR and WRTCDR.
They are activated by Service Script
Interpreter.

During script execution, charging data is

retained in charging views in RMP. When a
view is closed, the data is placed in a CDR by
FOAM.

Per Service Logic Processing Program Instance

(SLPI), up to 30 CDRs can be open
simultaneously.

Function Blocks SSI and CHVIEW co-operate

with SSCDO in the SCF Charging Data Output
feature.

2.1.3 Routing concepts

There are three ways of routing an IN-call to

the SSF from GMSC/MSC/VLR:

 To an inter nal SSF-AM within the same

node
 To an external SSF using IN-pre&filig;x
 To an external SSF using a dedicated
route

The dedicated route/IN pre&filig;x is used in

the SSF to select the IN Service Trigger (IST)
which will be used by the triggering tables to
&filig;nd the Service Key corresponding to the
IN-service to be invoked and the address to
the SCP node that contains the service.

If an IN call will be routed to an external SSP,

a way to address the SSP node is needed.
When OICK and TICK are used, a pre&filig;x
between 000-999 is added automatically in
front of the B-number, this pre&filig;xmight
not be suf&filig;cient to route through a
network. If more modi&filig;cations of the B-
number are needed, they can be done in the
B-number analysis using the B-origin speci
&filig;ed by the MIN software route.

MIN software routes

When a subscriber makes an outgoing call, the

proper category is detected in the HLR and the
MIN software route with respective Function
Code (FNC) will be activated in the MSC/HLR
according to the following table:

Table 3 MIN software routes

FN TYPE OF MIN ROUTE

C

1 Originating IN Service in MSC/VLR at Call from MS (OIN)

2 Originating IN Service in MSC/VLR at Call Forwarding (OIN)

3 Originating IN Service in GMSC (OIN)

4 Terminating IN Service in GMSC (TIN)

5 Originating IN Category Key Service in MSC/VLR at Call from

6 Originating IN Category Key Service in MSC/VLR at Call Forw

7 Originating IN Category Key Service in GMSC (OICK)

8 Terminating IN Category Key Service in GMSC (TICK)

9 Originating CAMEL in MSC/VLR at Call from MS (O-CSI)

10 Originating CAMEL in MSC/VLR at Call Forwarding (O-CSI)

11 Originating CAMEL in GMSC (O-CSI)

12 Terminating CAMEL in GMSC (T-CSI)

13 Extended Originating CAMEL with IN CapabilityIndicator in MS

MS (EOICK)

14 Extended Originating CAMEL with IN Capability Indicator in M

Forwarding (EOICK)

15 Extended Originating CAMEL with IN Capability Indicator in G

16 Extended Terminating CAMEL with IN Capability Indicator in G

17 Extended Originating CAMEL with IN Category Key in MSC/VL

 (EOICK)

18 Extended Originating CAMEL with IN CategoryK eyin MSC/VL

(EOICK)

19 Extended Originating CAMEL with IN Category Key in GMS (E

20 Extended Terminating CAMEL with IN Category Key in GMSC

The call is triggered from the mobile service

subscriber.

The IN calls can be sent directly to the SSF-AM

using the TRACO route. Since the SSF-AM
needs an ISTv alue, that value is set in the B-
number analysis when it is known what IN
service the call will use. Any IN pre&filig;x that
has been added in front of the received B-
number will be removed.

The SSF-AM uses function of the core TRAM

therefore it is necessary to de&filig;ne the
connection between TRAM and SSF-AM. In the
AM concept, Application Modules communicate
with each other using prede&filig;ned
protocols. The communication is handled by
the communication services (COSS) in the
Resource Module Platform (RMP), wich
transfers messages between different
Application Modules. The TRAM and the SSF-
AM communicate using the Open Intranode
Protocol (OIP).

This issue describes the invocation function of

an IN service. The trigger parameters, the IN
service invocation model and the trigger tables
are presented here.

The triggering function in the SSF is used in

order to set up a dialogue from the SSF to a
SLP running on the SCP.

The triggering function is implemented using a

standard set of AXE relation database tables.

The input to the trigger tables is the IST (IN

Service Trigger) which is received from the B-
number analysis in the TRAM in an OIP
message.

When the trigger function for an IN service is

to be implemented the following parameters
have to be speci&filig;ed:

 SCFaddress - The routing towards SCF

is done using the output of the table
SHTSD.
 Service Key (SK) - Key used by the
SCF to invoke the correct Service
Logical Program (IN service).
 SSFaddress - The SCF needs the SSF
address in order to send back result
and continue the dialogue.
 Trigger Detection Point - detects during
a call, that triggering of an IN service is
needed. The TDP is obtained by arming
a relevant Detection Point. In the BCSM
(Basic Call State Model) certain
prede&filig;ned Detection Points (DP)
are available.

Other optional parameters can be sent to the

SCF by the SSF:

 Called Party Number

 Calling Party Number
 Protocol Type
 Location Number

These parameters can be grouped as follows:

 Reference parameters. Specify a row

identi&filig;er or a reference to entry in
other tables.
 Parameters speci&filig;c for a Service
Provider. Describe an environment
supplied by a Service Provider; for
example, SSF and SCF addresses, kind
of used protocol and so on.
 Parameters speci&filig;c for the
PrePaid System. Those are the
parameters required for the service
execution.

The Trigger Tables are described in the way

they are loaded: SHTSO and SHTSD before
SHTDPS; SHTDPS and SHINS before SHTDP;
SHTDP before SHISTTOTDP and SHTNS before
SHIST.
The recommended order is the following:

 SHEXTRANS
 SHEXTLIST
 SHTSO
 SHTSD
 SHTDPS
 SHINS
 SHTDP
 SHTNS
 SHIST
 SHISTOTDP

2.1.3.1 B-Number Analysis for the PrePaid

The number analysis is described for each

relevant Traf&filig;c Case when the PrePaid
system is invoked.With exception of
emergency calls, calls to IVR (if required),
calls based on CAMEL PH3 and Service
Charging using Diameter or the Parlay API,
PrePaid subscriber calls will always go
through the SCP. Those calls include normal
originating calls to others subscribers, free
calls, calls to the service provider and all the
terminating calls.

The Calling Line Identity (CLI) of a mobile

PrePaid Subscriber has to be sent to make it
possible for the service to identify the PrePaid
Subscriber, this is the only way to charge the
subscriber.

A mobile PreP aid Subscr iber has the Or

iginating and/or Ter minating IN Category Key
(OICK and TICK) de&filig;ned in the HLR.

When a mobile PrePaid Subscriber makes a

call the OICK is indicated and as a
consequence of that the PrePaid is invoked.
The category TICK is doing the same for
terminating calls.

The exchange data will follow the call-set up

procedure presented for Originating call.
Figure 2 Call set up procedure, PrePaid
Originating

2.1.4 Announcements

Type of announcement system

There are several Announcement Systems,

among them:

 AST-DRV1 and V2:

controlled by ASDH for traf&filig;c, and

by ASDS for maintenance,
  AST-DRV3:

controlled by ASDH3 for traf&filig;c,

and ASDS3 for maintenance.

Announcements are normally de&filig;ned in

the MSC/SSF. The type of system used
depends on the hardware available, (see ASDS
or ASDS3 Application Information). The
difference between the two systems is the
capacity to store messages, but
de&filig;nitions are similar in both cases.

Some prerequisites are needed in order to

make the DT commands to use announcement
machines. The Board Phrase Numbers are
speci&filig;ed in documents which number has
the following notation: 1951-x/LZYxxx03/y. To
&filig;nd the document that speci&filig;es the
phrases for a certain board, see the &fllig;oor
plan speci&filig;cation. The LZY number can be
found in this document. PHR can be calculated
in the following way: PHR = Offset + Board
phrase number. Unfortunately this document
is not always available (market dependant).

In AM structure, the announcement system

has been transferred to RMP. The traf&filig;c
interface that is used to record and listen to
the announcements is allocated in XSS (TCIA).
This block will transform the TCS interface into
the standard AUIF interface, which is an
allowed XSS-RMP interface. In other words,
that means there will be announcements
coming from End of Selection or Number B
analysis, the digits will be sent through RC to
TCIA block and there they will be transformed
into an Announcement Code (ANNC).
Figure 3 Announcements handling
mechanism

Announcement Routes De&filig;nition

For a correct de&filig;nition of the

Announcement System the following must be
de&filig;ned:

The AUIF route is an interface block between

the announcement user functions and the
announcement systems. It is used by a user
function to do the following:

 Send an audible message to a

subscriber,
 Receive digits keyed in by a subscriber,
 Record an audible message from a
subscriber.

< EXROI:R=AUIF, DETY=AUIF;

This TCIA-block transforms the TCS interface

into the standard AUIF interface which is an
allowed XSS-RMP interface.

< EXROI:R=TCIAL1, DETY=TCIA, FNC=0;

Listening route

< EXRBC:R=TCIAL1, RSV=4;

< EXROI:R=TCIAR1, DETY=TCIA, FNC=0;

Recording route

< EXRBC:R=TCIAR1, RSV=8;

ASDH Routes

The system is based on three types of routes:

 One main route that administers a

group of devices that can reach the
same set of physical phrases.
 One Listening Route per
announcement, that route is used to
send announcements to listeners. The
route is seized through the
Announcement Unit User Interface
(AUIF). The announcements may
contain &filig;xed phrases, silent
 phrases, variable phrases and
recordable phrases.
 One Recording Route per
announcement, that route is used to
record the contents of a recordable
phrase. The route is seized through
AUIF too.

Main Route Definition:

< EXROI:R=1MAIN0, DETY=ASDH, FNC=1;

< EXDRI:R=1MAIN0, DEV=ASDH-0&&-31; !

Hw has to be loaded first!

Recording time in hard disk for RAM

announcements must be speci&filig;ed:

< EXMRC:R=1MAIN0, RSSC=768;

FNC=1 Main route

RSSC Recordable speech storage capacity in

seconds. This parametter is calculated
depending of the board number and its type.
For example: "RSSC=768", BFD 748 506
Installed -- 3 boards.

Note:
The names of the routes are done in mnemonically form. For example,
CSLXNN, CSRXNN, means PPS=PrePaid Service, L=Listen Route, X=x:nd
language, R=Recording Route, NN=number of message=relative position on
board. Below is described how to de&filig;ne one route of each type, because
routes are dependent on the installed recording boards.

Recording Routes

The Recording Routes are used

for temporary recordings.
Recording is only possible in
ASTRAM boards.

<
EXROI:R=PPSRXNN,DETY=ASDH,
FNC=5,R1=1MAIN0;

Listening Routes
<
EXROI:R=PPSLXNN,DETY=ASDH,
FNC=2,R1=1MAIN0;

<
EXRBC:R=PPSLXNN,MIS2=3,MIS
4=1,MIS5=32,IRM=1;

FNC=2 Listening Route (seized

through AUIF)

FNC=5 Recording Route (seized

through AUIF)

R Name of Listening (FNC=2) or

Recording (FNC=5) Route.

R1 Main Route (de&filig;ned with

FNC=1).

MIS2 Call termination Type,-

value "3" - after a number of
repetitions

MIS4 Call termination Data. It

contains supplementary
information for MIS2; if MIS2=3,
MIS4=number of repetitions
--"1".

MIS5 Maximum number of

devices that may be seized by a
listening route.

IRM Interim Route Mark. The

outgoing compatibility check and
the analysis of supplementary
services are inhibited. It is used
for outgoing routes where these
checks are not wanted.

Phrase concepts

When accessing a listening route,

a device in the corresponding
main route is seized. An
announcement according to the
phrases de&filig;ned for that
listening route will be sent. The
announcement for a listening
route can contain &filig;xed,
 recordable, silent and variable
phrases. A recordable phrase may
only be in one listening route.
Fixed phrases may be used in
several listening routes, while
recordable phrases may only be
used in one listening route.

Phrases are divided in four types,

and each type has a differentiate
phrase number range:

 Fixed Phrases:
o 6-4095, (HW
dependent)
o 34096-62767, see
Application
Information ASDH
for phrase mapping
 Silent Phrases:
o 5301-5399. A silent
interval within an
announcement.
Silent phrases have
the format 53XX,
where XX is the
length of the
silence in tenths of
a second.
 Variable Phrases:
o 6000-6999.
Phrases of which
contents change,
depending on the
call. See the
Application
Information for
function block
ASDHD for a
further description
of the values of the
variable phrases
that are
prede&filig;ned.

Note:
Be careful, range for variable phrases can be confused with ANNC generated
by SDP/IVR, but are different. One is PHR (relative position on board) and the
other is an Announcement Code (ANNC).
  Recordable Phrases
(stored on ASTRAM
boards):
o 10000-26382.
Altered through the
Recording
Procedure

< EXANC:R=PPSLXNN, PHR=phr;

Phrase for Listening Routes

< EXANC:R=PPSRXNN, PHR=phr;

Phrase for Recording Routes

<
EXANC:R=PPSLXNN,PHR=phr&ph
rphr; Variable phrases

Announcement Codes

See Recordable Announcements,

Reference [11] for information
about announcements to use.

<
EXAUI:R=PPSLXNN,ANNC=annc;

<
EXAUI:R=PPSRXNN,ANNC=annc;

Deblocking of announcement
routes

< BLORE:R=CSLXNN;

2.1.5 Tones

The following paragraph explains

how to set the parameters to
de&filig;ne tones characteristics
building a cadence. Refer to
Multi-Junctor Changable
Exchange Adaptation, Reference
[12] for further information
concerning value ranges.

Note:
In CAMEL Phase 2 there is a standard warning tone to be played 30 seconds
before call cut off. That has to be done in all SSF's otherwise they will be not
CAMEL Phase 2 compliant. The warning tone should be played 30 seconds
before the call is released.
Notice that all the parameter settings must be checked with market
requirements!

The tone has the following speci&filig;cations:

* 900 Hz.

* Attenuation level of -20db.

* 3 times 200 ms tones with 200 ms pause in between.

Note:
A 900 Hz -20dB tone needs to be de&filig;ned in the CCD hardware. See TR
AF74373

Comma
nds for
TONES
paramet
er set
activatio
n in
MSC
node
has the
followin
g
format:

<
SYPAC:
ACCESS
=ENABL
ED,PSW
=....;!
Ask
local
FSC for
passwor
d!

<
DBTRI;

<
DBTSC:
TAB=AX
EPARS,
SETNAM
E=MJC,
NAME=
name,V
ALUE=v
al;

<
DBTRE:
COM;

<
SYPAC:
ACCESS
=DISAB
LED;

For
complet
e DT
file, see
Model
DT for
MSC/SS
F,
Referen
ce [2].

Table 4 Parameter Set Ac

SETNAM NAME
E

MJC PREPATONEINIT

MJC PREPATONET1

MJC PREPAPAUST1
MJC PREPAFLEV1CCD

MJC PREPATONET2

MJC PREPAPAUST2

MJC PREPAFLEV2CCD

MJC PREPALEV2

MJC PREPATONET3

MJC PREPAPAUST3

MJC PREPAFLEV3CCD

MJC PREPALEV3

MJC PREPACYCLIC
 2.1.6
Signalli
ng
System
No.7
Signalli
ng
Data

Note:
The data and de&filig;nitions in this chapter are for a CME 20 network.

2.1.
6.1
Sign
allin
g
Poin
t

The
follo
wing
chap
ter
cont
ains
com
man
ds
for
de&f
ilig;
nitio
n of
sign
allin
g
nod
es.
In
this
chap
ter
only
sign
allin
g
data
for
INA
P
part
will
be
expl
aine
d,
whil
e
sign
allin
g
data
for
USS
D
part
bet
wee
n
SDP
-
HLR
will
be
expl
aine
d in
Cha
pter
5,
USS
D
bala
nce
on
dem
and
will
be
expl
aine
d in
Cha
pter
11.
Defi
ne
all
Sign
allin
g
Poin
ts
for
rout
es
con
nect
ed
to a
spec
i&fili
g;c
nod
e,
for
exa
mpl
e,
an
SCP
nod
e:

<
C7O
PI:O
WN
SP=
2-
own
sp,
SPT
YPE
=ST
P;!
SCP
is
de&f
ilig;
ned
as
OW
NSP
!

<
C7S
PI:S
P=2
-
msc
;

<
C7S
PI:S
P=2
-
sdp
0a;

<
C7S
PI:S
P=2
-
sdp
0b;

Give
a
nam
e
(spi
d)
for
each
Sign
allin
g
Poin
t:

<
C7P
NC:
SP=
2-
own
sp,S
PID
=spi
d;

<
C7P
NC:
SP=
2-
msc,
SPI
D=s
pid;

<
C7P
NC:
SP=
2-
sdp
0a,S
PID
=spi
d;

<
C7P
NC:
SP=
2-
sdp
0b,S
PID
=spi
d;

De&
filig;
ne
Poin
ts
for
SCC
P
net
wor
k:

<
C7N
PI:S
P=2
-
own
scp;

<
C7N
PI:S
P=2
-
msc
;

<
C7N
PI:S
P=2
-
sdp
0a;

<
C7N
PI:S
P=2
-
sdp
0b;

Defi
ne
of
one
or
mor
e
subs
yste
ms
for
an
SP
alre
ady
de&f
ilig;
ned
in
the
SCC
P
net
wor
k:

<
C7N
SI:S
P=2
-
nod
e,SS
N=s
sn;

Table 5 Sub

SSN PR

5 M

6 H

7 V

8 M

11 IN

15 EM

146 C

251 IN

252 IN

Rout
ing
Spe
ci&fi
lig;c
atio
n

<
C7R
SI:D
EST
=2-
msc,
PRI
O=1
,LS
=2-
msc
;
<
C7R
SI:D
EST
=2-
sdp
0a,P
RIO
=1,L
S=2
-
spd
0a;

<
C7R
SI:D
EST
=2-
sdp
0b,P
RIO
=1,L
S=2
-
sdp
0b;

GT
Anal
ysis

<
C7T
ZI;

<
C7T
CI;

!
Logi
cal
SDP
0!

<
C7G
CI:G
TRC
=gtr
c_a,
PSP
=2-
SDP
0a,P
TER
M,P
SSN
=11
,SSP
=2-
SDP
0b,S
TER
M,S
SSN
=11
,LSH
;!
phys
ical
SDP
0a!

<
C7G
CI:G
TRC
=gtr
c_b,
PSP
=2-
SDP
0b,P
TER
M,P
SSN
=11
,SSP
=2-
SDP
0a,S
TER
M,S
SSN
=11
,LSH
;!
phys
ical
SDP
0b!
<
C7G
CI:G
TRC
=10
,PSP
=O
WN
SP;
!
scp!

<
C7G
SI:T
T=1
0,NP
=1,
NA=
4,N
S=S
DP0
a,GT
RC=
gtrc
_a;

<
C7G
SI:T
T=1
0,NP
=1,
NA=
4,N
S=S
DP0
b,GT
RC=
gtrc
_b;

<
C7G
SI:T
T=0
,NP
=1,
NA=
4,N
S=s
cp,G
TRC
=10
;

<
C7T
AI;

AXE
par
am
eter
s

AXE
para
met
ers
are
para
met
ers
whic
h
are
used
to
cust
omiz
e
AXE
soft
war
e
conc
erni
ng
stan
dard
and
opti
onal
func
tion,
in
orde
r to
ada
pt
the
AXE
soft
war
e to
cust
ome
r/m
arke
t
requ
irem
ents
.
The
com
man
ds
for
para
met
er
set
activ
atio
n
hav
e
the
follo
wing
form
at:

<
SYP
AC:
ACC
ESS
=EN
ABL
ED,P
SW
=....
;!
Ask
local
FSC
for
pass
wor
d!

<
DBT
RI;
<
DBT
SC:
TAB
=AX
EPA
RS,
SET
NAM
E=s
etna
me,
NAM
E=n
ame
,VAL
UE=
val;

<
DBT
RE:
COM
;

<
SYP
AC:
ACC
ESS
=DI
SAB
LED
;

In
orde
r to
set
up
Eve
nt
Rep
ortin
g
supe
rvisi
on
for
Sign
allin
g
No.
7 it
is
nece
ssar
y to
activ
ate
the
follo
wing
para
met
ers:

Table 6 Para

SETNAM NAM
E

CCSF CCS

CCSF MTP
N

That
will
allo
w to
de&f
ilig;
ne
de
follo
wing
com
man
ds,
very
usef
ul
for
trou
ble
sho
utin
g:

<
C7E
SC:
ENU
M=e
num
,EM
AX=
10,N
FILT
ER=
1,LT
YPE
=W
RAP
;

<
C7E
RI:E
NUM
=AL
L;
(Acti
ve
all
eve
nts)

<
C7E
RP:E
NUM
=AL
L;
(Pri
nt
all
eve
nts)

<
C7E
RE:
ENU
M=A
LL,N
P;
(Del
ete
all
eve
nts
with
out
print
out)

Table 7 Enum

BLOCK

C7DP2

C7DR2

C7SL2

C7LS2

C7EPC2

C7MVM

C7OMASE

CUPOLAN

The
follo
wing
com
man
ds
are
usef
ul as
well
;
they
are
appl
icabl
e for
eve
nts
relat
ed
to
the
OMS
-R
Sub
syst
em:

<
ERE
SC:
ENU
M=e
num
,EM
AX=
10,N
FILT
ER=
1,LT
YPE
=W
RAP
;

<
ERE
PP:E
NUM
=AL
L;

<
ERE
PE:E
NUM
=AL
L,NP
;

<
ERE
PI:E
NUM
=AL
L;

See
in
Tabl
e8
the
Enu
m
and
Bloc
k
relat
ions
hip
for
the
OMS
-R
relat
ed
eve
nts:

Table 8 Enum

BLOCK

C7SRM

C7SRMH

C7CL

C7SM

C7CO

C7CLAN

C7BM

C7TCP

HZONED

HSTRD

GCPH

2.1.
7
ANS
I
No.
7
sign
 alli
ng
dat
a

Not
e:
This chapter contains the commands for de&filig;nitions of ANSI SS7 data for
the CMS40 network. The parameters used in this chapter are just examples.

2.1.7.1
Signalling Point

Define all
Signalling Points
for routes
connected to the
SCP node:

<
S7OPI:OWNSSP
=7-9-
ownsp,SSPCLLI=
STEXDSCPown;

Define Link Set:

< S7LSI:LS=7-9-
msc,LSN=msclsn
ame,LST=A,FCLL
I=msclocid;

< S7LSI:LS=7-9-
sdp,LSN=sdplsna
me,LST=A,FCLLI
=sdplocid;

Routing
Specification:

<
S7RSI:DEST=7-
9-msc,LS=7-9-
msc,PRIO=1;

<
S7RSI:DEST=7-
9-sdp,LS=7-9-
sdp,PRIO=1;
Define Signalling
Terminal:

<
S7STI:ST=S7ST-
x,TYPE=DS0A;

<
S7STI:ST=S7ST-
y,TYPE=DS0A;

Initiate Signalling
Link:

< S7SLI:LS=7-9-
msc,ST=S7ST-
x,SLC=0;

< S7SLI:LS=7-9-
sdp,ST=S7ST-
y,SLC=0;

Define SCCP
Network
Signalling Point:

< S7NPI:SP=7-
9-msc;

< S7NPI:SP=7-
9-sdp;

Define SCCP
Network
Subsystem:

< S7NSI:SP=7-
9-msc,SSN=ssn;
(See Table 5 for
Subsystem n
umbers) <
S7NSI:SP=7-9-
sdp,SSN=ssn;
(See Table 5 for
Subsystem n
umbers)

GT Analysis:

< S7TZI;
< S7TCI;

<
S7GCI:GTRC=gtr
c_sdp,PSP=7-9-
sdp;

<
S7GCI:GTRC=gtr
c_msc,PSP=7-9-
msc;

<
S7TSI:GTS=10-
sdp,GTRC=gtrc_s
dp;

<
S7TSI:GTS=10-
msc,GTRC=gtrc_
msc;

<
S7TSI:GTS=14-
scp,LSS=lss;
(See Table 5 for
Subsystem n
umber)

< S7TAI;

3
Charging
System
Traffic
Cases
The present
chapter will
describe
Charging System
traffic cases.

3.1 PrePaid
Originating
Traffic Case
When a mobile
PrePaid
subscriber makes
an outgoing call
the OICK
category will be
found in the VLR,
and the MIN
software route
with FNC=5 will
be activated in
the MSC/VLR.
After that a new
B-number
analysis will start
in BO 24
according to the
definition of the
MIN route, and
the dialled
number will be
pre&filig;xed
with the OICK
value (OICK =
310). If there are
more than one
SDP a different
OICK value must
be used for each
one.

In the MSC/SSF
B-number
analysis is done
and the IN
Service Trigger
(IST) parameter
is set. The IST
parameter is
used by the SSF
to determine the
correct data for
the further
processing of the
call.

IST=310
indicates the
PrePaid
Originating Call
in this example.
Calls to the
PrePaid service
are directed to
the software
route TRACO
through the
suitable Routing
Case (RC=71).

The Service Key

(SK) is a result
from the trigger
tables (SHTDPS)
in the SSF, and it
is sent from SSF
to SCP to identify
the service to be
invoked in the
SCP. The SCP
sends
Interrogations
about
subscriber`s
credit to the
SDP, checking if
the call is
allowed and for
how long.

When the call

has been routed
through the SCP,
the IN category
will be
suppressed and
the call set up
will continue
though SSF up to
TRACO route
where B number
analysis will be
done and the call
will progress like
a normal one.

The following
signalling
diagram
describes
PrePaid
Originating call
&fllig;ow.
Figure 4
PrePaid
Originating Calls

3.2 PrePaid
Terminating
Traffic Case

When a PrePaid
subscriber is
called, the TICK
information is
found in HLR.
Then the
software route
8MIN with
FNC=8 will be
seized and a new
B-number
analysis will start
in the BO=27
according to the
de&filig;nition of
the route. The
dialled number
will be
pre&filig;xed
with the TICK
value (TICK =
311). In case
there are more
than one SDP,
different TICK
must be used for
each one.

In the MSC/SSF
B-n umber
analysis, the IN
Ser vice Trigger
(IST ) parameter
is set. The IST
parameter is
used by the SSF
to determine the
correct data for
the further
processing of the
call.

IST=311
indicates the
PrePaid
Terminating Call
in this example.

Calls to the
PrePaid are
directed to the
software route
TRACO through
the suitable
Routing Case
(RC=71).

The Service Key

(SK) is a result
from the trigger
tables in the
SSF, and it is
sent from SSF to
SCP, to identify
the service to be
invoked in the
SCP. The SCP
sends
Interrogations
about the
subscriber credit
to the SDP to
check if the call
is allowed and
for how long.

When the call

has been routed
through the SCP,
the IN category
will be
suppressed and
the call set up
will continue like
a normal call.

The following
signalling
diagram
describes
PrePaid
Terminating call
&fllig;ow.

Figure 5
PrePaid
Terminating Calls

3.3 PrePaid
Roaming
Originating
Call (CAMEL
PH2)

The following
steps are made
when a roaming
originating call is
made.

1 Location
Update is
performed when
the PPS
subscriber A is
roaming in the
VPLMN. As a
response the HLR
will send CAMEL
Subscriber
Information
(CSI), to the VLR
in the VPLMN.

2 Subscriber A
initiates a call.
The Originating
CSI (O-CSI) data
triggers that the
CAMEL service is
applied to the
originating call
attempt. The
MSC/VLR will
hand over the
call to the
gsmSSF in the
VPLMN.

3 The gsmSSF
will invoke the
gsmSCF in the
HPLMN. The
gsmSCF address
is part of the CSI
data in the HLR.

4 The gsmSCF
processes
receive and store
data that is
required later
during the call
sequence. The
call will be
marked as
`Roaming
Originating'.

5 All data
received from
the gsmSSF is
used when
interrogating
SDP for retrieval
of call and
charging
information, such
as call length
limit and
announcements.
 6 If call is
allowed the
gsmSCF will
order the
gsmSSF to
connect and
supervise the
call.

Note:
This is the behaviour for CAMEL phase 2. Some differences with CAMEL phase
1 should be borne in mind. See Chapter 3.7, PrePaid Roaming calls (CAMEL
PH1).

7 If an announcem
be played, an assis
address is received
SCF. The MSC/gsm
VPLMN is connecte
assisting SSF in HP
the assisting SSF t
the SCF and the S
an assisting SSF in
play the announce

8 The call is conne

The following signa

diagram describes
Roaming Originatin
&fllig;ow.

Figure 6 PrePaid
Originating Call
3.4 Prepaid R
Forwarding Ca
handled by the

Late call forwardin

included here: con
Forwarding (CF), C
Forwarding on Mob
Subscriber Busy (C
Forwarding on No
(CFNRY). The follo
are made when ro
forwarding call is h
MSC.

1 Location Update
performed by the
subscriber B in VPL
response the HLR
CSI and call forwa
to the VLR in VPLM

2 Subscriber A call
subscriber B who i
in VPLMN.

3 The GMSC perfo

interrogation in th
retrieve whereabo
CSI)of subscriber B
collects informatio
interrogation and r
response to the GM

Terminating par t:

4 The gsmSSF trig

initiates the SCP w
about the call is co

5 The SCF will inte

SDP for retrieval o
charging informati
call length limit an
announcements.

6 The SCF orders t

to connect the call

7 The call is routed

8 If the subscriber
does not answer th
diverted and the g
initiate an originat
in the VPLMN to co
subscriber C.

Originating part:

9 The gsmSSF init

gsmSCP where dat
call is collected.

10 The SCF will int

the SDP for retriev
and charging infor
as call length limit
announcements.

11 The SCF will or

gsmSSF to connec
supervise the call.

12 The call is conn

following signalling
describes a PrePa
Forwarding call &fl

Figure 7 PrePaid
Forwarding calls h
the MSC
3.5 PrePaid R
Forwarding Ca
handled by the

Early call forwardin

explained here: Un
Call Forwarding (C
Call Forwarding on
Subscriber not Rea
(CFNRC).

The following step

when roaming forw
is handled by GMS

1 Location Update
performed by the
subscriber B in VPL
response the HLR
CSI and call forwa
to the VLR in VPLM

2 Subscriber A call
subscriber B.

3 The GMSC perfo

interrogation in th
retrieve whereabo
CSI)of subscriber B
collects informatio
interrogation and r
response to the GM

Terminating part:

4 The GMSC will tr

gsmSSF.

5 The gsmSSF will

gsmSCF.

6 The SCF will inte

SDP for retrieval o
charging informati
call length limit an
announcements.

7 gsmSCF orders t
to connect the call
8 The GMSC interr
HLR to send the ca
forwarding indicati
as response to GM
GMSC interrogates
gsmSSF Originatin

9 The gsmSSF invo

gsmSCF.

10 The SCF will se

traf&filig;c case to
Forwarded'.

11 The SCF will int

the SDP for retriev
and charging infor
such as call length
announcements.

12 If the call is allo

gsmSCF will order
gsmSSF to connec
supervise the call.

13 The call is route

correct forwarded-
and the gsmSSF w
supervise the call.

14 The call is conn

following signalling
describes PrePaid
Forwarding call ha
the GMSC.
Figure 8 PrePaid
Forwarding calls h
the GMSC

3.6 PrePaid R
Terminating C

The following step

when roaming term
call is made.

1 Subscriber A call
subscriber B who i
in VPLMN.

2 The GMSC perfo

interrogation in th
retrieve whereabo
subscriber B. The H
information to the
interrogation and r
response to the GM
information include
and terminating lo
number.

3 The GMSC will tr

gsmSSF.

4 The gsmSSF invo

gsmSCF.

5 The SCF determi

traf&filig;c case `R
Terminating' based
received terminati
number. 6 The SC
interrogates the SD
retrieves call and c
information, such
length limit and
announcement.

7 The gsmSCF ord

gsmSSF to connec
supervise the call.

8 With T-CSIsuppr
active, the GMSC i
the HLR a second
retrieve the roamin
9 The GMSC route
subscriber B

10 The call is conn

The following signa

diagram describes
Roaming Terminat

Figure 9 PrePaid
Terminating calls

3.7 PrePaid R
Call (CAMEL P

The following step

when roaming orig
is made. 1 Locatio
performed when th
subscriber A is roa
VPLMN. As a respo
HLR will send CAM
Subscriber Informa
to the VLR in the V

2 Subscriber A init
The Originating CS
data triggers that
service is applied t
originating call att
MSC/VLR will hand
call to the gsmSSF
VPLMN.
 3 The gsmSSF will
gsmSCF in the HPL
gsmSCF address is
CSI data in the HL

4 The gsmSCF pro

received data and
that are required l
the call sequence.
be marked as `Ro
Originating'.

5 All data received

gsmSSF is used wh
interrogating SDP
of call and chargin
information, such
length limit and
announcements.

6 If the call is allow

gsmSCF will order
gsmSSF to route t
towards the HPLMN

7 The visiting GMS

IAM operation with
gsmSCF+pointer t
stored in step 4 to
home gsmSSF.

8 The GT of the gs
removed and the c
continue as a norm
prepaid originatin
SK=14. The home
has now the contro
call.

9 The call is conne

The following signa

diagram describes
Roaming Originatin
&fllig;ow using CA

Note:
In case of Roaming Ter minating calls the ser vice is not tr iggered by using
CAMEL PH1. Instead of that there are two possibilities:
1) Use a normal CS1+ terminating call. There is a GDM where the home VLRs
are registered. This GDM allows to discriminate roaming and non roaming
calls.

2) Use a correction in the HLR to avoid sending the TICK when the subscriber
is registered in the HPLMN.

Figure 10 PrePai
calls CAMEL PH1

3.8 Charging
Originating SM

Figure 11 Chargin
SMS

When a Charging S
a short message a
de&filig;ned as an
(see Block MSMT),
analysis will start i
the route paramet
(DETY=TCON).

In the case the de

(see Chapter 6.3.2
Operator speci&fili
B-number sent fro
analysis in BO 199

OICK(3digits)+typ
+B-NUMBER+Orde
money,1=deduct m
SMS-1).

The B-number ana

`Type of SMS' and
entry point for the
ISK=IST-19900 -
iginating SMS in th

The SMS triggered

software route TRA
Routing Case (RC=
an IAM message to

Depending on the
MSMT (see Chapte
Parameters, Opera
the SC-address or
(MSMO) / originati
sent towards the B
destination addres
the called party nu
originating address
calling party numb
and originating ad
referred to as Bnu

In case of SC-Addr

A-number=A-Subs
number=SC+Orde
1 and IST.

In case of B-numb
A-number=A-Subs
number=B-numbe
of SMS-1 and IST.

The trigger tables

Service Key (SK) s
SCF, to identify th
in the SCP.

In this example, S
originating PPS SM

3.9 Charging
Terminating S

Figure 12 Chargin
SMS

When a short mes

subscriber and the
&filig;ned as a term
Block MSMT), a ne
will start in BO 199
parameter for the
(DETY=TCON).

The process is the

originating PPS SM
Originating PPS-SM
of SMS (1=termina

The B-number ana

`Type of SMS' and
entry point for the
ISK=IST-19800 -
minating SMS in th

The SMS triggered

software route TRA
Routing Case (RC=
described for origin
here.

The trigger tables

Service Key (SK) s
SCF, to identify th
in the SCP. In this
indicates terminati

3.9.1 Result cod

The release codes

values when they
system.

Figure 13 Result
1) Successful chec
money)

2) Unsuccessful ch
enough money)

3) Successful dedu

4) Unsuccessful de

5) Allow SMS free

number analysis.)

6) SC address not
number analysis.)

7) A-/B-Number n
Number analysis.)

For example: If th
with cause code 52
trace), the SSF wil
an internal value in
be translated into
to SHCM. SHCM w
and an EOS code o
that cause code in
REL to TRARE. TRA
message to TCON
EOS code into reas
MSMO or MSMT.

3.10 USSD C
Figure 14 USSD C

1 The PPS subscrib

*140*4670727101
and sends it to the
Service Code for U
operator and 4670
"B").

2 The MSC/VLR an
service code is rec
supplementary ser
the string is sent t

3 When the HLR re

the service code is
the external node

4 The SDP receive

performs the initia
received B-numbe
forwards the USSD

5 The SCP will inte

prerating of the ca

6 The SCP will con

subscriber. Termin
suppressed and op
forwarding be prev

7 Upon answer fro

SCP will interrogat
of call and chargin
call length limit, an
barred locations. T
parameter is set to

8 The SCP will mak

SSF. This step is n
limitations in the c
the SSF. No additi
resources are requ

9 The SCP will con

3.11 USSD U

For information reg

please see Traffic
 4 Chargin

4.1 Introduc

The feature Charg

the basic Charging
con&filig;guration
establishing of the
calls in the Chargin
con&filig;guration
System service, an
con&filig;guration
any other features
Roaming, and SMS

The exchange data

cover:

 charging data i
 SSF triggering
 B-no analysis
 service announ
 SS7 data for S

Involved nodes are

and SDP.

4.2 MSC/SSF

This chapter is giv

implementation in
Reference [2].

4.2.1 Size Alter

See Chapter 2.1.1

general comments

4.2.2 Charging

See Chapter 2.1.2

Note:
The operator can choose if the CDRs should be generated in SCP or in
MSC/SSF, see Installation/Upgrade Instruction IN Service, Ref. [x]. That is
achieved by means of GDM CS20_MSCCDR_TIME. For CS1+ calls it is possible
to collect CDRs from SCP or from MSC/SSF. For CAPv2 calls the CDRs are
always collected from SCP.

4.2.3 Routing A

See Chapter 2.1.3

information.

The exchange data

following issues:

 APC Links
 SSF, outgoing
SCP
 Check of GRI r
 MIN routes
 Routing Case a

4.2.3.1 APC links

OIP is the protocol

between two AMs.
Link. The operator
system.

Protocol ID 30 indi
set of messages se

<
ARLII:APCLNK=SS
ID=30;

< ARLBE:APCLNK=

APCLNK Link is ide

(direction TRAM to
TRAM). EPO1 First
dependent

EPO2 Second End-

PID Protocol Ident

SMAX If this param

sessions which can
link is limited by S

4.2.3.2 Software
The outgoing softw
is de&filig;ned by

< EXROI:R=TRACO

< EXRBC:R=TRAC

On the other side,

TCS (TRAM) for inc
created as follows:

< EXROI:R=TRACI

< EXRBC:R=TRAC

R Route Name

DETY Device Type

APCLNK Link is ide

(direction TRAM to
TRAM).

The incoming SSF

following comman

< SHRPI:ISR=INC

< SHRSC:APC=SS

< SHRPE;

The APC link SSFT

route in the TRAM
(INCOMINGROUTE

The outgoing SSF

following comman

< SHRPI:OSR=OU

< SHRSC:APC=SS

< SHRSC:PAR=BO

< SHRPE;

The APC link SSFT

route in the TRAM
(OUTGOINGROUTE
ISR Incoming Serv
designation. IN CO
de&filig;ned incom

OSR Outgoing Ser

designation. OUTG
de&filig;ned outgo

APC Application Mo
link to which the S
to be connected.

PAR Message Para

parameter. CO- Ch

VAL No. of tree va

SCAP Signalling ca
parameter de&filig
in the message.

4.2.3.3 Check GR

Block GRI initiates

the data received
to receive the OIC
the RSV value on t
in all GMSCs.

< EXROP:DETY=M

< EXROI:R=GRI3,
exist!

<
EXRBC:R=GRI3,BO
=0,MIS3=15;

R Interrogation na
used).

DETY Device type

number analysis. T
analysing the MSR
guiding value is 8.

CO New origin for

value).

RSV Register Signa

indicates which of
interrogation route
when Ericsson MAP
and Extension area
Extension area use

MIS1 Miscellaneou
(forwarded-to num
MIS3. The guiding

MIS2 Miscellaneou
(forwarded to leg)
value mis2=2.

MIS3 Miscellaneou
number analysis a
whether or not par
valid. MIS3=(b3*8
MIS3=15.

4.2.3.4 MIN softw

When a PrePaid S
OICK category will
software route wit
activ ated in the M

In case of PreP aid

subscr iber, the ca
HLR and the MIN s
(FNC) 8 will be act

If the terminating
transfer activated,
Function Code 6 ac

The call is triggere

call or a Terminati
subscriber.

When a subscriber
category is detecte
route with respect
activated in the MS

MML commands de
look like the follow
MSC/SSF, Referen

< EXROI:R=name

< EXRBC:R=name
R Route name. Re
(R=xMINy, where
value; in case FNC

DETY=MIN Device

FNC=x Function Co
block MIN.

MIS1 This parame

and RO are used;

MIS2 This parame

information; mis2=
parameter is relate

BO Origin for B-no

case can be analyz

4.2.3.5 Routing C

SSF, Routing Cas

All calls to the Pre

route TRACO throu
(RC=71). In B-num
the IST parameter
branching on para
(ISTI) in the route

< ANRPI:RC=71;

< ANRSI:BR=ISTI

< ANRSI:BR=ISTI

< ANRPE; < ANRA

ISTI Intelligent Ne

 "0" : No IN ser
 "1" : IN service

RC to node IVR:

< ANRSI:RC=15, R

< ANRAI:RC=15;

RC to block GRI:
< ANRSI:RC=121,

< ANRAI:RC=121;

4.2.4 Trigger An

The exchange data

following issues:

 Trigger Tables
 B-number Anal

Protocol Type

The Protocol Type

signalling network
presented are de&

Trigger Detection

Originating Basic C
used for the PPS o
Point (DP) number
of Call Leg State M

The armed DP3 is

used for originatin
DP12 is used.

The DP number th
a complete numbe

For more informat

Service Switching
Reference [13].

SK and IN Servic

There are different

PrePaid system, o
Termination, IVR F

SKs are related to

parameters and th
least one IST.
The values for the
system but the va
valid in this docum
application.

The Triggering a

The trigger functio

trigger tables. The
them contains refe
is graphically desc
detail in the docum
[14] and Triggerin
System Descriptio
Figure 15 Trigger

This part of the do

how the trigger mo
PrePaid system.

4.2.4.1 Table SH
anslation

The Extension Fiel

to translate a para
given protocol (INA

Note:
Before loading the SHEXTRANS data the following needs to be taken into
account.

 For CME20 par

When PrePaid Sy
call reference num
CDRs generated in
available to the SS

In case CS1+ prot

parameter by corr
same way as the G
the following corre

Block: SHTTM Corr

1779 Block: SHTD

 Two AXE par a

GMSCNF327 an

Note:
It is the responsibility of the network operator to ensure that MSPEC5 is not
used for other market speci&filig;c extensions.

The MML command

following ones. For

< DBTRI;

< DBTSI:TAB=SHE
DEF=def,DIR=dir,

< DBTRE:COM;

PROTI Protocol Ide

EXTTYPE Extension

DEF Data Encoding

DIR Direction Indic

parameter can be

AMTAG AMTP (App

Identi&filig;es the
MSPEC4, MSPEC5)

For more informat

4.2.4.2 Table SH

The Extension List

from the AMTP to

The following entri

Announcement Su
Indicator (INCI) an
sent from the serv

The MML command

following ones. For

< DBTRI;

<
DBTSI:TAB=SHEX
d,EXTNO=extno,G

< DBTRE:COM;

Parameters speci&
description

PROTI Protocol Ide

EXTTYPE Extension

EXTNO Extension F

ELISTID Extension

GSIS Generic Sign

received in AMTP I
CRIT Critically. T h
does not recognize
IGNore the extens

REQ Required for t

MANdatory or OPT

For more informat

4.2.4.3 Table SH

The function of the

such as the nature

The MML command

following ones. For

< DBTRI;

< DBTSI:TAB=SHT

< DBTRE:COM;

Parameters spec

TSOID Trigger Ser

identity. This para
the SHTDPS table

ORGNAME Origin N
which is available

FORGADR Format
address. FORGADR
the use of GT+SSN
parameter speci&f
For more informat

4.2.4.4 Table SH

The function of the

SCF. This informat
and how to derive
times each of the v

The references to

DT Commands de&
ones below, please

The MML command

following ones. For

< DBTRI;

< DBTSI:TAB=SHT
DPC=dpc,FDSTAD

< DBTRE:COM;

Parameters spec

TSDID Trigger Ser

parameter is the e
table with the sam

DPC Destination Po

DSTNAME Destina
destination as a st

FDSTADR Format o
or gsmSCF addres
indicates the use o
needed.

SSN SubSystem N
For more informat

4.2.4.5 Table SH

The function of the

data. This data de
any) that should b
control failure situ
be included in the
triggering to the S

Trigger data as SK
Each of required S

The SHTDPS table

and the SHTSO tab

The MML command

For a detailed infor

< DBTRI;

<
DBTSI:TAB=SHTD
V,EVTYPE=YES,TS

Parameters spec

TDPSID Trigger De
identity of the asso

TSDID Trigger Ser

SHTSD table.

TSOID Trigger Ser

SHTSO table.

SK Service Key. It
InitialDP operation

CESS Control ESSe

for a call. If SCF co
error in access-scr
When CESS=REL c
CAMEL protocol is

EVTYPE Event Typ

included or not wh
included.

CTMP Call Treatme

mandatory data ar
AssistRequestInstr
value). The value f

SHR Simulation Ha
be performed on t
simulation function

SHS Simulation Ha
be performed on t
simulation function

USI Unsuccessful S
the SCP invocation
SURVive. The valid

SHR and SHS for n

default values), th
example, SHR=8 a

For more informat

4.2.4.6 Table SH

This table details w

InitialDP operation
De&filig;nition).
The PrePaid syste
call-related signall

The MML command

ones. For a detaile

< DBTRI;

< DBTSI:TAB=SHI

< DBTRE:COM;

Parameters spec

INSID Invoke Netw

table parameter na

The following para

information should
values NOt include

CPN Calling Party N

CGCAT Calling par

ACGN Additional C

BCAP Bearer Capa

BGVNS Backward

CAUSE Cause Indi

CDN Called Party N

CUGCI Closed Use

CUGIC Closed Use

FGVNS Forward Gl

FWCI Forward Call

GDS Generic Digits

GNS Generic Numb

HLC High Layer Co

LN Location Numb

OCDN Original Cal

RDI Redirection In

RGN Redirecting N

RO Route Origin (d

SII Service Interac

For more informat

4.2.4.7 Table SH

The function of the

table (SHINS) entr
specify the identity
Data table entries
speci&filig;es a pro

The MML command

below. For details

< DBTRI;

<
DBTSI:TAB=SHTD
TINSID=tinsid,TLI

< DBTRE:COM;

Parameters spec

TDPID Trigger Det

in the SHISTTOTD
DIAGTYP The para
communicating wit
Default.

PROTI Protocol Ide

corresponds to the

TDPSID Trigger De
to an entry in the

TINSID Trigger Inv

an entry in the SH

TLISTID Extension
row in the SHEXTL
that table.

For more informat

4.2.4.8 Table SH

The function of the

cases. It also hold
from the SSF. The
table.

The MML command

below. For details

< DBTRI;

<
DBTSI:TAB=SHTN
,DRISRID=drisrid,
OSDCC=osdcc,SCF

< DBTRE:COM;
 Parameters spec

TNSID Trigger Net

the SHIST table.

BRISRID Basic Rou

SSF route which p
in the Basic Routin
&filig;nd RINDEX:

< SHRSP:ISR=inco

DRISRID Direct Ro

BROSRID Basic Ro
SSF route which p
in the Basic Routin
&filig;nd RINDEX:

< SHRSP:OSR=ou

DROSRID Direct R

Note:
RINDEX has sequential value depending of SSFRoute de&filig;nition order.

CLIDTYP Correlatio
Correlational ID. '1

ISCC Incoming SS
incoming leg; (9 d

OSBCC Outgoing S
the outgoing leg in

OSDCC Outgoing S
the outgoing leg in

SCFIDTY SCPId Ty
Value '0' - Explicitl

ROUTTYP Route Ty
Routing (DR) or Ba

Note:
The ISCC and OSBCC are discussed in Chapter 2.1.2, Charging Data.

For more informat

4.2.4.9 Table SH

In the PPS case , t

def aults in the Tr
information about

The entries in this

The MML command

Model DT for MSC/

< DBTRI;

< DBTSI:TAB=SHI

< DBTRE:COM;

Parameters spec

IST IN Service T ri

TNSID Trigger Net

with this IN Servic

SSFTYPE SSF Type

be Initiating or Ass

BCSMTYP Basic Ca
used for a call. The
TERMinating BSCM

For more inf orma

4.2.4.10 Table SH

The function of the

Relevant entr ies i

The PrePaid syste

(TDP3) is armed a
terminating calls.

The MML command

see Model DT for M

< DBTRI;

< DBTSI:TAB=SHI

< DBTRE:COM;

Parameters spec

IST IN Service Trig

TDPNO Trigger De
service normally u

TDPID Trigger Det

For more informat

 4.2.4.11 B-numb

The following BOs

Originating & ca

When a mobile Pre

MIN route will be s
prerequisites.

The dialled B numb

out by the MIN Ro
to trigger the IN a

Note:
As a consequence of modifying the B number analysis in the MIN route, it is
always obtained BNT=2 for the B-number that has been dialled by the PPS
subscriber, and this is the reason why no B-number preanalysis is needed at
this stage.

B=24, IN TRIGGER

All outgoing calls s

The emergency nu
from a normal call
System indicates t

 2290 it the call

 2577 if no SIM

Those EOS Codes

this analysis is a R

Below there is an e
 < ANESI:ES=2290

< ANESI:ES=2577

< ANEAI:ES=2290

Regarding the IVR

Frontend. The IVR

< ANBSI:B=24-31

< ANBSI:B=24-31

The rest of the cal

Note:
Be careful, number series must be opened in order to differentiate the
"special" numbers like 112, 555, 556... Will in the feature be speci&filig;ed
more numbers with speci&filig;c treatment, the tree will have to be opened to
allow differentiation, even if the national calls will go up to the SCP with the
pre&filig;x "0". See Model DT for MSC/SSF, Reference [2].

< ANBSI:B=24-31

< ANBSI:B=24-31

B=28, CONNECT R

The call has been

sends down to the
received in CONNE
Frontend is used, s
instance, the analy
are discriminated (

Example using tree

< ANBSI:B=28-x,F

< ANBSI:B=28-55

Example using tree

< ANBSI:B=28-46

< ANBSI:B=28-70

B=310, IN TRIGGE
 For International c
SDP. The tree is op
all document.

< ANBSI:B=310-0

< ANBSI:B=310-0

< ANBSI:B=310-0

< ANBSI:B=310-0

< ANBSI:B=310-0

< ANBSI:B=310-0

< ANBSI:B=310-0

< ANBSI:B=310-0

< ANBSI:B=310-0

< ANBSI:B=310-0

< ANBSI:B=310-0

< ANBSI:B=310-0

< ANBSI:B=310-0

< ANBSI:B=310-0

< ANBSI:B=310-0

< ANBSI:B=310-0

< ANBSI:B=310-0

< ANBSI:B=310-0

< ANBSI:B=310-5

Note:
Note that trees B=24 and B=310 could have been merged in just one free
tree (B=XX) but it has been decided to have two trees because this gives
more &fllig;exibility when the number series are very open at analysis. The
maximum number of digits that can be speci&filig;ed at analysis is 8, if it is
taken into account that OICK is already consuming 3 positions, there are only
5 positions left for analysis which might not be enough in some speci&filig;c
cases or in the future.
 Terminating call

When a PrePaid s
the analysis can go

B=27, IN TRIGGER

< ANBSI:B=27-31

The GMSC/MSC sh

Parameters spec

B "24" - B origin is
with FNC=8). "28"

M Modi&filig;cation

ISK Internal Servic

SDP0. IST-312- IN

CC=cc Charging C

L Number Length.

F First digit use sta

RC RC=15 - IVR C

x Any number (mu

Note:
The B-no tree should only be opened for valid numbers. If the B-no tree is
opened for all numbers, then the Calling subscriber does not receive the
correct announcement for non-existing numbers. This will also put load the
processor of the SDP. That processor load should instead be reserved for
existing numbers and functionality.

4.2.5 Mobile Te

MT Own Calling Ad

To specify Mobile T

< MGCAC:INT=46
IMSI Analysis

The IMSI number

< MGISI:IMSIS=im

Parameters spec

IMSIS Internationa

M Modi&filig;cation

ANRES Miscellaneo

MAPVER-2 Speci&f

NATMS Allow A-nu

INOPER Operator g

STALL Subscription

OWNMS Own Mobi

BO Origin for B-nu

OBA Origin for B-n

4.2.6 Signalling

See Chapter 2.1.6

4.3 HLR Exc

4.3.1 Size Alter

See Chapter 2.1.1

4.3.2 Charging

The following exch

Number Series A

The Number Serie

numbers. The Eric
The Number Serie
information to ana

For international n

< HGPAI:USRF=RS

< HGPAI:USRF=SD

< HGNSI:ONSA=1

< HGNSI:ONSA=3

For national numb

< HGPAI:USRF=RS

< HGPAI:USRF=SD

< HGPAI:USRF=H

< HGNSI:ONSA=2

< HGNSI:ONSA=4

< HGNSI:ONSA=5

Parameters spec

USRF USER Functi

NAPI Numbering P

NAI Nature of Add

ONSA Origin for Nu

CHAR Characterist

NS Number Series

See details in Appl

Regional charging

< HGEPC:PROP=R

0-1 Specifies whet

or'Too many Zone
4.3.3 Home Loc

Own Calling Add

< HGCAC:INT=467

AXE parameters

AXE parameters ar
customer/market r

Commands for par

< SYPAC:ACCESS=

< DBTRI;

< DBTSC:TAB=AX

< DBTRE:COM;

< SYPAC:ACCESS=

Subscriber Defin

< HGSDC:MSISDN

This command init

Subscriber Categ

All PPS subscribers

< HGSDC:MSISDN

< HGSDC:MSISDN

Moreover, the sub

< HGSDC:MSISDN

Parameters spec

OICK Originating I
originating call acc

TICK Terminating
terminating call ac

TS11 Teleservice "

Default settings fo
HTRAN, Ref. [17].

4.3.4 Signalling

See Chapter 2.1.6

4.4 SCP/gsm

4.4.1 Size Alter

See Chapter 2.1.1

4.4.2 Charging

It is possible to ge
Data.

4.4.3 Signalling

See Chapter 2.1.6

Besides that, addit

IN Protocol Hand

The SCP/gsmSCF a
gsmSSF during an

< PHGTI:GTA=467

Nature of address

Block name: INTC

Parameter name:

To check the NA in

< TEST SYSTEM;

< PRINT VAR INTC

Value 3 indicates t

The local FSC orga

5 USSD

5.1 Introduc

The feature USSD

sent from Charging

The SDP communi

 SDP will reach

 SDP will reach

For the first case s

So to reach HLR no

In the following ex
this chapter.

5.2 MSC Exc

5.2.1 Size Alter

Some size alteratio

5.2.2 Exchange

There are a few pr

< MGEPC:PROP=U

0-1 Handling of GS

< MGEPC:PROP=U

0-4 Escape code u

< MGEPC:PROP=U

0-1 Supplementar

< MGEPC:PROP=S

0-1 Allowance of n
case the MS is res

5.2.3 USSD in V

The USSD handler

operation is:

 Forwarded to t
 Sent to a local
 Rejected

The code entered b

A service code is b

 d=1, 2, or 3 ch
 X=2 or 3 decim
 c=* together w

5.2.4 MSC/VLR
 The service code e
command). There

Dialled characters

The application ide

 APP-0, transfer
 APP-1, deny ap
 APP-2, indicatio
 APP-3, handlin

If the code entered

rejection message

Note:
All service and procedure codes not defined in the General Purpose Digit
Analysis have default APP-0, so there is no real reason to connect them and
define it in ANGSI. No text string can be connected to APP-0.

If additional inform

5.3 HLR Exc

5.3.1 Size Alter

Some size alteratio

5.3.2 Exchange

There is two USSD

< HGEPC:PROP=U

0-4 Escape code u

< HGEPC:PROP=M

Time of periodical

5.3.3 Number S

The number series

Unstructured Supp

The Number Serie

an MSISDN. The u
using a service cod

< HGPAI:USRF=US

< HGPAI:USRF=EN

< HGNSI:ONSA=6

< HGNSI:ONSA=7

Parameters spec

CHAR USSDSC-1 m
External Node Add

To send USSD app

< HGXAI:ENAP=x,

Parameters spec

ENAP(0-63) USSD

EADD External Nod

 IMSIND IMSI Indic

Note:
The IMSIND parameter is only necessary for USSD Call Back (see Chapter
7.3.1, Number Series Analysis for USSD CB). So in case that feature is not
used, IMSIND can be omitted from the previous command.

Then the IMSI num

external node, it is

Balance on Dema

For USSD to addre

The SDP configura

ENAP number mus

Example:

Without Multiple S

< HGNSI:ONSA=X

< HGNSI:ONSA=X

All subscribers hav

< HGXAI:ENAP=2,

< HGXAI:ENAP=5,

Now the configura

because due to mu

For OICK-210 the

< HGNSI:ONSA=X

 The new node

 For OICK-210 t
 For OICK-310 t
 For OICK-310 t

and consequently

< HGXAI:ENAP=20

< HGXAI:ENAP=23
 < HGXAI:ENAP=56

< HGXAI:ENAP=59

5.3.4 Signalling

Subsystem numbe

< C7NSI:SP=2-SD

GT Analysis:

< C7TZI;

< C7TCI;

< C7GCI:GTRC=gt

< C7GSI:TT=0,NP

< C7TAI;

6 SMS cha

6.1 Introduc

The feature SMS c

receiving SMS mes

Involved nodes are

Preconditions

The following cond

 The operationa
 The basic exch
 Charging Syste
 The MSC/VLR/S
 Corrections for
 Parameter BNU

Note:
B-numbers, Routing Case Numbers and the values of IST parameters and so
on used in this specification may be changed in a real application due to
adaptation to existing data in operational nodes. Other parameters concerning
triggering should be adapted to an operational environment of a Service
Provider.
 Charging System I

Add on software

This function can c

Note:
The corrections listed in Table 24 are the ones that are released at the time
this document is being written; however they might be changed in the future.
Please contact local FSC for assistance.
 6.2 MSC Exc

This chapter descr

6.2.1 Traffic An

Definition of Rou

The function of the

< EXROI:R=PPSSM

< EXRBC:R=PPSSM

Parameters

FNC Function Code

BO B-number Orig

EO End-of-selectio

Connection of de

Software devices m
devices can be use

< EXDRI:R=PPSSM

De-blocking of d

The software devic

< BLODE:DEV=TC

Note:
The command is only allowing deblocking of maximum 32 devices in one
command. Repeat the command if more devices are needed.

A-number analys

The A-number ana

End of Selection
 The End-Of-Select

Size alteration eve

< ANESI:ES=5037

< ANESI:ES=5038

Parameters

ES End of Selectio

ESS Normal EOS S

Activation:

< ANEAI:ES=5037

< ANEAI:ES=5038

Note:
The EOS codes 5033-5036 are also used by TCON but they should not be
defined in the EOS analysis.

To make the B-num

number not found

Example:

< ANEPI:ES=100;

< ANESI:BE=EO-0

< ANESI:BE=EO-1

< ANEPE;

< ANEAI:ES=100;

In case of EOS 100

Routing Case ana

To make the B-num

EOS codes from th
"SC address not al

< ANRSI:RC=800,
< ANRSI:RC=801,

< ANRAI:RC=800;

< ANRAI:RC=801;

RC Routing Case

ES End of Selectio

B-number analys

The changes in the

Parameter BNUME
sent as B-number

B-number Analys

When a mobile PPS

PPSSMS route). Na
solution is based o
International B-nu

Example 1:

All B-numbers are

will generate EOS
319 subscriber wil
< ANBZI;

< ANBCI;

< ANBSI:B=199-3

< ANBSI:B=199-3

< ANBSI:B=199-3

< ANBSI:B=199-3

< ANBSI:B=199-3

< ANBSI:B=199-3

< ANBSI:B=199-3

< ANBSI:B=198-3

< ANBSI:B=198-3

< ANBSI:B=198-3

< ANBAI;

B=.... Called party

M=4 Modification o

RC=71 Routing Ca

RC=800 Routing C

RC=801 Routing C

ISK=IST-19900 IN

ISK=IST-19800 IN

NW Specifies that

L Called party num

Example 2:

The short code 456

generate EOS 503
of SMS, as B-numb
< PNBZI;

< PNBCI;

< PNBSI:BO=199,

< PNBSI:BO=199,

< PNBAI;

< ANBZI;

< ANBCI;

< ANBSI:B=200-3

< ANBSI:B=200-3

< ANBSI:B=200-3

< ANBSI:B=200-3

< ANBSI:B=200-3

< ANBSI:B=200-3

< ANBSI:B=200-3

< ANBSI:B=198-3

< ANBSI:B=198-3

< ANBSI:B=198-3

< ANBAI;

B=.... Called party

BNT B-number Typ

M=4 Modification o

RC=71 Routing Ca

RC=800 Routing C

RC=801 Routing C

ISK=IST-19900 IN
ISK=IST-19800 IN

NW Specifies that

L Called party num

Example 3:

All B-numbers with

number with intern
and country code 3

< ANBZI;

< ANBCI;

< ANBSI:B=199-3

< ANBSI:B=199-3

< ANBSI:B=199-3

< ANBSI:B=199-3

< ANBSI:B=199-3

< ANBSI:B=199-3

< ANBSI:B=199-3

< ANBSI:B=198-3

< ANBSI:B=198-3

< ANBSI:B=198-3

< ANBAI;

B=.... Called party

M=6 Modification o

RC=71 Routing Ca

RC=800 Routing C

RC=801 Routing C

ISK=IST-19900 IN
ISK=IST-19800 IN

NW Specifies that

L Called party num

6.2.2 SMS-Trigg

This chapter descr

new data needed f

Trigger Detection

No changes with re

The armed DP3 is

For terminating SM

Service Key and

The SK identifies t

There are 2 SKs de

The values for the

The Triggering a
Figure 16 Trigger

This part of the do

All comments give

6.2.2.1 SMS/ Tab

Use existing value

6.2.2.2 SMS/ Tab

Use existing value

6.2.2.3 SMS / Ta
It is recommended

< DBTRI;

< DBTSI:TAB=SHT

< DBTRE:COM;

For the meaning o

6.2.2.4 SMS / Ta

The PPS SMS serv

For more informat

6.2.2.5 SMS / Ta

There is no pointer

DT Commands def

< DBTRI;

< DBTSI:TAB=SHT

< DBTRE:COM;
See more details f

6.2.2.6 SMS / Ta

Refer to Chapter 4

6.2.2.7 SMS / Ta

See Section 4.2.4.

6.2.2.8 SMS / Ta

For PPS SMS the s

See Section 4.2.4.

6.3 Paramet

6.3.1 New Para

These parameters

These values shou

Block SHCC

Make sure that the

6.3.2 New Para

These parameters

Block TCON

These parameters
= 240). Format: 0

Variable 307(8-15

Digit 4 to 6 of the
1 if LENGTH_OF_M

Not used MNCs sh

Example:

Specifies that subs

< TEST SYSTEM;

< PRINT VAR TCO

< PRINT VAR TCO

< SET VAR TCON 3

< SET VAR TCON 3

< SET VAR TCON 3

< SET VAR TCON 3

< SET VAR TCON 3

< SET VAR TCON 3

< SET VAR TCON 3

< SET VAR TCON 3

< SET VAR TCON 3

< SET VAR TCON 0

< SET VAR TCON 0

< END TEST;

Block MTVS

Variable 162(3)/B0

0 = Always check

1 = Do not check i

Block MSMO

A parameter speci
parameter for han

Bit 0 in variable 96

Bit 2 in variable 96

Bit 3 in variable 96

The allowed combi

* Check is only do
 ** Check is only d

Example:

In case of technica

< TEST SYSTEM;

< PRINT VAR MSM

< SET VAR MSMO

< SET VAR MSMO

< SET VAR MSMO

< END TEST;

Block MSMT

A parameter speci
faults. A set of par

Bit 0 in variable 23

0 = SMS will not be delivered

1=SMS will be delivered

Bit 1 in variable 23

0=setting waiting flag in MTV

1=sending an Unknown Subscriber failure code to MSMTAP

Note:
This parameter is related to Market Adaptation TR HD25194, this EC has been
created in order to meet different customers' requirements. WAITINGFLAG
parameter in MSMT is used to select one of two different solutions, queuing
the charged MT SMS messages in the Service Center, or deleting the charged
MT SMS messages in the Service Center if the subscriber has no money or not
enough money on the account. This parameter will be set by the customers.

0 = SC address
1 = originating address
 0 = SMS SMS-STATUS-REPORT NO CHARGING
1 = SMS SMS-STATUS-REPORT CHARGING

nating OICKs.

Just specify one OICK value once in the table. The search is done from
NOOFOICKS to 1, reporting the fist hit.
Since the storing of the OICK-values are done in a record, a mechanism has
been put in place in block MSMT to prevent any attempt to decrease the size
of SAE 500 below NOOFOICKS+1. If such a decrease is attempted the SAAII
command will be denied with a fault code. Also problems may occur if later on
the parameter NOOFOICKS has to be increased. So before every new setting
for parameter NOOFOICKS verify that the SAE 500 in block MSMT has at least
NOOFOICK+1 individuals and if not, increase it to at least NOOFOICK+1:

< SAAEP:SAE=500,BLOCK=MSMT;
 llows the PPS subscriber to call/send SMS for as long as the prepaid account is provisioned.

Ms) that are installed in the SCP during installation procedure.

CS20_NAT_PREFIX_TIME
CS20_SMSSRVKEY_NRANAX
CS20_MOSMSPRE_CREANUM
CS20_MTSMSPRE_CREANUM
CS20_SMSFAULTCDE_TIME.
SSD, then followed by voice connection between calling and called party.
 PPS36_FORWSUPPR_INITCALL_R1A##
PPS36_SUPPRFORW_INITCALL_R1A##

ut.

This is valid when only one SDP handles the USSD CB queries. In the other
case an extension of the B-number analysis must be done, to send the
InitialDP to the right SCP/SDP.

< ANBSI:B=28-#1000,M=1,ISK=IST-1,RC=71,L=5-28, CC=75;

< ANBSI:B=28-#1001,M=1,ISK=IST-2,RC=71,L=5-28, CC=75;

Where the number after the USSD Call Back prefix is the SDP Id (2 digits).
This value is set in the SDP configuration.

The User Functions USSDSC and ENAP3SC might already be defined, if so

define the number series for USSD CB only.
ach one; there are more differences, but they will be specified in the following sections. Meanwhile,

PLMN cannot send a National address in the world network. The following figure shows a diagram of

Until now SSN=2 as gsmSSF and SSN=146 as gsmSCF have been used when
using CAMEL phase 2 for PPS. However, the standards (ETSI EN 300 927)
state that after 31-03-2001 only SSN=146 can be used for CAP, irrespective
if it is gsmSSF or gsmSCF (see parameter list of CAMPM01, CAMPM02).

In order to use SSN=146 for both gsmSSF and gsmSCF, it is necessary to

load three market corrections (blocks SHPM2, SHPM3 and C7TCP). By means
of those corrections, a new exchange property (MGEPC) -called SCPSSPUSE-
is defined (Block C7TCP).

The default value (=0) means that this node will behave as a gsmSSF. The
value 1 means that the node will behave as gsmSCF. This means that for an
SCP this value has to be changed to 1, when a new CAMEL ph.1/2 installation
is done, so it will behave as gsmSCF:
MGEPC:ID=SCPSSPUSE-1; ! Use this node as gsmSCF !

Each market should ask for those corrections if needed.

In this document SSN=146 is used for both gsmSSF and gsmSCF.

Sometimes it can be useful to have an integrated gsmSSF and gsmSCF

(SSCP), for instance, in a Test Environment. In such a case, both SSN=2 and
SSN=146 must be used. Be aware that according to CAMEL standardization
that architecture is not allowed, see previous Note.

The following SAE list needs to be checked and adapted for CAMEL. In this
section there are no guide values for the SAEs; if details or further
information is needed, see the Application Information for the different
software blocks.
For CAMEL PH1 a new Outgoing gsmSSF route must be defined because a
new BO is needed for the CONNECT operation.
"153" Originating Roaming CAMEL PH2
"154" Terminating Roaming CAMEL PH2
"155" Originating Roaming CAMEL PH1
ssage with the destination number, which is analyzed in this tree. The destination number received in
CAMELOUTGOINGR1 in OSR) is analyzed and the analysis tree (74) is obtained. After that, a jump is

For CAMEL PH1 things are slightly different since the received operation from
SCP is CONNECT instead of CONTINUE. As a consequence of OSR route, the
analysis will continue in BO 75.
R paragraph).

The first IST is not reached through B number analysis: it is defined at the
MIN route in VPLMN part. By means of that IST the HPLMN will be reached.
Once in HPLMN a new IST will be fetched from the B number analysis.

when using CAMEL PH1, another trigger tables set for CS1+ is also needed.
gsmSSF. This issue is further discussed in Section 8.2.3.10, CAMEL PH1/ Table SHISTTOTDP - gsmSSF

For PrePaid using CAMEL with CME20 this table is not needed.
 For PrePaid using CAMEL with CME20 this table is not needed.

s found in the SHTDPS table with the same parameter name (TSOID).

e is used, more parameters are needed. The parameter specifies the row identity.

ephony (E.163, E.164).

AMEL.
nd in the SHTDSP table with the same parameter name (TSDID). DSTNAME Destination service Name.
ress. FDSTADR=7 indicates the use of CSI Global Title and Subsystem Number.

No SK parameter definition is needed.

ue for CAMEL is CSI (CAMEL Subscription Information).

case of SCP restart or error in access-script) then the call can SURVive (default value) or be RELeased.

ding the Initial DP or AssistRequestInstructions. The call can SURVive or may be RELeased (default

ntout is required (for example: SHR=8 and SHS=5).

2].
`1' - corresponds to CS1+
`2' - corresponds to CAP

`3' indicates White.

2.4.9, Table SHIST-SSF IN Service Trigger, if further details about the previous parameters are

rked as CAMEL subscriber (HGCMI command, see Section 8.4.4, HLR subscriber definition on page

IST is not reached through number-B analysis. The IST parameter is defined
at the MIN route in VPLMN part, to point out the triggering table for a specific
HPLMN.
ere are defined for the CAP phase 2 protocol.

vice invocation if a complete number is obtained by gsmSSF. This issue is further discussed in Chapter
 For PrePaid using CAMEL with CME20 this table is not needed.

P without examination by the SSF-AM.

For PrePaid using CAMEL with CME20 this table is not needed.

s the nature and numbering plan of the address.

eter is the entry to SHTSO table and the reference is found in the SHTDPS table with the same

ailable in the Service Provider network.

RGADR='2' indicates the use of GT+SSN. In case this value is used, more parameters are needed. The

obal title to be used in SCCP.

gsmSSF's own global title. "1" means ISDN/Telephony (E.163, E.164).

F.
 see Model DT for MSC/SSF, Reference [2].

he entry to SHTSD table, and the reference is found in the SHTDSP table with the same parameter

ring.

STADR=7 indicates the use of CSI Global Title and Subsystem Number.

be used in SCCP.

No SK parameter definition is needed.

MMEN

ming
MEL

ke the default values); they are needed only if tracing printout is required (For example, SHR=8 and

PS - TDP Service Data.

en gsmSSF and SCP/gsmSCF is established. It can be defined with default parameters, therefore it is

s, see Model DT for MSC/SSF, Reference [2].

S - SSF Invoke Network Signalling.

see Model DT for MSC/SSF, Reference [2] for further information.

dpsid,TINSID=tinsid;

MMEN

ming
MEL

o CAP.

nicating with the SCP. `3' indicates White.

etection Point.
MMEN

ming
MEL

work Signalling.

that calls to IVR are possible using short number.

ice Trigger.

calls, TDP12.

MENT

ing
nating
with
L PH2

ing
natin
s, with
L PH2

to TDP.

tingSSPIPRoutingAddress, correlationID and sCFID is received.

dialog. That means, for instance, that CorrelationID can be send as a part of B-number marked with
ossibilities.

o SCF with correlationID.

received in SSF and REL is sent to the assisting SSF. Call released resulting in REL sent from leg1 to

Origination

GNAM

ISTI

vice Origination.

Destination

vice Destination.
Data

G_SS

SHTDPS - TDP Service Data.

k Signalling

SHINS table is not necessary in the assisting SSF.

gger Detection Point

isting SSF

TID COMMENT

Roaming
Originatin
g CAMEL
PH2

er Detection Point.

igger Network Signalling

t information about how to send correlation ID to SCF is included in SHTNS table.

isting SSF

COMMENT

Assisting SSF

nal parameters must be defined:

ple for CAMEL PH2,

 SCFIDLT

ntry is found in the SHIST table.

oute;

srroute;

RINDEX has sequential value depending of SSFRoute definition order.

harging Case to be applied to the incoming leg, (8 enables CDR).

s the Charging Case to be applied to the outgoing leg in the case of basic routing, (0 enables CDR).

es the Charging Case to be applied to the outgoing leg in the case of direct routing, (0 enables CDR).

to be used for the call, Direct Routing (DR) or Basic Routing (BR). BR is the default value, it is not

The ISCC and OSBCC parameters are discussed in Chapter 2.1.2, Charging
Data.

eter specifies the method of transport of the Correlational ID. '0' stands for carried in B-Number

s that the SCF provided Calling Party Number overwrites the Calling Party Number received from the

pecifies the position in the B-Number of the first digit of the CorrelationId.

es the length of the CorrelationId.

ecifies the method of transport of the SCPId Value '1' stands for Carried in B-number implicitly. It
ed then the SCFIDLT and SCFIDST parameters cannot be null.
e length of the SCFid.

s the position in B-number of the first SCFid digit.

parameters can be found in the appropriate Table Description.

SF/ Table SHIST - SSF IN Service Trigger

mple for CAMEL PH2, assisting SSF

BCSMTYP COMMENT

ORIG Roaming CAMEL

PH2 assisting SSF

ing.

e number of called party digits that have to have been collected if the SCF is to be invoked at TDP2

pter 4.2.4.9, Table SHIST-SSF IN Service Trigger.

SF/ Table SHISTTOTDP - SSF IST to TDP

ues example for CAMEL PH2, assisting SSF

DPNO COMMEN
T

DP2 Roaming
CAMEL
PH2
assisting
SSF

.2.4.10, Table SHISTTOTDP - SSF IST to TDP.

r assisting SSF

T-82, RC=71;

SSF (VPLMN).
change Data

defined in every MSC VPLMN so it is possible for the PrePaid subscriber to make any roaming type of

nalling is used. SCP/gsmSCF, HLR and MSC SS7 addresses of HPLMN nodes need to be defined as
ot send a National address in the world Network.

The following SAE list needs to be checked and adapted for CAMEL. In this
section there are no guide values for the SAEs; if details or further
information is needed, see the Application Information for the different
software blocks.

ted to CAMEL phase 1 & 2, VPLMN

COMMENT

The function also handles some call related

Intelligent Network Application Protocol (INAP)
operations and CAMEL Application Part (CAP)
operations received from the SCF.

Seized when an operation is received from the

SCF.

Define number of dialogue individuals in block

SHPM2 for CAMEL V1.

Define number of dialogue individuals in block

SHPM3 for CAMEL V2.
Block MTVIN stores mobile subscriber data
related to CAMEL.

602 MTVIN stores data related to O-CSI for

visiting mobile subscribers.

603 MTVIN stores data related to MISI for

visiting mobile subscribers.

622 MTVIN stores data related to SS-CSI for

visiting mobile subscribers.

meters
parameter set activation in MSC/gsmSSF node have the following format:

D,PSW=....;!Ask local FSC for password!

ETNAME=setname,NAME=name,VALUE=val;

ED;

Model DT MSC, Ref. [2].

ctivation in MSC/gsmSSF, VPLMN

VALUE COMMENT

1 Active CAMEL PH1 in

gsmSSF.

1 Active CAMEL PH2 in

gsmSSF. It is mandatory
to activate MSCNF384
before.

1 Subscriber INFO to
HLR/MAP.

1 Subscriber INFO to
HLR/CAP.

1 Active Extended CAMEL in

gsmSSF.

0 Determines Call Barring in

the gsmSSF if the gsmSCF
Modifies the destination
number. "0" disables the
barring.

1 Supports administration of
Location Numbers in
MSC/VLR and GMSC.
Determines whether
C 1 Extended CAMEL applies
for all circuit switched
 basic services except
emergency calls or only for
telephony and auxiliary
telephony.

"0" Extended CAMEL with

IN category key provided
for all basic services except
emergency calls.

"1" for telephony and

auxiliary telephony.

1 Active CAMEL PH1 in GMSC

1 Active Extended CAMEL in

GMSC.

1 Active CAMEL PH2 in GMSC

he SubSystem Number (SSN) definition for CAMEL before starting the definitions of Signalling System

bers for CAMEL phase 1&2, VPLMN

COMMEN
T

gsmSSF
(HPLMN)
CAMEL
PH1

gsmSSF
(HPLMN)
CAMEL
PH2

found in Plexview and can be checked by using the following commands:

SN >;

SN >;
d sections CAMEL PH1 will be differentiated from CAMEL PH2 because they need separate trigger tables
n the call returns from gsmSCF.

SSF Routing Data

The exchange that is going to be used in the following sections is different

from the one studied before and therefore data can differ. However, it is
supposed that the VPLMN has the same data defined (RC, TRACO, B-number
and so on) as the HPLMN. This issue must be studied carefully for a specific
case.

nks

links are needed. Use the same as for the CS1+ protocol. See Section 4.2.3.1, APC links.

are Routes towards/from the gsmSSF

oftware route TRACO and the incoming software route TRACI are the same ones as defined for CS1+
2.3.2, Software Routes towards/from the SSF).

SFTRAM is connected to TRACO software route in the TRAM and a new INCOMING Route to the gsmSSF

oftware route CAMELINCOMINGR is defined by the following commands:

CAMELINCOMINGR1;

=SSFTRAM;

SFTRAM is connected to TRACI software route in the TRAM and to the new OUTGOING Route defined in

oftware route,CAMELOUTGOINGR1, (different name can be done), is established.

=CAMELOUTGOINGR1;

=SSFTRAM;

OUTGOINGR1 the B origin for all outgoing calls from the PrePaid service is specified.

=CAMELOUTGOINGR1;

=BO,VAL=74,SCAP=1;
=CO,VAL=8,SCAP=1;

Routes

meter stores the IST value which triggers the table to use the CAMEL protocol in proper routes (FNC
ee Table 3.

ute,DETY=MIN,FNC=fnc;

ute,MIS1=mis1,BO=bo,CO=co,MIS2=mis2,MIS5=113;

name (Ex. 9MIN2 fnc=9, INoperator Group=2)

vice Type

Code according to traffic cases, see Table 3.

e used in the triggering tables. "113" Originating Roaming CAMEL PH2 VPLMN.

tor group (INOPER defined in MGISI command).

-no analysis.

Analysis for HPLMN subscribers

ommand define IMSI analysis for PrePaid subscriber allowing CAMEL to be used.

S=51499,M=7-4670727,NA=4,ANRES=MAPVER-2& OBA-30& CBA-40& CBAZ-40& INOPER-2& PLMN-1&

-2& MAPVER-2;

cifies that MAP V3 is used.

orted CAMEL phase2.

tor group for access to intelligent network.

ption Type allowed.

SF, Routing Case for Outgoing Routes

d. See Chapter 4.2.3.5, Routing Case Analysis.

that the SS7 interconnection route with HPLMN is already defined in the VPLMN. This also applies to the

CCH=NO, R=route, SP=MM1;

mber Analysis for O-CSI

umber origins used for O-CSI

ON

IN origInating and Terminating CAMEL calls (MIN with FNC=9 and

ng CAMEL calls in GMSC (MIN with FNC=11),

ting CAMEL HPLMN GMSC (MIN with FNC=12).

ng CAMEL at call forwarding (MIN with FNC=10).

R Route from CAMEL, TRACO function.

for O-CSI calls

07... is dialled:

-0,M=2, RC=71, cc=cc, BNT=1,L=13; In case 46707... is dialled:

-4,RC=71,CC=cc,BNT=1, L=11;

for IN triggering forwarded calls

ysis of IN triggering forwarded calls the following command is needed:

-46, RC=71, L=11, D=10-1;

for the CONTINUE operation received from the SCP

en triggered to the SCP, the SDP has been checked that the PPS subscriber has credit enough so as to
he call, and the SCP sends down to the MSC a CONTINUE message with the destination number, which
his tree. The destination number received in the CONTINUE is exactly the same number that the one
SCP in tree B=74 except for the case where IVR Frontend is used, as then the SCP translates the
data in TRACO (CAMELOUTGOINGR1 in OSR) is analyzed and the tree analysis (74) is obtained. After
made to B=30, where national and international calls are discriminated.

For CAMEL PH1 things are slightly different since the received operation from
SCP is CONNECT instead of CONTINUE. As a consequence of OSR route, the
analysis will continue in BO 75.
 ANBSI:B=74-00, M=2, F=74, L=13;

ANBSI:B=74-46, RC=41, BNT=1, L=11;

ANBSI:B=74-49, F=41, L=11-16;

ANBSI:B=74-707, M=0-46, F=74, BNT=1, L=9;

or CAMEL PH1 the analysis is done in B-number (75) Destination. The number is removed (M=11) and
e call queue index is only sent to TRACO route:

ANBSI:B=75-46707,RC=71,CC=cc,L=16,NW,ISK=IST-14,M=11;

ANBAI;

3.3 CAMEL PH2-gsmSSF triggering tables Originating/Terminating calls

ervice Key and IN Service Trigger

he SK identifies the service to be invoked in the SCP/gsmSCF, the SK is associated by means of

ubscriber command when is marked as CAMEL subscriber (HGCMI command, see HLR paragraph).

ote:
IST is not reached through number-B analysis. The IST parameter is defined
at the MIN route in VPLMN part, to point out the triggering table for an
specific HPLMN.

Table 76 Triggering Parameters for CAMEL PH2 for Charging System, VPLMN

Type of access IST

Originating calls 113

Protocol Type

The Protocol Type decides which service parameters the signalling network can handle; the
trigger tables presented here are defined for the CAP V2 protocol.

Trigger Detection Point

The armed DP2 is the Trigger Detection Point (TDP) for the PrePaid roaming service. The
DP number 2 indicates service invocation if a complete number is obtained by gsmSSF. This
issue is further discussed in Chapter 8.2.3.10, CAMEL PH1/ Table SHISTTOTDP - gsmSSF
IST to TDP.

For more information about BCSM please see the document Service Switching Function,
Basic call handling, Reference [13].
Figure 21 Trigger Table Model for Roaming with CAMEL PH2, VPLMN

8.3.3.1 VPLMN-CAMEL PH2/ Table SHEXTRANS - gsmSSF Extension Field Translation

The Extension Translation Field table is a table which translates between INAP extension
tags and AMTAG tags.

Note:
For PrePaid using CAMEL with CME20 this table is not needed.

8.3.3.2 VPLMN-CAMEL PH2/ Table SHEXTLIST - Extension Field List Table

The Extension List Field table is a list of parameters which will be transferred
from the AMTAG to the INAP without examination by the SSF-AM.

Note:
For PrePaid using CAMEL with CME20 this table is not needed.

8.3.3.3 VPLMN- CAMEL PH2/ Table SHTSO - gsmSSF Trigger

Service Origination

The function of the SHTSO table is to hold information on the

gsmSSF's own address such as the nature and numbering plan of
the address.

Table 77 SHTSO Parameters values example for CAMEL PH2 in VPLMN

TSOI FORGADR ORGNAM

D E

113 0 VGSMSSF

8.3.3.4 VPLMN-CAMEL PH2/ Table SHTSD - gsmSSF Trigger

Service Destination (SCP/gsmSCF)

The function of the SHTSD table is to provide information that

allows routing to SCP/gsmSCF; the routing for the calls triggered
from the VPLMN is based on GT + SSN.

For the commands definition of the SHTSD table refer to Model DT

for MSC/SSF, Reference [2].

Table 78 SHTSD Parameters values example for CAMEL PH2 in VPLMN

TSDI FDSTADR DSTNAME DPC GTTRA

D N

113 7 GSMSCF - 0

See parameters information in Chapter 8.2.3.4, CAMEL PH1/ Table

SHTSD - gsmSSF Trigger Service Destination (SCP/gsmSCF).

8.3.3.5 VPLMN-CAMEL PH2/ Table SHTDPS - gsmSSF TDP Service

Data

Note:
No SK parameter definition is needed.

Table 79 SHTDPS Parameters values example for CAMEL PH2 in VPLMN

TDPSI TSDID TSOID CESS CTMP EVTYPE USI SK

D
113 113 113 CSI CSI YES CSI -

See parameters information in Chapter 8.2.3.5,

CAMEL PH1/ Table SHTDPS - gsmSSF TDP Service
Data.

8.3.3.6 VPLMN-CAMEL PH2/ Table SHINS - gsmSSF

Invoke Network Signalling

This table details which parameters should be

included when a dialogue between gsmSSF and
SCP/gsmSCF is established. The table can be defined
with default parameters, therefore only the row must
be defined.

MML commands definition for the SHINS table would

look like the ones below, see Model DT for MSC/SSF,
Reference [2].

< DBTRI;

< DBTSI:TAB=SHINS,INSID=insid;

< DBTRE:COM;

Table 80 SHINS Parameters values example for CAMEL PH2 in VPLMN

INSID COMMENT

113 Roaming originating/Terminating CAMEL PH2

See parameters information and default values in

Section 4.2.4.6, Table SHINS - SSF Invoke Network
Signalling.

8.3.3.7 VPLMN-CAMEL PH2 / Table SHTDP-gsmSSF

Trigger Detection Point

MML commands definition of the SHTDP table would

look like the following ones, see Model DT for
MSC/SSF, Reference [2].

< DBTRI;
<
DBTSI:TAB=SHTDP,TDPID=tdpid,DIAGTYP=diagtyp,
PROTI=proti,TDPSID=tdpsid,TINSID=tinsid;

< DBTRE:COM;

Table 81 SHTDP Parameters values example for CAMEL PH2 in VPLMN

TDPI DIAGTYP PROTI TDPSID TINSID TLISTID

D

113 3 2 113 113 -

If more information related to the SHTDP parameters

is needed, see Chapter 8.2.3.7, CAMEL PH1 / Table
SHTDP-gsmSSF Trigger Detection Point.

8.3.3.8 VPLMN-CAMEL PH2/ Table SHTNS - gsmSSF

Trigger Network Signalling

Table 82 SHTNS Parameters values example for CAMEL PH2 in VPLMN

BRISRID BROSRID OSBCC
TNSI ISCC SCFIDTY
D DRISRID DROSRID OSDCC

113 3 4 9 2 0

See parameters information in Chapter 4.2.4.8, Table

SHTNS - SSF Trigger Network Signalling.

8.3.3.9 VPLMN-CAMEL PH2/ Table SHIST-gsmSSF IN

Service Trigger

Table 83 SHIST Parameters values example for CAMEL PH2 in VPLMN

IST TNSID SSFTYPE NUMDIG BCSMTYP

11 113 I 0 ORIG
3
More information regarding the SHIST parameters
can be found in Chapter 8.2.3.9, CAMEL PH1/ Table
SHIST-gsmSSF IN Service Trigger.

8.3.3.10 VPLMN-CAMEL PH2/ Table SHISTTOTDP -

gsmSSF IST to TDP

For Roaming Originating calls in CAMEL PH2 TDP used

is TDP2.

Table 84 SHISTTOTDP Parameters values example for CAMEL PH2 in V

IST TDPI TDPNO COMMENT

D

11 113 DP2 Roaming Originating call

3 CAMEL PH2

See parameters information in Chapter 4.2.4.10,

Table SHISTTOTDP - SSF IST to TDP.

8.3.4 Exchange data for assisting SSF in

VPLMN

For more information check Chapter 8.2.5, Exchange

data for assisting SSF for HPLMN.

In SHTNS table it is included important information

about how to send correlation ID when ETC is sent
from gsmSCF to initiating SSF. This is the same table
which is used for normal originating or terminating
call scenario.

8.3.4.1 VPLMN-CAMEL PH2 Assisting SSF/ Table

SHTNS - SSF Trigger Network Signalling

To build ARI, special triggering table must be defined.

Table 85 SHTNS Parameters values example for CAMEL PH2 in VPLMN,

SSF
BRISRID BROSRID OSBCC
TNSI ISCC SCFIDTY C
D DRISRI DROSRID OSDCC
D

153 3 4 8 0 1 A
S
n
 s
C
I
n
(

Table 86 SHTNS Additional parameters values example for CAMEL PH2

assisting SSF (correlation ID)

TNSI CLIDATA CLIDTYP CLIDST CLIDLTH SCFIDST

D

153 0 0 6 5 1

Parameters

TNSID Trigger Network Signalling Identity. The

reference to this entry is found in the SHIST table.

BRISRID RINDEX value in ISR route; to find RINDEX:

< SHRSP:ISR=isrroute;

DRISRID Direct Routing Incoming SSF Route Id (see

BRISRID).

BROSRID RINDEX value in OSR route; to find

RINDEX: < SHRSP:OSR=osrroute;

DROSRID Direct Routing Outgoing SSF Route Id (see

BROSRID).

Note:
RINDEX has sequential value depending of SSFRoute definition order.

ISCC Incoming SSF Charging Case. It

specifies the Charging Case to be applied
to the incoming leg (8 enables CDR).

OSBCC Outgoing SSF Basic Charging

Case. It specifies the Charging Case to
be applied to the outgoing leg in the case
of basic routing (0 enables CDR).

OSDCC Outgoing SSF Direct Charging

Case. It specifies the Charging Case to
be applied to the outgoing leg in the case
of direct routing (0 enables CDR).
 ROUTTYP Route Type. It specifies the
type of routing to be used for the call,
Direct Routing (DR) or Basic Routing
(BR). BR is the default value, is not
neccesary to type it in the command line.

Note:
The ISCC and OSBCC are discussed in Chapter 2.1.2, Charging Data.

CLIDTYP CorrelationId Type.

This parameter specifies the
method of transport of the
Correlational ID. '0' stands
for Carried in B-Number
implicitly.

CLIDATA Calling Party Id

Data. '0' stands for SCF
provided Calling Party
Number overwrites the
Calling Party Number
received from the incoming
side.

CLIDST Correlation Id Start

Position. It specifies the
position in the B-Number of
the first digit of the
CorrelationId.

CLIDLTH Correlation Id
Length. It specifies the
length of the CorrelationId.

SCFIDTY SCPId Type.This

parameter specifies the
method of transport of the
SCPId. Value'1' stands for
Carried in B-number
implicitly. It should be noted
that if the value 1 is used
then the SCFIDLT and
SCFIDST parameters cannot
be null.

SCFIDLT Length of SCPId. It

specifies the length of the
SCFid.

SCFIDST SCFId Start

position. It specifies the
 position in B-number of the
first SCFid digit.

8.3.4.2 B-number analysis

definition to support
assisting Scenario in VPLMN

In the incoming TRACI route

from gsmSCF the
Correlation ID will be
analyzed and then the call
will be sent towards
assisting SSF.

< ANBSI:B=29-13251, L=5-

10, RC=xxx;

B B-number origin of
incoming route from SCF.

13251 Correlation ID.

RC RC towards assisting
SSF.

8.4 HLR-(HPLMN)
Exchange Data

8.4.1 Size Alteration

Data

Note:
The following SAE list needs to be checked and adapted for CAMEL. In this
section there are no guide values for the SAEs; if details or further
information is needed, see the Application Information for the different
software blocks.

Table 87 List os SAEs related to

SA BLOCK
E

602 HCSID
603 HCSID

604 HCSID

605 HCSID

500 HSDH3

604 HSDH3

500 HLUAP3

500 HREDAP3

500 HPSIAP3
500 HREDAP3

HLR node
parameters

Commands for
CAMEL
parameter set
activation in
HLR node have
the following
format.

<
SYPAC:ACCESS
=ENABLED,PS
W=....;!Ask
local FSC for
password!

< DBTRI;

<
DBTSC:TAB=A
XEPARS,SETNA
ME=setname,N
AME=name,VA
LUE=val;

< DBTRE:COM;

<
SYPAC:ACCESS
=DISABLED;

For a complete
DT file see
Model DT for
HLR, Reference
[4]. The
following
parameters are
used for CAMEL
parameter set
activation in
HLR node.

Table 88 Parameter Set Activatio

SETNAME NAME

GSMHRSF HLRNF498

GSMFNNS HLRNF497
F

GSMHRSF HLRNF496

GSMHRSF HLRNF746

8.4.2 HLR
Properties
and Roaming
Characteristic
s

In the HLR
node MAP
version 3 must
be allowed to
be used. The
following
command will
enable MAP v3:

<
HGEPP:ID=ALL
; !Print all
properties!

<
HGEPC:PROP=
MV3RESTRICTI
ON-2; !set
MAPv3!

To set the
Roaming Area
Characteristic
for roaming
area, allowing
CAMEL
subscription:

<
HGRCP:CHAR=
ALL; !Print all
roaming areas!

<
HGRCI:AREA=4
-
46707,CHAR=O
CSIPH2; !set
originating
Camel
subscription
information!

<
HGRCI:AREA=4
-
46707,CHAR=T
RAFFV3; !allow
use of MAPv3!

<
HGRCI:AREA=4
-
46707,CHAR=T
RAFFV2; !allow
use of MAPv2!

<!
HGRCI:AREA=4
-
46707,CHAR=E
XTCAMEL; !For
execution of
CS1+ in
HLPMN!

For visiting
roaming data:

<
HGRCI:AREA=4
-
49,CHAR=OCSI
PH2;
<
HGRCI:AREA=4
-
49,CHAR=TRAF
FV3;

8.4.3
SCF/gsmSCF
Global Title
Address

In the HLR the

address of
SCF/gsmSCP
needs to be
defined:

<
HGGSI:GSA=4
6707272001;

8.4.4 HLR
Subscriber
definition

The following
commands
need to be
defined for a
PrePaid
subscriber in
the HLR:

<
HGSUI:IMSI=5
149900000000
18,MSISDN=46
707271018,
PROFILE=1; !
GSM
subscription!

<
HGCMI:MSISD
N=4670727101
8,SK=80,OCTD
P=2,
GSA=4670727
2001,DEH=0,C
CH=2; !
Originating
CAMEL
subscription!

The parameter
DEH defines
what the
gsmSSF will do
in the following
three error
cases:

1. The gsmSSF
attempts to
invoke a
CAMEL Service,
but there is no
response from
the SCP.

2. There is a
communication
failure between
the gsmSSF
and the
gsmSCP at any
point during a
CAP dialogue,
when the
gsmSSF is
waiting for an
instruction
from the SCP.

3. The CAMEL
Service is
supported, but
the CAMEL
triggering of
originating and
forwarded calls
fails due to
incomplete or
incorrect
setting of IMSI
number series
analysis data
and/or
software route
data for IN
subscribers in
MSC/VLR.
 The permissible
values for this
parameter are
"Release Call"
(0) and
"Continue Call"
(1).

<
HGCMI:MSISD
N=4670727101
8,SK=80,TCTD
P=12,
GSA=4670727
2001,DEH=0,C
CH=2,I=N; !
Terminating
CAMEL
subscription!

<
HGCEC:MSISD
N=4670727101
8,SSLO=1; !
Sending
subscriber
state and
location
information!

8.5 HLR-
(VPLMN)
Exchange
Data

8.5.1 Size
Alteration
Data

Note:
The following SAE list needs to be checked and adapted for CAMEL. In this
section there are no guide values for the SAEs; if details or further
information is needed, see the Application Information for the different
software blocks.

Table 89 List os SAE

SA BLOCK
E
602 HCSID

603 HCSID

604 HCSID

605 HCSID

500 HSDH3

604 HSDH3

500 HLUAP3

500 HREDAP3
500 HPSIAP3

500 HREDAP3

HL
R
no
de
pa
ra
m
et
er
s

Co
m
m
an
ds
for
CA
ME
L
pa
ra
m
et
er
set
act
iva
tio
n
in
HL
R
no
de
ha
ve
th
e
foll
ow
in
g
for
m
at:

<
SY
PA
C:
AC
CE
SS
=E
NA
BL
ED
,P
S
W
=.
...
;!
As
k
loc
al
FS
C
for
pa
ss
wo
rd!

<
DB
TR
I;

<
DB
TS
C:
TA
B=
AX
EP
AR
S,
SE
TN
A
ME
=s
et
na
m
e,
NA
ME
=n
a
m
e,
VA
LU
E=
val
;

<
DB
TR
E:
CO
M;

<
SY
PA
C:
AC
CE
SS
=
DI
SA
BL
ED
;

Fo
r
co
m
ple
te
DT
file
,
se
e
Mo
del
DT
for
HL
R,
Re
fer
en
ce
[4
].
Th
e
foll
ow
in
g
pa
ra
m
et
er
s
ar
e
us
ed
for
CA
ME
L
pa
ra
m
et
er
set
act
iva
tio
n
in
HL
R
no
de
.

Table 90 Parameter

SETNAME NAME

GSMHRSF HLRNF498

GSMFNNS HLRNF497
F

GSMHRSF HLRNF496

GSMHRSF HLRNF746

8.
5.
2
HL
R
Pr
op
er
tie
s
an
d
Ro
a
mi
ng
Ch
ar
ac
te
ris
tic
s

In
th
e
HL
R
no
de
M
AP
ve
rsi
on
3
m
us
t
be
all
ow
ed
to
be
us
ed
.
Th
e
foll
ow
in
g
co
m
m
an
d
wil
l
en
abl
e
M
AP
v3
:

<
H
GE
PP
:I
D
=A
LL
;!
Pri
nt
all
pr
op
ert
ies
!

<
H
GE
PC
:P
RO
P=
M
V3
RE
ST
RI
CT
IO
N-
2;
!
set
M
AP
v3
!

To
set
th
e
Ro
a
mi
ng
Ar
ea
ch
ar
act
eri
sti
c
for
ro
a
mi
ng
ar
ea
,
all
ow
in
g
CA
ME
L
su
bs
cri
pti
on
:

<
H
GR
CP
:C
HA
R=
AL
L;
!
Pri
nt
all
ro
a
mi
ng
ar
ea
s!

<
H
GR
CI
:A
RE
A=
4-
46
,C
HA
R=
OC
SI
PH
2;

<
H
GR
CI
:A
RE
A=
4-
46
,C
HA
R=
TR
AF
FV
3;

<
H
GR
CI
:A
RE
A=
4-
46
,C
HA
R=
OC
SI
PH
1;

8.
6
S
C
P/
g
m
S
C
F-
(H
P
L
M
N)
E
 x
c
h
a
n
g
e
D
at
a

8.
6.
1
Si
ze
Al
te
ra
tio
n
Da
ta

N
ot
e:
The following SAE list needs to be checked and adapted for CAMEL. In this
section there are no guide values for the SAEs; if details or further
information is needed, see the Application Information for the different
software blocks.

Table 91

SA BLO
E

500 SSC
671 SSC

605 SCF

760 CAM

760 CAM
8.6.2
SCP/gs
mSCF
Signallin
g System
No.7

Own
Global
Title
Address
definitio
n

The IN
Protocol
Handling
Own
Global
Title
Address is
used by
the
gsmSSF
during a
Prepaid
Roaming
call. The
SCP/gsm
SCF
address
needs to
be
defined in
internatio
nal
format,
because it
is used in
internatio
nal
signalling
networks.

The
nature of
address
(NA) of
SCP is
normally
set as
national
number,
so it has
to be
changed
to
internatio
nal
number
format.
See
Chapter
4.4.3,
Signalling
Data SCF
on page
83 about
IN
Protocol
Handling
own
address
item.

To specify
own
SCP/gsm
SCF
address
the
following
command
is used:

<
PHGTI:GT
A=46707
272001;

It is
assumed
that links
and
routing
between
SCP-MSC
and MSC-
GMSC in
HPLMN
already
exists
(CCITT7 -
MTP layer
up and
working).
To check
links and
routing
definition
the
following
command
s may be
used:

<
C7LTP:LS
=ALL;

<
C7RSP:DE
ST=ALL;

It is also
needed to
check Sub
System
Number
(SSN)
definition
for CAMEL
before
starting
defined
Signalling
System
No.7
routing
data.

Table 92

BLOCK
NAME

CAMPM0
1

CAMPM0
2
To check
the SSN
for CAMEL
the
following
command
s can be
used:

< TEST
SYSTEM;

< PRINT
VAR
<BLOCK>
<ZZSSN>
;

Global
Title
definitio
n

For
signalling
between
gsmSSF
and
gsmSCF
in HPLMN,
the
routing is
based on
the
Destinatio
n Point
Code +
Sub
System
Number
(SSN).
For
signalling
between
gsmSSF
(VPLMN)
and
gsmSCF
(HPLMN),
the
routing is
based on
the Global
Title
address
(GT) +
Sub
System
Number
(SSN).

<
C7NPC:SP
=2-200,
CON,
MSG=1;

<
C7NSI:SP
=2-200,
SSN=146
; !(SSN
definition
for
gsmSSF)!

< C7TZI;

<
C7TCI; !
Own
gsmSCF
GT (must
be
already
defined)!

<
C7GCI:GT
RC=10,PS
P=OWNS
P,PTERM;

<
C7GSI:NS
=467072
72001,NA
=4,NP=1,
TT=0,GTR
C=10; In
gsmSCF it
is
necessary
to define
Global
Title
address
of the
gsmSSF
located in
the
VPLMN.

<
C7GCI:GT
RC=3,PSP
=2-
200,PINT
ER;

<
C7GSI:TT
=0,NP=1,
NA=4,
NS=49,G
TRC=3;!
(VPLMN
gsmSSF
GT)!

< C7TAI;

PINTER
The
Signalling
Point (SP)
is defined
to be an
intermedi
ate
primary
SP.

To be
able to
reach a
node
outside
the
HPLMN
the
routing
has to go
through
an
internatio
nal
Signalling
Transfer
Point
(STP).
The STP
node will
analyse
the GT
number
and
reroute it
to the
VPLMN's
STP.

9
AIR

9.1
Introdu
ction

The AIR
will
enable
USSD
User
Account
Refill and
USSD
Balance
on
demand
for
Charging
System
subscriber
s. The
AIR
communic
ates with
HLR
through
EMAP.
The AIR
can
communic
ate with
HLR
directly
but this is
not
recomme
nded due
to
redundan
cy. The
recomme
nded
communic
ation is
through
an STP.
GMSC can
behave as
an STP
(signalling
transfer
point). So
to reach
HLR from
AIR,
routing
can be
done
using the
GMSC
node in
between,
using
already
existing
signalling
links. In
the
following
sections it
is
assumed
that the
HLR is
Stand
Alone and
that the
AIR is
connected
through
GMSC.

9.2
SCP
Exchan
ge Data

<
C7SPI:SP
=2-5861;

<
C7SPI:SP
=2-5862;

<
C7PNC:SP
=2-
5861,SPI
D=AIRVS
1A;

<
C7PNC:SP
=2-
5862,SPI
D=AIRVS
1B;

<
C7LDI:LS
=2-5861;

<
C7LDI:LS
=2-5862;

<
C7SLI:LS
=2-
5861,SLC
=0,ST=C
7ST2-
X,ACL=A1
,SDL=AIR
VS1A;

<
C7SLI:LS
=2-
5862,SLC
=0,ST=C
7ST2-
X,ACL=A1
,SDL=AIR
VS1B;

<
C7RSI:DE
ST=2-
5861,PRI
O=1,LS=
2-5861;

<
C7RSI:DE
ST=2-
5862,PRI
O=1,LS=
2-5862;

<
C7RAI:DE
ST=2-
5861;

<
C7RAI:DE
ST=2-
5862;

<
C7LAI:LS
=2-
5861,SLC
=0;

<
C7LAI:LS
=2-
5862,SLC
=0;

<
C7NPI:SP
=2-
5861,CON
;

<
C7NPI:SP
=2-
5862,CON
;

<
C7NSI:LS
=2-
5861,SSN
=11;

<
C7NSI:LS
=2-
5861,SSN
=15;

<
C7NSI:LS
=2-
5862,SSN
=11;

<
C7NSI:LS
=2-
5862,SSN
=15;

See more
details in
Model DT
for
MSC/SSF,
Reference
[2].

9.3
MSC
Exchan
ge Data

9.3.1
AIR Data
In all
MSC/VL
R's

<
EXROI:R=
AIRS&AIR
R,DETY=
UPD,FNC
=7;

<
EXDRI:R=
AIRS&
AIRR,DEV
=UPD-X;

<
BLORE:R
=AIRS;

9.3.2
Route
supervisi
on

<
DUDAC:R
=AIRS,AC
L=A2,ADL
=5;

<
SEQAC:R
=AIRS,AC
L=A3,QU
OS=60,Q
UOB=85;

9.3.3
MSC
Signallin
g System
No.7
Data

<
C7SPI:SP
=2-2300;

<
C7PNC:SP
=2-
2300,SPI
D=AIR;
<
C7LDI:LS
=2-2300;

<
C7SLI:LS
=2-
2300,SLC
=0,ST=C
7ST2-
X,ACL=A1
,SDL=AIR
;

<
C7RSI:DE
ST=2-
2300,PRI
O=1,LS=
2-2300;

<
C7RAI:DE
ST=2-
2300;

<
C7LAI:LS
=2-
2300,SLC
=0;

<
C7NPI:SP
=2-
2300,CON
;

<
C7NSI:LS
=2-
2300,SSN
=15;

See more
details in
Model DT
for
MSC/SSF,
Reference
[2].
9.4
HLR
Exchan
ge Data

9.4.1
HLR
Signallin
g System
No.7
Data

9.4.1.1
Link
towards
AIR
through
STP

<
C7SPI:SP
=2-2300;

<
C7PNC:SP
=2-
230,SPID
=AIR;

<
C7RSI:DE
ST=2-
2300,PRI
O=1,LS=
2-200;

<
C7LDI:LS
=2-2300;

9.4.1.2
Global
Title
Analysis

< C7TZI;

< C7TCI;
<
C7GCI:GT
RC=3,PSP
=2-
2300,PTE
RM,PSSN
=15;

<
C7GSI:TT
=0,NP=1,
NA=3,NS
=707272
300,GTRC
=3;

<
C7GSI:TT
=0,NP=1,
NA=4,NS
=467072
7230,GTR
C=3;

< C7TAI;

9.4.2
Number
Series
Analysis
for USSD
User
Account
Refill

The USSD
value is
an
example.

<
HGPAI:O
NSA=3,N
AI=0,NAP
I=0,USRF
=USSDSC
;

<
HGPAI:O
NSA=4,N
AI=0,NAP
I=0,USRF
=ENAP3S
C;

<
HGNSI:O
NSA=3,N
S=120,C
HAR=USS
DSC-1;

<
HGNSI:O
NSA=4,N
S=120,C
HAR=ENA
P3SC-1;

9.4.3
Voucher
Refill
and
Balance
on
demand

<
HGXAI:EN
AP=2,
EADD=4-
46707272
300;

If multiple
SDP
configurat
ion is
used a
correction
is needed
in HLR
(see
Chapter
5.3.4,
Number
Series
Analysis
for USSD
Balance
on
Demand).
Ask local
FSC for
assistance
.

In such a
case the
following
line has
to be
used:

<
HGXAI:EN
AP=56,EA
DD=3-
42444290
; !If
correction
is loaded!

10
Optim
ized
Signal
ling
for
Bonus
on
Incom
ing
Calls
(BIC)

10.1
Introdu
ction

The
purpose
of this
feature is
to give a
monetary
bonus to
specific
Charging
System
Subscribe
rs with
relation to
received
calls.

10.2
MSC/SS
F
Exchan
ge Data

This
chapter
describes
the
invocation
functional
ity of BIC.

10.2.1
Size
Alteratio
n Data

No special
Size
Alteration
events
are
needed
for this
feature.

10.2.2
Trigger
Tables in
the SSF,
CS1+

The
trigger
paramete
rs, the IN
service
invocation
model
and the
trigger
tables are
presented
here.

10.2.2.1
SK and IN
Service
Trigger

A specific
Service
Key (SK)
is used
for BIC
service.

From a
PPS point
of view,
this
service
has a
behaviour
like a
Terminati
ng PPS
call, but
by means
of
applying
a
Negative
Tariff, the
result is
an
increase
of money
in the
called
subscriber
's
account.

SKs are
related to
IN
Service
Trigger
(IST)
paramete
rs and
this
means
that each
SK
requires
at least
one IST.

Table 93

Type of
access

Bonus
Incomin
g Calls,
Logical
SDP 0

10.2.2.2
The
Triggering
and
Service
Invocatio
n Model
for BIC

The
trigger
function
of IN
services
is
implemen
ted in
form of
the
trigger
tables.
There are
10 trigger
tables
and each
of them
contains
reference
s to the
others.
The
trigger
function
is
graphicall
y
described
in Figure
28.

Figure 22
Trigger
Tables
Model for
BIC

10.2.2.3
BIC/
Table
SHEXTRA
NS - SSF
Extension
Field
Translatio
n

Existing
values
from
Chapter
4.2.4.1,
Table
SHEXTRA
NS - SSF
Extension
Field
Translatio
n are
used.

10.2.2.4
BIC /
Table
SHEXTLIS
T - SSF
Extension
Field List

Existing
values
from
Section
4.2.4.2,
Table
SHEXTLIS
T - SSF
Extension
Field List
are used.

10.2.2.5
BIC /
Table
SHTSO -
SSF
Trigger
Service
Originatio
n

Existing
values
from
Chapter
4.2.4.3,
Table
SHTSO -
SSF
Trigger
Service
Originatio
n are
used.

10.2.2.6
BIC /
Table
SHTSD -
SSF
Trigger
Service
Destinatio
n

Existing
values
from
Section
4.2.4.4,
Table
SHTSD -
SSF
Trigger
Service
Destinatio
n are
used.

10.2.2.7
Table
SHTDPS -
TDP
Service
Data

Table 94
 TDPSI T
D D

188 3

For the
meaning
of
paramete
rs see
Chapter
4.2.4.5,
Table
SHTDPS -
TDP
Service
Data.

10.2.2.8
BIC /
Table
SHINS -
SSF
Invoke
Network
Signalling

Existing
values
from
Chapter
4.2.4.6,
Table
SHINS -
SSF
Invoke
Network
Signalling
are used.

10.2.2.9
BIC /
Table
SHTDP-
SSF
Trigger
Detection
Point

Table 95
 TDPI D
D

188 1

For the
meaning
of
paramete
rs See
Section
4.2.4.7,
Table
SHTDP-
SSF
Trigger
Detection
Point.

10.2.2.10
BIC /
Table
SHTNS -
SSF
Trigger
Network
Signalling

Existing
values
from
Section
4.2.4.8,
Table
SHTNS -
SSF
Trigger
Network
Signalling
are used.

10.2.2.11
BIC /
Table
SHIST-
SSF IN
Service
Trigger
See
Section
4.2.4.9,
Table
SHIST-
SSF IN
Service
Trigger on
page 73
for
further
details.

Table 96

IST TNS

18 311
8

10.2.2.12
BIC /
Table
SHISTTOT
DP - SSF
IST to
TDP

The
Detection
Point
number
12 is
armed
and used
as a TDP
for
PrePaid
BIC calls.

Table 97

IST TDP
D

18 188
8
See
Chapter
4.2.4.10,
Table
SHISTTOT
DP - SSF
IST to
TDP for
further
informatio
n.

10.2.3
B-
number
Analysis
for BIC
Calls

Table 98

BO

27

310

When a
PrePaid
subscriber
is called,
HLR will
send the
TICK
informatio
n (TICK =
188) to
GMSC/MS
C. Then
the route
8MIN1
will be
seized
and the
analysis
will go
further
with the
BO
pointed
out in
route
8MIN1.

B=27, IN
TRIGGERI
NG, pps
terminati
ng call
SSF
====>
SCF

<
ANBSI:B=
27-188x,
ISK=IST-
188,M=3,
F=310,
CC=cc;

For more
details
see
Chapter
4.2.4.11,
B-number
Analysis
for
PrePaid
Originatin
g/
Terminati
ng Calls.

The
GMSC/MS
C should
be able to
support
the
terminati
ng IN
suppleme
ntary
services.

Paramet
ers

B "27" - B
origin is
reserved
for
Prepaid
Terminati
ng calls
(Route
MIN with
FNC=8),
"28" - B
origin
OSR
Route,
TRACO
function
(Return
from IN),
"310" - B
origin
pointed
out from
B=24,
B=27.

M
Modificati
on of B-
number,
delete
OICK/TIC
K (M=3)
or any
other
prefix.

ISK
Internal
Service
Key. IST
188 - IN
Service
Trigger
for BIC,
Logical
SDP0.

CC
Charging
Case,
used if
needed.
L Number
Length.
The
number
length
should
normally
be
indicated
as soon
as it can
be
determine
d.

F First
digit use
stated
origin.

RC
RC=15 -
IVR Call,
RC=71 -
TRACO
SSF
routing
case (IN
Call),
RC=121 -
GRI3
route.

x Any
number
(must be
opened
properly).

10.3
HLR
Exchan
ge Data

10.3.1
Subscrib
er
Categori
es
 Only
Terminati
ng
subscriber
category
is needed.

<
HGSDC:M
SISDN=m
sisdn,SUD
=tick-
188;

TICK-188
Terminati
ng
Category;
value 188
for BIC.

Note:
There is a limitation when using TICK, it can only be used by one service, for
example, Bonus on Incoming Calls or charging of Terminating Calls. In case
such a combination of features is required a correction in HLR is needed. Ask
local FSC for assistance.
11 Mobile
Number
Portability

11.1
Introduction

Mobile Number
Portability as
implemented in
PrePaid
System/Charging
System allows a
subscriber to keep
same MSISDN whe
moving the
subscription from o
operator to anothe
while at the same
keeping the possib
to separate on-net
off-net calls (Insid
the same operator
to other operator).

Mobile Number
Portability using A
Time Interrogation
(ATI) has a direct
interrogation inter
to the number
portability informa
database. A net wo
prefix pointing to t
operator serving th
called/calling party
retrieved from the
database. This
identifier can be us
in the tariff structu
to provide
differentiated real-
time charging for o
net and off-net cal
also for terminatin
charging in the SD
Mobile Number
Portability using A
an enhancement o
the Mobile Numbe
Portability feature
using SRF, which w
introduced in earlie
PPS versions.

Implementation ha
been moved from
MSC/SRF to SCP a
CCN, hence remov
the requirement to
have an Ericsson M

The new
implementation
supports CS1+, CA
Phase 2 & 3, SMS
&voice/data.

This solution is
delivered as RPC "
R9.1 MNP DATA
ACCESS" .

It includes new
software in nodes
and SCP.

Involved nodes are

MSC/VLR/SSF/FNR
SCP and SDP.

Preconditions:

The following
conditions should b
fulfilled:

 The operationa
networks have
upgraded to
CME/20/CMS40
 The basic exch
data for the
CME20/CMS40
platform and o
nodes have to
loaded.
 PPS IN 3.6.1 re
data are define
IN nodes.
 PPS is working
 The Tariff struc
the SDP has be
adapted to
accommodate
Portability, with
Network Prefix
parameter.

Add on Software

Correction N64FZ-
0233 is to be loade
the SCF, correction
N64RP-1953 and
N64RP-1955 are to
loaded in the FNR.
Contact local FSC
assistance with the
loading of these
corrections.

11.2 SCP No
Exchange Dat

11.2.1 CCITT7 N
DATA

The following anal

is needed:
<
C7GCI:GTRC=33,PS
-100,PINTER;

The Signalling Poin

(SP=2-100) is defi
to be an intermedi
primary SP.

<
C7GSI:NS=4670727
9,TT=200,NP=1,NA
GTRC=33;

Where NS is the FN
GT address.

The Translation Ty
(TT), should have
same value as the
set by FNR at FMA
block. See Section
11.3.1 Parameter
Settings. .

11.3 FNR/MS
Node Exchang
Data

11.3.1 Paramet
Settings.

The ATI-TT, stored

variable CDUMMY2
FMAPTC block, sho
be set.

The value must be

same introduced a
for MNP Data Acce
SCP node, See Sec
11.2.1 CCITT7 No
DATA, but, cannot
the same as TTINT
AXEPARAMETER.

To set the ATI-TT

following comman
are required, this w
set the ATI- TT to
< TEST SYSTEM;

< PRINT VAR FMAP

15;

< SET VAR FMAPTC

= 200;

< PRINT VAR FMAP

15;

The country code c

be checked and se
required) using the
following comman
(for example Swed
= 46):

< PRINT VAR FLNA

128(1);

< PRINT VAR FLNA

128(34);

< PRINT VAR FLNA

128(35);

< SET VAR FLNAN

128(1) = H'F46;

< SET VAR FLNAN

128(34) = H'F4;

< SET VAR FLNAN

128(35) = H'F;

< END TEST;

11.3.2 FNR Nod

Parameters

A summary of the
parameters involve
the MNP function i
Commands for the
FNR parameter set
activation have the
following format:
<
SYPAC:ACCESS=ENA
D,PSW=....; !Ask
local FSC for
password!

< DBTRI;

<
DBTSC:TAB=AXEPAR
ETNAME=setname,N
=name,VALUE=val;

< DBTRE:COM;

<
SYPAC:ACCESS=DIS
ED;

11.3.3 SAEs dat

The Size alteration

related to the FNR
function are:
11.3.4 Subscrib
data for FNR

The values assigne

the parameters are
examples.

Change of Network
Prefix of the mobil
operator in the FN

<
FGOPC:ONPREFIX=4
;

Change the defaul

route translation in
FNR:

<
FGDRC:MSISDN=467
73099;! DEFAULT
ROUTING TOWARDS
HLR!

Define a Gateway
Mobile Services
Switching Center
(GMSC) series
belonging to the
operator in the FN

< FGGSI:GMSCS=70

Define a subscribe
number translation
the FNR:

<
FGNTI:MSISDN=468
71011,NPREFIX=40
!IMPORTED!

<
FGNTI:MSISDN=467
71034,NPREFIX=20
!EXPORTED!

<
FGNTI:MSISDN=468
71010,NPREFIX=30
!OTHER!

<
FGNTI:MSISDN=467
71037,NPREFIX=40
!HOME!

Definitions of
subscriber types fo
MNP:

 Imported: - A
subscriber who
MSISDN series
assigned to an
operator and h
ported to the c
operator, ( own
NPREFIX)
 Exported: - A
subscriber has
NPREFIX not b
to the home ne
and the MSISD
national destin
code (NDC) eq
the home NDC
 Other: - A subs
has a NPREFIX
equal to the ho
operator and th
MSISDN has an
not equal to th
NDC.
 Home: - A sub
whose MSISDN
number series
assigned to the
(original) opera
and whose NPR
also belongs to
home operator

11.3.5 CCITT N
SCCP signalling D
The following data
to be defined, in o
to define the SCCP
signalling data to r
messages between
MSC, SCP and FNR
The values given
below are example
and should be ada
to your network.

<
C7GCI:GTRC=27,PS
WNSP,PSSN=253; !
gmsc->SSN FNR-SC

<
C7GCI:GTRC=28,PS
WNSP,PSSN=222;!
gmsc->SSN FNR-TC

The CCN Signalling

Point (SP=2-5555)
defined to be an
intermediate prima
SP.

<
C7GCI:GTRC=96,PS
-5555,PINTER; !C

Global Title definit

of CCN in FNR.

<
C7GSI:TT=0,NP=1,
4,NS=46707275557
RC=96;

Standard Global Ti
routing for FNR
functions.

<
C7GSI:TT=0,NP=1,
4,NS=4670727103,
C=27;

! HOME - INCOMIN
SMS FROM GMSC
FNR, NP&FA !
<
C7GSI:TT=0,NP=1,
4,NS=468882710,
GTRC=27;

! HOME - INCOMIN
SMS FROM GMSC
FNR, NP&FA !

<
C7GSI:TT=0,NP=7,
4,NS=4688827,GTR
; ! LU !

<
C7GSI:TT=0,NP=1,
4,NS=#134000,GTR
;

! HOME - NON-CAL
RELATED MESSAG
FROM OTHER
NETWORK !

<
C7GSI:TT=128,NP=
A=4, NS=46888271
GTRC=27;

! NP-FROM FNR TO
HLR - GMSC TO SR

<
C7GSI:TT=200,NP=
A=4,NS=46,GTRC=2

<
C7GSI:TT=247,NP=
A=4, NS=46,
GTRC=28;

!NP-FROM SRF TO
MAPF!

<
C7GSI:TT=249,NP=
A=4, NS=46707271
GTRC=2;

! NP-FROM FNR TO
HLR - SRF TO HLR
<
C7GSI:TT=249,NP=
A=4, NS=46888271
GTRC=2;

! NP-FROM FNR TO
HLR - SRF TO HLR

12 Glossa
13
Reference
List