DESCRIPTION

13/190 46-FAD 104 08 Uen C

Traffic Case Description - Mobile

Originating Calls
Abstract
The purpose of this document is to describe the traffic case "Mobile Originating calls"
from data transcript point of view.
The document does not explain on BLOCK/SIGNAL level. This information can be
found in the FUNCTION DESCRIPTION for each function block.
All referenced DT subfiles can be found in the DT Info Model.
Contents
1

Revision Information

2
2.1
2.2
2.3
2.4
2.5

Description
Abbreviations
Concerned Nodes
General
Call from MS to PSTN
Emergency Call from MS

1 Revision Information
Revision Impacts
A
Document based on earlier CME20
DT Info Models.
B
Emergency call from MS added.
Document rewritten.
C
Updated document to SS R7

2 Description

Prepared Date
ERATHHE 96-0913
ERAMIST 97-0526
ETOTRRE 98-0921

2.1 Abbreviations
AOC
Advice Of Charge
BC
Bearer Capability
CAPL
Channel Allocation Priority Level
CC
Charging Case
CI
Cell Identity
EA
Emergency Area
EC
Echo Canceller
IDD
International Dialled Digit (e.g. double zero)
MS
Mobile Station
PLMN
Public Land Mobile Network
PSTN
Public Switched Telephone Network
TSC
Telecommunication Service Code
TMR
Transmission Medium Requirement

2.2 Concerned Nodes

MSC/VLR

2.3 General
When a mobile originating call is initiated, a chain of analysis functions are started. This
document describes the basic DT involved in the traffic cases "Call from MS to PSTN"
and " Emergency call from MS".
In the traffic case "Call from MS to MS" the mobile originating part of the call is handled
similarly to whats described in this document. For the terminating part, see traffic case
description "Mobile Terminating calls" doc. no. 14/190 46-FAD 104 08 Uen in the DT
Info model.

2.4 Call from MS to PSTN

In the description below an example of a mobile originating call to PSTN is given,
following the logical sequence for DT analysis. The mobile subscriber Mr Indusson
wants to make a normal speech call from his Mobile Station. He dials the number "08
123456" and presses the "call set-up" button.

2.4.1 DT Analysis Flow Chart

Figure 1

2.4.2

Telecommunication Service Analysis

When a mobile subscriber initiates a call, a call set up message is sent from the MS to the
BSC which delivers it to the MSC. In the message a GSM Bearer Capability (GSM BC)
is sent. If the call is an ordinary speech call, the BC indicates "speech". The parameter is

converted into a Basic Service Code (BASC). The BASC is the input to the
Telecommunication Service analysis, which determines, what type of calls the MSC/VLR
supports (see subfile 16000).
Example: The call is a normal speech call and will result in TSC=1.
Example 1 MML command definitions
MGTEI:TEC=THY, TSC=1;

The output here is Telecommunication Service Code (TSC), which serves as a pointer to
the command MGTCI. This command specifies the network requirements i.e. Wanted
Type of Signalling, Tone Protection etc..
Example 2 MML command definitions
MGTCI:TSC=1,
WSIG=NOIS,
TBI=NO,
.....

Telecommunication Service Code

Wanted Type of Signalling
Tone Protection Information

If the telecommunication service is supported in the exchange, the VLR checks if the
subscriber has the proper subscriber service. If the subscription is missing, the call set up
will be cancelled.
Example: Mr Indusson has the subscription "Teleservice Telephony" (TS11), so the call
is allowed.

2.4.3 IMSI Number Analysis

Information about the MS is fetched from the IMSI number analysis (subfile 76000). This
information includes parameters like OBA, CBA and NATMS. The parameter OBA is
the input to the B-number analysis. It specifies the origin for start of pre B-number
analysis.
Example: Mr Indussons IMSI number is included in the IMSI number series below.
Example 3 MML command definitions
MGISI:IMSI=240 01 75,
............
ANRES=OBA-30,
CBA-46,
NATMS,
.....;

Origin for B-number analysis

Call Barring Access (BOIEXH)
National Mobile Subscriber

2.4.4 B-Number Analysis

2.4.4.1 General
B-number analysis is carried out in two stages. The first stage is referred to as preanalysis of the B-number and then the analysis of the B-number takes place.
2.4.4.2 Pre B-Number Analysis
The pre-analysis acts as a filter and then as a selector. Due to the pre-analysis, it is
possible to reduce the number of origins used in the B-number analysis tables. The preanalysis uses the extra information contained in the set up message originating from the
MS, the B-Number Type and the Number Plan (BNT and NAPI). This makes it possible
to distinguish between a normal MS originated call, International call and a Forwarded-to
number in the pre B-number analysis (see subfile 15700).
Example 4 MML command definitions
PNBSI:BO=30,
BNT=2,
OBA=30;

