OWG003407 Hand Over Analysis and Process: 5 January 2007

5 January 2007 Internal use only
OWG003407 Hand Over

Analysis and Process
1.0 www.huawei.com
HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential

HUAWEI TECHNOLOGIES CO., LTD.
Contents
Introduction to HandOver
Role of MSC-A
Role of MSC-B
Role of 3G MSC-A
Role of 3G MSC-B
Procedures for Intra MSC HO
Procedures for Intra 3G MSC HO
Procedures for Inter MSC HO
Procedures for Inter 3G MSC HO
HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 2
Introduction to HandOver
• The purpose of the HO procedures is to ensure that the
connection to the MS/UE is maintained as it moves from one
Cell or Radio network to the other.
• The various types of Handovers that are possible, taking
into consideration the GSM and the UMTS networks are:
 Handover between Base Stations connected to the same
MSC, termed Intra MSC handover.
 Handover between Radio Network Subsystems connected to
the same 3G_MSC, termed as Intra 3G_MSC handover. This
also include inter-system handover between RNS and BSS if
the 3G_MSC supports the A-interface.

Types of HO – Contd.
• Handover between Base Stations connected to different MSCs,
termed as inter MSC HO. This can be sub-divided into three sub
categories
 Basic inter-MSC HO
 Subsequent inter-MSC HO
 Subsequent inter-MSC Handback.
• Handover between Radio Network Subsystems connected to

different 3G_MSCs, termed as inter-3G_MSC handover/relocation. This
can be divided into three sub categories
 Inter 3G_MSC HO from UMTS to GSM.
 Inter 3G_MSC HO from GSM to UMTS.
 Inter 3G_MSC relocation, where the UE is relocated from
3G_MSC A to 3G_MSC B.

Introduction to the Terminology Used
 Basic Handover is the procedure where the UE is

handed from a controlling (3G)MSC-A to another (3G)MSC-B.
 Subsequent Handover is the procedure where the UE is

handed from (3G)MSC-B to a third (3G)MSC-B’.
 Subsequent Handback is the procedure where the UE is

handed from (3G)MSC-B back to (3G)MSC-A.
 Limitation: Inter-MSC HO does not support Call-

reestablishment.

Why HandOver?
 Handover may be initiated by the network based on the RF criteria
as measured by the MS or the network and the traffic criteria.
 The RF criteria include
 Signal level
 Connection quality
 Power level
 Propagation Delay
 The Traffic criteria include
 Current traffic loading per cell
 Interference levels
 Maintenance requests

Role of MSC-A
 In the Intra-MSC HO case, MSC-A controls the call, MM and the RR
- during the call, before, and after an intra-MSC HO. When BSSAP
procedures are to be performed, they are initiated by MSC-A.
 In the inter-MSC HO case, MSC-A controls the call and MM during

the call, before and after the basic or subsequent HO. When BSSAP
procedures related to dedicated resources have to be performed
towards the MS, they are initiated by MSC-A. The MSC-A, MSC-B
interface works as MSC-BSS interface for a subset of BSSMAP
procedures.

Role of MSC-A Contd..
 During a basic HO case, MSC-A initiates and controls all the HO
procedures from it’s initiation to it’s completion.
 During a subsequent HO back to MSC-A, MSC-A acts as BSS towards

MSC-B, which controls the HO procedure until it’s termination in MSC-A.
 During a subsequent HO to a third MSC-B’, MSC-A works towards

MSC-B’ as described in basic HO and towards MSC-B as described in
subsequent HO back to MSC-A. This typically means, tearing down the
hand-shake with MSC-B and establishing a new one with MSC-B’ (almost
at the same time).

Role of MSC-A Contd..
 During a basic inter-system HO case, MSC-A initiates and controls
all the HO related procedures - from it’s initiation until it’s completion.
 During a subsequent inter-system HO back to MSC-A, MSC-A acts

as a BSS towards 3G_MSC-B, which controls the HO procedure until
the termination in MSC-A.
 During a subsequent inter-system HO to a third 3G_MSC-B’, MSC-A

works towards 3G_MSC-B’ as described in basic HO and towards
3G_MSC-B as described in subsequent HO back to MSC-A.

Functional Composition of MSC-A
B’
Signalling 2 Call
functions Control B’’
Procedures
MSC-A
B’’’
y
A’
B’’ 1 BSC/MSC x 3 Handover
(MS/BSC) Control
A’’ Procedures Procedures
B’’ MSC-A MSC-A
z
4 MAP
Procedures C
MSC-A
Switching control
Switching B’
5 Switch
A’ functions
and B’’
B’’ Handover
A’’ Device
B’’ MSC-A B’’’

Functional Composition of MSC-A Contd.
MSC-A can be realized as having five functional components

as described in the above figure
BSC/MSC Procedure
Call Control Procedures
Handover control Procedures
MAP control Procedures
Switch and Handover Device.
Interface A’ is the interface to the old BSS, whereas interface

A” is the interface to the new BSS.

Interface B’ is used for normal call control procedures.
When a basic HO from MSC-A to MSC-B has to be performed or

for an inter-system, basic HO, interface B” is employed to
provide a signaling and CC mechanism to (3G)MSC-B.
When a subsequent HO to MSC-B’ has to be performed or for

