You are on page 1of 18

Feature 525: Inter-MSC Handover

DN00197943 © Nokia Corporation 1 (18)


Issue 13-0 en Nokia Proprietary and Confidential
Feature 525: Inter-MSC Handover

The information in this documentation is subject to change without notice and describes only
the product defined in the introduction of this documentation. This documentation is intended
for the use of Nokia's customers only for the purposes of the agreement under which the
documentation is submitted, and no part of it may be reproduced or transmitted in any form or
means without the prior written permission of Nokia. The documentation has been prepared to
be used by professional and properly trained personnel, and the customer assumes full
responsibility when using it. Nokia welcomes customer comments as part of the process of
continuous development and improvement of the documentation.
The information or statements given in this documentation concerning the suitability, capacity,
or performance of the mentioned hardware or software products cannot be considered binding
but shall be defined in the agreement made between Nokia and the customer. However, Nokia
has made all reasonable efforts to ensure that the instructions contained in the documentation
are adequate and free of material errors and omissions. Nokia will, if necessary, explain issues
which may not be covered by the documentation.
Nokia's liability for any errors in the documentation is limited to the documentary correction of
errors. NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS
DOCUMENTATION OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL
(INCLUDING MONETARY LOSSES), that might arise from the use of this documentation or
the information in it.
This documentation and the product it describes are considered protected by copyright
according to the applicable laws.
NOKIA logo is a registered trademark of Nokia Corporation.
Other product names mentioned in this documentation may be trademarks of their respective
companies, and they are mentioned for identification purposes only.

Copyright © Nokia Corporation 2004. All rights reserved.

2 (18) © Nokia Corporation DN00197943


Nokia Proprietary and Confidential Issue 13-0 en
Contents

Contents 3

Summary of changes 5

1 Installation and testing 7


1.1 Configuration requirements 7
1.1.1 Network elements involved 7
1.1.2 Hardware effects 7
1.1.3 Firmware effects 7
1.2 Remarks 7
1.3 Installation and activation 8
1.4 Testing 17
1.4.1 Test environment 17
1.4.2 Prerequisites for testing 18
1.4.3 Test execution and expected results 18
1.5 Deactivation of feature 18
1.6 Deactivation testing 18

DN00197943 © Nokia Corporation 3 (18)


Issue 13-0 en Nokia Proprietary and Confidential
Feature 525: Inter-MSC Handover

4 (18) © Nokia Corporation DN00197943


Nokia Proprietary and Confidential Issue 13-0 en
Summary of changes

Changes between document issues are cumulative. Therefore, the latest document
issue contains all changes made to previous issues.

Changes made between issues 13–0 and 12–0

For more information on the feature, refer to the corresponding feature


description.

Changes made between issues 12–0 and 11–0

Integrated and Standalone MSS have been added to Section Network elements
involved.

Changes made between issues 11–0 and 2.3–7

The issue numbering has been changed together with the change in the document
format.

DN00197943 © Nokia Corporation 5 (18)


Issue 13-0 en Nokia Proprietary and Confidential
Feature 525: Inter-MSC Handover

6 (18) © Nokia Corporation DN00197943


Nokia Proprietary and Confidential Issue 13-0 en
Installation and testing

1 Installation and testing

1.1 Configuration requirements

1.1.1 Network elements involved

The following network elements are needed:

• an MSC

• a Standalone MSS

• an Integrated MSS

1.1.2 Hardware effects

This feature has no effects on hardware.

1.1.3 Firmware effects

This feature has no effects on firmware.

1.2 Remarks
Handover between base stations belonging to different PLMNs is not supported
by this feature.

DN00197943 © Nokia Corporation 7 (18)


Issue 13-0 en Nokia Proprietary and Confidential
Feature 525: Inter-MSC Handover

1.3 Installation and activation


Implementation Procedure in the MSC-A

Define the ISDN-number of the home MSC in the GSM network and the network
element-specific number file (HRNFIL) of the MSC-A.

Creating the ISDN-number of the MSC

1. Create the MSC ISDN number:

ZWVS:MSC=<msc>:NP=<np>;

