MSC Database Administration Siemens

MSC Database Administration

Contents
1 Cells and Location Areas 3
1.1 Definition of Cells and Location Areas 4
1.2 Using Cells and Location Areas 6
2 Regional Roaming Subscription 25
2.1 Functionality 26
2.2 MML Commands 28
3 Cell-Oriented Routing 31
3.1 Functionality 32
3.2 MML Commands 34
4 Subscriber-Related Routing 39
4.1 Functionality 40
4.2 Administration 42
5 Monitoring of Forwarded and Transferred Calls 45
5.1 Function 46
5.2 Administration 48
5.3 Example 50
6 Mobile Station Routing Numbers 51
6.1 Inter-MSC Handover 52
6.2 Mobile Terminating Call 54
6.3 Administration of Mobile Station Routing Numbers 56
7 Exercises 59
8 Solutions 67

MN2513EU09S1_0001 SSNC
1
© 2001 Siemens AG
 Siemens MSC Database Administration

2 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
MSC Database Administration Siemens

1 Cells and Location Areas

MN2513EU09S1_0001 SSNC
3
© 2001 Siemens AG
 Siemens MSC Database Administration

1.1 Definition of Cells and Location Areas

l Cell
A cell is the smallest addressable radio range from the perspective of the MSC.
A cell describes the geographical area covered by the radio resources of a base
station. A cell is identified from the MSC with the help of the location area code
(LACOD) and the cell identification (CI). A cell is addressed from the MSC via the
signaling point code (CCS7 address) of the BSC. The location cell of a subscriber
is not used for call setup in the MSC, but it is known in the MSC and is used for
traffic measurement. A cell is internationally unambiguously addressed via the cell
global identity. This consists of the components MCC/MNC/LACOD/CI.
l Location area
As described already, the location of the subscriber in the MSC/VLR is not carried
out on a call basis. Only the location area of the subscriber is stored in the VLR –
i.e., the subscriber is reachable owing to the location area. A location area can
contain several cells. One or several location areas are allocated unambiguously
to an MSC. The address logic of the location area and thus of all the cells from the
MSC contained within ensues via the signaling point code of the BSC.
A location area is internationally unambiguously identifiable via the location area
identity. This consists of the following components:
MCC/MNC/LACOD.

4 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
MSC Database Administration Siemens

SIEMENS SIEMENS

MSC/VLR

Subscriber Data
LAI

BSS BSS
addressed by addressed by
Signaling Point Signaling Point
Code Code

Cell Cell
Cell Cell Cell Cell
Cell Cell Cell
Cell Cell
Location Area Cell Location Area

Cell: Location Area

CGI = MCC/MNC/LACOD/CI
Location Area:
LAI = MCC/MNC/LACOD

Fig. 1 Cells and location areas

MN2513EU09S1_0001 SSNC
5
© 2001 Siemens AG
 Siemens MSC Database Administration

1.2 Using Cells and Location Areas

1.2.1 Internal Cells and Location Areas

1.2.1.1 Function
The location of a mobile subscriber is defined in the MSC specific only to the location
area. In other words, regardless of the cell in a location area in which the subscriber
is currently to be found, only the location area of the subscriber is stored in the VLR.
For this reason, the cells that constitute a location area and the base station system
via which the subscriber can be reached must be reported to the system.

Location update:
When a subscriber changes location, the mobile station compares the new LAI
(location area identity) transmitted by the BSS with the LAI of the previous location
update that is stored on the SIM card. If the two LAIs do not match, the mobile station
has changed location and is now positioned in a different location area of the same or
another MSC. The mobile station sends the old LAI and the received LAI to the MSC.
The MSC then analyzes the old LAI. If the location has changed within the MSC area,
the MSC can detect the change by means of the database because the old LAI can
be found as an internal cell/location area in the MSC in this case. The new LAI is
then entered in the subscriber data of the VLR in order to make the mobile subscriber
accessible for mobile terminating calls, for example.

6 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
MSC Database Administration Siemens

SIEMENS SIEMENS

VLR/MSC
Cell/Lacode
Cell/Lacode
Data
Data
old
oldLAI?
LAI?
VLR
VLRMSUB
MSUB
Data
Data
new
newLAI
LAI old LAI
new LAI

new
LAI

SIM Card SIM Card

new LAI
=
old LAI old LAI old LAI?

Fig. 2 Internal cell data for location update

MN2513EU09S1_0001 SSNC
7
© 2001 Siemens AG
 Siemens MSC Database Administration

Mobile terminating calls

After a location update, the location area identity (LAI) is stored in the subscriber’s
VLR data. If a ‘provide roaming number’ is then received from the HLR during a
mobile terminating call, a mobile station roaming number is output, linked with the
VLR subscriber data and returned to the HLR.
Next, a circuit connection (e.g. ISUP) is set up to the visited MSC/VLR of the called
party by the visited MSC/VLR of the calling party. The subscriber can be easily
identified since the called party number received (mobile station roaming number) is
linked with the VLR subscriber data. The LAI and TMSI are stored in the VLR
subscriber data.
The CCS7 signaling address or addresses of the assigned base station systems are
assigned to the location areas in the semipermanent location area / cell data. A
paging signal is sent with the TMSI in the broadcast channel to all assigned base
station systems. If the mobile station is in the corresponding BSC area, this
information is returned as a paging response. A traffic channel is then switched to the
appropriate base station system in reply.
The LAI is therefore used for detecting the location area of the called subscriber and
thus for detecting the corresponding base station system(s).

8 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
MSC Database Administration Siemens

SIEMENS SIEMENS Cell/Lacod

Cell/Lacod
Data
Data
ISUP: LAI
MSRN LAI
BSC
BSCSPC
SPC
Netind
Netind
VLR
VLRMSUB
MSUB
Data
Data
Paging Response
LAI
LAI
TMSI
TMSI Paging
(TMSI)

Broadcast
TMSI Broadcast TMSI

SIM Card

Broadcast
TMSI
=
stored TMSI?

Fig. 3 Application of cells/location areas for mobile terminating calls