an inter-system subsequent HO to 3G_MSC-B’, interface B’”
is employed.

Handover control procedures provide the overall control of HO

and interworking between the internal interfaces.
MAP Procedures is responsible for controlling the exchange of

MAP messages between MSCs during an inter-MSC HO, or
during an inter MSC, inter-system HO.
The Switch and HO device is responsible for connecting the new

path into the network via the interface B’.

States of HO Device
A’ B’
A’’
a) Intra-M SC Handover case.
A’ B’
B’’
b) Basic Handover case and handover of MS to MS call in the same MSC.
B’
B’’
B’’’
c) Subsequent Handover case
NOTE: In a) and b) A’ is released after handover;

In c) B’’ is released after handover.

States of HO device Contd.
Resulting Connection
Intermediate
Case Initial Connection Successful Unsuccessful
Connection
Procedure Procedure
Fig 2a B’ to A’ B’ to A’ and A” B’ to A’ B’ to A’
Fig 2b B’ to A’ B’ to A’ and B” B’ to B” B’ to A’
Fig 2c B’ to B” B’ to B” and B’” B’ to B’” B’ to B”

Role of MSC-B
In the intra-MSC handover case, MSC-B keeps control of the whole
intra-MSC handover procedure.
MSC-B notifies (3G)MSC-A of the successful intra-MSC HO

completion by using the A_HO_PERFORMED message.
In the inter MSC HO case, the role of MSC-B (MSC-B’) is only to

provide the radio resource control within it’s area.
MSC-B will do some processing on the BSSMAP message received

on the E/A interface, whereas it relays the DTAP information
transparently between the A and the E interface.

Functional Composition of MSC-B
The functional composition of MSC-B is essentially the same as that
of MSC-A. However, there are some differences.
BSC/MSC Procedures are used to control the signaling between the
MSC, BSC and the MS. Interface A” is the connection to the new
BSC, when an intra-MSC HO takes place.
Call Control Procedures are used for normal call control and
signaling to MSC-A or 3G_MSC-A in case of inter-system, inter-
MSC HO.
HO Control Procedures provide the overall control of the HO
procedures.
MAP Procedures are responsible for controlling the exchange of MAP
messages between MSC-A, or 3G_MSC-A, and MSC-B and for
signaling to the VLR in MSC-B.

Functional Composition of MSC-B Contd.
Signalling 2 Call
Procedures
MSC-B
y
A’
B’’ 1 BSC/MSC x 3 Handover
(MS/BSC) Control
A’’ Procedures Procedures
B’’ MSC-B MSC-B
z
4 MAP
Procedures C
MSC-B
Switching control
Switching
A’ functions 5
Switch B’’
B’’ MSC-B
A’’
B’’

Role of 3G_MSC-A
In the intra-3G_MSC HO case, the 3G_MSC controls the call, MM
and the RR before, during and after an Intra-3G_MSC
HO/relocation. When RANAP/BSSMAP procedures have to be
performed, they are initiated and driven by 3G_MSC-A.
In the inter 3G_MSC relocation case, 3G_MSC-A controls the call
and MM of the UE during the call, before, during and after a
basic or subsequent HO. The 3G_MSC-A, 3G_MSC-B interface
works as 3G_MSC-A-RNS interface for RANAP procedures. The
Direct Transfer signaling between 3G_MSC-A and MS is relayed
transparently by 3G_MSC-B.

Role of 3G_MSC-A Contd.
During the basic relocation, 3G_MSC-A initiates and controls all
the relocation procedures, from it’s initiation until it’s
completion.
For a subsequent relocation back to 3G_MSC-A, 3G_MSC-A acts

as an RNS towards 3G_MSC-B, which controls the relocation
procedure until it’s termination in 3G_MSC-A of the HO RR
allocation.
During a subsequent relocation to 3G_MSC-B’, 3G_MSC-A works

towards 3G_MSC-B’ as described in basic HO; and towards
3G_MSC-B as described in subsequent HO back to 3G_MSC-A.

During a basic inter-system UMTS to GSM HO, 3G_MSC-A initiates
and controls the HO procedures, from it’s initiation to it’s
completion.
During a subsequent inter-system UMTS to GSM HO back to

3G_MSC-A, 3G_MSC-A acts as a BSS towards MSC-B which
controls the HO procedure till the termination in 3G_MSC-A.
During a subsequent inter-system UMTS to GSM HO to a third

MSC-B’, 3G_MSC-A works towards MSC-B’ as described in
basic inter-system HO and towards MSC-B as described in
subsequent HO back to 3G_MSC-A.

During a basic inter-system GSM to UMTS HO, 3G_MSC-A initiates
and controls the HO procedures, from it’s initiation to it’s
completion.
During a subsequent inter-system GSM to UMTS HO back to

3G_MSC-A, 3G_MSC-A acts as an RNS towards MSC-B which
controls the HO procedure till the termination in 3G_MSC-A.
During a subsequent inter-system GSM to UMTS HO to a third

3G_MSC-B’, 3G_MSC-A works towards 3G_MSC-B’ as described
in basic inter-system HO and towards MSC-B as described in
subsequent HO back to 3G_MSC-A.

