Open

1 (20)
Prepared (also subject responsible if other) No.

edbrqas MU/NWE-05:
Approved Checked Date Rev Reference

11/10/2006 PA1

TFO/TrFO, Activation in CN5.0 network

Contents

0 GENERAL DOCUMENTATION ISSUES.................................................2

0.1 Revision Information..................................................................2
0.2 References................................................................................2
1 INTRODUCTION.....................................................................................3
1.1 Concepts...................................................................................3
1.2 Prerequisites.............................................................................3
2 ACTIVITIES TO MSC in POOl ACTIVATION..........................................5
2.1 RNC- Preparation Phase...........................................................5
2.2 BSC – Preparation Phase..........................................................5
2.3 MSC – Preparation Phase.........................................................9
2.4 BSC- Activation Phase............................................................18
3 Capacity...............................................................................................19
4 Alarms..................................................................................................19
4.1 RNC........................................................................................19
4.2 BSC.........................................................................................19
4.3 MSC........................................................................................19
5 Counters..............................................................................................19
5.1 BSC.........................................................................................19
5.2 RNC........................................................................................20
5.3 MSC........................................................................................20
6 Impact on MGW...................................................................................20
7 Appendices..........................................................................................20
 Open
2 (20)
Prepared (also subject responsible if other) No.

edbrqas MU/NWE-05:
Approved Checked Date Rev Reference

11/10/2006 PA1

0 GENERAL DOCUMENTATION ISSUES

0.1 Revision Information

Rev. Author Date Reason for Revision

PA1 Raquel Santos 10-20-2006 New document

0.2 References

Ref. Document Title Document Number

[1] BSC- User Description, MSC in 231/1553-HSC

Pool 103 12/9 Uen B
[2] MSC in Pool in MSC 7/1553-APR 101
49/2 Uen A
[3] MSC in pool (User Description) 19/1553-HSD 101
73/2 Uen Rev A
[4] MSC in Pool for GSM 10/190 46-FAD 109
1001 Uen A
 Open
3 (20)
Prepared (also subject responsible if other) No.

edbrqas MU/NWE-05:
Approved Checked Date Rev Reference

11/10/2006 PA1

1 INTRODUCTION

This document describes the steps necessary to activate MSC In POOl in the CN5.0 network.
It’s important to keep in mind that MSC is not a feature that you just activate it and
deactivated it; MSC in Pool is a special configuration of the network that enable it to share
the traffic and improve the performance .

1.1 Concepts

MSC Pool is a group of MSC (called MSC Pool Members), sharing in parallel, the traffic
generated by one and only one MSC Pool Area. All MSC Pool Members in the same MSC Pool
are logically connected to all RNC(s) and BSC(s) in the MSC Pool Area

MSC Pool

MSC Pool Members

MSC-1 MSC-2 MSC-3

Iu, A interfaces

RNC-1 RNC-2 RNC-3

BSC-1 BSC-2 BSC-3

LA1 LA2 LAY LAZ

MSC Pool Area

1.2 Prerequisites

1.2.1 Software

1 OSS-RC is updated to support MSC Pool. OSS-RC 5.x

2 MSC(s) are configured with MSS 4.2 software/functions. MSC Pool for
GSM is already available in GSM R11
 Open
4 (20)
Prepared (also subject responsible if other) No.

edbrqas MU/NWE-05:
Approved Checked Date Rev Reference

11/10/2006 PA1

3 RNC(s) are configured with P5.

4 BSC(s) are configured with the software version supporting “3GPP

load redistribution”. This step is needed if there is an MSC Pool with
BSC(s) that is expanded with WCDMA RAN. BSS 06B. MSC in Pool is
supported for BYB 501 HW and onwards

5 Assumes that the UE(s) are complying with existing standards related
to TMSI reallocation and handling non-broadcasted location areas.

1.2.2 Tools

WinFiol to Access MSC-S

MOSHELL to access RNC
Protocol Analyzer
 Open
5 (20)
Prepared (also subject responsible if other) No.

