Hand Over

DESCRIPTION15/190 46-FAD 104 08 Uen D

Handover Abstract

The purpose of this document is to describe the function Inter-MSC Handover from a Data Transcript point of view.

Contents

1 Revision Information

2 Description

1 Revision Information 2

Description

2.1 Abbreviations 2.2 Concerned Nodes 2.3 General 2.4 Technical Solution 2.5 Traffic Cases 3

Data Transcript Impacts

3.1 General 3.2 Subfile 10000 - Size Alteration Event, APT 3.3 Subfile 13000 - Exchange Properties 3.4 Subfile 15300 - Route Characteristics 3.5 Subfile 15450 - Internal Number-Series / Roaming & HO Numbers 3.6 Subfile 15600 - B-Number Analysis 3.7 Subfile 77100 - Inter-Msc Handover 4

Miscellaneous Information

4.1 Class 5

References

Revision Impacts Prepared DateA New document ERAJOGI 96-09-13B Checked document ERAMIST 97-05-26C Updated document to SS R7 ETOTRRE 98-09-21D Updated to SS R8.0. No changes. ERARDPN 00-02-29

2.1 Abbreviations

2.2 Concerned Nodes

� MSC

2.3 General

Handover can only be performed during a call. Handover occurs in the network when the BSC serving the call finds out that an neighbouring cell got noticeable better conditions to take over. This evaluation is based on measurements produced by the MS itself and the BTS. Signal strength, Bit error rate and Timing advance are measurement that the BSC uses as criteria to initiate the Handover procedure.

There are three different cases of Handover that can occur in the network,

� Intra-BSC Handover:

Handover within a cell or between two cells belonging to the same BSC.

� Inter-BSC/Intra-MSC Handover:

Handover between two cells belonging to different BSCs but the same MSC.

� Inter-MSC Handover:

Handover between two cells belongs to different MSCs.

There are three different types of Inter-MSC Handover,

� Basic Handover � Subsequent Handover back to the anchor MSC � Subsequent Handover to third MSC

Those three cases of Inter-MSC Handover will be described in this document.

2.4 Technical Solution

Inter-MSC handover can be performed using either MAP version 1, MAP version 2 or MAP version 3. More functionality can be used using MAP V3. Which version to use is set with the Exchange property, HOMAPVERSION. The parameter determines the primary MAP version to be used when

BSC Base Station ControllerBTS Base Transceiver StationCGI Cell Global IdentityHO HandoverMAP Mobile Application PartMS Mobile StationMSC Mobile Services Switching CentreVLR Visitor Location Register

establishing outgoing inter-MSC handover dialogue towards non-anchor MSCs.

2.4.1 Handover Analysis in MSC/VLR

2.4.1.1 Routes

The allocation of handover numbers is handled by the block MRNR (same block as for roaming numbers). One or more separate route(s) are defined for handover.

One software route for block MHOC is defined for handling of all outgoing Handover calls. A BO is defined for B-number analysis origin for incoming handover numbers. Also a RO, for possible branching in the route analysis, is defined. The route for outgoing Handover calls has FNC=1.

Example 1 MML command definitions

EXROI:R=1MHOC, DETY=MHOC, FNC=1; ! ROUTE FOR OUT GOING HO CALLS ! EXRBC:R=1MHOC, BO=8, RO=4;

One incoming software route is defined for every MSC that are possible to Handover calls to. This route is used for incoming calls from the MS that are handed over to another MSC. This is possible if the MS puts the Handover call on hold and initiates a new call. There is a possibility to define CO and RO for these routes. Origin for B-number analysis will be the normal origin for mobile originating calls (defined in IMSI number analysis). These MHOC-routes has FNC=2.


EXROI:R=2MHOC1, DETY=MHOC, FNC=2; ! ROUTE FOR INC OMING MOBILE ! ! ORIGINATED CA LLS FROM MSC2, ! ! I.E. CALL PUT ON HOLD AND A ! ! SECOND CALL I S INITIATED ! ! BO FROM MGISI !

2.4.1.2 Handover Numbers

Handover numbers could either be allocated as an separate number series or within the same number series as the roaming numbers. How many numbers that should be allocated is subscriber and traffic dependent.

MGRSI - Definition of Handover numbers with connection to already defined route.

If same number for roaming and handover should be used.


MGRSI:R=MRNR0, MSRNS= 46 70 757 01;

If own number for handover should be used.


MGRSI:R=HOVER0, MSRNS= 46 70 757 03;

MGRSC - Connection of Handover numbers. HONPERM means that the number series is permitted to use only as Handover numbers.


MGRSC:MSRNS= 46 70 757 03, USAGE=HONPERM;

MGRNI - Connection of Handover number.


MGRNI:MSRN= 46 70 757 0300 && 46 70 757 0399;

2.4.1.3 B-Number Analysis

B-number analysis is the same for HO-numbers as for roaming numbers. Analysis of incoming HO-numbers from other MSC is specified in route definition of software route for block MHOC (FNC=1).


ANBSI:B=8-467076, BNT=1, L=11, D=5-0, CC=3, RC=25; ! MSRN TO MSC2! ! HANDOVER # !

Incoming own HO-numbers from PSTN must lead to termination.


ANBSI:B=8-467075, BNT=4, M=2, F=9; !TERMINATING ! !ROAMING AND ! !HANDOVER NO.! ANBSI:B=9-70 757 03, MTE, D=5-0, L=9, CC=3;

2.4.1.4 Definition of Cells, Own and Neighbouring

Own cell definition are in case of Handover used for analysis of the received CGI in Handover required message from own BSC. If the CGI not belongs to own MSC service area it will lead to a Inter MSC Handover (otherwise Intra MSC Handover).

MGNMI - definition of neighbouring MSCs. Here MUST all MSCs, which are possible to hand over calls to, be defined. MSCADDR is the MSCs SCCP address proceeded by the NA (Nature of Address). NA=4 means international format. " R" is the route defined for this particular MSC, used for incoming calls from MS which have put hand over call on hold.