If 3G_MSC-A supports the optional Multicall and the UE is
engaged with multiple bearers, then
In the intra 3G_MSC relocation case, the 3G_MSC tries to relocate
all the bearers to the new RNS.
In the basic/subsequent relocation case, the 3G_MSC-A tries to
relocate all the bearers to 3G_MSC-B(B’). If 3G_MSC-B(B’) does
not support multiple bearers, then 3G_MSC-A selects one bearer
to be handed over according to the priority level defined in RAB
parameters and tries to relocate the selected bearer.
In the intra-3G_MSC inter-system UMTS to GSM HO case, and the
basic inter-system UMTS to GSM HO case, the 3G_MSC-A
selects one bearer to be handed over according the priority level
of RAB.

Functional Composition of 3G_MSC-A
The 3G_MSC-A can be realized as having five functional
components
RNC/BSC/3G_MSC Procedures
Call Control Procedures
Handover/Relocation Control Procedures
MAP Procedures
Switch and HO/Relocation device.
Interface Iu’ is the connection to the old RNC, Iu” to the new RNC, A’
is the to the old BSS and A” to the new BSS.
Interface B’ is for normal CC procedures, B”, B’” for providing
signaling and call control connection to 3G_MSC-B/3G_MSC-B’
during a basic/ subsequent relocation respectively.

Functional Composition of 3G_MSC-A Contd.
B’
Signalling 2 Call
Procedures
3G_MSC-A
B’’’
y
Iu’/A’
1 RNC/ BSC/ HO/ Rel
B’’ x 3
3G_MSC Control
Iu’’/A’’ (UE/MS/ RNC/ BSC) Procedures
B’’ Procedures 3G_MSC-A
UMSC-A
z
4 MAP
Procedures C
3G_MSC-A
Switching control
Switching B’
5 Switch
Iu’/A’ functions
and B’’
HO/Rel
Iu’’/A’’ Device
3G_MSC-A B’’’

Functional Composition of 3G_MSC-A
Contd.
Handover Control Procedures provide the overall control of the
HO/relocation procedures.
MAP Procedures are responsible for controlling the exchange of

MAP messages between 3G_MSCs during an inter-3G_MSC
HO/relocation or between 3G_MSC-A and MSC-B during an
inter-system inter-3G_MSC HO.
The Switch and HO Device is responsible for connecting the new

path into the network via interface B’.

States of HO device
Resulting Connection
Intermediate
Case Initial Connection Successful Unsuccessful
Connection
Procedure Procedure
B’ to Iu’ B’ to Iu’, Iu” B’ to Iu” B’ to Iu’
Fig 5a B’ to Iu’ B’ to Iu’, A” B’ to A’ B’ to Iu’
B’ to A’ B’ to A’, Iu” B’ to Iu” B’ to A’
Fig 5b B’ to Iu’ B’ to Iu’ and B” B’ to B” B’ to Iu’
Fig 5c B’ to B” B’ to B” and B’” B’ to B’” B’ to B”

States of HO device Contd.
Iu’/A’ B’
Iu’’/A’’
a) Intra-3G_M SC Handover/Relocation case.
Iu’ B’
B’’
b) Basic Handover/Relocation case and handover/relocation of UE/MS to
UE/MS call in the same 3G_MSC.
B’
B’’
B’’’
c) Subsequent Handover/Relocation case
NOTE: In a) and b) Iu’ is released after handover/relocation;

In c) B’’ is released after handover/relocation.

Role of 3G_MSC-B
In the intra 3G_MSC HO/relocation case, the 3G_MSC-B keeps
control of the whole HO process. It notifies (3G)MSC-A of intra-
3G_MSC-B, inter system HO and intra systems HO using
A_HO_PERFORMED message.
In the case of intra-3G_MSC-B SRNS relocation, if security
algorithms have changed:
When BSSMAP is used on the E interface, A_HO_PERFORMED is
sent.
When RANAP is used on the E-interface, LOCATION_REPORT
message is sent.
In both the cases, the selected UMTS algorithm is indicated in the
MAP_PROCESS_ACCESS_SIG_REQ message.

Role of 3G_MSC-B Contd.
In the inter-3G_MSC relocation case, the role of 3G_MSC-B
(3G_MSC-B’) is only to provide RR control within it’s area.
The release of the dedicated resources between 3G_MSC-B and

RNS is the responsibility of 3G_MSC-B and RNS and is not
controlled by 3G_MSC-A.
3G_MSC-B will do some processing on the RANAP messages

received on the E/Iu interface, whereas it will transfer the DTAP
messages transparently between Iu and the E interface.

In the inter system UMTS to GSM, inter 3G_MSC HO case, the role of
3G_MSC-B is to provide RR control within it’s area.
3G_MSC-B will do some processing on the BSSMAP information
received on the E-interface or the BSSMAP information received
on the A-interface, whereas it relays the DTAP messages
transparently between the A and the E interfaces.
In the inter system GSM to UMTS Inter-3G_MSC HO case, 3G_MSC-B
will do some processing on the BSSMAP information received on
the E-interface and on the RANAP messages on the Iu interface.
Whereas it transparently passes the DTAP information between the
E and the Iu interfaces.