edbrqas MU/NWE-05:
Approved Checked Date Rev Reference

11/10/2006 PA1

2 ACTIVITIES TO MSC in POOl ACTIVATION

2.1 RNC- Preparation Phase

Not implemented yet.

2.2 BSC – Preparation Phase

Introduction
The following preparation should be done in BSS in order to add an MSC into an MSC pool.
The preparation is done per BSC node and shall be done when the MSC is in mode INACTIVE
This section of the procedure needs to be performed for all BSC(s) involved in the Pool.

Procedure

Action
Configure the A-interface links to the MSC

Result

Comment

Action
Define the MSC including signaling point (SP)

Set per MSC with command RRMBI

RRNLP;
RLTDP:MSC=ALL;

Result

Comment
 Open
6 (20)
Prepared (also subject responsible if other) No.

edbrqas MU/NWE-05:
Approved Checked Date Rev Reference

11/10/2006 PA1

Action
Define Core Network Identity (CNID) if Network Operation Mode I is to be used (Gs interface
is used between SGSN and MSC)

Set per MSC with command RRMBI

RRNLP;
RLTDP:MSC=ALL;

Result

Comment
Value Range: 0-4095 Ref [1]

Action
Define one or more NRI values for the new MSC node. The parameter is used to identify
which MSC (G) that handles the mobile user. Each mobile user receives a TMSI including NRI
at first registration. One or several NRI values can be defined per MSC

Set per MSC with command RRNRI

RRNLP;
RLTDP:MSC=ALL;

Result

Comment
Value Range: 0-1023 Ref [1]

Action
Define the relative capacity of the MSC (CAP).

RLTDC:MSC=<MSC>,CAP=100;
RLTDP:MSC=ALL;

Result

Comment
 Open
7 (20)
Prepared (also subject responsible if other) No.

edbrqas MU/NWE-05:
Approved Checked Date Rev Reference

11/10/2006 PA1

Value Range 0 – 255 Ref [1]

Action
The PART parameter is used at MSC Reselection and defines the percentage of the MS(s)
located in the radio coverage area of the BSC and that are registered in the specified MSC
node and that shall be moved to other MSC(s) at the next registration activity

RLTDC: MSC=<MSC>,PART=<PART>;
RLTDP:MSC=ALL;

Result

Comment
Value Range: 1 -100 Ref [1]

Action
The RAND parameter is used at MSC Reselection to ensure that the MS(s) that are moved to
another MSC do not have a certain TMSI pattern

RLTDC: MSC=<MSC>,RAND=<RAND>;
RLTDP:MSC=ALL;

Result

Comment
Value Range: 1 -255 Ref [1]

Action
The MSCNRILENGTH parameter defines the length of the NRI value within the TMSI. The
parameter is given as number of bits.

Set per BSC with command RRNLC.

RLTDP:MSC=ALL;

Result

Comment
Value Range: 0-10 bits Ref [1]
 Open
8 (20)
Prepared (also subject responsible if other) No.

edbrqas MU/NWE-05:
Approved Checked Date Rev Reference

11/10/2006 PA1

Action
Redefine neighbouring cells

RLNRP:CELL=ALL,CELLR=ALL;

Result

Comment
 Open
9 (20)
Prepared (also subject responsible if other) No.

edbrqas MU/NWE-05:
Approved Checked Date Rev Reference

11/10/2006 PA1

2.3 MSC – Preparation Phase

Introduction

The MSC level pool radio network configuration data needs to be distributed to all MSC(s)
within the pool.
In order to have an active MSC Pool feature, an MSC Pool Member must be assigned at least
one NRI value with a length different from zero. All NRI values must have the same length. If
the NRI length is zero, the MSC does not assign any NRI values to TMSI and the MSC Pool
feature is not operational (not an MSC Pool Member).
The MSC configuration should be done with BSC MODE Parameter INACTIVE.

Procedure

Action
Define NRI length and own RNI values on every MSC that will belong to the pool.