where:

<msc> the international coded MSC number


<np> E164

2. List the MSC ISDN number:

ZWVI:MSC;

About the Base Station Configuration

In the MSC, there are two files related to the location areas: one for the home
MSC's location areas (LAFILE) and another for the neighbouring MSC's ones
(NLAFIL). In the handover required message, the MSC-A receives the cell
identity (CI) and the location area code (LAC) where the call is going to be
handed over. The target cell is searched among the home MSC's location areas
first. If it is not found there, the search is expanded to the neighbouring location
areas. If the target cell is found in the NLAFIL, the MSC initiates the inter-MSC
handover procedure.

Configuring the radio network

1. Update the new location area to the NLAFIL in the MSC-A, which belongs
to a neighbouring MSC:

ZEIA:<lac>:MISDN=<misdn>,MNA=<mna>,MSPC=<mspc>,MSNC=<msnc>:
:CID=<cid>,VER=<ver>;

where:

lac the location area number

8 (18) © Nokia Corporation DN00197943


Nokia Proprietary and Confidential Issue 13-0 en
Installation and testing

misdn the national coded MSC ISDN number

mna NA

mspc the signalling point code of the target MSC

msnc NA0

cid the target cell identification method

ver the profile of the target BSC

2. Check the home location areas:

ZELO;

3. Check the neighbouring location areas:

ZEIO;

Adding the MAP subsystem for the MSC-MSC interface

There has to be an MAPM-subsystem for the MAP connection between the


MSCs. If it does not exist, create it with the SCCP data handling commands.

1. Check the subsystems:

ZNHI;

2. Select the subsystems of the facing MSC and add the MAPM subsystem:

ZNFD:<msnc>,<mspc>,0:<mssn>,<msna>,0;

where:

<msnc> the MSC signalling network, NA0

<mspc> the SPC of the facing MSC

<mssn> the MSC subsystem number, 8 for inter-MSC handover

<msna> the MSC subsystem name

Selecting the MAP Version

Use the MAP protocol phase 2 when the neighbouring MSCs have been updated
to support the MAP protocol phase 2.

DN00197943 © Nokia Corporation 9 (18)


Issue 13-0 en Nokia Proprietary and Confidential
Feature 525: Inter-MSC Handover

1. Change the MAP version to phase 2:

ZOPH:MODIFY:AC=<ac>,EXT=YES,:VER=<pha>;

where:

<ac> Application context, here 11

<pha> MAP version, here 2

2. Checking the highest supported MAP protocol version:

ZOPH:INTERR;

where:

ac Application context, here 11

Routing of Handover Call in MSC-A

In the inter-MSC handover, the call between the MSCs is routed from the MSC-
A to the MSC-B with the handover number (HON) received from the MSC-B.
The handover numbers are usually analysed in tree 50, but the operator can decide
otherwise. The handover number analysis tree is defined in the EOS analysis.

The selected route used in the inter-MSC handover must be uncompressed and it
should offer 64 kbit/s end-to-end digital connection between MSCs to ensure the
success of the data calls after handover.

1. Create the EOS analysis:

ZRXC:<cc>:<arg>,<ari>,,,<tree>,<corg>;

where:

cc 1032, cause code

arg ALL, analysis result group

ari CMANAL, analysis result identifier

tree the user defined analysis tree

corg the charging origin

2. Create the analysis of HON:

ZRDC:TREE=<tree>,DIG=<dig>,TON=<ton>,:ROU=<rou>,CT=<ct>,SP=
<sp>:CP=<cp>;

10 (18) © Nokia Corporation DN00197943


Nokia Proprietary and Confidential Issue 13-0 en
Installation and testing

where:

tree the handover number analysis tree defined in the EOS


analysis

dig the handover number to be analysed in national form

ton NAT

rou the route leading to the facing MSC

ct SC

sp seizure point of the route

cp OE

3. Check the analysis of handover number:

ZRII:TREE=<tree>;

where:

tree the handover number analysis tree defined in the EOS


analysis

Intermediate charging due to Inter MSC handover in MSC-A