Pre B-number origin (from MGISI)

B-number type (BNT=2 unknown format)
Origin for B-number analysis

PNBSI:BO=30,
BNT=1,
OBA=32;

Pre B-number origin (from MGISI)

B-number type (BNT=1 International format)
Origin for B-number analysis

Example: Mr Indusson dialled "08 123456" which is a number in "Unknown format".

The number will therefore be analysed in OBA=30.
All MS originated calls are in "Unknown format" except if " International format" is
specially chosen on the MS.
All Forwarded-to-number should be in "International format" (see subfile 78000).
2.4.4.3 B-Number Analysis
From the pre B-number analysis the Origin for B-number analysis (OBA) is derived.
The B-number analysis makes an analysis of the dialled number. The table delivers a
large amount of analysis results which are used in other analysis tables, e.g. Route and
Charging analysis.
Example 5 MML command definitions
ANBSI:B=30-08,
L=7-12,
M=1,
BNT=4,
CC=4,
D=4-1,
RC=1;

Analysed number
Number length
Modification of the number (removes first digit)
New B-number type
Charging Case
Destination Code
Routing Case

Example: Mr Indusson dialled 08 123456, which means that the number will be modified
(0 removed => 8 123456), BNT set to 4 and RC=1 is fetched.

2.4.5 Access Barring Analysis

2.4.5.1 General
Access barring analysis is the method of determining whether a MS is permitted to make
a call. This function is invoked by the use of the D parameter from the analysis of the Bnumber and points to a table for access barring.
2.4.5.2 National Calls
The D-parameter (Destination code) received from the B-number analysis is connected to
a TDCL (Trunk Discrimination Class, see subfile 15500).
Example 6 MML command definitions
ANDSI:D=4-1, TDCL=1;

The TDCL value is compared to the Calling Barring Access (CBA) value. If they are
equal then the call will fail and if they are not then the call can proceed. The CBA value
is a translation of the subscriber data for barring (BAOC, BOIC, OBA, OBI etc.) fetched
from block MTV (see parameter list for the block MTV).
Example: Mr Indusson has no barring services active, so the call is permitted.
2.4.5.3 International Calls
The concept for barring of international calls are the same as described above except for
the barring service "Barring of all outgoing international calls except those directed to the
home PLMN" (BOIEXH). The BOIEXH service uses the CBA value defined in the IMSI
number analysis. This value is determined by the network operator, values 13 to 255 are
available for use.
Let's say that a German subscriber with SS BOIEXH active roams in our MSC and wants
to make an international call home to Germany.
Example 7 MML command definitions
MGISI:IMSI=262 02
=>
CBA-49
ANBSI:B=32-49
=>
D=6-49
ANDSI:D=6-49,
TDCL=1&2&44&46;

The CBA value from the IMSI analysis is compared with the TDCL value pointed out
(via the Access Barring table) in the B-number analysis. The values are not equal, so the
call can proceed.

If a U.K subscriber with SS BOIEXH active roams in our MSC and wants to make an
international call to Germany, the call will be barred due to that the fetched CBA-44 and
the TDCL value pointed out in the B-number analysis are equal.
Example 8 MML command definitions
MGISI:IMSI=234 15
=>
CBA-44
ANBSI:B=32-49
=>
D=6-49
ANDSI:D=6-49
TDCL=1&2&44&46;

2.4.6 Routing Case Analysis

Another output from the B-number analysis table is the Routing Case (RC) This
parameter is analysed in the Routing Case analysis table to determine the outgoing route
for the call to proceed. The outgoing route must already be defined (command EXROI).
Different routing alternatives can be chosen and branching can be done on several input
parameters, such as Transmission Medium Requirement (TMR) (see subfile 15400).
Example 9 MML command definitions
ANRPI:RC=1;
ANRSI:BR=TMR-0,ESR=1,R=PSTNO... => Speech call, ECs required
ANRSI:BR=TMR-1&&-4,R=PSTNO..... => Data call, ECs not required
ANRPE;

The TMR (input from the call set up message) is used as a branching parameter to control
the Echo Cancellers (EC) function.
Example: A route towards PSTN is pointed out in the RC analysis.

2.4.7 Route Definition

The definition of a route is a group of devices each having the same qualities. By
qualities we mean: destination, device type, signalling system and any other
characteristics.
Example 10 MML command definitions
EXROI:R=PSTNO,DETY=UPD,FNC=3,SP=2-400,SI=ISUP4;

Example: A route towards PSTN has been pointed out in the Routing Case analysis.

2.4.8 A-Number Analysis

2.4.8.1 General

A-number analysis is carried out in two stages. The first stage is referred to as preanalysis of the A-number and then the analysis of the A-number takes place.
2.4.8.2 Pre A-Number Analysis
The principle for pre A-number analysis is the same as for pre B-number analysis, see
paragraph 2.4.4.2.
Example 11 MML command definitions
PNASI:NAPI=1,
ANT=1,
OAA=0;

