MOP FOR MSS POOLING ACTIVATION.

1 (4)

Author: National Core Team.

Date:16.11.2011

Owner : NCT

NCT-PO-55

MOP For MSS Pooling Activation

PURPOSE
This Document covers detailed MSS pooling activation steps and changes in Node level. The main
purpose of this concept enable easy CN controlled load balancing between MSCs/MSSs in the pool area,
and higher resiliency and signaling savings at the radio interface through enhancements in core network
signaling.

SCOPE
This document covers MSS pooling activation procedure in MSS.

BENEFITS

Signaling savings in the core network: fewer location updates, fewer inter-MSC/MSS
handovers/relocations, and reduced HLR update signaling.
Multipoint in MSC Server architecture, when compared to MSC architecture: provides
optimal use of A and Iu transmission resources, no need for connecting user plane trunks from
each BSC to each MGW.
Overlapping pool areas to support MS moving patterns and to gain better utilization of core
network resources during traffic profile variation.
Easier capacity upgrades in the network, easier network level capacity planning.
Core network element resiliency for example in natural disasters.
More flexibility for software upgrades and maintenance of an MSC/MSS within the pool area.
Fewer RAN node rehomings due to a larger (pool area wide) service area.
Easy CN controlled load balancing between MSCs/MSSs in the pool area.
Higher resiliency and signaling savings at radio interface via enhancements in core network
signaling.
Optimal use of VLR resources in the pool area when VLR capacity or license is limiting the
subscriber inclusion in a certain VLR.

PREREQUSITES

1692 feature need to be activated in MSS (License required).

Multipoint License in MGW.
All BSC or RNCs need to be integrated with all the MSS in Pool Area.
All Node B sites & LAs need to be replicated in All MSS in pool.
SIGTRAN Links from all the connected MSS and RNC should be activated.
UPD for RNC must have VMGWs of All the Connected MGWs.

MOP FOR MSS POOLING ACTIVATION.

2 (4)

Author: National Core Team.

Date:16.11.2011

Owner : NCT

NCT-PO-55

MSS Pooling Activation procedure

Allowing implicit Location Updates
Activate Implicit location update in PRFILE (ZWOC:2,292,FF :;)

Activating Multipoint A or Iu in MSC Server Concept

1. Define the MSS Global Core Network ID (ZWVS: CNID=19 <GlobalCNid>;)

Creating own pool areas

2. Define the name of the used pool area and the length of the NRI used inside the pool area
(ZE3M:POOLNAME=CHNPOOL<poolname>,NRILEN=6<nrilen>;)
3. Check the created pool area information(ZE3O)

Adding the own MSS to the pool area

4. Check the name of the own MSS (ZQNI;)

5. Add the own MSS to the pool area. Define the used NRIs, and whether this MSS is the primary source
(ZE3A:TYPE=OWN,MSSNAME=<mssname>:CONFSEL=<confsel>,NRI=<nrivalue>:;)
6. Add the information needed for own MSS Maintenance Mode (ZE3E::MNRI=<nullnri>,
NBLAC=<maintlac>,NBMCC=<maintmcc>, NBMNC=<maintmnc>;)
7. Check the own MSS information (ZE3I:TYPE=OWN;)

Setting the TMSI allocation into use

8. Print the PLMN names and indexes (ZMXL;)

9. Check the existing TMSI allocation method definitions in your PLMN (ZMXP:NAME=<PLMN_name>;)
10. Set the TMSI reallocation to '
ON'in the location update with new visitor, IMSI attach, location update, and
periodic location update
(ZMXN:NAME=<PLMN_name>::TNEW=Y,TIMSI=Y,TLOC=<locup_itv>,TPER=<per_itv>;)
11. Check the new defined TMSI allocation methods used in your PLMN (ZMXP:NAME=<PLMN_name>;)
12. Activate the TMSI allocation in this MSS (ZMXM::TMUSE=Y;)
13. Check the activation status of the TMSI allocation (ZMXO;)

Adding parallel MSSs to the same pool area

14. Add the parallel MSS to the own pool area and define if it is primary or secondary. Define the NRIs
and the VLR info
a. If only the Multipoint Iu feature is active (ZE3A:TYPE=PAR,MSSNAME=<mssname>:
NRI=<nrivalue>:VDIG=<vlr_gt>;)
b. If both the Multipoint Iu and Multipoint A features are active
(ZE3A:TYPE=PAR,MSSNAME=<mssname>:NRI=<nrivalue>:VDIG=<vlr_gt>:MDIG=<mss_gt>;)