MN2513EU09S1_0001 SSNC
9
© 2001 Siemens AG
 Siemens MSC Database Administration

Internal MSC handover

In the course of a handover, the base station system suggests possible cells to the
MSC for the handover. The MSC can use the cells assigned to it to check whether
they are internal cells with which it can perform an internal MSC handover.

10 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
MSC Database Administration Siemens

SIEMENS SIEMENS

Cell/Lacode
Cell/Lacode
data
data
Intra-MSC suggested
suggestedcell?
cell?
Handover

Handover required
(List of possible cells)

Handover
SIM Card SIM Card

Fig. 4 Intra-MSC handover dependent on internal cell

MN2513EU09S1_0001 SSNC
11
© 2001 Siemens AG
 Siemens MSC Database Administration

1.2.1.2 MML Command

Cells assigned to an MSC are created with CR INTCELL. This MML command
assigns a cell ID to an LACOD each time. The command can be entered multiply with
the same LACOD but with different cell IDs.
Another important assignment is the combination of the cell ID base station and
SPC/NETIND (CCS7 signaling point code).
The parameter ‘location mark number’ must also be entered. This parameter is
treated separately at a later stage.
The parameter LOCNO (0...999999999999999) enables all cells in a network to be
uniquely numbered and identified. The parameter can be used in the mobile call
record, for example, in order to clearly identify the origin, or can be transferred to the
IN (service control point) in order to perform origin-dependent routing, for example.
The LOCNO is just an operator specific value.
Since IN services are available also for roaming subscribers (using a service acc. to
the CAMEL standard) a unique location information about the cell of a call may also
be entered. The geographical area description (GAD) comprises latitude, longitude
and cell size, expressed in hexadecimal values.
The parameter ORIG2 allows distance-related charging because, on the one hand, it
can be included in the mobile call records and, on the other hand, evaluated in the
zoning converter.

12 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
MSC Database Administration Siemens

Creation and Display of Location Areas, Cells and

Location Mark Numbers
CR INTCELL: LACOD= <location area code>,
CI= <cell identification,
BSCSPC= <BSC signalling point code>,
NETIND= <net indicator>,
LMN= <location mark number>
RC=<BSC or RNC>
[,GAD= <geogr. coordinates>]
[,LOCNO=<location number>]
[,ORIG2=<originating mark for zoning>],.....;

DISP INTCELL: LACOD= <location area code>[,CI= <cell identification]

or
BSCSPC= <BSC signalling point code>,
NETIND= <net indicator>,....;

DISP LMN: LMN= <location mark number>;

BSCSPC NETIND LACOD CI Result

X just LACODs

<lacod> CI
BSCSPC
NETIND
LMN

<bscspc> <netind> LACOD

CI
LMN

<lacod> <ci> BSCSPC

NETIND
LMN
cell depend.
routing data

Fig. 5 Cell, location area and location mark number administration

MN2513EU09S1_0001 SSNC
13
© 2001 Siemens AG
 Siemens MSC Database Administration

1.2.1.3 Location Mark Numbers

A location mark number can be allocated to a cell. A location mark number is a cell-
dependent full directory number which is applied cell-dependently as dialing
information for a GSM emergency call.

14 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
MSC Database Administration Siemens

S I EM E NS S I E ME N S

MSC/VLR

PSTN
PSTN
BSS

Emergency Emergency
Center 1 Center 2

Emergency
Emergency
Button
Button
LMN= e.g.E8902CC110C9172
LMN= e.g.E8901CC110C9172

Fig. 6 Location mark number

MN2513EU09S1_0001 SSNC
15
© 2001 Siemens AG
 Siemens MSC Database Administration

1.2.2 External Location Areas

1.2.2.1 Function

Location change from a known VLR/MSC

If an MSUB changes the location from an VLR/MSC that is known in the new
VLR/MSC, the IMSI can be requested from the old VLR. This dispenses with the
need to transmit the IMSI via the air interface – this is undesirable because it would
be transferred without encryption.
In addition to the LACODs of neighboring MSCs, the LACODs of MSCs considered to
be the most important national traffic nodes (airports, major train stations, etc.)
should be known in all national MSCs/VLRs. Even better would be to report the
LACODs of all national MSCs/VLRs in all national MSCs/VLRs.

16 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
MSC Database Administration Siemens

External
ExternalLacode
Lacode
Data
Data
SIEMENS SIEMENS SIEMENS SIEMENS

Old VLR/MSC old

oldLAI?
LAI?
=> VLRISD
=> VLRISD
VLR
VLRMSUB
MSUB
Data IMSI
Data New VLR/MSC

IMSI
IMSI

IMSI
old LAI
new LAI

new
LAI

SIM Card SIM Card

new LAI
=
old LAI old LAI old LAI?

Fig. 7 Location area data for location update

MN2513EU09S1_0001 SSNC
17
© 2001 Siemens AG
 Siemens MSC Database Administration

Inter-MSC handover
A minimum of all location areas of neighboring MSCs must be created as external
location areas for handovers to the areas to be completed successfully.
The BSS sends the MSC a list of suggested cells for a handover. The MSC first
compares the first cell in the list with the internal cell database so as to initiate an
internal MSC handover if necessary. If the cell is not found there, a search for the cell
is made in the external location area database. The external database contains the
external LACODs and the associated MSCID. If the cell is found there, the MSCID is
converted to a CCS7 signaling address and the inter-MSC handover is initiated.

18 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
MSC Database Administration Siemens

SIEMENS SIEMENS

Cell/Lacode
Inter-MSC Cell/Lacode
External data
ExternalLacode
SIEMENS SIEMENS

handover Lacode data

data
data
suggested cell?
suggested cell?
suggested
suggestedcell?
cell?
=>MSCID
=>MSCID

Handover request
(List of possible cells)

Handover
SIM Card SIM Card

Fig. 8 Location area data for inter-MSC handover

MN2513EU09S1_0001 SSNC
19
© 2001 Siemens AG
 Siemens MSC Database Administration

1.2.2.2 MML Commands