MGNDI:[NRIL=NRIL],NRIV=NRIV...;
MGNDP;

Result
MGNDP;
MOBILE TELEPHONY NETWORK RESOURCE IDENTIFIER DATA
NRIL NRIV
6 1
END

Comment
The functionality will be activated when defining an NRI length greater than 0. Maximum 8
NRI per MSC

Action
Define the proxy table in the MSC(s) that will act as proxy

MGPTI:VLRADDR=<VLRADDR>,NRIV=<NRIV>...;
MGPTP:VLRADDR=ALL;
 Open
10 (20)
Prepared (also subject responsible if other) No.

edbrqas MU/NWE-05:
Approved Checked Date Rev Reference

11/10/2006 PA1

Result
MGPTP:VLRADDR=ALL;
MOBILE TELEPHONY NETWORK RESOURCE IDENTIFIER VLR PROXY TABLE DATA

VLRADDR NRIV NRIV NRIV NRIV NRIV NRIV NRIV NRIV

4-447785011000 1
4-447785012895 2
4-447785011100 3
4-447785012000 10
4-447785012100 11
4-447785012200 12
4-447785012300 13
4-447785012400 14
4-447785012500 15
4-447785013000 20
4-447785013100 21
4-447785013200 22
4-447785013300 23
4-447785013400 24

END

Comment

The proxy MSC relays signalling between two different MSC nodes. The proxy MSC has the
knowledge of the complete assignment of NRI values to MSC addresses in the whole MSC
Pools. By deriving a NRI from a TMSI and mapping the NRI to a MSC address, the proxy MSC
can identify a MSC node among multiple MSC nodes serving the same LA.

Action
Note that for all BSC(s) which are going to serve the pool, the parameter GLCNID should be
set to indicate support of Global CN-Id.

MGRIP:RNC=ALL;
MGRIC:RNC=RNC+ {[,RNCID=RNCID] [,GLCNID=GLCNID]};

Result
MGRIP:RNC=ALL;
MT RADIO NETWORK CONTROLLER DATA

RNC RNCID R1 R2 GLCNID

 Open
11 (20)
Prepared (also subject responsible if other) No.

edbrqas MU/NWE-05:
Approved Checked Date Rev Reference

11/10/2006 PA1

RNCPH6 234-15-596 RCPH6SO RCPH6SI NOTSUP

RNCCODEC
UMTS_AMR2_SET7
RNCPH5 234-15-595 RCPH5SO RCPH5SI NOTSUP

RNCCODEC
UMTS_AMR2_SET7
RNCPH2 234-15-593 RCPH3SO RCPH3SI NOTSUP

RNCCODEC
UMTS_AMR2_SET7
RNCPH4 234-15-594 RCPH4SO RCPH4SI NOTSUP

RNCCODEC
UMTS_AMR2_SET7
END

Comment
The equivalent data on BSC/RNC can be defined in parallel.
Repeat this action for all BSC(s) included in the scope of this procedure.

Action
Definition of BSC related signalling and traffic data in the MSC.

Result

WH definition, signalling data, BSC parameters and routes

Comment
These operations are not traffic affecting so they can be executed at any time. The equivalent
data on BSC can be defined in parallel.

Action
 Open
12 (20)
Prepared (also subject responsible if other) No.

edbrqas MU/NWE-05:
Approved Checked Date Rev Reference

11/10/2006 PA1

The existing area clusters in the MSC shall be extended with the area clusters from the other
MSC(s)

To Add it:
MGAAI:AREA=area + {[,SAI=<SAI>][,LAI=<LAI>][,PLMN=<PLMN>]};

To change it:
MGAAC:AREA=area +{[,RO=<RO>][,CO=<CO>][,EA=<EA>][,CARID=<CARID>]};

MGAAP: AREA=ALL;

Result
MGAAP: AREA=ALL;
MT AREA CLUSTER DATA

AREA ACET AREAID RO CO EA