A-Number Type
Origin for A-number analysis

Example: Mr Indussons A-number is analysed in international format.

2.4.8.3 A-Number Analysis
The A-number analysis can be used to route different A-number series to different
destination. It can also be used to restrict an A-number series from calling a particular
destination or specify differentiated charging for national and international subscribers.
The A-number is the calling subscribers MSISDN. The MSISDN is sent to the
MSC/VLR during the location updating procedure. (see subfile 15800).
Example 12 MML command definitions
ANASI:A=0-46,
ACO=0;

A-Number
A-Number Charging Origin

Example: Swedish A-numbers (inter alia Mr Indusson) gets ACO-0.

2.4.9 Charging Analysis

2.4.9.1 Initial Charging Analysis
The input to the Initial Charging analysis (Traffic Activity Dependent Charging analysis)
is the Charging Case (CC) derived from the B-number analysis.
The branching conditions in the analysis, can be used to differentiate the charging
depending on the type of call (see subfile 15100).
Example 13 MML command definitions
CHIPI:CC=4;
CHISI:BC=TSC-0&&-4&-19&&-255...
CHISI:BC=TSC-7&&-18...
CHISI:BC=TSC-5&-6...

=> NCC=1 (speech)

=> NCC=5 (data)
=> NCC=6 (fax)

CHIPE;

Example: Our subscriber initiated a normal speech call which results in a new Charging
Case (NCC=1). The TSC parameter is derived from the Telecommunication Service
Analysis.
2.4.9.2 Charging Analysis
The input here is the New Charging Case (NCC) derived from the Initial Charging
analysis or (if the CC not were specified in the Initial Charging analysis) the original
Charging Case derived from the B-number analysis.
Example 14 MML command definitions
CHAPI:CC=1,
CHABI:BC=CO-0&&-30&ACO-0;
CHASI:.....,TC=1;
CHABI:BC=CO-31;
CHASI:.....,NP;
CHAPE;

The Tariff Class (TC) derived points towards a Tariff (T), which is necessary to define if
Advice of Charge (AOC) are to be used in the node.
Example 15 MML command definitions
CHCSI:TC=1 => T=1

For more information about charging see document " Charging" doc. no. 8/190 46-FAD
104 08 Uen in the DT Info model.

2.5 Emergency Call from MS

Mobile Subscriber emergency calls are handled as highest priority calls. They get priority
when requesting processor capacity and at outgoing trunk seizure.
The emergency call set up is similar to the basic traffic case " Call from MS" with the
exception that some functions are invoked/ignored depending on the setting of certain
emergency call related exchange parameters.
An emergency call is initiated when the emergency code 112 is dialled on a Mobile
Station and a request to establish an emergency call is generated. When the message is
received in the MSC/VLR, a check for the IMSI number is performed.
If no IMSI (TMSI) is received in the set up message, the exchange property
EMCNOIMSI controls whether the call is allowed to proceed or not.

Example 16 MML command definitions

MGEPC:PROP=EMCNOIMSI-1; ! Emergency call set up without an IMSI !

For a Mobile Station which is not registered (Location Updating has not been performed)
in the MSC/VLR, the call may be allowed to proceed anyway depending on the exchange
parameter EMCNOLU.
Example 17 MML command definitions
MGEPC:PROP=EMCNOLU-1;

For a Mobile Station which is registered, procedures for security related functions, such
as authentication and ciphering, are invoked. If authentication fails, the call proceeds
anyway but without ciphering.
Upon completion of the procedures for security related functions, the procedure for
equipment identity control is started. Two exchange properties related to this function are
checked. IMEICONTROLEMR controls whether IMEI check is to be performed and
IMEIROUTGRYEMR controls if grey listed subscriber are to be re-routed to an
announcement. If the call is to be re-routed an End of Selection (EOS=2742) is generated,
which is used to route the call to an announcement machine.
Example 18 MML command definitions
MGEPC:PROP=IMEICONTROLEMR-1; ! IMEI control at emergency calls
MGEPC:PROP=IMEIROUTGRYEMR-0; ! Re-routing at grey listed IMEI

!
!

ANESI:ES=2742, F=99, M=0-100; ! Announcement, grey listed IMEI !

After reception of a request from the Mobile Station to set up the call, telecommunication
service analysis is performed for the emergency call.
Example 19 MML command definitions
MGTEI:TEC=EMERG, TSC=99, CRT=FR-FR, PSCVL=FRV1&FRV2;
MGTCI:TSC= 99, WSIG=NOIS, TBP= NO, TPI=YES, NOTE="EMERG";