15. Check the parallel MSS information (ZE3I:TYPE=PAR;)

MOP FOR MSS POOLING ACTIVATION.

3 (4)

Author: National Core Team.

Date:16.11.2011

Owner : NCT

NCT-PO-55

Creating neighbour pool areas

16. Define the neighbour pool area and the length of the NRI used inside that pool area
(ZE3C:POOLNAME=<poolname>,NRILEN=<nrilength>;)
17. Output the neighbour pool area information (ZE3S;)

Adding MSSs to the neighbour pool area

18. Add the MSS to the neighbour pool area. Define the NRIs and the VLR information used by the MSS
in the neighbour pool area
(ZE3L:POOLNAME=<poolname>:MSSNAME=<mssname>,NRI=<nrivalue>:VDIG=<vlr_gt>:MDIG=<
mss_gt>:;)
19. Check the MSSs in the neighbour pool area (ZE3J:POOLNAME=<poolname>;)

Defining Network LAs to the neighbour pool area

20. Define network LA information to the neighbour pool or modify the already existing information

a. Create a new network LA (ZEIA:<lac>:::NPAI=<Neighbour pool area index>;)

b. Modify an already existing network LA (ZEIM:<lac>:NPAI=<Neighbour pool area index>;)
21. Check all the neighbour pool area network LA relations (ZE3S::Y;)

Activating subscriber authentication and ciphering

22. Activate authentication in the MSS (ZMXM::AUTH=Y;)

23.
24.
25.
26.

Check the activation status of authentication (ZMXO;)

Print out the PLMN names and indexes (ZMXL;)
Check the existing authentication and ciphering keys in your PLMN (ZMXP:NAME=<PLMN_name>;)
Set authentication and ciphering to '
ON'with location update, new visitor, IMSI attach, and periodic location
update. Allow UMTS Ciphering
(ZMXN:NAME=<PLMN_name>:::ANEW=Y,AIMSI=Y,ALOC=<locup_itv>,APER=<per_itv>:::UCIPH=Y,CIPH=Y;)
27. Check the new authentication and ciphering methods in your PLMN (ZMXP:NAME=<PLMN_name>;)

Exporting existing radio network configuration

28. Choose the own and the auxiliary network LAs which will be included in the transfer file
(ZELT:TYPE=LA,NAME=<laname>:INC=Y; or ZELT:TYPE=AUXLA,NAME=<laname>:INC=Y;)

29. Choose the network LAs which will be included in the transfer file
(ZEIT:LAC=<lac>,MCC=<mcc>,MNC=<mnc>:INC=Y;)
30. Check the own and auxiliary network LAs which will be included in the transfer file (ZELO::INCSEL=Y; or
ZELJ::INCSEL=Y;)
31. Check the network LAs which will be included in the transfer file (ZEIO::INCSEL=Y;)
32. Analyze the chosen LAs for conflicts (ZELL;)
33. Create an empty directory for the transfer files in the source MSS (ZIWL::WSB,DEF::<transferdir>,,,<initials>;)
34. Export the selected radio network to the transfer file (ZE3X:DNAME=<transferdir>;)
35. Check the copied radio network elements in the summary report against the chosen Las
36. Transfer the files (NPCFIL00.IMG,..., and NPCFIL06.IMG) from the <transferdir> directory under the root
directory of the active software package by a selectable method, for example, FTP, MO-disk, or DAT-tape to the
other MSSs.

MOP FOR MSS POOLING ACTIVATION.

4 (4)

Author: National Core Team.

Date:16.11.2011

Owner : NCT

NCT-PO-55

Importing existing radio network configuration

37. Create an empty directory for the transfer files in the target MSS
(ZIWL::WSB,DEF::<transferdir>,,,<initials>;)

38. Create an empty RNFILIMP directory for the combined radio network files in the target MSS
(ZIWL::WSB,DEF::RNFILIMP,,,<initials>;)
39. Import the radio network from the transfer files (ZE3Y:DNAME=<transferdir>;)
40. Check the copied radio network elements in the summary report against the LAs chosen in the import phase.
The following data is included in the report

Activating the imported radio network configuration

41. Activate the new radio network configuration in the target MSS (ZE3V;)