MSC in Pool

1. Introduction
The MSC in Pool, as a part of Intra Domain Connection of RAN Nodes to Multiple CN
Nodes solution, overcomes the strict hierarchy, which restricts the connection of a
BSC node to just one MSC. This restriction results from routing mechanisms in the
BSC which differentiate only between information to be sent to the MSC. The MSC in
Pool solution introduces further the concept of pool-areas which is enabled by the
routing mechanism in the BSC. An MSC pool-area is comparable to an MSC service
area as a collection of one or more BSC service areas. In difference to an MSC
service area a pool-area is served by multiple MSCs in parallel which share the
traffic of this area between each other

2. Benefits:
2.1 Network Resource Identification

An MSC pool-area is an area within which an MS roams without a need to change

the serving MSC. A pool-area is served by one or more MSCs nodes in parallel.
The complete service area of a BSC belongs to the same one or more poolarea(s). An BSC service area may belong to multiple pool-areas, which is the case
when multiple overlapping pool-areas include this BSC service area. If LAs span
over multiple BSC service areas then all these BSC service areas have to belong
to the same pool-area

2.2 Redundancy
2.3 MSS load Distribute

3.

Procedure:

3.1 TO Check CCITT7 SIGNALLING POINT DATA

c7spp:sp=all;
CCITT7 SIGNALLING POINT DATA
SP

SPID

3-1022

OWNSP

SIBSC30

3-2072

SIMGW15

3-4102

DSMSS07

END

3.2

c7spi:sp=3-4104;
3.3

To Add new Signaling Point

{ Adding new SP 3-4104}

To define SPID

C7pnc:sp=3-4104,spid=DSMSS12; { Defining spid=DSMSS12 which having SP 34104}

3.4 MSC Definition in BSC Data

Rrmbp: msc=all;

{ to check Current MSC Definition}

MSC DEFINITION IN BSC DATA

MSC

SP

CNID

DSMSS03

3-5001

DSMSS04

3-5002

DSMSS11

3-2035

DSMSS07

3-4102

END

To Define MSC:

RRMBI:MSC=DSMSS12,SP=3-4104,CNID=5
CNID=5}

{adding DSMSS12 3-4104 with

3.5 Define CCITT7 SCCP NETWORK CONFIGURATION DATA

To Check:

c7ncp: sp=all,ssn=all;
CCITT7 SCCP NETWORK CONFIGURATION DATA

SP

SPID

SPSTATE

3-2072

SIMGW15 ALLOWED

BROADCASTSTATUS SCCPSTATE
CON

PROHIBITED

SSN

SUBSYSTEMSTATE

SST

254

PROHIBITED

YES

SPSTATE

BROADCASTSTATUS SCCPSTATE

SP

SPID

3-4102

DSMSS07 ALLOWED

NCON

ALLOWED

SSN

SUBSYSTEMSTATE

SST

254

ALLOWED

YES

To define:

c7npi:sp=3-4104;

{ adding new Sp}

c7nsi:sp=3-4104,ssn=254;

{adding ssn id to new Sp}

3.6

MTP ROUTING Data.

c7rsp:dest=all;

{ to check current mtp routing data}

CCITT7 MTP ROUTING DATA

DEST

SPID

DST PRIO

3-2072

SIMGW15

ACC

3-4102

DSMSS07

ACC

LSHB

LS

SPID

RST

3-2072

SIMGW15

WO

3-2072

SIMGW15

WO

END

c7rsi:dest=3-4104,prio=1,ls=3-2072
Connecting
MGW }

4.

{ Defining new sp with priority and ls of

ATTACH CIC to New MSS.

After links definition, coordinate with Core team for definition at their end and after
definition proceed to attach CICs to new MSS as per plan. Below attached reference DT
for adding CIC.

DT Of SIBSC30.xlsx

5. NETWORK RESOURCE IDENTIFIER DATA (NRI)

An NRI is a part of Temporary Mobile Subscriber Identity (TMSI). It is used to route

messages to the right MSC or to the right Network Service (NS) entity

rrnrp:msc=all

{To check the current

value}
RRNRI: MSC=DSMSS12, NRI=9&&12;
{TO defines one or
more NRIs and associates them
with an MSC}

6. NETWORK RESOURCE IDENTIFIER LENGTH DATA

Rrnlp;
length of MSCs and SGSNs}

{ It lists the current NRI

RRNLC:MSCNRILENGTH=5;
all MSCs to 5 bits}
RRNLC:SGSNNRILENGTH=7;
for all NS entities to 7 bits}

{ changes the MSC NRI length for

{ changes the SGSN NRI length

7. MSC TRAFFIC DISTRIBUTION DATA

RLTDP:MSC=ALL;
defined MSCs.}

RLTDC:MSC=MSC1,MODE=ACTIVE; { changes the mode of the MSC MSC1 to

{ to check MSC traffic distribution data for all

ACTIVE}

RLTDC:MSC=MSC1,CAP=20;

to 20}

{ The relative capacity value for MSC1 is changed