MGNMI:MSC=MSC2, MSCADDR=4-46 70 764 0000, R=2MHOC1;

MGOCI - Here all cells that are neighbouring cells to own cells (own cells = cells belonging to own MSC service area.) have to be defined. Note that there is no need to define all cells in neighbouring MSCs, only neighbouring cells to own cells (also defined in BSC).


MGOCI:MSC=MSC2, CELL=30001, CGI=240-01-0004-0001 ; MGOCI:MSC=MSC2, CELL=30003, CGI=240-01-0004-0002 ; MGOCI:MSC=MSC2, CELL=40003, CGI=240-01-0004-0003 ;

These definitions are used to translate the received CGI (received in HO required message from own BSC) to a MSC SCCP address, which will be used in HO signalling with that MSC.

In the definition of neighbouring MSCs all MSCs possible for subsequent HO must be defined. Note that this can be more than two, even if the basic traffic cases only describes subsequent HO to third exchange. It could be subsequent HO to fourth, fifth, sixth exchange and so on.

2.5 Traffic Cases

2.5.1 General

The Inter-MSC handover function realises the continuity of a call when the mobile subscriber moves between cells controlled by different MSCs.

The function implemented in the non-anchor MSC is able to receive the incoming handover call from the anchor MSC and to supervise it during the movements of the subscriber within the MSC controlled area. When a subsequent handover is necessary, the call can be handed back to the anchor MSC or to a third MSC.

Figure 1 The three cases of Inter-MSC handover

2.5.2 Basic Handover

The MS has a speech connection, and moves between two MSC serving areas. The serving BSC detects that a HO (Hand Over) is necessary, and sends " HO required" message to the serving MSC. This message includes Cell Identity of the target Cell.

The serving (anchor) MSC receives the message, and performs analysis of the target cell identity. If the cell belongs to another MSC (MSC-B), the MHOC block in anchor MSC (MSC-A) will handle an outgoing HO procedure to the target MSC. The message "Perform HO" is sent from MSC-A to MSC-B (target Cell Identity included).

In MSC-B the MHIC block handles the incoming HO procedure. A free radio resource will be allocated in the target cell ("HO request" and " HO request acknowledge" signalling with BSC-B). If the radio allocation is successful, MHIC will allocate a HO number from the HOVER route and send it in a "Radio channel acknowledge" message to MSC-A.

MSC-A will now set up a speech connection to MSC-B, using the received HO-number. This is done using normal telephony signalling (R2/TUP/ISUP). MSC-A will also send a "HO Command" to the BSC.

When the MS has switched over to the target cell a "HO-detect" message is sent from BSC-B to MSC-B, and further to MSC-A. Also a " faked" B-answer signal is sent from MSC-B to MSC-A where it is stopped. According to the first of following events and according to exchange properties, the MSC-A can switch the call over to MSC-B:

1. When the Group switch trigger timer expires. 2. When receiving Hand Over detect from MSC-B. 3. When the B-answer signal is received from MSC-B. 4. When MAP message, send end signal, is received from MSC-B.

When the HO is completed in MSC-B, the "Send end signal" is sent to MSC-A. Now the MSC-A will clear the radio connection on the "A-side" ("Clear command" and "Clear complete"). MSC-B will have the main radio resource control and be considered the serving MSC, but not the anchor MSC. The MHIC block controls the call in MSC-B until its cleared or a subsequent HO is performed.

MSC-A (anchor MSC) has the overall call control (block MHOC) until the call is cleared. When the MS ends the call, it is forced to do a location updating to the new MSC/VLR (MSC-B), HLR will be updated and the subscriber deleted in the MSC-A VLR

2.5.3 Subsequent Handover in MSC-B

If a MS moves back to the MSC-A service area a subsequent HO back is performed. Since the MSC-A is already controlling the call, the speech connection to MSC-B is not needed anymore. The MS will be allocated a radio resource in MSC-A.

If a MS moves from MSC-B to a third MSC (MSC-B'), a subsequent HO to third MSC is performed. A new speech connection from MSC-A to MSC-B' is set up, and the connection to MSC-B is released. The MS will be allocated a radio resource in MSC-B'.

In subsequent Handover to third exchange, the MSC-B' will receive the CGI value of the target cell in HO required message from own (serving) BSC. MSC-B will analyse the CGI value to find out which MSC (MSC-B') it belongs to. Then the MSC-B will send CGI for serving and target cell and the address of MSC-B'. Now MSC-A will have all information to ask MSC-B' for a HO-number and perform the Handover.

3 Data Transcript Impacts

3.1 General

The Data Transcript commands are divided into different chapters depending on which subfile in the loading sequence they belong to.

All subfiles that are affected by the function Handover are mentioned in this document.

For the SAEs, the NI parameter values are typical values calculated in AI.

3.2 Subfile 10000 - Size Alteration Event, APT


SAAII:SAE=274, NI= 3;