You can generate intermediate charging due to the inter-MSC handover in the
MSC-A. This is controlled by the PRFILE parameter
INTERMEDIATE_CHARGING (class 1, parameter 75). This parameter is a bitstruct
consisting of 8 bits, where a bit indicates whether intermediate charging has to be
done (XXX1XXXXB, 1 is indicating the place). Pay a special attentiond when
changing the value of this parameter:

• The command for generating intermediate charging:

ZWOC:1,75,<value>;

where:

value value = existing value + 10

DN00197943 © Nokia Corporation 11 (18)


Issue 13-0 en Nokia Proprietary and Confidential
Feature 525: Inter-MSC Handover

Generating PTC ticket due to Inter MSC handover in the MSC-A

You can generate a PTC ticket due to Inter-MSC handover in the MSC-A. This
ticket generation is route-dependent because it is controlled by the route-
dependent outgoing call control parameter file (OP0FIL) record. It is also
controlled in general by the charging parameter (CHPARA) file.

1. Set the PTC generating parameter ON in CHPARA:

ZGTM:<ctype>:<index>,<gpar>;

where:

ctype TERM

index 10
gpar ALL

2. Set the PTC generating parameter ON in OP0FIL record:

ZCPF:NCCP=<nccp>::::::HOCDR=<hocdr>;

where:

nccp the name of the parameter set used in the outgoing route
to the MSC-B

hocdr Y

Implementation procedure in the MSC-B

Creating the handover number

Define the handover number in the HRNFIL of the MSC-B. Ensure that the
handover number is in the same form when it is released as it was when it was
reserved.

1. Create the handover number:

ZWVC:HON=<hon>:TON=<ton>;

where:

hon the handover number range

ton the type of number

12 (18) © Nokia Corporation DN00197943


Nokia Proprietary and Confidential Issue 13-0 en
Installation and testing

2. Check the handover number:

ZWVJ:HON:;

Routing the handover call in the MSC-B

Note
Create a special route type before routing the inter-MSC handover call in the
MSC-B. Then create an analysis of the handover number leading to the specific
route defined earlier.

1. Create the handover special route to the SPCROU file:

ZRPH:OUTR=<outr>,STP=<stp>;

where:

outr customer specific (GSMEND)

stp 1

2. Check the record number of the handover special route in the SPCROU
file:

ZRPI:SRT=<srt>;

where:

srt HO

3. Create the analysis of HON:

ZRDC:TREE=<tree>,DIG=<dig>,TON=<ton>,:SPR=<spr>,CT=<ct>,SP=
<sp>,:NCHA=<ncha>;

where:

tree the tree number where the incoming route from the
MSC-A is analysed

dig the handover number to be analysed

ton the type of number

spr the number of SPCROU record reserved for handover

ct SC

DN00197943 © Nokia Corporation 13 (18)


Issue 13-0 en Nokia Proprietary and Confidential
Feature 525: Inter-MSC Handover

sp 1

ncha the name of charging

Generating POC ticket due to Inter MSC handover in the MSC-B

You can generate a POC ticket due to the Inter MSC handover in the MSC-B.
This ticket generation is route-dependent because it is controlled by the route-
dependent incoming call control parameter file (IP0FIL) record. It is also
controlled in general by the charging parameter (CHPARA) file.

1. Set the POC generating parameter ON in CHPARA:

ZGTM:<ctype>:<index>,<gpar>;

where:

ctype ORIG
index 12

gpar ALL

2. Set the POC generating parameter ON in OP0FIL record:

ZCPF:NCCP=<nccp>::::::HOCDR=<hocdr>;

where:

nccp the name of the parameter set used in the incoming


route from the MSC-A

hocdr Y

Generating the MTC ticket due to Inter MSC handover in the MSC-B

You can generate an MTC ticket due to Inter MSC handover in the MSC-B. This
ticket generation is controlled by charging parameter (CHPARA) file.

• Set the POC generating parameter ON in CHPARA:

ZGTM:<ctype>:<index>,<gpar>;

where:

ctype TERM

index 9

14 (18) © Nokia Corporation DN00197943