If 3G_MSC-B does not support Multicall and 3G_MSC-A requests to
relocate multiple bearers, 3G_MSC-B indicates the same to
3G_MSC-A.
If 3G_MSC-B supports Multicall and the UE is engaged with multiple
bearers
In the basic HO case, 3G_MSC-B should allocate a unique HO
Number to each bearer.
In the intra 3G_MSC HO case, the 3G_MSC-B tries to relocate all the
bearers to a new RNS.
In the subsequent relocation back to the 3G_MSC-A or to another
3G_MSC-B’, 3G_MSC-B requests 3G_MSC-A to relocate all the
bearers to 3G_MSC-A or 3G_MSC-B’.
In the inter system HO case from UMTS to GSM, 3G_MSC-B selects a
bearer depending on it’s priority and tries to relocate the single
bearer to the new MSC.

Functional Composition of 3G_MSC-B
Signalling 2 Call
Procedures
3G_MSC-B
y
Iu’/A’
1 RNC/ BSC/ 3 HO/ Rel
x
3G_MSC Control
Iu’’/A’’ (UE/MS/ RNC/ BSC) Procedures
Procedures 3G_MSC-B
3G_MSC-B
z
4 MAP
Procedures C
3G_MSC-B
Switching control
Switching
Iu’/A’ functions 5
Switch B’’
3G_MSC-B
Iu’’/A’’

Functional Composition of 3G_MSC-B Contd.
The 3G_MSC-B can be realized as having five components
RNC/BSC/3G_MSC Procedures control the signaling between the
3G_MSC, RNC, BSC and the UE/MS.
Call Control Procedures are used for normal call control and
signaling to (3G)MSC-A.
HO/Relocation Procedures provide the overall control of the
HO/relocation procedures.
MAP procedures are responsible for controlling the MAP
messages between 3G_MSC-A, or MSC-A and 3G_MSC-B and
for signaling to the VLR in 3G_MSC-B.
Switching Device is responsible for connecting the circuit from
3G_MSC-A or MSC-A to RNS-B. This unit also acts as a
HO/Relocation device for Intra 3G_MSC HO/Relocation
controlled by 3G_MSC-B.

Procedures for Intra-MSC HO
MS MS
BSS-A MSC-A BSS-B
A-Handover-Required
A-Handover-Request
A-Handover-Request-Ack
A-Handover-Command
RI-HO-Command
RI-HO-Access
A-Handover-Detect
RI-HO-Complete
A-Handover-Complete
A-Clear-Command
A-Clear-Complete

Procedures for Intra-MSC HO Contd.
When the BSS currently supporting the MS determines that the MS
requires to be Handed over, it sends a A-HO-REQUIRED message
to the MSC.
A-HO-REQUIRED message contains the list of possible candidate BSSs for
HO.
When the MSC receives this message, it begins the process of handing
over the MS to a new BSS.
The MSC generates a A-HO-REQUEST to the new BSS.
The BSS allocates the required radio resources and sends A-HO-
REQUEST-ACK to MSC.
The MSC then sends A-HO-COMMAND to the old BSS.

BSS-A then sends the Radio Interface message RI_HO_COMMAND
containing a HN previously allocated by BSS-B.
The MS will then access the new radio resources with the HN as a
reference.
The number is cross checked at the new BSS and if it is the allocated
one, BSS-B sends A-HO-DETECT to MSC.
When the MS is successfully communicating with the new BSS, a RI-

HO-COMPLETE message is sent to BSS-B.
BSS-B will then send A-HO-COMPLETE to MSC.
One reception of this at MSC, it instructs the old MSC to release it’s
resources as described in the MSC.

If a failure occurs during the HO, for example A-HO-FAILURE
returned from BSS-B then MSC will terminate the HO to BSS-B.
Under these conditions, the MSC may optionally do one of these
Retry the HO to the same cell
Select the next cell in the A-HO-REQUIRED message
Await the next A-HO-REQUIRED message
Send an A-HO-REQUIRED-REJECT to BSS-A, if A-HO-COMMAND has not

already been sent.
During the period that the MS is not in communication with the

network, MSC-A shall queue all appropriate messages.

Procedures for Intra-3G_MSC HO
The intra-3G_MSC HO include
UMTS to GSM HO (A interface is supported)
GSM to UMTS HO (A interface is supported)
SRNS relocation (UMTS-UMTS HO)

UMTS-GSM Intra-3G_MSC HO
UE/MS UE/MS
RNS-A 3G_MSC-A BSS-B
Iu-Relocation-Required
A-Handover-Request
A-Handover-Request-Ack
Iu-Relocation-Command
RRC-HO-Command
RI-HO-Access
A-Handover-Detect
RI-HO-Complete
A-Handover-Complete
Iu-Release-Command
Iu-Release-Complete
UMTS to GSM HO
UMTS-GSM Intra-3G_MSC HO
When multiple bearers are supported at 3G_MSC, then it has to

do the additional functionality:
Upon receipt of IU-RELOC-REQUIRED from RNS-A, 3G_MSC-A will
select one bearer if the UE is engaged in multiple bearers.
When A-HO-REQUEST-ACK is received from BSS-B, the 3G_MSC-A

sends IU-RELOC-COMMAND, which indicates the bearers not to be
handed over as bearers to be released, to RNS-A.
When 3G_MSC-A receives A-HO-COMPLETE from BSS, 3G_MSC-A