! Number of neighbouring MSC'S. EXT: min: 1 MTRAN (M) ! ! max: - MNMSCD ! ! RED: min: 1 MHO ! ! max: - MHOC ! ! MHIC ! ! ----------------------------------------------- ------------ ! SAAII:SAE=500, NI= 77, BLOCK=MHIC; ! Expected number of incoming EXT.min: 1 ! ! handover calls during 60 seconds. max:500 ! ! Same value as for MHOC (SAE 500) RED.min: 1 ! ! max:- ! ! ------------------------------------------------ --------- ! SAAII:SAE=500, NI= 77, BLOCK=MHOC; ! Expected number of outgoing EXT.min: 1 ! ! handover calls during 60 seconds. max:500 ! ! Same value as for MHIC (SAE 500) RED.min: 1 ! ! max:- ! ! ------------------------------------------------ --------- ! SAAII:SAE=500, NI= 16, BLOCK=MHOMH; ! Number of individuals. EXT.min:1 ! ! Recommended number of ind. is the max:500 ! ! sum of MHIC and MHOC ind. divided RED.min: ! ! by 10. max:- ! ! ------------------------------------------------ --------- ! SAAII:SAE=500, NI= 37, BLOCK=MHOAP; ! Number of task indivi- EXT.min: 1 ! ! duals, when SAE=500. max:500 ! ! RED.min: 1 ! ! The recommended number max:500 ! ! of task individuals is ! ! the sum of MHIC (SAE=500) ! ! and MHOC (SAE=500) indivi- ! ! duals multiplied with the amount ! ! of traffic using MAP V1. ! ! ------------------------------------------------ --------- ! SAAII:SAE=500, NI= 115, BLOCK=MHOAP2; ! Number of task indivi- EXT.min: 1 ! ! duals, when SAE=500. max:500 ! ! RED.min: 1 ! ! The recommended number max:500 ! ! of task individuals is ! ! the sum of MHIC (SAE=500) ! ! and MHOC (SAE=500) indivi- ! ! duals multiplied with the amount ! ! of traffic using MAP V2. ! ! ------------------------------------------------ --------- ! SAAII:SAE=500, NI= 500, BLOCK=MRRM; SAAII:SAE=500, NI=1000, BLOCK=MRRM; SAAII:SAE=500, NI=1500, BLOCK=MRRM; SAAII:SAE=500, NI=2000, BLOCK=MRRM; SAAII:SAE=500, NI=2500, BLOCK=MRRM; SAAII:SAE=500, NI=2706, BLOCK=MRRM; ! Number of BSSMAP transactions EXT.min: 1 ! ! allowed for the MSC. max:500 ! ! RED.min: 1 ! ! Recommended number of task max:500 ! ! individuals is the expected ! ! maximum number of simultaneous !

! setup transactions. ! ! ! ! The number shall be equal at ! ! least to the number of ! ! individuals for SAE=500 in ! ! block MSCCO. ! ! ------------------------------------------------ --------- ! SAAII:SAE=500, NI= 31, BLOCK=MHO; ! Number of task individuals. EXT.min:1 ! ! Recommended number of ind. is max:500 ! ! the max number of HO performed RED.min:1 ! ! during 5 s. max:- ! ! ------------------------------------------------ --------- ! SAAII:SAE=500, NI= 58, BLOCK=MTOS; ! Number of individuals sending EXT.min:1 ! ! of the ringing control tone max:500 ! ! towards A-subscriber after an RED.min:1 ! ! inter-MSC handover of the max: ! ! B-subscriber before the B-subscriber ! ! answers and if the Interworking Unit ! ! ETC is not u-law adapted. ! ! Recommended value: ! ! Number of individuals needed to ! ! support the offered traffic ! !TR (erlang) with 0.001 loss probability ! ! ! ! PHOT * (1 - PDATA) * HTT ! ! + PDATA * PMTOSD * HTD ! ! TR (erlang) = ------------------------ * NSUB * BHCT * RH ! ! 3600 ! ! ! ! BHCT Average number of mobile-terminated busy hour ! ! calls per subscriber ! ! HTD Holding time of a SAE individual for a ! ! fax or data call (seconds) ! ! HTT Average holding time of a SAE indivi dual ! ! for a terminating voice call (second s) ! ! NSUB Number of subscribers registered in the VLR ! ! PDATA Proportion of terminating calls that are fax ! ! or data calls ! ! PHOT Proportion of mobile-terminated call s in which! ! the terminating mobile performs inte r-MSC ! ! handover during call setup ! ! PMTOSD Proportion of terminating fax or dat a calls ! ! that require ringing control tone fr om MTOS ! ! RH Ratio of high load to normal load ! ! TR Traffic offered to SAE individuals ! ! ! ! Typical Values ! ! ! ! BHCT = 0. 277 HTD = 39 ! ! HTT = 20 NSUB = 100000 ! ! PDATA = 0.1 PHOT = 0.015 ! ! PMTOSD = 1 RH = 1.2 ! ! ------------------------------------------------ --------- ! SAAII:SAE=500, NI= 77, BLOCK=MHIC; ! Number of task individuals, EXT.min: 1 ! ! when SAE=500. max:500 ! ! Recommended value: RED.min: 1 ! ! Expected maximum number of max:- ! ! incoming handover calls !

! during 60 seconds. ! ! ------------------------------------------------ --------- ! SAAII:SAE=501, NI= 400, BLOCK=MHO; SAAII:SAE=501, NI= 800, BLOCK=MHO; SAAII:SAE=501, NI= 960, BLOCK=MHO; ! Number of neighbouring cell EXT.min: 8 ! ! data individuals and number of max:400 ! ! cell statistics individuals. RED.min: 8 ! ! max:400 ! ! The size of the cell statistics ! ! file is one eighth that of the ! ! neighbouring cell data file. ! ! ------------------------------------------------ --------- ! SAAII:SAE=504, NI= 32, BLOCK=MHOC; ! Number of MHOC routes + 1. EXT.min: 1 ! ! max:500 ! ! RED.min: 1 ! ! max:- ! ! ------------------------------------------------ -------- ! SAAII:SAE=504, NI=5, BLOCK=MRNR; SAAII:SAE=504, NI=10, BLOCK=MRNR; SAAII:SAE=504, NI=11, BLOCK=MRNR; ! Number of Roaming and Handover EXT.min: 1 ! ! Number series, when SAE=504. max: 5 ! ! There is space for 100 Roaming RED.min: 1 ! ! and/or Handover Numbers in every max:- ! ! series except in the series ! ! which is used for statistics ! ! (a series which is used for ! ! statistics cannot have any ! ! Roaming/Handover numbers ! ! allocated to it). ! ! The Roaming Number statistics ! ! always reserves one series ! ! individual irrespective of whether ! ! statistics is used or not. ! ! If assigned, Handover Number ! ! statistics needs one series. ! ! The needed number of Roaming ! ! Number series depends on the ! ! number of Roaming Numbers to ! ! be connected. ! ! ------------------------------------------------ --------- ! !SAAII:SAE=504, NI= 0, BLOCK=MRNR1;! ! The function block MRNR1 holds the EXT.min: 1 ! ! Roaming Number series and provides max: 5 ! ! Roaming Numbers for routing of in- RED.min: 1 ! ! coming calls from GMSC to the MSC/ max:- ! ! VLR. MRNR1 also provides Handover Numbers ! ! which are used in routing of incoming calls ! ! in Inter-exchange handover. ! ! Roaming and Handover number series can be ! ! allocated per Local Access and Transport ! ! Area (LATA). CMS 40 ONLY ! ! ------------------------------------------------ --------- ! SAAII:SAE=527, NI= 333, BLOCK=MRRMH; ! Number of buffer individuals EXT.min: 1 ! ! when SAE=527. max:500 ! ! RED.min: 1 !