The command CR EXTLAC reports external LACODs in an MSC/VLR. A LACOD is
linked with an MSCID for each command call. The MSCID is used for finding the
foreign MSC for handover later. A VLRISDN may also be assigned as an optional
parameter. The VLRISDN is used, for example, for addressing the VLR for location
updates. If no VLRISDN is entered, the MSCID is used instead.
The commands CAN EXTLAC and DISP EXTLAC are used to respectively cancel
and display external LACODs.
MOD EXTLAC can modify either a LACOD, MSCID or VLRISDN.

20 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
MSC Database Administration Siemens

External LACOD Administration

CR EXTLAC: LACOD= ,MSCID= [,VLRISD= ];

CAN EXTLAC: LACOD= ;

DISP EXTLAC: MSCID= ;

MOD EXTLAC: LACOD= ,NLACOD= ;

MOD EXTLAC: LACOD= <,NMSCID= ,NVLRISD= >;

Fig. 9 External LAC administration

MN2513EU09S1_0001 SSNC
21
© 2001 Siemens AG
 Siemens MSC Database Administration

1.2.2.3 Structured LACODs

A great deal of administration is required to create the LACODs of all MSCs/VLRs
belonging to a PLMN in all MSCs/VLRs of this PLMN. Structured LACODs provide a
solution to this problem.
In accordance with GSM, a LACOD has 16 bits. If a structured LACOD is used, the
16 bits are distributed project-specifically to bits per MSC (DISP MPRDDAT
MSCLACOD) and bits per LACOD belonging to the corresponding MSC. If the
LACODs of a different MSC/VLR are then announced in an MSC/VLR using
CR EXTLAC, only the MSC-specific part of the 16 bits has to be defined. The
remaining bits can assume any value at all.
Example: The number of bits for the LACOD must be set to 8 in the mobile project
data – i.e., in this case, 8 bits are assigned to the MSC-specific part and the
supplement to make up the 16 bits represents the LACOD for the corresponding
MSC.
If the MSC-specific part has the binary value 1, the following LACOD range is
obtained for the MSC:

MSC-specific part Specific part of the Decimal LACOD value

LACODs of the MSC
00000001 00000000 256
00000001 00000001 257
00000001 ................
00000001 11111111 511

Since the decimal value range (e.g., 256..511) is permanently assigned to the
corresponding MSC, the MML command ‘CR EXTLAC’ need only create the LACOD
‘256’ (i.e., only the start of the range) and assign it to an MSC. In other words, the
following LACODs would be assigned to the different MSCs.
For example:
MSC1: 0...255 (CR EXTLAC:LACOD=0,..),
MSC2: 256...511 (CR EXTLAC:LACOD=256,..),
MSC3:512...767 (CR EXTLAC:LACOD=511,..),
MSCn: 65280...65535 (CREXTLAC:LACOD=65280,..).

22 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
MSC Database Administration Siemens

Example structured LACOD:

Mobile Project Data:
LENGTH OF MSC EXTERNAL LACOD (MSCLACOD): 8

8 bits MSC-specific 8 bits for the LACOD

(MSCLACOD): 8 of the MSC

MSC-specific LACOD-specific LACOD CR EXTLAC:LACOD=

range decimal
00000000 00000000 0 0
00000000 00000001 1
00000000 00000010 2
..... ....... .......
00000000 11111111 255
00000001 00000000 256 256
00000001 00000001 257
00000001 00000010 258
....... .......... ........
00000001 11111111 511
................ ................ ............... .....................

Fig. 10 Structured LACOD

MN2513EU09S1_0001 SSNC
23
© 2001 Siemens AG
 Siemens MSC Database Administration

24 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
MSC Database Administration Siemens

2 Regional Roaming Subscription

MN2513EU09S1_0001 SSNC
25
© 2001 Siemens AG
 Siemens MSC Database Administration

2.1 Functionality
Regional zones can be assigned to a mobile subscriber for each PLMN whose
services he is entitled to use (e.g. wireless loop subscriber). The zones limit the
possibility to certain location areas or cells. The subscriber is assigned zone codes
used for identifying these permitted roaming zones. The zones themselves are
defined in the VLR. During a location update the zone codes of zones permitted for
the location PLMN are stored in the VLR together with other mobile subscriber data.
It can be decided in the VLR whether the mobile subscriber may use the services of
the PLMN in his present location area by comparing the mobile subscriber zone
codes with the identifiers of the cells or location areas.
l Regional roaming administration based on LACODs:
Here the LACODs that make up a roaming zone are specified in the VLR. If one of
these zones is assigned in the HLR to a subscriber, he/she is only permitted to use
the service (location update) in those LACODs.
l Regional roaming administration based on cells, roaming restriction based on
LACODs:
In this case the cell IDs constituting a roaming zone are specified in the VLR. If
one of these zones is assigned in the HLR to a subscriber, he/she is only
permitted to use the service (location update) in the location area to which the
corresponding cell or cells are assigned.
l Regional roaming administration based on cells, roaming restriction based on
cells:
In this case the cell IDs constituting a roaming zone are specified in the VLR. If
one of these zones is assigned in the HLR to a subscriber, he/she is only
permitted to use location updates in the location area to which the corresponding
cell or cells are assigned. A check is performed during call setup (MOC/MTC,
mobile terminating SMS, mobile origin SMS, etc.) to determine whether the
subscriber is located in any of the permitted cells.

26 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
MSC Database Administration Siemens

SIEMENS SIEMENS

HLR Regional
Regional
Roaming
Roaming
Roaming
Zone
Data
Data
HLR
HLRMSUB
MSUB SIEMENS SIEMENS

Data Local
LocalArea
Area
Data VLR/MSC ororCell
Cellids
ids
Roaming
RoamingZone
Zone

Roaming
Roaming Roaming Zone
allowed Administration
allowed based on Cell. Subscription in
call
callnot
not the whole location area
allowed
allowed

Roaming
Roaming
allowed allowed
allowed allowed
allowedtoo
too
allowed
call
call
allowed
allowed allowed
allowed allowed
allowed
Roaming Zone
Roaming Zone Administration
Administration based on Location
based on Cell. Cell Area. Subscription in
checked during Call setup the whole location area