1 SAI 234-15-248-39546 0 31 25
36 SAI 234-15-230-52835 0 31 10
234-15-230-52834
234-15-230-52833

Comment
For the case and for the MSC(s) where either no area cluster administration is available or
area cluster administration is available but not used, the equivalent configuration data
at BSC(s) or LA(s) or both shall be set.

Action
The existing inner cells in an MSC shall be extended with the inner cells from the other
MSC(s)

To Add it:
MGCEI:CELL=<cell>,CGI=<CGI>,BSC=<BSC>;

To change it:
MGCEC:CELL=<cell>+{[,CO=<CO>][,RO=<RO>][,NCS=<NCS>][,EA=<EA>]};

MGCEP:CELL=ALL;

Result
MGCEP:CELL=ALL;

MT CELL DATA
 Open
13 (20)
Prepared (also subject responsible if other) No.

edbrqas MU/NWE-05:
Approved Checked Date Rev Reference

11/10/2006 PA1

CELL CGI BSC CO RO NCS EA

T482151 234-15-21-2151 BEAPH 11 0 0 0
T482152 234-15-21-2152 BEAPH 11 0 0 0

Comment
The outer cells are still needed for handover as the pool is not operative yet.

Action
The existing outer cells/RNC(s) in an MSC shall be extended with the outer cells/RNC(s) from
the other MSC(s)

To add outer cell:

MGOCI::CELL=<cell>+{[,LAI=<LAI>][,CGI=<CGI>][,PLMN=<PLMN>]}+
{[,MSC=<MSC>][,MSCG=<MSCG>]};

To add outer RNC:

MGORI:RNC=<RNC>,RNCID=<RNCID>+{[,MSC=<MSC>][,MSCG=<MSCG]};

MGOCP:CELL=ALL;

Result
MGOCP:CELL=ALL;
MT OUTER CELL DATA

CELL AREAID MSC NCS

U39539 234-15-249-39539 OK 0
CN5GRA 234-15-160-1601 OK 0

Comment

Action
Define the external to the pool cooperating VLR(s) associated to the recently defined external
to the pool outer cells (LAI)/RNC(s).

To initiate a cooperating VLR:

MGCVI:VLR=VLR[,VLRADDR=VLRADDR,MAPV=MAPV],LAI=LAI...;

To specify a new LAI or RNI to a VLR already defined:

MGCVI:VLR=VLR[,VLRADDR=VLRADDR,MAPV=MAPV], NRIV=NRIV...,LAI=LAI[,NRIL=NRIL];

MGCVP:VLR=ALL;
 Open
14 (20)
Prepared (also subject responsible if other) No.

edbrqas MU/NWE-05:
Approved Checked Date Rev Reference

11/10/2006 PA1

Result
MGCVP:VLR=ALL;
MT COOPERATING VLR DATA
VLR VLRADDR MAPV LAI
PINGU 4-447785012895 MAP-2 234-15-228
END

Comment

Action
Remove the outer cells that shall be transformed into inner cells

To delete a cell:
MGOCE:CELL=CELL;

To delete RNC(s)
MGORE:RNC=RNC;

MGOCP:CELL=ALL;

Result
The outer cells or RNC(s) became the inner cells RNC(s)
MGOCP:CELL=ALL;
MT OUTER CELL DATA

CELL AREAID MSC NCS

U39539 234-15-249-39539 OK 0
CN5GRA 234-15-160-1601 OK 0
CN5GRB 234-15-160-1602 OK 0
CN5GRC 234-15-160-1603 OK 0

Comment
Outer cells belonging to BSC(s) or outer RNC(s) outside of the pool should not be removed.

Action
Remove cooperating VLR representing the MSC(s) in the pool

MGCVE:VLR=<VLR>,LAI=<LAI>,NRIV=<ALL>;

MGCVP:VLR=ALL;
 Open
15 (20)
Prepared (also subject responsible if other) No.

edbrqas MU/NWE-05:
Approved Checked Date Rev Reference

11/10/2006 PA1