! max:500 ! ! ------------------------------------------------ --------- ! !SAAII:SAE=901, NI= 0, BLOCK=MRNR1;! ! The file is used to store EXT.min: ! ! MSRNS data when this series is max: ! ! connected to the local access RED.min: ! ! and transport area (LATA). max: ! ! See block MTRAN for information. CMS 40 ONLY ! ! ------------------------------------------------ --------- ! SAAII:SAE=1053, NI= 3324; ! Number of active SCCP signalling EXT.min: 1 MRRMH ! ! connections between MSC and BSC. max:50 0 ! ! RED.min: 1 ! ! max:- ! !------------------------------------------------- -----------!

3.3 Subfile 13000 - Exchange Properties


!***** INTRA-MSC HANDOVER *****! MGEPC:PROP=CAUSEINHOREQ-0; ! HANDLING OF BSSMAP CAU SE IN ! ! HANDOVER REQUEST' MESS AGE. ! ! THIS PARAMETER STATES IF BSSMAP ! ! INFORMATION ELEMENT CA USE IS TO ! ! BE SENT IN BSSMAP MESS AGE ! ! 'HANDOVER REQUEST'. ! ! THE PROPERTY IS INTROD UCED BECAUSE ! ! THE BSSMAP MESSAGE HAN DOVER REQUEST! ! IN GSM PHASE 1 DID NOT INCLUDE ! ! THE CAUSE WHICH HAS BE EN ADDED ! ! IN GSM PHASE 2 FOR DIR ECTED RETRY ! ! FUNCTION. MESSAGE HAND OVER REQUEST ! ! WOULD BE REJECTED BY G SM PHASE 1 ! ! BSCs BECAUSE OF UNEXPE CTED ! ! INFORMATION ELEMENT CA USE. ! ! PARAMETER IS MANDATORY WITH ! ! APPLICATION DEPENDENT VALUE: ! ! 0 = THE INFORMATION EL EMENT CAUSE ! ! IS PACKED IN ALL 'HAND OVER REQUEST'! ! MESSAGES TOWARDS ALL B SCS ! ! BELONGING TO THE MSC, THEY SHOULD ! ! THEN ALL BE GSM PHASE 2 COMPATIBLE ! ! IN ORDER TO ACCEPT THE PRESENCE OF ! ! INFORMATION ELEMENT CA USE IN THE ! ! RECEIVED MESSAGE. ! ! 1 = THE INFORMATION EL EMENT CAUSE ! ! IS NOT PACKED IN ANY ' HANDOVER ! ! REQUEST' MESSAGES TOWA RDS ANY BSC ! ! BELONGING TO THE MSC, EVEN IF SOME ! ! BSCS ARE GSM PHASE 2 C OMPATIBLE. ! ! IN CASE OF INTER-MSC H ANDOVER, THE ! ! MSC DOESNT KNOW THE BS Cs BELONGING! ! TO THE SURROUNDING MSC S, THEREFORE ! ! IT SENDS THE CAUSE TO THE NON- ! ! ANCHOR MSC WHICH DECI DES OR NOT TO! ! SEND THE CAUSE INFORMA TION ELEMENT ! ! TO ITS BSC. !

MGEPC:PROP=HNDRELCHINTRA-1; !Channel release in intra -MSC handover! !The parameter is optiona l. It defines! !the release of the origi nal channel ! !after expiration of the timer ! ! HNDTCMDINTRA for handov er time ! ! supervision in intra-MS C handover. ! ! 0 = Terminate the hando ver and ! ! continue the call on th e original ! ! channel. ! ! 1 = Release the origina l channel. ! ! ! !Default value = 1. The p arameter is ! !owned by the block MHO. ! MGEPC:PROP=HNDSDCCH-1; ! INTRA-MSC HANDOVER O N SIGNALLING ! ! CHANNELS. ! ! DETERMINES IF INTRA- MSC HANDOVER ! ! IS ALLOWED ON SIGNAL LING CHANNELS! ! 0 = INTRA-MSC HANDOV ER IS NOT ! ! ALLOWED ON SIGNALLIN G CHANNELS. ! ! 1 = INTRA-MSC HANDOV ER IS ALLOWED! ! ON SIGNALLING CHANNE LS. ! ! PARAMETER IS OPTIONA L WITH ! ! DEFAULT VALUE = 1. ! ! THE PARAMETER IS OWN ED BY THE ! ! BLOCK MHO. ! MGEPC:PROP=HNDSDCCHTCH-1; ! INTRA-MSC HANDOVER F ROM ! ! SIGNALLING TO TRAFFI C CHANNEL. ! ! DETERMINES IF HANDOV ER IS ALLOWED! ! FROM SIGN TO TRAFFIC CHANNEL: ! ! 0 = HANDOVER IS NOT ALLOWED FROM ! ! SIGNALLING TO TR AFFIC CHANNEL! ! 1 = HANDOVER IS ALLO WED FROM ! ! SIGNALLING TO TR AFFIC CHANNEL! ! PARAMETER IS OPTIONA L WITH ! ! DEFAULT VALUE = 1. ! ! THE PARAMETER IS OWN ED BY THE ! ! BLOCK MHO. ! MGEPC:PROP=HNDTCMDINTRA-15; ! TIME SUPERVISION IN INTRA-MSC ! ! HANDOVER(T102 IN GSM 03.09). THE ! ! TIME BETWEEN THE HAN DOVER COMMAND! ! AND HANDOVER COMPLET E' MESSAGES ! ! IN INTRA-MSC HANDOVE R. THE VALUE ! ! IS SPECIFIED IN SECO NDS (STEPS ! ! ON 1 S). PARAMETER I S OPTIONAL ! ! WITH DEFAULT VALUE = 15. ! ! THE PARAMETER IS OWN ED BY THE ! ! BLOCK MHO. ! MGEPC:PROP=HNDTGSOPINTRA-80; ! SWITCHING TIME IN IN TRA-MSC ! ! HANDOVER. TIME SUPER VISION OF THE! ! SWITCHING MOMENT OF THE GS, ! ! STARTED AT SENDING O F HANDOVER ! ! COMMAND IN INTRA-MSC HANDOVER. ! ! WHEN THE TIMER EXPIR ES THE PATH ! ! IN GS IS CHANGED TO THE NEW SIDE.! ! THE VALUE IS SPECIFI ED IN MILLI- !