releases all the calls via BSS-B, which has been carried by the bearers
not to be handed over, and then sends IU-RELEASE-COMMAND to
RNS-A.

GSM-UMTS Intra-3G_MSC HO
UE/MS UE
BSS-A 3G_MSC-A RNS-B
A-Handover-Required
Iu-Relocation-Request
Iu-Relocation-Request-Ack
A-Handover-Command
RI-HO-Command
Iu-Relocation-Detect
RRC-HO-Complete
Iu-Relocation-Complete
A-Clear-Command
A-Clear-Complete
GSM to UMTS
GSM-UMTS Intra-3G_MSC HO
If a failure occurs during a HO attempt, for example, A-HO-

FAILURE returned from BSS-A or IU-RELOC-FAILURE from
RNS-B, the 3G-MSC-A terminates the HO to RNS-B.
3G_MSC-A optionally may do the following
Await the next A-HO-REQUIRED message.
Send an A-HO-REQUIRED-REJECT to BSS-A, if A-HO-COMMAND has

not already been sent.

network, 3G_MSC-A queues all the appropriate messages.

Intra 3G_MSC SRNS Relocation
UE UE
RNS-A 3G_MSC-A RNS-B
Iur-SRNC-Relocation-Commit
Iu- Release-Command
Iu- Release-Complete
Basic Intra SRNS Relocation Procedure

UE UE
RNS-A 3G_MSC-A RNS-B
RR-HO-Command Detection of UE in
target RNS
RR-HO-Complete
Iu- Release-Command
Iu- Release-Complete
Basic Intra SRNS Relocation Procedure Combined with Hard Change of Radio Resources
If a failure occurs during the SRNS relocation attempt, then

3G_MSC-A will terminate the relocation to RNS-B and sends
IU-RELOCATION-PREPATION-FAILURE to RNS-A.
If IU-RELOCATION-CANCEL is received from RNS-A, then 3G-

MSC_A will terminate the relocation to RNS-B and send IU-
RELOC-CANCEL-ACK to RNS-A.

network, the 3G_MSC-A queues all the appropriate messages.

If multiple bearers are supported by 3G_MSC-A, then 3G_MSC-A

does additionally the following
Upon receipt of IU-RELOC-REQUIRED from RNS-A, 3G_MSC-A
generates an IU-RELOCATION-REQUEST message, which may include
multiple bearers to RNS-B.
When an IU-RELOC-REQUEST-ACK is received from RNS-B, 3G_MSC-A

sends IU-RELOC-COMMAND which includes the bearers that failed to
setup by the RNS-B as bearers to be released, to RNS-A.
After 3G_MSC-A receives IU-RELOC-COMPLETE message from RNS-B,

3G_MSC-A releases all the calls via RNS-B, which has been carried by
the bearers failed to setup in RNS-B, and then sends IU-RELEASE-
COMMAND to RNS-A.

Procedures for Inter-MSC HO
The inter MSC HO procedures can be divided further, taken into

consideration UMTS and GPRS networks, as well as whether
circuit is required or not and whether the 3G_MSC supports
multicall.
Basic HO requiring a Circuit between MSC-A and MSC-B
Basic HO not requiring a Circuit between MSC-A and MSC-B
Subsequent HO requiring a Circuit between MSC-A and MSC-B (Includes

Handback as well)
Subsequent HO not requiring a Circuit(Include Handback)
UMTS-GSM, GSM-UMTS, UMTS-UMTS HO, which include basic HO,

subsequent HO and subsequent Handback. This case also includes the
optional multicall.

Basic HO requiring a Circuit between MSC-A
and MSC-B
M S/BSS-A BSS-B/M S
M SC-A M SC-B VLR-B
A-HO-REQUIRED
MAP-Prep-Handover req. MAP-Allocate-Handover-Number req.
A-HO-REQUEST
A-HO-REQUEST-ACK
MAP-Prep-Handover resp. MAP-Send-Handover-Report req.
IAM
MAP-Send-Handover-Report resp. (1)
A-HO-COMMAND ACM
MAP-Process-Access-Sig req. A-HO-DETECT
A-CLR-CMD/COM MAP-Send-End-Signal req. A-HO-COMPLETE
ANSWER
RELEASE
End of call
MAP-Send-End-Signal resp.
NOTE 1: Can be sent at any time after the reception of IAM

Basic HO requiring a Circuit between
MSC-A and MSC-B
The MAP-PREPARE-HO request carries in the A-HO-REQUEST all
information needed by MSC-B for allocating a radio channel.
MSC-B returns MAP-PREPARE-HO response after getting the HN

from it’s associated VLR.
The HN is used to route the connection of the call from MSC-A to

MSC-B.
The TCH allocation result is sent to MSC-A using MAP-PROCESS-

ACCESS-SIGNALING request.
Once A-HO-REQUEST-ACK is received by MSC-A, it tries to

establish a circuit with MSC-B using the signaling procedures
supported by the network.

Basic HO without a Circuit between MSC-A
and MSC-B
MS/BSS-A BSS-B/MS
MSC-A MSC-B VLR-B
A-HO-REQUIRED
MAP-Prep-Handover req.
A-HO-REQUEST
A-HO-REQUEST-ACK
A-HO-COMMAND MAP-Prep-Handover resp.
A-CLR-CMD/COM MAP-Send-End-Signal req. A-HO-COMPLETE
End of link