Fig. 11 Roaming zones

MN2513EU09S1_0001 SSNC
27
© 2001 Siemens AG
 Siemens MSC Database Administration

2.2 MML Commands

l For a feature to function correctly it must be released (sales feature) and activated
with MODMSERVOPT.
A distinction must be made between the features REGRO, RSCELLBA and
RSCELLID.
FEAT=REGRO basic feature: The regional subscription is administered on the
basis of the location area.
FEAT=REGRO&RSCELLBA supplementary feature: The regional subscription is
administered using the cell ID but is effective for location areas.
FEAT=REGRO&RSCELLID supplementary feature: Administered like RSCELLBA
but checks during call setup if the subscriber is in the appropriate cell.
l The command CR RSZONE uniquely assigns one or more location areas
(REGRO) or one or more cell IDs (REGRO&RSCELLBA or REGRO&RSCELLID)
to a zone number (roaming zone) in the MSC/VLR.
l The MML command ‘ENTR RSSERV’ assigns the zones defined in the MSC/VLR
to a mobile subscriber as permitted roaming areas.
Rule: If the zone 0 is assigned to the subscriber in addition to other zones for
RSCELLBA, the subscriber is allowed to use the service in the corresponding
VLRs in the known zones (LACODs) and in all other VLRs.

28 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
MSC Database Administration Siemens

Regional Subscription Administration

Feature in the DISP MSERVOPT

REGRO GSM Basic Feature: Administration and check based

on LACOD

REGRO& Supplementary Feature: Administration based on

RSCELLBA CELL, check based on LACOD

REGRO& Supplementary Feature: Administration based on

RSCELLID CELL, call setup check based on Cell

In the VLR

CR RSZONE: ZCODE=<roaming zone number>, RSAREA= <cell id

or lacode> ;

In the HLR

ENTR RSSERV: MSIN= ,

PLMN= <CC>-[<NDC>],
ZCODE=<roaming zone number>,

Fig. 12 Administration of regional subscription

MN2513EU09S1_0001 SSNC
29
© 2001 Siemens AG
 Siemens MSC Database Administration

30 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
MSC Database Administration Siemens

3 Cell-Oriented Routing

MN2513EU09S1_0001 SSNC
31
© 2001 Siemens AG
 Siemens MSC Database Administration

3.1 Functionality
Alongside the cell-dependent management of real emergency calls, there is the
possibility to cell-dependently convert certain service abbreviated numbers into full
directory numbers. This could, for instance, be applied when the operator-specific
service numbers, breakdown service, etc. are to be accessed cell-dependently. This
means, for example, that – depending on the location on the freeway that a car
breaks down– the call is connected to different breakdown service points although
the same abbreviated number is used. This takes place through the evaluation of the
cell in which the subscriber is currently located and the conversion of the dialed
abbreviated numbers into various full directory numbers.

32 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
MSC Database Administration Siemens

S IE ME NS S IE ME N S

MSC/VLR

PSTN
PSTN

BSS

Service Service
Center 1 Center 2
Short Service
Short Service
Number
Number

Long Number = e.g. 082217389

Long Number = e.g. 08917389

Fig. 13 Cell-dependent routing

MN2513EU09S1_0001 SSNC
33
© 2001 Siemens AG
 Siemens MSC Database Administration

3.2 MML Commands

l The setup of the database for cell-dependent routing consists of several steps:
a) The service provider name must be announced with the command
CR PROVNAM (create provider name). In addition, whether the call to this
provider should be handled as an emergency call can be specified in this
command.
b) The full directory numbers per origin cell are specified with the command CR
PROVNO (create provider number) for the provider setup.
c) The general code via which the provider should be able to be reached is set
up and linked with the provider name with the command CR CPT (create
code point).
l The following display commands are reachable for the display: DISP PROVNAM,
DISP PROVNO, DISP CPT.

34 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
MSC Database Administration Siemens

Creation and Display of Cell dependent Routing

CR PROVNAM: PROVNAM=<provider name>,
TYPE={ORD|EM},.....;

CR PROVNO: PROVNAM=<provider name>,

PROVNO=<digit combination cell dependent>,
CI=<cell id>,
LACOD=<location area code>;

CR CPT: CODE=<cell independent short code>,

TRATYP=MOBPROV,
PROVNAM=<provider name>,....;

DISP PROVNAM: PROVNAM=<provider name>;

DISP PROVNO: PROVNO=<digit combination cell dependent>;

DISP CPT: CODE=<cell independent short code>,

{TRATYP=MOBPROV | PROVNAM=<provider name>};

Fig. 14 Cell-dependent routing administration

MN2513EU09S1_0001 SSNC
35
© 2001 Siemens AG
 Siemens MSC Database Administration

3.2.1 Example
In the next example, the provider number for a second emergency number is
displayed in addition to the official GSM number.
The subscriber dials 110. The incoming normal call is analyzed in the digit translator
and routed to the provider EMCAL110. Cell-dependent full emergency numbers are
created for this provider. They begin with E and are followed by the PSTN local area
code. The remaining digits are determined by national legal requirements. With the
long directory number, the call is again routed to the digit translator and a destination
in the PSTN is addressed from there.

36 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
MSC Database Administration Siemens

LAC=05051

LAC=05021 LAC=05721
PSTN

SIEMENS SIEMENS

CI=10191 CI=10192 CI=3590 CI=10200 CI=2381

CI=10191 CI=10192 CI=3590 CI=10200 CI=2381
E05021 E05021 E05051 E05021 E05721
E05021 E05021 E05051 E05021 E05721

<CRPROVNAM:PROVNAM=EMCAL110,TYPE=EM;