! SECONDS WITH 20 MS I NTERVALS. ! ! PARAMETER IS OPTIONA L WITH ! ! DEFAULT VALUE = 80. ! ! PARAMETER VALUE 0 ME ANS ! ! NO SUPERVISION. ! ! THIS PARAMETER IS ME ANINGFUL ! ! AND IT CAN BE CHANGE D ONLY IF THE! ! TIME SUPERVISION IS USED TO ! ! DEFINE THE OPERATION POINT OF THE! ! GROUP SWITCH. ! !***** INTER-MSC HANDOVER IN ANCHOR MSC *****! MGEPC:PROP=HOMAPVERSION-2; ! 1-2 ! ! Default MAP version to be u sed by the ! ! anchor MSC in the outgoing handover ! ! dialogue towards the non-an chor MSC. ! ! This version is used for th e Application! ! Context name HANDOVERCONTRO LCONTEXT when! ! establishing the dialogue. ! ! 1 = dialogue initiated by a nchor MSC in ! ! MAP V1 or Ericsson MAP V2 d epending om ! ! parameter MAPVHO above. ! ! 2 = dialogue firstly initia ted by anchor! ! MSC in MAP V2 and if the no n-anchor MSC ! ! cannot handle MAP V2 a new attempt is ! ! made in MAP V1 or Ericsson MAP V2 ! ! depending on parameter MAPV HO above ! ! (fallback). ! ! Parameter is optional with default ! ! value = 2. ! ! The parameter is owned by t he block MHO.! MGEPC:PROP=MAXNUMHOV1-100; ! 0-655335 ! ! Max number of outgoing hando ver dialogue ! ! attempts allowed in MAP V1 o r Ericsson ! ! MAP V2 towards non-anchor MS C when ! ! HOMAPVERSION above indicates MAP V2 ! ! should be used. ! ! This parameter is only meani ngful if ! ! HOMAPVERSION indicates MAP V 2 should be ! ! used in outgoing handover di alogue setup ! ! Whereas the parameter is com mon to all ! ! MSCs there is one counter pe r MSC. The ! ! counter starts after the fir st fallback ! ! is made. When the specified limit is ! ! reached the counter is reset to zero and ! ! the current attempt is made in MAP V2. ! ! Parameter is optional with d efault ! ! value = 100. Parameter value 0 means ! ! outgoing dialogue will alway s be ! ! attempted in MAP V2. ! ! The parameter is owned by th e block MHO. ! MGEPC:PROP=HNDSDCCHINTO-1; ! 0-1 ! ! Outgoing inter-MSC handover on signalling! ! channels in anchor MSC. ! ! Determines if outgoing inter -MSC handover! ! is allowed on signalling cha nnels: ! ! Only used when MAP V2. ! ! 0 = Outgoing inter-MSC hando ver is not !

! allowed on signalling ch annels. ! ! 1 = Outgoing inter-MSC hando ver allowed ! ! on signalling channels. ! ! Parameter is optional with d efault ! ! value = 1. ! ! The parameter is owned by th e block MHO. ! MGEPC:PROP=HNDBEFOREBANSW-0; ! HANDOVER BEFORE B- ANSWER. ! ! PARAMETER INDICATES IF INTER-MSC ! ! HANDOVER IS ALLOWED BEF ORE ANSWER ! ! FROM B-SUBSCRIBER. ! ! 0 = NOT ALLOWED. ! ! 1 = HANDOVER ALLOWED. ! ! PARAMETER IS OPTIONAL W ITH ! ! DEFAULT VALUE = 0. ! ! THE PARAMETER IS OWNED BY THE ! ! BLOCK MHO. ! MGEPC:PROP=HNDTGSOPBASIC-80; ! SWITCHING TIME IN BASIC HANDOVER. ! ! TIME SUPERVISION OF THE SWITCHING ! ! MOMENT OF THE GS, START ED AT SENDING ! ! OF HANDOVER COMMAND IN BASIC HANDOVER.! ! WHEN THE TIMER EXPIRES THE PATH ! ! IN GS IS CHANGED TO THE NEW SIDE. ! ! THE VALUE IS SPECIFIED IN MILLISECONDS! ! WITH 20 MS INTERVALS. ! ! PARAMETER IS OPTIONAL W ITH ! ! DEFAULT VALUE = 80. PAR AMETER VALUE 0 ! ! MEANS NO SUPERVISION. ! ! THIS PARAMETER IS MEANI NGFUL ! ! AND IT CAN BE CHANGED O NLY IF THE ! ! TIME SUPERVISION IS USE D TO DEFINE ! ! THE OPERATION POINT OF THE GROUP ! ! SWITCH. ! ! THE PARAMETER IS OWNED BY THE BLOCK ! ! MHO. ! MGEPC:PROP=HNDTGSOPSUB-140; ! SWITCHING TIME IN SUBSE QUENT HANDOVER.! ! TIME SUPERVISION OF THE SWITCHING ! ! MOMENT OF THE GS, START ED AT SENDING ! ! OF MESSAGE 'SUBSEQUENT HANDOVER ! ! ACKNOWLEDGEMENT' IN SUB SEQUENT ! ! HANDOVER BACK TO ANCHOR MSC ! ! WHEN THE TIMER EXPIRES THE PATH IN GS ! ! IS CHANGED TO THE NEW S IDE. ! ! THE VALUE IS SPECIFIED IN MILLISECONDS! ! WITH 20 MS INTERVALS. ! ! PARAMETER IS OPTIONAL W ITH ! ! DEFAULT VALUE = 140. ! ! PARAMETER VALUE 0 MEANS NO SUPERVISION! ! THIS PARAMETER IS MEANI NGFUL ! ! AND IT CAN BE CHANGED O NLY IF THE ! ! TIME SUPERVISION IS USE D TO DEFINE ! ! THE OPERATION POINT OF THE GROUP ! ! SWITCH. ! ! THE PARAMETER IS OWNED BY THE BLOCK ! ! MHO. ! MGEPC:PROP=HNDTGSOPSUBTH-140; ! SWITCHING TIME IN SUBSE QUENT HAND- ! ! OVER TO THIRD MSC. !