Result
MGCVP:VLR=ALL;
MT COOPERATING VLR DATA
VLR VLRADDR MAPV LAI
PINGU 4-447785012895 MAP-2 234-15-228
END

Comment

Action
To define a new neighboring MSC Group (MSCG) or adds a neighboring MSC to an existing
neighboring MSC group in the Mobile services Switching Centre/Visitor Location Register
(MSC/VLR) Server

MGMGI:MSCG=MSCG,MSC=MSC;

MGMGP:MSCG=ALL;
MGNMP:MSC=ALL;

Result
MGMGP:MSCG=ALL;
MT NEIGHBOURING MSC GROUP DATA

MSCG MSC
PTH OK
KT
END
Comment

Action
To delete neighboring MSC Group (MSCG)

MGMGE:MSCG=MSCG,MSC=MSC;

MGMGP:MSCG=ALL;
MGNMP:MSC=ALL;

Result
MGNMP:MSC=ALL;
MT NEIGHBOURING MSC DATA
 Open
16 (20)
Prepared (also subject responsible if other) No.

edbrqas MU/NWE-05:
Approved Checked Date Rev Reference

11/10/2006 PA1

MSC MSCADDR R MSCCAPA

DT 4-447785013400 KTDT1HO MAPV-3

MSLOT-0
14DOT4-0
Comment
The former inter-MSC handover will become intra-MSC Handover

Action
DBTRI;
DBTSC:TAB=AXEPARS,SETNAME=GSM1APTF,NAME=MSCPOOL,VALUE=1;
DBTRE:COM;

Result

Comment
0= feature disabled
1= feature enabled

Action
DBTRI;
DBTSC:TAB=AXEPARS,SETNAME=GSMMMSC,NAME=MSCREQNUM,VALUE=1;
DBTRE:COM;

Result

Comment

Defines the maximum number of trials to select MSC from the neighboring MSC group
Applicable when target MSC is an MSC Pool
Value Range: 1-16
Default value=1

Action
DBTRI;
DBTSC:TAB=AXEPARS,SETNAME=GSMMMSC,NAME=ADMHOMSCPOOL,VALUE=0;
DBTRE:COM;

Result
 Open
17 (20)
Prepared (also subject responsible if other) No.

edbrqas MU/NWE-05:
Approved Checked Date Rev Reference

11/10/2006 PA1

Comment
Activate (1) the administration for Handover to MSC in Pool
Value Range 0-1

Action
DBTRI;
DBTSC:TAB=AXEPARS,SETNAME=GSMMMSC,NAME=OWNCNID,VALUE=0;
DBTRE:COM;

Result

Comment
Define CN-ID of the Global CN-ID of an MSC/VLR
Value range 0-4095

Action
DBTRI;
DBTSC:TAB=AXEPARS,SETNAME= GSMMMSC,NAME=TIMNRICHGM,VALUE=1;
DBTRE:COM;

Result

Comment
MSC/VLR server in MSC-Pool
The time supervision value during the handling of the changes in the Network Resource
Identifier (NRI) list in MSC/VLR server.
Values shall be greater or equal than the duration of timer used for periodic location
updating.
Dependent on: MSCPOOL GSM1APTF
Value Range 1-255
Default value 255

Action
Sub file 05000 Global Size Alteration

SAAII:SAE=1141,NI=10; !MSC – GROUP!

!SAAII:SAE=1137,NI=10; ! The area cluster conversation table!
!SAAII:SAE=156,NI=80; ! The number of subsystem individuals!

Result

Comment
 Open
18 (20)
Prepared (also subject responsible if other) No.

edbrqas MU/NWE-05:
Approved Checked Date Rev Reference

11/10/2006 PA1

Action
Sub file 10000 Size Alteration APT

SAAII:BLOCK=MCVLRD,SAE=500,NI=10; !Proxy Table!