<CRPROVNO:PROVNAM=EMCAL110,LACOD=511,CI=10192,PROVNO=E05021CC110C9172!
:PROVNAM=EMCAL110,LACOD=511,CI=10191,PROVNO=E05021CC110C9172!
Cell :PROVNAM=EMCAL110,LACOD=511,CI=3590,PROVNO=E05051CC110C9172!
:PROVNAM=EMCAL110,LACOD=511,CI=10200,PROVNO=E05021CC110C9172!
Id :PROVNAM=EMCAL110,LACOD=511,CI=2381,PROVNO=E05721CC110C9172!
.....
110 <CRDEST:DEST=HNVR541VE1E ;
<CRCPT:CODE=110,ORIG1=20-1,TRATYP=MOBPROV, PROVNAM=EMCAL110!
.....
<CRCPT:CODE=E,DEST=HNVR541VE1E ,ORIG1=20-1!
.....

Fig. 15 Example: provider number used for emergency calls

MN2513EU09S1_0001 SSNC
37
© 2001 Siemens AG
 Siemens MSC Database Administration

38 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
MSC Database Administration Siemens

4 Subscriber-Related Routing

MN2513EU09S1_0001 SSNC
39
© 2001 Siemens AG
 Siemens MSC Database Administration

4.1 Functionality
The ”subscriber-related routing” feature enables mobile originating calls (MOC) to be
routed to specific destination numbers defined in the mobile subscriber's HLR. To
request a connection of this kind, the mobile subscriber generally dials an
abbreviated directory number. The MSC detects from the associated code point that
the requested connection belongs to a service provider and to a specific service. It
therefore builds a ”service number” with the format <CC> <NDC> m <Y> <SN> from
the MSISDN (contained in the VLR database) of the mobile subscriber. CC, NDC and
SN form the MSISDN of the calling subscriber; "m" is a project-specific hexadecimal
digit. The service itself is not specified exactly in the MSC, but identified by a service
code Y (Y=0,1,2,...,9). If the mobile subscriber is set up with multinumbering – i.e.,
the subscriber has more than one SN, the MSC uses the SN of the base MSISDN.
The service number is used to carry out global title translation and then an
interrogation of the HLR of the calling subscriber. In each case, the full service
directory number is sent to the HLR. The HLR determines the service address
created for this service and, in some cases, for this mobile subscriber, and this
address is then sent to the MSC in response to the interrogation (see OMN: SSS-
SU). The service address is defined in the HLR using one of the following methods:
l a fixed entered directory number, which usually corresponds to the ISDN
numbering plan (E.164)
l a directory number which consists of a digit sequence xxx (usually three digits)
and the MSISDN of the calling mobile subscriber, and has the following structure:
<CC><NDC> <xxx> <SN>; in this case, the service center is identified by at least
xxx, although parts of the SN may also be necessary for routing
l a mobile station roaming number which is requested by the HLR of the service
center; in this case, the connection is similar to a ”pseudo MTC” to a service
center.
The service address received as interrogation response in the HLR is used to
execute routing to the service center in the MSC.

40 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
MSC Database Administration Siemens

Service SIEMENS SIEMENS

short
MSC/VLR
number Provider
Providerdata:
data: PBX

Service specific
Service specific Service
indication
indication„Y“
„Y“ Center

b) MSRN

Interrogation a) CC/NDC/<service Center>

Send Routing Info: b) MSRN from service Center
<CC><NDC>m<Y><SN> c) CC/NDC/<service Center>/<SN>

b) MSRN Request
SIEMENS SIEMENS

HLR Subscriber
Subscriberrelated
relatedService
Servicedata
data
for Service Indication
for Service Indication „Y“:„Y“:
• •a)a) Fixed
Fixedaddress:
address:
Service
ServiceCenter
CenterNumber
Number
as
asInterrogation
InterrogationResponse
Response
• •b)b) Service
ServiceCenter
CenterAddress:
Address:
global
global title to requestan
title to request anMSRN
MSRN
from a Service Center
from a Service Center
• •c)c) Subscriber
Subscriberdependent
dependent
Address:
Address:
Service
ServiceCenter
CenterDirectory
DirectoryNumber
Number
inclusive
inclusiveSN SNasasInterrogation
InterrogationResult
Result

Fig. 16 Subscriber-related routing

MN2513EU09S1_0001 SSNC
41
© 2001 Siemens AG
 Siemens MSC Database Administration

4.2 Administration
In the MSC/VLR, the abbreviated directory number must be created using a code
point and must also refer to a provider (PROVNAM). The provider is assigned a
SERVICE INDICATOR (SERVIND) in the CR PROVNO command. This index has
one character and corresponds to the service indicator “Y” described earlier.
The service indicator is inserted in the MAP message to the HLR with a leading,
project-specific hexadecimal digit "m" between the NDC and the SN of the calling
party. The digit "m" to be used, must be entered in the project data during installation.
It makes sense to choose a digit that does not interfere with the network's MSISDN
numbering plan.
If the HLR does not find the calling party number in the HLR subscriber data, it
branches to the subscriber-related service data that were specified with CR
SUBRSERV and assigned to a subscriber with ENTR OPRSERV.

42 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
MSC Database Administration Siemens

Service SIEMENS SIEMENS

short
code:233
ENTRMPRDDAT:SERVIND=5...;
CR CPT: CODE=233,
TRATYP=MOBPROV,
PROVNAM=SERV233;
CR PROVNAM:
PROVNAM=SERV233,
SERVIND=3;
CR CPT:CODE=0049 178 53 89,
TRATYP=MOBINTER,...;
Interrogation
Send Routing Info for:
0049178538942361 FIXED 0049 178 99 233
SCADR MSRN from service Center
SUBDEP 0049 178 99 233 89 42361

SIEMENS SIEMENS CR SUBRSERV:

OPRSERV=SUBRELRO,
SERVICE=233, IND=3,
ADDRTYPE= FIXED ,
SCADR
SUBDEP
ADDR= 49178 99 233;
ENTR OPRSERV:
OPRSERV=SUBRELRO,
MSIN= 89 2134321,
SERV=233;

Fig. 17 Example: Administration

Subscriber Related Routing Administration

DISP MPRDDAT: SERVIND= <1...F>;
In the VLR/MSC
CR PROVNAM: PROVNAM= ,SERVIND= ;
In the HLR