End of Selection analysis is initiated with an emergency call specific End of Selection
code, EOS=2290 for " Emergency call with SIM card" and EOS=2577 for "Emergency
call without SIM card". The EOS code leads to modification of the (non-existing) Bnumber in the EOS analysis.
Example 20 MML command definitions
ANESI:ES=2290, F=30,M=0-90000; ! Emergency call, with SIM card
!
ANESI:ES=2577, F=30,M=0-90000; ! Emergency call, without SIM card !

Different emergency centres can be reached depending on the Emergency Area (EA)
category defined by command MGCEC. The Emergency Area category is specified on a
per cell basis.
Example 21 MML command definitions
MGCEC:CELL=KISTA1A, CO= 4, EA=1, RO=1;
MGCEC:CELL=KISTA2A, CO= 4, EA=2, RO=1;
MGCEC:CELL=KISTA3A, CO= 4, EA=3, RO=1;
ANESI:ES=2290, F=30,M=0-90000; ! Emergency call, with SIM card
!
ANESI:ES=2577, F=30,M=0-90000; ! Emergency call, without SIM card !

B-number analysis is restarted which leads to a routing case RC.

Example 22 MML command definitions
ANBSI:B=30-900, L=5, BNT=2, RC=90; ! National Emergency Number !

Routing analysis is performed and an EOS code is derived. The branching is specified on
the different Emergency Areas defined.
Example 23 MML command definitions
ANRPI:RC=90;
ANRSI:BR=EA-1, P01=1, ES=2601;
ANRSI:BR=EA-2, P02=1, ES=2602;
ANRSI:BR=EA-3, P03=1, ES=2603;
ANRPE;

EOS-analysis is performed and BO (B-number origin) and B-number are returned.

Example 24 MML command definitions
ANESI:ES=2601, F=30, M=0-9112; ! B-number to Emergency Area 1 !
ANESI:ES=2602, F=30, M=0-9113; ! B-number to Emergency Area 2 !
ANESI:ES=2603, F=30, M=0-9114; ! B-number to Emergency Area 3 !

The routing of the emergency call to the emergency centre is done with this B-number.
This way it is possible to have an EOS code for each Emergency Area. The intention is to
use those EOS codes reserved for TCS internal use. However, if these are not enough, it
is advisable to use EOS codes from 9999 and downwards.
If A-number is requested, it is returned to TCS, if MSIDSN is valid, otherwise not
available indication is returned.
Two exchange properties APPCI and APPSEPCI defines if the originating Cell Identity
(CI) must be appended, with or without separator, at the end of the emergency centre
number. This allows the forwarding of the Cell Identity to the network.

Example 25 MML command definitions

MGEPC:PROP=APPCI-0;
! Appending of Cell Identity (CI) !
MGEPC:PROP=APPSEPCI-0; ! Appending of CI with separator !

Another exchange property SSEM2 is checked to see whether network initiated

Supplementary Service operations are allowed in parallel to an emergency call. However
invocation of barring Supplementary Services as well as operator determined barring are
ignored.
Example 26 MML command definitions
MGEPC:PROP=SSEM2-0;

Supplementary service operations

After seizure of an outgoing line, the Mobile Station is informed that the set up of the call
is processing.
At this point an A-interface line for speech transmission towards the BSS is seized. After
seizure of the A-interface line, the BSS is requested to assign a traffic channel to the air
interface. If the feature Channel Allocation Priority Level (CAPL) is active, exchange
property CAPLTCHEMER is checked for the Channel Allocation Priority Level to be
used for the emergency call.
Example 27 MML command definitions
MGEPC:PROP=CAPLTCHSCH-0; ! Channel Allocation Priority Level active !
MGEPC:PROP=CAPLTCHEMER-0; ! CAPL used for Emergency calls
!

After receiving an indication from the BSS that the traffic channel assignment has been
completed, the call is set up to an emergency centre.
The Mobile Station is informed when the emergency centre is free (alerting). Upon
indication about B-answer, the Mobile Station is informed. When the Mobile Station has
acknowledged to the indication about B-answer, the emergency call has been established.
If the Mobile Subscriber dials the national emergency call number instead of using the
emergency code (if not the same number), the call will be set up as a normal telephony
call. The call is accepted if the destination pointed out by the national emergency number
is not barred by the access barring analysis.

References
1/1553 1/APT 210 25/1 Uen A
Traffic handling
2/155 16-ANT 292 01/2 Uen A

Call from MS, Preparation

4/155 16-ANT 292 01/2 Uen B
Call from MS, Establishment
19/155 17 ANT 292 01/1 Uen A
Call from Mobile Subscriber in MSC/VLR
87/155 17 ANT 219 07/3 Uen A
Emergency call from Mobile Subscriber in MSC/VLR
9/190 82 CNT 214 9954 PA10
ANRSI