Subsequent Handback with a Circuit
MS/BSS-B BSS-A/MS
MSC-A MSC-B VLR-B
A-HO-REQUIRED
MAP-Prep-Sub-Handover req.
A-HO-REQUEST
A-HO-REQUEST-ACK
MAP-Prep-Sub-Handover resp. A-HO-COMMAND
A-HO-DETECT
A-HO-COMPLETE
MAP-Send-End-Signal resp. A-CLR-CMD/COM
Release

Subsequent Handover with a Circuit
M S/BSS
M SC-B’ VLR-B’
M SC-A M SC-B VLR-B
A-HO-REQUIRED
MAP-Prepare-Handover req. MAP-Allocate-Handover-Number req.
MAP-Prepare-Handover resp. MAP-Send-Handover-Report req.
IAM
MAP-Send-Handover-Rep. resp. (1)
ACM
MAP-Prep-Sub-Ho resp.
A-HO-COMMAND
A-HO-DETECT
MAP-Process-Access-Signalling req.
A-HO-COMPLETE
MAP-Send-End-Signal req.
Answer
Release
A-CLR-CMD/COM
(end of call)
Release

Subsequent Handback without a Circuit
MS/BSS-B BSS-A/MS
MSC-A MSC-B VLR-B
A-HO-REQUIRED
A-HO-REQUEST
A-HO-REQUEST-ACK
A-HO-DETECT
A-HO-COMPLETE

Subsequent Handover without a Circuit
M S/BSS
M SC-B’ VLR-B’
M SC-A M SC-B VLR-B
A-HO-REQUIRED
MAP-Prepare-Handover req.
MAP-Prepare-Handover resp.
A-HO-COMMAND
A-HO-DETECT
A-HO-COMPLETE
A-CLR-CMD/COM
(end of link)

Basic HO with a Circuit between 3G_MSC-A
and MSC-B
UE/M S/RNS-A BSS-B/M S/UE
3G_M SC-A M SC-B VLR-B
Iu-RELOCATION-
REQUIRED MAP-Prep-Handover req. MAP-Allocate-Handover-Number req.
A-HO-REQUEST
A-HO-REQUEST-ACK
IAM
Iu-RELOCATION- ACM
COMM AND
Iu-RELEASE- MAP-Send-End-Signal req. A-HO-COMPLETE

CMD/COM
ANSWER
RELEASE
End of call

Basic HO without a Circuit between 3G_MSC-
A and MSC-B
UE/MS/RNS-A BSS-B/UE/MS
3G_MSC-A MSC-B VLR-B
Iu-RELOCATION-
REQUIRED
A-HO-REQUEST
A-HO-REQUEST-ACK
Iu-RELOCATION- MAP-Prep-Handover resp.
COMMAND
Iu-RELEASE- MAP-Send-End-Signal req. A-HO-COMPLETE

CMD/COM
End of link

Subsequent HB with Circuit between
3G_MSC-A and MSC-B
UE/MS/BSS-B RNS-A/UE/MS
MSC-A 3G_MSC-B VLR-B
Iu-RELOCATION-
MAP-Prep-Sub-Handover req. REQUIRED
A-HO-REQUEST
A-HO-REQUEST-ACK
MAP-Prep-Sub-Handover resp. Iu-RELOCATION-
A-HO-DETECT COMMAND
A-HO-COMPLETE
MAP-Send-End-Signal resp. Iu-RELEASE-
Release CMD/COM

Subsequent HO with Circuit between
3G_MSC-A and MSC-B’
UE/M S/BSS/RNS
M SC-B’ VLR-B’
3G_M SC-A 3G_M SC-B VLR-B
Iu-RELOCATION-
REQUIRED
MAP-Prep -Sub-Handover req.
MAP-Prep are-Handover req. MAP-Allocate-Handover-Number req.
MAP-Prep are-Handover resp . MAP-Send-Handover-Rep ort req.
IAM
MAP-Send-Handover-Rep . resp . (1)
ACM
MAP-Prep -Sub-Ho resp .

Iu-RELOCATION-CMD
A-HO-DETECT
MAP-Process-Access-Signallin g req.
A-HO-COMPLETE
MAP-Send-End-Sign al req.
Answer
Release
MAP-Send-End-Sign al resp .
Iu-RELEASE-CM D/COM
(end of call)
Release
NOTE 1: Can be sent at any time after the recep tion of IAM

Subsequent HB without Circuit
between 3G_MSC-A and MSC-B
UE/MS/BSS-B RNS-A/UE/MS
MSC-A 3G_MSC-B VLR-B
Iu-RELOCATION-
MAP-Prep-Sub-Handover req. REQUIRED
A-HO-REQUEST
A-HO-REQUEST-ACK
MAP-Prep-Sub-Handover resp. Iu-RELOCATION-
A-HO-DETECT COMMAND
A-HO-COMPLETE
CMD/COM

Subsequent HO without Circuit
between 3G_MSC-A and MSC-B’
UE/M S/BSS/RNS
M SC-B’ VLR-B’
Iu-RELOCATION-REQUIRED
Iu-RELOCATION-CMD
A-HO-DETECT
A-HO-COMPLETE
Iu-RELEASE-CM D/COM
(end of link)