CR SUBRSERV: OPRSERV= ,SERV= ,IND= ,ADDRTYPE= ,ADDR= ;

ENTR OPRSERV: MSIN= ,OPRSERV= ,SERV=

Fig. 18 Subscriber-related routing: MML commands

MN2513EU09S1_0001 SSNC
43
© 2001 Siemens AG
 Siemens MSC Database Administration

44 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
MSC Database Administration Siemens

5 Monitoring of Forwarded and

Transferred Calls

MN2513EU09S1_0001 SSNC
45
© 2001 Siemens AG
 Siemens MSC Database Administration

5.1 Function
The so-called fraud protection package has been introduced for CF and CT in order
to prevent mobile subscribers from committing fraud by switching calls with call
forwarding or call transfer and then failing to pay the ensuing charges.
l Automatic monitoring function:
This function uses thresholds to limit the maximum number of simultaneous call
forwarding or call transfer calls per party, or issues a warning when a specified
number of calls has been exceeded.
l Manual monitoring:
CF and CT calls can be indicated according to a specified call duration or number
of simultaneous calls.
l Forced release:
CT and CF calls that were conspicuous during manual monitoring can be manually
released.

46 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
MSC Database Administration Siemens

Japan
SIEMENS SIEMENS

1 USA

SIEMENS SIEMENS SIEMENS SIEMENS

2
MSC

SIEMENS SIEMENS

MSUB with
CT or CF

n
Russia

Fig. 19 Reason for fraud protection

Fraud package

• Threshholds for CT and CF call limitation

• Threshholds for CT and CF call displays
• Manual monitoring of suspect calls by
input of call duration or number of calls
• Release of suspect calls

Fig. 20 Fraud package

MN2513EU09S1_0001 SSNC
47
© 2001 Siemens AG
 Siemens MSC Database Administration

5.2 Administration
Threshold values for the maximum number of simultaneously existing CF or CT calls
are entered with the MML command ‘ACT SMSUBDET’ (suspect MSUB detection).
Moreover, thresholds for the maximum number of calls can also be administered. A
warning is output each time this number is exceeded. Note that CT calls always have
an incoming and an outgoing side and must therefore be considered as two calls in
each case.
The same MML command is also used to reactivate the feature after deactivation.
The command DISP SMSUB displays all current CT or CF calls for the MSUB. The
command is often used if the threshold value for a display for an MSUB has been
exceeded.
DISP SMCALL displays MSUBs that have exceeded either a specified number of CT
or CF calls, or a duration specified for individual CT or CF calls.
Calls that appear suspicious to a carrier can be released with REL SMCALL.

48 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
MSC Database Administration Siemens

Fraud Protection Administration

DISP MSERVOPT: FEAT=FRAUDPR;

ACT SMSUBDET : [INFOTHR=] [,RELTHR=] ;

DACT SMSUBDET ;

DISP SMSUBDET ;

DISP SMSUB : <IMSI= ,CALL= ,CDUR=> ;

DISP SMCALL : IMSI= ;

REL SMCALL : IMSI= ,CALLIND= ;

Fig. 21 Fraud protection for CF/CT

MN2513EU09S1_0001 SSNC
49
© 2001 Siemens AG
 Siemens MSC Database Administration

5.3 Example
Display to check if feature is generally activ

DISP MSERVOPT:FEAT=FRAUDPR;

DISPMSERVOPT:FEAT=FRAUDPR; EXEC'D

SERVICE/ CONNECTION RADIO CHANNEL ALTERNATIVE

FEATURE STATUS ELEMENT REQUIREMENT SCI OCI SERVICE
----------+--------+------------+--------------+-----+-----+-----------
FRAUDPR ACT

END JOB 8948

Activate Suspect MSUB detection

ACT SMSUBDET:INFOTHR=2,RELTHR=4;

ACTSMSUBDET:INFOTHR=2,RELTHR=4; EXEC'D

SUSPECT MOBILE SUBSCRIBER DETECTION

STATUS: ACTIVE INFORMATION THRESHOLD: 2 RELEASE THRESHOLD: 4

END JOB 9589

3 CF or 2 CT calls for MSUB 262085300000000 have happened

D900#/MSC00000/SR6012345678-NNN/410 96-11-12 12:34:07

9628 2996/08702

SUSPECT MOBILE SUBSCRIBER DETECTION

REASON: MAXIMUM NUMBER OF CALLS EXCEEDED

IMSI : 262085300000000

Display MSUB 262085300000000

DISP SMCALL:IMSI=262085300000000;

DISPSMCALL:IMSI=262085300000000; EXEC'D

SUSPECT MOBILE CALLS

IMSI = 262085300000000

CALL-DURATION

CALLIND FTN/CDPA TYPE HOUR MINUTE MSISDN

--------+---------------+-----+------+-------+---------------
1 0893304 CT 0 3 491785110000
2 0893303 CT 0 3 491785110000
3 0893302 CT 0 0 491785110000
4 0893301 CT 0 0 491785110000

END JOB 9629

Realease of the first „Call Transfer“-connection (Callind=1 or 2):

REL SMCALL:IMSI=262085300000000,CALLIND=2
DANGEROUS COMMAND RELSMCALL READY TO EXECUTE <
;

RELSMCALL:IMSI=262085300000000,CALLIND=2; EXEC'D

Fig. 22 Example: Fraud protection

50 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
MSC Database Administration Siemens

6 Mobile Station Routing Numbers

MN2513EU09S1_0001 SSNC
51
© 2001 Siemens AG
 Siemens MSC Database Administration

6.1 Inter-MSC Handover