SAAII:BLOCK=MBSSD,SAE=687,NI=500; ! Definition of CGI!
SAAII:BLOCK=MCVLRD,SAE=630,NI=20; ! Definition of cooperating VLR(s)!
SAAII:BLOCK=MCVLRD,SAE=629,NI=20; ! Definition of cooperating VLR(s)!
SAAII:BLOCK=MCVLRD,SAE=602,NI=50; ! Definition of cooperating VLR(s)!
SAAII:BLOCK=MCVLRD,SAE=603,NI=30; ! Definition of cooperating VLR(s)!
SAAII:BLOCK=MALTC,SAE=504,NI=120; ! Definition of MALT Routes!
SAAII:SAE=504,BLOCK=MUIUCM ,NI=12; ! RNC routes!

Result

Comment

2.4 BSC- Activation Phase

Action
The MODE parameter defines the mode of the MSC node in the BSC. It shall be noted that a
corresponding mode parameter does not exist in the MSC node itself, the MODE parameter is
a BSC internal parameter representing the BSC(s) view of the MSC node from a traffic
execution perspective

RLTDC: MSC=<MSC>,MODE=ACTIVE;
RLTDP:MSC=ALL;

Result

Comment
Value Range: Active, Inactive, Reselect and Barred. Ref [1]
In the INACTIVE mode, the MSC is defined and MSC related configuration can be made, for
example configuration of signaling and transmission links towards the MSC node. The BSC will
however not distribute any traffic towards the MSC or handle any terminating calls or
incoming handovers from the MSC.
When changing the mode from INACTIVE to ACTIVE, a RESET message is sent to the MSC
and the BSC starts distributing traffic towards the MSC. Terminating calls and incoming
handovers from the MSC will be handled.
 Open
19 (20)
Prepared (also subject responsible if other) No.

edbrqas MU/NWE-05:
Approved Checked Date Rev Reference

11/10/2006 PA1

3 Capacity

 32 MSC pool members per MSC pool

 32 MSC pool members per BSC
 32 MSC pool per BSC
 32 MSC pools per OSS-RC
 15000 cells per OSS-RC
 8 MSC pools per MSC/VLR
 8 NRI values per MSC/VLR
 1024 NRI values per BSC
 2048 Location numbers, in the MSC pool area. It includes all the location numbers
controlled by the MSC pool members (that is, multiple MSC pool areas)
 M-MGW may be configured with a maximum of 32 Virtual MGW(s).

4 Alarms

4.1 RNC
Not implemented yet.

4.2 BSC
There is an observation alarm issued whenever the mode of an MSC in an active pool is
changed to BARRED or RESELECT. This is to warn the operator that traffic distribution will be
affected for that MSC.

4.3 MSC
No new alarms regarding MSC in Pool.

5 Counters

There are no new counters on the nodes to collect performance information for the pool; the
counters are collected from individual nodes in the pool

5.1 BSC

The follow existent counters can be checked.

STS counter NUMREROUTMSG

The OSS performance monitoring reports on pool level can be used to monitor changes to the
normal MSC selection caused by alternative routing. For Alternative Routing the number of
rerouted connection establishments per MSC(s) is measured, on BSC level (STS counter
NUMREROUTMSG in object type MSC). The statistics can be used to check that Alternative
 Open
20 (20)
Prepared (also subject responsible if other) No.

edbrqas MU/NWE-05:
Approved Checked Date Rev Reference

11/10/2006 PA1

Routing gives the desired effect. It can also explain why the traffic distribution differs from
the CAP settings.

STS counter NUMTMSSEL

It is also possible to monitor the number of times an MSC is selected for mobile originating
connections per MSC, on BSC level (STS counter NUMTMSSEL in object type MSC).

5.2 RNC
Not implement yet

5.3 MSC
No new counters regarding to MSC in Pool.

6 Impact on MGW

The amount of additional two context calls has impact on the total node capacity point of
view on MFD capacity. All other node internal capacities are less impacted. Whether the extra
required MFD capacity has direct impact on node supported capacity figures depends on the
base configuration and traffic distribution

7 Appendices
-

Any comment to improve this document will be welcome.