! TIME SUPERVISION OF THE SWITCHING ! ! MOMENT OF THE GS, START ED AT SENDING! ! OF MESSAGE 'SUBSEQUENT HANDOVER ! ! ACKNOWLEDGEMENT' IN SUB SEQUENT ! ! HANDOVER TO A THIRD MSC . ! ! WHEN THE TIMER EXPIRES THE PATH IN ! ! GS IS CHANGED TO THE NE W SIDE. ! ! THE VALUE IS SPECIFIED IN ! ! MILLISECONDS WITH 20 MS INTERVALS. ! ! PARAMETER IS OPTIONAL W ITH ! ! DEFAULT VALUE = 140. ! ! PARAMETER VALUE 0 MEANS NO SUPER- ! ! VISION. THIS PARAMETER IS MEANINGFUL! ! AND IT CAN BE CHANGED O NLY IF THE ! ! TIME SUPERVISION IS USE D TO DEFINE ! ! THE OPERATION POINT OF THE GROUP ! ! SWITCH. ! ! THE PARAMETER IS OWNED BY THE ! ! BLOCK MHO. ! MGEPC:PROP=HNDRELCHBASIC-1; ! CHANNEL RELEASE IN BASI C HANDOVER. ! ! PARAMETER DEFINES THE R ELEASE OF THE! ! ORIGINAL CHANNEL AFTER EXPIRATION OF! ! THE TIMER HNDTCMDBASIC FOR HANDOVER ! ! TIME SUPERVISION IN BAS IC HANDOVER. ! ! 0 = TERMINATE THE HANDO VER AND ! ! CONTINUE THE CALL ON TH E ORIGINAL ! ! CHANNEL. ! ! 1 = RELEASE THE ORIGINA L CHANNEL. ! ! PARAMETER IS OPTIONAL W ITH DEFAULT ! ! VALUE = 1. ! ! THE PARAMETER IS OWNED BY THE ! ! BLOCK MHO. ! MGEPC:PROP=HNDRELCHSUB-0; ! CHANNEL RELEASE IN SUBS EQUENT ! ! HANDOVER. PARAMETER DEF INES THE ! ! RELEASE OF THE ORIGINAL CHANNEL ! ! AFTER EXPIRATION OF THE TIMER ! ! HNDTCMDSUB FOR HANDOVER TIME ! ! SUPERVISION IN SUBSEQUE NT HANDOVER ! ! BACK TO ANCHOR MSC. ! ! 0 = TERMINATE THE HANDO VER AND ! ! CONTINUE THE CALL ON TH E ORIGINAL ! ! CHANNEL. ! ! 1 = RELEASE THE ORIGINA L CHANNEL. ! ! PARAMETER IS OPTIONAL W ITH DEFAULT ! ! VALUE = 0. ! ! THE PARAMETER IS OWNED BY THE ! ! BLOCK MHO. ! MGEPC:PROP=HNDRELCHSUBTH-0; ! CHANNEL RELEASE IN SUBS EQUENT ! ! HANDOVER TO THIRD MSC. ! ! PARAMETER DEFINES THE R ELEASE OF THE! ! ORIGINAL CHANNEL AFTER EXPIRATION OF! ! THE TIMER HNDTCMDSUBTH FOR HANDOVER ! ! TIME SUPERVISION IN SUB SEQUENT ! ! HANDOVER TO A THIRD MSC . ! ! 0 = TERMINATE THE HANDO VER AND ! ! CONTINUE THE CALL ON TH E ORIGINAL ! ! CHANNEL. ! ! 1 = RELEASE THE ORIGINA L CHANNEL. !