1. The mobile station and BTS (base transceiver station) measure, for example, the
transmission quality and reception level. The mobile station also measures the
reception of neighboring cells and transfers the values to the BSS.
2. If required, the BSC generates a list of suggested cells from the measurement
results with up to 16 cells, and sends the list with a ‘handover required’ to the
corresponding MSC.
3. The MSC checks the first cell in the list to determine whether it belongs to the
MSC’s own area (CR INTCELL:CI=, LACOD=...;). If not, it checks if the cell
belongs to an announced MSC (CR EXTLAC:LACOD=..., MSCID=...;).
4. The MSCID found in CR EXTLAC is then translated to a signaling address and a
handover request is sent to the new MSC. The new cell is reported to the MSC.
5. The new MSC sends a handover request to the BSS associated with the cell
(CR INTCELL).
6. The BSS seizes a traffic channel and provides a so-called handover reference
number. The MSC seizes a trunk to the BSC.
7. The new MSC provides temporary routing information for the old MSC (handover
number).
8. The old MSC switches a conference (in the group switch) on receiving the
handover number.
9. The trunk LTG reports ‘conference successful’.
10. A trunk call (e.g., ISUP) is set up to the new MSC.
11. A prepare handover is sent with the handover reference number to the old
BSC/mobile station.
12. The mobile station carries out a handover to the new cell. This is done using the
handover reference number transmitted by the new BSC.
13. The new BSC reports ‘handover performed’.
14. The message is transferred to the old MSC. It releases the conference.
15. The old MSC sends a traffic channel release message to the old BSS to release
the old connection.

52 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
MSC Database Administration Siemens

2 1
SIEMENS SIEMENS

11

Trunk LTG 15

8
SCCP

14

7 14

12
10 4

SIEMENS SIEMENS

Handover
Handover SCCP
Numbers
Numbers

1788980
1788980000
000
..
.. 5
..
6
1788980
1788980999
999 13

Fig. 23 Inter-MSC handover

MN2513EU09S1_0001 SSNC
53
© 2001 Siemens AG
 Siemens MSC Database Administration

6.2 Mobile Terminating Call

1. An own mobile subscriber number has been received. Interrogation is started in
the VLR/MSC of the calling party.
2. The dialed MSISDN is translated to a signaling address and a ‘send routing
information’ is sent to the HLR of the called party.
3. The HLR searches in the HLR subscriber data for the VLR/MSC of the called
party on the basis of the IMSI. The VLRISD stored there is converted to the
signaling address of the VLR/MSC. A ‘provide roaming number’ message is sent
to the VLR/MSC of the called party.
4. The VLR/MSC of the called party takes a temporary directory number from the
pool of mobile station roaming numbers (MSRN) and in standard cases (specified
in the mobile project data) transfers it in international format to the HLR.
5. The HLR transfers the MSRN to the MSC of the calling party.
6. The MSC of the calling party analyzes the MSRN and sets up a trunk call (e.g.,
ISUP) to the MSC/VLR of the called party. The subscriber is identified by means
of the MSRN output there.
7. The TMSI and LACOD stored in the VLR subscriber data are used to send a
paging message to the appropriate BSC (CR INTCELL:LACOD= ...,
BSCSPC=....,...;). The TMSI is transmitted in the broadcast channel.
8. If the subscriber is found in the area of the corresponding BSC, it responds with a
paging response.

54 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
MSC Database Administration Siemens

SIEMENS SIEMENS

1 VLR/MSC
5

SCCP

SIEMENS SIEMENS

2
HLR

SCCP

6 4

SIEMENS SIEMENS
3
SCCP
Mobile
MobileStation
Station
Roaming
RoamingNumbers
Numbers
7
1788980
1788980000
000
..
..
VLR/MSC 8
..
1788980
1788980999
999

Fig. 24 Mobile terminating call

MN2513EU09S1_0001 SSNC
55
© 2001 Siemens AG
 Siemens MSC Database Administration

6.3 Administration of Mobile Station Routing

Numbers
The handover numbers and mobile station roaming numbers discussed earlier can
be combined to form so-called mobile station routing numbers. In other words, each
MSC has a pool of mobile station routing numbers that can, however, be distributed
between mobile station roaming numbers and handover depending on the project.
The mobile station routing numbers are administered in the national format but are
sent in the international format via MAP. This can be determined in the project data
(with the DISP MPRDDAT parameters ‘MSRNFORM’ and ‘HONFORM’).
The mobile station routing numbers are entered with a directory number root – e.g.,
1788980, and the range of directory numbers to be covered is specified (e.g.,
1788980000...1788980999) with the following MML command:
CR MSRNB: MSRNP=1788980, MSRNR=3;
The parameter MSRNK indicates whether the directory numbers are to be used for
handover or roaming or for both.
If the LACOD parameter is specified, the routing numbers are output in accordance
with the location (LACOD). This can be used for mobile terminating calls in the
intelligent network, for example.

56 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
MSC Database Administration Siemens

Mobile Station Routing Number Administration

CR MSRNB : MSRNP = ,MSRNR= [,LACOD=] [,MSRNK=];

CAN MSRNB : MSRNP= [,LACOD=] ;

DISP MSRNB ;

MOD MSRNB : MSRNP= ,LACOD= ,NLACOD= [,NMSRNR=]

[,NMSRNK=] ;

MOD MSRNB : MSRNP= [,LACOD=] <,NMSRNR= ,NMSRNK=> ;

MOD MSRNB : MSRNP= ,NMSRNP= [,LACOD=] [,NMSRNR=]

[,NMSRNK=] ;

MSRNK={BOTH|HON|MSRN}
MSRNP Mobile Station Routing Number Prefix
MSRNR Mobile Station Routing Number Range

Fig. 25 Mobile station routing number administration

MN2513EU09S1_0001 SSNC
57
© 2001 Siemens AG
 Siemens MSC Database Administration

58 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
MSC Database Administration Siemens

7 Exercises

MN2513EU09S1_0001 SSNC
59
© 2001 Siemens AG
 Siemens MSC Database Administration

60 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
MSC Database Administration Siemens

Exercise 1
Title: MSC data
Objective: The participant can detect errors in the MSC database
Prerequisite: None
Task
An internal mobile call from the MSUB _________________________________
to the MSUB ______________________________________
was unsuccessful. Check the MSC database using what you have learned, and
attempt to find the error.
Do not correct the error.

Query

What suggestions would you make to clear the error?

MN2513EU09S1_0001 SSNC
61
© 2001 Siemens AG
 Siemens MSC Database Administration