GSM to UMTS HO
The GSM to UMTS HO can be divided into

Basic HO requiring a circuit between MSC-A, 3G_MSC-B
Basic HO not requiring a circuit
Subsequent HO from MSC-B to 3G_MSC-B’ with a circuit
Subsequent Handback to 3G_MSC-A with a circuit
Subsequent HO from MSC-B to 3G_MSC-B’ without a circuit
Subsequent Handback to 3G_MSC-A without a circuit

Basic GSM to UMTS HO with a Circuit
RNS-B/UE/M S
UE/M S/BSS-A
3G_M SC-B
M SC-A VLR-B
A-HO-REQUIRED
Iu-RELOCATION-REQUEST
Iu-RELOCATION-REQUEST-ACK
IAM
A-HO-COMMAND ACM
MAP-Process-Access-Sig req. Iu-RELOCATION-DETECT
A-CLR-CMD/COM MAP-Send-End-Signal req. Iu-RELOCATION-COM PLETE
ANSWER
RELEASE
End of call

Basic GSM to UMTS HO without a Circuit
UE/M S/BSS-A RNS-B/UE/M S

M SC-A 3G_M SC-B VLR-B
A-HO-REQUIRED
A-HO-COMMAND MAP-Prep-Handover resp.
MAP-Process-Access-Sig req. Iu-RELOCATION-DETECT
A-CLR-CMD/COM MAP-Send-End-Signal req. Iu-RELOCATION-COM PLETE
End of link

Subsequent GSM to UMTS
Handback with a Circuit
UE/MS/RNS-B BSS-A/UE/MS
A-HO-REQUIRED
Iu-RELOCATION-DETECT
Iu-RELOCATION-COMPLETE
Release

Handover with a Circuit
UE/M S/BSS/RNS
3G_M SC-B’ VLR-B’
M SC-A M SC-B VLR-B

A-HO-REQUIRED
MAP-Prep are-Handover resp . MAP-Send-Handover-Rep ort req.
IAM
ACM

A-HO-COMMAND
Iu-RELOCATION-COM PLETE
Answer
Release
A-CLR-CMD/COM
(end of call)
Release

Handback without a Circuit
UE/MS/RNS-B BSS-A/UE/MS
A-HO-REQUIRED
Iu-RELOCATION-COMPLETE

Handover without a Circuit
UE/M S/BSS/RNS
3G_M SC-B’ VLR-B’
M SC-A M SC-B VLR-B

A-HO-REQUIRED
A-HO-COMMAND
Iu-RELOCATION_COM PLETE
A-CLR-CMD/COM
(end of link)

SRNS Relocation
The HO procedures for Inter UMTS HO can be sub-divided into
Basic relocation procedure with a circuit between 3G_MSC-A and 3G_MSC-B
(Includes multiple bearers)
Basic relocation not requiring a circuit
Subsequent relocation back requiring a circuit connection
Subsequent relocation requiring a circuit connection
Subsequent relocation back without a circuit connection
Subsequent relocation without a circuit connection

Basic Relocation with a circuit connection
RNS-A RNS-B
IU-RELOC-REQUIRED
IU-RELOC-REQUEST
IU-RELOC-REQUEST-ACK
IAM
IU-RELOC-COMM AND ACM
MAP-Process-Access-Sig req. IU-RELOC-DETECT
IU-REL-CM D/COM MAP-Send-End-Signal req. IU-RELOC-COM PLETE
ANSWER
RELEASE
End of call

Basic Relocation with multiple circuit
connections
If 3G_MSC-A supports multicall function, 3G_MSC-A does the
following
If 3G_MSC-B does not support multiple bearers, it indicated 3G_MSC-A.
3G_MSC-A selects one bearer to be handed over. It reconstructs the IU-

RELOC-REQUEST and sends MAP-PREPARE-HO request.
Upon receipt of MAP-PREPARE-HO response, 3G_MSC-A sends IU-

RELOC-COMMAND to RNS-A indicating the bearers not to be handed
as the bearers to be released.
After 3G_MSC-A receives MAP-SEND-END-SIGNAL request from

3G_MSC-B, it releases the calls via 3G_MSC-B and then 3G_MSC-A
sends IU-RELEASE-COMMAND to RNS-A.

Basic Relocation with multiple circuit
connections
If 3G_MSC-A supports multicall function, 3G_MSC-A does the
following
If 3G_MSC-B supports multicall, and it receives MAP-PREPARE-HO request
from 3G_MSC-A, and the number of bearers to be handed over exceed
3G_MSC-B capability, it selects as many bearers and assigns a HN to each
bearer through it’s VLR.
3G_MSC-B then sends IU-RELOC-REQUEST to RNS-B.
After the reception of IU-RELOC-REQUEST-ACK from RNS-B, 3G_MSC-B

generates Relocation Number List containing couples of (RAB ID, HN) that
were successfully allocated and sends to 3G_MSC-A using MAP-PREPARE-
HO response.
3G_MSC-A on receipt of this establishes circuits and sends IU-RELOC-

COMMAND to RNS-A indicating the number of bearers that failed to setup.