! PARAMETER IS OPTIONAL W ITH DEFAULT ! ! VALUE = 0. ! ! THE PARAMETER IS OWNED BY THE ! ! BLOCK MHO. ! MGEPC:PROP=HNDTCMDBASIC-15; ! TIME SUPERVISION IN BAS IC HANDOVER ! ! (T103 IN GSM 03.09). ! ! THE TIME BETWEEN THE 'H ANDOVER COM- ! ! MAND' AND 'SEND END SIG NAL' MESSAGES! ! IN BASIC HANDOVER. ! ! THE VALUE IS SPECIFIED IN SECONDS ! ! (STEPS ON 1S). ! ! PARAMETER IS OPTIONAL W ITH DEFAULT ! ! VALUE = 15. ! ! THE PARAMETER IS OWNED BY THE ! ! BLOCK MHO. ! MGEPC:PROP=HNDTCMDSUB-5; ! TIME SUPERVISION IN SUB SEQUENT ! ! HANDOVER (T104 IN GSM 0 3.09). ! ! THE TIME BETWEEN THE ME SSAGES ! ! 'SUBSEQUENT HANDOVER AC KNOWLEDGEMENT! ! AND 'HANDOVER COMPLETE' ! ! IN SUBSEQUENT HANDOVER BACK TO ! ! ANCHOR-MSC. ! ! THE VALUE IS SPECIFIED IN SECONDS ! ! (STEPS ON 1 S). ! ! PARAMETER IS OPTIONAL W ITH DEFAULT ! ! VALUE = 5. ! ! THE PARAMETER IS OWNED BY THE ! ! BLOCK MHO. ! MGEPC:PROP=HNDTCMDSUBTH-5; ! TIME SUPERVISION IN SUB SEQUENT ! ! HANDOVER TO THIRD MSC. ! ! THE TIME BETWEEN THE ME SSAGES ! ! 'SUBSEQUENT HANDOVER AC KNOWLEDGEMENT! ! AND 'SEND END SIGNAL' I N HANDOVER ! ! TO A THIRD MSC. ! ! THE VALUE IS SPECIFIED IN SECONDS ! ! (STEPS ON 1 S). ! ! PARAMETER IS OPTIONAL W ITH DEFAULT ! ! VALUE = 5. ! ! THE PARAMETER IS OWNED BY THE ! ! BLOCK MHO. ! !***** INTER-MSC HANDOVER IN NON-ANCHOR MSC *****! MGEPC:PROP=HNDSDCCHINTI-1; ! 0-1 ! ! Incoming inter-MSC hand over on ! ! signalling channels. ! ! Determines if incoming inter-MSC ! ! handover is allowed on signalling ! ! channels. ! ! Only valid if MAP V2. ! ! 0 = Incoming inter-MSC handover is ! ! not allowed on signalli ng channels. ! ! 1 = Incoming inter-MSC handover is ! ! allowed on signalling c hannels. ! ! Parameter is optional w ith default ! ! value = 1. ! ! The parameter is owned by the !

! block MHIC. ! MGEPC:PROP=HNDRELCHSUBNON-1; ! CHANNEL RELEASE IN SUBS EQUENT ! ! HANDOVER IN NON-ANCHOR MSC. ! ! PARAMETER DEFINES THE R ELEASE ! ! OF THE ORIGINAL CHANNEL AFTER ! ! EXPIRATION OF TIMER HND TCMDSUBNON ! ! FOR HANDOVER TIME SUPER VISION IN ! ! SUBSEQUENT HANDOVER IN NONANCHOR MSC! ! 0 = TERMINATE THE HANDO VER AND ! ! CONTINUE THE CALL ON TH E ORIGINAL ! ! CHANNEL. ! ! 1 = RELEASE THE ORIGINA L CHANNEL. ! ! PARAMETER IS OPTIONAL W ITH DEFAULT ! ! VALUE = 1. ! ! THE PARAMETER IS OWNED BY THE ! ! BLOCK MHIC. ! MGEPC:PROP=HNDTCMDBASNON-20; ! TIME SUPERVISION IN BAS IC HANDOVER ! ! IN NON-ANCHOR MSC. ! ! THE TIME BETWEEN THE PS TN MESSAGE ! ! 'ADDRESS COMPLETE' AND BSSAP MESSAGE! ! HANDOVER COMPLETE IN BA SIC HANDOVER ! ! IN NON-ANCHOR MSC. ! ! AFTER EXPIRATION OF THI S TIMER THE ! ! HANDOVER IS TERMINATED AND THE ! ! RESERVED CHANNEL IS REL EASED. ! ! THE VALUE IS SPECIFIED IN SECONDS ! ! (STEPS ON 1 S). ! ! PARAMETER IS OPTIONAL W ITH DEFAULT ! ! VALUE = 20. ! ! THE PARAMETER IS OWNED BY THE ! ! BLOCK MHIC. ! MGEPC:PROP=HNDTCMDSUBNON-20; ! TIME SUPERVISION IN SUB SEQUENT ! ! HANDOVER IN NON-ANCHOR MSC. ! ! THE TIME BETWEEN 'HANDO VER COMMAND' ! ! AND 'END SIGNAL' MESSAG ES IN ! ! SUBSEQUENT HANDOVER IN NONANCHOR MSC! ! AFTER EXPIRATION OF THI S TIMER THE ! ! HANDOVER IS TERMINATED AND THE ! ! RESERVED CHANNEL IS REL EASED. ! ! THE VALUE IS SPECIFIED IN SECONDS ! ! (STEPS ON 1 S). ! ! PARAMETER IS OPTIONAL W ITH DEFAULT ! ! VALUE = 20. ! ! THE PARAMETER IS OWNED BY THE ! ! BLOCK MHIC. ! !***** ROAMING AND HANDOVER NUMBER ALLOCATION (MSRN ) *****! MGEPC:PROP=MSRNHOMETHOD-2; ! ROAMING AND HANDOVER NU MBER ! ! ALLOCATION METHOD. ! ! DEFINES THE ALLOCATION METHOD OF ! ! ROAMING AND HANDOVER NU MBERS USED ! ! IN THE MSC/VLR. ! ! 0 = ROAMING AND HANDOVE R NUMBERS ARE! ! ALLOCATED FROM THE SAME NUMBER ! ! SERIES. ! ! 1 = ROAMING AND HANDOVE R NUMBERS ARE!