Nokia Proprietary and Confidential Issue 13-0 en
Installation and testing

gpar ALL

Measuring destination

You can use the handover number as an outgoing destination in the destination
measurement in the MSC-A. To carry out the measuring, the PRFILE parameter
HO_NUM_AFFECTS_TO_TRA must be set.

1. Set the parameter HO_NUM_AFFECTS_TO_TRA ON in PRFILE:

ZWOC:<class>,<index>,<val>;

where:

class 9, parameter class

index 76, parameter index


val 1, value

2. Add an object to the object list:

ZTDC:<mode>,<obln>:TYPE=<dtype>,OUT=<hon>;

where:

mode DEST, measurement mode

obln the user defined list number, object list number

dtype INT, destination type

hon the handover number in international form

3. Create the traffic measurement:

ZTMC:<name>,<type>,<obln>,<rod>;

where:

name the user-defined measurement name

type DEST

obln the object list number defined in the TDC command

rod ALL

4. Start the measurement:

ZTMS:<name>;

DN00197943 © Nokia Corporation 15 (18)


Issue 13-0 en Nokia Proprietary and Confidential
Feature 525: Inter-MSC Handover

where:

name the user-defined measurement name

Measuring destination to destination

In the destination to destination measurement, you can define the MSISDN


number of the subscriber by defining the handover as an incoming destination and
the handover number as an outgoing destination in the MSC-A. This kind of
measurement shows how the handovers made by the subscribers are divided
between the different handover number destinations.

1. To carry out the measuring, set the PRFILE


parameterHO_NUM_AFFECTS_TO_TRA as described in the destination
measurement.

2. Add an object to the object list:

ZTDC:<mode>,<obln>:TYPE=<dtype>,INC=<indest>,OUT=<hon>;

where:

mode DTD, measurement mode

obln the user-defined list number, object list number

dtype INT, destination type

indest the subscriber's MSISDN number in international form

hon the handover number in international form

3. Create the traffic measurement:

ZTMC:<name>,<type>,<obln>,<rod>;

where:

name the user-defined measurement name

type DTD

obln the object list number defined in the TDC command

rod ALL

4. Start the measurement:

ZTMS:<name>;

where:

16 (18) © Nokia Corporation DN00197943


Nokia Proprietary and Confidential Issue 13-0 en
Installation and testing

name the user-defined measurement name

Field reporting

You can define a handover number as an outgoing destination in a trafficability


measurement in the MSC-A. To carry out the clear code to destination measuring,
the PRFILE parameter HO_NUM_AFFECTS_TO_FDR must be set.

1. Set the parameter HO_NUM_AFFECTS_TO_FDR ON in PRFILE:

ZWOC:<class>,<index>,<val>;

where:

class 9, parameter class

index 78, parameter index


val 1, value

2. Modify the destination number:

ZTUM:<ccgm>:DEST=<dest>;

where:

ccgm DES, clear code group mode

dest the handover number in international form

3. Start the measurement:

ZTUS:<cls>;

where:

cls CLS (clear codes to destination)

Implementation instructions

The feature is automatically available after software installation.

1.4 Testing

1.4.1 Test environment

The following network elements are required:

DN00197943 © Nokia Corporation 17 (18)


Issue 13-0 en Nokia Proprietary and Confidential
Feature 525: Inter-MSC Handover

• two MSCs

• an HLR

• two BSCs

• two BTSs

• two mobile stations

1.4.2 Prerequisites for testing

The radio network must be configured to support inter MSC handovers.

1.4.3 Test execution and expected results

Test execution

• Establish an MS call.

• Move the MS to the location area covered by another BTS which belongs
to a different MSC.

• Check the continuity of the call.

• Clear the call.

Expected results

1. The new path through the MSC-B is established successfully.

2. The old BSS-A-MS connection is released correctly.

1.5 Deactivation of feature


The feature is available automatically after software installation and cannot be
deactivated

1.6 Deactivation testing


As the feature cannot be deactivated, deactivation testing is not possible.

18 (18) © Nokia Corporation DN00197943


Nokia Proprietary and Confidential Issue 13-0 en