62 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
MSC Database Administration Siemens

Exercise 2
Title: Mobile Station Routing Numbers
Objective: The participant can create mobile station routing numbers
Prerequisite: Groups are used. Group 1 uses the existing HLRID+1, group 2
the HLRID+2, group 3 the HLRID+3, etc.

For example, HLRID=70, group 1:71, group 2:72, group 3:73,

etc.
Task
n Display the mobile station routing numbers.
n Create the mobile station routing numbers as follows:

<NDC><HLRID>8.....

1000 mobile station roaming numbers should be available.

400 handover numbers should be available

Query

What MML commands did you use?

MN2513EU09S1_0001 SSNC
63
© 2001 Siemens AG
 Siemens MSC Database Administration

64 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
MSC Database Administration Siemens

Exercise 3
Title: Provider data
Objective: The participant can create mobile provider numbers
Prerequisite: Groups are used. The individual groups use different input
values. They are distinguished by the number <team>.
Task
n Create the connection to a mobile provider as follows:

Short number: ____________________ <team>

Provider name: ADAC<team>

Provider number/cell id: ______________ <team>/ ________________

Provider number/cell id: ______________ <team>/ ________________

BSC ORIG1:________________________

This number is not an emergency directory number.

All directory numbers are routed to the destination ADAC:

Query

What MML commands did you use?

MN2513EU09S1_0001 SSNC
65
© 2001 Siemens AG
 Siemens MSC Database Administration

66 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
MSC Database Administration Siemens

8 Solutions

MN2513EU09S1_0001 SSNC
67
© 2001 Siemens AG
 Siemens MSC Database Administration

68 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
MSC Database Administration Siemens

Solution 1
Title: MSC data
Objective: The participant can detect errors in the MSC database
Prerequisite: None

Task
An internal mobile call from the MSUB _________________________________
to the MSUB ______________________________________
was unsuccessful. Check the MSC database using what you have learned, and
attempt to find the error.
Do not correct the error.

Query

What suggestions would you make to clear the error?

MN2513EU09S1_0001 SSNC
69
© 2001 Siemens AG
 Siemens MSC Database Administration

70 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
MSC Database Administration Siemens

Solution 2
Title: Mobile Station Routing Numbers
Objective: The participant can create mobile station routing numbers
Prerequisite: Groups are used. Group 1 uses the existing HLRID+1, group 2
the HLRID+2, group 3 the HLRID+3, etc.

For example, HLRID=70, group 1:71, group 2:72, group 3:73,

etc.
Task
n Display the mobile station routing numbers.
n Create the mobile station routing numbers as follows:

<NDC><HLRID>8.....

1000 mobile station roaming numbers should be available.

400 handover numbers should be available

Query

What MML commands did you use?

MSC6/SR70/D2MMPK1V1702-F05/103 99-05-25 09:02:15

0907 CA SIEMENS0 2878/00007

CRMSRNB:MSRNP=1725480,MSRNR=3,MSRNK=MSRN; EXEC'D

END JOB 0907

MSC6/SR70/D2MMPK1V1702-F05/103 99-05-25 09:02:19

0908 CA SIEMENS0 2878/00007

CRMSRNB:MSRNP=1725481,MSRNR=2,MSRNK=HON; EXEC'D

END JOB 0908

MSC6/SR70/D2MMPK1V1702-F05/103 99-05-25 09:02:23

0911 CA SIEMENS0 2878/00007

MN2513EU09S1_0001 SSNC
71
© 2001 Siemens AG
 Siemens MSC Database Administration

CRMSRNB:MSRNP=1725482,MSRNR=2,MSRNK=HON; EXEC'D

END JOB 0911

MSC6/SR70/D2MMPK1V1702-F05/103 99-05-25 09:02:27

0915 CA SIEMENS0 2878/00007

CRMSRNB:MSRNP=1725483,MSRNR=2,MSRNK=HON; EXEC'D

END JOB 0915

MSC6/SR70/D2MMPK1V1702-F05/103 99-05-25 09:02:32

0920 CA SIEMENS0 2878/00007

CRMSRNB:MSRNP=1725484,MSRNR=2,MSRNK=HON; EXEC'D

END JOB 0920

72 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
MSC Database Administration Siemens

Solution 3
Title: Provider data
Objective: The participant can create mobile provider numbers
Prerequisite: Groups are used. The individual groups use different input
values. They are distinguished by the number <team>.
Task
n Create the connection to a mobile provider as follows:

Short number: ____________________ <team>

Provider name: ADAC<team>

Provider number/cell id: ______________ <team>/ ________________

Provider number/cell id: ______________ <team>/ ________________

BSC ORIG1: ________________________

This number is not an emergency directory number.

All directory numbers are routed to the destination ADAC:

Query

What MML commands did you use?

MSC6/SR70/D2MMPK1V1702-F05/103 99-05-25 09:10:47

1134 CFE NELSON22 2999/00007

CRPROVNAM:PROVNAM=ADAC1; EXEC'D

END JOB 1134

MSC6/SR70/D2MMPK1V1702-F05/103 99-05-25 09:14:34

1190 CFE NELSON22 2999/00007

CRPROVNO:PROVNAM=ADAC1,LACOD=1,CI=2,PROVNO=01726000001; EXEC'D

END JOB 1190

MN2513EU09S1_0001 SSNC
73
© 2001 Siemens AG
 Siemens MSC Database Administration

MSC6/SR70/D2MMPK1V1702-F05/103 99-05-25 09:14:38

1194 CFE NELSON22 2999/00007

CRPROVNO:PROVNAM=ADAC1,LACOD=1,CI=1,PROVNO=01726000002; EXEC'D

END JOB 1194

MSC6/SR70/D2MMPK1V1702-F05/103 99-05-25 13:02:17

5341 CFE NELSON22 2878/00007

CRCPT:CODE=110,ORIG1=20,TRATYP=MOBPROV,PROVNAM=ADAC1; EXEC'D

END JOB 5341

74 SSNC MN2513EU09S1_0001
© 2001 Siemens AG