! ALLOCATED FROM THE SEPARATE ! ! NUMBER SERIES. ! ! 2 = ROAMING NUMBER ALLO CATION IS ! ! PERFORMED BASED ON THE LOCATION ! ! AREA WHERE THE MS I S ROAMING AND! ! THE HANDOVER NUMBER S ARE ! ! ALLOCATED FROM SEPA RATE NUMBER ! ! SERIES RESERVED FOR HANDOVER USE! ! ONLY. ! ! THE VALUE 2 IS NOT SUPP ORTED ! ! IN ALL MARKETS: ! ! - VALUE 2 IS APPLICABLE ON MARKET ! ! HAVING THE FUNCTION ' ALLOCATION OF! ! ROAMING NUMBERS PER L OCATION AREA ! ! IN MSC/VLR'. ! ! A CORRESPONDING FAULT C ODE IS ! ! PRINTED OUT WHEN TRYING TO DEFINE ! ! THESE VALUES IN THE EXC HANGE ! ! NOT SUPPORTING THESE FU NCTIONS. ! ! THE USED METHOD CAN BE CHANGED ! ! TO ANOTHER ONLY IF THE ROAMING AND ! ! HANDOVER NUMBER ALLOCAT ION HAS BEEN ! ! INHIBITED FOR ALL NUMBE R SERIES ! ! ROUTES. A FAULT CODE IN DICATING DATA! ! MISMATCH IS PRINTED OUT IF THE ! ! INHIBITION HAS NOT BEEN PERFORMED ! ! BEFORE ATTEMPTING TO CH ANGE THE ! ! ALLOCATION METHOD. SEE OPERATIONAL ! ! INSTRUCTION: MT ROAMING AND HANDOVER! ! NUMBER ADMINISTRATION. ! ! PARAMETER IS OPTIONAL W ITH ! ! DEFAULT VALUE = 0. ! ! THE PARAMETER IS OWNED BY THE BLOCK ! ! MRNR. ! MGEPC:PROP=MSRNHNDLIMIT-0; ! NUMBERS RESERVED FOR HA NDOVER. ! ! THE PARAMETER IS VALID ONLY WHEN ! ! THE SAME POOL (ROUTES) IS USED FOR ! ! BOTH ROAMING AND HANDOV ER NUMBER ! ! ALLOCATION. IT INDICATE S, IN PERCENT! ! OF THE TOTAL AMOUNT OF CONNECTED ! ! NUMBERS, THE MINIMUM AM OUNT OF ! ! NUMBERS THAT MUST BE ID LE TO ALLOW ! ! ALLOCATION OF ROAMING N UMBERS. ! ! WHEN THE AMOUNT OF IDLE NUMBERS ! ! DROPS BELOW THIS LIMIT, THE NUMBERS ! ! ARE TEMPORARILY RESERVE D FOR HAND- ! ! OVER NUMBER REQUESTS ON LY. IF IN ! ! THIS SITUATION ROAMING NUMBERS ARE ! ! REQUESTED FOR THE MOBIL E TERMINATING! ! CALLS, THEN ROAMING NUM BER ! ! CONGESTION IS INDICATED TO THE HLR. ! ! THE PARAMETER IS OPTION AL WITH ! ! DEFAULT VALUE = 0. ! ! THE PARAMETER IS OWNED BY THE ! ! BLOCK MRNR. ! MGEPC:PROP=MSRNHNDTIME-100; ! VALIDITY TIME OF ALLOCA TED HANDOVER ! ! NUMBER. ! ! IF THE TIMER EXPIRES TH E ALLOCATED ! ! HANDOVER NUMBER AND NEW RADIO ! ! RESOURCES ARE RELEASED. !

! THE VALUE IS SPECIFIED IN SECONDS ! ! (STEPS ON 5 S). ! ! PARAMETER IS OPTIONAL W ITH DEFAULT ! ! VALUE = 100. ! ! THE PARAMETER IS OWNED BY THE ! ! BLOCK MRNR. !

3.4 Subfile 15300 - Route Characteristics


!**** ROUTES FOR INTER MSC HANDOVER ****! EXROI:R=HOVER0,DETY=MRNR; ! ROUTE FOR HAN DOVER ONLY ! EXROI:R=1MHOC, DETY=MHOC, FNC=1; ! ROUTE FOR OUT GOING ! ! HO CALLS ! EXRBC:R=1MHOC, BO=8, RO=4; EXROI:R=2MHOC1, DETY=MHOC, FNC=2; ! ROUTE FOR INC OMING MOBILE ! ! ORIGINATED CA LLS FROM MSC2! ! I.E. CALL PUT ON HOLD AND ! ! A SECOND CALL IS INITIATED! ! BO FROM MGISI !

3.5 Subfile 15450 - Internal Number-Series / Roaming & HO Numbers


!***********************************************! !**** DEFINITION OF ROAMING/HANDOVER NUMBER ****! !***********************************************! MGRSI:R=HOVER0, MSRNS= 46 70 757 03; MGRSC:MSRNS= 46 70 757 03, USAGE=HONPERM; !***********************************************! !**** CONNECTION OF ROAMING/HANDOVER NUMBER ****! !***********************************************! MGRNI:MSRN= 46 70 757 0300 && 46 70 7570399;

3.6 Subfile 15600 - B-Number Analysis


!**** ROAMING/HANDOVER NUMBERs ****! ANBSI:B=8-467075, BNT=4, M=2, F=9; !TERM INATING ! !ROAM ING AND ! !HAND OVER NUMBERS ! ANBSI:B=8-467076, BNT=1, L=11, D=5-0, CC=3, RC=25;! MSRN TO MSC2! ! HANDOVER # !

!**** OWN HANDOVER NUMBERs ****! ANBSI:B=9-70 757 03, MTE, D=5-0, L=9, CC=3;

3.7 Subfile 77100 - Inter-Msc Handover


!****************************! !**** INTER MSC HANDOVER ****! !****************************! !***** DEFINITION OF NEIGHBOURING MSCS *****! MGNMI:MSC=MSC2, MSCADDR=4-46 70 764 0000, R=2M HOC1; !***** INITIATION OF OUTER CELLS *****! MGOCI:MSC=MSC2, CELL=STHLM2A, CGI=234-01-0300 -00011;

4 Miscellaneous Information

4.1 Class

The function is Standard - Basic.

5 References 21/155 16-ANT 294 01/1 Uen A

Roaming and handover number provision in MSC/VLR

31/155 16-ANT 293 01/1 Uen A Handover

33/155 16-ANT 293 01/1 Uen A Inter-MSC handover call setup and supervision in anchor MSC

4/155 17-ANT 293 01/1 Uen A Inter-MSC handover in non-anchor MSC/VLR

2/155 42-CNT 219 1618 Uen A Mobile telephony data: Roaming and handover number series

2/155 18-1/apt 210 25/2 Uen PA10 Mobile telephony data: Changeable exchange adaption

Documents

Hand Over