Basic Relocation without a circuit
connection
RNS-A RNS-B
IU-RELOC-REQUIRED
IU-RELOC-REQUEST
IU-RELOC-REQUEST-ACK
MAP-Prep-Handover resp.
IU-RELOC-COMM AND
MAP-Process-Access-Sig req. IU-RELOC-DETECT
IU-REL-CM D/COM MAP-Send-End-Signal req. IU-RELOC-COM PLETE
End of link

Subsequent Relocation back with a
circuit connection
RNS-B RNS-A
3G_MSC-A 3G_MSC-B VLR-B
Iu-RELOCATION-
REQUIRED
Iu-RELOCATION-
REQUEST
Iu-RELOCATION-
REQUEST-ACK MAP-Prep-Sub-Handover resp. Iu-RELOCATION-
COMMAND
Iu-RELOCATION-
DETECT
Iu-RELOCATION-
COMPLETE
CMD/COM
Release

Subsequent Relocation with
a circuit connection
RNS-B RNS-B'
3G_M SC-B' VLR-B'

Iu-RELOCATION-
REQUIRED
Iu-RELOCATION-
REQUEST
Iu-RELOCATION-
MAP-Prep are-Handover resp . REQUEST-ACK
MAP-Send-Handover-Rep ort req.
IAM
ACM

Iu-RELOCATION-CMD
Iu-RELOCATION-
DETECT
Iu-RELOCATION-
COM PLETE
Answer
Release
Iu-RELEASE-CM D/COM
(end of call)
Release
Subsequent Relocation back without a
circuit connection
RNS-B RNS-A
3G_MSC-A 3G_MSC-B VLR-B
Iu-RELOCATION-
REQUIRED
Iu-RELOCATION-
REQUEST
Iu-RELOCATION-
REQUEST-ACK MAP-Prep-Sub-Handover resp. Iu-RELOCATION-
COMMAND
Iu-RELOCATION-
DETECT
Iu-RELOCATION-
COMPLETE
CMD/COM

Subsequent Relocation
without a circuit connection
RNS-B RNS-B'
3G_M SC-B' VLR-B'

Iu-RELOCATION-
REQUIRED
Iu-RELOCATION-
REQUEST
Iu-RELOCATION-
MAP-Prepare-Handover resp. REQUEST-ACK
Iu-RELOCATION-CMD
Iu-RELOCATION-
DETECT
Iu-RELOCATION-
COM PLETE
Iu-RELEASE-CM D/COM
(end of link)

Question and Answer

5 January 2007 Internal use only
Thank You
www.huawei.com
www.huawei.com
HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential

Page 79
HUAWEI TECHNOLOGIES CO., LTD.

OWG003407 Hand Over Analysis and Process: 5 January 2007

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

OWG003407 Hand Over Analysis and Process: 5 January 2007

Încărcat de

Drepturi de autor:

Formate disponibile

5 January 2007 Internal use only

OWG003407 Hand Over

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 3

 Subsequent inter-MSC Handback.

• Handover between Radio Network Subsystems connected to

 Inter 3G_MSC HO from GSM to UMTS.

 Inter 3G_MSC relocation, where the UE is relocated from

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 4

 Basic Handover is the procedure where the UE is

 Subsequent Handover is the procedure where the UE is

 Subsequent Handback is the procedure where the UE is

 Limitation: Inter-MSC HO does not support Call-

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 5

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 6

 In the inter-MSC HO case, MSC-A controls the call and MM during

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 7

 During a subsequent HO back to MSC-A, MSC-A acts as BSS towards

 During a subsequent HO to a third MSC-B’, MSC-A works towards

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 8

 During a subsequent inter-system HO back to MSC-A, MSC-A acts

 During a subsequent inter-system HO to a third 3G_MSC-B’, MSC-A

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 9

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 10

MSC-A can be realized as having five functional components

Call Control Procedures

Handover control Procedures

MAP control Procedures

Switch and Handover Device.

Interface A’ is the interface to the old BSS, whereas interface

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 11

When a basic HO from MSC-A to MSC-B has to be performed or

When a subsequent HO to MSC-B’ has to be performed or for

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 12

Handover control procedures provide the overall control of HO

MAP Procedures is responsible for controlling the exchange of

The Switch and HO device is responsible for connecting the new

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 13

NOTE: In a) and b) A’ is released after handover;

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 14

Fig 2c B’ to B” B’ to B” and B’” B’ to B’” B’ to B”

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 15

MSC-B notifies (3G)MSC-A of the successful intra-MSC HO

In the inter MSC HO case, the role of MSC-B (MSC-B’) is only to

MSC-B will do some processing on the BSSMAP message received

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 16

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 17

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 18

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 19

For a subsequent relocation back to 3G_MSC-A, 3G_MSC-A acts

During a subsequent relocation to 3G_MSC-B’, 3G_MSC-A works

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 20

During a subsequent inter-system UMTS to GSM HO back to

During a subsequent inter-system UMTS to GSM HO to a third

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 21

During a subsequent inter-system GSM to UMTS HO back to

During a subsequent inter-system GSM to UMTS HO to a third

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 22

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 23

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 24

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential Page 25

MAP Procedures are responsible for controlling the exchange of

The Switch and HO Device is responsible for connecting the new