23009-650 Handover CN and UE

3GPP TS 23.009 V6.5.
0 (2008-12)
Technical Specification
3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Handover procedures (Release 6)
GLOBAL SYSTEM FOR MOBILE COMMUNICATIONS
The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification. Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organisational Partners' Publications Offices.
Release 6
3GPP TS 23.009 V6.5.0 (2008-12)
Keywords
GSM, UMTS, handover
3GPP Postal address
3GPP support office address

650 Route des Lucioles - Sophia Antipolis Valbonne - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Internet
http://www.3gpp.org
Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media.
2008, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC). All rights reserved. UMTS is a Trade Mark of ETSI registered for the benefit of its members 3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners LTE is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners GSM and the GSM logo are registered and owned by the GSM Association
3GPP
Release 6
3GPP TS 23.009 V6.5.0 (2008-12)
Contents
Foreword ......................................................................................................................................................6 1 2 3 Scope..................................................................................................................................................7 References ..........................................................................................................................................8 Abbreviations and definitions..............................................................................................................9
3.1 Abbreviations...............................................................................................................................................9 3.2 Definitions ...........................................................................................................................................................10
4
4.1 4.1.1 4.1.2 4.2 4.2.1 4.2.2 4.3 4.3.1 4.3.2 4.4 4.4.1 4.4.2
Role, functional composition of MSCs and interfaces for handover ...................................................11

MSC-A ......................................................................................................................................................11 Role of MSC-A ....................................................................................................................................11 Functional composition of MSC-A and its interfaces for handover.........................................................12 MSC-B ......................................................................................................................................................14 Role of MSC-B.....................................................................................................................................14 Functional composition of MSC-B and its interfaces for handover .........................................................15 3G_MSC-A ...............................................................................................................................................16 Role of 3G_MSC-A..............................................................................................................................16 Functional composition of 3G_MSC-A and its interfaces for handover/relocation ..................................18 3G_MSC-B................................................................................................................................................20 Role of 3G_MSC-B ..............................................................................................................................20 Functional composition of 3G_MSC-B and its interfaces for handover/relocation ..................................23
5 6
6.1 6.2 6.2.1 6.2.1.1 6.2.1.2 6.2.2 6.2.3 6.2.3.1 6.2.3.2
Handover initiation conditions ..........................................................................................................24 General description of the procedures for intra - MSC handovers ......................................................25
Procedure for Intra-MSC Handovers...........................................................................................................25 Procedure for Intra-3G_MSC Handovers ....................................................................................................27 Intra-3G_MSC Handover from UMTS to GSM .....................................................................................27 With no bearer or one bearer............................................................................................................27 With multiple bearers (Optional functionality) .................................................................................28 Intra-3G_MSC GSM to UMTS Handover .............................................................................................28 Procedure for Intra-3G_MSC SRNS Relocation ....................................................................................30 With no bearer or one bearer............................................................................................................31 With multiple bearers (Optional functionality) .................................................................................32
7
7.1 7.2 7.3 7.3.1 7.3.2 7.4 7.4.1 7.4.2
General description of the procedures for inter - MSC handovers ......................................................32

Basic handover procedure requiring a circuit connection between MSC-A and MSC-B ...............................33 Basic handover procedure not requiring the establishment of a circuit connection between MSC-A and MSC-B ......................................................................................................................................................35 Procedure for subsequent handover requiring a circuit connection...............................................................36 Description of subsequent handover procedure i): MSC-B to MSC-A ....................................................37 Description of the subsequent handover procedure ii): MSC-B to MSC-B' .............................................38 Procedure for subsequent handover not requiring a circuit connection .........................................................39 Description of the subsequent handover procedure without circuit connection i): MSC-B to MSC-A......40 Description of the subsequent handover procedure without circuit connection ii): MSC-B to MSC-B' ....40
8
8.1 8.1.1 8.1.1.1 8.1.1.2 8.1.2
General Description of the procedures for inter - 3G_MSC handovers ...............................................41
Handover UMTS to GSM...........................................................................................................................41 Basic Handover procedure requiring a circuit connection between 3G_MSC -A and MSC-B .................42 With one circuit connection .............................................................................................................43 With multiple circuit connections (Optional functionality) ...............................................................45 Basic UMTS to GSM Handover procedure not requiring the establishment of a circuit connection between 3G_MSC-A and MSC-B .........................................................................................................45 8.1.3 Procedure for subsequent UMTS to GSM handover requiring a circuit connection.................................46 8.1.3.1 Description of subsequent UMTS to GSM handover procedure i): 3G_MSC-B to MSC-A................47 8.1.3.1.1 With one circuit connection........................................................................................................47 8.1.3.1.2 With multiple circuit connections (Optional functionality) ..........................................................47 8.1.3.2 Description of subsequent UMTS to GSM handover procedure ii): 3G_MSC-B to MSC-B' ..............48
3GPP
Release 6
3GPP TS 23.009 V6.5.0 (2008-12)
8.1.3.2.1 8.1.3.2.2 8.1.4 8.1.4.1 8.1.4.2 8.2 8.2.1 8.2.2 8.2.3 8.2.3.1 8.2.3.2 8.2.4 8.2.4.1 8.2.4.2 8.3 8.3.1 8.3.1.1 8.3.1.2 8.3.1.2.1 8.3.1.2.2 8.3.2 8.3.3 8.3.3.1 8.3.3.1.1 8.3.3.1.2 8.3.3.2 8.3.3.2.1 8.3.3.2.2 8.3.4 8.3.4.1 8.3.4.2
With one circuit connection .............................................................................................................48 With multiple circuit connections (Optional functionality) ..........................................................48 Procedure for subsequent UMTS to GSM handover not requiring a circuit connection ...........................50 Description of subsequent UMTS to GSM handover procedure i): 3G_MSC-B to MSC-A................51 Description of the subsequent UMTS to GSM handover procedure without circuit connection ii): 3G_MSC-B to MSC-B'....................................................................................................................51 Handover GSM to UMTS...........................................................................................................................52 Basic Handover procedure requiring a circuit connection between MSC-A and 3G_MSC-B ..................53 Basic GSM to UMTS Handover procedure not requiring the establishment of a circuit connection between MSC-A and 3G_MSC-B .........................................................................................................55 Procedure for subsequent GSM to UMTS handover requiring a circuit connection.................................56 Description of subsequent GSM to UMTS handover procedure i): MSC-B to 3G_MSC-A................57 Description of subsequent GSM to UMTS handover procedure ii): MSC-B to 3G_MSC-B' ..............57 Procedure for subsequent GSM to UMTS handover not requiring a circuit connection ...........................59 Description of subsequent GSM to UMTS handover procedure without circuit connection i): MSC-B to 3G_MSC-A ....................................................................................................................60 Description of subsequent GSM to UMTS handover procedure without circuit connection ii): MSC-B to 3G_MSC-B'....................................................................................................................60 SRNS Relocation .......................................................................................................................................61 Basic relocation procedure requiring a circuit connection between 3G_MSC-A and 3G_MSC-B............62 With one circuit connection .............................................................................................................63 With multiple circuit connections (Optional functionality) ...............................................................65 3G_MSC-B does not support multiple bearers ............................................................................65 3G_MSC-B supports multiple bearers ........................................................................................65 Basic relocation procedure not requiring the establishment of a circuit connection between 3G_MSC-A and 3G_MSC-B ................................................................................................................66 Procedure for subsequent relocation requiring a circuit connection ........................................................67 Description of subsequent relocation procedure i): 3G_MSC-B to 3G_MSC-A.................................67 With one circuit connection........................................................................................................67 With multiple circuit connections (Optional functionality) ..........................................................68 Description of subsequent relocation procedure ii): 3G_MSC-B to 3G_MSC-B' ...............................68 With one circuit connection........................................................................................................69 With multiple circuit connections (Optional functionality) ..........................................................69 Procedure for subsequent relocation not requiring a circuit connection...................................................71 Description of subsequent relocation procedure i): 3G_MSC-B to 3G_MSC-A.................................72 Description of subsequent relocation procedure ii): 3G_MSC-B to 3G_MSC-B'' ..............................72 BSS/MSC and MS/MSC procedures in MSC-A (functional unit 1) .............................................................73 Call control procedures MSC-A (functional unit 2).....................................................................................74 Handover control procedures MSC-A (functional unit 3) ............................................................................75 MAP procedures in MSC-A (functional unit 4)...........................................................................................76 Interworking between Handover control procedures and MAP procedures in MSC-A..................................76 Compatibility with GSM Phase 1 ...............................................................................................................76
9
9.1 9.2 9.3 9.4 9.5 9.6
Detailed procedures in MSC-A .........................................................................................................73
10
10.1 10.2 10.3 10.4 10.5 10.6
Detailed procedures in MSC-B..........................................................................................................77

BSS/MSC (MS/BSS) procedures MSC-B (functional unit 1).......................................................................77 Call control procedures MSC-B (functional unit 2) .....................................................................................77 Handover control procedures MSC-B (functional unit 3).............................................................................78 MAP procedures MSC-B (functional unit 4)...............................................................................................78 Interworking between Handover control procedures and MAP procedures in MSC-B..................................79 Compatibility with GSM Phase 1 ...............................................................................................................79
11
11.1 11.2 11.3 11.4 11.5 11.6 11.7
Detailed procedures in 3G_MSC-A...................................................................................................79

RNC/BSC/3G_MSC and UE/MS/3G_MSC procedures in 3G_MSC-A (functional unit 1)...........................79 Call control procedures 3G_MSC-A (functional unit 2) ..............................................................................79 Handover/Relocation control procedures 3G_MSC-A (functional unit 3) ....................................................81 MAP procedures in 3G_MSC-A (functional unit 4) ....................................................................................83 Interworking between Handover/Relocation control procedures and MAP procedures in 3G_MSC-A..........83 Compatibility with GSM Phase 1 ...............................................................................................................84 Protocol interworking.................................................................................................................................84
12
Detailed procedures in 3G_MSC-B ...................................................................................................84
3GPP
Release 6
3GPP TS 23.009 V6.5.0 (2008-12)
12.1 12.2 12.3 12.4 12.5 12.6 12.7 12.8 12.8.1 12.8.1.1 12.8.1.2 12.8.2 12.8.2.1 12.8.2.2 12.8.3 12.8.3.1 12.8.3.2
RNC/BSC/3G_MSC (UE/MS/RNC/BSC) procedures in 3G_MSC-B (functional unit 1) .............................84 Call control procedures 3G_MSC-B (functional unit 2)...............................................................................84 Handover/Relocation control procedures in 3G_MSC-B (functional unit 3).................................................85 MAP procedures in 3G_MSC-B (functional unit 4).....................................................................................87 Interworking between Handover/Relocation control procedures and MAP procedures in 3G_MSC-B..........87 Compatibility with GSM Phase 1 ...............................................................................................................87 Protocol interworking.................................................................................................................................87 Interactions between handover/relocation control procedures and other RANAP procedures......................88 Interactions between handover/relocation control procedures and the security mode procedure ............88 Intra-3G_MSC-B handover/relocation..........................................................................................88 Subsequent Inter-MSC handover/relocation ...................................................................................90 Interactions between handover/relocation control procedures and the RAB assignment procedure ........92 Intra-3G_MSC-B handover/relocation..........................................................................................92 Subsequent Inter-MSC handover/relocation ...................................................................................94 Interactions between directed retry handover procedures and the RAB assignment procedure...............96 Intra-3G_MSC-B directed retry handover ......................................................................................96 Subsequent Inter-MSC directed retry handover ..............................................................................97 GSM handover...........................................................................................................................................99 UMTS to GSM handover .........................................................................................................................100 GSM to UMTS handover .........................................................................................................................101 SRNS Relocation .....................................................................................................................................102 Without circuit connection ..................................................................................................................102 With circuit connection (Optional functionality)..................................................................................102
13
13.1 13.2 13.3 13.4 13.4.1 13.4.2
Subsequent channel assignment using a circuit connection between MSC-A and MSC-B ..................99
14
14.1 14.2 14.3
Directed retry handover...................................................................................................................103

GSM handover.........................................................................................................................................103 GSM to UMTS handover .........................................................................................................................104 UMTS to GSM handover .........................................................................................................................106
15
SDL diagrams .................................................................................................................................107 Change history .........................................................................................284
Annex A (informative):
3GPP
Release 6
3GPP TS 23.009 V6.5.0 (2008-12)
Foreword
This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). The present document provides a mechanism giving reliable transfer of signalling messages within the 3GPP system. The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document.
3GPP
Release 6
3GPP TS 23.009 V6.5.0 (2008-12)
Scope
The present document contains a detailed description of the handover procedures to be used in PLMNs. The purpose of the handover procedures, as described in the present document, are to ensure that the connection to the Mobile Station (MS) or User Equipment (UE) is maintained as it moves from one cell or radio network to another. The document defines the circuit switched handover functionality based on the service requirements in 3GPP TS 22.129 [9]. The present document considers the following four cases: i) handover between Base Stations connected to the same MSC, this is termed an Intra-MSC handover; ii) handover between Radio Network Subsystems connected to the same 3G_MSC, this is termed an Intra-3G_MSC handover/relocation. This case also includes inter-system handover between RNS and BSS if the 3G_MSC supports the A-interface. In the context of this specification the term RNS refers also to a BSS when serving a mobile station in Iu mode; iii) handover between Base Stations connected to different MSCs, this is termed an Inter-MSC handover. This category can be sub-divided into three further procedures: a) the Basic Inter-MSC Handover procedure, where the MS is handed over from a controlling MSC (MSC-A) to another MSC (MSC-B); b) the Subsequent Inter-MSC Handover procedure, where the MS is handed over from MSC-B to a third MSC (MSC-B'); c) the Subsequent Inter-MSC handback, where the MS is handed back from MSC-B to MSC-A. iv) handover between Radio Network Subsystems connected to different 3G_MSCs, this is termed an Inter3G_MSC handover/relocation. In the context of this specification the term RNS also refers to a BSS when serving a mobile station in Iu mode. This category can be divided into three further sub-procedures: a) the Inter-3G_MSC Handover procedure from UMTS to GSM, where the UE/MS is handed over from a controlling 3G_MSC (3G_MSC-A) to an MSC (MSC-B); b) the Inter-3G_MSC Handover procedure from GSM to UMTS, where the UE/MS is handed over from a controlling MSC (MSC-A) to a 3G_MSC (3G_MSC-B); c) the Inter-3G_MSC Relocation procedure, where the UE is relocated from 3G_MSC-A to 3G_MSC-B. This procedure can also be combined with a hard change of radio resources (Hard Handover with switch in the core network). The MSC in this category can optionally be a 3G_MSC supporting the A-interface. The three sub-procedures do also cover subsequent handover/relocation to a third MSC-B' or 3G_MSC-B' and subsequent handover/relocation back to MSC-A or 3G_MSC-A. In both cases i) and iii) the same procedures as defined in the 3GPP TS 48.008 [5] and the 3GPP TS 24.008 [10] shall be used on the A-interface and on the Radio Interface, respectively. In case ii) the same procedures as defined in the 3GPP TS 25.413 [11] and the 3GPP TS 24.008 [10] shall be used on the Iu-interface. If the 3G_MSC in case ii) also supports the A-interface, the 3GPP TS 48.008 [5] and the 3GPP TS 24.008 [10] shall be used on the A-interface. In case iii) the handover procedures shall transport the A-interface messages between MSC-A and MSC-B described in the Mobile Application Part (MAP), 3GPP TS 29.002 [12]. In case iv) the handover procedures shall transport the A-interface messages between 3G_MSC and MSC described in the Mobile Application Part (MAP), 3GPP TS 29.002 [12]. In case iv) the relocation procedure shall transport the Iu-interface messages between 3G_MSC-A and 3G_MSC-B described in the Mobile Application Part (MAP), 3GPP TS 29.002 [12]. The interworking between the 3GPP TS 29.002 [12] protocol and the 3GPP TS 48.008 [5] protocol is described in the 3GPP TS 29.010 [8].
3GPP
Release 6
3GPP TS 23.009 V6.5.0 (2008-12)
Multicall supplementary service is not applicable in GERAN Iu mode and relocation of Multicalls is therefore only possible within UTRAN. Handovers, which take place on the same MSC are termed Intra-MSC handovers; this includes both Inter-BSS and Intra-BSS handovers. Handovers, which take place on the same 3G_MSC are termed Intra-3G_MSC handovers; this includes Inter-RNS handovers and optionally RNS to BSS and BSS to RNS handovers. In the context of this specification the term InterSystem handover can also refer to a handover which takes place between a Base Station serving a mobile station in Iu mode and a Base Station serving a mobile in A/Gb mode. "Flexible Iu interface for handover/relocation" Option (see 3GPP TS 23.221 [19], subclause 4.2.1): Up to release 99 an RNS can be connected only to one 3G_MSC. From release 4 onwards, as a network option, an RNS can have Iu interfaces to more than one MSC. Such an additional Iu interface may be selected by an MSC during an intra-PLMN relocation or intra-PLMN BSS to RNS handover procedure. This allows the MSC to use an Intra-3G_MSC handover procedure according to case ii) instead of an Inter-3G_MSC handover procedure according to case iv). The decision whether to use the Intra-3G_MSC handover procedure is implementation and configuration dependent. In a network implementing this option, a global title based on the Global RNC-Id may optionally be used for the addressing of the Iu interface messages. "Intra Domain Connection of RAN Nodes to Multiple CN Nodes" Option (see 3GPP TS 23.236 [18]): when applied, a BSS or an RNS can be connected to more than one MSC. The present document also covers the requirements for handover in ongoing GSM voice group calls, directed retry and handover without a circuit connection between (U)MSCs. The present document does not consider the case of handovers between radio channels on the same BSS (Intra-BSS handover) or the handover of packet radio services. The Inter-RNS handover case that results in a relocation is covered by the present document but not other Inter-RNS or Intra-RNS handover cases. For voice broadcast calls in GSM, the speaker uses normal point-to-point handover procedures, whilst the listeners use idle mode cell reselection procedures, as for the voice group call listeners. Voice group calls is only applicable to GSM and handover of voice group calls is therefore only possible in GSM. Inter-MSC hand-over imposes a few limitations on the system. After inter-MSC hand-over: call re-establishment is not supported.
The list of 3GPP TS 48.008 [5] features supported during and after Inter-MSC handover is given in 3GPP TS 49.008 [7]. In the Inter-MSC handover case, the interworking between a Phase 1 BSSMAP protocol possibly used by one MSC and the Phase 2 BSSMAP protocol used in the Phase 2 MAP protocol on the E-interface is performed by this MSC. NOTE: The message primitive names used in the SDL diagrams and message flows in the present document do not represent the actual messages specified in the GSM or 3GPP stage 3 technical specifications. The primitive names are only intended to be indicative of their use in the present document.
References
References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. For a specific reference, subsequent revisions do not apply. For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
3GPP
Release 6
3GPP TS 23.009 V6.5.0 (2008-12)
[1] [2] [2a] [3] [4] [5] [6] [7] [8]
ITU-T Recommendation Q.118: "Abnormal conditions - Special release arrangements". Void. 3GPP TR 21.905: "3G Vocabulary". 3GPP TS 43.068: "Voice Group Call Service (VGCS); Stage 2". 3GPP TS 45.008: "Radio Subsystem Link Control". 3GPP TS 48.008: "Mobile Switching Centre - Base Station System (MSC-BSS) Interface Layer 3 specification". 3GPP TS 48.058: "Base Station Controler - Base Transceiver Station (BSC-BTS) Interface Layer 3 specification". 3GPP TS 49.008: "Application of the Base Station System Application Part (BSSAP) on the E-interface". 3GPP TS 29.010: "Information Element Mapping between Mobile Station - Base Station System (MS-BSS) and Base Station System - Mobile-services Switching Centre (BSS-MSC); Signalling procedures and the Mobile Application Part (MAP)". 3GPP TS 22.129: "Handover Requirements between UMTS and GSM or other Radio Systems". 3GPP TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols; Stage 3". 3GPP TS 25.413: "UTRAN Iu interface RANAP signalling". 3GPP TS 29.002: "Mobile Application Part (MAP) specification". 3GPP TS 25.303: "UE functions and inter-layer procedures in connected mode". 3GPP TS 25.331: "Radio Resource Control (RRC) Protocol Specification". 3GPP TS 29.108: "Application of the Radio Access Network Application Part (RANAP) on the Einterface". ITU-T Recommendation G.711: "Pulse code modulation (PCM) of voice frequencies". 3GPP TS 23.135: "Multicall supplementary service; Stage 2". 3GPP TS 23.236: "Intra Domain Connection of RAN Nodes to Multiple CN Nodes". 3GPP TS 23.221: "Architectural Requirements". 3GPP TS 25.401: "UTRAN Overall Description". 3GPP TS 23.195: "Provision of UE Specific Behaviour Information to Network Entities". 3GPP TS 23.172: "Technical realization of Circuit Switched (CS) multimedia service; UDI/RDI fallback and service modification".
[9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20] [21] [22]
3
3.1
Abbreviations and definitions

Abbreviations
A third generation MSC that supports the Iu interface and optionally the A interface The controlling 3G_MSC on which the call was originally established The 3G_MSC to which the UE is handed over in a Basic Handover The 3G_MSC to which the UE is handed over in a Subsequent Handover
For the purpose of the present document, the following abbreviations apply: 3G_MSC 3G_MSC-A 3G_MSC-B 3G_MSC-B'
3GPP
Release 6
10
3GPP TS 23.009 V6.5.0 (2008-12)
BSC BSS BSS-A BSS-B BTS GERAN ISC MS MSC MSC-A MSC-B MSC-B' RNC RNS SBSS SNA SRNS UE UE/MS UESBI USIM
Base Station Controller Base Station System The BSS from which the MS is being handed over The BSS to which the MS is being handed over Base Transceiver Station GSM EDGE Radio Access Network International Switching Centre Mobile Station A second generation Mobile Services Switching Centre that only supports the A interface The controlling MSC on which the call was originally established The MSC to which the MS is handed over in a Basic Handover The MSC to which the MS is handed over in a Subsequent Handover Radio Network Controller Radio Network Subsystem Serving BSS Shared Network Area Serving RNS A User Equipment is a terminal that supports USIM and the UMTS Uu interface A terminal that supports USIM, SIM, the Uu interface and the Um interface UE Specific Behaviour Information UMTS Subscriber Identity Module
Other abbreviations used in the GSM specifications are listed in 3GPP TR 21.905[2a].
3.2 Definitions
The following terms are used in this Technical Specification: A/Gb mode: mode of operation of the MS when connected to the Core Network via GERAN and the A and/or Gb interfaces. Throughout this specification the term GSM refers to GERAN A/Gb mode. Iu mode: mode of operation of the MS when connected to the Core Network via GERAN or UTRAN and the Iu interface. Throughout this specification the term UMTS refers to UTRAN or GERAN Iu mode. Iur interface: the logical interface between two UTRAN RNSs. Iur-g interface: the logical interface between two BSSs or a BSC and an RNC and it is only considered in Iu mode. Iu Currently used codec: the codec used by the UE/MS in UTRAN or GERAN Iu mode before a handover or SRNS relocation. Iu Selected codec: the codec to be used by the UE/MS in UTRAN or GERAN Iu mode after the handover or SRNS relocation. Iu Supported Codecs List: a list of codecs supported by the MS and by the core network, provided by MSCA/3G_MSC-A to 3G_MSC-B during Inter-MSC handover/relocation. The Iu Supported Codecs List may contain separate list of codecs for UTRAN Iu mode and GERAN Iu mode. Within each list, the codecs are ordered in decreasing order of priority, the first entry in the list being the highest priority codec (preferred codec) and the last entry the lowest priority codec. Default speech codec: In UTRAN Iu mode the default speech codec is the UMTS AMR or UMTS AMR2 codec, dependent on the capabilities of the UE/MS. For a description of how the network determines the default UMTS speech codec, see [10], subclause 5.2.1.11. If necessary, 3G_MSC-B shall use the Radio Resource Information instead of the GSM Bearer Capability, since the GSM Bearer Capability is not available in MSC-B. In GERAN Iu mode the default speech codec is the AMR FR codec. UE Specific Behaviour Information - Iu (UESBI-Iu): information that is sent from the MSC to the RAN and that can be used to derive specific information about the UE's capabilities.
3GPP
Release 6
11
3GPP TS 23.009 V6.5.0 (2008-12)
4
4.1
4.1.1
Role, functional composition of MSCs and interfaces for handover

MSC-A
Role of MSC-A
In the Intra-MSC handover case, the MSC-A (simply termed MSC) controls the call, the mobility management and the radio resources before, during and after an Intra-MSC handover. When BSSAP procedures have to be performed, they are initiated and driven by MSC-A. In the Inter-MSC handover case, MSC-A is the MSC which controls the call and the mobility management of the Mobile during the call, before, during and after a basic or subsequent handover. When BSSAP procedures related to dedicated resources have to be performed towards the MS, they are initiated and driven by MSC-A. The MSC-A MSC-B interface works as a MSC - BSS interface for a subset of BSSMAP procedures. These BSSMAP procedures, described in 3GPP TS 49.008 [7] are only those related to dedicated resources. The DTAP signalling is relayed transparently by MSC-B between MSC-A and the MS. During a basic handover, MSC-A initiates and controls all the handover procedure, from its initiation (reception of Handover Required from BSS-A on A-interface) until its completion (reception of Handover Complete from MSC-B on E-interface). For handover to an area where "Intra Domain Connection of RAN Nodes to Multiple CN Nodes" is applied, MSC-A can have multiple target CN nodes for each handover target in a pool-area as specified in 3GPP TS 23.236 [18]. During a subsequent handover back to MSC-A, MSC-A acts as a BSS towards MSC-B, which controls the handover procedure until the termination in MSC-A of the handover radio resources allocation (sending of the Handover Request Acknowledge to MSC-B from MSC-A). Then all handover related messages shall terminate at MSC-A (e.g. Handover Detect/Complete from BSS-B, Handover Failure from BSS-A). During a subsequent handover to a third MSC, MSC-A works towards MSC-B' as described above in the basic handover paragraph and towards MSC-B as described above in subsequent handover paragraph. In the Inter-System, inter-MSC handover case, MSC-A is the MSC which controls the call and the mobility management of the Mobile during the call, before, during and after a basic or subsequent handover. When BSSAP procedures related to dedicated resources have to be performed towards the MS, they are initiated and driven by MSC-A. The MSC-A - 3G_MSC-B interface works as a MSC - BSS interface for a subset of BSSMAP procedures. These BSSMAP procedures, described in 3GPP TS 49.008 [7] are only those related to dedicated resources. The DTAP signalling is relayed transparently by 3G_MSC-B between MSC-A and the MS. During a basic inter-system handover, MSC-A initiates and controls all the handover procedure, from its initiation (reception of Handover Required from BSS-A on A-interface) until its completion (reception of Handover Complete from 3G_MSC-B on E-interface). During a subsequent inter-system handover back to MSC-A, MSC-A acts as a BSS towards 3G_MSC-B, which controls the handover procedure until the termination in MSC-A of the handover radio resources allocation (sending of the Handover Request Acknowledge to 3G_MSC-B from MSC-A). Then all handover related messages shall terminate at MSC-A (e.g. Handover Detect/Complete from BSS-B, Handover Failure from BSS-A). During a subsequent inter-system handover to a third MSC, MSC-A works towards 3G_MSC-B' as described above in the basic inter-system handover paragraph and towards 3G_MSC-B as described above in subsequent inter-system handover paragraph. If MSC-A supports the "Provision of UE Specific Behaviour Information to Network Entities" (see 3GPP TS 23.195 [21]), it shall send UESBI-Iu to the target MSC during basic and subsequent handover, and basic and subsequent intersystem handover.
3GPP
Release 6
12
3GPP TS 23.009 V6.5.0 (2008-12)
4.1.2
Functional composition of MSC-A and its interfaces for handover
In order to simplify the description of the handover procedures the controlling MSC (MSC-A) can be considered to be composed of five functional units, as shown in figure 1. Signalling functions: 1) BSC/MSC (MS/BSC) Procedures MSC-A. This unit is used to control the signalling between the MSC, BSC and MS. Interface A' is the connection to the old BSC and interface A'' is the connection to the new BSC, when an Intra-MSC handover takes place. Interface x represents the interworking connection to the Handover Control Procedures MSC-A. 2) Call Control Procedures MSC-A. This unit is used to control the call. Interface B' is used for normal call control procedures. When a Basic handover from MSC-A to MSC-B is to be performed then interface B'' is employed to provide a signalling and call control connection to MSC-B. If a Subsequent handover to MSC-B' is to be performed then interface B''' is used. Similarly, when a Basic inter-system handover from MSC-A to 3G_MSC-B is to be performed, then interface B'' is employed to provide a signalling and call control connection to 3G_MSC-B. If a subsequent inter-system handover to 3G_MSC-B' is to be performed, then interface B''' is used. 3) Handover Control Procedures MSC-A. This unit provides both the overall control of the handover procedure and interworking between the internal interfaces (x, y and z). 4) MAP Procedures MSC-A. This unit is responsible for controlling the exchange of MAP messages between MSCs during an Inter-MSC handover, or between MSC-A and 3G_MSC-B during an Inter-system Inter-MSC handover. This unit communicates with the Handover Control Procedures MSC-A via interface z. Switching functions: 5) Switch and Handover Device MSC-A. For all calls, except for ongoing voice group calls (see 3GPP TS 43.068 [3] for a definition) this unit is responsible for connecting the new path into the network via interface B'. In the case of ongoing voice group calls this unit is responsible for maintaining the connection between the down link group call channels and the active uplink. In specific cases it may be unnecessary to take any explicit action in the MSC concerning the handover device. The handover device interconnections are illustrated in figure 2.
3GPP
Release 6
13
3GPP TS 23.009 V6.5.0 (2008-12)
Signalling functions
Call Control Procedures MSC-A y Handover Control Procedures MSC-A z MAP Procedures MSC-A
B B
A A
1 BSC/MSC (MS/BSC) Procedures MSC-A
Switching control Switching functions
A A
Switch and Handover Device MSC-A
B B
Figure 1: Functional composition of the controlling MSC (MSC-A) for supporting handover For MS to MS calls in the same MSC the configuration in Figure 2b) applies. In this case interface B'' is internal to MSC-A and does not connect to another MSC. The handover device can either be a three-party bridge or a switching facility without three-party connection capabilities. For a three-party bridge configuration the states of the handover device are as shown in table 1. The three-party configuration exists in the intermediate state. This type of handover device may reduce the interruption time. However, this may require noise reduction if one of the radio channels is unterminated at some time in the intermediate state. For a handover device consisting of a simple switch there will be no intermediate state. Table 1: States of the handover device
Case Initial Connection B' to A' B' to A' B' to B'' Intermediate Connection B' to A' and A'' B' to A' and B'' B' to B''and B''' Resulting Connection Successful Unsuccessful Procedure Procedure B' to A'' B' to A' B' to B'' B' to B''' B' to A' B' to B''
Figure 2a) Figure 2b) Figure 2c)
3GPP
Release 6
14
3GPP TS 23.009 V6.5.0 (2008-12)
A a) Intra-MSC Handover case. A B
B b) Basic Handover case and handover of MS to MS call in the same MSC.
B B c) Subsequent Handover case

NOTE: In a) and b) A is released after handover; In c) B is released after handover.
Figure 2: Connections in the handover device (Unit 5)
4.2
4.2.1
MSC-B
Role of MSC-B
by using the A-
In the Intra-MSC handover case, the MSC-B keeps the control of the whole Intra-MSC handover procedure. MSC-B notifies MSC-A or 3G_MSC-A of successful intra -MSC-B handover completion HANDOVER-PERFORMED message.
In the Inter-MSC handover case, the role of MSC-B (MSC-B') is only to provide radio resources control within its area. This means that MSC-B keeps control of the radio resources connection and release towards BSS-B. MSC-B will do some processing on the BSSMAP information received on the E-interface or A-interface whereas it will relay the DTAP information transparently between A-interface and E-interface. MSC-A initiates and drives a subset of BSSMAP procedures towards MSC-B, while MSC-B controls them towards its BSSs to the extent that MSC-B is responsible for the connections of its BSSs. The release of the dedicated resources between MSC-B and BSS-B is under the responsibility of MSC-B and BSS-B, and is not directly controlled by MSC-A. When clearing is to be performed due to information received from BSS-B, MSC-B shall transfer this clearing indication to MSC-A, to clear its connection with BSS-B, to terminate the dialogue with MSC-A through the E-interface, and to release its circuit connection with MSC-A, if any. In the same way, the release of the connection to its BSS-B, is initiated by MSC-B, when the dialogue with MSC-A ends normally and a release is received from the circuit connection with MSC-A, if any, or when the dialogue with the MSC-A ends abnormally. When a release is received by MSC-B for the circuit connection with MSC-A then MSC-B shall release the circuit connection.
3GPP
Release 6
15
3GPP TS 23.009 V6.5.0 (2008-12)
In the Inter-system Inter-MSC handover case, the role of MSC-B (MSC-B') is only to provide radio resources control within its area. This means that MSC-B keeps control of the radio resources connection and release towards BSS-B. MSC-B will do some processing on the BSSMAP information received on the E-interface or A-interface whereas it will relay the DTAP information transparently between A-interface and E-interface. 3G_MSC-A initiates and drives a subset of BSSMAP procedures towards MSC-B, while MSC-B controls them towards its BSSs to the extent that MSC-B is responsible for the connections of its BSSs. The release of the dedicated resources between MSC-B and BSS-B is under the responsibility of MSC-B and BSS-B, and is not directly controlled by 3G_MSC-A. When clearing is to be performed due to information received from BSS-B, MSC-B shall transfer this clearing indication to 3G_MSC-A, to clear its connection with BSS-B, to terminate the dialogue with 3G_MSC-A through the E-interface, and to release its circuit connection with 3G_MSC-A, if any. In the same way, the release of the connection to its BSS-B, is initiated by MSC-B, when the dialogue with 3G_MSC-A ends normally and a release is received from the circuit connection with MSC-A, if any, or when the dialogue with the MSC-A ends abnormally. When a release is received by MSC-B for the circuit connection with 3G_MSC-A then MSC-B shall release the circuit connection. For subsequent inter-MSC handover to an area where "Intra Domain Connection of RAN Nodes to Multiple CN Nodes" is applied, MSC-B can have multiple target CN nodes for each handover target in a pool-area as specified in 3GPP TS 23.236 [18].
4.2.2
Functional composition of MSC-B and its interfaces for handover
The functional composition of an MSC acting as MSC-B is essentially the same as that of MSC-A. However, there are some differences. The functional units are as follows (see figure 3). Signalling functions: 1) BSC/MSC (MS/BSC) Procedures MSC-B. This unit is used to control the signalling between the MSC, BSC and MS. Interface A'' is the connection to the new BSC, when an Intra-MSC handover takes place. Interface x represents the interworking connection to the Handover Control Procedures MSC-B. 2) Call Control Procedures MSC-B. This unit is used for normal call control and signalling to MSC-A, or 3G_MSC-A in the case of inter-system inter-MSC handover. 3) Handover Control Procedures MSC-B. This unit provides both the overall control of the handover procedure and interworking between the internal interfaces (x, y and z) in MSC-B. 4) MAP Procedures MSC-B. This unit is responsible for controlling the exchange of MAP messages between MSC-A, or 3G_MSC-A, and MSC-B and for signalling to the VLR in MSC-B. Switching functions: 5) Switch MSC-B. For all calls, except ongoing voice group calls (see 3GPP TS 43.068 [3] for a definition) this unit is responsible, with BSS-B, for connecting the circuit from MSC-A, or 3G_MSC-A, to BSS-B. This unit may also need to act as a handover device for Intra-MSC handovers controlled by MSC-B. In the case of ongoing voice group calls this unit is responsible for maintaining the connection between the group member currently assigned the uplink and the distribution device. In specific cases it may be unnecessary to take any explicit action in the MSC concerning the handover device.
3GPP
Release 6
16
3GPP TS 23.009 V6.5.0 (2008-12)
Call Control Procedures MSC-B y Handover Control Procedures MSC-B z MAP Procedures MSC-B
A A
1 BSC/MSC (MS/BSC) Procedures MSC-B
A A
Switch MSC-B
Figure 3: Functional composition of MSC-B for supporting handover
4.3
3G_MSC-A
For roles and functional composition of the 3G_MSC-A working as pure GSM MSC, please see previous clause ("MSC-A").
4.3.1
Role of 3G_MSC-A
In the Intra-3G_MSC handover/relocation case, the 3G_MSC-A (simply termed 3G_MSC) controls the call, the mobility management and the radio resources before, during and after an Intra-3G_MSC handover/relocation. When RANAP or BSSMAP procedures have to be performed, they are initiated and driven by 3G_MSC-A. In a network implementing the "Flexible Iu interface for handover/relocation" option, 3G_MSC-A may optionally use a global title based on the Global RNC-Id for the addressing of the Iu interface messages towards the target RNC. For handover/relocation to an area where "Intra Domain Connection of RAN Nodes to Multiple CN Nodes" is applied, 3G_MSC-A can have multiple target CN nodes for each handover/relocation target in a pool-area as specified in 3GPP TS 23.236 [18]. In the case of intra-MSC handover of a speech call, 3G_MSC-A controls the transcoder in the core network. The 3G_MSC-A determines if a transcoder is required to be inserted or released in the CN. In the case of Inter-3G_MSC relocation, 3G_MSC-A links out the transcoder. In the Inter-3G_MSC relocation case, 3G_MSC-A is the 3G_MSC that controls the call and the mobility management of the UE during the call, before, during and after a basic or subsequent relocation. When RANAP procedures related to dedicated resources have to be performed towards the UE, they are initiated and driven by 3G_MSC-A. The
3GPP
Release 6
17
3GPP TS 23.009 V6.5.0 (2008-12)
3G_MSC-A - 3G_MSC-B interface works as a 3G_MSC - RNS interface for the RANAP procedures. The Direct Transfer signalling is relayed transparently by 3G_MSC-B between 3G_MSC-A and the UE. During a successful relocation the order to perform location reporting at change of Service Area is not transferred to the target RNS. In the Intra-3G_MSC-A relocation case, the 3G_MSC-A re-issues the Location Reporting Control towards the target RNS. In the Inter-3G_MSC relocation case, 3G_MSC-A keeps the control of the Location Report Control procedure. However, re-issuing the Iu-LOCATION-REPORTING-CONTROL messages due to subsequent Intra3G_MSC-B relocations is the responsibility of 3G_MSC-B. During a basic relocation, 3G_MSC-A initiates and controls all the relocation procedure, from its initiation (reception of Relocation Required from RNS-A on Iu-interface) until its completion (reception of Relocation Complete from 3G_MSC-B on E-interface). During 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 the termination in 3G_MSC-A of the handover radio resources allocation (sending of the Relocation Request Acknowledge to 3G_MSC-B from 3G_MSC-A). Then all relocation related messages shall terminate at 3G_MSC-A (e.g. Relocation Detect/Complete from RNS-B, Relocation Cancel from RNS-A). During a subsequent relocation to a third 3G_MSC, 3G_MSC-A works towards 3G_MSC-B' as described above in the basic relocation paragraph and towards 3G_MSC-B as described above in subsequent relocation paragraph. In the Inter-System, inter-3G_MSC handover case, 3G_MSC-A is the 3G_MSC which controls the call and the mobility management of the UE/MS during the call, before, during and after a basic or subsequent inter-system handover. When BSSAP procedures related to dedicated resources have to be performed towards the UE/MS, they are initiated and driven by 3G_MSC-A. The 3G_MSC-A MSC-B interface works as a 3G_MSC BSS interface for a subset of BSSMAP procedures. These BSSMAP procedures described in 3GPP TS 09 08 [7] are those related to dedicated resources. The DTAP signalling is relayed transparently by MSC-B between 3G_MSC-A and the UE/MS. During a basic inter-system UMTS to GSM handover, 3G_MSC-A initiates and controls all the handover procedure, from its initiation (reception of Relocation Required from RNS-A on Iu-interface) until its completion (reception of Handover Complete from MSC-B on E-interface). During a subsequent inter-system UMTS to GSM handover back to 3G_MSC-A, 3G_MSC-A acts as a BSS towards 3G_MSC-B, which controls the handover procedure until the termination in 3G_MSC-A of the handover radio resources allocation (sending of the Handover Request Acknowledge to 3G_MSC-B from 3G_MSC-A). Then all handover related messages shall terminate at 3G_MSC-A (e.g. Handover Detect/Complete from BSS-B, Relocation Cancel from RNS-A). During a subsequent inter-system UMTS to GSM handover to a third 3G_MSC, 3G_MSC-A works towards MSC-B' as described above in the basic inter-system handover paragraph and towards 3G_MSC-B as described above in subsequent inter-system handover paragraph. During a basic inter-system GSM to UMTS handover, 3G_MSC-A initiates and controls all the handover procedure, from its initiation (reception of Handover Required from BSS-A on A-interface) until its completion (reception of Handover Complete from 3G_MSC-B on E-interface). During a subsequent inter-system GSM to UMTS handover back to 3G_MSC-A, 3G_MSC-A acts as an RNS towards MSC-B, which controls the handover procedure until the termination in 3G_MSC-A of the handover radio resources allocation (sending of the Handover Request Acknowledge to MSC-B from 3G_MSC-A). Then all handover related messages shall terminate at 3G_MSC-A (e.g. Relocation Detect/Complete from RNS-B, Handover Failure from BSS-A). During a subsequent inter-system GSM to UMTS handover to a third 3G_MSC, 3G_MSC-A works towards 3G_MSC-B' as described above in the basic inter-system handover paragraph and towards MSC-B as described above in subsequent inter-system handover paragraph. 3G_MSC-A may assign a priority level defined as RAB parameter in 3GPP TS 25.413 [11] for each bearer. In case of relocation of a multicall configuration the 3G_MSC-B or the target RNC shall select the bearers to be handed over according to the priority level, if the target cell is not able to accommodate all bearers. If a selection has to be made between bearers of the same priority level, then the selection criteria are implementation dependent. For network sharing (see 3GPP TS 25.401 [20], subclause 7.2.3) 3G MSC-A shall send the SNA information to 3G_MSC-B except for emergency calls.
3GPP
Release 6
18
3GPP TS 23.009 V6.5.0 (2008-12)
If 3G_MSC-A supports the optional supplementary service Multicall (See 3GPP TS 23.135) and UE is engaged with multiple bearers the following description applies: In the Intra-3G_MSC relocation case, the 3G-MSC-A tries to relocate all bearers to a new RNS. In the basic relocation case, the 3G-MSC-A tries to relocate all bearers to 3G_MSC-B. If 3G_MSC-A receives an indication that the 3G_MSC-B does not support multiple bearers, then 3G_MSC-A shall be able to select one bearer to be handed over according to 3GPP TS 22.129 [9] and tries again to relocate the selected bearer. In the subsequent relocation to a third 3G_MSC-B' case, the 3G-MSC-A tries to relocate all bearers to 3G_MSCB'. If 3G_MSC-A receives an indication that the 3G_MSC-B' does not support multiple bearers, then 3G_MSCA shall be able to select one bearer to be handed over according to 3GPP TS 22.129 [9] and tries again to relocate the selected bearer. In the Intra-3G_MSC inter-system UMTS to GSM handover case and the basic inter-system UMTS to GSM handover case, the 3G_MSC-A shall be able to select one bearer to be handed over according to 3GPP TS 22.129 [9] and tries to handover the selected bearer. In all cases described above, 3G_MSC-A shall release some calls which has been carried by the bearers failed to set up in new RNS or the bearers not to be handed over.
If 3G_MSC-A supports the "Provision of UE Specific Behaviour Information to Network Entities" (see 3GPP TS 23.195 [21]), it shall send UESBI-Iu to the RNS-B during intra-3G_MSC handover/relocation and during subsequent inter-3G_MSC handover/relocation back to 3G_MSC-A. Furthermore, 3G_MSC-A shall send UESBI-Iu to the target MSC during basic and subsequent inter-MSC handover, and basic and subsequent inter-3G_MSC handover/relocation. For a SCUDIF call (see 3GPP TS 23.172 [22]) 3G_MSC-A may send information of the alternative radio access bearer to the target RNS during the intra-3G_MSC handover/relocation and to the target MSC during basic and subsequent inter-3G_MSC handover/relocation or assignment.
4.3.2
Functional composition of 3G_MSC-A and its interfaces for handover/relocation
In order to simplify the description of the handover/relocation procedures the controlling 3G_MSC (3G_MSC-A) can be considered to be composed of five functional units, as shown in figure 4. Signalling functions: 1) RNC/BSC/3G_MSC (UE/MS/RNC/BSC) Procedures 3G_MSC-A. This unit is used to control the signalling between the 3G_MSC, RNC or BSC and UE/MS. Interface Iu' is the connection to the old RNC and interface Iu'' is the connection to the new RNC, when an Intra-3G_MSC relocation takes place. Interface Iu' is the connection to the old RNC and interface A'' is the connection to the new BSC, when an Intra-3G_MSC UMTS to GSM handover takes place. Interface A' is the connection to the old BSC and interface Iu'' is the connection to the new RNC, when an Intra-3G_MSC GSM to UMTS handover takes place. Interface x represents the interworking connection to the Handover/Relocation Control Procedures 3G_MSC-A. 2) Call Control Procedures 3G_MSC-A. This unit is used to control the call. Interface B' is used for normal call control procedures. When a Basic relocation from 3G_MSC-A to 3G_MSC-B is to be performed then interface B'' is employed to provide a signalling and call control connection to 3G_MSC-B. If a Subsequent handover/relocation to 3G_MSC-B' is to be performed then interface B''' is used. Similarly, when a Basic intersystem handover from 3G_MSC-A to 3G_MSC-B is to be performed, then interface B'' is employed to provide a signalling and call control connection to 3G_MSC-B. If a Subsequent inter-system handover to 3G_MSC-B' is to be performed then interface B''' is used. 3) Handover/Relocation Control Procedures 3G_MSC-A. This unit provides both the overall control of the handover/relocation procedure and interworking between the internal interfaces (x, y and z). 4) MAP Procedures 3G_MSC-A. This unit is responsible for controlling the exchange of MAP messages between 3G_MSCs during an Inter-3G_MSC handover/relocation, or between 3G_MSC-A and MSC-B during an Intersystem Inter-3G_MSC handover. This unit communicates with the Handover/Relocation Control Procedures 3G_MSC-A via interface z. Switching functions:
3GPP
Release 6
19
3GPP TS 23.009 V6.5.0 (2008-12)
5) Switch and Handover/Relocation Device 3G_MSC-A. For all calls this unit is responsible for connecting the new path into the network via interface B'. In specific cases it may be unnecessary to take any explicit action in the 3G_MSC concerning the handover/relocation device. The handover/relocation device interconnections are illustrated in figure 5.
Call Control Procedures 3G_MSC-A y HO/Rel Control Procedures 3G_MSC-A z MAP Procedures 3G_MSC-A
B B
Iu/A Iu/A
RNC/BSC/ 3G_MSC (UE/MS/RNC/BSC) Procedures 1
Iu/A Iu/A
Switch and HO/Rel Device 3G_MSC-A
B B
Figure 4: Functional composition of the controlling 3G_MSC (3G_MSC-A) for supporting handover/relocation For UE/MS to UE/MS calls in the same 3G_MSC the configuration in figure 5b) applies. In this case interface B'' is internal to 3G_MSC-A and does not connect to another 3G_MSC. The handover/relocation device can be either a three-party bridge or a switching facility without three-party connection capabilities. For a three-party bridge configuration the states of the handover/relocation device are as shown in table 2. The three-party configuration exists in the intermediate state. This type of handover/relocation device may reduce the interruption time. However, this may require noise reduction if one of the radio channels is unterminated at some time in the intermediate state. For a handover/relocation device consisting of a simple switch there will be no intermediate state.
3GPP
Release 6
20
3GPP TS 23.009 V6.5.0 (2008-12)
Table 2: States of the handover/relocation device

Case Initial Connection B' to Iu' B' to Iu' B' to A' B' to Iu' B' to B'' Intermediate Connection B' to Iu' and Iu'' B' to Iu' and A'' B' to A' and Iu'' B' to Iu' and B'' B' to B''and B''' Resulting Connection Successful Unsuccessful Procedure Procedure B' to Iu'' B' to Iu' B' to A'' B' to Iu' B' to Iu'' B' to A' B' to B'' B' to B''' B' to Iu' B' to B''
Figure 5a)
Figure 5b) Figure 5c)
Iu/A
Iu/A a) Intra-3G_MSC 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.
Figure 5: Connections in the handover/relocation device (Unit 5)
4.4
3G_MSC-B
For roles and functional composition of the 3G_MSC-B working as pure GSM MSC, please see previous clause ("MSC-B").
4.4.1
Role of 3G_MSC-B
In the Intra-3G_MSC handover/relocation case, the 3G_MSC-B keeps the control of the whole Intra-3G_MSC handover/relocation procedure. 3G_MSC-B notifies MSC-A or 3G_MSC-A of intra-3G_MSC-B InterSystem handover and intra GSM handovers, by using the A-HANDOVER-PERFORMED message. If the security algorithms have been changed during an intra-3G_MSC-B SRNS relocation; or
3GPP
Release 6
21
3GPP TS 23.009 V6.5.0 (2008-12)
if the codec type or codec modes of the Iu Selected codec have been changed during this relocation and the Iu Supported Codecs List was received by 3G_MSC-B before,
then 3G_MSC-B shall indicate the changed parameters, i.e. the selected UMTS algorithm(s) and/or the codec type and codec modes of the Iu Selected codec, to MSC-A or 3G_MSC-A in the MAP-PROCESS-ACCESS-SIGNALLING request. Encapsulated in the MAP-PROCESS-ACCESS-SIGNALLING request 3G_MSC-B shall send: an A-HANDOVER-PERFORMED message, when encapsulated BSSAP is used on the E interface; or an Iu-LOCATION-REPORT message, when encapsulated RANAP is used on the E interface.
On reception of an order to perform location reporting at change of Service Area from 3G_MSC-A, 3G_MSC-B shall be responsible to re-issue the Iu-LOCATION-REPORTING-CONTROL message after subsequent Intra-3G_MSC-B relocations/handovers. This shall be performed immediately after the successful completion of the Relocation Resource Allocation procedure. In a network implementing the "Flexible Iu interface for handover/relocation" option, in the Intra-3G_MSC handover/relocation case, 3G_MSC-B may optionally use a global title based on the Global RNC-Id for the addressing of the Iu interface messages towards the target RNC. For subsequent inter-MSC handover/relocation to an area where "Intra Domain Connection of RAN Nodes to Multiple CN Nodes" is applied, 3G_MSC-B can have multiple target CN nodes for each handover target in a pool-area as specified in 3GPP TS 23.236 [18]. The role of 3G_MSC-B is also to provide transcoder resources. For speech calls in UMTS, 3G_MSC-B shall select an Iu Selected codec from the Iu Supported Codecs List provided by MSC-A/3G_MSC-A in the MAP-PREPAREHANDOVER request. If the Iu Supported Codecs List was not received, 3G_MSC-B shall select the appropriate default speech codec. If an intra-3G_MSC-B intersystem handover to UMTS is performed, and the Iu Supported Codecs List was received by 3G_MSC-B during the basic inter MSC handover/relocation procedure, then 3G_MSC-B shall indicate the Iu Selected codec to MSC-A or 3G_MSC-A in MAP-PROCESS-ACCESS-SIGNALLING request. In the Inter-3G_MSC relocation case, the role of 3G_MSC-B (3G_MSC-B') is only to provide radio resources control within its area. This means that 3G_MSC-B keeps control of the radio resources connection and release towards RNSB. 3G_MSC-B will do some processing on the RANAP information received on the E-interface or the RANAP information received on the Iu-interface whereas it will relay the Direct Transfer information transparently between Iu-interface and E-interface. 3G_MSC-A initiates and drives RANAP procedures towards 3G_MSC-B, while 3G_MSC-B controls them towards its RNSs to the extent that 3G_MSC-B is responsible for the connections of its RNSs. The release of the dedicated resources between 3G_MSC-B and RNS-B is under the responsibility of 3G_MSC-B and RNS-B, and is not directly controlled by 3G_MSC-A. When clearing is to be performed due to information received from RNS-B, 3G_MSC-B shall transfer this clearing indication to 3G_MSC-A, to clear its connection with RNS-B, to terminate the dialogue with 3G_MSC-A through the E-interface, and to release its circuit connection with 3G_MSC-A, if any. In the same way, the release of the connection to its RNS-B, is initiated by 3G_MSC-B, when the dialogue with 3G_MSC-A ends normally and a release is received from the circuit connection with 3G_MSC-A, if any, or when the dialogue with the 3G_MSC-A ends abnormally. When a release is received by 3G_MSC-B for the circuit connection with 3G_MSC-A then 3G_MSC-B shall release the circuit connection. In the Inter-system UMTS to GSM Inter-3G_MSC handover case, the role of 3G_MSC-B (3G_MSC-B') is only to provide radio resources control within its area. This means that 3G_MSC-B keeps control of the radio resources connection and release towards BSS-B. 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 will relay the DTAP information transparently between A-interface and E-interface. 3G_MSC-A initiates and drives a subset of BSSMAP procedures towards 3G_MSC-B, while 3G_MSC-B controls them towards its BSSs to the extent that 3G_MSC-B is responsible for the connections of its BSSs. The release of the dedicated resources between 3G_MSC-B and BSS-B is under the responsibility of 3G_MSC-B and BSS-B, and is not directly controlled by 3G_MSC-A. When clearing is to be performed due to information received from BSS-B, 3G_MSC-B shall transfer this clearing indication to 3G_MSC-A, to clear its connection with BSS-B, to terminate the dialogue with 3G_MSC-A through the E-interface, and to release its circuit connection with MSC-A, if any. In the same way, the release of the connection to its BSS-B, is initiated by
3GPP
Release 6
22
3GPP TS 23.009 V6.5.0 (2008-12)
3G_MSC-B, when the dialogue with 3G_MSC-A ends normally and a release is received from the circuit connection with 3G_MSC-A, if any, or when the dialogue with the MSC-A ends abnormally. When a release is received by 3G_MSC-B for the circuit connection with 3G_MSC-A then 3G_MSC-B shall release the circuit connection. In the Inter-system GSM to UMTS Inter-3G_MSC handover case, the role of 3G_MSC-B (3G_MSC-B') is only to provide radio resources control within its area. This means that 3G_MSC-B keeps control of the radio resources connection and release towards RNS-B. 3G_MSC-B will do some processing on the BSSMAP information received on the E-interface or the RANAP information received on the Iu-interface whereas it will relay the Direct Transfer information transparently between Iu-interface and E-interface. MSC-A initiates and drives a subset of BSSMAP procedures towards 3G_MSC-B, while 3G_MSC-B controls them towards its RNSs to the extent that 3G_MSC-B is responsible for the connections of its RNSs. The release of the dedicated resources between 3G_MSC-B and RNS-B is under the responsibility of 3G_MSC-B and RNS-B, and is not directly controlled by MSC-A. When clearing is to be performed due to information received from RNS-B, 3G_MSC-B shall transfer this clearing indication to MSC-A, to clear its connection with RNS-B, to terminate the dialogue with MSC-A through the E-interface, and to release its circuit connection with MSC-A, if any. In the same way, the release of the connection to its RNS-B, is initiated by 3G_MSC-B, when the dialogue with MSC-A ends normally and a release is received from the circuit connection with MSC-A, if any, or when the dialogue with the MSC-A ends abnormally. When a release is received by 3G_MSC-B for the circuit connection with MSC-A then 3G_MSC-B shall release the circuit connection. At intra-PLMN handover/relocation, 3G_MSC-B shall send Service Handover related information to the BSC/RNC if and only if this Service Handover information is received from 3G_MSC-A. 3G_MSC-B shall not modify Service Handover related information received from a 3G_MSC-A within the same PLMN. For network sharing (see 3GPP TS 25.401 [20], subclause 7.2.3) when SNA information is received by 3G_MSC-B from 3G_MSC-A, 3G MSC-B shall send the SNA information to the RNS. If 3G_MSC-B does not support the optional supplementary service Multicall (see 3GPP TS 23.135) and 3G_MSC-A requests to relocate multiple bearers, 3G_MSC-B shall indicate that it does not support multiple bearers to 3G_MSC-A. If 3G_MSC-B supports the optional supplementary service Multicall (see 3GPP TS 23.135) and UE is engaged with multiple bearers the following description applies: In the basic relocation case, the 3G_MSC-B shall be able to allocate a Handover Number for each bearer. The 3G_MSC-B shall also be able to select some bearers to be handed over according to the priority level defined as RAB parameters in 3GPP TS 25.413 [11] so that the number of bearers will fulfill the maximum number of bearers supported by the 3G_MSC-B. If a selection has to be made between bearers of the same priority level, then the selection criteria are implementation dependent. In the Intra-3G_MSC relocation case, the 3G_MSC-B tries to relocate all bearers to a new RNS. In the subsequent relocation back to the 3G_MSC-A or to a third 3G_MSC-B' case, the 3G_MSC-B tries to request to the 3G_MSC-A to relocate all bearers to the 3G_MSC-A or to the 3G_MSC-B'. In the Intra-3G_MSC inter-system UMTS to GSM handover case and the subsequent inter-system UMTS to GSM handover back to the 3G_MSC-A or to a third MSC-B' case, the 3G_MSC-B shall be able to select one bearer to be handed over according to 3GPP TS 22.129 [9] and tries to handover the selected bearer.
If 3G_MSC-B supports the "Provision of UE Specific Behaviour Information to Network Entities" (see 3GPP TS 23.195 [21]), and if it received UESBI-Iu from MSC-A or 3G_MSC-A during the basic inter-MSC handover/relocation, then 3G_MSC-B shall store the UESBI-Iu and forward it to RNS-B during basic inter-MSC handover/relocation and subsequent intra-3G_MSC-B handover/relocation. If 3G_MSC-B supports SCUDIF calls (see 3GPP TS 23.172 [22]), and if it received information of alternative radio access bearer from 3G_MSC-A during the basic inter-MSC handover/relocation or assignment, then 3G_MSC-B shall store that information and forward it to RNS-B during basic inter-MSC handover/relocation or assignment and subsequent intra-3G_MSC-B handover/relocation.
3GPP
Release 6
23
3GPP TS 23.009 V6.5.0 (2008-12)
4.4.2
Functional composition of 3G_MSC-B and its interfaces for handover/relocation
The functional composition of a 3G_MSC acting as 3G_MSC-B is essentially the same as that of 3G_MSC-A. However, there are some differences. The functional units are as follows (see figure 6). Signalling functions: 1) RNC/BSC/3G_MSC (UE/MS/RNC/BSC) Procedures 3G_MSC-B. This unit is used to control the signalling between the 3G_MSC, RNC, BSC and UE/MS. Interface Iu' is the connection to the old RNC and interface Iu'' is the connection to the new RNC, when an Intra-3G_MSC relocation takes place. Interface Iu' is the connection to the old RNC and interface A'' is the connection to the new BSC, when an Intra-3G_MSC UMTS to GSM handover takes place. Interface A' is the connection to the old BSC and interface Iu'' is the connection to the new RNC, when an Intra-3G_MSC GSM to UMTS handover takes place. Interface x represents the interworking connection to the Handover/Relocation Control Procedures 3G_MSC-B. 2) Call Control Procedures 3G_MSC-B. This unit is used for normal call control and signalling to 3G_MSC-A or MSC-A in the case of inter-system inter-3G_MSC handover. 3) Handover/Relocation Control Procedures 3G_MSC-B. This unit provides both the overall control of the handover/relocation procedure and interworking between the internal interfaces (x, y and z) in 3G_MSC-B. 4) MAP Procedures 3G_MSC-B. This unit is responsible for controlling the exchange of MAP messages between 3G_MSC-A, or MSC-A, and 3G_MSC-B and for signalling to the VLR in 3G_MSC-B. Switching functions: 5) Switch 3G_MSC-B. For all calls this unit is responsible, with RNS-B, for connecting the circuit from 3G_MSC-A, or MSC-A, to RNS-B. This unit may also need to act as a handover/relocation device for Intra3G_MSC handovers/relocation controlled by 3G_MSC-B. In specific cases it may be unnecessary to take any explicit action in the 3G_MSC concerning the handover/relocation device.
3GPP
Release 6
24
3GPP TS 23.009 V6.5.0 (2008-12)
Call Control Procedures 3G_MSC-B y HO/Rel Control Procedures 3G_MSC-B z MAP Procedures 3G_MSC-B
Iu/A Iu/A
RNC/BSC/ 3G_MSC (UE/MS/RNC/BSC) Procedures 1
Iu/A Iu/A
Switch 3G_MSC-B
Figure 6: Functional composition of 3G_MSC-B for supporting handover/relocation
Handover initiation conditions
Handover may be initiated by the network based on RF criteria as measured by the MS or the Network (signal level, Connection quality, power level propagation delay) as well as traffic criteria (e.g. current traffic loading per cell, interference levels, maintenance requests, etc.). In order to determine if a handover is required, due to RF criteria, it is typically the MS that shall take radio measurements from neighbouring cells. These measurements are reported to the serving cell on an event driven or regular basis. When a network determines a need for executing a handover the procedures given in 3GPP TS 08.08 [5], 3GPP TS 25.303 [13], 3GPP TS 25.331 [14] are followed. The decision process used to determine when to perform soft handover or hard handover will typically differ. Depending on the support for soft or hard handover the Intra-MSC and Inter-MSC handover may differ. In the case of an ongoing GSM voice group call (see 3GPP TS 43.068 [3]) the criteria described above shall only apply to the mobile station currently assigned the uplink and other users with a dedicated connection, no actions shall be taken for the listening users.
3GPP
Release 6
25
3GPP TS 23.009 V6.5.0 (2008-12)
General description of the procedures for intra - MSC handovers
This clause gives a brief overview of the procedures that shall be followed when performing Intra-MSC handovers. Detailed explanation of these procedures can be found in 3GPP TS 48.008 [5] and 3GPP TS 24.008 [10]. There are two types of handover that can be considered which involve a BSS and single MSC. These are Internal Handover and External Handover. An Internal Handover is a handover which takes place between channels on a cell or cells controlled by a single BSS, without reference to the MSC, although the MSC maybe informed of its occurrence. This case is not considered in the present document. Handovers between channels on the same cell or between cells on the same BSS which are controlled by the MSC are termed External Handovers and use identical procedures to those for Intra-MSC handovers. Only the Intra-MSC handover case will be considered in the present document. Handovers from a BSS to an RNS controlled by the same 3G_MSC are intra-3G_MSC GSM to UMTS handovers. Handovers from an RNS to a BSS controlled by the same 3G_MSC are intra-3G_MSC UMTS to GSM handovers. There are two types of handover in UMTS: soft handover and hard handover. The first one is fully performed within UTRAN, without involving the core network. The second one may be also performed within UTRAN or GERAN, or between GERAN and UTRAN, or the core network may be involved if the Iur or Iur-g interface between RNSs does not exist. This case of hard handover involving the core network is the only one that is covered in the present document, together with SRNS relocation with Iur or Iur-g interface.
6.1
Procedure for Intra-MSC Handovers
The procedure for a successful External Intra-MSC handover is shown in figure 7. It is assumed that selection of a candidate MS has already taken place within the BSS based upon the criteria presented in clause 5. The exact algorithm, in the BSS, for determining a candidate MS is not addressed in the present document. The procedures discussed do not make use of the Mobile Application Part (MAP), represented by signalling function 4 in figure 2 and figure 3. The procedure described in this clause covers case i).
MS
BSS-A A-Handover-Required A-Handover-Request A-Handover-Request-Ack A-Handover-Command RI-HO-Command A-Handover-Detect RI-HO-Complete A-Handover-Complete A-Clear-Command A-Clear-Complete RI-HO-Access MSC-A BSS-B
MS
Figure 7: Basic External Intra-MSC Handover Procedure
3GPP
Release 6
26
3GPP TS 23.009 V6.5.0 (2008-12)
The successful operation of the procedure is as follows. When the BSS (BSS-A), currently supporting the MS, determines that the MS requires to be handed over it will send an A-HANDOVER-REQUIRED message to the MSC (MSC-A). The A-HANDOVER-REQUIRED message shall contain a list of cells, or a single cell, to which the MS can be handed over. The list of cells shall be given in order of preference based upon operator determined criteria (These criteria are not addressed within the present document and are operator dependent). When the MSC-A receives the AHANDOVER-REQUIRED message it shall begin the process of handing over the MS to a new BSS (BSS-B). (NOTE: BSS-A and BSS-B maybe the same BSS). The MSC-A shall generate an A-HANDOVER-REQUEST message to the selected BSS (BSS-B). When BSS-B receives the A-HANDOVER-REQUEST message it shall take the necessary action to allow the MS to access the radio resource of BSS-B, this is detailed in 3GPP TS 48.058 [6] and in 3GPP TS 45.008 [4]. The switching of the radio resource through the necessary terrestrial resources is detailed in 3GPP TS 24.008 [10] and 3GPP TS 08.08 [5]. Once resource allocation has been completed by BSS-B it shall return an A-HANDOVER-REQUEST-ACK. to MSC-A. When this message is received by MSC-A it shall begin the process of instructing the MS to tune to a new dedicated radio resource. An A-HANDOVER-COMMAND will be sent by the MSC-A to BSS-A. On receipt of the AHANDOVER-COMMAND message BSS-A will send the radio interface message RI-HANDOVER-COMMAND, containing a Handover Reference number previously allocated by BSS-B, to the MS. The MS will then access the new radio resource using the Handover Reference number contained in the RI-HANDOVER-ACCESS message. The number will be checked by BSS-B to ensure it is as expected and the correct MS has been captured. If this is the correct MS then the BSS-B shall send an A-HANDOVER-DETECT to MSC-A. When the MS is successfully communicating with the BSS-B a RI-HANDOVER-COMPLETE message will be sent by the MS to BSS-B. The BSS-B will then send an A-HANDOVER-COMPLETE message to MSC-A. NOTE: The A-HANDOVER-REQUEST-ACK from BSS-B contains the complete Radio Interface message that shall be sent by BSS-A to the MS in the RI-HANDOVER-COMMAND, MSC-A transparently passes this radio interface message onto BSS-A.
After MSC-A has received the A-HANDOVER-COMPLETE message from BSS-B it shall begin to release the resources allocated on BSS-A. In figure 7 the resource is released by using the A-CLEAR-COMMAND sequence. In the case of ongoing GSM voice group calls the clearing of resources on BSS-A shall not be used if the resources are still be used on the down link. If a failure occurs during the handover attempt, for example A-HANDOVER-FAILURE returned from BSS-A or BSSB, then MSC-A will terminate the handover to BSS-B. Under these conditions MSC-A may optionally take one of a number of actions: i) retry the handover to the same cell; ii) select the next cell from the list contained in the A-HANDOVER-REQUIRED message and attempt a handover to the new cell; iii) await the next A-HANDOVER-REQUIRED message; iv) send an A-HANDOVER-REQUIRED-REJECT to BSS-A, if an A-HANDOVER-COMMAND has not already been sent. The exact action taken is dependent on whether the failure occurs before or after the A-HANDOVER-COMMAND has been sent. In all cases the existing connection to the MS shall not be cleared except in the case of expiry of the timer for receipt of A-HANDOVER-COMPLETE. During the period that the MS is not in communication with the network MSC-A shall queue all appropriate messages. All messages shall be delivered to the MS once communication is resumed . In the case of an Intra-MSC handover on MSC-B then the messages shall be queued by MSC-B. In the case of ongoing GSM voice group calls if a failure occurs when handing over a user on a dedicated channel then the procedures described above may optionally be applied.
3GPP
Release 6
27
3GPP TS 23.009 V6.5.0 (2008-12)
6.2
6.2.1
Procedure for Intra-3G_MSC Handovers

Intra-3G_MSC Handover from UMTS to GSM
The procedure for a successful Intra-3G_MSC handover from UMTS to GSM is shown in figure 8. It is assumed that selection of a candidate UE/MS has already taken place within the RNS based upon the criteria presented in clause 5. The exact algorithm, in the RNS, for determining a candidate UE/MS is not addressed in the present document. The procedures discussed do not make use of the Mobile Application Part (MAP), represented by signalling function 4 in figures 4 and 6. The procedure described in this clause covers case ii).
UE/MS RNS-A
Iu-Relocation-Required A-Handover-Request A-Handover-Request-Ack Iu-Relocation-Command RRC-HO-Command A-Handover-Detect RI-HO-Complete A-Handover-Complete Iu-Release-Command Iu-Release-Complete RI-HO-Access
UE/MS 3G_MSC-A BSS-B
Figure 8: Basic Intra-3G_MSC Handover from UMTS to GSM Procedure
6.2.1.1
With no bearer or one bearer
The successful operation of the procedure is as follows. When the RNS (RNS-A), currently supporting the UE/MS, determines that the UE/MS requires to be handed over to GSM it will send an IU-RELOCATION-REQUIRED message to the 3G_MSC (3G_MSC-A). The IU-RELOCATION-REQUIRED message shall contain a single cell, to which the UE/MS can be handed over. When the 3G_MSC-A receives the IU-RELOCATION-REQUIRED message it shall begin the process of handing over the UE/MS to a BSS (BSS-B). The 3G_MSC-A shall generate an A-HANDOVERREQUEST message to the selected BSS (BSS-B). When BSS-B receives the A-HANDOVER-REQUEST message it shall take the necessary action to allow the UE/MS to access the radio resource of BSS-B, this is detailed in 3GPP TS 48.058 6 and in 3GPP TS 45.008 4 . The switching of the radio resource through the necessary terrestrial resources is detailed in 3GPP TS 24.008 10 and 3GPP TS 08.08 5 . Once resource allocation has been completed by BSS-B it shall return an A-HANDOVER-REQUEST-ACK. to 3G_MSC-A. When this message is received by 3G_MSC-A it shall begin the process of instructing the UE/MS to tune to a new dedicated radio resource. An IU-RELOCATION-COMMAND will be sent by the 3G_MSC-A to RNS-A. On receipt of the IU-RELOCATION-COMMAND message RNS-A will send the radio resource control message RRCHANDOVER-COMMAND, containing a Handover Reference number previously allocated by BSS-B, to the UE/MS. The UE/MS will then access the new radio resource using the Handover Reference number contained in the RIHANDOVER-ACCESS message. The number will be checked by BSS-B to ensure it is as expected and the correct UE/MS has been captured. If this is the correct UE/MS then the BSS-B shall send an A-HANDOVER-DETECT to 3G_MSC-A. When the UE/MS is successfully communicating with the BSS-B a RI-HANDOVER-COMPLETE message will be sent by the UE/MS to BSS-B. The BSS-B will then send an A-HANDOVER-COMPLETE message to 3G_MSC-A. NOTE: The A-HANDOVER-REQUEST-ACK from BSS-B contains the complete radio resource control message that shall be sent by RNS-A to the UE/MS in the RRC-HANDOVER-COMMAND, 3G_MSC-A transparently passes this radio interface message onto RNS-A.
3GPP
Release 6
28
3GPP TS 23.009 V6.5.0 (2008-12)
After 3G_MSC-A has received the A-HANDOVER-COMPLETE message from BSS-B it shall begin to release the resources allocated on RNS-A. In figure 8 the resource is released by using the IU-RELEASE-COMMAND sequence. If a failure occurs during the handover attempt, for example A-HANDOVER-FAILURE returned from BSS-B, then 3G_MSC-A will terminate the handover to BSS-B and send an IU-RELOCATION-PREPARATION-FAILURE message to RNS-A. If RNS-A has decided to cancel the handover, it sends IU-RELOCATION-CANCEL message to 3G_MSC-A. The 3G_MSC-A will then terminate the handover towards BSS-B (if initiated) and send IU-RELOCATION-CANCELACKNOWLEDGE message to RNS-A. In all cases the existing connection to the UE/MS shall not be cleared except in the case of expiry of the timer for receipt of A-HANDOVER-COMPLETE. During the period that the UE/MS is not in communication with the network 3G_MSC-A shall queue all appropriate messages. All messages shall be delivered to the UE/MS once communication is resumed. In the case of an Intra3G_MSC handover from UMTS to GSM on 3G_MSC-B then the messages shall be queued by 3G_MSC-B.
6.2.1.2
With multiple bearers (Optional functionality)
If 3G_MSC-A supports the optional supplementary service Multicall (See 3GPP TS 23.135), 3G_MSC-A shall have the following functionality additionally to the description in clause 6.2.1.1. Upon receipt of the IU-RELOCATION-REQUIRED from RNS-A 3G_MSC-A shall select one bearer to be handed over if the UE is engaged with multiple bearers. After that, 3G_MSC-A generates an A-HO-REQUEST message for the selected bearer to BSS-B. When an A-HO-REQUEST-ACK is received from BSS-B, 3G_MSC-A sends IU-RELOCATION-COMMAND, which indicates the bearers not to be handed over as bearers to be released, to RNS-A. After 3G_MSC-A receives A-HO-COMPLETE message from BSS-B, 3G_MSC-A shall release 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.
6.2.2
Intra-3G_MSC GSM to UMTS Handover
The procedure for a successful Intra-3G_MSC handover is shown in figure 9. It is assumed that selection of a candidate UE/MS has already taken place within the BSC based upon the criteria presented in clause 5. The exact algorithm, in the BSC, for determining a candidate UE/MS is not addressed in the present document. The procedures discussed do not make use of the Mobile Application Part (MAP), represented by signalling function 4 in figures 4 and 6. The procedure described in this clause covers case ii). In case of subsequent handover the following applies. If 3G_MSC-B supports location reporting at change of Service Area and if encapsulated BSSAP signalling is used on the E-interface, 3G_MSC-B shall always initiate the Location Reporting Control procedure at change of Service Area towards the target RNS since no request for Location Reporting can be received from MSC-A. In that case, the Location Reporting Control procedure shall be initiated by 3G_MSC-B after the Relocation Resource Allocation procedure has been executed successfully. The change of Service Area shall be reported to MSC-A within an A-HANDOVER-PERFORMED message. In the case of ongoing voice group calls, the handover does not take place since voice group calls are not supported in UMTS.
3GPP
Release 6
29
3GPP TS 23.009 V6.5.0 (2008-12)
UE/MS
BSS-A 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 3G_MSC-A RNS-B
UE
Figure 9: Basic External Intra-3G_MSC GSM to UMTS Handover Procedure The successful operation of the procedure is as follows. When the BSS (BSS-A), currently supporting the UE, determines that the UE requires to be handed over to UMTS it will send an A-HANDOVER-REQUIRED message to the 3G_MSC (3G_MSC-A). The A-HANDOVER-REQUIRED message shall contain a single cell, to which the UE can be handed over. When the 3G_MSC-A receives the A-HANDOVER-REQUIRED message it shall begin the process of handing over the UE to a new RNS (RNS-B). The 3G_MSC-A shall generate an Iu-RELOCATION-REQUEST message to the selected RNS (RNS-B). For handover of a speech call to UTRAN Iu mode, 3G_MSC-A shall include a NAS Synch Indicator in the Iu-RELOCATION-REQUEST message. When RNS-B receives the Iu-RELOCATIONREQUEST message it shall take the necessary action to allow the UE to access the radio resource of RNS-B, this is detailed in the 3GPP TS 25.300 series and the 3GPP TS 25.200 series of Technical Specifications. The switching of the radio resource through the necessary terrestrial resources is detailed in the 3GPP TS 25.430 series and 3GPP TS 25.413 [11]. Once resource allocation has been completed by RNS-B, it shall return an Iu-RELOCATION-REQUEST-ACK. to 3G_MSC-A. When this message is received by 3G_MSC-A it shall begin the process of instructing the UE to tune to a new dedicated radio resource. An A-HANDOVER-COMMAND will be sent by the 3G_MSC-A to BSS-A. On receipt of the A-HANDOVER-COMMAND message BSS-A will send the radio interface message RI-HANDOVERCOMMAND. The UE will then access the new radio resource. On detection of the UE, the RNS-B shall send an IuRELOCATION-DETECT to 3G_MSC-A. When the UE is successfully communicating with the RNS-B an RRCHANDOVER-COMPLETE message will be sent by the UE to RNS-B. The RNS-B will then send an IuRELOCATION-COMPLETE message to 3G_MSC-A. NOTE: The Iu-RELOCATION-REQUEST-ACK from RNS-B contains the complete RRC message that shall be sent by BSS-A to the MS in the RI-HANDOVER-COMMAND, 3G_MSC-A transparently passes this radio interface message onto BSS-A.
After 3G_MSC-A has received the Iu-RELOCATION-COMPLETE message from RNS-B, it shall begin to release the resources allocated on BSS-A. In figure 9 the resource is released by using the A-CLEAR-COMMAND sequence. If a failure occurs during the handover attempt, for example, A-HANDOVER-FAILURE returned from BSS-A or Iu-RELOCATION FAILURE returned from RNS-B, then 3G_MSC-A will terminate the handover to RNS-B. Under these conditions 3G_MSC-A may optionally take one of a number of actions: i) await the next A-HANDOVER-REQUIRED message; ii) send an A-HANDOVER-REQUIRED-REJECT to BSS-A, if an A-HANDOVER-COMMAND has not already been sent. The exact action taken is dependent on whether the failure occurs before or after the A-HANDOVER-COMMAND has been sent.
3GPP
Release 6
30
3GPP TS 23.009 V6.5.0 (2008-12)
In all cases the existing connection to the UE shall not be cleared except in the case of expiry of the timer for receipt of Iu-RELOCATION-COMPLETE. During the period that the UE is not in communication with the network 3G_MSC-A shall queue all appropriate messages. All messages shall be delivered to the UE once communication is resumed. In the case of an Intra-3G_MSC GSM to UMTS handover on 3G_MSC-B then the messages shall be queued by 3G_MSC-B.
6.2.3
Procedure for Intra-3G_MSC SRNS Relocation
The procedure for a successful Intra-3G_MSC SRNS Relocation is shown in figures 10 and 11. SRNS Relocation is used to relocate the serving RNS functionality from one RNS to another. The procedure may or may not involve change of the radio resources assigned for the corresponding UE. Whether or not the Relocation includes change of radio resources assigned for the UE does not affect the SRNS Relocation procedure in the Core Network. In case of subsequent Intra-3G_MSC-B SRNS relocation the following applies: If 3G_MSC-B has previously received an order to perform location reporting at change of Service Area from 3G_MSC-A and if 3G_MSC-B also supports Location Reporting Control, it shall issue the Iu-LOCATIONREPORTING-CONTROL message towards the target RNS immediately after successful completion of relocation. Upon receipt of Iu-LOCATION-REPORT, 3G_MSC-B shall forward it towards 3G_MSC-A via E interface. If 3G_MSC-B supports location reporting at change of Service Area and if encapsulated BSSAP signalling is used on the E-interface, 3G_MSC-B shall always initiate the Location Reporting Control procedure at change of Service Area towards the target RNS, since no request for Location Reporting can be received from MSC-A. In that case the Location Reporting Control procedure shall be initiated by 3G_MSC-B after the Relocation Resource Allocation procedure has been executed successfully. The change of Service Area shall be reported to MSC-A within an A-HANDOVER-PERFORMED message. It is assumed that selection of a candidate UE has already taken place within RNS based upon the criteria presenting in clause 5. The exact algorithm, in RNS, for determining a candidate UE is not addressed in the present document. The procedure discussed does not make use of the Mobile Application Part (MAP), represented by signalling function 4 in figures 4 and 6. The procedure described in this clause covers case ii).
UE RNS-A
Iu-Relocation-Required Iu-Relocation-Request Iu-Relocation-Request-Ack Iu-Relocation-Command Iur-SRNC-Relocation-Commit Iu-Relocation-Detect Iu-Relocation-Complete Iu- Release-Command Iu- Release-Complete
UE 3G_MSC-A RNS-B
Figure 10 Basic intra-3G_MSC SRNS Relocation Procedure
3GPP
Release 6
31
3GPP TS 23.009 V6.5.0 (2008-12)
UE RNS-A
Iu-Relocation-Required Iu-Relocation-Request Iu-Relocation-Request-Ack Iu-Relocation-Command RR-HO-Command Iu-Relocation-Detect RR-HO-Complete Iu-Relocation-Complete Iu- Release-Command Iu- Release-Complete
UE 3G_MSC-A RNS-B
Detection of UE in target RNS
Figure 11 Basic intra-3G_MSC SRNS Relocation Procedure combined with hard change of radio resources (Hard Handover with switch in the Core Network)
6.2.3.1
With no bearer or one bearer
The successful operation of the procedure is as follows. When the Serving RNS (RNS-A) makes the decision to perform the SRNS Relocation procedure it will send an IU-RELOCATION-REQUIRED message to the 3G_MSC (3G_MSC-A). The IU-RELOCATION-REQUIRED message shall contain the identifier of the target RNS to which the Relocation is to be performed. When the 3G_MSC-A receives the IU-RELOCATION-REQUIRED message it shall begin the process of relocating the serving RNS functionality to the new RNS (RNS-B). The 3G_MSC-A shall generate an IU-RELOCATION-REQUEST message to the selected RNS (RNS-B). For the relocation of a speech call to UTRAN Iu mode, 3G_MSC-A shall include the NAS Synch Indicator in the Iu-RELOCATION-REQUEST, if the Iu Selected codec to be used after the relocation is different from the Iu Currently used codec. When RNS-B receives the IU-RELOCATION-REQUEST message it shall take the necessary action to establish the new Iu transport bearers for each Radio Access Bearer related to 3G_MSC-A for the UE in question, this is detailed in the 3GPP TS 25.430 series and 3GPP TS 25.413 [11]. Once resource allocation has been completed by RNS-B it shall return an IU-RELOCATION-REQUESTACKNOWLEDGE to 3G_MSC-A. When this message is received by 3G_MSC-A, and 3G_MSC-A is ready for the move in Serving RNS functionality, it shall indicate the completion of the preparation phase on the core network side for the SRNS Relocation. An IU-RELOCATION-COMMAND message is sent by 3G_MSC-A to RNS-A. RNS-A acts as follows: i) if the procedure is a SRNS Relocation without change of radio resources, which means that the Iur interface between RNS-A and RNS-B can be used for the procedure, the RNS-A shall send IUR-SRNS-RELOCATIONCOMMIT message to the RNS-B to trigger the Relocation execution. See figure 10. ii) if the procedure is a SRNS Relocation with change of radio resources, which means that the Iur interface between RNS-A and RNS-B is not used for the procedure, the RNS-A shall trigger the handover procedure on the air interface by sending the RRC-HANDOVER-COMMAND to the UE. The UE will then access the new radio resources. See figure 11. NOTE: The IU-RELOCATION-REQUEST-ACKNOWLEDGE from RNS-B may optionally contain a transparent container, which is transferred by 3G_MSC-A to the RNS-A using the IU-RELOCATION-COMMAND message.
When the relocation execution trigger is received, RNS-B shall then take the necessary action to assume the role of Serving RNS and shall send an IU-RELOCATION-DETECT message to 3G_MSC-A. When the UE is successfully in communication with the RNS-B, then RNS-B shall send an IU-RELOCATION-COMPLETE message to 3G_MSC-A. After 3G_MSC-A has received the IU-RELOCATION-COMPLETE message from RNS-B, it shall begin to release the resources associated to the RNS-A. In figures 10 and 11, the resources are released by using the IU-RELEASE-COMMAND sequence.
3GPP
Release 6
32
3GPP TS 23.009 V6.5.0 (2008-12)
If a failure occurs during the SRNS Relocation attempt, then 3G_MSC-A will terminate the relocation to RNS-B. For example, if IU-RELOCATION-FAILURE is returned from RNS-B then 3G_MSC-A will terminate the relocation to RNS-B and send IU-RELOCATION-PREPARATION-FAILURE to RNS-A. If IU-RELOCATION-CANCEL is returned from RNS-A, then 3G_MSC-A will terminate the relocation to RNS-B and send IU-RELOCATIONCANCEL-ACKNOWLEDGE to RNS-A. In all cases the existing connection to the UE shall not be cleared except in the case of expiry of the timer for receipt of Iu-RELOCATION-COMPLETE. During the period that the UE is not in communication with the network, 3G_MSC-A shall queue all appropriate messages. All messages shall be delivered to the UE once communication is resumed. In the case of an Intra-3G_MSC SRNS Relocation (with or without change of radio resources) on 3G_MSC-B, then the messages shall be queued by 3G_MSC-B.
6.2.3.2
With multiple bearers (Optional functionality)
If 3G_MSC-A supports the optional supplementary service Multicall (See 3GPP TS 23.135), 3G_MSC-A shall have the following functionality additionally to the description in clause 6.2.3.1. Upon receipt of the IU-RELOCATION-REQUIRED from RNS-A, 3G_MSC-A generates an IU-RELOCATIONREQUEST message, which may include multiple bearers, to RNS-B. When an IU-RELOCATION-REQUEST-ACK is received from RNS-B, 3G_MSC-A sends IU-RELOCATIONCOMMAND, which indicates the bearers failed to set up in RNS-B as bearers to be released, to RNS-A. After 3G_MSC-A receives IU-RELOCATION-COMPLETE message from RNS-B, 3G_MSC-A shall release calls via RNS-B, which has been carried by the bearers failed to set up in RNS-B, and then sends IU-RELEASE-COMMAND to RNS-A.
General description of the procedures for inter - MSC handovers
The following clauses describe two options for the Basic and Subsequent Handover procedures. The first, as described in clauses 7.1 and 7.3 respectively, provides for a circuit connection between MSC-A and MSC-B. The second, as described in clauses 7.2 and 7.4 respectively, provides for a Basic and Subsequent Handover without the provision of a circuit connection between MSC-A and MSC-B. In all the above mentioned clauses, the following principles apply: a) during the handover resource allocation, except for the messages explicitly indicated in b and c below, only the handover related messages that are part of the applicable BSSAP subset - as defined in 3GPP TS 49.008 [7] shall be transferred on the E-interface; b) the trace related messages that are part of the applicable BSSAP subset - as defined in 3GPP TS 49.008 [7] - can be sent by the MSC-A on the E-interface after successful handover resource allocation. In the clauses 7.1 and 7.2, it is however allowed at basic handover initiation on the E-Interface to transfer one trace related message that is part of the applicable BSSAP subset - as defined in 3GPP TS 49.008 [7] - together with the applicable handover related message. The applicable handover related message shall always appear as the first message; c) during the handover resource allocation for subsequent inter-MSC handover according to subclauses 7.3 and 7.4, it is allowed to transfer either DTAP or RANAP Direct Transfer messages on the E-Interface between MSC-A and MSC-B. RANAP Direct Transfer messages shall be used for this purpose if and only if the basic handover procedure was an inter MSC SRNS relocation; d) during the handover execution, ie while the MS is not in communication with the network, the MSC-A shall queue all outgoing BSSAP or RANAP messages until the communication with the MS is resumed; e) during the execution of a basic inter-MSC handover to MSC-B or a subsequent inter-MSC handover to a third MSC-B, only the handover related messages and the A-Clear-Request message that are part of the applicable BSSAP subset - as defined in 3GPP TS 49.008 [7] may be sent by the target MSC on the E-interface;
3GPP
Release 6
33
3GPP TS 23.009 V6.5.0 (2008-12)
f) during a subsequent inter-MSC handover back to MSC-A or to a third MSC-B, MSC-B may initiate either an Iu-Release-Request procedure or an A-Clear-Request procedure on the E-interface. An Iu-Release-Request procedure shall be initiated only if the basic handover procedure was an inter-MSC SRNS relocation; g) finally, during supervision, ie while the MS is not in the area of MSC-A after a successful Inter-MSC handover, the subset of BSSAP procedures and their related messages - as defined in 3GPP TS 49.008 [7] - shall apply on the E-Interface. As the only exception to this rule, in case of a subsequent inter-MSC SRNS relocation back to 3G_MSC-A or to a third 3G_MSC-B, during the relocation resource allocation, the relocation and trace related messages that are part of the applicable RANAP subset - as defined in 3GPP TS 29.108 [15] - shall be transferred on the E-interface (see subclause 8.3, a and b). If a subsequent inter-MSC handover/relocation back to 3G_MSC-A or to a third 3G_MSC-B is cancelled, then the supervision continues, and BSSAP procedures and their related messages shall apply on the E-interface. NOTE: A subsequent inter-MSC SRNS relocation back to 3G_MSC-A or to a third 3G_MSC-B can occur, e.g., if after the basic inter-MSC handover to 3G_MSC-B the MS performed a subsequent intra-3G_MSC-B GSM to UMTS inter-system handover;
h) during the intra-MSC-B handover execution, if any, the MSC-B shall queue all outgoing BSSAP messages until the communication with the MS is resumed.
7.1
Basic handover procedure requiring a circuit connection between MSC-A and MSC-B
The procedure used for successful Inter-MSC Handover is shown in figure 12. Initiation of the handover procedure is described in clause 5. The procedure described in this clause makes use of messages from the 3GPP TS 08.08 [5] and of the transport mechanism from the Mobile Application Part (MAP) (3GPP TS 29.002 [12]). After an Inter-MSC handover further Intra-MSC handovers may occur on MSC-B, these handovers will follow the procedures specified in the previous clause.
3GPP
Release 6
34
3GPP TS 23.009 V6.5.0 (2008-12)
MS/BSS-A MSC-A A-HO-REQUIRED MAP-Prep-Handover req. MSC-B
BSS-B/MS VLR-B MAP-Allocate-Handover-Number req. A-HO-REQUEST A-HO-REQUEST-ACK MAP-Prep-Handover resp. IAM MAP-Send-Handover-Report resp. (1) MAP-Send-Handover-Report req.
A-HO-COMMAND
ACM MAP-Process-Access-Sig req. A-HO-DETECT A-HO-COMPLETE
A-CLR-CMD/COM
MAP-Send-End-Signal req. ANSWER RELEASE MAP-Send-End-Signal resp.
End of call
NOTE 1: Can be sent at any time after the reception of IAM.
Figure 12: Basic Handover Procedure requiring a circuit connection The handover is initiated as described in clause 6.1. (This is represented by A-HO-REQUIRED in figure 12. Upon receipt of the A-HO-REQUIRED from BSS-A, MSC-A shall send a MAP-PREPARE-HANDOVER request to MSC-B including a complete A-HO-REQUEST message. NOTE: MSC-A shall not send further MAP-PREPARE-HANDOVER requests while a MAP-PREPAREHANDOVER response is pending or before any timeouts.
The MAP-PREPARE-HANDOVER request shall carry in the A-HO-REQUEST all information needed by MSC-B for allocating a radio channel, see 3GPP TS 08.08 [5]. For compatibility reasons, the MAP-PREPARE-HANDOVER request will also identify the cell to which the call is to be handed over. For speech calls, MSC-A shall also include the Iu Supported Codecs List to be used by MSC-B for subsequent intra-MSC-B intersystem handover to UMTS and intraMSC-B SRNS relocation. MSC-B will return the MAP-PREPARE-HANDOVER response after having retrieved a Handover Number from its associated VLR (exchange of the messages MAP-allocate-handover-number request and MAP-send-handover-report request). The Handover Number shall be used for routing the connection of the call from MSC-A to MSC-B. If a traffic channel is available in MSC-B the MAP-PREPARE-HANDOVER response, sent to MSC-A will contain the complete A-HO-REQUEST-ACKNOWLEDGE message received from BSS-B, containing the radio resources definition to be sent by BSS-A to the MS and possible extra BSSMAP information, amended by MSC-B due to the possible interworking between the BSSMAP protocol carried on the E-interface and the BSSMAP protocol used on the A-interface. If the traffic channel allocation is queued by BSS-B, the A-QUEUING-INDICATION may optionaly be sent back to MSC-A. The further traffic channel allocation result (A-HO-REQUEST-ACK or A-HOFAILURE) will be transferred to MSC-A using the MAP-PROCESS-ACCESS-SIGNALLING request. If the traffic channel allocation is not possible, the MAP-PREPARE-HANDOVER response containing an A-HO-FAILURE will be sent to MSC-A. MSC-B will do the same if a fault is detected on the identity of the cell where the call has to be handed over. MSC-B simply reports the events related to the dialogue. It is up to MSC-A to decide the action to perform if it receives negative responses or the operation fails due to the expiry of the MAP-PREPARE-HANDOVER timer. If an error related to the TCAP dialogue or to the MAP-PREPARE-HANDOVER request is returned from MSC-B, this will be indicated to MSC-A and MSC-A will terminate the handover attempt. MSC-A may retry the handover attempt
3GPP
Release 6
35
3GPP TS 23.009 V6.5.0 (2008-12)
using the cell identity list, if provided, or may reject the handover attempt towards BSS-A. The existing connection to the MS shall not be cleared. When the A-HO-REQUEST-ACKNOWLEDGE has been received, MSC-A shall establish a circuit between MSC-A and MSC-B by signalling procedures supported by the network. In figure 12 this is illustrated by the messages IAM (Initial Address Message) and ACM (Address Complete Message) of Signalling System no 7. MSC-B awaits the capturing of the MS (clause 6.1) on the radio path when the ACM is sent and MSC-A initiates the handover execution when ACM is received (illustrated by the A-HO-COMMAND and described in the clause 6.1). MSC-B transfers to MSC-A the acknowledgement received from the correct MS (A-HO-DETECT/A-HOCOMPLETE). The A-HO-DETECT, if received, is transferred to MSC-A using the MAP-PROCESS-ACCESSSIGNALLING request. The A-HO-COMPLETE, when received from the correct MS, is included in the MAP-SENDEND-SIGNAL request and sent back to MSC-A. The circuit is through-connected in MSC-A when the A-HO-DETECT or the A-HO-COMPLETE is received from MSC-B. The old radio channel is released when the A-HO-COMPLETE message is received from MSC-B. The sending of the MAP-SEND-END-SIGNAL request starts the MAP supervision timer for the MAP dialogue between MSC-A and MSC-B. When the MAP-SEND-END-SIGNAL request including the A-HO-COMPLETE message is received in MSC-A the resources in BSS-A shall be cleared. In order not to conflict with the PSTN/ISDN signalling system(s) used between MSC-A and MSC-B, MSC-B must generate an answer signal when A-HO-DETECT/COMPLETE is received. MSC-B shall release the Handover Number when the circuit between MSC-A and MSC-B has been established. If the circuit between MSC-A and MSC-B cannot be established (e.g. an unsuccessful backward message is received instead of ACM). MSC-A terminates the inter-MSC handover attempt by sending an appropriate MAP message, for example an ABORT. MSC-A may retry the handover at this point, see clause 6.1. MSC-A shall retain overall call control until the call is cleared by the fixed subscriber or the MS and there is no further call control functions to be performed (e.g. servicing waiting calls, echo cancellers). When MSC-A clears the call to the MS it also clears the call control functions in MSC-A and sends the MAP-SENDEND-SIGNAL response to release the MAP resources in MSC-B. MSC-A may terminate the procedure at any time by sending an appropriate MAP message to MSC-B. If establishment of the circuit between MSC-A and MSC-B has been initiated, the circuit must also be cleared. The handover will be aborted by MSC-A if it detects clearing or interruption of the radio path before the call has been established on MSC-B.
7.2
Basic handover procedure not requiring the establishment of a circuit connection between MSC-A and MSC-B
The basic handover procedures to be used when no circuit connection is required by MSC-A are similar to those described in clause 7.1 for circuit switched calls. The main differences to the procedures described in clause 7.1 relate to the establishment of circuits between the network entities and the Handover Number allocation. In the case of ongoing GSM voice group calls the circuit connections are already established therefore the procedures described in this clause are also applicable. When applied to ongoing voice group calls the clearing of resources on BSS-A shall not be used if the resources are still be used on the down link. Consequently the A-CLEAR-COMMAND message shall not be sent, but an HANDOVER-SUCCEEDED message shall be sent. In the case of basic handover, MSC-A shall specify to MSC-B that no Handover Number is required in the MAPPREPARE-HANDOVER request (see 3GPP TS 29.002 [12]). As for the basic handover using a circuit connection, the A-HO-REQUEST is transmitted at the same time. Any subsequent Handover Number allocation procedure will not be invoked until the completion of the basic handover procedure (see clause: Subsequent Channel Assignment using a circuit connection). MSC-B shall then perform the radio resources allocation as described in clause 7.1. The MAP-PREPARE-HANDOVER response shall be returned to MSC-A including either the response of the radio resources allocation request received from BSS-B (A-HO-REQUEST-ACKNOWLEDGE/A-HO-FAILURE with possible extra BSSMAP information. These extra information are amended by MSC-B due to the possible interworking between the BSSMAP protocol carried on the E-interface and the BSSMAP protocol used on the A-interface) or potentially the A-QUEUING-INDICATION . The basic handover procedure will continue as described in clause 7.1 except that no circuit connection will be established towards MSC-B.
3GPP
Release 6
36
3GPP TS 23.009 V6.5.0 (2008-12)
The relevant case for the basic handover without circuit connection is shown in figure 13. As can be seen the major differences to the equivalent figure 12 is the omission of any circuit establishment messaging and the omission of handover number allocation signalling.
MS/BSS-A MSC-A A-HO-REQUIRED MAP-Prep-Handover req. A-HO-REQUEST MSC-B
BSS-B/MS VLR-B
A-HO-REQUEST-ACK A-HO-COMMAND MAP-Prep-Handover resp. MAP-Process-Access-Sig req. A-CLR-CMD/COM MAP-Send-End-Signal req. A-HO-DETECT A-HO-COMPLETE
End of link
MAP-Send-End-Signal resp.
Figure 13: Basic Handover Procedure without circuit connection
7.3
Procedure for subsequent handover requiring a circuit connection
After the call has been handed over to MSC-B, if the MS leaves the area of MSC-B during the same call, subsequent handover is necessary in order to continue the connection. The following cases apply: i) the MS moves back to the area of MSC-A; ii) the MS moves into the area of a third MSC (MSC-B'). In both cases the call is switched in MSC-A; the circuit between MSC-A and MSC-B shall be released after a successful subsequent handover has been performed.
3GPP
Release 6
37
3GPP TS 23.009 V6.5.0 (2008-12)
7.3.1
Description of subsequent handover procedure i): MSC-B to MSC-A
The procedure for successful handover from MSC-B back to MSC-A is shown in figure 14.
MS/BSS-B MSC-A MSC-B A-HO-REQUIRED MAP-Prep-Sub-Handover req. A-HO-REQUEST A-HO-REQUEST-ACK MAP-Prep-Sub-Handover resp. A-HO-DETECT A-HO-COMPLETE MAP-Send-End-Signal resp. Release A-CLR-CMD/COM A-HO-COMMAND BSS-A/MS VLR-B
Figure 14: Subsequent handover procedure i):successful handover from MSC-B to MSC-A using a circuit connection The procedure is as follows. MSC-B sends the MAP-PREPARE-SUBSEQUENT-HANDOVER request to MSC-A indicating the new MSC number(MSC-A number), indicating also the identity of the cell where the call has to be handed over and including a complete A-HO-REQUEST message. (NOTE: MSC-B shall not send further MAP-PREPARE-SUBSEQUENTHANDOVER requests while a handover attempt is pending or before any timeouts). Since MSC-A is the call controlling MSC, this MSC needs no Handover Number for routing purposes; MSC-A can immediately initiate the search for a free radio channel. When a radio channel can be assigned, MSC-A shall return in the MAP-PREPARE-SUBSEQUENT-HANDOVER response the complete A-HO-REQUEST-ACKNOWLEDGE message received from the BSS-B and possible extra BSSMAP information, amended by MSC-A due to the possible interworking between the BSSMAP protocol carried on the E-interface and the BSSMAP protocol used on the A-interface. If the traffic channel allocation is queued by BSS-B, the A-QUEUING-INDICATION may optionaly be sent back to MSC-B. The further traffic channel allocation result (A-HO-REQUEST-ACK or A-HO-FAILURE) will be transferred to MSC-B using the MAP-FORWARD-ACCESSSIGNALLING request.If a radio channel cannot be assigned or if a fault is detected on the target cell identity, or the target cell identity in the A-HO-REQUEST is not consistent with the target MSC number, the MAP-PREPARESUBSEQUENT-HANDOVER response containing an A-HO-FAILURE message shall be given to MSC-B, in addition MSC-B shall maintain the connection with the MS. If the procedure in MSC-A is successful then MSC-B can request the MS to retune to the new BSS-B on MSC-A. This is illustrated in figure 14 by the A-HO-COMMAND message. The operation is successfully completed when MSC-A receives the A-HO-COMPLETE message. After handover MSC-A shall release the circuit to MSC-B. MSC-A must also terminate the MAP procedure for the basic handover between MSC-A and MSC-B by sending an appropriate MAP message. MSC-B will clear the resources in BSS-A when the MAP-SEND-END-SIGNAL response is received.
3GPP
Release 6
38
3GPP TS 23.009 V6.5.0 (2008-12)
7.3.2
Description of the subsequent handover procedure ii): MSC-B to MSC-B'
The procedure for successful handover from MSC-B to MSC-B' is shown in figure 15. The procedure consists of two parts: a subsequent handover from MSC-B back to MSC-A as described in clause 7.3.1 (the same procedures apply if MSC-A is replaced by 3G_MSC-A); and a basic handover from MSC-A to MSC-B' as described in clause 7.1.
MSC-B sends the MAP-PREPARE-SUBSEQUENT-HANDOVER request to MSC-A indicating a new MSC number (which is the identity of MSC-B'), indicating also the target cell identity and including a complete A-HO-REQUEST, MSC-A then starts a basic handover procedure towards MSC-B'. When MSC-A receives the ACM from MSC-B', MSC-A informs MSC-B that MSC-B' has successfuly allocated the radio resources on BSS-B' side by sending the MAP-PREPARE-SUBSEQUENT-HANDOVER response containing the complete A-HO-REQUEST-ACKNOWLEDGE received from BSS-B'and possible extra BSSMAP information, amended by MSC-A due to the possible interworking between the BSSMAP protocol carried on the E-interface between MSC-A and MSC-B' and the BSSMAP protocol carried on the E-interface between MSC-A and MSC-B. Now MSC-B can start the procedure on the radio path. For MSC-A the handover is completed when it has received the MAP-SEND-END-SIGNAL REQUEST from MSC-B'containing the A-HO-COMPLETE received from the BSS-B'. The circuit between MSC-A and MSC-B is released. MSC-A also sends the MAP-SEND-END-SIGNAL response to MSC-B in order to terminate the original MAP dialogue between MSC-A and MSC-B. MSC-B releases the radio resources when it receives this message. If the traffic channel allocation is queued by the BSS-B', the A-QUEUING-INDICATION may optionaly be sent back to MSC-B. If no radio channel can be allocated by MSC-B' or no circuit between MSC-A and MSC-B' can be established or a fault is detected on the target cell identity or the target cell identity in the A-HO-REQUEST is not consistent with the target MSC number, MSC-A informs MSC-B by using the A-HO-FAILURE message included in the MAP-PREPARE-SUBSEQUENT-HANDOVER response. MSC-B shall maintain the existing connection with the MS. When the subsequent handover is completed, MSC-B' is considered as MSC-B. Any further inter-MSC handover is handled as described above for a subsequent handover.
3GPP
Release 6
39
3GPP TS 23.009 V6.5.0 (2008-12)
MS/BSS MSC-B MSC-A MSC-B A-HO-REQUIRED MAP-Prep-Sub-Handover req. MAP-Prepare-Handover req. MAP-Prepare-Handover resp. 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 MAP-Send-End-Signal resp. A-CLR-CMD/COM (end of call) Release MAP-Send-End-Signal resp. MAP-Allocate-Handover-Number req. MAP-Send-Handover-Report req. VLR-B VLR-B
Figure 15: Subsequent handover procedure ii): Successful handover from MSC-B to MSC-B'requiring a circuit connection
7.4
Procedure for subsequent handover not requiring a circuit connection
As for the subsequent handover with a circuit connection, the same two cases of subsequent handover apply: i) the MS moves back to the area of MSC-A; ii) the MS moves into the area of a third MSC (MSC-B').
3GPP
Release 6
40
3GPP TS 23.009 V6.5.0 (2008-12)
7.4.1
Description of the subsequent handover procedure without circuit connection i): MSC-B to MSC-A
The procedure for successful handover from MSC-B back to MSC-A without circuit connection is shown in figure 16. The only difference with the figure 14, is that no circuit release is needed between MSC-A and MSC-B.
MS/BSS-B MSC-A MSC-B A-HO-REQUIRED MAP-Prep-Sub-Handover req. A-HO-REQUEST A-HO-REQUEST-ACK MAP-Prep-Sub-Handover resp. A-HO-DETECT A-HO-COMPLETE MAP-Send-End-Signal resp. A-CLR-CMD/COM A-HO-COMMAND BSS-A/MS VLR-B
Figure 16: Subsequent handover procedure i): Successful handover from MSC-B to MSC-A not requiring a circuit connection
7.4.2
Description of the subsequent handover procedure without circuit connection ii): MSC-B to MSC-B'
The procedure for successful handover from MSC-B to MSC-B' is shown in figure 17. The procedure consists of two parts: a subsequent handover from MSC-B back to MSC-A as described in clause 7.4.1(the same procedures apply if MSC-A is replaced by 3G_MSC-A); and a basic handover from MSC-A to MSC-B' as described in clause 7.2.
The only difference to the equivalent figure 15 is the omission of the circuit and handover number allocation signallings.
3GPP
Release 6
41
3GPP TS 23.009 V6.5.0 (2008-12)
MS/BSS MSC-B MSC-A MSC-B A-HO-REQUIRED MAP-Prep-Sub-Handover req. MAP-Prepare-Handover req. MAP-Prepare-Handover resp. MAP-Prep-Sub-Ho resp. A-HO-COMMAND A-HO-DETECT MAP-Process-Access-Signalling req. A-HO-COMPLETE MAP-Send-End-Signal req. MAP-Send-End-Signal resp. A-CLR-CMD/COM (end of link) MAP-Send-End-Signal resp. VLR-B VLR-B
Figure 17: Subsequent handover procedure ii): Successful handover from MSC-B to MSC-B' without circuit connection
8
8.1
General Description of the procedures for inter 3G_MSC handovers

Handover UMTS to GSM
The following clauses describe two options for the Basic and Subsequent UMTS to GSM Handover procedures. The first, as described in clauses 8.1.1 and 8.1.3 respectively, provides for a circuit connection between 3G_MSC-A and 3G_MSC-B. The second, as described in clauses 8.1.2 and 8.1.4 respectively, provides for a Basic and Subsequent Handover without the provision of a circuit connection between 3G_MSC-A and 3G_MSC-B. 3G_MSC can also be a pure GSM MSC. In all the above mentioned clauses, the following principles apply: a) during the handover resource allocation, except for the messages explicitly indicated in b and c below, only the handover related messages that are part of the applicable BSSAP subset - as defined in 3GPP TS 49.008 [7] shall be transferred on the E-interface; b) the trace related messages that are part of the applicable BSSAP subset - as defined in 3GPP TS 49.008- can be sent by the 3G_MSC-A on the E-interface after successful handover resource allocation. In the clauses 8.1.1 and 8.1.2, it is however allowed at basic handover initiation on the E-Interface to transfer one trace related message that is part of the applicable BSSAP subset - as defined in 3GPP TS 49.008 [7] - together with the applicable handover related message. The applicable handover related message shall always appear as the first message;
3GPP
Release 6
42
3GPP TS 23.009 V6.5.0 (2008-12)
c) during the handover resource allocation for subsequent inter-MSC inter-system handover according to subclauses 8.1.3 and 8.1.4, it is allowed to transfer either DTAP or RANAP Direct Transfer messages on the EInterface between 3G_MSC-A and 3G_MSC-B. RANAP Direct Transfer messages shall be used for this purpose if and only if the basic handover procedure was an inter MSC SRNS relocation; d) during the handover execution, i.e. while the UE/MS is not in communication with the network, the 3G_MSC-A shall queue all outgoing BSSAP or RANAP messages until the communication with the UE/MS is resumed; e) during the execution of a basic inter-system inter-MSC handover to MSC-B or a subsequent inter-system interMSC handover to a third MSC-B, only the handover related messages and the A-Clear-Request message that are part of the applicable BSSAP subset - as defined in 3GPP TS 49.008 [7] may be sent by the target MSC on the E-interface; f) during a subsequent inter-system inter-MSC handover back to 3G_MSC-A or to a third MSC-B, 3G_MSC-B may initiate either an Iu-Release-Request procedure or an A-Clear-Request procedure on the E-interface. An IuRelease-Request procedure shall be initiated only if the basic handover procedure was an inter-MSC SRNS relocation; g) finally, during supervision, i.e. while the UE/MS is not in the area of 3G_MSC-A after a successful Inter3G_MSC handover, the subset of BSSAP procedures and their related messages - as defined in 3GPP TS 49.008 [7] - shall apply on the E-Interface. As the only exception to this rule, in case of a subsequent inter-MSC SRNS relocation back to 3G_MSC-A or to a third 3G_MSC-B, during the relocation resource allocation, the relocation and trace related messages that are part of the applicable RANAP subset - as defined in 3GPP TS 29.108 [15] - shall be transferred on the E-interface (see subclause 8.3, a and b). If a subsequent inter-MSC handover/relocation back to 3G_MSC-A or to a third 3G_MSC-B is cancelled, then the supervision continues, and BSSAP procedures and their related messages shall apply on the E-interface. NOTE: A subsequent inter-MSC SRNS relocation back to 3G_MSC-A or to a third 3G_MSC-B can occur, e.g., if after the basic inter-MSC handover to 3G_MSC-B the MS performed a subsequent intra-3G_MSC-B GSM to UMTS inter-system handover;
h) during the intra-3G_MSC -B handover execution, if any, the 3G_MSC -B shall queue all outgoing BSSAP or RANAP messages until the communication with the UE/MS is resumed.
8.1.1
Basic Handover procedure requiring a circuit connection between 3G_MSC -A and MSC-B
The procedure used for successful Inter-3G_MSC UMTS to GSM Handover is shown in figure 18. Initiation of the UMTS to GSM handover procedure is described in clause 5. The procedure described in this clause makes use of messages from the 3GPP TS 08.08 and of the transport mechanism from the Mobile Application Part (MAP) (3GPP TS 29.002 [12]). After an Inter-3G_MSC relocation/handover, Intra-3G_MSC UMTS to GSM handover may occur on 3G_MSC -B, this handover will follow the procedures specified in a previous clause.
3GPP
Release 6
43
3GPP TS 23.009 V6.5.0 (2008-12)
UE/MS/RNS-A 3G_MSC-A Iu-RELOCATIONREQUIRED MAP-Prep-Handover req. MSC-B
BSS-B/MS/UE VLR-B MAP-Allocate-Handover-Number req. A-HO-REQUEST A-HO-REQUEST-ACK MAP-Prep-Handover resp. IAM MAP-Send-Handover-Report resp. (1) MAP-Send-Handover-Report req.
Iu-RELOCATIONCOMMAND
ACM MAP-Process-Access-Sig req. A-HO-DETECT A-HO-COMPLETE
Iu-RELEASECMD/COM
MAP-Send-End-Signal req. ANSWER RELEASE MAP-Send-End-Signal resp.
End of call
Figure 18: Basic UMTS to GSM Handover Procedure requiring a circuit connection
8.1.1.1
With one circuit connection
The UMTS to GSM handover is initiated as described in clause 6.2.1. (This is represented by Iu-RELOCATIONREQUIRED in figure 18). Upon receipt of the Iu-RELOCATION-REQUIRED from RNS-A, 3G_MSC-A shall send a MAP-PREPARE-HANDOVER request to MSC-B including a complete A-HO-REQUEST message. NOTE: 3G_MSC-A shall not send further MAP-PREPARE-HANDOVER requests while a MAP-PREPAREHANDOVER response is pending or before any timeouts.
3GPP
Release 6
44
3GPP TS 23.009 V6.5.0 (2008-12)
The MAP-PREPARE-HANDOVER request shall carry in the A-HO-REQUEST all information needed by MSC-B for allocating a radio channel, see 3GPP TS 08.08. For compatibility reasons, the MAP-PREPARE-HANDOVER request will also identify the cell to which the call is to be handed over. For speech calls, 3G_MSC-A shall also include the Iu Supported Codecs List to be used by MSC-B for subsequent intra-MSC-B intersystem handover to UMTS and intraMSC-B SRNS relocation. MSC-B will return the MAP-PREPARE-HANDOVER response after having retrieved a Handover Number from its associated VLR (exchange of the messages MAP-allocate-handover-number request and MAP-send-handover-report request). The Handover Number shall be used for routing the connection of the call from 3G_MSC-A to MSC-B. If a traffic channel is available in MSC-B the MAP-PREPARE-HANDOVER response, sent to 3G_MSC-A will contain the complete A-HO-REQUEST-ACKNOWLEDGE message received from BSS-B, containing the radio resources definition to be sent by RNS-A to the UE/MS and possible extra BSSMAP information, amended by MSC-B due to the possible interworking between the BSSMAP protocol carried on the E-interface and the BSSMAP protocol used on the A-interface. If the traffic channel allocation is queued by BSS-B, the A-QUEUING-INDICATION may optionally be sent back to 3G_MSC-A. The further traffic channel allocation result (A-HO-REQUEST-ACK or AHO-FAILURE) will be transferred to 3G_MSC-A using the MAP-PROCESS-ACCESS-SIGNALLING request. If the traffic channel allocation is not possible, the MAP-PREPARE-HANDOVER response containing an A-HO-FAILURE will be sent to 3G_MSC-A. MSC-B will do the same if a fault is detected on the identity of the cell where the call has to be handed over. MSC-B simply reports the events related to the dialogue. It is up to 3G_MSC-A to decide the action to perform if it receives negative responses or the operation fails due to the expiry of the MAP-PREPARE-HANDOVER timer. If an error related to the TCAP dialogue or to the MAP-PREPARE-HANDOVER request is returned from MSC-B, this will be indicated to 3G_MSC-A and 3G_MSC-A will terminate the handover attempt. 3G_MSC-A rejects the handover attempt towards RNS-A. The existing connection to the UE/MS shall not be cleared. When the A-HO-REQUEST-ACKNOWLEDGE has been received, 3G_MSC-A shall establish a circuit between 3G_MSC-A and MSC-B by signalling procedures supported by the network. In figure 18 this is illustrated by the messages IAM (Initial Address Message) and ACM (Address Complete Message) of Signalling System no 7. MSC-B awaits the capturing of the UE/MS (clause 6.2.1) on the radio path when the ACM is sent and 3G_MSC-A initiates the UMTS to GSM handover execution when ACM is received (illustrated by the Iu-RELOCATION-COMMAND and described in the clause 6.2.1). 3G_MSC-A removes the transcoder from the path to the other party. As handover to GSM means that a transcoder is inserted in the BSS-B then G.711 [16] is assumed on the E-interface. MSC-B transfers to 3G_MSC-A the acknowledgement received from the correct UE/MS (A-HO-DETECT/A-HOCOMPLETE). The A-HO-DETECT, if received, is transferred to 3G_MSC-A using the MAP-PROCESS-ACCESSSIGNALLING request. The A-HO-COMPLETE, when received from the correct UE/MS, is included in the MAPSEND-END-SIGNAL request and sent back to 3G_MSC-A. The circuit is through connected in 3G_MSC-A when the A-HO-DETECT or the A-HO-COMPLETE is received from MSC-B. The old radio channel is released when the AHO-COMPLETE message is received from MSC-B. The sending of the MAP-SEND-END-SIGNAL request starts the MAP supervision timer for the MAP dialogue between 3G_MSC-A and MSC-B. When the MAP-SEND-ENDSIGNAL request including the A-HO-COMPLETE message is received in 3G_MSC-A, the resources in RNS-A shall be cleared. In order not to conflict with the PSTN/ISDN signalling system(s) used between 3G_MSC-A and MSC-B, MSC-B must generate an answer signal when A-HO-DETECT/COMPLETE is received. MSC-B shall release the Handover Number when the circuit between 3G_MSC-A and MSC-B has been established. If the circuit between 3G_MSC-A and MSC-B cannot be established, (e.g. an unsuccessful backward message is received instead of ACM), 3G_MSC-A terminates the inter-3G_MSC UMTS to GSM handover attempt by sending an appropriate MAP message, for example an ABORT. 3G_MSC-A shall retain overall call control until the call is cleared by the fixed subscriber or the UE/MS and there is no further call control functions to be performed (e.g. servicing waiting calls, echo cancellers). When 3G_MSC-A clears the call to the UE/MS it also clears the call control functions in 3G_MSC-A and sends the MAP-SEND-END-SIGNAL response to release the MAP resources in MSC-B. 3G_MSC-A may terminate the procedure at any time by sending an appropriate MAP message to MSC-B. If establishment of the circuit between 3G_MSC-A and MSC-B has been initiated, the circuit must also be cleared. The UMTS to GSM handover will be aborted by 3G_MSC-A if it detects clearing or interruption of the radio path before the call has been established on MSC-B.
3GPP
Release 6
45
3GPP TS 23.009 V6.5.0 (2008-12)
8.1.1.2
With multiple circuit connections (Optional functionality)
If 3G_MSC-A supports the optional supplementary service Multicall (See 3GPP TS 23.135), 3G_MSC-A shall have the following functionality additionally to the description in clause 8.1.1.1. Upon receipt of the IU-RELOCATION-REQUIRED from RNS-A 3G_MSC-A shall select one bearer to be handed over if the UE is engaged with multiple bearers. After that, the 3G_MSC-A generates an A-HO-REQUEST message for the selected bearer and sends it to MSC-B over MAP-PREPARE-HANDOVER request. When MAP-PREPARE-HANDOVER response including an A-HO-REQUEST-ACK is received from MSC-B, 3G_MSC-A sends IU-RELOCATION-COMMAND, which indicates the bearers not to be handed over as bearers to be released, to RNS-A. After 3G_MSC-A receives MAP-SEND-END-SIGNAL request from MSC-B, 3G_MSC-A shall release calls via MSCB, which has been carried by the bearers not to be handed over, and then 3G_MSC-A sends IU-RELEASECOMMAND to RNS-A.
8.1.2
Basic UMTS to GSM Handover procedure not requiring the establishment of a circuit connection between 3G_MSC-A and MSC-B
The basic UMTS to GSM handover procedures to be used when no circuit connection is required by 3G_MSC-A are similar to those described in clause 8.1.1 for circuit switched calls. The main differences to the procedures described in clause 8.1.1 relate to the establishment of circuits between the network entities and the Handover Number allocation. In the case of basic UMTS to GSM handover, 3G_MSC-A shall specify to MSC-B that no Handover Number is required in the MAP-PREPARE-HANDOVER request (see 3GPP TS 29.002 [12]). As for the basic UMTS to GSM handover using a circuit connection, the A-HO-REQUEST is transmitted at the same time. Any subsequent Handover Number allocation procedure will not be invoked until the completion of the basic UMTS to GSM handover procedure (see clause: Subsequent Channel Assignment using a circuit connection). MSC-B shall then perform the radio resources allocation as described in clause 8.1.1. The MAP-PREPARE-HANDOVER response shall be returned to 3G_MSC-A including either the response of the radio resources allocation request received from BSS-B (A-HO-REQUESTACKNOWLEDGE/A-HO-FAILURE with possible extra BSSMAP information. These extra information are amended by MSC-B due to the possible interworking between the BSSMAP protocol carried on the E-interface and the BSSMAP protocol used on the A-interface) or potentially the A-QUEUING-INDICATION. The basic UMTS to GSM handover procedure will continue as described in subclause 8.1.1 except that no circuit connection will be established towards MSC-B. The relevant case for the basic UMTS to GSM handover without circuit connection is shown in figure 19. As can be seen the major differences to the equivalent figure 18 is the omission of any circuit establishment messaging and the omission of handover number allocation signalling.
3GPP
Release 6
46
3GPP TS 23.009 V6.5.0 (2008-12)
UE/MS/RNS-A 3G_MSC-A Iu-RELOCATIONREQUIRED MAP-Prep-Handover req. MSC-B
BSS-B/UE/MS VLR-B
A-HO-REQUEST A-HO-REQUEST-ACK Iu-RELOCATIONCOMMAND MAP-Prep-Handover resp. MAP-Process-Access-Sig req. Iu-RELEASECMD/COM MAP-Send-End-Signal req. A-HO-DETECT A-HO-COMPLETE
End of link
Figure 19: Basic UMTS to GSM Handover Procedure without circuit connection
8.1.3
Procedure for subsequent UMTS to GSM handover requiring a circuit connection
After the call has been handed over to 3G_MSC-B, if the UE/MS leaves the area of 3G_MSC-B during the same call and enters a GSM area, subsequent UMTS to GSM handover is necessary in order to continue the connection. The following cases apply: i) the UE/MS moves back to the area of MSC-A; ii) the UE/MS moves into the area of a third MSC (MSC-B'). In both cases the call is switched in 3G_MSC-A; the circuit between 3G_MSC-A and MSC-B shall be released after a successful subsequent handover has been performed the same procedures apply if 3G_MSC-A is replaced by MSC-A.
3GPP
Release 6
47
3GPP TS 23.009 V6.5.0 (2008-12)
8.1.3.1
Description of subsequent UMTS to GSM handover procedure i): 3G_MSC-B to MSC-A
The procedure for successful UMTS to GSM handover from MSC-B back to 3G_MSC-A is shown in figure 20.
UE/MS/BSS-B MSC-A 3G_MSC-B Iu-RELOCATIONREQUIRED RNS-A/UE/MS VLR-B
MAP-Prep-Sub-Handover req. A-HO-REQUEST A-HO-REQUEST-ACK MAP-Prep-Sub-Handover resp. A-HO-DETECT A-HO-COMPLETE MAP-Send-End-Signal resp. Release
Iu-RELOCATIONCOMMAND Iu-RELEASECMD/COM
Figure 20: Subsequent UMTS to GSM handover procedure i): successful UMTS to GSM handover from 3G_MSC-B to MSC-A using a circuit connection
8.1.3.1.1
The procedure is as follows. 3G_MSC-B sends the MAP-PREPARE-SUBSEQUENT-HANDOVER request to MSC-A indicating the new MSC number (MSC-A number), indicating also the identity of the cell where the call has to be handed over and including a complete A-HO-REQUEST message. (NOTE: 3G_MSC-B shall not send further MAP-PREPARE-SUBSEQUENTHANDOVER requests while a handover attempt is pending or before any timeouts). Since MSC-A is the call controlling MSC, this MSC needs no Handover Number for routing purposes; MSC-A can immediately initiate the search for a free radio channel. When a radio channel can be assigned, MSC-A shall return in the MAP-PREPARE-SUBSEQUENT-HANDOVER response the complete A-HO-REQUEST-ACKNOWLEDGE message received from the BSS-B and possible extra BSSMAP information, amended by MSC-A due to the possible interworking between the BSSMAP protocol carried on the E-interface and the BSSMAP protocol used on the A-interface. If the traffic channel allocation is queued by BSS-B, the A-QUEUING-INDICATION may optionally be sent back to 3G_MSC-B. The further traffic channel allocation result (A-HO-REQUEST-ACK or A-HO-FAILURE) will be transferred to 3G_MSC-B using the MAP-FORWARDACCESS-SIGNALLING request. If a radio channel cannot be assigned or if a fault is detected on the target cell identity, or the target cell identity in the A-HO-REQUEST is not consistent with the target MSC number, the MAP-PREPARE-SUBSEQUENT-HANDOVER response containing an A-HO-FAILURE message shall be given to 3G_MSC-B, in addition 3G_MSC-B shall maintain the connection with the UE/MS. If the procedure in MSC-A is successful then 3G_MSC-B can request the UE/MS to retune to the new BSS-B on MSC-A. This is illustrated in figure 20 by the Iu-RELOCATION-COMMAND message. The operation is successfully completed when MSC-A receives the A-HO-COMPLETE message. After UMTS to GSM handover MSC-A shall release the circuit to 3G_MSC-B. MSC-A must also terminate the MAP procedure for the basic UMTS to GSM handover between MSC-A and 3G_MSC-B by sending an appropriate MAP message. 3G_MSC-B will clear the resources in RNS-A when the MAP-SEND-END-SIGNAL response is received.
8.1.3.1.2
If 3G_MSC-B supports the optional supplementary service Multicall (See 3GPP TS 23.135), 3G_MSC-B shall have the following functionality additionally to the description in clause 8.1.3.1.1.
3GPP
Release 6
48
3GPP TS 23.009 V6.5.0 (2008-12)
Upon receipt of the IU-RELOCATION-REQUIRED from RNS-A which indicates the target is BSS, 3G_MSC-B shall select one bearer to be handed over if the UE is engaged with multiple bearers. After that, the 3G_MSC-B generates an A-HO-REQUEST message for the selected bearer and sends it to 3G_MSC-A over MAP-PREPARE-SUBSEQUENTHANDOVER request with indication of RAB ID of the selected bearer. When MAP-PREPARE-SUBSEQUENT-HANDOVER response including an A-HO-REQUEST-ACK is received from the 3G_MSC-A, 3G_MSC-B sends IU-RELOCATION-COMMAND, which indicates the bearers not to be handed over as bearers to be released, to RNS-A. After 3G_MSC-A receives A-HO-COMPLETE message from BSS-B, 3G_MSC-A shall release calls via BSS-B, which has been carried by the bearers not to be handed over, and then 3G_MSC-A sends MAP-SEND-END-SIGNAL response to 3G_MSC-B.
8.1.3.2
Description of subsequent UMTS to GSM handover procedure ii): 3G_MSC-B to MSC-B'
The procedure for successful UMTS to GSM handover from 3G_MSC-B to MSC-B' is shown in figure 21. The procedure consists of two parts: a subsequent UMTS to GSM handover from 3G_MSC-B back to 3G_MSC-A as described in clause 8.1.3.1 (the same procedures apply if 3G_MSC-A is replaced by MSC-A); and a basic handover from 3G_MSC-A to MSC-B' as described in clause 7.1.
8.1.3.2.1
3G_MSC-B sends the MAP-PREPARE-SUBSEQUENT-HANDOVER request to 3G_MSC-A indicating a new MSC number (which is the identity of MSC-B'), indicating also the target cell identity and including a complete A-HO-REQUEST, 3G_MSC-A then starts a basic handover procedure towards MSC-B'. When 3G_MSC-A receives the ACM from MSC-B', 3G_MSC-A informs 3G_MSC-B that MSC-B' has successfully allocated the radio resources on BSS-B' side by sending the MAP-PREPARE-SUBSEQUENT-HANDOVER response containing the complete A-HO-REQUEST-ACKNOWLEDGE received from BSS-B' and possible extra BSSMAP information, amended by 3G_MSC-A due to the possible interworking between the BSSMAP protocol carried on the E-interface between 3G_MSC-A and MSC-B' and the BSSMAP protocol carried on the E-interface between 3G_MSC-A and 3G_MSC-B. Now 3G_MSC-B can start the procedure on the radio path. For 3G_MSC-A the UMTS to GSM handover is completed when it has received the MAP-SEND-END-SIGNAL REQUEST from MSC-B' containing the A-HO-COMPLETE received from the BSS-B'. The circuit between 3G_MSC-A and 3G_MSC-B is released. 3G_MSC-A also sends the MAP-SEND-END-SIGNAL response to 3G_MSC-B in order to terminate the original MAP dialogue between 3G_MSC-A and 3G_MSC-B. 3G_MSC-B releases the radio resources when it receives this message. If the traffic channel allocation is queued by the BSS-B', the A-QUEUING-INDICATION may optionally be sent back to 3G_MSC-B. If no radio channel can be allocated by MSC-B' or no circuit between 3G_MSC-A and MSC-B' can be established or a fault is detected on the target cell identity or the target cell identity in the A-HO-REQUEST is not consistent with the target MSC number, 3G_MSC-A informs 3G_MSC-B by using the A-HO-FAILURE message included in the MAP-PREPARE-SUBSEQUENT-HANDOVER response. 3G_MSC-B shall maintain the existing connection with the UE/MS. When the subsequent UMTS to GSM handover is completed, MSC-B' is considered as MSC-B. Any further inter-MSC handover is handled as described earlier for a subsequent handover.
8.1.3.2.2
If 3G_MSC-B supports the optional supplementary service Multicall (See 3GPP TS 23.135), 3G_MSC-B shall have the following functionality additionally to the description in clause 8.1.3.2.1. Upon receipt of the IU-RELOCATION-REQUIRED from RNS-B 3G_MSC-B shall select one bearer to be handed over if the UE is engaged with multiple bearers. After that, the 3G_MSC-B generates an A-HO-REQUEST message for the selected bearer and sends it to 3G_MSC-A over MAP-PREPARE-SUBSEQUENT-HANDOVER request with indication of RAB ID of the selected bearer.
3GPP
Release 6
49
3GPP TS 23.009 V6.5.0 (2008-12)
Upon receipt of the MAP-PREPARE-SUBSEQUENT-HANDOVER request from 3G_MSC-B, 3G_MSC-A starts a basic handover procedure towards MSC-B'. When 3G_MSC-A receives the ACM from MSC-B', 3G_MSC-A informs 3G_MSC-B that MSC-B' has successfully allocated the radio resources on BSS-B' side by sending the MAP-PREPARE-SUBSEQUENT-HANDOVER response containing the complete A-HO-REQUEST-ACK received from BSS-B' and possible extra BSSAP information, amended by 3G_MSC-A due to the possible interworking between the BSSMAP protocol carried on the E-interface between 3G_MSC-A and MSC-B' and the BSSMAP protocol carried on the E-interface between 3G_MSC-A and 3G_MSC-B. When MAP-PREPARE-SUBSEQUENT-HANDOVER response including an A-HO-REQUEST-ACK is received from 3G_MSC-A, 3G_MSC-B sends IU-RELOCATION-COMMAND, which indicates the bearers not to be handed over as bearers to be released, to RNS-A. After 3G_MSC-A receives MAP-SEND-END-SIGNAL request from MSC-B', 3G_MSC-A shall release calls via MSC-B', which has been carried by the bearers not to be handed over, and then 3G_MSC-A sends MAP-SEND-ENDSIGNAL response to 3G_MSC-B.
3GPP
Release 6
50
3GPP TS 23.009 V6.5.0 (2008-12)
UE/MS/BSS/RNS MSC-B 3G_MSC-A 3G_MSC-B VLR-B VLR-B
Iu-RELOCATIONREQUIRED MAP-Prep-Sub-Handover req. MAP-Prepare-Handover req. MAP-Prepare-Handover resp. IAM MAP-Send-Handover-Rep. resp. (1) ACM MAP-Prep-Sub-Ho resp. Iu-RELOCATION-CMD A-HO-DETECT MAP-Process-Access-Signalling req. A-HO-COMPLETE MAP-Send-End-Signal req. Answer Release MAP-Send-End-Signal resp. Iu-RELEASE-CMD/COM (end of call) Release MAP-Send-End-Signal resp. MAP-Allocate-Handover-Number req. MAP-Send-Handover-Report req.
Figure 21: Subsequent handover procedure ii): Successful UMTS to GSM handover from 3G_MSC-B to MSC-B' requiring a circuit connection
8.1.4
Procedure for subsequent UMTS to GSM handover not requiring a circuit connection
As for the subsequent UMTS to GSM handover with a circuit connection, the same two cases of subsequent handover apply: i) the UE/MS moves back to the area of MSC-A; ii) the UE/MS moves into the area of a third MSC (MSC-B').
3GPP
Release 6
51
3GPP TS 23.009 V6.5.0 (2008-12)
8.1.4.1
Description of subsequent UMTS to GSM handover procedure i): 3G_MSC-B to MSC-A
The procedure for successful UMTS to GSM handover from 3G_MSC-B back to MSC-A without circuit connection is shown in figure 22. The only difference with the figure 20, is that no circuit release is needed between MSC-A and 3G_MSC-B.
UE/MS/BSS-B MSC-A 3G_MSC-B Iu-RELOCATIONREQUIRED RNS-A/UE/MS VLR-B
MAP-Prep-Sub-Handover req. A-HO-REQUEST A-HO-REQUEST-ACK MAP-Prep-Sub-Handover resp. A-HO-DETECT A-HO-COMPLETE MAP-Send-End-Signal resp.
Iu-RELOCATIONCOMMAND Iu-RELEASECMD/COM
Figure 22: Subsequent UMTS to GSM handover procedure i): Successful UMTS to GSM handover from 3G_MSC-B to MSC-A not requiring a circuit connection
8.1.4.2
Description of the subsequent UMTS to GSM handover procedure without circuit connection ii): 3G_MSC-B to MSC-B'
The procedure for successful UMTS to GSM handover from 3G_MSC-B to MSC-B' is shown in figure 23. The procedure consists of two parts: a subsequent UMTS to GSM handover from 3G_MSC-B back to 3G_MSC-A as described in clause 8.1.4.1 (the same procedures apply if 3G_MSC-A is replaced by MSC-A); and a basic handover from 3G_MSC-A to MSC-B' as described in clause 7.2.
3GPP
Release 6
52
3GPP TS 23.009 V6.5.0 (2008-12)
UE/MS/BSS/RNS MSC-B 3G_MSC-A 3G_MSC-B Iu-RELOCATION-REQUIRED MAP-Prep-Sub-Handover req. MAP-Prepare-Handover req. MAP-Prepare-Handover resp. MAP-Prep-Sub-Ho resp. Iu-RELOCATION-CMD A-HO-DETECT MAP-Process-Access-Signalling req. A-HO-COMPLETE MAP-Send-End-Signal req. MAP-Send-End-Signal resp. Iu-RELEASE-CMD/COM (end of link) MAP-Send-End-Signal resp. VLR-B VLR-B
Figure 23: Subsequent UMTS to GSM handover procedure ii): Successful UMTS to GSM handover from 3G_MSC-B to MSC-B' without circuit connection
8.2
Handover GSM to UMTS
The following clauses describe two options for the Basic and Subsequent GSM to UMTS Handover procedures. The first, as described in clauses 8.2.1 and 8.2.3 respectively, provides for a circuit connection between (3G_)MSC-A and (3G_)MSC-B. The second, as described in clauses 8.2.2 and 8.2.4 respectively, provides for a Basic and Subsequent Handover without the provision of a circuit connection between (3G_)MSC-A and (3G_)MSC-B. In all the above mentioned clauses, the following principles apply: a) during the handover resource allocation, except for the messages explicitly indicated in b and c below, only the handover related messages that are part of the applicable BSSAP subset - as defined in 3GPP TS 49.008 [7] shall be transferred on the E-interface; b) the trace related messages that are part of the applicable BSSAP subset - as defined in 3GPP TS 49.008 [7] - can be sent by the MSC-A on the E-interface after successful handover resource allocation. In the clauses 8.2.1 and 8.2.2, it is however allowed at basic handover initiation on the E-Interface to transfer one trace related message that is part of the applicable BSSAP subset - as defined in 3GPP TS 49.008 [7] - together with the applicable handover related message. The applicable handover related message shall always appear as the first message; c) during the handover resource allocation for subsequent inter-MSC inter-system handover according to subclauses 8.2.3 and 8.2.4, it is allowed to transfer either DTAP or RANAP Direct Transfer messages on the EInterface between MSC-A and 3G_MSC-B. RANAP Direct Transfer messages shall be used for this purpose if and only if the basic handover procedure was an inter MSC SRNS relocation; d) If 3G_MSC-B or 3G-MSC-B supports location reporting at change of Service Area, 3G_MSC-B or 3G_MSCB' shall always initiate the Location Reporting Control procedure at change of Service Area towards the target RNS since no request for Location Reporting can be received from MSC-A. In that case, the Location Reporting
3GPP
Release 6
53
3GPP TS 23.009 V6.5.0 (2008-12)
Control procedure shall be initiated by 3G_MSC-B or 3G-MSC-B after the Relocation Resource Allocation procedure has been executed successfully. The change of Service Area shall be reported to MSC-A within an AHANDOVER-PERFORMED message; e) during the handover execution, i.e. while the UE/MS is not in communication with the network, the MSC-A shall queue all outgoing BSSAP or RANAP messages until the communication with the UE/MS is resumed; f) during the execution of a basic inter-system inter-MSC handover to 3G_MSC-B or a subsequent inter-system inter-MSC handover to a third 3G-MSC-B, only the handover related messages and the A-Clear-Request message that are part of the applicable BSSAP subset - as defined in 3GPP TS 49.008 [7] may be sent by the target MSC on the E-interface; g) during a subsequent inter-system inter-MSC handover back to 3G_MSC-A or to a third 3G_MSC-B, 3G_MSCB may initiate either an Iu-Release-Request procedure or an A-Clear-Request procedure on the E-interface. An Iu-Release-Request procedure shall be initiated only if the basic handover procedure was an inter-MSC SRNS relocation; h) finally, during supervision, i.e. while the UE/MS is not in the area of MSC-A after a successful Inter-3G_MSC GSM to UMTS handover, the subset of BSSAP procedures and their related messages - as defined in 3GPP TS 49.008 [7] - shall apply on the E-Interface. As the only exception to this rule, in case of a subsequent inter-MSC SRNS relocation back to 3G_MSC-A or to a third 3G_MSC-B, during the relocation resource allocation, the relocation and trace related messages that are part of the applicable RANAP subset - as defined in 3GPP TS 29.108 [15] - shall be transferred on the E-interface (see subclause 8.3, a and b). If a subsequent inter-MSC handover/relocation back to 3G_MSC-A or to a third 3G_MSC-B is cancelled, then the supervision continues, and BSSAP procedures and their related messages shall apply on the E-interface; i) during the intra-3G_MSC-B GSM to UMTS handover execution, if any, the 3G_MSC-B shall queue all outgoing BSSAP or RANAP messages until the communication with the UE/MS is resumed.
8.2.1
Basic Handover procedure requiring a circuit connection between MSC-A and 3G_MSC-B
The procedure used for successful Inter-3G_MSC Handover from GSM to UMTS is shown in figure 24. Initiation of the GSM to UMTS handover procedure is described in clause 5. The procedure described in this clause makes use of messages from the 3GPP TS 08.08 [5], 3GPP TS 25.413 [11] and of the transport mechanism from the Mobile Application Part (MAP) (3GPP TS 29.002 [12]). After an Inter-3G_MSC handover further Intra-3G_MSC handovers may occur on 3G_MSC-B, these handovers will follow the procedures specified in the previous clauses.
3GPP
Release 6
54
3GPP TS 23.009 V6.5.0 (2008-12)
UE/MS/BSS-A MSC-A A-HO-REQUIRED MAP-Prep-Handover req. 3G_MSC-B
RNS-B/UE/MS VLR-B
MAP-Allocate-Handover-Number req. Iu-RELOCATION-REQUEST Iu-RELOCATION-REQUEST-ACK
MAP-Prep-Handover resp. IAM
MAP-Send-Handover-Report req.
MAP-Send-Handover-Report resp. (1) A-HO-COMMAND ACM MAP-Process-Access-Sig req. A-CLR-CMD/COM MAP-Send-End-Signal req. ANSWER RELEASE MAP-Send-End-Signal resp. Iu-RELOCATION-DETECT Iu-RELOCATION-COMPLETE
End of call
Figure 24: Basic GSM to UMTS Handover Procedure requiring a circuit connection The GSM to UMTS handover is initiated as described in clause 6.2.2. (This is represented by A-HO-REQUIRED in figure 24). Upon receipt of the A-HO-REQUIRED from BSS-A, MSC-A shall send a MAP-PREPARE-HANDOVER request to 3G_MSC-B including a complete A-HO-REQUEST message. NOTE: MSC-A shall not send further MAP-PREPARE-HANDOVER requests while a MAP-PREPAREHANDOVER response is pending or before any timeouts.
The MAP-PREPARE-HANDOVER request shall carry in the A-HO-REQUEST all information needed by 3G_MSC-B for allocating radio resources in RNS-B, see 3GPP TS 08.08 [5]. The MAP-PREPARE-HANDOVER request shall also carry the identity of the target RNS to which the call is to be handed over, see 3GPP TS 29.002 [12]. 3G_MSC-B will return the MAP-PREPARE-HANDOVER response after having retrieved a Handover Number from its associated VLR (exchange of the messages MAP-allocate-handovernumber request and MAP-send-handover-report request). The Handover Number shall be used for routing the connection of the call from MSC-A to 3G_MSC-B. For speech calls, 3G_MSC-B shall select an Iu Selected codec from the Iu Supported Codecs List, generate associated RAB parameters and connect a transcoder. If the Iu Supported Codecs List was not received, 3G_MSC-B shall select the appropriate default speech codec. For handover to UTRAN Iu mode, 3G_MSC-B shall also generate a NAS Synch Indicator for the Iu-RELOCATIONREQUEST message. If the Iu Supported Codecs List was received by 3G_MSC-B, then the Iu Selected codec shall be indicated in the MAP-PREPARE-HANDOVER response, sent from 3G_MSC-B to MSC-A.
3GPP
Release 6
55
3GPP TS 23.009 V6.5.0 (2008-12)
If radio resources are available in RNS-B the MAP-PREPARE-HANDOVER response will contain the complete AHO-REQUEST-ACK message generated from the Iu-RELOCATION-REQUEST-ACK received from RNS-B, containing the radio resources definition to be sent by BSS-A to the UE/MS. If the radio resource allocation is not possible, the MAP-PREPARE-HANDOVER response containing an A-HO-FAILURE will be sent to MSC-A. 3G_MSC-B will do the same if a fault is detected on the identity of the cell where the call has to be handed over. 3G_MSC-B simply reports the events related to the dialogue. It is up to MSC-A to decide the action to perform if it receives negative responses or the operation fails due to the expiry of the MAP-PREPARE-HANDOVER timer. If an error related to the TCAP dialogue or to the MAP-PREPARE-HANDOVER request is returned from 3G_MSC-B, this will be indicated to MSC-A and MSC-A will terminate the handover attempt. MSC-A shall reject the handover attempt towards BSS-A. The existing connection to the UE/MS shall not be cleared. When the A-HO-REQUEST-ACK has been received, MSC-A shall establish a circuit between MSC-A and 3G_MSC-B by signalling procedures supported by the network. In figure 24 this is illustrated by the messages IAM (Initial Address Message) and ACM (Address Complete Message) of Signalling System no 7. 3G_MSC-B awaits the capturing of the UE/MS (clause 6.2.2) on the radio path when the ACM is sent and MSC-A initiates the handover execution when ACM is received (illustrated by the A-HO-COMMAND and described in the clause 6.2.2). 3G_MSC-B transfers to MSC-A the acknowledgement received from the correct UE/MS (A-HO-DETECT/A-HOCOMPLETE). The Iu-RELOCATION-DETECT, if received, is converted to A-HO-DETECT and transferred to MSC-A using the MAP-PROCESS-ACCESS-SIGNALLING request. The Iu-RELOCATION-COMPLETE, when received from the correct UE/MS, is converted to A-HO-COMPLETE and included in the MAP-SEND-END-SIGNAL request and sent back to MSC-A. The circuit is through-connected in MSC-A when the A-HO-DETECT or the A-HO-COMPLETE is received from 3G_MSC-B. The old radio channel is released when the A-HO-COMPLETE message is received from 3G_MSC-B. The sending of the MAP-SEND-END-SIGNAL request starts the MAP supervision timer for the MAP dialogue between MSC-A and 3G_MSC-B. When the MAP-SEND-END-SIGNAL request including the A-HO-COMPLETE message is received in MSC-A the resources in BSS-A shall be cleared. In order not to conflict with the PSTN/ISDN signalling system(s) used between MSC-A and 3G_MSC-B, 3G_MSC-B must generate an answer signal when Iu-RELOCATION-DETECT/COMPLETE is received. 3G_MSC-B shall release the Handover Number when the circuit between MSC-A and 3G_MSC-B has been established. If the circuit between MSC-A and 3G_MSC-B cannot be established (e.g. an unsuccessful backward message is received instead of ACM). MSC-A terminates the inter3G_MSC handover attempt by sending an appropriate MAP message, for example an ABORT. MSC-A shall retain overall call control until the call is cleared by the fixed subscriber or the UE/MS and there is no further call control functions to be performed (e.g. servicing waiting calls, echo cancellers). When MSC-A clears the call to the UE/MS it also clears the call control functions in MSC-A and sends the MAPSEND-END-SIGNAL response to release the MAP resources in 3G_MSC-B. MSC-A may terminate the procedure at any time by sending an appropriate MAP message to 3G_MSC-B. If establishment of the circuit between MSC-A and 3G_MSC-B has been initiated, the circuit must also be cleared. The GSM to UMTS handover will be aborted by MSC-A if it detects clearing or interruption of the radio path before the call has been established on 3G_MSC-B.
8.2.2
Basic GSM to UMTS Handover procedure not requiring the establishment of a circuit connection between MSC-A and 3G_MSC-B
The basic GSM to UMTS handover procedures to be used when no circuit connection is required by MSC-A are similar to those described in clause 8.2.1 for circuit switched calls. The main differences to the procedures described in clause 8.2.1 relate to the establishment of circuits between the network entities and the Handover Number allocation. In the case of basic GSM to UMTS handover, MSC-A shall specify to 3G_MSC-B that no Handover Number is required in the MAP-PREPARE-HANDOVER request (see 3GPP TS 29.002 [12]). As for the basic GSM to UMTS handover using a circuit connection, the A-HO-REQUEST is transmitted at the same time. Any subsequent Handover Number allocation procedure will not be invoked until the completion of the basic GSM to UMTS handover procedure (see clause: Subsequent Channel Assignment using a circuit connection). 3G_MSC-B shall then perform the radio
3GPP
Release 6
56
3GPP TS 23.009 V6.5.0 (2008-12)
resources allocation as described in clause 8.2.1. The MAP-PREPARE-HANDOVER response shall be returned to MSC-A including either the translated response of the radio resources allocation request received from RNS-B (A-HOREQUEST-ACK/A-HO-FAILURE). The basic GSM to UMTS handover procedure will continue as described in clause 8.2.1 except that no circuit connection will be established towards 3G_MSC-B. The relevant case for the basic GSM to UMTS handover without circuit connection is shown in figure 25. As can be seen the major differences to the equivalent figure 24 are the omission of any circuit establishment messaging and the omission of handover number allocation signalling.
UE/MS/BSS-A MSC-A A-HO-REQUIRED MAP-Prep-Handover req. Iu-RELOCATION-REQUEST Iu-RELOCATION-REQUEST-ACK A-HO-COMMAND MAP-Prep-Handover resp. MAP-Process-Access-Sig req. A-CLR-CMD/COM MAP-Send-End-Signal req. Iu-RELOCATION-DETECT Iu-RELOCATION-COMPLETE 3G_MSC-B
RNS-B/UE/MS VLR-B
End of link
Figure 25: Basic GSM to UMTS Handover Procedure without circuit connection
8.2.3
Procedure for subsequent GSM to UMTS handover requiring a circuit connection
After the call has been handed over to MSC-B, if the UE/MS leaves the GSM area of MSC-B during the same call and enters a UTRAN area, subsequent GSM to UMTS handover is necessary in order to continue the connection. The following cases apply: i) the UE/MS moves back to the area of 3G_MSC-A; ii) the UE/MS moves into the area of a third 3G_MSC (3G_MSC-B'). In both cases the call is switched in 3G_MSC-A; the circuit between 3G_MSC-A and MSC-B shall be released after a successful subsequent handover has been performed.
3GPP
Release 6
57
3GPP TS 23.009 V6.5.0 (2008-12)
8.2.3.1
Description of subsequent GSM to UMTS handover procedure i): MSC-B to 3G_MSC-A
The procedure for successful GSM to UMTS handover from MSC-B back to 3G_MSC-A is shown in figure 26.
UE/MS/RNS-B 3G_MSC-A MSC-B A-HO-REQUIRED MAP-Prep-Sub-Handover req. Iu-RELOCATION-REQUEST Iu-RELOCATION-REQUEST-ACK MAP-Prep-Sub-Handover resp. Iu-RELOCATION-DETECT Iu-RELOCATION-COMPLETE MAP-Send-End-Signal resp. Release A-CLR-CMD/COM A-HO-COMMAND BSS-A/UE/MS VLR-B
Figure 26: Subsequent GSM to UMTS handover procedure i): successful handover from MSC-B to 3G_MSC-A using a circuit connection The procedure is as follows. MSC-B sends the MAP-PREPARE-SUBSEQUENT-HANDOVER request to 3G_MSC-A indicating the new MSC number (3G_MSC-A number), indicating also the identity of the target RNS where the call has to be handed over and including a complete A-HO-REQUEST message. (NOTE: MSC-B shall not send further MAP-PREPARESUBSEQUENT-HANDOVER requests while a handover attempt is pending or before any timeouts). Since 3G_MSC-A is the call controlling MSC, this MSC needs no Handover Number for routing purposes; 3G_MSC-A can immediately initiate the search for free radio resources. 3G_MSC-A then inserts a transcoder between its RNS and the connection to the other party. When radio resources can be assigned, 3G_MSC-A shall return in the MAP-PREPARE-SUBSEQUENT-HANDOVER response the complete A-HO-REQUEST-ACK message generated from the Iu-RELOCATION-REQUEST-ACK received from the RNS-B and possible extra BSSMAP information, amended by 3G_MSC-A due to the possible interworking between the BSSMAP protocol carried on the E-interface and the RANAP protocol used on the Iuinterface. If radio resources cannot be assigned or if a fault is detected on the target cell identity, or the target cell identity in the A-HO-REQUEST is not consistent with the target MSC number, the MAP-PREPARE-SUBSEQUENTHANDOVER response containing an A-HO-FAILURE message shall be given to MSC-B, in addition MSC-B shall maintain the connection with the UE/MS. If the procedure in 3G_MSC-A is successful then MSC-B can request the UE/MS to retune to the new RNS-B on 3G_MSC-A. This is illustrated in figure 26 by the A-HO-COMMAND message. The operation is successfully completed when 3G_MSC-A receives the Iu-RELOCATION-COMPLETE message. After GSM to UMTS handover 3G_MSC-A shall release the circuit to MSC-B. 3G_MSC-A must also terminate the MAP procedure for the basic handover between 3G_MSC-A and MSC-B by sending an appropriate MAP message. MSC-B will clear the resources in BSS-A when the MAP-SEND-END-SIGNAL response is received.
8.2.3.2
Description of subsequent GSM to UMTS handover procedure ii): MSC-B to 3G_MSC-B'
The procedure for successful GSM to UMTS handover from MSC-B to 3G_MSC-B' is shown in figure 27.
3GPP
Release 6
58
3GPP TS 23.009 V6.5.0 (2008-12)
The procedure consists of two parts: a subsequent handover from MSC-B back to MSC-A as described in clause 7.3.1 (the same procedures apply if MSC-A is replaced by 3G_MSC-A); and a basic GSM to UMTS handover from MSC-A to 3G_MSC-B' as described in clause 8.2.1.
MSC-B sends the MAP-PREPARE-SUBSEQUENT-HANDOVER request to MSC-A indicating a new MSC number (which is the identity of 3G_MSC-B'), indicating also the identity of the target RNS where the call has to be handed over and including a complete A-HO-REQUEST, MSC-A then starts a basic handover procedure towards 3G_MSC-B'. When MSC-A receives the ACM from 3G_MSC-B', MSC-A informs MSC-B that 3G_MSC-B' has successfully allocated the radio resources on RNS-B' side by sending the MAP-PREPARE-SUBSEQUENT-HANDOVER response containing the complete A-HO-REQUEST-ACK generated from the RELOCATION-REQUEST-ACK received from RNS-B' and possible extra BSSMAP information, amended by MSC-A due to the possible interworking between the BSSMAP protocol carried on the E-interface between MSC-A and 3G_MSC-B' and the BSSMAP protocol carried on the E-interface between MSC-A and MSC-B. Now MSC-B can start the procedure on the radio path. For MSC-A the handover is completed when it has received the MAP-SEND-END-SIGNAL REQUEST from 3G_MSC-B' containing the A-HO-COMPLETE generated from Iu-RECOLATION COMPLETE received from the RNS-B'. The circuit between MSC-A and MSC-B is released. MSC-A also sends the MAP-SEND-END-SIGNAL response to MSC-B in order to terminate the original MAP dialogue between MSC-A and MSC-B. MSC-B releases the radio resources when it receives this message. If no radio resources can be allocated by 3G_MSC-B' or no circuit between MSC-A and 3G_MSC-B' can be established or a fault is detected on the target cell identity or the target cell identity in the A-HO-REQUEST is not consistent with the target MSC number, MSC-A informs MSC-B by using the A-HO-FAILURE message included in the MAPPREPARE-SUBSEQUENT-HANDOVER response. MSC-B shall maintain the existing connection with the UE/MS. When the subsequent GSM to UMTS handover is completed, 3G_MSC-B' is considered as 3G_MSC-B. Any further inter-MSC handover is handled as described above for a subsequent handover.
3GPP
Release 6
59
3GPP TS 23.009 V6.5.0 (2008-12)
UE/MS/BSS/RNS 3G_MSC-B MSC-A MSC-B A-HO-REQUIRED MAP-Prep-Sub-Handover req. MAP-Prepare-Handover req. Iu-RELOCATION-REQUEST Iu-RELOCATION-REQUEST-ACK MAP-Prepare-Handover resp. IAM MAP-Send-Handover-Rep. resp. (1) ACM MAP-Prep-Sub-Ho resp. A-HO-COMMAND Iu-RELOCATION-DETECT MAP-Process-Access-Signalling req. Iu-RELOCATION-COMPLETE MAP-Send-End-Signal req. Answer Release MAP-Send-End-Signal resp. A-CLR-CMD/COM (end of call) Release MAP-Send-End-Signal resp. MAP-Send-Handover-Report req. MAP-Allocate-Handover-Number req. VLR-B VLR-B
Figure 27: Subsequent GSM to UMTS handover procedure ii): Successful handover from MSC-B to 3G_MSC-B' requiring a circuit connection
8.2.4
Procedure for subsequent GSM to UMTS handover not requiring a circuit connection
As for the subsequent GSM to UMTS handover with a circuit connection, the same two cases of subsequent handover apply: i) the UE/MS moves back to the area of 3G_MSC-A; ii) the UE/MS moves into the area of a third 3G_MSC (3G_MSC-B').
3GPP
Release 6
60
3GPP TS 23.009 V6.5.0 (2008-12)
8.2.4.1
Description of subsequent GSM to UMTS handover procedure without circuit connection i): MSC-B to 3G_MSC-A
The procedure for successful GSM to UMTS handover from MSC-B back to 3G_MSC-A without circuit connection is shown in figure 28. The only difference with the figure 26, is that no circuit release is needed between 3G_MSC-A and MSC-B.
UE/MS/RNS-B 3G_MSC-A MSC-B A-HO-REQUIRED MAP-Prep-Sub-Handover req. Iu-RELOCATION-REQUEST Iu-RELOCATION-REQUEST-ACK MAP-Prep-Sub-Handover resp. Iu-RELOCATION-DETECT Iu-RELOCATION-COMPLETE MAP-Send-End-Signal resp. A-CLR-CMD/COM A-HO-COMMAND BSS-A/UE/MS VLR-B
Figure 28: Subsequent GSM to UMTS handover procedure i): Successful handover from MSC-B to 3G_MSC-A not requiring a circuit connection
8.2.4.2
Description of subsequent GSM to UMTS handover procedure without circuit connection ii): MSC-B to 3G_MSC-B'
The procedure for successful GSM to UMTS handover from MSC-B to 3G_MSC-B' is shown in figure 29. The procedure consists of two parts: a subsequent handover from MSC-B back to MSC-A as described in clause 7.4.1 (the same procedures apply if MSC-A is replaced by 3G_MSC-A); and a basic GSM to UMTS handover from MSC-A to 3G_MSC-B' as described in clause 8.2.2.
3GPP
Release 6
61
3GPP TS 23.009 V6.5.0 (2008-12)
UE/MS/BSS/RNS 3G_MSC-B MSC-A MSC-B A-HO-REQUIRED MAP-Prep-Sub-Handover req. MAP-Prepare-Handover req. Iu-RELOCATION-REQUEST Iu-RELOCATION-REQUEST-ACK MAP-Prepare-Handover resp. MAP-Prep-Sub-Ho resp. A-HO-COMMAND Iu-RELOCATION-DETECT MAP-Process-Access-Signalling req. Iu-RELOCATION_COMPLETE MAP-Send-End-Signal req. MAP-Send-End-Signal resp. A-CLR-CMD/COM (end of link) MAP-Send-End-Signal resp. VLR-B VLR-B
Figure 29: Subsequent GSM to UMTS handover procedure ii): Successful handover from MSC-B to 3G_MSC-B' without circuit connection
8.3
SRNS Relocation
The following clauses describe two options for the Basic and Subsequent Relocation procedures. The first, as described in clauses 8.3.1 and 8.3.3 respectively, provides for a circuit connection between 3G_MSC-A and 3G_MSC-B. The second, as described in clauses 8.3.2 and 8.3.4 respectively, provides for a Basic and Subsequent Relocation without the provision of a circuit connection between 3G_MSC-A and 3G_MSC-B. In all the above mentioned clauses, the following principles apply: a) during the relocation resource allocation, except for the messages explicitly indicated in b and c below, only the relocation related messages that are part of the applicable RANAP subset - as defined in 3GPP TS 29.108 [15] shall be transferred on the E-interface; b) the trace related messages that are part of the applicable RANAP subset - as defined in 3GPP TS 29.108 [15] can be sent by the 3G_MSC-A on the E-interface after successful relocation resource allocation. In the clauses 8.3.1 and 8.3.2, it is however allowed at basic relocation initiation on the E-Interface to transfer one trace invocation related message that is part of the applicable RANAP subset - as defined in 3GPP TS 29.108 [15] together with the applicable relocation related message. The applicable relocation related message shall always appear as the first message; c) during the relocation resource allocation for subsequent inter-MSC SRNS relocation according to subclauses 8.3.3 and 8.3.4, it is allowed to transfer either DTAP or RANAP Direct Transfer messages on the E-Interface between 3G_MSC-A and 3G_MSC-B. RANAP Direct Transfer messages shall be used for this purpose if and only if the basic handover procedure was an inter MSC SRNS relocation;
3GPP
Release 6
62
3GPP TS 23.009 V6.5.0 (2008-12)
d) the Iu-Location Reporting Control message which belongs to the applicable RANAP subset - as defined in 3GPP TS 29.108 [15] - can be sent by the 3G_MSC-A on the E-interface after successful relocation resource allocation; e) during the relocation execution, i.e. while the UE is not in communication with the network, the 3G_MSC-A shall queue all outgoing RANAP or BSSAP messages until the communication with the UE is resumed; f) during the execution of a basic inter-MSC SRNS relocation to 3G_MSC-B or a subsequent inter-MSC SRNS relocation to a third 3G-MSC-B, only the relocation related messages and the Iu-Release-Request message that are part of the applicable RANAP subset - as defined in 3GPP TS 29.108 [15] may be sent by the target MSC on the E-interface; g) during a subsequent inter-MSC SRNS relocation back to 3G_MSC-A or to a third 3G_MSC-B, 3G_MSC-B may initiate either an Iu-Release-Request procedure or an A-Clear-Request procedure on the E-interface. An IuRelease-Request procedure shall be initiated only if the basic handover procedure was an inter-MSC SRNS relocation; h) finally, during supervision, i.e. while the UE is not in the area of 3G_MSC-A after a successful Inter-3G_MSC relocation, the subset of RANAP procedures and their related messages - as defined in 3GPP TS 29.108 [15] shall apply on the E-Interface. As an exception to this rule, 3G_MSC-B shall notify 3G_MSC-A of a successfully completed subsequent intra-MSC-B intra GSM or inter-system handover by using the Internal Handover Indication procedure as specified in 3GPP TS 49.008 [7]. Furthermore, in case of a subsequent interMSC intra GSM or inter-system handover back to 3G_MSC-A or to a third 3G_MSC-B, during the handover resource allocation, the handover and trace related messages that are part of the applicable BSSAP subset - as defined in 3GPP TS 49.008 [7] - shall be transferred on the E-interface (see list items a and b in clause 7, subclause 8.1, and 8.2, respectively). If a subsequent inter-MSC handover/relocation back to 3G_MSC-A or to a third 3G_MSC-B is cancelled, then the supervision continues, and RANAP procedures and their related messages shall apply on the E-interface. NOTE: A subsequent inter-MSC intra GSM or GSM to UMTS inter-system handover back to 3G_MSC-A or to a third 3G_MSC-B can occur, e.g., if after the basic inter-MSC SRNS relocation to 3G_MSC-B the MS performed a subsequent intra-3G_MSC-B UMTS to GSM inter-system handover;
i) during the intra-3G_MSC-B relocation execution, if any, the 3G_MSC-B shall queue all outgoing RANAP messages until the communication with the UE is resumed. j) after successful completion of the Intra-3G_MSC-B relocation, if 3G_MSC-B or 3G-MSC-B has previously received an order to perform location reporting at change of Service Area from 3G_MSC-A, it shall act as specified in subclause 6.2.3.
8.3.1
Basic relocation procedure requiring a circuit connection between 3G_MSC-A and 3G_MSC-B
The procedure used for successful Inter-3G_MSC SRNS relocation is shown in figure 30. Initiation of the relocation procedure is described in clause 5. The procedure described in this clause makes use of messages from the 3GPP TS 25.413 [11] and of the transport mechanism from the Mobile Application Part (MAP) (3GPP TS 29.002 [12]). After an Inter-3G_MSC SRNS relocation further Intra-3G_MSC relocations may occur on 3G_MSC-B, these relocations will follow the procedures specified in a previous clause.
3GPP
Release 6
63
3GPP TS 23.009 V6.5.0 (2008-12)
RNS-A 3G_MSC-A IU-RELOC-REQUIRED MAP-Prep-Handover req. 3G_MSC-B
RNS-B VLR-B
MAP-Allocate-Handover-Number req. IU-RELOC-REQUEST IU-RELOC-REQUEST-ACK
MAP-Prep-Handover resp. IAM
MAP-Send-Handover-Report req.
MAP-Send-Handover-Report resp. (1) IU-RELOC-COMMAND ACM MAP-Process-Access-Sig req. IU-REL-CMD/COM MAP-Send-End-Signal req. ANSWER RELEASE MAP-Send-End-Signal resp. IU-RELOC-DETECT IU-RELOC-COMPLETE
End of call
Figure 30: Basic SRNS Relocation Procedure requiring a circuit connection
8.3.1.1
The relocation is initiated as described in clause 6.2.3. (This is represented by IU-RELOC-REQUIRED in figure 30). Upon receipt of the IU-RELOC-REQUIRED from RNS-A, 3G_MSC-A shall send a MAP-PREPARE-HANDOVER request to 3G_MSC-B including a complete IU-RELOC-REQUEST message. (NOTE: 3G_MSC-A shall not send further MAP-PREPARE-HANDOVER requests while a MAP-PREPARE-HANDOVER response is pending or before any timeouts). The MAP-PREPARE-HANDOVER request shall carry in the IU-RELOC-REQUEST all information needed by 3G_MSC-B for allocating radio resources in the case of SRNS relocation without Iur interface, see 3GPP TS 25.413 [11]. For speech calls, 3G_MSC-A shall include the Iu Currently used codec and the Iu Supported Codecs List in the MAPPREPARE-HANDOVER request. 3G_MSC-A shall configure the RANAP RAB parameters according to the appropriate default speech codec. For a relocation to UTRAN Iu mode, if this codec is different from the Iu Currently used codec, 3G_MSC-A shall also include the NAS Synch Indicator for the default speech codec in the IuRELOCATION-REQUEST. Alternatively, if 3G_MSC-B is known to support the use of the Iu Supported Codecs List, 3G_MSC-A may configure the RANAP RAB parameters according to the preferred codec and indicate this to 3G_MSC-B by including the RAB configuration indicator in the MAP-PREPARE-HANDOVER request. For a relocation to UTRAN Iu mode, if the preferred codec is different from the Iu Currently used codec, 3G_MSC-A shall also include the NAS Synch Indicator for the preferred codec in the Iu-RELOCATION-REQUEST. The decision to use this option is based on internal configuration information in 3G_MSC-A. MAP-PREPARE-HANDOVER request shall also carry the identity of the target RNS to which the call is to be relocated, see 3GPP TS 29.002. 3G_MSC-B will return the MAP-PREPARE-HANDOVER response after having retrieved one or several Handover Numbers from its associated VLR (exchange of the messages MAP-allocatehandover-number request and MAP-send-handover-report request). The Handover Numbers shall be used for routing the connections of the calls from 3G_MSC-A to 3G_MSC-B.
3GPP
Release 6
64
3GPP TS 23.009 V6.5.0 (2008-12)
For speech calls, 3G_MSC-B shall select an Iu Selected codec from the Iu Supported Codecs List and connect a transcoder. If the Iu Supported Codecs List was not received, 3G_MSC-B shall select the appropriate default speech codec. 3G_MSC-B shall reconfigure the RANAP RAB parameters according to the Iu Selected codec: if the RAB configuration indicator is included in the MAP-PREPARE-HANDOVER request and the codec selected by 3G_MSC-B is different from the preferred codec; or if the RAB configuration indicator is not included in the MAP-PREPARE-HANDOVER request and the codec selected by 3G_MSC-B is different from the appropriate default speech codec.
Additionally, for a relocation to UTRAN Iu mode, if the Iu Selected codec is different from the Iu Currently used codec, 3G_MSC-B shall include the NAS Synch Indicator for the Iu Selected codec in the Iu-RELOCATION-REQUEST. If the Iu Supported Codecs List was received by 3G_MSC-B, then the Iu Selected codec shall be indicated in the MAPPREPARE-HANDOVER response, sent from 3G_MSC-B to 3G_MSC-A. If radio resources are available in 3G_MSC-B, the MAP-PREPARE-HANDOVER response will contain the complete IU-RELOC-REQUEST-ACKNOWLEDGE message received from RNS-B, containing the radio resources definition to be sent by RNS-A to the UE (in case of relocation without Iur interface) and possible extra RANAP information, amended by 3G_MSC-B due to the possible interworking between the RANAP protocol carried on the E-interface and the RANAP protocol used on the Iu-interface. If the radio resource allocation is not possible, the MAP-PREPAREHANDOVER response containing an IU-RELOCATION-FAILURE will be sent to 3G_MSC-A. 3G_MSC-B will do the same if a fault is detected on the identity of the RNS where the call has to be relocated. 3G_MSC-B simply reports the events related to the dialogue. It is up to 3G_MSC-A to decide the action to perform if it receives negative responses or the operation fails due to the expiry of the MAP-PREPARE-HANDOVER timer. If an error related to the TCAP dialogue or to the MAP-PREPARE-HANDOVER request is returned from 3G_MSC-B, this will be indicated to 3G_MSC-A and 3G_MSC-A will terminate the relocation attempt. The existing connection to the UE shall not be cleared. When the IU-RELOC-REQUEST-ACKNOWLEDGE has been received, 3G_MSC-A shall establish a circuit between 3G_MSC-A and 3G_MSC-B by signalling procedures supported by the network. In figure 30 this is illustrated by the messages IAM (Initial Address Message) and ACM (Address Complete Message) of Signalling System no 7. 3G_MSC-B awaits the capturing of the UE (clause 6.2.3) on the radio path when the ACM is sent and 3G_MSC-A initiates the relocation execution when ACM is received (illustrated by the IU-RELOC-COMMAND and described in the clause 6.2.3). 3G_MSC-A shall remove the transcoder between the MSC and other party. 3G_MSC-B transfers to 3G_MSC-A the acknowledgement received from the correct UE (IU-RELOC-DETECT/IURELOC-COMPLETE). The IU-RELOC-DETECT, if received, is transferred to 3G_MSC-A using the MAPPROCESS-ACCESS-SIGNALLING request. The IU-RELOC-COMPLETE, when received from the correct UE, is included in the MAP-SEND-END-SIGNAL request and sent back to 3G_MSC-A. The circuit is through connected in 3G_MSC-A when the IU-RELOC-DETECT or the IU-RELOC-COMPLETE is received from 3G_MSC-B. The old radio resources are released when the IU-RELOC-COMPLETE message is received from 3G_MSC-B. The sending of the MAP-SEND-END-SIGNAL request starts the MAP supervision timer for the MAP dialogue between 3G_MSC-A and 3G_MSC-B. When the MAP-SEND-END-SIGNAL request including the IU-RELOC-COMPLETE message is received in 3G_MSC-A, the resources in RNS-A shall be released. In order not to conflict with the PSTN/ISDN signalling system(s) used between 3G_MSC-A and 3G_MSC-B, 3G_MSC-B must generate an answer signal when IU-RELOC-DETECT/COMPLETE is received. 3G_MSC-B shall release the Handover Number when the circuit between 3G_MSC-A and 3G_MSC-B has been established. If the circuit between 3G_MSC-A and 3G_MSC-B cannot be established, (e.g. an unsuccessful backward message is received instead of ACM) 3G_MSC-A terminates the inter-3G_MSC relocation attempt by sending an appropriate MAP message, for example an ABORT. 3G_MSC-A shall retain overall call control until the call is cleared by the fixed subscriber or the UE and there is no further call control functions to be performed (e.g. servicing waiting calls, echo cancellers). When 3G_MSC-A clears the call to the UE it also clears the call control functions in 3G_MSC-A and sends the MAPSEND-END-SIGNAL response to release the MAP resources in 3G_MSC-B.
3GPP
Release 6
65
3GPP TS 23.009 V6.5.0 (2008-12)
3G_MSC-A may terminate the procedure at any time by sending an appropriate MAP message to 3G_MSC-B. If establishment of the circuit between 3G_MSC-A and 3G_MSC-B has been initiated, the circuit must also be cleared. The relocation will be aborted by 3G_MSC-A if it detects release or interruption of the radio path before the call has been established on 3G_MSC-B.
8.3.1.2
8.3.1.2.1

3G_MSC-B does not support multiple bearers
If 3G_MSC-A supports the optional supplementary service Multicall (See 3GPP TS 23.135), 3G_MSC-A shall have the following functionality additionally to the description in clause 8.3.1.1. Upon receipt of the IU-RELOCATION-REQUIRED from RNS-A, 3G_MSC-A generates IU-RELOCATIONREQUEST and sends a MAP-PREPARE-HANDOVER request to 3G_MSC-B including the IU-RELOCATIONREQUEST message, which may include multiple bearers. If 3G_MSC-A receives an indication that 3G_MSC-B does not support multiple bearers, 3G_MSC-A shall select one bearer to be handed over if the UE is engaged with multiple bearers. 3G_MSC-A reconstructs IU-RELOCATION-REQUEST and sends again a MAP-PREPARE-HANDOVER request to 3G_MSC-B including the IU-RELOCATION-REQUEST message, which includes only the selected bearer. When MAP-PREPARE-HANDOVER response including an IU-RELOCATION-REQUEST-ACK is received from 3G_MSC-B, 3G_MSC-A sends IU-RELOCATION-COMMAND, which indicates the bearers not to be handed over as bearers to be released, to RNS-A. After 3G_MSC-A receives MAP-SEND-END-SIGNAL request from 3G_MSC-B, 3G_MSC-A shall release calls via 3G_MSC-B, which has been carried by the bearers not to be handed over, and then 3G_MSC-A sends IU-RELEASECOMMAND to RNS-A.
8.3.1.2.2
3G_MSC-B supports multiple bearers
If 3G_MSC-A and 3G_MSC_B support the optional supplementary service Multicall (See 3GPP TS 23.135), 3G_MSCA and 3G_MSC-B shall have the following functionality additionally to the description in clause 8.3.1.1. Upon receipt of the IU-RELOCATION-REQUIRED from RNS-A, 3G_MSC-A generates IU-RELOCATIONREQUEST and sends a MAP-PREPARE-HANDOVER request to 3G_MSC-B including the IU-RELOCATIONREQUEST message, which may include multiple bearers. When MAP-PREPARE-HANDOVER request including an IU-RELOCATION-REQUEST message is received by the 3G_MSC-B and the number of bearers included in the IU-RELOCATION-REQUEST message has exceeded the maximum number of bearers supported by 3G_MSC-B, the 3G_MSC-B shall select several bearers so that the number of bearers will fulfil the range of 3G_MSC-B capability. In this case 3G_MSC-B shall reconstruct IU-RELOCATIONREQUEST message to cope with the capability of 3G_MSC-B. The 3G_MSC-B shall retrieve multiple Handover Numbers from its associated VLR (exchange of the messages MAP-allocate-handover-number request and MAP-sendhandover-report request several times). The number of Handover Numbers depends on the number of RAB IDs in the reconstructed IU-RELOCATION-REQUEST. After the completion of Handover Number allocation 3G_MSC-B may select several bearers and reconstruct IURELOCATION-REQUEST again if the number of successfully allocated Handover Numbers is less than the number of required bearers, and sends IU-RELOCATION-REQUEST to RNS-B. After the reception of IU-RELOCATION-REQUEST-ACK from RNS-B, the 3G_MSC-B shall generate Relocation Number List, which includes couples of RAB ID (See 3GPP TS 25.413 [11]) and Handover Number successfully allocated. Then the 3G_MSC-B sends MAP-PREPARE-HANDOVER response including Relocation Number List back to the 3G_MSC-A. Upon receipt of the MAP-PREPARE-HANDOVER response 3G_MSC-A shall establish circuits between 3G_MSC-A and 3G_MSC-B by signalling procedures supported by the network according to the Relocation Number List. When 3G_MSC-A receives all the results from attempted circuits (the results may be successful ACM message or unsuccessful backward message for each attempt) and if at least one circuit has been successfully established, 3G_MSC-A sends IU-RELOCATION-COMMAND, which indicates the bearers failed to set up in RNS-B and the bearers associated with circuits which has failed to set up as bearers to be released, to RNS-A.
3GPP
Release 6
66
3GPP TS 23.009 V6.5.0 (2008-12)
After 3G_MSC-A receives MAP-SEND-END-SIGNAL request from 3G_MSC-B, 3G_MSC-A shall release calls via 3G_MSC-B, which has been carried by the bearers failed to set up in RNS-B and the bearers associated with circuits which has failed to set up, and then 3G_MSC-A sends IU-RELEASE-COMMAND to RNS-A. If no circuit connection has been successfully established 3G_MSC-A terminates the inter-3G_MSC relocation attempt by sending an appropriate MAP massage, for example ABORT.
8.3.2
Basic relocation procedure not requiring the establishment of a circuit connection between 3G_MSC-A and 3G_MSC-B
The basic SRNS relocation procedures to be used when no circuit connection is required by 3G_MSC-A are similar to those described in clause 8.3.1 for circuit switched calls. The main differences to the procedures described in clause 8.3.1 relate to the establishment of circuits between the network entities and the Handover Number allocation. In the case of basic relocation, 3G_MSC-A shall specify to 3G_MSC-B that no Handover Number is required in the MAP-PREPARE-HANDOVER request (see 3GPP TS 29.002 [12]). As for the basic relocation using a circuit connection, the IU-RELOC-REQUEST is transmitted at the same time together with the identity of the target RNS to which the call is to be relocated. Any subsequent Handover Number allocation procedure will not be invoked until the completion of the basic relocation procedure (see clause: Subsequent Channel Assignment using a circuit connection). 3G_MSC-B shall then perform the radio resources allocation as described in clause 8.3.1 if applicable. The MAPPREPARE-HANDOVER response shall be returned to 3G_MSC-A including either the response of the radio resources allocation request received from RNS-B (IU-RELOC-REQUEST-ACKNOWLEDGE/IU-RELOC-FAILURE with possible extra RANAP information. This extra information is amended by 3G_MSC-B due to the possible interworking between the RANMAP protocol carried on the E-interface and the RANAP protocol used on the Iu-interface). The basic relocation procedure will continue as described in clause 8.3.1 except that no circuit connection will be established towards 3G_MSC-B. The relevant case for the basic relocation without circuit connection is shown in figure 31. As can be seen the major differences to the equivalent figure 30 are the omission of any circuit establishment messaging and the omission of handover number allocation signalling.
RNS-A 3G_MSC-A IU-RELOC-REQUIRED MAP-Prep-Handover req. IU-RELOC-REQUEST IU-RELOC-REQUEST-ACK MAP-Prep-Handover resp. IU-RELOC-COMMAND MAP-Process-Access-Sig req. IU-REL-CMD/COM MAP-Send-End-Signal req. IU-RELOC-DETECT IU-RELOC-COMPLETE 3G_MSC-B
RNS-B VLR-B
End of link MAP-Send-End-Signal resp.
Figure 31: Basic SRNS relocation procedure without a circuit connection
3GPP
Release 6
67
3GPP TS 23.009 V6.5.0 (2008-12)
8.3.3
Procedure for subsequent relocation requiring a circuit connection
After the call has been relocated to 3G_MSC-B, if the UE leaves the area of 3G_MSC-B during the same call, subsequent relocation is necessary in order to continue the connection when no Iur interface exists between the involved RNSs, or to optimise the transmission path when the Iur interface is used. The following cases apply: i) the UE moves back to the area of 3G_MSC-A; ii) the UE moves into the area of a third 3G_MSC (3G_MSC-B'). In both cases the call is switched in 3G_MSC-A; the circuit between 3G_MSC-A and 3G_MSC-B shall be released after a successful subsequent relocation has been performed. If 3G_MSC-A is replaced by MSC-A in the procedures, then a subsequent relocation from 3G_MSC-B to 3G_MSC-B' shall not be possible since MSC-A does not support the RANAP protocol.
8.3.3.1
Description of subsequent relocation procedure i): 3G_MSC-B to 3G_MSC-A
The procedure for successful relocation from 3G_MSC-B back to 3G_MSC-A is shown in figure 32.
RNS-B 3G_MSC-A 3G_MSC-B Iu-RELOCATIONREQUIRED RNS-A VLR-B
MAP-Prep-Sub-Handover req. Iu-RELOCATIONREQUEST Iu-RELOCATIONREQUEST-ACK Iu-RELOCATIONDETECT Iu-RELOCATIONCOMPLETE MAP-Send-End-Signal resp. Release MAP-Prep-Sub-Handover resp.
Iu-RELEASECMD/COM
Figure 32: Subsequent relocation procedure i) successful relocation from 3G_MSC-B to 3G_MSC-A using a circuit connection
8.3.3.1.1
The procedure is as follows. 3G_MSC-B sends the MAP-PREPARE-SUBSEQUENT-HANDOVER request to 3G_MSC-A indicating the new 3G_MSC number (3G_MSC-A number), indicating also the identity of the target RNS where the call has to be relocated and including a complete IU-RELOC-REQUEST message. For speech calls, 3G_MSC-B shall configure the RANAP RAB parameters according to the appropriate default speech codec. For a relocation to UTRAN Iu mode, if this codec is different from the Iu Currently used codec, 3G_MSC-B shall also include the NAS Synch Indicator for the default speech codec in the Iu-RELOCATION-REQUEST. Alternatively, if 3G_MSC-A is known to support the use of the Iu Supported Codecs List, 3G_MSC-B may configure the RANAP RAB parameters according to the preferred codec and indicate this to 3G_MSC-A by including the RAB configuration indicator in the MAP-PREPARE-SUBSEQUENT-HANDOVER request. For a relocation to UTRAN Iu mode, if the preferred codec is different from the Iu Currently used codec, 3G_MSC-B shall also include the NAS Synch Indicator for the preferred codec in the Iu-RELOCATION-REQUEST. NOTE: 3G_MSC-B shall not send further MAP-PREPARE-SUBSEQUENT-HANDOVER requests while a relocation attempt is pending or before any timeouts.
3GPP
Release 6
68
3GPP TS 23.009 V6.5.0 (2008-12)
Since 3G_MSC-A is the call controlling 3G_MSC, this 3G_MSC needs no Handover Number for routing purposes; 3G_MSC-A can immediately initiate the relocation towards the target RNS. For speech calls, 3G_MSC-A shall select an Iu Selected codec and connect a transcoder. 3G_MSC-A shall reconfigure the RANAP RAB parameters according to the Iu Selected codec: if the RAB configuration indicator is included in the MAP-PREPARE-SUBSEQUENT-HANDOVER request, and the codec selected by 3G_MSC-A is different from the preferred codec; or if the RAB configuration indicator is not included in the MAP-PREPARE-SUBSEQUENT-HANDOVER request and the codec selected by 3G_MSC-A is different from the appropriate default speech codec.
Additionally, for a relocation to UTRAN Iu mode, if the Iu Selected codec is different from the Iu Currently used codec, 3G_MSC-A shall include the NAS Synch Indicator for the Iu Selected codec in the Iu-RELOCATION-REQUEST. When relocation can be initiated, 3G_MSC-A shall return in the MAP-PREPARE-SUBSEQUENT-HANDOVER response the complete IU-RELOC-REQUEST-ACKNOWLEDGE message received from the RNS-B and possible extra RANAP information, amended by 3G_MSC-A due to the possible interworking between the RANAP protocol carried on the E-interface and the RANAP protocol used on the Iu-interface. If a radio resource cannot be assigned or if a fault is detected on the target RNS identity, or the target RNS identity in the IU-RELOC-REQUEST is not consistent with the target 3G_MSC number, the MAP-PREPARE-SUBSEQUENT-HANDOVER response containing an IURELOC-FAILURE message shall be given to 3G_MSC-B, in addition 3G_MSC-B shall maintain the connection with the UE. If the procedure in 3G_MSC-A is successful then 3G_MSC-B can request the UE to retune to the new RNS-B on 3G_MSC-A in the case of relocation without Iur interface, or request RNS-B to become serving RNS in the case of relocation with Iur interface. This is illustrated in figure 32 by the IU-RELOC-COMMAND message. The operation is successfully completed when 3G_MSC-A receives the IU-RELOC-COMPLETE message. After relocation 3G_MSC-A shall release the circuit to 3G_MSC-B. 3G_MSC-A must also terminate the MAP procedure for the basic relocation between 3G_MSC-A and 3G_MSC-B by sending an appropriate MAP message. 3G_MSC-B will release the resources in RNS-A when the MAP-SEND-ENDSIGNAL response is received.
8.3.3.1.2
If 3G_MSC-A and 3G_MSC_B support the optional supplementary service Multicall (See 3GPP TS 23.135), 3G_MSCA and 3G_MSC-B shall have the following functionality additionally to the description in clause 8.3.3.1.1. Upon receipt of the IU-RELOCATION-REQUIRED from RNS-A, 3G_MSC-B generates IU-RELOCATIONREQUEST which may include several bearers and sends it to 3G_MSC-A over MAP-PREPARE-SUBSEQUENTHANDOVER request. 3G_MSC-A sends IU-RELOCATION-REQUEST to RNS-B and receives IU-RELOCATION-REQUEST-ACK. When MAP-PREPARE-SUBSEQUENT-HANDOVER response is received from 3G_MSC-A, 3G_MSC-B sends IURELOCATION-COMMAND, which indicates the bearers failed to set up in RNS-B as bearers to be released, to RNSA. After 3G_MSC-A receives IU-RELOCATION-COMPLETE message from RNS-B, 3G_MSC-A shall release calls via RNS-B, which has been carried by the bearers failed to set up in RNS-B, and then 3G_MSC-A sends MAP-SENDEND-SIGNAL response to 3G_MSC-B.
8.3.3.2
Description of subsequent relocation procedure ii): 3G_MSC-B to 3G_MSC-B'
The procedure for successful relocation from 3G_MSC-B to 3G_MSC-B' is shown in figure 33. The procedure consists of two parts: a subsequent relocation from 3G_MSC-B back to 3G_MSC-A as described in clause 8.3.3.1; and
3GPP
Release 6
69
3GPP TS 23.009 V6.5.0 (2008-12)
a basic relocation from 3G_MSC-A to 3G_MSC-B' as described in clause 8.3.1.
8.3.3.2.1
3G_MSC-B sends the MAP-PREPARE-SUBSEQUENT-HANDOVER request to 3G_MSC-A indicating a new 3G_MSC number (which is the identity of 3G_MSC-B'), indicating also the target RNS identity and including a complete IU-RELOC-REQUEST, 3G_MSC-A then starts a basic relocation procedure towards 3G_MSC-B'. For speech calls, 3G_MSC-B shall configure the RANAP RAB parameters according to the appropriate default speech codec. For a relocation to UTRAN Iu mode, if this codec is different from the Iu Currently used codec, 3G_MSC-B shall also include the NAS Synch Indicator for the default speech codec in the Iu-RELOCATION-REQUEST. Alternatively, if 3G_MSC-A and 3G_MSC-B are known to support the use of the Iu Supported Codecs List, 3G_MSCB may configure the RANAP RAB parameters according to the preferred codec and indicate this to 3G_MSC-A by including the RAB configuration indicator in the MAP-PREPARE-SUBSEQUENT-HANDOVER request. For a relocation to UTRAN Iu mode, if the preferred codec is different from the Iu Currently used codec, 3G_MSC-B shall also include the NAS Synch Indicator for the preferred codec in the Iu-RELOCATION-REQUEST. The decision to use this option is based on internal configuration information in 3G_MSC-B. When 3G_MSC-A receives the ACM from 3G_MSC-B', 3G_MSC-A informs 3G_MSC-B that 3G_MSC-B' has successfully allocated the radio resources on RNS-B' side by sending the MAP-PREPARE-SUBSEQUENTHANDOVER response containing the complete IU-RELOC-REQUEST-ACKNOWLEDGE received from RNS-B' and possible extra RANAP information, amended by 3G_MSC-A due to the possible interworking between the RANAP protocol carried on the E-interface between 3G_MSC-A and 3G_MSC-B' and the RANAP protocol carried on the E-interface between 3G_MSC-A and 3G_MSC-B. Now 3G_MSC-B can start the procedure on the radio path if needed. For 3G_MSC-A the relocation is completed when it has received the MAP-SEND-END-SIGNAL REQUEST from 3G_MSC-B'containing the IU-RELOC-COMPLETE received from the RNS-B'. The circuit between 3G_MSC-A and 3G_MSC-B is released. 3G_MSC-A also sends the MAP-SEND-END-SIGNAL response to 3G_MSC-B in order to terminate the original MAP dialogue between 3G_MSC-A and 3G_MSC-B. 3G_MSC-B releases the radio resources when it receives this message. If no radio resource can be allocated by 3G_MSC-B' or no circuit between 3G_MSC-A and 3G_MSC-B' can be established or a fault is detected on the target RNS identity or the target RNS identity in the IU-RELOC-REQUEST is not consistent with the target 3G_MSC number, 3G_MSC-A informs 3G_MSC-B by using the IU-RELOC-FAILURE message included in the MAP-PREPARE-SUBSEQUENT-HANDOVER response. 3G_MSC-B shall maintain the existing connection with the UE. When the subsequent relocation is completed, 3G_MSC-B' is considered as 3G_MSC-B. Any further inter-3G_MSC relocation is handled as described above for a subsequent relocation.
8.3.3.2.2
If 3G_MSC-A and 3G_MSC-B support the optional supplementary service Multicall (See 3GPP TS 23.135), 3G_MSCA and 3G_MSC-B shall have the following functionality additionally to the description in clause 8.3.3.2.1. Upon receipt of the IU-RELOCATION-REQUIRED from RNS-B 3G_MSC-B generates an IU-RELOCATIONREQUEST message which may include multiple bearer and sends it to 3G_MSC-A over MAP-PREPARESUBSEQUENT-HANDOVER request. Upon receipt of the MAP-PREPARE-SUBSEQUENT-HANDOVER request from 3G_MSC-B, 3G_MSC-A starts a basic relocation procedure towards 3G_MSC-B'. 8.3.3.2.2.1 3G_MSC-B' does not support multiple bearers
If 3G_MSC-A receives an indication that 3G_MSC-B' does not support multiple bearers, 3G_MSC-A shall select one bearer to be handed over. 3G_MSC-A reconstructs IU-RELOCATION-REQUEST and sends again a MAP-PREPAREHANDOVER request to 3G_MSC-B' including the IU-RELOCATION-REQUEST message, which includes only the selected bearer. Upon receipt of MAP-PREPARE-HANDOVER response from 3G_MSC-B', 3G_MSC-A shall reconstructs IU-RELOCATION-REQUEST-ACK to indicate the bearers not to be handed over as the bearers failed to set up in IU-RELOCATION-REQUEST-ACK and send it over MAP-PREPARE-SUBSEQUENT-HANDOVER response to 3G_MSC-B.
3GPP
Release 6
70
3GPP TS 23.009 V6.5.0 (2008-12)
When MAP-PREPARE-SUBSEQUENT-HANDOVER response is received from 3G_MSC-A 3G_MSC-B sends IURELOCATION-COMMAND, which indicates the bearers failed to set up as bearers to be released, to RNS-A. After 3G_MSC-A receives MAP-SEND-END-SIGNAL request from 3G_MSC-B', 3G_MSC-A shall release calls via 3G_MSC-B', which has been carried by the bearers failed to set up, and then 3G_MSC-A sends MAP-SEND-ENDSIGNAL response to 3G_MSC-B. 8.3.3.2.2.2 3G_MSC-B' supports multiple bearers
If some of circuit connections failed to set up between 3G_MSC-A and 3G_MSC-B', 3G_MSC-A shall reconstruct IURELOCATION-REQUEST-ACK message so that the IU-RELOCATION-REQUEST-ACK includes only the bearers which have successfully established circuit connection and sends it to 3G_MSC-B over MAP-PREPARESUBSEQUENT-HANDOVER response. When MAP-PREPARE-SUBSEQUENT-HANDOVER response is received from 3G_MSC-A 3G_MSC-B sends IURELOCATION-COMMAND, which indicates the bearers failed to set up as bearers to be released, to RNS-A. After 3G_MSC-A receives MAP-SEND-END-SIGNAL request from 3G_MSC-B', 3G_MSC-A shall release calls via 3G_MSC-B', which has been carried by the bearers failed to set up, and then 3G_MSC-A sends MAP-SEND-ENDSIGNAL response to 3G_MSC-B.
3GPP
Release 6
71
3GPP TS 23.009 V6.5.0 (2008-12)
RNS-B
RNS-B' 3G_MSC-B' VLR-B' VLR-B
3G_MSC-A
3G_MSC-B
Iu-RELOCATIONREQUIRED MAP-Prep-Sub-Handover req. MAP-Prepare-Handover req. Iu-RELOCATIONREQUEST Iu-RELOCATIONREQUEST-ACK MAP-Allocate-Handover-Number req.
MAP-Prepare-Handover resp. IAM
MAP-Send-Handover-Report req. MAP-Send-Handover-Rep. resp. (1)
ACM MAP-Prep-Sub-Ho resp. Iu-RELOCATION-CMD Iu-RELOCATIONDETECT MAP-Process-Access-Signalling req. Iu-RELOCATIONCOMPLETE MAP-Send-End-Signal req. Answer Release MAP-Send-End-Signal resp. Iu-RELEASE-CMD/COM (end of call) Release MAP-Send-End-Signal resp.
Figure 33: Subsequent relocation procedure ii) Successful SRNS relocation from 3G_MSC-B to 3G_MSC-B' requiring a circuit connection
8.3.4
Procedure for subsequent relocation not requiring a circuit connection
As for the subsequent relocation with a circuit connection between 3G_MSC-A and 3G_MSC-B, the same two cases of subsequent relocation apply: i) the UE moves back to the area of 3G_MSC-A; ii) the UE moves into the area of a third 3G_MSC (3G_MSC-B'). If 3G_MSC-A is replaced by MSC-A in the procedures, then a subsequent relocation from 3G_MSC-B to 3G_MSC-B' shall not be possible since MSC-A does not support the RANAP protocol.
3GPP
Release 6
72
3GPP TS 23.009 V6.5.0 (2008-12)
8.3.4.1
Description of subsequent relocation procedure i): 3G_MSC-B to 3G_MSC-A
The procedure for successful relocation from 3G_MSC-B back to 3G_MSC-A without circuit connection is shown in figure 34. The only difference with the figure 32 is that no circuit release is needed between 3G_MSC-A and 3G_MSC-B.
RNS-B 3G_MSC-A 3G_MSC-B Iu-RELOCATIONREQUIRED
RNS-A VLR-B
MAP-Prep-Sub-Handover req. Iu-RELOCATIONREQUEST Iu-RELOCATIONREQUEST-ACK Iu-RELOCATIONDETECT Iu-RELOCATIONCOMPLETE MAP-Send-End-Signal resp. MAP-Prep-Sub-Handover resp.
Iu-RELEASECMD/COM
Figure 34: Subsequent relocation procedure i) successful relocation from 3G_MSC-B to 3G_MSC-B not requiring a circuit connection
8.3.4.2
Description of subsequent relocation procedure ii): 3G_MSC-B to 3G_MSC-B''
The procedure for successful relocation from 3G_MSC-B to 3G_MSC-B' is shown in figure 35. The procedure consists of two parts: a subsequent relocation from 3G_MSC-B back to 3G_MSC-A as described in clause 8.3.4.1; and a basic relocation from 3G_MSC-A to 3G_MSC-B' as described in clause 8.3.2.
3GPP
Release 6
73
3GPP TS 23.009 V6.5.0 (2008-12)
RNS-B
RNS-B' 3G_MSC-B' VLR-B' VLR-B
3G_MSC-A
3G_MSC-B
Iu-RELOCATIONREQUIRED MAP-Prep-Sub-Handover req. MAP-Prepare-Handover req. Iu-RELOCATIONREQUEST Iu-RELOCATIONREQUEST-ACK
MAP-Prepare-Handover resp. MAP-Prep-Sub-Ho resp. Iu-RELOCATION-CMD
Iu-RELOCATIONDETECT MAP-Process-Access-Signalling req. Iu-RELOCATIONCOMPLETE MAP-Send-End-Signal req. MAP-Send-End-Signal resp. Iu-RELEASE-CMD/COM (end of link) MAP-Send-End-Signal resp.
Figure 35: Subsequent relocation procedure ii) Successful SRNS relocation from 3G_MSC-B to 3G_MSC-B' not requiring a circuit connection
9
9.1
Detailed procedures in MSC-A

BSS/MSC and MS/MSC procedures in MSC-A (functional unit 1)
The handover procedures in this functional unit consist of: i) signalling between the MS and the MSC; ii) signalling between the BSS and the MSC for access management.
3GPP
Release 6
74
3GPP TS 23.009 V6.5.0 (2008-12)
9.2
-
Call control procedures MSC-A (functional unit 2)

the first entity is the call control procedure as part of the normal interworking between the PSTN/ISDN and the PLMN; for an MS originating call MSC-A is the originating exchange, for an MS terminating call MSC-A is the destination exchange; the second entity is the call control procedure for the connection between MSC-A and MSC-B in case of a handover from MSC-A to MSC-B. For this call control procedure the following applies.
The call control procedures related to handover in MSC-A can be divided into two functional entities:
Call set-up: the connection to MSC-B is set up by procedures relevant to the signalling system used in the PSTN/ISDN to which MSC-A is connected. The call is set up by using the MS Handover Number received from MSC-B as part of the MAP procedure; the call set-up direction will always be from MSC-A to MSC-B, even when the call was originally established by the MS. Functional unit 2 (see figure 2) should therefore keep information on call set-up direction in order to be able to interpret correctly any clearing signals (see below); the unit should indicate the address complete condition to functional unit 3 and through-connect without awaiting the answer signal from MSC-B. This applies also to signalling systems where address complete signals are not supported. In such cases an artificial address complete is established by functional unit 2.
Call clearing: call clearing consists of two parts: after inter-MSC handover, clearing of the MS-BSS connection and clearing of the inter-MSC connection. If a request to release the call is generated by the network while the MS is re-tuning from one BSS to another BSS, then MSC-A shall begin clearing the call to the network and queue the call release to the MS until the MS has resumed communication. This includes the case when MSC-B and/or MSC-B' are involved; the MAP procedures are used to transfer information between MSC-B and MSC-A in order to maintain full call control within MSC-A. MSC-A determines, based on information received from MSC-B, the appropriate signals (according to 3GPP TS 24.008 [10]) to be sent to the MS, and sends this information to MSC-B; when MSC-A clears the call to the MS it also clears the call control functions in MSC-B and sends the MAPSEND-END-SIGNAL response to release the MAP resources in MSC-B. The clearing of the connection is by procedures relevant to the signalling system in the PSTN/ISDN to which MSC-A is connected; when the Signalling System no 7 ISDN User Part is used, the normal symmetric release procedures apply on both the connection to the fixed network and to MSC-B; when a signalling system is used without a symmetric release possibility, some notice should be given to the clear-forward and clear-back procedures; for MS terminating calls the following conditions apply on clear-forward and clear-back: when a clear-forward signal is received on interface B' (see figure 1), MSC-A clears the circuit to MSC-B by normal clear-forward procedures; when a clear-back signal is received from MSC-B, MSC-A starts normal clear-back procedures towards the fixed network (interface B') and sends the clear-forward signal on interface B'' in order to clear the connection with MSC-B.
NOTE 1: This case corresponds to a fault situation. for MS originated calls the following applies: when MSC-A receives a clear-back signal from MSC-B, this signal must be interpreted as indicating a clearforward condition. MSC-A then clears both the connection on interface B' (see figure 1) and to MSC-B by normal clear-forward procedures.
NOTE 2: This case corresponds to a fault situation.
3GPP
Release 6
75
3GPP TS 23.009 V6.5.0 (2008-12)
when MSC-A receives a clear-back signal on interface B', MSC-A should distinguish between national and international connections: for international connections where the Q.118 [1] supervision is done in the ISC, MSC-A sends a clearforward signal on both interface B' to the fixed network and interface B'' to MSC-B; for national connections or for international connections where the Q.118 [1] supervision is not done in the ISC, a timer is started according to national practice for clear-back supervision and MSC-A proceeds as follows: i) if a clear-back signal is received from MSC-B, MSC-A interprets this as indicating a clear-forward condition and proceeds by clearing the connections on interface B' and to MSC-B by normal clearforward procedures; ii) if the timer expires, MSC-A proceeds by normal clear-forward of the connections on interface B' and to MSC-B.
9.3
Handover control procedures MSC-A (functional unit 3)
The procedures of functional unit 3 are given in terms of SDL diagrams in figure 41. To easily distinguish the interface concerned the messages received or sent from this unit are prefixed with either 'MAP' for a MAP message, 'A' for an AInterface message or 'I' for an ISDN/PSTN message. The procedures of functional unit 3 include: i) initiation. The initiation condition is shown by the signal A-HANDOVER-REQUIRED. The diagram also includes queuing when there is no channel available. Calls for which handover has been initiated should be queued with priority higher than normal calls. They should have lower priority than emergency calls. ii) handover of calls within the area of MSC-A, i.e. handover case i). In this case MSC-A controls the procedures on both the previous and the new radio channel, using signals A-HANDOVER-REQUEST and A-HANDOVERCOMMAND. The handover procedure is completed when A-HANDOVER-COMPLETE is received. If this signal is not received (expiry of timer T102), the radio path and the connection on interface B' are released. In the case of ongoing GSM voice group calls for subsequent users of the VGCS channel uplink the original connection shall always be maintained. For handover devices with three-party capabilities the handover device is first set up so that all interfaces A', A'' and B' are connected (illustrated by the signal 'set up handover device'). This is done when the Handover Command is sent to the MS . The device is connected in its final position (i.e. A'' to B' for case ii)) (illustrated by the signal 'connect handover device') when A-HANDOVER-COMPLETE is received. iii) handover to MSC-B . This procedure is the one described in clauses 7.1. and 7.2. For handover devices with three-party capabilities the handover device is set-up when MSC-A sends the Handover Command to the MS , i.e. the interfaces A', B' and B'' are then connected. The device is connected in its final position (i.e. B' to B'') when the successful procedure indication is received from functional unit 4. iv) subsequent handover to MSC-A . The procedure is described in clauses 7.3. and 7.4. When a handover to MSC-A indication is received from functional unit 4, the handover device is set up so that interfaces B', B'' and A' are connected (for handover devices with three-party capabilities). When A-HANDOVER-COMPLETE is received, the device is connected in its final position (i.e. B' to A'). If A-HANDOVER-COMPLETE is not received (expiry of timer T104), the handover device releases interface A', B' and B''.
3GPP
Release 6
76
3GPP TS 23.009 V6.5.0 (2008-12)
v) subsequent handover to a third MSC (MSC-B') . The procedure is described in clauses 7.3. and 7.4. The handover device is set up in its initial position, (i.e. interconnection of interfaces B', B'' and B''') when the connection to MSC-B' has been established. MSC-B is informed via functional unit 4 that the connection has been established and that the procedure on the radio path can be initiated. The device is connected in its final position (i.e. B' to B''') when a successful procedure indication is received from functional unit 4. MSC-B is informed that all procedures in MSC-B can be terminated (illustrated by the MAP-SEND-END-SIGNAL response). The device returns to the state where B' and B'' are connected if the subsequent handover procedure fails. Timers in MSC-A. The procedures are supervised by timers in order to avoid a deadlock when responses are not received or the procedures fail. The following timers are defined: T101: T102: T103: this timer supervises the queuing time for a free channel. If T101 expires, a no channel indication is generated, a retry procedure could be applied as described in clause 6.1. T101 is set by O&M, this timer supervises the time for handover completion for handover between BSSs in MSC-A. T102 is set by O&M, this timer supervises the time between issuing an A-HANDOVER-COMMAND from MSC-A and receiving a successful procedure indication from MSC-B. This timer also supervises the time between sending an A-HO-REQUEST-ACKNOWLEDGE to MSC-B and receiving a successful procedure indication from MSC-B'. If T103 expires, the handover procedure is terminated. T103 is set by O&M, this timer supervises the time between sending of an A-HO-REQUEST-ACKNOWLEDGE to MSC-B and receiving the A-HANDOVER-COMPLETE from BSS-B on MSC-A. If the timer expires, the new radio channel is released. T104 is set by O&M.
T104:
9.4
-
MAP procedures in MSC-A (functional unit 4)

procedures for basic handover; procedures for subsequent handover.
The MAP procedures for handover are defined in 3GPP TS 29.002 [12]. They include:
These procedures are as outlined in clause 7.
9.5
Interworking between Handover control procedures and MAP procedures in MSC-A
The interworking between the Handover control procedures and the MAP procedures for handover is defined in 3GPP TS 29.010 [8]. It includes: interworking at basic handover initiation; interworking at subsequent handover completion.
This interworking is not described in the present document.
9.6
Compatibility with GSM Phase 1
If the MSC-A initiates an Inter-MSC handover procedure according to Phase 2 MAP and BSSMAP protocols while using a Phase 1 BSSMAP protocol towards BSS-A, MSC-A has to perform the protocol interworking. The same holds if a Phase 2 BSSMAP protocol is used between MSC-A and BSS-A and the E-interface supports only Phase 1 protocol.
3GPP
Release 6
77
3GPP TS 23.009 V6.5.0 (2008-12)
10
10.1
Detailed procedures in MSC-B

BSS/MSC (MS/BSS) procedures MSC-B (functional unit 1)
The handover procedures in this functional unit consist of: i) signalling between the MS and the MSC; ii) signalling between the BS and the MSC for access management. Signals exchanged with functional unit 3 are indicated in clause 10.3.
10.2
Call control procedures MSC-B (functional unit 2)
These procedures relate to the call control in MSC-B of the "handover" connection with MSC-A. For these procedures the following apply: Call set-up: the connection is set up by MSC-A. MSC-B should provide, if possible, the following backward signals: signals indicating unsuccessful call set-up and, if possible, the cause of call failure; address complete signal; answer signal (see note). The answer signal is not related to answering by the MS and it has no meaning in the handover procedure between MSC-A and MSC-B. But after successful handover or successful subsequent channel assignment using a circuit connection between MSC-A and MSC-B this signal is needed for bringing the connection in the answered state in the intermediate PSTN/ISDN exchanges.
NOTE:
there will be no indication that the call applies to a handover. This information has to be derived from the MS Handover Number received during call set-up in relation to the earlier MAP-PREPARE-HANDOVER request/MAP-PREPARE-HANDOVER response procedure between MSC-A and MSC-B.
Call clearing: call clearing consists of two parts after inter-MSC handover: clearing of the BSS-MS connection and clearing of the inter-MSC connection, this case is only applicable to calls successfully handed over. If a request to release the call is generated by the network while the MS is re-tuning from one BSS to another BSS, then MSC-B shall begin clearing the call to the network and queue the call release to the MS until the MS has resumed communication; the MAP is used to transfer information between MSC-A and MSC-B in order to make it possible for MSC-B to send the appropriate signals to the MS, specified in 3GPP TS 24.008 [10], and still leave the call control to MSC-A. MSC-A normally initiates release of the connection between MSC-A and MSC-B. Exceptionally MSC-B is allowed to release the connection if no MAP-SEND-END-SIGNAL response is received, or if the Handover is to be aborted. when the Signalling System no 7 ISDN User Part is used, the normal symmetric release procedures apply. When a signalling system is used without a symmetric release possibility or a fault condition occurs, the following may apply: when MSC-B receives a clear-forward signal from MSC-A, it shall release the radio resources; in fault situation eg. machine malfunction or loss of the connection on interface A, MSC-B may send a clearback signal to MSC-A.
3GPP
Release 6
78
3GPP TS 23.009 V6.5.0 (2008-12)
10.3
Handover control procedures MSC-B (functional unit 3)
The procedures of functional unit 3 are given in form of SDL diagrams in figure 42. To easily distinguish the interface concerned the messages received or sent from this unit are prefixed with either 'MAP' for a MAP message, 'A' for an A-Interface message or 'I' for an ISDN/PSTN message. The procedure in functional unit 3 include: i) handover from MSC-A. This case is initiated by MSC-A, and includes allocation and establishment of the new radio channel. The procedure is outlined in clauses 7.1. and 7.2. ii) intra-MSC handovers within the area controlled by MSC-B. This procedure is the same as that of i) in clause 9.3, except that the A-HANDOVER-REQUIRED is received by MSC-B. After successful completion of the intra-MSC handover, MSC-B shall notify MSC-A by sending an AHANDOVER-PERFORMED message. iii) subsequent handover to another MSC (MSC-A or MSC-B'). The initiation procedure is essentially the same as that of i) of clause 9.3. The Handover Command to the MS is now generated by MSC-B after the A-HO-REQUEST-ACKNOWLEDGE is received from MSC-A (via functional unit 4). The procedure is terminated in MSC-B when MSC-B receives a terminate procedure indication from functional unit 4. Timers in MSC-B. The following procedures are supervised by timers in order to avoid a deadlock when responses are not received or the procedures fail. The following timers are defined: T201: T202: T204: this timer supervises the queuing time for a free channel. T201 is set by O&M; this timer supervises the time for handover completion for handover between BSSs in MSC-B. If T202 expires, the radio path and the connection on interface B' are released. T202 is set by O&M; this timer supervises the time between sending of address complete message to MSC-A and receiving the A-HANDOVER-COMPLETE from BSS-B on MSC-B. This timer also supervises the time between issuing the handover command to the MS and receiving the MAP-SEND-END-SIGNAL response from MSC-A, for a subsequent handover. In the case of a handover without circuit connection between MSC-A and MSC-B this timer supervises the time between issuing the A-HO-REQUEST-ACKNOWLEDGE to the MSC-A and receiving the A-HANDOVER-COMPLETE from BSS-B on MSC-B. If the timer expires, then any new radio channel is released. T204 is set by O&M; this timer is used to supervise the time for establishing a circuit connection from MSC-A to MSC-B. When T210 expires, the allocated channel in MSC-B is released. T210 is set by O&M. This timer is not started when MSC-A explicitly indicates that no handover number is needed; this timer is used to control the time between requesting a subsequent handover (A-HO-REQUEST to the MSC-A) and receiving the response from MSC-A (A-REQUEST-ACKNOWLEDGE/A-HO-FAILURE). If T211 expires, the existing connection with the MS is maintained. T211 is set by O&M.
T210:
T211:
10.4
-
MAP procedures MSC-B (functional unit 4)
The MAP procedures for handover are defined in 3GPP TS 29.002 [12]. They include: procedures for basic handover; procedures for subsequent handover; procedures for obtaining the handover number from the VLR.
These procedures are outlined in clause 7.
3GPP
Release 6
79
3GPP TS 23.009 V6.5.0 (2008-12)
10.5
Interworking between Handover control procedures and MAP procedures in MSC-B
The interworking between the Handover control procedures and the MAP procedures for handover is defined in 3GPP TS 29.010 [8]. It includes: interworking at basic handover completion; interworking at subsequent handover initiation.
10.6
If the MSC-B accepts an Inter-MSC handover procedure according to Phase 2 MAP and BSSMAP protocols while using a Phase 1 BSSMAP protocol towards BSS-B, MSC-B has to perform the protocol interworking. The same holds if a Phase 1 MAP protocol is requested on the E-interface and MSC-B uses a Phase 2 BSSMAP protocol towards BSS-B.
11
Detailed procedures in 3G_MSC-A
For detailed procedures in MSC-A at handover within the GSM network, please see clause 9 "Detailed procedures in MSC-A".
11.1
RNC/BSC/3G_MSC and UE/MS/3G_MSC procedures in 3G_MSC-A (functional unit 1)
The handover/relocation procedures in this functional unit consist of: i) signalling between the UE/MS and the 3G_MSC; ii) signalling between the RNS/BSS and the 3G_MSC for access management.
11.2
-
Call control procedures 3G_MSC-A (functional unit 2)
The call control procedures related to handover/relocation in 3G_MSC-A can be divided into two functional entities: the first entity is the call control procedure as part of the normal interworking between the PSTN/ISDN and the PLMN/UTRAN; for an UE/MS originating call 3G_MSC-A is the originating exchange, for an UE/MS terminating call 3G_MSC-A is the destination exchange; the second entity is the call control procedure for the connection between 3G_MSC-A and 3G_MSC-B in case of a handover/relocation from 3G_MSC-A to 3G_MSC-B. For this call control procedure the following applies.
Call set-up: the connection to 3G_MSC-B is set up by procedures relevant to the signalling system used in the PSTN/ISDN to which 3G_MSC-A is connected. The call is set up by using the Handover Number received from 3G_MSC-B as part of the MAP procedure; the call set-up direction will always be from 3G_MSC-A to 3G_MSC-B, even when the call was originally established by the UE/MS. Functional unit 2 (see figure 5) should therefore keep information on call set-up direction in order to be able to interpret correctly any clearing signals (see below); the unit should indicate the address complete condition to functional unit 3 and through-connect without awaiting the answer signal from 3G_MSC-B. This applies also to signalling systems where address complete signals are not supported. In such cases an artificial address complete is established by functional unit 2.
3GPP
Release 6
80
3GPP TS 23.009 V6.5.0 (2008-12)
Call clearing: call clearing consists of two parts: after handover/relocation, clearing of the RNS-UE/MS or BSS-UE/MS connection and clearing of the inter-3G_MSC connection. If a request to release the call is generated by the network while the UE/MS is re-tuning from one RNS/BSS to another RNS/BSS, then 3G_MSC-A shall begin clearing the call to the network and queue the call release to the UE/MS until the UE/MS has resumed communication. This includes the case when 3G_MSC-B and/or 3G_MSC-B' are involved; the MAP procedures are used to transfer information between 3G_MSC-B and 3G_MSC-A in order to maintain full call control within 3G_MSC-A. 3G_MSC-A determines, based on information received from 3G_MSC-B, the appropriate signals (according to 3GPP TS 24.008 [10]) to be sent to the UE/MS, and sends this information to 3G_MSC-B; when 3G_MSC-A clears the call to the UE/MS it also clears the call control functions in 3G_MSC-B and sends the MAP-SEND-END-SIGNAL response to release the MAP resources in 3G_MSC-B. The clearing of the connection is by procedures relevant to the signalling system in the PSTN/ISDN to which 3G_MSC-A is connected; when the Signalling System no 7 ISDN User Part is used, the normal symmetric release procedures apply on both the connection to the fixed network and to 3G_MSC-B; when a signalling system is used without a symmetric release possibility, some notice should be given to the clear-forward and clear-back procedures; for UE/MS terminating calls the following conditions apply on clear-forward and clear-back: when a clear-forward signal is received on interface B' (see figure 4), 3G_MSC-A clears the circuit to 3G_MSC-B by normal clear-forward procedures; when a clear-back signal is received from 3G_MSC-B, 3G_MSC-A starts normal clear-back procedures towards the fixed network (interface B') and sends the clear-forward signal on interface B'' in order to clear the connection with 3G_MSC-B.
NOTE 1: This case corresponds to a fault situation. for UE/MS originated calls the following applies: when 3G_MSC-A receives a clear-back signal from 3G_MSC-B, this signal must be interpreted as indicating a clear-forward condition. 3G_MSC-A then clears both the connection on interface B' (see figure 4) and to 3G_MSC-B by normal clear-forward procedures;
NOTE 2: This case corresponds to a fault situation. when 3G_MSC-A receives a clear-back signal on interface B', 3G_MSC-A should distinguish between national and international connections: for international connections where the Q.118 [1] supervision is done in the ISC, 3G_MSC-A sends a clear-forward signal on both interface B' to the fixed network and interface B'' to 3G_MSC-B; for national connections or for international connections where the Q.118 [1] supervision is not done in the ISC, a timer is started according to national practice for clear-back supervision and MSC-A proceeds as follows: i) if a clear-back signal is received from 3G_MSC-B, 3G_MSC-A interprets this as indicating a clearforward condition and proceeds by clearing the connections on interface B' and to 3G_MSC-B by normal clear-forward procedures; ii) if the timer expires, 3G_MSC-A proceeds by normal clear-forward of the connections on interface B' and to 3G_MSC-B.
3GPP
Release 6
81
3GPP TS 23.009 V6.5.0 (2008-12)
11.3
Handover/Relocation control procedures 3G_MSC-A (functional unit 3)
The procedures of functional unit 3 are given in terms of SDL diagrams in figure 43. To easily distinguish the interface concerned the messages received or sent from this unit are prefixed with either 'MAP' for a MAP message, 'A' for an AInterface message, 'I' for an ISDN/PSTN message or 'Iu' for an Iu-message. The procedures of functional unit 3 include: i) initiation. The initiation condition is shown by the signal Iu-RELOCATION-REQUIRED or A-HANDOVERREQUIRED; The diagram also includes queuing when there is no channel available. Calls for which handover/relocation has been initiated should be queued with priority higher than normal calls. They should have lower priority than emergency calls. ii) handover/relocation of calls within the area controlled by 3G_MSC-A, i.e. handover/relocation case i); In the handover/relocation from RNS-A/BSS-A to RNS-B/BSS-B 3G_MSC-A controls the procedures on both the previous and the new radio channel, using signals Iu-RELOCATION-REQUEST/A-HANDOVERREQUEST and Iu-RELOCATION-COMMAND/A-HANDOVER-COMMAND. The handover/relocation procedure is completed when Iu-RELOCATION-COMPLETE/A-HANDOVER-COMPLETE is received. If this signal is not received (expiry of timer T102, T302, T502 or T702), the radio path and the connection on interface B' are released. For handover/relocation devices with three-party capabilities the device is first set up so that all interfaces Iu'/A', Iu''/A'' and B' are connected (illustrated by the signal 'set up handover device'). This is done when the Relocation Command is sent to serving RNS or Handover Command is sent to the serving BSS. The device is connected in its final position (i.e. Iu''/ A'' to B' for case ii)) (illustrated by the signal 'connect handover device') when IuRELOCATION-COMPLETE/A-HANDOVER-COMPLETE is received. iii) relocation to 3G_MSC-B. This procedure is the one described in clauses 8.3.1 and 8.3.2. For handover/relocation devices with three-party capabilities the device is set-up when 3G_MSC-A sends the Relocation Command to the UE, i.e. the interfaces Iu', B' and B'' are then connected. The device is connected in its final position (i.e. B' to B'') when the successful procedure indication is received from functional unit 4; iv) UMTS to GSM handover to MSC-B. This procedure is the one described in clauses 8.1.1 and 8.1.2. For handover/relocation devices with three-party capabilities the device is set-up when 3G_MSC-A sends the Relocation Command to the serving RNS, i.e. the interfaces Iu', B' and B'' are then connected. The device is connected in its final position (i.e. B' to B'') when the successful procedure indication is received from functional unit 4; v) GSM to UMTS handover to 3G_MSC-B. This procedure is the one described in clauses 8.2.1 and 8.2.2. For handover/relocation devices with three-party capabilities the device is set-up when MSC-A sends the Handover Command to the serving BSS , i.e. the interfaces A', B' and B'' are then connected. The device is connected in its final position (i.e. B' to B'') when the successful procedure indication is received from functional unit 4; vi) subsequent relocation from 3G_MSC-B to 3G_MSC-A. The procedure is described in clauses 8.3.3.1 and 8.3.4.1. When a relocation to 3G_MSC-A indication is received from functional unit 4, the handover/relocation device is set up so that interfaces B', B'' and Iu' are connected (for devices with three-party capabilities). When Iu-RELOCATION-COMPLETE is received, the device is connected in its final position (i.e. B' to Iu'); If Iu-RELOCATION-COMPLETE is not received (expiry of timer T704), the handover/relocation device releases interface Iu', B' and B''. vii)subsequent GSM to UMTS handover from MSC-B to 3G_MSC-A. The procedure is described in clauses 8.2.3.1 and 8.2.4.1. When a handover to 3G_MSC-A indication is received from functional unit 4, the handover device is set up so that interfaces B', B'' and A' are connected (for handover devices with three-party capabilities). When Iu-RELOCATION-COMPLETE is received, the device is connected in its final position (i.e. B' to Iu'); If Iu-RELOCATION-COMPLETE is not received (expiry of timer T504), the device releases interface Iu', B' and B''.
3GPP
Release 6
82
3GPP TS 23.009 V6.5.0 (2008-12)
viii) subsequent UMTS to GSM handover from 3G_MSC-B to MSC-A. The procedure is described in clauses 8.1.3.1 and 8.1.4.1. When a handover to MSC-A indication is received from functional unit 4, the handover device is set up so that interfaces B', B'' and Iu' are connected (for handover devices with three-party capabilities). When A-HANDOVER-COMPLETE is received, the device is connected in its final position (i.e. B' to A'); If A-HANDOVER-COMPLETE is not received (expiry of timer T304), the device releases interface A', B' and B''. ix) subsequent relocation from 3G_MSC-B to a third 3G_MSC (3G_MSC-B'). The procedure is described in clauses 8.3.4.2 and 8.3.5.2. The handover/relocation device is set up in its initial position, (i.e. interconnection of interfaces B', B'' and B''') when the connection to 3G_MSC-B' has been established. 3G_MSC-B is informed via functional unit 4 that the connection has been established and that the procedure on the radio path can be initiated. The device is connected in its final position (i.e. B' to B''') when a successful procedure indication is received from functional unit 4. 3G_MSC-B is informed that all procedures in 3G_MSC-B can be terminated (illustrated by the MAP-SEND-END-SIGNAL response). The device returns to the state where B' and B'' are connected if the subsequent relocation procedure fails; x) subsequent UMTS to GSM handover from 3G_MSC-B to a third MSC (MSC-B'). The procedure is described in clauses 8.1.3.2 and 8.1.4.2. The handover/relocation device is set up in its initial position, (i.e. interconnection of interfaces B', B'' and B''') when the connection to MSC-B' has been established. 3G_MSC-B is informed via functional unit 4 that the connection has been established and that the procedure on the radio path can be initiated. The device is connected in its final position (i.e. B' to B''') when a successful procedure indication is received from functional unit 4. 3G_MSC-B is informed that all procedures in 3G_MSC-B can be terminated (illustrated by the MAP-SEND-END-SIGNAL response). The device returns to the state where B' and B'' are connected if the subsequent UMTS to GSM handover procedure fails; xi) subsequent GSM to UMTS handover from MSC-B to a third MSC (3G_MSC-B'). The procedure is described in clauses 8.2.3.2 and 8.2.4.2. The handover/relocation device is set up in its initial position, (i.e. interconnection of interfaces B', B'' and B''') when the connection to 3G_MSC-B' has been established. MSC-B is informed via functional unit 4 that the connection has been established and that the procedure on the radio path can be initiated. The device is connected in its final position (i.e. B' to B''') when a successful procedure indication is received from functional unit 4. MSC-B is informed that all procedures in MSC-B can be terminated (illustrated by the MAP-SEND-END-SIGNAL response). The device returns to the state where B' and B'' are connected if the subsequent GSM to UMTS handover procedure fails. NOTE: The procedures ii), vi) and vii) may be applied also in case of a handover/relocation to an RNC which is controlled by 3G_MSC-A by using the Flexible Iu interface for handover/relocation option.
Timers in 3G_MSC-A. The procedures are supervised by timers in order to avoid a deadlock when responses are not received or the procedures fail. The following timers are defined for SRNS Relocation: T701: this timer supervises the queuing time for a free channel for the relocation inside UMTS. If T701 expires, a no channel indication is generated and 3G_MSC-A will terminate the relocation as described in clause 6.2.3. T701 is set by O&M; this timer supervises the time for relocation completion for relocation between RNSs in 3G_MSC-A. T702 is set by O&M; this timer supervises the time between issuing an Iu-RELOCATION-COMMAND from 3G_MSC-A and receiving a successful procedure indication from 3G_MSC-B. This timer also supervises the time between sending an IU-RELOCATION-REQUEST-ACKNOWLEDGE to 3G_MSC-B and receiving a successful procedure indication from 3G_MSC-B'. If T703 expires, the relocation procedure is terminated. T703 is set by O&M; this timer supervises the time between sending of an IU-RELOCATION-REQUEST-ACKNOWLEDGE to 3G_MSC-B and receiving the Iu-RELOCATION-COMPLETE from RNS-B on 3G_MSC-A. If the timer expires, the new radio channel is released. T704 is set by O&M.
T702: T703:
T704:
3GPP
Release 6
83
3GPP TS 23.009 V6.5.0 (2008-12)
The following timers are defined for UMTS to GSM handover: T301: this timer supervises the queuing time for a free channel for the UMTS to GSM handover. If T301 expires, a no channel indication is generated and 3G_MSC-A will terminate the handover as described in clause 6.2.3. T301 is set by O&M; this timer supervises the time for UMTS to GSM handover completion for handover from RNS to BSS in 3G_MSC-A. T302 is set by O&M; this timer supervises the time between issuing an Iu-RELOCATION-COMMAND from 3G_MSC-A and receiving a successful procedure indication from MSC-B. This timer also supervises the time between sending an A-HO-REQUEST-ACKNOWLEDGE to MSC-B and receiving a successful procedure indication from MSC-B'. If T303 expires, the UMTS to GSM handover procedure is terminated. T303 is set by O&M; this timer supervises the time between sending of an A-HO-REQUEST-ACKNOWLEDGE to MSC-B and receiving the A-HANDOVER-COMPLETE from BSS-B on 3G_MSC-A. If the timer expires, the new radio channel is released. T304 is set by O&M.
T302: T303:
T304:
The following timers are defined for GSM to UMTS handover: T501: this timer supervises the queuing time for a free channel for the GSM to UMTS handover. If T501 expires, a no channel indication is generated and 3G_MSC-A will terminate the handover as described in clause 6.2.3. T501 is set by O&M; this timer supervises the time for GSM to UMTS handover completion for handover from BSS to RNS in 3G_MSC-A. T502 is set by O&M; this timer supervises the time between issuing an A-HANDOVER-COMMAND from MSC-A and receiving a successful procedure indication from 3G_MSC-B. This timer also supervises the time between sending an A-HANDOVER-REQUEST-ACKNOWLEDGE to 3G_MSC-B and receiving a successful procedure indication from 3G_MSC-B'. If T503 expires, the GSM to UMTS handover procedure is terminated. T503 is set by O&M; this timer supervises the time between sending of an A-HANDOVER-REQUEST-ACKNOWLEDGE to 3G_MSC-B and receiving the Iu-RELOCATION-COMPLETE from RNS-B on 3G_MSC-A. If the timer expires, the new radio channel is released. T504 is set by O&M.
T502: T503:
T504:
11.4
-
MAP procedures in 3G_MSC-A (functional unit 4)
The MAP procedures for handover/relocation are defined in 3GPP TS 29.002 [12]. They include: procedures for basic handover/relocation; procedures for subsequent handover/relocation.
These procedures are as outlined in clause 8.
11.5
Interworking between Handover/Relocation control procedures and MAP procedures in 3G_MSC-A
The interworking between the Handover/Relocation control procedures and the MAP procedures for handover/relocation is defined in 3GPP TS 29.010 [8]. It includes: interworking at basic handover/relocation initiation; interworking at subsequent handover/relocation completion.
3GPP
Release 6
84
3GPP TS 23.009 V6.5.0 (2008-12)
11.6
Interworking with the GSM Phase 1 is not supported.
11.7
Protocol interworking
If the 3G_MSC-A initiates a basic inter-MSC UMTS to GSM handover procedure according to MAP and BSSMAP protocols while using a RANAP protocol towards RNS-A, 3G_MSC-A has to perform the protocol interworking between RANAP on the Iu-Interface and encapsulated BSSMAP on the E-interface. The same holds if 3G_MSC-A accepts a subsequent inter-3G_MSC GSM to UMTS handover back to 3G_MSC-A while using a RANAP protocol towards RNS-B.
12
Detailed procedures in 3G_MSC-B
For detailed procedures in 3G_MSC-B at handover within the GSM network, please see clause 10 'Detailed procedures in MSC-B'.
12.1
RNC/BSC/3G_MSC (UE/MS/RNC/BSC) procedures in 3G_MSC-B (functional unit 1)
The Intra and Inter-3G_MSC handover/relocation procedures in this functional unit consist of: i) signalling between the UE/MS and the 3G_MSC; ii) signalling between the RNS/BSS and the 3G_MSC for access management. Signals exchanged with functional unit 3 are indicated in clause 12.3.
12.2
Call control procedures 3G_MSC-B (functional unit 2)
These procedures relate to the call control in 3G_MSC-B of the "3G_MSC handover/relocation" connection with 3G_MSC-A. For these procedures the following apply: Call set-up: the connection is set up by 3G_MSC-A. 3G_MSC-B should provide, if possible, the following backward signals: signals indicating unsuccessful call set-up and, if possible, the cause of call failure; address complete signal; answer signal (see note). The answer signal is not related to answering by the UE/MS and it has no meaning in the 3G_MSC handover/relocation procedure between 3G_MSC-A and 3G_MSC-B. But after successful handover/relocation or successful subsequent channel assignment using a circuit connection between 3G_MSC-A and 3G_MSC-B this signal is needed for bringing the connection in the answered state in the intermediate PSTN/ISDN exchanges.
NOTE:
there will be no indication that the call applies to a 3G_MSC handover/relocation. This information has to be derived from the UE/MS Handover Number received during call set-up in relation to the earlier MAPPREPARE-HANDOVER request/MAP-PREPARE-HANDOVER response procedure between 3G_MSC-A and 3G_MSC-B.
3GPP
Release 6
85
3GPP TS 23.009 V6.5.0 (2008-12)
Call clearing: call clearing consists of two parts after inter-3G_MSC handover/relocation: clearing of the RNS-UE/MS or the BSS-UE/MS connection and clearing of the inter-3G_MSC connection, these cases are only applicable to calls successfully handed over or relocated. If a request to release the call is generated by the network while the UE/MS is re-tuning from one RNS/BSS to another RNS/BSS, then 3G_MSC-B shall begin clearing the call to the network and queue the call release to the UE/MS until the UE/MS has resumed communication; the MAP is used to transfer information between 3G_MSC-A and 3G_MSC-B in order to make it possible for 3G_MSC-B to send the appropriate signals to the UE/MS, specified in 3GPP TS 24.008 [10], and still leave the call control to 3G_MSC-A. 3G_MSC-A normally initiates release of the connection between 3G_MSC-A and 3G_MSC-B. Exceptionally 3G_MSC-B is allowed to release the connection if no MAP-SEND-END-SIGNAL response is received, or if the 3G_MSC Handover/Relocation is to be aborted; when the Signalling System no 7 ISDN User Part is used, the normal symmetric release procedures apply. When a signalling system is used without a symmetric release possibility or a fault condition occurs, the following may apply: when 3G_MSC-B receives a clear-forward signal from 3G_MSC-A, it shall release the radio resources; in fault situation e.g. machine malfunction or loss of the connection on interface Iu or interface A, 3G_MSC-B may send a clear-back signal to 3G_MSC-A.
12.3
Handover/Relocation control procedures in 3G_MSC-B (functional unit 3)
The procedures of functional unit 3 are given in form of SDL diagrams in figure 44. To easily distinguish the interface concerned the messages received or sent from this unit are prefixed with either 'MAP' for a MAP message, 'A' for an A-Interface message, 'Iu' for an Iu-Interface message or 'I' for an ISDN/PSTN message. The procedure in functional unit 3 include: i) inter 3G_MSC handover/relocation from 3G_MSC-A; This case is initiated by 3G_MSC-A, and includes allocation and establishment of the new radio resources. The procedure is outlined in clauses 8.1.1 and 8.1.2. for UMTS to GSM handover, clauses 8.2.1 and 8.2.2 for GSM to UMTS handover and clauses 8.3.1 and 8.3.2 for relocation. ii) intra-3G_MSC UMTS to GSM handovers within the area controlled by 3G_MSC-B; This procedure is the same as that of ii) in clause 11.3, except that the Iu-RELOCATION-REQUIRED is received by 3G_MSC-B. After successful completion of the intra-3G_MSC handover, 3G_MSC-B shall notify 3G_MSC-A by sending an A-HANDOVER-PERFORMED message. iii) intra-3G_MSC GSM to UMTS handovers within the area controlled by 3G_MSC-B; This procedure is the same as that of ii) in clause 11.3, except that the A-HANDOVER-REQUIRED is received by 3G_MSC-B. After successful completion of the intra-3G_MSC handover, 3G_MSC-B shall notify 3G_MSCA by sending an A-HANDOVER-PERFORMED message. iv) intra-3G_MSC SRNS Relocation within the area controlled by 3G_MSC-B; This procedure is the same as that of ii) in clause 11.3, except that the Iu-RELOCATION-REQUIRED is received by 3G_MSC-B. After successful completion of the intra-3G_MSC SRNS relocation, if security algorithms have been changed, 3G_MSC-B shall notify 3G_MSC-A by sending an A-HANDOVERPERFORMED or an Iu-LOCATION-REPORT message, depending on the access network protocol used encapsulated on the E-interface (see subclauses 4.4.1 and 6.2.3). v) subsequent handover/relocation to another 3G_MSC (3G_MSC-A or 3G_MSC-B'); The initiation procedure is essentially the same as that of i) of clause 11.3. The Handover Command to the BSS or the Relocation Command to the RNS is now generated by 3G_MSC-B after the A-HO-REQUESTACKNOWLEDGE or Iu-RELOCATION-REQUEST-ACKNOWLEDGE is received from 3G_MSC-A (via
3GPP
Release 6
86
3GPP TS 23.009 V6.5.0 (2008-12)
functional unit 4). The procedure is terminated in 3G_MSC-B when 3G_MSC-B receives a terminate procedure indication from functional unit 4. NOTE: The procedures iii), iv) and, in case of a subsequent handover back to 3G_MSC-A, the procedure v) may be applied also in case of a handover/relocation to an RNC which is controlled by 3G_MSC-B or 3G_MSC-A respectively by using the "Flexible Iu interface for handover/relocation" option.
Timers in 3G_MSC-B. The following procedures are supervised by timers in order to avoid a deadlock when responses are not received or the procedures fail. The following timers are defined for UMTS to GSM handover: T401: T402: this timer supervises the queuing time for a free channel. T401 is set by O&M; this timer supervises the time for handover completion for UMTS to GSM handover from RNS to BSS in 3G_MSC-B. If T402 expires, the radio path and the connection on interface B' are released. T402 is set by O&M; this timer supervises the time between sending of address complete message to 3G_MSC-A and receiving the A-HANDOVER-COMPLETE from BSS-B on 3G_MSC-B. This timer also supervises the time between issuing the handover command to the UE/MS and receiving the MAP-SEND-END-SIGNAL response from 3G_MSC-A, for a subsequent handover from UMTS to GSM. In the case of a UMTS to GSM handover without circuit connection between 3G_MSC-A and 3G_MSC-B this timer supervises the time between issuing the A-HO-REQUEST-ACKNOWLEDGE to the 3G_MSC-A and receiving the AHANDOVER-COMPLETE from BSS-B on 3G_MSC-B. If the timer expires, then any new radio channel is released. T404 is set by O&M; this timer is used to supervise the time for establishing a circuit connection from 3G_MSC-A to 3G_MSC-B. When T410 expires, the allocated channel in 3G_MSC-B is released. T410 is set by O&M. This timer is not started when 3G_MSC-A explicitly indicates that no handover number is needed; this timer is used to control the time between requesting a subsequent UMTS to GSM handover (A-HO-REQUEST to the 3G_MSC-A) and receiving the response from 3G_MSC-A (A-HO-REQUESTACKNOWLEDGE/A-HO-FAILURE). If T411 expires, the existing connection with the UE/MS is maintained. T411 is set by O&M.
T404:
T410:
T411:
The following timers are defined for GSM to UMTS handover: T601: T602: this timer supervises the queuing time for a free radio resource. T601 is set by O&M; this timer supervises the time for handover completion for GSM to UMTS handover from BSS to RNS in 3G_MSC-B. If T602 expires, the radio path and the connection on interface B' are released. T602 is set by O&M; this timer supervises the time between sending of address complete message to 3G_MSC-A and receiving the Iu-RELOCATION-COMPLETE from RNS-B on 3G_MSC-B. This timer also supervises the time between issuing the handover command to the UE/MS and receiving the MAP-SEND-END-SIGNAL response from 3G_MSC-A, for a subsequent handover from GSM to UMTS. In the case of a GSM to UMTS handover without circuit connection between 3G_MSC-A and 3G_MSC-B this timer supervises the time between issuing the A-HO-REQUEST-ACKNOWLEDGE to the 3G_MSC-A and receiving the IuRELOCATION-COMPLETE from RNS-B on 3G_MSC-B. If the timer expires, then any new radio resource is released. T604 is set by O&M; this timer is used to supervise the time for establishing a circuit connection from 3G_MSC-A to 3G_MSC-B. When T610 expires, the allocated radio resource in 3G_MSC-B is released. T610 is set by O&M. This timer is not started when 3G_MSC-A explicitly indicates that no handover number is needed; this timer is used to control the time between requesting a subsequent GSM to UMTS handover (A-HO-REQUEST to the 3G_MSC-A) and receiving the response from 3G_MSC-A (A-HO-REQUESTACKNOWLEDGE/A-HO-FAILURE). If T611 expires, the existing connection with the UE/MS is maintained. T611 is set by O&M.
T604:
T610:
T611:
The following timers are defined for SRNS Relocation:
3GPP
Release 6
87
3GPP TS 23.009 V6.5.0 (2008-12)
T801: T802: T804:
this timer supervises the queuing time for a free radio resource. T801 is set by O&M; this timer supervises the time for relocation completion for relocation between RNSs in 3G_MSC-B. If T802 expires, the radio path and the connection on interface B' are released. T802 is set by O&M; this timer supervises the time between sending of address complete message to 3G_MSC-A and receiving the Iu-RELOCATION-COMPLETE from RNS-B on 3G_MSC-B. This timer also supervises the time between issuing the handover command to the UE and receiving the MAP-SEND-END-SIGNAL response from 3G_MSC-A, for a subsequent relocation. In the case of a relocation without circuit connection between 3G_MSC-A and 3G_MSC-B this timer supervises the time between issuing the Iu-RELOCATION-REQUEST-ACKNOWLEDGE to the 3G_MSC-A and receiving the Iu-RELOCATION-COMPLETE from RNS-B on 3G_MSC-B. If the timer expires, then any new radio resource is released. T804 is set by O&M; this timer is used to supervise the time for establishing a circuit connection from 3G_MSC-A to 3G_MSC-B. When T810 expires, the allocated channel in 3G_MSC-B is released. T810 is set by O&M. This timer is not started when 3G_MSC-A explicitly indicates that no handover number is needed; this timer is used to control the time between requesting a subsequent relocation (Iu-RELOCATIONREQUEST to the 3G_MSC-A) and receiving the response from 3G_MSC-A (Iu-RELOCATIONREQUEST-ACKNOWLEDGE/ Iu-RELOCATION-FAILURE). If T811 expires, the existing connection with the UE is maintained. T811 is set by O&M.
T810:
T811:
12.4
-
MAP procedures in 3G_MSC-B (functional unit 4)
The MAP procedures for handover/relocation are defined in 3GPP TS 29.002 [12]. They include: procedures for basic handover/relocation; procedures for subsequent handover/relocation; procedures for obtaining the handover number from the VLR.
These procedures are outlined in clause 8.
12.5
Interworking between Handover/Relocation control procedures and MAP procedures in 3G_MSC-B
The interworking between the Handover/Relocation control procedures and the MAP procedures for handover/relocation is defined in 3GPP TS 29.010 [8]. It includes: interworking at basic handover/relocation completion; interworking at subsequent handover/relocation initiation.
12.6
GSM phase 1 is not supported.
12.7
Protocol interworking
If the 3G_MSC-B accepts an Inter-3G_MSC GSM to UMTS handover procedure according to MAP and BSSMAP protocols while using a RANAP protocol towards RNS-B, 3G_MSC-B has to perform the protocol interworking between RANAP on the Iu-Interface and encapsulated BSSMAP on the E-interface. The same holds if 3G_MSC-B initiates a subsequent inter-MSC UMTS to GSM handover while using a RANAP protocol towards RNS-A.
3GPP
Release 6
88
3GPP TS 23.009 V6.5.0 (2008-12)
If during the supervision, i.e. while the UE/MS is not in the area of MSC-A or 3G_MSC-A, the protocol used encapsulated on the E-interface and the protocol used between 3G_MSC-B and the serving BSS or RNS are different, then 3G_MSC-B has to perform the protocol interworking between BSSAP and RANAP. NOTE: The two protocols are different, e.g., after an inter-MSC GSM to UMTS inter-system handover, or after an inter-MSC SRNS relocation to 3G_MSC-B followed by a subsequent intra-3G_MSC-B UMTS to GSM inter-system handover.
12.8 Interactions between handover/relocation control procedures and other RANAP procedures
This clause gives an overview of the procedures that shall be followed when handover/relocation control procedures interact with other RANAP procedures on 3G_MSC-B.
12.8.1
12.8.1.1
Interactions between handover/relocation control procedures and the security mode procedure
Intra-3G_MSC-B handover/relocation
A security mode control procedure may be requested by MSC-A/3G_MSC-A after an Inter-MSC GSM to UMTS handover or Inter-MSC SRNS relocation. If RNS-A replies with an Iu-SECURITY-MODE-REJECT containing the cause value 'Relocation Triggered' due to an already initiated Intra-3G_MSC-B UMTS to GSM handover or Intra3G_MSC-BSRNS relocation, the 3G_MSC-B shall not forward the result of the security mode control procedure to MSC-A/3G_MSC-A, but wait for the outcome of the handover/relocation procedure. If the relocation procedure is completed successfully, the 3G_MSC-B shall reattempt the security mode control procedure towards the new serving radio network. If the handover procedure is completed successfully, the 3G_MSC-B shall reattempt the cipher mode control procedure towards the new serving radio network, if ciphering is to be activated.
3GPP
Release 6
89
3GPP TS 23.009 V6.5.0 (2008-12)
BSS-A
3G_MSC-A 3G MSC-B Inter-MSC HO Completed MAP-Forward-Access-Sig req. -Sig req. Iu-SECURITYMODECOMMAND
UE/RNS-A
BSS-B/UE
Iu-RELOCATIONREQUIRED Iu-SECURITYMODE-REJECT
A-HO-REQUEST A-HO-REQUEST-ACK
A-HO-DETECT A-HO-COMPLETE
MAP-Process-Access-Sig req. Sig req.
Iu-RELEASECMD/CMP A-CIPHER-MODE-COMMAND A-CIPHER-MODE-COMPLETE
MAP-Process-Access-Sig req. ig req.
NOTE:
The message flow is shown in the perspective of 3G_MSC-B. It is assumed that RNS-A has sent the IuRELOCATION-REQUIRED before it received the Iu-SECURITY-MODE-COMMAND.
Figure 35a: Collision between a subsequent Intra-3G_MSC-B handover/relocation and a security mode control procedure i): successful handover/relocation If the handover/relocation procedure is unsuccessful and the UE is still served by RNS-A, the 3G_MSC-B shall reattempt the security mode procedure towards RNS-A.
3GPP
Release 6
90
3GPP TS 23.009 V6.5.0 (2008-12)
BSS-A
3G_MSC-A Inter-MSC HO Completed
3G MSC-B
UE/RNS-A
BSS-B/UE
MAP-Forward-Access-Sig req. -Sig req.
Iu-SECURITYMODECOMMAND Iu-RELOCATIONREQUIRED Iu-SECURITYMODE-REJECT
A-HO-REQUEST A-HO-FAILURE
Iu-RELOCATIONPREPARATIONFAILURE Iu-SECURITYMODECOMMAND Iu-SECURITYMODECOMPLETE
MAP-Process-Access-Sig req. ..Sig req.
NOTE:
Figure 35b: Collision between a subsequent Intra-3G_MSC-B handover/relocation and a security mode control procedure ii): unsuccessful handover/relocation
12.8.1.2
Subsequent Inter-MSC handover/relocation
A security mode control procedure may be requested by MSC-A/3G_MSC-A after an Inter-MSC GSM to UMTS handover or Inter-MSC SRNS relocation. If RNS-A replies with an Iu-SECURITY-MODE-REJECT containing the cause value 'Relocation Triggered' due to an already initiated subsequent Inter-MSC handover/relocation, the 3G_MSCB shall not forward the result of the security mode procedure to MSC-A/3G_MSC-A, but wait for the outcome of the handover/relocation procedure. If the subsequent Inter-MSC relocation procedure is completed successfully, the 3G_MSC-A shall reattempt the security mode control procedure towards the new serving radio network or MSCB'/3G_MSC-B'. If the subsequent Inter-MSC handover procedure is completed successfully, the MSC-A/3G_MSC-A shall reattempt the cipher mode control procedure towards the new serving radio network or MSC-B'/3G_MSC-B, if ciphering is to be activated.
3GPP
Release 6
91
3GPP TS 23.009 V6.5.0 (2008-12)
BSS-B/UE BSS-A 3G_MSC-A 3G MSC-B Inter-MSC HO Completed MAP-Forward-Access-Sig req. -Sig req. Iu-SECURITYMODECOMMAND Iu-RELOCATIONREQUIRED Iu-SECURITYMODE-REJECT UE/RNS-A MSC-B
MAP-Prep-Sub-Handover req.
MAP-Prep-Handover req. A-HO-REQUEST A-HO-REQUEST-ACK MAP-Prep-Handover rsp. MAP-Prep-Sub-Handover rsp. Iu-RELOCATIONCOMMAND MAP-Process-Access-Sig req. A-HO-COMPLETE MAP-Send-End-Signal req. MAP-Send-End-Signal rsp Iu-RELEASECMD/CMP MAP-Forward-Access-Sig req. -Sig req. A-CIPHER-MODECOMMAND A-CIPHER-MODECOMPLETE A-HO-DETECT
MAP-Process-Access-Sig req.
NOTE:
Figure 35ba: Collision between a subsequent Inter-MSC handover/relocation and a security mode control procedure i): successful handover/relocation If the subsequent Inter-MSC handover/relocation procedure is unsuccessful and the UE is still served by 3G_MSC-B, the 3G_MSC-B shall reattempt the security mode procedure towards RNS-A.
3GPP
Release 6
92
3GPP TS 23.009 V6.5.0 (2008-12)
BSS-B/UE BSS-A 3G_MSC-A 3G MSC-B Inter-MSC HO Completed MAP-Forward-Access-Sig req -Sig req. Iu-SECURITYMODECOMMAND Iu-RELOCATIONREQUIRED Iu-SECURITYMODE-REJECT UE/RNS-A MSC-B
MAP-Prep-Handover req. A-HO-REQUEST A-HO-FAILURE MAP-Prep-Handover rsp. MAP-Prep-Sub-Handover rsp. Iu-RELOCATIONPREPARATIONFAILURE Iu-SECURITYMODECOMMAND Iu-SECURITYMODECOMPLETE
MAP-Process-Access-Sig req. Sig req.
NOTE:
Figure 35bb: Collision between a subsequent Intra-3G_MSC-B handover/relocation and a security mode control procedure ii): unsuccessful handover/relocation
12.8.2
12.8.2.1
Interactions between handover/relocation control procedures and the RAB assignment procedure
Intra-3G_MSC-B handover/relocation
A subsequent channel assignment procedure may be requested by MSC-A/3G_MSC-A after an Inter-MSC GSM to UMTS handover or Inter-MSC SRNS relocation without circuit connection (see subclauses 13.2 and 13.4). If RNS-A replies with an Iu-RAB-ASSIGNMENT-RESPONSE containing the cause value 'Relocation Triggered' due to an already initiated Intra-3G_MSC-B UMTS to GSM handover or Intra-3G_MSC-B SRNS relocation, the 3G_MSC-B shall not forward the result of the RAB assignment procedure to MSC-A/3G_MSC-A, but wait for the outcome of the handover/relocation procedure. If the handover/relocation procedure is completed successfully, the 3G_MSC-B shall construct an A-ASSIGNMENT-COMPLETE or Iu-RAB-ASSIGNMENT-RESPONSE message, dependent on the encapsulated protocol used on the E-interface, and forward this message to MSC-A/3G_MSC-A in the MAPPREPARE-HANDOVER response.
3GPP
Release 6
93
3GPP TS 23.009 V6.5.0 (2008-12)
BSS-A
3G_MSC-A 3G MSC-B Inter-MSC HO Completed MAP-Prep-Handover req.
UE/RNS-A
BSS-B/UE
Iu-RABASSIGNMENTREQUEST Iu-RELOCATIONREQUIRED Iu-RABASSIGNMENTRESPONSE
MAP-Prep-Handover rsp. Iu-RELEASECMD/CMP
NOTE:
The message flow is shown in the perspective of 3G_MSC-B. It is assumed that RNS-A has sent the IuRELOCATION-REQUIRED before it received the Iu-RAB-ASSIGNMENT-REQUEST.
Figure 35c: Collision between a subsequent Intra-3G_MSC-B handover/relocation and a RAB assignment procedure i): successful handover/relocation If the handover/relocation procedure is unsuccessful and the UE is still served by RNS-A, the 3G_MSC-B shall reattempt the RAB assignment procedure towards RNS-A.
3GPP
Release 6
94
3GPP TS 23.009 V6.5.0 (2008-12)
BSS-A
3G_MSC-A Inter-MSC HO Completed
3G MSC-B
UE/RNS-A
BSS-B/UE
MAP-Prep-Handover req. Iu-RABASSIGNMENTREQUEST Iu-RELOCATIONREQUIRED Iu-RABASSIGNMENTRESPONSE
A-HO-REQUEST A-HO-FAILURE
Iu-RELOCATIONPREPARATIONFAILURE Iu-RABASSIGNMENTREQUEST Iu-RABASSIGNMENTRESPONSE
MAP-Prep-Handover rsp.
NOTE:
Figure 35d: Collision between a subsequent Intra-3G_MSC-B handover/relocation and a RAB assignment procedure ii): unsuccessful handover/relocation
12.8.2.2
Subsequent Inter-MSC handover/relocation
A subsequent channel assignment procedure may be requested by MSC-A/3G_MSC-A after an Inter-MSC GSM to UMTS handover or Inter-MSC SRNS relocation without circuit connection (see subclauses 13.2 and 13.4). If RNS-A replies with an Iu-RAB-ASSIGNMENT-RESPONSE containing the cause value 'Relocation Triggered' due to an already initiated subsequent Inter-MSC handover/relocation, the 3G_MSC-B shall not forward the result of the RAB Assignment procedure to MSC-A/3G_MSC-A, but wait for the outcome of the handover/relocation procedure.
3GPP
Release 6
95
3GPP TS 23.009 V6.5.0 (2008-12)
BSS-B/UE BSS-A 3G_MSC-A 3G MSC-B Inter-MSC HO Completed MAP-Prep-Handover req. Iu-RABASSIGNMENTREQUEST Iu-RELOCATIONREQUIRED MAP-Prep-Sub-Handover req. Iu-RABASSIGNMENTRESPONSE A-HO-REQUEST A-HO-REQUEST-ACK MAP-Prep-Handover rsp. IAM. ACM. MAP-Prep-Sub-Handover rsp. Iu-RELOCATIONCOMMAND MAP-Process-Access-Sig req. A-HO-COMPLETE MAP-Send-End-Signal req. ANM. MAP-Send-End-Signal rsp Iu-RELEASECMD/CMP A-HO-DETECT UE/RNS-A MSC-B
MAP-Prep-Handover req.
NOTE:
Figure 35da: Collision between a subsequent Inter-MSC handover/relocation and a RAB assignment procedure i): successful handover/relocation If the subsequent Inter-MSC handover/relocation procedure is unsuccessful and the UE is still served by 3G_MSC-B, the 3G_MSC-B shall reattempt the subsequent channel assignment procedure towards RNS-A.
3GPP
Release 6
96
3GPP TS 23.009 V6.5.0 (2008-12)
BSS-B/UE BSS-A 3G_MSC-A 3G MSC-B Inter-MSC HO Completed MAP- Prep-Handover req. Iu-RABASSIGNMENTREQUEST Iu-RELOCATIONREQUIRED MAP-Prep-Sub-Handover req. Iu-RABASSIGNMENTRESPONSE A-HO-REQUEST A-HO-FAILURE MAP-Prep-Handover rsp. MAP-Prep-Sub-Handover rsp. Iu-RELOCATIONPREPARATIONFAILURE Iu- RABASSIGNMENTREQUEST Iu- RABASSIGNMENTRESPONSE UE/RNS-A MSC-B
MAP-Prep-Handover req.
MAP- Prep-Handover rsp
NOTE:
Figure 35db: Collision between a subsequent Inter-MSC handover/relocation and a RAB assignment procedure ii): unsuccessful handover/relocation
12.8.3
12.8.3.1
Interactions between directed retry handover procedures and the RAB assignment procedure
Intra-3G_MSC-B directed retry handover
For a description of the directed retry handover procedure see subclause 14.3. A subsequent channel assignment procedure may be requested by MSC-A/3G_MSC-A after an Inter-MSC GSM to UMTS handover or Inter-MSC SRNS relocation without circuit connection (see subclauses 13.2 and 13.4). If RNS-A replies with an Iu-RAB-ASSIGNMENT-RESPONSE containing the cause value 'Directed Retry' and the subsequent IuRELOCATION-REQUIRED indicates that an Intra-3G_MSC-B directed retry handover is required, the 3G_MSC-B shall not forward the result of the RAB assignment procedure to MSC-A/3G_MSC-A, but wait for the outcome of the directed retry handover procedure. If the directed retry handover procedure is completed successfully, the 3G_MSC-B shall construct an A-ASSIGNMENT-COMPLETE or Iu-RAB-ASSIGNMENT-RESPONSE message, dependent on the encapsulated protocol used on the E-interface, and forward this message to MSC-A/3G_MSC-A in the MAPPREPARE-HANDOVER response.
3GPP
Release 6
97
3GPP TS 23.009 V6.5.0 (2008-12)
BSS-A
3G_MSC-A 3G MSC-B Inter-MSC HO Completed MAP-Prep-Handover req.
UE/RNS-A
BSS-B/UE
Iu-RABASSIGNMENTREQUEST Iu-RABASSIGNMENTRESPONSE Iu-RELOCATIONREQUIRED
MAP-Prep-Handover rsp. Iu-RELEASECMD/CMP
Figure 35e: Interaction between a RAB assignment procedure and a subsequent Intra-3G_MSC-B directed retry handover i): successful directed retry handover If the directed retry handover procedure is unsuccessful and the UE is still served by RNS-A, the 3G_MSC-B may optionally take one of a number of actions: i) send an Iu-RELOCATION-PREPARATION FAILURE to RNS-A, if an Iu-RELOCATION-COMMAND has not already been sent. Additionally 3G_MSC-B may retry the assignment procedure to RNS-A; ii) retry the assignment procedure to RNS-A, if the failure message was returned from RNS-A. This option is additional to those for normal handover; iii) construct an A-ASSIGNMENT-FAILURE message containing the cause value 'Radio interface failure, reversion to old channel' or Iu-RAB-ASSIGNMENT-RESPONSE message containing the cause value 'Failure In The Radio Interface Procedure', dependent on the encapsulated protocol used on the E-interface, and forward this message to MSC-A/3G_MSC-A.
12.8.3.2
Subsequent Inter-MSC directed retry handover
A subsequent channel assignment procedure may be requested by MSC-A/3G_MSC-A after an Inter-MSC GSM to UMTS handover or SRNS relocation without circuit connection (see subclauses 13.2 and 13.4). If RNS-A replies with an Iu-RAB-ASSIGNMENT-RESPONSE containing the cause value 'Directed Retry' and the subsequent IuRELOCATION-REQUIRED indicates that a subsequent Inter-MSC directed retry handover is required, the 3G_MSC-B shall not forward the result of the RAB Assignment procedure to MSC-A/3G_MSC-A, but wait for the outcome of the directed retry handover procedure. 3G_MSC-B shall continue with the directed retry handover procedure as described in subclause 14.3.
3GPP
Release 6
98
3GPP TS 23.009 V6.5.0 (2008-12)
BSS-B/UE BSS-A 3G_MSC-A 3G MSC-B Inter-MSC HO Completed MAP- Prep-Handover req. Iu-RABASSIGNMENTREQUEST Iu-RABASSIGNMENTRESPONSE Iu-RELOCATIONREQUIRED UE/RNS-A MSC-B
MAP-Prep-Handover req. A-HO-REQUEST A-HO-REQUEST-ACK MAP-Prep-Handover rsp. IAM. ACM. MAP-Prep-Sub-Handover rsp. Iu-RELOCATIONCOMMAND MAP-Process-Access-Sig req. A-HO-COMPLETE MAP-Send-End-Signal req. ANM. MAP-Send-End-Signal rsp. Iu-RELEASECMD/CMP A-HO-DETECT
Figure 35f: Interaction between a RAB assignment procedure and a subsequent Inter-MSC directed retry handover i): successful directed retry handover If the directed retry handover procedure is unsuccessful and the UE is still served by 3G_MSC-B, the 3G_MSC-B may optionally take one of a number of actions: i) send an Iu-RELOCATION-PREPARATION FAILURE to RNS-A, if an Iu-RELOCATION-COMMAND has not already been sen. Additionally 3G_MSC-B may retry the assignment procedure to RNS-A t; ii) retry the assignment procedure to RNS-A, if the failure message was returned from RNS-A. This option is additional to those for normal handover; iii) construct an A-ASSIGNMENT-FAILURE message containing the cause value 'Radio interface failure, reversion to old channel' or Iu-RAB-ASSIGNMENT-RESPONSE message containing the cause value 'Failure In The Radio Interface Procedure', dependent on the encapsulated protocol used on the E-interface, and forward this message to MSC-A/3G_MSC-A.
3GPP
Release 6
99
3GPP TS 23.009 V6.5.0 (2008-12)
13
13.1
Subsequent channel assignment using a circuit connection between MSC-A and MSC-B
GSM handover
If a circuit connection has to be set up (for example for a Mobile Originated or Mobile Terminated Call Establishment) after an Inter-MSC handover without circuit connection, MSC-A shall request a Handover Number using a MAP-PREPARE-HANDOVER request, containing the A-ASSIGNMENT-REQUEST, on the established MAP connection. For speech calls, MSC-A shall also include the Iu Supported Codecs List to be used by MSC-B for subsequent intra-MSC-B intersystem handover to UMTS and intra-MSC-B SRNS relocation. If MSC-B indicates to MSC-B and to MSC-A that at least one of two procedures assignment or Handover Number allocation can not be completed, then MSC-A shall terminate the circuit establishment attempt. The existing connection to the MS shall be maintained, if possible. Upon receipt of the MAP-PREPARE-HANDOVER request MSC-B shall perform the requested assignment operation towards the BSS. In addition it shall retrieve a Handover Number from VLR-B. If a failure occurs in the assignment or Handover Number allocation then it shall be reflected in the MAP-PREPARE-HANDOVER response that at least one of these two procedures has not been completed (i.e. either by a MAP-PREPARE-HANDOVER result with the assignment procedure outcome and the Handover Number allocation outcome or by a MAP-PREPARE-HANDOVER error). When MSC-A receives a successful MAP-PREPARE-HANDOVER response it shall establish a circuit connection to MSC-B by using the appropriate network supported procedures. In figure 36 this is indicated by the IAM (Initial Address Message) and ACM (Address Complete Message). MSC-B shall also send the Answer message if appropriate to the signalling system. Upon receipt of the Answer MSC-A shall consider the circuit connection establishment phase complete. If a failure occurs during the cirucit establishment phase then the existing connection to the MS shall be maintained, if possible.
BSS-B/MS MSC-A MSC-B MAP-Alloc-Handover-Number req. A-ASG-REQUEST A-ASG-COMPLETE MAP-Prep-Handover resp. IAM MAP-Send-Handover-Report resp. (1) ACM Answer MAP-Send-Handover-Report req. VLR-B
MAP-Prepare-Handover req.
End of call
RELEASE MAP-Send-End-Signal resp.
NOTE:
Can be sent at any time after the reception of IAM.
Figure 36: Successful circuit-switched call establishment after a Basic Handover without circuit connection
3GPP
Release 6
100
3GPP TS 23.009 V6.5.0 (2008-12)
13.2
UMTS to GSM handover
If a circuit connection has to be set up (for example for a Mobile Originated or Mobile Terminated Call Establishment) after an Inter-3G_MSC UMTS to GSM handover without circuit connection, 3G_MSC-A shall request a Handover Number using a MAP-PREPARE-HANDOVER request, containing the A-ASSIGNMENT-REQUEST, on the established MAP connection. For speech calls, 3G_MSC-A shall also include the Iu Supported Codecs List to be used by MSC-B for subsequent intra-MSC-B intersystem handover to UMTS and intra-MSC-B SRNS relocation. If MSC-B indicates to MSC-B and to 3G_MSC-A that at least one of two procedures assignment or Handover Number allocation can not be completed, then 3G_MSC-A shall terminate the circuit establishment attempt. The existing connection to the UE/MS shall be maintained, if possible. Upon receipt of the MAP-PREPARE-HANDOVER request MSC-B shall perform the requested assignment operation towards the BSS. In addition it shall retrieve a Handover Number from VLR-B. If a failure occurs in the assignment or Handover Number allocation then it shall be reflected in the MAP-PREPARE-HANDOVER response that at least one of these two procedures has not been completed (i.e. either by a MAP-PREPARE-HANDOVER result with the assignment procedure outcome and the Handover Number allocation outcome or by a MAP-PREPARE-HANDOVER error). When 3G_MSC-A receives a successful MAP-PREPARE-HANDOVER response, it shall establish a circuit connection to MSC-B by using the appropriate network supported procedures. In figure 37 this is indicated by the IAM (Initial Address Message) and ACM (Address Complete Message). MSC-B shall also send the Answer message if appropriate to the signalling system. Upon receipt of the Answer 3G_MSC-A shall consider the circuit connection establishment phase complete. If a failure occurs during the circuit establishment phase then the existing connection to the UE/MS shall be maintained, if possible.
BSS-B/UE/MS 3G_MSC-A MSC-B MAP-Alloc-Handover-Number req. A-ASG-REQUEST A-ASG-COMPLETE MAP-Prep-Handover resp. IAM MAP-Send-Handover-Report resp. (1) ACM Answer MAP-Send-Handover-Report req. VLR-B
End of call
Figure 37: Successful circuit-switched call establishment after a Basic UMTS to GSM Handover without circuit connection
3GPP
Release 6
101
3GPP TS 23.009 V6.5.0 (2008-12)
13.3
GSM to UMTS handover
If a circuit connection has to be set up (for example for a Mobile Originated or Mobile Terminated Call Establishment) after an Inter-3G_MSC GSM to UMTS handover without circuit connection, MSC-A shall request a Handover Number using a MAP-PREPARE-HANDOVER request, containing the A-ASSIGNMENT-REQUEST, on the established MAP connection. If 3G_MSC-B indicates to 3G_MSC-B and to MSC-A that at least one of two procedures assignment or Handover Number allocation can not be completed, then MSC-A shall terminate the circuit establishment attempt. The existing connection to the UE/MS shall be maintained, if possible. Upon receipt of the MAP-PREPARE-HANDOVER request 3G_MSC-B shall perform the requested assignment operation towards the RNS. In addition it shall retrieve a Handover Number from VLR-B. If a failure occurs in the assignment or Handover Number allocation then it shall be reflected in the MAP-PREPARE-HANDOVER response that at least one of these two procedures has not been completed (i.e. either by a MAP-PREPARE-HANDOVER result with the assignment procedure outcome and the Handover Number allocation outcome or by a MAP-PREPAREHANDOVER error). For speech calls, 3G_MSC-B shall select a codec from the Iu Supported Codecs List, generate associated RAB parameters and connect a transcoder. If the Iu Supported Codecs List was not received, 3G_MSC-B shall select the appropriate default speech codec. For an assignment in UTRAN Iu mode, 3G_MSC-B shall also generate a NAS Synch Indicator for the Iu-RABASSIGNMENT-REQUEST message. If the Iu Supported Codecs List was received by 3G_MSC-B, then the Iu Selected codec shall be indicated in the MAP-PREPARE-HANDOVER response, sent from 3G_MSC-B to MSC-A. When MSC-A receives a successful MAP-PREPARE-HANDOVER response, it shall establish a circuit connection to 3G_MSC-B by using the appropriate network supported procedures. In figure 38 this is indicated by the IAM (Initial Address Message) and ACM (Address Complete Message). 3G_MSC-B shall also send the Answer message if appropriate to the signalling system. Upon receipt of the Answer MSC-A shall consider the circuit connection establishment phase complete. If a failure occurs during the circuit establishment phase then the existing connection to the UE/MS shall be maintained, if possible.
RNS-B/UE/MS MSC-A 3G_MSC-B MAP-Alloc-Handover-Number req. IU-RAB-ASG-REQUEST IU-RAB-ASG-COMPLETE MAP-Prep-Handover resp. IAM MAP-Send-Handover-Report resp. (1) ACM Answer MAP-Send-Handover-Report req. VLR-B
End of call
Figure 38: Successful circuit-switched call establishment after a Basic GSM to UMTS Handover without circuit connection
3GPP
Release 6
102
3GPP TS 23.009 V6.5.0 (2008-12)
13.4
13.4.1
SRNS Relocation
Without circuit connection
If a circuit connection has to be set up (for example for a Mobile Originated or Mobile Terminated Call Establishment) after an Inter-3G_MSC relocation without circuit connection, 3G_MSC-A shall request a Handover Number using a MAP-PREPARE-HANDOVER request, containing the IU-RAB-ASSIGNMENT-REQUEST, on the established MAP connection. For speech calls, 3G_MSC-A shall include the Iu Supported Codecs List in the MAP-PREPARE-HANDOVER request. 3G_MSC-A shall configure the RANAP RAB parameters according to the appropriate default speech codec. Alternatively, if 3G_MSC-B is known to support the use of the Iu Supported Codecs List, 3G_MSC-A may configure the RANAP RAB parameters according to the preferred codec and indicate this to 3G_MSC-B by including the RAB configuration indicator in the MAP-PREPARE-HANDOVER request. The decision to use this option is based on internal configuration information in 3G_MSC-A. For an assignment in UTRAN Iu mode, 3G_MSC-A shall also include the NAS Synch Indicator in the Iu-RABASSIGNMENT-REQUEST. If 3G_MSC-B indicates to 3G_MSC-B and to 3G_MSC-A that at least one of two procedures (RAB) assignment or Handover Number allocation can not be completed, then 3G_MSC-A shall terminate the circuit establishment attempt. The existing connection to the UE shall be maintained, if possible. Upon receipt of the MAP-PREPARE-HANDOVER request, 3G_MSC-B shall perform the requested RAB assignment operation towards the RNS. In addition it shall retrieve a Handover Number from VLR-B. For speech calls, 3G_MSC-B shall select an Iu Selected codec from the Iu Supported Codecs List and connect a transcoder. If the Iu Supported Codecs List was not received, 3G_MSC-B shall select the appropriate default speech codec. 3G_MSC-B shall reconfigure the RANAP RAB parameters according to the Iu Selected codec: if the RAB configuration indicator is included in the MAP-PREPARE-HANDOVER request and the codec selected by 3G_MSC-B is different from the preferred codec; or if the RAB configuration indicator is not included in the MAP-PREPARE-HANDOVER request and the codec selected by 3G_MSC-B is different from the appropriate default speech codec.
Additionally, for an assignment in UTRAN Iu mode, 3G_MSC-B shall include the NAS Synch Indicator for the Iu Selected codec in the Iu-RAB-ASSIGNMENT-REQUEST. If the Iu Supported Codecs List was received by 3G_MSCB, then the Iu Selected codec shall be indicated in the MAP-PREPARE-HANDOVER response, sent from 3G_MSC-B to 3G_MSC-A. If a failure occurs in the RAB assignment or Handover Number allocation then it shall be reflected in the MAPPREPARE-HANDOVER response that at least one of these two procedures has not been completed (i.e. either by a MAP-PREPARE-HANDOVER result with the RAB assignment procedure outcome and the Handover Number allocation outcome or by a MAP-PREPARE-HANDOVER error). When 3G_MSC-A receives a successful MAP-PREPARE-HANDOVER response, it shall establish a circuit connection to 3G_MSC-B by using the appropriate network supported procedures. In figure 39 this is indicated by the IAM (Initial Address Message) and ACM (Address Complete Message). 3G_MSC-B shall also send the Answer message if appropriate to the signalling system. Upon receipt of the Answer 3G_MSC-A shall consider the circuit connection establishment phase complete. If a failure occurs during the circuit establishment phase then the existing connection to the UE shall be maintained, if possible.
13.4.2
With circuit connection (Optional functionality)
If 3G_MSC-A and 3G_MSC-B support the optional supplementary service Multicall (See 3GPP TS 23.135), 3G_MSCA and 3G_MSC-B shall have the following functionality additionally to the description in clause 13.4.1. A new circuit connection shall be able to set up (for example for a new Mobile Originated or a new Mobile Terminated Call Establishment) after an Inter-3G_MSC relocation with one or several circuit connections. The procedures for the
3GPP
Release 6
103
3GPP TS 23.009 V6.5.0 (2008-12)
establishment of the additional circuit connection in 3G_MSC-A and 3G_MSC-B are the same as that described in clause 13.4.1.
RNS-B/UE 3G_MSC-A 3G_MSC-B MAP-Alloc-Handover-Number req. IU-RAB-ASG-REQUEST IU-RAB-ASG-COMPLETE MAP-Prep-Handover resp. IAM MAP-Send-Handover-Report resp. (1) ACM Answer MAP-Send-Handover-Report req. VLR-B
End of call
Figure 39: Successful circuit-switched call establishment after a Basic Relocation without circuit connection
14
14.1
Directed retry handover

[Directed retry in the cases of SRNS relocation is FFS]
Editor's Note:
GSM handover
The directed retry procedure allows the network to select the optimum cell for the Mobile Station. The process of directed retry involves the assignment of a Mobile Station to a radio channel on a cell other than the serving cell. This process is triggered by the assignment procedures, as described in 3GPP TS 08.08 [5], and employs internal or external handover procedures as described in clauses 6 and 7. The successful procedure for a directed retry is as shown in figure 40 and as described below. If during the assignment phase, as represented by the A-ASSIGNMENT-REQUEST message, a handover becomes necessary, due to either radio conditions or congestion, then the Mobile Station may be handed over to a different cell. When the decision has been made to handover the MS the BSS-A may send an A-ASSIGNMENT-FAILURE message, indicating 'directed retry', before sending the A-HANDOVER-REQUIRED message to MSC-A, indicating 'directed retry'. However BSS-A may alternatively send the A-HANDOVER-REQUIRED message, indicating 'directed retry', without sending the A-ASSIGNMENT-FAILURE message. Other cause values may be used instead of "Directed Retry" in the A-HANDOVER-REQUIRED message, this will allow the MSC to take different actions dependent on the received cause. Upon receipt of the A-HANDOVER-REQUIRED message from BSS-A, then MSC-A shall initiate the handover as described in clauses 6 and 7. No resources shall be cleared in the MSC-A or BSS-A for this connection. After receipt of the A-HANDOVER-COMPLETE message from BSS-B the assignment procedure shall be considered to be complete and the resources on BSS-A shall be cleared.
3GPP
Release 6
104
3GPP TS 23.009 V6.5.0 (2008-12)
MS
BSS-A A-Assignment-Request A-Assignment-Failure A-Handover-Required A-Handover-Request A-Handover-Request-Ack A-Handover-Command RI-HO-Command A-Handover-Detect RI-HO-Complete A-Handover-Complete A-Clear-Command A-Clear-Complete RI-HO-Access MSC-A BSS-B
MS
Figure 40: Example of a Directed Retry Intra-MSC Handover Procedure If a failure occurs during the handover attempt, for example A-HANDOVER-FAILURE returned from BSS-A or BSSB, then MSC-A will terminate the handover to BSS-B. Under these conditions MSC-A may optionally take one of a number of actions: i) retry the handover to the same cell; ii) select the next cell from the list contained in the A-HANDOVER-REQUIRED message and attempt a handover to the new cell; iii) send an A-HANDOVER-REQUIRED-REJECT to BSS-A, if an A-HANDOVER-COMMAND has not already been sent. Additionally MSC-A may retry the assignment procedure to BSS-A; iv) retry the assignment procedure to BSS-A, if the failure message was returned from BSS-A. This option is additional to those for normal handover; v) Clear the complete call. The procedures for Inter-MSC handover are also applicable to the directed retry process. If an Inter-MSC handover is necessary then the assignment process should be considered to have completed successfully upon receipt of the A-HOCOMPLETE included in the MAP-SEND-END-SIGNAL request.
14.2
GSM to UMTS handover
The directed retry procedure allows the network to select the optimum cell for the UE/MS. The process of directed retry involves the assignment of a UE/MS to a radio channel on a cell other than the serving cell. This process is triggered by the assignment procedures, as described in 3GPP TS 08.08 [5], and employs internal or external GSM to UMTS handover procedures as described in clauses 6.2.2 and 8.2. The successful procedure for a directed retry in case of an intra-3G_MSC GSM to UMTS handover is as shown in figure 40a and as described below.
3GPP
Release 6
105
3GPP TS 23.009 V6.5.0 (2008-12)
If during the assignment phase, as represented by the A-ASSIGNMENT-REQUEST message, a GSM to UMTS handover becomes necessary, due to radio conditions, congestion or inability to provide the requested bearer service in GSM, then the UE/MS may be handed over to a UMTS cell. If the requested bearer service cannot be provided in GSM, 3G_MSC-A shall indicate in the A-ASSIGNMENT-REQUEST message that handover to UMTS should be performed. When the decision has been made to handover the UE/MS the BSS-A may send an A-ASSIGNMENT-FAILURE message, indicating 'directed retry', before sending the A-HANDOVER-REQUIRED message to 3G_MSC-A, indicating 'directed retry'. However BSS-A may alternatively send the A-HANDOVER-REQUIRED message, indicating 'directed retry', without sending the A-ASSIGNMENT-FAILURE message. Other cause values may be used instead of "Directed Retry" in the A-HANDOVER-REQUIRED message, this will allow the 3G_MSC to take different actions dependent on the received cause. Upon receipt of the A-HANDOVER-REQUIRED message from BSS-A, then 3G_MSC-A shall initiate the GSM to UMTS handover as described in clauses 6.2.2 and 8.2. No resources shall be cleared in the 3G_MSC-A or BSS-A for this connection. After receipt of the Iu-RELOCATION-COMPLETE message from RNS-B the assignment procedure shall be considered to be complete and the resources on BSS-A shall be cleared.
UE/MS
BSS-A A-Assignment-Request A-Assignment-Failure A-Handover-Required Iu-Relocation-Request Iu-Relocation-Request-Ack A-Handover-Command RI-HO-Command Iu-Relocation-Detect 3G_MSC-A RNS-B
UE/MS
RRC-HO-Complete Iu-Relocation-Complete A-Clear-Command A-Clear-Complete
Figure 40a: Example of a Directed Retry Intra-3G_MSC GSM to UMTS Handover Procedure If a failure occurs during the handover attempt, for example A-HANDOVER-FAILURE returned from BSS-A or IuRELOCATION FAILURE from RNS-B then 3G_MSC-A will terminate the GSM to UMTS handover to RNS-B. Under these conditions 3G_MSC-A may optionally take one of a number of actions: i) send an A-HANDOVER-REQUIRED-REJECT to BSS-A, if an A-HANDOVER-COMMAND has not already been sent. Additionally 3G_MSC-A may retry the assignment procedure to BSS-A; ii) retry the assignment procedure to BSS-A, if the failure message was returned from BSS-A. This option is additional to those for normal handover; iii) Clear the complete call. The procedures for Inter-3G_MSC GSM to UMTS handover are also applicable to the directed retry process. If an Inter-3G_MSC GSM to UMTS handover is necessary then the assignment process should be considered to have completed successfully upon receipt of the A-HO-COMPLETE included in the MAP-SEND-END-SIGNAL request.
3GPP
Release 6
106
3GPP TS 23.009 V6.5.0 (2008-12)
14.3
UMTS to GSM handover
The directed retry procedure allows the network to select the optimum cell for the UE/MS. The process of directed retry involves the assignment of a UE/MS to a radio channel on a cell other than the serving cell. This process is triggered by the assignment procedures, as described in 3GPP TS 25.413 [1], and employs UMTS to GSM handover procedures as described in clauses 6.2.1 and 8.1. The successful procedure for a directed retry in case of an intra-3G_MSC UMTS to GSM handover is as shown in figure 40b and as described below. If during the assignment phase, as represented by the Iu-RAB-ASSIGNMENT-REQUEST message, a UMTS to GSM handover becomes necessary, due to either radio conditions. congestion or network preference, then the UE/MS may be handed over to a GSM cell. If the handover to GSM is required due to network preference, 3G_MSC-A shall indicate in the Iu-RAB-ASSIGNMENT-REQUEST message that handover to GSM should be performed. When the decision has been made to handover the UE/MS the RNS-A shall send an Iu-RAB-ASSIGNMENT-RESPONSE message, indicating 'directed retry', before sending the Iu-RELOCATION-REQUIRED message to 3G_MSC-A, indicating 'directed retry'. Other cause values may be used instead of "Directed Retry" in the Iu-RELOCATION-REQUIRED message, this will allow the 3G_MSC to take different actions dependent on the received cause. Upon receipt of the Iu-RELOCATIONREQUIRED message from RNS-A, then 3G_MSC-A shall initiate the UMTS to GSM handover as described in clauses 6.2.1 and 8.1. No resources shall be cleared in the 3G_MSC-A or RNS-A for this connection. After receipt of the A-HANDOVER-COMPLETE message from BSS-B the assignment procedure shall be considered to be complete and the resources on RNS-A shall be cleared.
UE/MS RNS-A 3G_MSC-A BSS-B

Iu- RAB-Assignment-Request Iu- RAB-Assignment-Response Iu-Relocation-Required A-Handover-Request A-Handover-Request-Ack Iu-Relocation-Command RRC-HO-Command A-Handover-Detect RI-HO-Complete A-Handover-Complete Iu-Release-Command Iu-Release-Complete RI-HO-Access
UE/MS
Figure 40b: Example of a Directed Retry Intra-3G_MSC UMTS to GSM Handover Procedure If a failure occurs during the handover attempt, for example Iu-RELOCATION FAILURE returned from RNS-A or AHANDOVER-FAILURE from BSS-B then 3G_MSC-A will terminate the UMTS to GSM handover to BSS-B. Under these conditions 3G_MSC-A may optionally take one of a number of actions: i) send an Iu-RELOCATION-PREPARATION FAILURE to RNS-A, if an Iu-RELOCATION-COMMAND has not already been sent. Additionally 3G_MSC-A may retry the assignment procedure to RNS-A; ii) retry the assignment procedure to RNS-A, if the failure message was returned from RNS-A. This option is additional to those for normal handover; iii) Clear the complete call. The procedures for Inter-3G_MSC UMTS to GSM handover are also applicable to the directed retry process. If an Inter-3G_MSC UMTS to GSM handover is necessary then the assignment process should be considered to have completed successfully upon receipt of the A-HO-COMPLETE included in the MAP-SEND-END-SIGNAL request.
3GPP
Release 6
107
3GPP TS 23.009 V6.5.0 (2008-12)
15
SDL diagrams
NOTE 1: The message primitive names used in the SDL diagrams and message flows in the present document do not represent the actual messages specified in the GSM or 3GPP stage 3 technical specifications. The primitive names are only intended to be indicative of their use in the present document. SDL Annotation. The following conventions and abbreviations have been used in the SDLs. Text included in '[]' is used to indicate either, the BSSMAP message (as defined in 3GPP TS 49.008 [7]) included in the message, or the transport of a Handover Number. When traversing the following SDLs it may be possible that resources appear to be released repeatedly, however these operations are only executed once on their first occurrence. Furthermore it maybe that certain messages cannot, in practice, be received in particular states, after specific events have taken place. In general both of the above cases are obvious. This approach has been adopted (in line with other GSM Technical Specifications) in order to reduce the complexity of the SDLs and improve clarity, without reducing the quality of the functional description. The following abbreviations have been used in the SDLs: A-HO-REQUEST A-HO-REQUEST-ACK A-HO-COMPLETE A-HO-DETECT A-HO-PERFORMED A-ASG-REQUEST A-ASG-COMPLETE A-ASG-FAILURE MAP-PAS req MAP-FAS req IU-RLC-REQUEST IU-RLC-REQUEST-ACK IU-RLC-COMPLETE IU-RLC-DETECT IU-IREL-REQUEST IU-RREL-REQUEST IU-RASG-REQUEST IU-RASG-RESPONSE A-HANDOVER-REQUEST A-HANDOVER-REQUEST-ACK. A-HANDOVER-COMPLETE A-HANDOVER-DETECT A-HANDOVER-PERFORMED A-ASSIGNMENT-REQUEST A-ASSIGNMENT-COMPLETE A-ASSIGNMENT-FAILURE MAP-PROCESS-ACCESS-SIGNALLING req. MAP-FORWARD-ACCESS-SIGNALLING req. IU-RELOCATION-REQUEST IU-RELOCATION-REQUEST-ACK IU-RELOCATION-COMPLETE IU-RELOCATION-DETECT IU-IU-RELEASE-REQUEST IU-RAB-RELEASE-REQUEST IU-RAB-ASSIGNMENT-REQUEST IU-RAB-ASSIGNMENT-RESPONSE
NOTE 2: The SDL diagrams have been checked for consistency with the allocation of the A interface circuits by the BSC. The conclusion was that SDLs are expressed in general terms, and offer a sufficient latitude of interpretation to be consistent with the allocation of A interface circuits by the BSC.
3GPP
Release 6
108
3GPP TS 23.009 V6.5.0 (2008-12)
Pro ce d ure M S C _A_ H O

Pro c ed ur e for H and o ve r in M SC -A
S hee t1 (26)
IDLE
C all in P rog re s s o n MSC -A
A-H A N DO VE R- R EQ UIR ED fro m BS S-A
Fr om M S o r N etwor k Im pl icit R e leas e of BS S- A
C all Re lea se
K no wn M SC? No
Yes
No
H an do ver allow ed to C ell? Yes
W hic h MSC?
M S C -B
M SC- A
Kno w n BSS ? No Yes
Ye s 3
S elect N ew Ce ll? No No
R eso ur ces on BSS - B? Yes
No S en d R ejec t? Ye s
A-H A N D OVE R R EJ EC T to B SS- A
C all in P rog re s s o n MSC -A
ID LE
Figure 41 (Sheet 1 of 26): Handover control procedure in MSC-A
3GPP
Release 6
109
3GPP TS 23.009 V6.5.0 (2008-12)

H and ove r on M S C - A from B SS -A to BSS - B. Pro c ed ur e for H and o ve r in M SC -A
S hee t2 (26)
A-H A N DO VE R -R EQU EST to BS S- B
Set T10 1
W ait for C ha n ne l A llo catio n Intra- MS C
A-H A N D OVE R R EQU E ST- A CK fro m BS S-B
A- H AN D OVE R F A IL U R E fr o m BS S- B
Fr om M S o r Ne two rk
Ca ll Re le as e
R e set T1 01
E xpiry T 1 01
R ese t T 10 1
A- CLE AR -R E QU EST fr o m B SS- A
Qu eu e M es sag es for M S in M S C -A
C a ll R e le ase
to Netw o rk
H an dov er C o m ma n d nc el Cha nn el Ca to M S vi a B SS-A in B SS-B
Se t U p H a nd ov e r D e vice
In terna l m e ss a ge in M SC -A
Retr y Han do ver A tte m pt? Y es
No
R el ea se Res ou rces in BSS -A
Set T10 2
N ew C ell Cell? Sa m e C el l
Can c el C han ne l in BSS -B
W ait for a cc es s by MS o n BSS
IDL E
3GPP
Release 6
110
3GPP TS 23.009 V6.5.0 (2008-12)
Procedure MSC_A_H O
Proc edur e for Hando ve r in MSC-A
Sheet3 (26)
Wait for access by MS on B SS
A-HANDOVERCOMPLETE from BS S-B
A-HANDOVERDETECT from BSS-B
Connect the Handover Device (O ption)
O nly if not already c on nec ted
Connect the Handover Device (Option)
Reset T102
Relea se Resources in BSS-A
Forward queued mes sages for MS via BSS-B
Call in Progress on MSC-A
W ait for acc es s by MS on BSS
3GPP
Release 6
111
3GPP TS 23.009 V6.5.0 (2008-12)
Procedure MSC_A_HO
Procedure for Handover in MSC-A
Sheet4(26)
Wait for access by MS on BSS
A-HANDOVERFAILURE from BSS-A
A-CLEARREQUEST from BSS-A
(Allowed once in this state)
Expiry T102
Call Release
From Network
Reset T102
(Allowed once A-CLEARREQUEST in this state) from BSS-B
Release Resources Release Resources in BSS-A in BSS-A
Forward queued messages for MS via BSS-A
Release Resources in BSS-B
Yes Wait for MS on BSS-B? No
Release Handover Device
Reset T102
Call Release
to Network
Call in Progress on MSC-A
IDLE
3GPP
Release 6
112
3GPP TS 23.009 V6.5.0 (2008-12)

Pro c ed ur e for H and o ve r in M SC -A Ba sic H a nd ove r to MSC -B Circ uit Co nn ecti on r eq ui re d
S hee t5 (26)
M AP-P REPA R EHA ND OVER req . [A-H O- REQ UEST ] to MS C- B
W ait For A ck now led g em en t fr om M S C -B
M AP-P R EPA R EH AN D OVER resp . [A- H O- REQU EST -AC K] fro m M SC- B
M AP - PR EP ARE H AN D OVER r esp . [A - HO- FA ILU R E] fr o m MSC -B
M AP -P RE PAR E HA ND OVE R re s p. [M A P ERR OR ] fr om M SC -B
Han do ver Num b er? R e qu este d
N ot R eq u est ed
R etry H an do ver A tte m pt? Y es
No
I_C ON N ECT (IAM ) to M SC - B us ing Ha nd ove r N um be r
C ell? Sam e C e ll New C el l
W ait for C o nne c tio n fr om M S C -B
3GPP
Release 6
113
3GPP TS 23.009 V6.5.0 (2008-12)
Procedure MSC_A_H O
Sheet6 (26)
Wait For Ack nowledgement from MSC-B
ERRO R
from MSC-B
A-CLEAR-R EQUEST from BSS-A
Call Re lease
From MS or Network
Canc el MAP Re sources
in MSC-A
to Network
Call Release
Retry Handover Attempt? Yes
Release Resource s in BSS-A No
Same Cell Cell? New Cell
Cancel MAP Resources
to MS C-B
IDLE
3GPP
Release 6
114
3GPP TS 23.009 V6.5.0 (2008-12)
Procedure MSC_A_H O
Sheet7 (26)
W ait for Connection from MSC-B
I_COMPLETE (AC M) from MSC-B
(A llowed onc e in this state )
From MS or Netwo rk
Call Releas e
MAP-PA S req. [A-CLEAR-REQUEST ] from MSC-B
Call Release
to MS and Network
Queue M es sages for MS in MSC-A
Wait for Connection from MSC-B
ERROR
from MSC-B or Network
Rel ease Res ources in BSS-A
Han dov er Command to MS vi a B SS-A
I_DISCONNECT (REL) to MS C-B
Set T103
No Retry Handover A ttempt? Yes
to MSC-B in MSC-A
Cancel MAP Procedures
Set Up the Handov er Device
Internal message in MSC-A
Same Cell Cell? New Cel l
I_DISCONNECT (RE L) to MSC-B
W ait for Completion on MS C-B
IDLE
3GPP
Release 6
115
3GPP TS 23.009 V6.5.0 (2008-12)
Procedure MSC_A_H O
Sheet8 (26)
W ait for Completion on MS C-B
MAP-S ENDEND-SIG NA L req. [A-HO-CO MP LE TE] from MSC-B
I-ANSW ER (ANM) from MSC-B
MAP-PAS req. [A-HO-DE TECT] from MSC -B
Reset T103
MA P-PAS re q. [A-CLEAR-REQUEST] from BSS-B
(Allowed once in thi s state)
A-CLEA R-REQ UEST from BS S-A
Rel eas e Resourc es on BSS-A
Co nnect Handov er Device (option)
Yes W ait for MS on MSC-B? No Wai t for Comple tion on MSC-B
Cal l Release
to Network and MS
Forward queu ed messages via MS C-B
Us e M AP FORWA RD- ACCESSSIGNAL LING req
Release MAP Resources
to MSC-B in MS C-A
Co nnect Handov er Devi ce (option)
Release Resources on BSS-A
I_DISCO NN ECT (REL) to MS C-B
Call on MSC-B
IDLE
W ait for Co mpl etion on MS C-B
3GPP
Release 6
116
3GPP TS 23.009 V6.5.0 (2008-12)
Procedure MSC_A_H O
Sheet9 (26)
Wai t for Comple tion on MSC-B
A -HANDOV ERFAILURE f rom B SS-A
I_DISCONNECT (RE L) from MSC-B
Expiry T1 03
Call Re lease
from Network
Res et T103
In MSC-A and to MSC-B
Re lease Handov er Device
In ter nal to MSC-A
Forward q ueued messages for MS via BSS-A
Internal to MSC-A
W ait for Co mpl etion on MS C-B
Releas e Handove r Device
I_DISCON NE CT (REL) to MSC-B
in MSC-A to MSC-B
from MSC-B
Canc el MAP Proc edures
Canc el MAP Procedures
In MSC-A and to MS C-B
Release Handover Devic e
In ter nal to MSC-A
I_DISCONNE CT (REL) to MSC-B
Release Resources BSS-A
Call in P rogress on MSC-A
Wait for Completion on MSC-B
W ait for Completion on MSC-B
IDLE
3GPP
Release 6
117
3GPP TS 23.009 V6.5.0 (2008-12)
Procedure MSC_A_H O
Sheet10(26)
Call on MS C-B
MAP-PREPARESUB SEQUENTHAND OVER req. [A-HO-REQU EST] from MSC-B Known MSC? Yes No Call on MSC-B
MAP-P AS req. [A-CLEARREQUEST] from MSC-B
From MS or Netwo rk
Call Releas e
MAP-SEND- ENDSIGNA L resp. to MSC-B
Hand over all owed to Cell? Yes
No
Cancel MAP procedures
from MSC -B
MSC-B'
Which MSC?
Call Release
to Network and MS
MSC-A
Known BSS? Yes
No
Res ourc es on new BSS? Yes
No
A -HANDOV ERREQ UEST to BSS-B
MAP-PREPA RESUBSEQUENTHANDOVER resp. [A-HO-FAILURE] to MS C-B Set T101 No Circuit Connection? Yes
MAP-PRE PA RESU BSEQUENTHANDOVER resp. [MAP ERROR] to MSC-B
Wait for Channel Allocation
MS on MSC-B
Call on MSC-B
IDLE
3GPP
Release 6
118
3GPP TS 23.009 V6.5.0 (2008-12)
Procedure MSC_A_H O
Sheet11(26)
Wait for Channel Alloc ation
A -HANDOV ERREQUEST-ACK. f rom B SS-B
A-HANDOVERFA ILU RE fro m BSS-B
Expiry T1 01
Cal l Rel eas e
From MS or Network
Res et T101
Reset T 101
Ca nce l Ch annel B SS-B
Queue Mess ages for MS in MSC-A
( All owed once i n this state)
MAP-PAS req. [A -CLEAR-REQ UE ST ] from MS C-B
MAP-SEND-ENDSIGNAL resp to MSC -B
M AP -PREPARES UBS EQUE NTHANDOVER resp [ A- HO-REQUEST-ACK] t o MSC-B No Ci rcui t Connection? Yes
Releas e Reso urces in B SS-B
Call on MSC-B
Se t Up Handover Device
No
R etry Same C ell? Yes
Set T104
MAP-P REPARESUBSEQUEN THA NDOVER res p. [A-HO-FAILURE] to MS C-B Call on MSC-B
Wai t for Access by MS
IDLE
3GPP
Release 6
119
3GPP TS 23.009 V6.5.0 (2008-12)
Procedure MSC_A_H O
Sheet12(26)
Wai t for access by MS
A-HANDOVERCOMPLETE from BSS-B
A-H ANDOVERDETE CT from BS S-B
Expiry T104
Res et T104
No
Circuit Connection? Yes
Call Release
to Network
Connect Handover Dev ice (option)
Connect Handover D evic e (option)
Release Resource s on BSS-B
Forward q ueued messages for MS via BSS-B
in MSC-A to MS C-B
MA P-SEND- ENDSIGNA L resp. to MSC-B
I_DISCONNECT (REL) to MSC-B
No
Circui t Conn ection? Yes
Releas e Handover Dev ice
I_DISC ONNECT (REL) to MSC-B
W ait for ac cess by MS
IDLE
3GPP
Release 6
120
3GPP TS 23.009 V6.5.0 (2008-12)
Procedure MSC_A_H O
Sheet13(26)
W ait for acces s by MS
MAP-PAS req. [A-HOFAILU RE] from MSC-B
MA P-PAS re q. [A -CLEARREQU EST] from MSC-B
from Network
Call Releas e
A-CLEARREQ UEST from BSS-B
Us e MAP -FORW ARDACCESS-SIGNALLING r eq.
Release Resources on BSS-B
Circu it Connection? Yes
No
Re lease Ha ndov er Dev ice
Call on MSC-B
MS on MS C-B
Wait fo r access by MS
3GPP
Release 6
121
3GPP TS 23.009 V6.5.0 (2008-12)
Procedure MSC_A_H O
Proc edur e for Hando ve r in MSC-A Subsequent Handover f rom MSC-B to MSC-B' Circuit Connecti on requir ed
Sheet14(26)
MA P-PREPARE-H ANDOV ER req [A-HO-REQU EST] to MSC-B '
Wai t for Ack from MSC-B '
MAP-PREPAREHAND OVER resp.. [A-HO-REQU EST-ACK] from MSC-B'
MAP-P REPAREHA NDOVER resp. [A-HO-FAILURE] from MSC -B'
Hand over Number?
Not Reques ted
Requested
Retry Same Cell? No
Yes
I_CONNECT (IAM) to MSC-B' u sing Handover Number
MAP -PREPARESUB SEQUENTHANDOVER resp. [A-HO-FAILURE] to MSC -B Call on MSC-B
Wai t for Connection from MSC-B'
3GPP
Release 6
122
3GPP TS 23.009 V6.5.0 (2008-12)
Procedure MSC_A_H O
Sheet15(26)
Wai t for Ack from MSC-B '
ERROR
from MSC-B'
from MS C- B o r Network
ERRO R
Call Re lease
From MS or Network
Releas e MA P Reso urces
to MSC-B '
to MSC-B'
MAP-PAS req. [A-CLEAR-REQUEST] from MSC-B
MAP-S EN DEND-SIGNA L resp. to MS C-B
Retry Same Cell? No
Cancel MAP Procedures Yes
to MSC-B'
MAP-PREPARE S UBS EQ UE NTHANDOVE R resp. to MSC-B
ERROR
Call on MS C-B
W ait for Ack from MSC-B'
IDLE
3GPP
Release 6
123
3GPP TS 23.009 V6.5.0 (2008-12)
Procedure MSC_A_H O
Sheet16(26)
W ait for Connection from MSC-B'
I_ COMPLETE from MSC-B' (ACM) from MSC-B' or Network
ERROR
from MS or Netwo rk
Call Releas e
Set up Handov er Device
MAP-PAS req. [A -CLEARREQ UEST] from MSC-B'
MAP-PA S req. [A-CLEARREQ UE ST] from MSC -B
Wait for Connection from MSC-B'
MAP-P REPARESUBSEQUENTHA ND OVER res p. [A-HO-RE QUES T-A CK] to MS C-B Cancel MAP Procedures Cancel MAP Proc edures
to MSC-B'
Cancel MAP Proced ures
to MSC-B'
to MSC-B and MSC -B'
Queue m es sages for MS in MSC-A
I_ DISCONNECT (RE L) to MSC-B'
MAP -SENDE ND-SI GNAL res p t o MSC-B
Retr y to MSC-B' Yes No
Call Release
to Network and MS
Set T103
ERROR
M AP -PREPARES UBS EQ UE NTHAN DO VER resp. to MSC-B
I_DISCONNECT (REL) to MSC-B and MSC-B'
W ait for Completion on MSC-B'
Call on MSC-B
IDLE
3GPP
Release 6
124
3GPP TS 23.009 V6.5.0 (2008-12)
Procedure MSC_A_H O
Sheet17(26)
W ait for Completion on MSC-B'
MAP-S ENDEND-SIG NA L req. [A-HO-CO MP LE TE] from MSC-B'
MAP-P AS req. [A-HO -DETECT] from MSC-B '
MAP-PA S req. [A-CLEARREQ UE ST] from MSC -B
(Al lowed once in thi s state)
Reset T103
I_ANSWER (ANM) from MSC-B '
MAP-P AS req. [A-CLEARREQUEST] from MSC-B '
(Allowed o nc e in this state)
Connect Handover Device (option)
Wait fo r access by MS? No
Forward queu ed messages f or MS via MSC-B'
Rel ease Hand over Dev ice
MAP-S ENDEND-SIG NA L resp. to MS C-B
to MSC-B and MSC -B'
I_DISC ONNE CT (REL) to MSC-B
to Network and MS
Cal l Rel ease
Redefine MSC-B' as MSC-B
I_DISCONNECT (REL) to MSC-B and MSC-B'
Call on MSC-B
W ait for Completion from MSC-B'
IDLE
3GPP
Release 6
125
3GPP TS 23.009 V6.5.0 (2008-12)

Pro c ed ur e for H and o ve r in M SC -A
S hee t1 8 ( 26)
W ait for C o mp letio n o n MSC - B'
E xp ir y T10 3
MA P- P AS re q. [A-H O- FA ILU RE] fro m M SC- B
fr om MS C - B'
C an c e l M A P Pr oc ed ur es
Fr o m Ne tw o rk or MS C -B
C all Rele as e
Res et T10 3
from M S C- B
C a nce l M A P Pr o ced ures
I_DISC ON N EC T (R EL ) to M S C -B '
Ca nc el M AP Pr oc ed ur es
to MSC - B '
I_D ISC ONN E C T ( R E L) to M SC- B
R elea se H an do ver D e vic e
R e le ase Ha ndov er D ev ice
R el ea s e H an do ver D evic e
I_ DISC ON NEC T (R EL ) to M S C -B'
Yes W a it fo r a cce s s by MS? No
M SC- B C o nn ec tio n? No
Ye s
C an cel M AP Pr o ce d ure s
to M S C- B'
U se M AP FOR W A RD A C CE SS S IGN AL L IN G r e q .
Forw ar d q u eu ed m es sa ge s fo r M S via M S C -B
I_D ISC ON N ECT ( R EL ) to MS C - B'
C a ll Re le ase
to Ne two rk
ID LE
Call on MS C -B
ID L E
W ai t for Co m ple tio n on MSC -B '
3GPP
Release 6
126
3GPP TS 23.009 V6.5.0 (2008-12)

Pro c ed ur e for H and o ve r in M SC -A Ba sic H a nd ove r to M SC -B no C i rcui t C o n ne ction r equ ir ed
S hee t1 9 ( 26)
Qu eu e M es sag es for M S in M S C -A
H an dov er C o m ma n d to M S vi a B SS-A
Set T10 3
W ait for MS o n MS C- B
M AP-S EN D END - S IG NA L r eq . [A-H O- CO MP LE TE ] fr om M SC -B
( Allo w e d o n ce in thi s state )
A- CL EA R- REQ UE ST fr om BS S- A
M AP-PAS r eq. [A -H O- DE TECT ] fr om M SC -B
R e set T1 03
M AP -PA S r e q. [A - CL EAR - REQU ES T ] fro m B SS- B
( Allo we d o n ce in thi s state )
R el ea s e R eso urc es on BS S- A
R e le ase R eso urce s o n B SS-A
Ye s
W a it fo r M S on M SC - B? No
For war d q ue u ed m e ssa ge s f or MS via MS C- B
Us e M AP FOR W A RD - AC C E SSSIGN A LL IN G r eq.
C al l R elea se
to N etw ork an d MS
R elea se M A P R eso urc e s
to M S C- B in MS C- A
MS on M SC- B
W a it fo r MS o n M SC -B
ID L E
W a it for MS o n MS C- B
3GPP
Release 6
127
3GPP TS 23.009 V6.5.0 (2008-12)
Procedure MSC_A_H O
Sheet20(26)
Wai t for MS on MSC-B
from MS C- B
Expi ry T103
Call Re lease
from Netw ork
Res et T103
In MSC-A and to MSC-B
Cancel MAP Proc edures
Forward q ueued messages for MS via BSS-A
Relea se Resources BSS-A
Release Resourc es BS S-A
in MSC-A to MSC-B
Wait for MS on MSC-B
IDLE
W ait for MS on MS C- B
3GPP
Release 6
128
3GPP TS 23.009 V6.5.0 (2008-12)
P rocedure MSC_A_H O
P rocedure fo r Handover in MSC-A MS Established on MSC-B without a Circ ui t Connection
S heet21(26)
MS on MS C-B
Request fo r Circuit Establishment
From MSC-B
From MS or Network
Call Release
MAP -PREPARE- Call S UBS EQUE NTRelease HANDO VE R req. [A-HO-REQUEST] from MS C-B MAP-P REPAREHA NDOVER req. [NULL] [A-AS G-REQUEST] to MS C-B
to Network
MAP-SEND-ENDS IG NAL resp. to MSC-B
Wait For Response from MSC-B
IDLE
3GPP
Release 6
129
3GPP TS 23.009 V6.5.0 (2008-12)
Procedure MSC_A_H O
Circuit Connecti on Establishme nt to MS C-B Proc edur e for Hando ve r in MSC-A
Sheet22(26)
Wait Fo r Res ponse from MSC-B
MAP-PREPAREHAND OVER resp. [Handover Number] [A -ASG-COMP LETE] from MSC-B I_CONNECT (IAM) to MSC-B using Handover Number
Call Release
From MS or Netwo rk
MAP-SENDEND-SIGNAL resp. to MSC-B
Wai t for Comple te from MSC-B
IDLE
3GPP
Release 6
130
3GPP TS 23.009 V6.5.0 (2008-12)
Procedure MSC_A_H O
Sheet23(26)
Wait For Response from MSC-B
MAP-P REPAREHAND OVER res p. [M AP ERROR] from MSC-B
M AP -PREPAREHAN DOVER resp. [A-ASG-FAILURE] from MS C- B
from MSC -B
No Retry? Yes
MA P-PAS req. [A-CLEAR-REQUEST] from MSC-B
(Allowed onc e Call in this state ) Release
to Network
MAP-P REPAREHA ND OVER req. [NULL] [A-AS G-REQUEST] to MS C-B Wait For Response from MSC-B
Failure
R esponse to C ircui t E stablishment R equest
Failure
Re sponse to Circuit Establishment Re quest
MS on MSC-B
MS on MSC-B
IDLE
3GPP
Release 6
131
3GPP TS 23.009 V6.5.0 (2008-12)
Procedure MSC_A_H O
Sheet24(26)
W ait for Complete from MSC-B
I_COM PLE TE (ACM) from MSC-B
MAP-PAS req. [A-C LE ARREQUEST] from MSC-B
(Allow ed on ce in this state)
Cal l Rel eas e
From MS or Network
from MS C-B
MAP-S ENDEND-SIGNAL resp. to MSC-B
Succes s
Respo nse to Circuit Establishment Request
Respons e to Circuit E stablis hment Request
Fa ilure
Call on MSC-B
Wait for Complete from MSC-B
IDLE
3GPP
Release 6
132
3GPP TS 23.009 V6.5.0 (2008-12)

Pro c ed ur e for H and o ve r in M SC -A Su bse qu ent Han do ver f ro m MSC - B to M SC - B' no C ir cui t C o n ne ctio n r eq u ire d.
S hee t2 5 ( 26)
M AP-P REPA R ESU BS EQU E N THA ND OVER res p. [A-H O- RE QU ES T-A CK] to MS C- B Qu eu e M es sag es for M S in M S C -A
Set T10 3
W ait for MS o n MSC - B'
M AP-S EN D EN D- S IGN A L r eq [A-H O- CO MP LE TE ] fro m M SC -B '
M AP -P AS re q. [A - HO -D ETEC T] fr o m MSC -B '
( Allo w ed o nc e in th is s tate )
M AP -PAS r e q. [A -C L EAR RE Q UES T ] fr om M SC -B
R e set T1 03
M AP-P AS r eq. [A -C LE AR REQ UEST ] fro m M SC -B '
( Allowed o nce in th is sta te )
Yes
W a it for acces s by M S? No
For war d q ue u ed m e ssa ge s f or MS via MS C- B
Us e M AP FOR W A RD - AC C E SSSIGN AL LIN G r eq
to M SC -B a nd M SC -B '
C an c e l M AP P r oc e dur e s
R e define M SC - B' a s M SC- B
to N e tw o rk a nd MS
C a ll R e lea se
MS on M SC- B
W ait for MS on M SC -B '
ID LE
3GPP
Release 6
133
3GPP TS 23.009 V6.5.0 (2008-12)
Procedure MSC_A_H O
Sheet26(26)
W ait for MS on MSC-B'
Expiry T103
MA P-PAS re q. [A-HOFAILU RE] from MSC-B
from MSC- B'
Call Re lease
from Netw ork or MSC-B
Res et T103
from MSC-B
Forward queu ed messages f or MS via MS C-B
Us e M AP FORW ARDACCESSSIGNALLING req.
W ait for acces s by MS? No
Yes
Ca nc el MAP Proc edures
to MSC-B'
to MSC-B '
MS on MSC-B
IDLE
W ait for MS on MSC- B'
3GPP
Release 6
134
3GPP TS 23.009 V6.5.0 (2008-12)
Procedure MSC_B_H O
Procedures fo r Handover i n MSC-B
Sheet1 (18)
IDLE
MAP-PREPARE-H ANDO VER req. [A-HO-REQU EST] from MSC-A
Known BSS? Yes
No
Not Requ es ted
Hand over Number? Requested
MA P-ALLOCATE HAND OVER-NUMBE R req. to VLR
MAP-PRE PA REHANDOV ER resp [A-HO-FAILURE] to MSC-A
Set T201
A-HANDOVERREQ UE ST to BSS-B
Wai t for Channel or Handover N umber
IDLE
Figure 42 (Sheet 1 of 18): Handover control procedure in MSC-B
3GPP
Release 6
135
3GPP TS 23.009 V6.5.0 (2008-12)
Procedure MSC_B_H O
Sheet2 (18)
Wait for Channel or Handover Number
A -H ANDOV ERREQ UEST -ACK from B SS-B
MAP-A LLOCATEHANDOVERNU MBER res p. from VLR
Reset T201
Handover Number? Not Requested
Requested
MAP-PREPAREHANDO VE R resp. [A-HO-REQUEST -ACK] to MSC-A
W ait for Handover Number A lloca tion
W ait for Channel All ocation
MAP-ALLOCATEHAN DOVERNUMBE R resp. from VLR
A-HANDOVERREQUEST-ACK from BSS-B
Reset T201
MAP-PREPARE HAN DO VE R resp. [A-HO -REQUEST-ACK] [Handover Number] to MSC-A Set T204 S et T210
Wait for MS on B SS-B
W ait for Connection from MS C-A
3GPP
Release 6
136
3GPP TS 23.009 V6.5.0 (2008-12)
Procedure MSC_B_H O
Sheet3 (18)
W ait for Channel or Handover N umber
Wait for Channel Alloc ation
W ait for Channel or Handover Number
W ait for Handov er Number All ocation
A-HANDOVERFAILU RE from BSS-B
Ex pi ry T201
A-CLEA R-REQUEST from BS S-B
ERRO R
Indication from VLR
Relea se Resources in BSS-B
Retry Same Cell? Yes
No
MAP-P REPAREHA NDOVER resp. [MAP E RROR] to MS C-A
Set T201
MAP-PRE PARE HANDOVER resp. [A-HO-FAILURE] to MSC-A
Cancel Channel on BSS-B
A-HANDOVERREQUEST to BS S-B
W ait for Channel or Handover N umber
IDLE
IDLE
3GPP
Release 6
137
3GPP TS 23.009 V6.5.0 (2008-12)
Procedure MSC_B_H O
Procedures fo r Handover i n MSC-B Ba sic handover f rom MS C-A to MSC-B Circuit Connecti on requir ed
Sheet4 (18)
W ait for Connection from MSC-A
I_CONNECT (IAM) from MSC-A (Us es Handover No.)
Ex piry T210
A-CLE AR-REQUEST f rom B SS-B
Reset T210
To MSC-A in MSC-B
e.g. MAP-ABO RT from MSC-A
MAP-PAS req. [A -C LEARRE QUES T] to MS C-A
MAP -SEND-HANDOV ERREPORT res p. to VLR-B
To MSC-A in MSC-B
Set T204
I_COMPLETE (AC M) to MS C-A
Release Radio Resources o n BS S-B
W ait for acces s by MS on BSS-B
I DLE
3GPP
Release 6
138
3GPP TS 23.009 V6.5.0 (2008-12)
Procedure MSC_B_H O
Sheet5 (18)
W ait for acces s by MS on BSS-B
A-HANDOVERCOMPLE TE from BSS-B
A -CLEARR EQ UEST from B SS-B
Expiry T2 04
from MSC-A
Cancel MAP Procedure
MAP-P AS req [A -CLEARREQ UEST] to MSC-A
Res et T204
Reset T204
I_DISCONNE CT (REL) to MSC-A
Yes
ANM Sent? No
I_DISCO NN ECT (REL) from MSC-A
Releas e Resources on BSS-B
I_ANS WER (ANM) to MS C-A
A-HAND OVERD ETECT from BSS-B
to MSC-A in MSC-B
I _AN SW ER (ANM ) t o MSC-A
MAP-S ENDEND-SIG NA L req. [A-HO-CO MP LE TE] to MS C-A
Release Resources on B SS-B
MAP-P AS req [A-HO-DE TECT] to MS C-A
Call in Progress on MS C-B
I DLE
W ait for acc ess by MS on BSS-B
Wai t for Disconnect
3GPP
Release 6
139
3GPP TS 23.009 V6.5.0 (2008-12)
Procedure M SC_B_HO
Procedures for Handover in MSC-B
Sheet6(18)
Forward Messages to MS
Call in Progress on MSC-B
MAP-SENDEND-SIGNAL resp. fro m MSC-A
A-CLEAR-REQUEST from BSS-A
A-HO-PERFORMED from BSS
MAP-PAS req. [A-CLEAR-REQ UEST] to MSC-A
MAP-PAS req . [A-HO-PE RFORMED] to MSC-A
Can cel MAP Procedures
Release Resources I_DISCONNECT in BSS-A (REL) from MSC-A
from MSC-A
MSC-A disconnected? No
Yes
Release Resources in BSS-A
A-HANDO VERREQUIRED from BS S-A
Wait for Disconnect
I_DISCONNECT (REL) to MSC-A
I_DISCONNECT (REL) from MSC-A
IDLE
IDLE
3GPP
Release 6
140
3GPP TS 23.009 V6.5.0 (2008-12)
Procedure MSC_B_H O
Sheet7 (18)
Known MSC? No
Yes
No
Handover allowed to Cell? Yes MSC-A/MSC-B' Which MSC? MS C-B
Known BSS? No Yes
MAP-P REPARESU BSEQUENTHA NDOVER req. [A-HO-REQ UEST] to MS C-A
Yes
Select New C ell? No
Resources on BSS-B? No Yes
No Send Rejec t?
Yes A-HANDOVERREJECT to BS S-A
Set T211
No
Call in P rogress on MSC-B
MS on MSC-B
Wait for Respons e
3GPP
Release 6
141
3GPP TS 23.009 V6.5.0 (2008-12)
Pro ce d ure M S C _B_ H O

Pr o ced ures fo r Ha nd ove r i n M S C- B Ha nd ove r fro m BS S-A to BS S- B on M SC -B
S hee t8 (18)
A-H A N DOV E R- R EQU E ST to BS S- B
S et T20 1
W ait for C h ann el
A-H A N D OVE R R EQU E ST- A CK fro m BS S-B
Ex pi ry T 2 01
A- H AND OV ER F A IL UR E fr o m B S S- B
M A P- SEN D- END S IG NAL r e sp. f rom MS C- A
R e set T20 1
R ese t T 20 1
A- CLE AR -R E QU EST fr o m B SS- A
Qu eu e M es sag es i n M S C -B
M AP - PAS re q [A -C L EAR R EQ UE ST ] to M SC- A
Ca nce l C han ne l req ues t on B SS-B
H an dov er C o m ma n d to M S vi a B SS-A
R e lea s e R e sou r ce s C an c e l M A P o n BS S- B P r oc e du res
T o M S C -A in M S C -B
Se t U p H a nd ov e r D e vice
R etry H an do ver A tte m pt? Y es
R ele ase Re s o urce s on B SS-A No
S et T20 2
C ell? S am e C e ll New C el l
W ait for a cc es s by MS
W ai t for D isc o nn e ct
3GPP
Release 6
142
3GPP TS 23.009 V6.5.0 (2008-12)

Pr o ced ures fo r Ha nd ove r i n M S C- B
S hee t9 (18)
W ait for a cc es s by MS
A-H A N D OVE R COM PL E TE fro m BS S-B
A -H AND OV ER D ET ECT fo r m B S S-B
A - H AND OV ER F AIL UR E f rom B SS-A
R e set T20 2
M AP-P AS r eq. [A-H O- PERF OR M ED] to MS C- A
C ircu it C o nn ec tio n? Ye s
No
Cir cu it Con ne ctio n? Ye s
No
Co nn ect H a nd ov e r D e vice (O p tio n al )
Co nn e ct Ha nd o ve r De vice (Op tion al )
R ese t T2 02
For war d q ue u ed m e ssa ge s via B S S- B
Fo r wa rd queu ed m e ssag es vi a BS S- A
R e le ase R eso urce s in B SS- A
R e lea se R e sou rce s in BSS - B
C ircu it C o nn ec tio n? Ye s
No
No
C irc u it C on nec tion ? Yes
Re le ase H a nd ov e r D e vice
R e lea se H a n dov e r D e vice
C a ll in P rog re s s o n MS C- B
MS on MS C- B
W ait for a cce ss by M S
MS on M S C -B
C all in Pro gres s on MS C- B
3GPP
Release 6
143
3GPP TS 23.009 V6.5.0 (2008-12)
Procedure MSC_B_H O
Sheet10(18)
W ait for acces s by MS
Expiry T202
A-CLEAR-REQ UEST fr om BSS-B
MAP-SEN D-ENDSIGNAL resp. from MSC -A
Release Resources in BSS -B and B SS-A
Release Res ourc es in BS S-A
Yes
W ait for acce ss by MS? No
MAP-PAS req. [A-CLEAR-REQUEST] to MS C-A
MA P-PAS req. [A-CLEAR-REQUEST] to MSC-A
Release Resource s i n BSS -B and B SS-A
To MSC-A in MSC-B
To MS C-A in MSC-B
I_DISC ONNE CT (REL) to MSC-A
Release Resourc es in BS S-B
IDLE
Wait for access by MS
W ait for Dis connect
W ait for Dis connec t
3GPP
Release 6
144
3GPP TS 23.009 V6.5.0 (2008-12)

Pr o ced ures fo r Ha nd ove r i n M S C- B Su bse quen t H an do ver fr o m M SC -B to M SC- A
S hee t1 1 ( 18)
W a it fo r Re s pon se
M AP- P R EPA RE SU B SEQ UE N TH AN DO VE R r esp . [A - HO- R EQU E ST - ACK ] fr om MS C- A Re s et T2 11 R e se t T 2 11
M AP -PR E PAR E S UBS EQ UE NT H AN DO VE R r e sp. [A- HO -FA ILU R E o r M AP E RR OR ] fr om MS C- A
Exp iry T2 11
A- C LE AR R EQU ES T fro m BSS - A
M A P-P A S r e q . [A-C L EA R R EQ UE ST ] to M S C- A
M AP R el ea se Res our ces -SEN D -EN D SIGN AL re sp. in B SS -B fr om M SC -A
in M SC -B to M S C- A
Ca nce l MA P Pro ced ur e s
H and ove r Co m m an d to M S via BS S- A
R e tr y H a nd ove r A ttem p t? Ye s
No
Se t T2 04
S am e C e ll C e ll? N ew C ell
R ele ase Re s o urce s in BS S-A
W a it fo r Ack . fr o m MS C- A
W ai t for D isc o nn e ct
3GPP
Release 6
145
3GPP TS 23.009 V6.5.0 (2008-12)

Pr o ced ures fo r Ha nd ove r i n M S C- B
S hee t1 2 ( 18)
W ai t for A ck . fr o m MS C- A
M AP- S END END SIGN A L res p. fr o m M SC -A
Ex pi ry T 2 04
A- C LE AR -R E QU EST from B SS-A
A-H AN D OVE R FAIL U RE from BS S-A
Res et T20 4
Re lea se Re s o ur ce s MA P- P AS re q. [A-C LEA R -R EQU EST] in B SS-A to M SC -A
Re set T2 04
R ele ase Re s o urce s Ca nce l MA P in B SS-A Pr oce du res
to M SC -A in M SC- B
R e le ase R e so u rc e s in B SS- A
M AP-PAS r eq. [A -H O- FAIL U RE] to MSC -A
to M SC -A
C an c e l M A P Pr oc ed ur es
Circui t C on n ec tio n? Y es
No
Circu it C on nec tio n? Yes
No
W ai t for D isc o nne ct
IDLE
C all i n P ro gre s s o n MS C- B
MS on MS C- B
3GPP
Release 6
146
3GPP TS 23.009 V6.5.0 (2008-12)
Proce dure MSC_B_H O

Proce dures for Ha ndover in MSC-B Basic han dov er from MSC-A to MSC-B no Circ uit Connect ion required
Sheet13(18)
W ai t for MS on BSS-B
A-CLEARREQUEST from BSS-B
E xp iry T204
from MS C-A
Cancel MAP Proc edure
Reset T2 04
MAP-P AS req [A-CLEARREQ UEST] to MS C-A
MAP -SENDEND-SIGNAL req. [A -HO-COMPLETE] to MSC-A
A-HANDOVERDETECT from BSS-B
to MSC-A in MS C-B
MA P-PAS req. [A-HO-DE TECT] to MSC-A
MS on MSC-B
Wait fo r MS on BSS-B
IDLE
3GPP
Release 6
147
3GPP TS 23.009 V6.5.0 (2008-12)
Procedure MSC_B_H O
Sheet14(18)
Forward Messages to MS
MS on MS C-B
MA P-SENDEND-SIG NAL resp. from MSC-A
A-HANDOVERREQ UIRED fro m BSS-A
MAP-PREPAREHANDOVER req. [NU LL] [A-ASG-R EQ UE ST] from MSC-A MAP-ALLOCATEHANDOV ER-NUMBER req. to VLR
Releas e Resources in BSS-B
A-ASSIGNMENTREQUEST to B SS-A
IDLE
Wa it f or Ass ignmen t or Han dov er Number
3GPP
Release 6
148
3GPP TS 23.009 V6.5.0 (2008-12)
Procedure MSC_B_H O
Procedures fo r Handover i n MSC-B Circuit Connecti on Establishment on MS C-B
Sheet15(18)
Wait for Assi gnment or Handover Number
A-ASSIGNMENTCOMPLE TE from BSS-A
MAP-ALLOCATEHAN DOVERNUMBE R resp. from VLR
Wait for Handover Number Alloc ation
W ait for Assignment
MAP-ALLOCATEHANDOVERNUMBE R resp. from VLR
A-ASSIGNME NT COMPLETE from BS S-A
M AP -PREPAREHAN DO VER resp. [Handover Numbe r] [A-ASG-COMPLETE] to MSC-A Set T210
Wait for Connect from MSC-A
3GPP
Release 6
149
3GPP TS 23.009 V6.5.0 (2008-12)
Procedure MSC_B_H O
Sheet16(18)
W ait for Ass ignment or Handover N umber
Wai t for Assignment
Wait for W ait for W ait for Assi gnment or Handover Number As signment or Handover Number A lloca tion Handover Numb er
Wait fo r Handov er Number Allocation
A-ASSIGNMENTFAILU RE from BSS-A
E RROR
Indi cation fro m VLR
MAP-S ENDEND-SIG NA L resp. fr om MSC-A
MAP-P REPAREHA ND OVER res p. [A-AS G-FA ILURE] to MS C-A
M AP -PREPAREHAN DO VER resp. [MAP ERR OR] to MSC-A
A-CLEAR-REQUEST from BSS-A
MAP-PA S req. [A-CLEAR-REQ UEST] to MSC-A
to MSC-A a nd VLR-B
to VLR-B
MS on MSC-B
IDLE
3GPP
Release 6
150
3GPP TS 23.009 V6.5.0 (2008-12)
Procedure MSC_B_H O
Sheet17(18)
Wai t for Connect from MSC-A
I_CONNECT (IAM) from MSC-A (Uses Handover No.)
Expiry T210
A-CLEAR-REQUEST fro m BSS-A
Res et T210
to MSC-A in MSC-B
MAP-PA S req. [A-CLEAR_REQ UE ST] to MS C-A
MAP-SEND- HANDOVERREP ORT resp . to VLR-B
to MS C-A in MSC -B
I_COMPLETE (ACM) to MS C-A
Release Radio Resources on BSS-A
Call on MS C-B
IDLE
3GPP
Release 6
151
3GPP TS 23.009 V6.5.0 (2008-12)
Procedure MSC_B_H O
Sheet18(18)
Wait for Connect from MSC-A
I_DISCONNECT (REL) from MSC-A
MAP-SENDEND-SIGNAL res p. from MSC-A
from MSC-A
Release Resour ces on BS S-A
MS on MS C-B
ID LE
IDLE
3GPP
Release 6
152
3GPP TS 23.009 V6.5.0 (2008-12)
Procedure 3G_MS C_A_H O

Procedure for Handove r in 3G_MSC-A
S heet1 (78)
IDLE
Call i n P rogress on 3G_MS C-A
A-HANDO VE R-REQ UIRED from BSS-A (GS M to UMTS Han dover)
Iu-REL OCATIO N-REQUIRED from RNS-A
Known MSC? No
Yes
Type of handover
To GSM
No
Handover allowed to Cell? 11 Yes 3G_MSC-B
S RN S Relocation 10
From MS or N etwork Imp licit Rel eas e of B SS-A
Call Release
W hic h M SC?
3G_MSC-A No
Known RNS? Yes
3 No Resources o n RNS-B? Yes No Send Rejec t? Yes
A-HANDOVERREJECT to BS S-A
Call i n P rogress on 3G_MS C-A (GSM)
IDLE
Figure 43 (sheet 1 of 78): Handover control procedure in 3G_MSC-A
3GPP
Release 6
153
3GPP TS 23.009 V6.5.0 (2008-12)
Procedure 3G_MSC_A_H O
Procedur e for Handove r in 3G_MSC-A Handover on 3G_MSC-A from BSS-A to RNS-B.
Sheet2 (78)
Iu RELOCAT IO N-R EQ UE ST to RNS-B
Set T501
Wait for Channel Allocation Intra-MSC
Iu-RELOCATIONREQUEST-ACK from RNS-B
Iu-RELOCAT IO N FAIL URE from RNS-B
From UE/MS or Network
Call Releas e
Reset T501
E xpiry T 501
Reset T501
Queue M es sages for UE/MS in 3G_MSC-A
Call Release
to Network
Han dov er Command to UE/MS via B SS-A
Cancel Channel in RNS-B
Release Res ources in BSS-A
Set Up Handov er Device
Internal message in 3G_MSC-A
Set T502
W ait for acces s by UE/MS on RNS/BSS (GSM to UMTS Ho)
IDLE
3GPP
Release 6
154
3GPP TS 23.009 V6.5.0 (2008-12)
Procedur e for Handove r in 3G_MSC-A
Sheet3 (78)
Wai t for acces s by UE /MS on RNS/BSS (GS M to UM TS Ho)
Iu-R ELOCATION COMPLETE from RNS-B
Iu-RELOCATIO N DETE CT from RNS-B
Connect the Handove r Device (O ption)
Only if not already connec ted
Connect the Handover Devic e (Option)
Res et T502
Releas e Resources in BSS-A
Forward queued me ssages for UE/MS vi a RNS-B
Call in P rogress on 3G_MS C-A (UTRAN)
W ait for access by UE/MS on RNS/B SS (GSM t o UMTS handover)
3GPP
Release 6
155
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet4 (78)
W ait for Access by UE/MS On RNS/BSS (GSM to UMTS Ho)
A-HANDOVERFAILU RE from BSS-A
A-CLEARREQ UEST from B SS-A
(Allow ed once in thi s state)
Expiry T5 02
Cal l Rel eas e
From N etwork
Reset T502
(All owed once in thi s state)
Iu-REL EA SE REQ UEST from RNS- B
Release Resources in BS S-A
Release Resource s in BSS-A
Forward queued messages for UE/MS via BSS-A
Releas e Resources in RNS-B
Yes
W ait for UE/MS on BSS-B? No
Release Ha ndover Device
Re lease Re sources in RNS -B
Reset T 502
Release Resources in R NS-B
Call Release
to Network
Releas e Handover Devic e
Call in Progress on 3G_MSC-A (GSM )
Wait for access by UE/MS on RNS /B SS (GSM to UMT S Ho)
IDLE
Wa it for acces s by UE /MS on RNS/BSS (G SM to UMTS Ho)
3GPP
Release 6
156
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet5 (78)
10
Known MSC? No
Yes
No
Handover allowed to Cell? Yes MSC-B
Which MSC? 3G_MS C-A No
Known BSS? Yes
12 No
Resources on BSS-B? Yes
Iu- RELOC ATION PREP ARAT ION FAIL URE to RNS-A
Call in P rogres s on 3G_MS C-A (UT RAN)
13
14
3GPP
Release 6
157
3GPP TS 23.009 V6.5.0 (2008-12)
Procedur e for Handove r in 3G_MSC-A Handover on 3G_MSC-A from RNS-A to BSS-B.
Sheet6 (78)
13
A-HANDO VER -REQU EST to BS S-B
Set T301
Wait for Channel Allocation Intra-MSC
A-HANDOVERFA ILURE from BSS-B
Call Releas e
Reset T301
E xpiry T 301
Reset T301
Iu-R ELEASEREQUEST from RNS-A
Call Release
to Network
Han dov er Command to UE/MS via Iu-RELOCATION Command to RNS-A
Cancel Channel in B SS-B
Release Res ources in RNS-A
Cancel Channel in BSS-B
Set T302
W ait for acces s by UE/MS on B SS/RNS (UMTS to GSM Ho)
12
IDLE
3GPP
Release 6
158
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet7 (78)
Wait for access by UE/MS on BSS/RNS (UMTS to GSM han dov er)
A -H ANDOVER-COMPLETE from BS S-B
A-HANDO VE R- DETECT from BSS-B
Connect the Handover Dev ice (O ption)
Only if not alread y connec ted
Connec t t he Handov er Device (Option)
Res et T302
Forward queued mes sages for UE/MS via B SS-B
Cal l in Progress on 3G_MSC -A (GSM)
W ait for access by U E/MS on B SS/RNS (UMTS to GSM Ho)
3GPP
Release 6
159
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet8 (78)
W ait for Access by UE/MS On RNS/BSS (UMTS to GSM Ho)
Iu-RELOCATIONCANCEL from RNS-A
Iu-REL EA SE REQ UEST from RNS- A
Expiry T3 02
Cal l Rel eas e
From N etwork
Reset T302
A-CLEAR REQ UEST from B SS-B
Release Resources in RNS-A
Release Resource s in R NS-A
Forward queued messages for UE/MS vi a RNS-A
Releas e Resources in BSS-B
Yes
W ait for UE/MS on BSS-B? No
Re lease Re sources in BSS -B
Reset T 302
Release Resources in BS S-B
Call Release
to Network
Call in Progress on 3G_MSC-A (UTRAN)
Wait for access by UE/MS on RNS /B SS (UMTS to GSM Ho)
IDLE
Wa it for acces s by UE /MS on RNS/BSS (UMTS to GSM Ho)
3GPP
Release 6
160
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet9 (78)
11
Yes Known 3G_MSC? No
Which 3G _MSC?
3G_MSC-B
3G_MS C-A Known RNS? No 16 Yes
Resources on RNS-B? No Yes Iu- RELOC ATION PREP ARAT ION FAIL URE to RNS-A
Call in P rogres s on 3G_MS C-A (UT RAN)
15
17
3GPP
Release 6
161
3GPP TS 23.009 V6.5.0 (2008-12)
Procedur e for Handove r in 3G_MSC-A SRNS R el ocation on 3G_MSC-A from RNS -A to RN S-B
Sheet10(78)
15
Iu-RELOCATION -REQU EST to RNS-B
Set T701
Wait for Channel Allocation Intra-3G_MS C
Iu-RELOCAT IO N FAIL URE from RNS-B
From UE or Network
Call Releas e
Reset T701
E xpiry T 701
Reset T701
Iu-R ELEASEREQUEST from RNS-A
Queue M es sages for UE in 3G_MSC-A
Call Release
to Network
Iu-RELOCATION Command to RNS-A
Set T702
W ait for acces s by UE on RNS (SRNS Relocation)
16
IDLE
3GPP
Release 6
162
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet11(78)
Wait for access by UE on RNS (SRNS RELO CATION)
Iu-RELO CATIONCOMPLETE from RNS-B
Iu-RELOCATIONDET ECT from RNS-B
Connect the Handove r Dev ice (O ption)
Only i f not already connec ted
Conne ct the Handover Device (Option)
Reset T702
Rel ease Res ources in RNS-A
Forward queued mes sages for UE via RNS-B
Call in P rogress on 3 G_MS C-A (UTRAN)
W ait for access by UE on RNS (SRNS Reloca tio n)
3GPP
Release 6
163
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet12(78)
W ait for Access by UE O n RNS (SRNS Relocation)
Iu-RELOCATIONCANCEL from RNS-A
Iu-REL EA SE REQ UEST from RNS- A
Expiry T7 02
Cal l Rel eas e
From N etwork
Reset T702
Iu-REL EA SE REQ UEST from RNS- B
Release Resource s in R NS-A
Forward queued messages f or UE via RN S-A
Releas e Resources in RNS-B
Yes
W ait for UE on RN S-B? No
Re lease Re sources in RNS -B
Reset T 702
Release Resources in R NS-B
Call Release
to Network
Call in Progress on 3G_MSC-A (UTRAN)
Wait for access by UE on RNS (SRNS Relo cation)
IDLE
Wa it for acces s by UE on RNS ( SRNS Re location)
3GPP
Release 6
164
3GPP TS 23.009 V6.5.0 (2008-12)
Procedur e for Handove r in 3G_MSC-A Bas ic GS M to UMTS han dov er to 3G_MSC-B Circuit Connection required
Sheet13(78)
MAP-P REPAREHA ND OVER req. [A-HO-REQ UEST] to 3G_MS C- B
Wait For Ack nowledgement from 3G_MSC-B (GSM to UMTS Ho)
MAP-PREPAREHAND OVER resp. [A-HO-REQU EST-ACK] from 3G_MSC-B
MAP-PREPARE HANDOVER r esp. [A-HO-FA ILUR E] from 3G_MS C-B
MAP-P REPAREHA NDOVER res p. [MAP ERROR] from 3G_MSC-B
Handover Number?
N ot Requested
Requested I_CONNECT (IAM) to 3G_MSC-B using Handover Number
W ait for Connection from 3G_MSC-B (GSM to UMTS Ho)
3GPP
Release 6
165
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet14(78)
Wait For Ack nowledgement from 3G_MSC-B (GSM to UMTS Ho)
ERRO R
from 3G_MSC-B
Call Re lease
in 3G_MSC-A
to Network
Call Release
to 3G_MS C-B
IDLE
3GPP
Release 6
166
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet15(78)
W ait for Connection from 3G_MSC-B (GSM to UMTS Ho)
I_COMPLETE (AC M) from 3G_MSC-B
(A llowed once in this s tate )
From UE /MS or Netwo rk
Call Releas e
MAP-PA S req. [A-CLEAR-REQUEST ] from 3G_MSC-B
(Allowed once i n thi s state)
Call Release
to UE /MS and Network
Wait f or Connec ti on from 3G_MSC-B (GSM to UMT S Ho)
ERROR
from 3G_MS C-B or Network
I_DISCONNECT (REL) to 3G_MSC-B
Set T503
to 3G_MSC-B in 3G_MSC-A
I_D ISCONNECT (REL) to 3G_MS C-B
W ait for Comp letion on 3G_MSC-B (GSM to UMTS Ho)
IDLE
3GPP
Release 6
167
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet16(78)
W ait for Comp letion on 3G_MSC-B (GSM to UMTS Ho)
MAP-S ENDEND-SIG NA L req. [A-HO-CO MP LE TE] from 3G_MSC-B
I-ANSW ER (ANM) from 3G_MSC-B
MAP-PAS req. [A-H O-DE TECT] from 3G_MSC-B
Reset T503
MA P-PAS re q. [A-CLEAR-REQUEST] from BSS-B
(Allowed once in this s tate)
A-CLEAR-R EQ UEST from BSS-A
Release Resourc es on BSS-A
Yes
W ait for UE/MS on 3G_MSC-B? No
Wai t f or Completion on 3G_MS C-B (GS M to UM TS Ho)
Call Release
to Ne twork and UE/MS
Forward queu ed messages via 3G_MSC-B
Release MAP Resourc es
Connect Handove r Devi ce (op tio n)
Re lease Re sources on BSS-A
I_DIS CO NNECT (REL) t o 3G_MSC -B
Call on 3G_MSC-B (UTRAN)
IDLE
Wai t f or C ompletion on 3G_MS C-B (GS M to UM TS Ho)
3GPP
Release 6
168
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet17(78)
Wai t f or Completion on 3G_MS C-B (GS M to UM TS Ho)
I_DISCONNECT (REL) from 3 G_ MSC-B
Expiry T5 03
Cal l Rel eas e
from Network
Res et T503
In 3G_MSC -A and to 3G_MSC -B
Re lease Handover Device
In ternal to 3G_MSC-A
Forward q ueued me ssages for UE /MS vi a B SS-A
Internal to 3 G_ MSC-A
Wa it for Comp letion on 3G_MS C-B (G SM to UMTS Ho)
in 3G_MSC-A to 3G_MSC-B
from 3G_MSC-B
In 3G _MSC-A and to 3G_MS C-B
Internal to 3G_MSC-A
Release Resources BSS-A
Call in P rogress on 3G_MS C-A (GSM)
W ait for Completion on 3G_MSC-B (GSM to UMTS Ho)
IDLE
3GPP
Release 6
169
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet18(78)
Call on MSC-B (GSM)
MAP-PREPARESUB SEQUENTHAND OVER req. [A-HO-REQU EST] from MSC-B Known 3G _M SC? Yes No Call on MSC-B
MAP-P AS req. [A-CLEARREQUEST] from 3 G_MS C-B
Call Releas e
No
from MSC -B
3G_MSC-B'
Which 3G_MSC? 3G_MSC-A
Call Release
to Network and UE/MS
Known RNS? Yes
No
Res ourc es on new RNS? Yes
No
IuR ELO CATIONR EQ UEST to RNS-B
MAP-P REPARESUBSEQUENTHANDOVER resp. [A-HO-FAILURE] to MS C-B Set T501 No Circuit Connection? Yes
MAP-PRE PA RESUBSEQUENTHANDOVER resp. [MAP E RROR] to MS C-B
Wait for Channel Allocation (GS M to UM TS Ho)
UE/MS o n MSC -B (GSM)
Call on MSC-B (GSM)
IDLE
3GPP
Release 6
170
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet19(78)
Wait for Channel Allocation (GS M to UMTS Ho)
Iu-RELOCATION REQU EST-ACK. from RNS-B
IuRELOC ATION FAILURE from RNS-B
Expiry T5 01
Call Re lease
Reset T501
Reset T501
Ca nc el Channel RNS-B
Queue Messages for UE/MS in 3G_MSC-A
MAP-PAS req. [A -CLEAR-REQUE ST] from MS C-B
MAP-SEND-ENDSIGNAL resp to MS C-B
MAP-PREPARE SUBSEQ UENTH ANDOV ER resp [A-HO -R EQUESTACK] t o MSC-B No Circuit Connect ion? Yes
Release Resources in RNS-B
I_DISCON NE CT (REL) to MSC-B
Call o n MSC -B
Se t Up Handove r Dev ice
Set T504
MAP-PREPARESUBSEQUENT HA NDOVER resp. [A-HO-FAILURE] to MSC-B Call on MSC-B (GSM)
Wait for Acces s by UE /MS (GS M to UMTS Ho)
IDLE
3GPP
Release 6
171
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet20(78)
Wa it f or acces s by UE /MS (G SM to UMTS Ho)
Iu-RELOCATION COMPLE TE from RNS- B
Iu-RE LO CATION DETECT from RNS-B
Expiry T504
Res et T504
No
Call Release
to Network
Connect Han dov er Devi ce (o ption)
C onnec t H andover D evice (option)
Release Resources on RNS-B
Forward queued messages for MS via RNS-B
in 3G_MSC-A to MS C-B
MA P-SEND-ENDSIGNAL resp. to MSC-B
I _DISCONNECT (RE L) to MSC-B
No
Ci rcui t Con nection? Yes
Releas e Han dov er Device
I_DISCON NECT (REL) to MSC-B
Call in P rogress on 3G_MS C-A (UT RAN)
W ait for access by UE/MS (GSM to UMTS Ho)
IDLE
3GPP
Release 6
172
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet21(78)
W ait for acces s by UE/MS (GSM to UMTS Ho)
MAP-PAS req. [A-HOFAILU RE] from MSC-B
fro m Network
Call Releas e
Iu -RELEASE REQUEST from RNS-B
Re lease Re sources on RNS-B
No
Call on MS C-B (GSM )
UE /MS on MSC-B (GSM)
Wait for access by UE /MS (GS M to UMTS Ho)
3GPP
Release 6
173
3GPP TS 23.009 V6.5.0 (2008-12)
Procedur e for Handove r in 3G_MSC-A Sub sequent GSM to UMTS Handover from MSC-B to 3G _MSC-B' Circ uit Connection required
Sheet22(78)
MAP-PREPARE-H ANDOVER req [A-HO-REQ UEST] to 3G_MSC- B'
W ai t for Ack from 3G_MSC-B' (GSM to UMTS Ho)
MAP-P REPAREHAND OVER res p.. [A-HO-RE QUES T-A CK] from 3G_MSC-B'
MAP-PRE PA REHANDOVER resp. [A-HO-FAILURE] from 3G_MSC-B '
Handover Number?
Not Requested
Requested
I_CONNECT (IAM) to 3G_MS C- B' using Han dov er Number
MAP-P REPARESUBSEQUENTHA NDOVER resp. [A-HO-FAILURE] to MSC-B Call on MSC- B (GSM)
W ait for Connection from 3G_MSC-B' (GSM to UMTS Ho)
3GPP
Release 6
174
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet23(78)
W ai t for Ack from 3G_MSC-B' (GSM to UMTS Ho)
ERRO R
from 3G_MSC-B'
f rom MS C-B o r Network
ERRO R
Call Release
Re lease MAP Re sources
to 3G_MSC- B'
to 3G_MSC- B'
MAP-PAS req. [A-CLEAR- REQUEST] from 3G_MSC-B
MAP-S ENDEND-SIGNA L resp. to MS C-B
to 3G_MSC-B'
Release Handov er Device
ERROR
MAP-P REPARESUBSEQUENTHA ND OVER res p. to MS C-B
I_DISC ONNECT (REL) to MSC-B
W ait for Ack fr om 3G _MSC-B' (GSM to UMTS Ho)
IDLE
3GPP
Release 6
175
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet24(78)
W ait for Connection from 3G_MSC-B' (GSM to UMTS Ho)
I_ COMPLETE (ACM) from 3G_MSC-B'
fr om 3G_MSC-B' or Network
ERRO R
from UE/MS or Network
Call Releas e
MAP-P AS req. [A-CLEARREQUEST] from 3G_ MSC-B '
MAP-PA S req. [A-CLEARREQ UEST] from MSC-B
W ait f or Connection f rom 3G _MSC -B' (GSM to UMTS Ho)
MAP-P REPARESUBSEQUENTHA ND OVER res p. [A-HO-RE QUES T-A CK] to MS C-B Cancel MAP Procedures Canc el MAP Procedures
to 3G _MSC-B'
to 3G_MSC-B'
to MS C-B and 3G _MSC-B'
Queue m es sages for UE/MS in 3G_MSC-A
I_ DISCONNECT (RE L) to 3G_MSC-B'
MAP -SENDE ND-SIGNAL resp to MSC-B
Call Release
to Network and UE /MS
Set T503
E RROR
M AP -PREPARES UBS EQ UE NT H ANDO VER resp. to MSC-B
I_DISCO NNECT (REL) to MSC-B and 3G _MSC-B'
W ait for Comp letion on 3G _MSC-B' (GSM to UMTS Ho)
Call o n MSC -B (GSM)
IDLE
3GPP
Release 6
176
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet25(78)
MAP-S ENDEND-SIG NA L req. [A-HO-CO MP LE TE] from 3G_MSC-B'
MAP-P AS req. [A-HO-DETECT] from 3G _MSC-B'
MAP-PA S req. [A-CLEARREQUE ST ] from MSC-B
(Al lowed onc e in this state)
Reset T503
I_ANSWER (ANM) from 3G_MSC -B '
MA P-PAS req. [A -CLEARREQUEST] from 3G_MSC-B'
(A llowed once in this s tate)
Connec t Handover Devi ce (option)
Yes
Wait for ac cess by UE/ MS? No
Forward queu ed messages for UE/MS via 3G_MSC-B'
Release Handove r Dev ice
MAP-S ENDEND-SIG NA L resp. to MS C-B
to MS C-B and 3G_MSC-B'
I_DISC ONNE CT (REL) to MSC-B
Call Release
Redefine 3G_MSC-B' as 3G_MSC-B
I_D ISCO NNECT (REL ) to MSC-B and 3G_MSC-B'
W ait for Completion fr om 3G _MSC-B' (GSM to UMTS Ho)
IDLE
3GPP
Release 6
177
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet26(78)
Expiry T503
MA P-PAS re q. [A-HO-FAILU RE] from MSC-B
from 3G_MSC-B'
From Network or MSC-B
Call Releas e
Res et T503
from MSC-B
I_DISCONNEC T (REL) to 3G_ MSC-B '
to 3G_MSC- B'
Rel eas e Handover Device
I_ DISC ONNECT (REL) to 3G_MSC-B '
W ait for acc ess by UE/MS? No
Yes
MSC-B Connection? No
Yes
to 3G_MSC-B'
Use MAPFORW ARDACCE SS SIGNALLING req.
Forward queued mes sages for UE/MS vi a MSC-B
I_DISCONN ECT (REL) to 3G _MSC-B'
Call Re lease
to Netwo rk
IDLE
Call on MSC-B (GSM)
IDLE
Wait f or Co mpleti on on 3G _MSC -B ' (GS M to UMTS Ho)
3GPP
Release 6
178
3GPP TS 23.009 V6.5.0 (2008-12)
Procedur e for Handove r in 3G_MSC-A Bas ic GS M to UMTS Handover to 3G_MSC-B no Circuit Connection requ ired
Sheet27(78)
Set T503
W ait for UE/MS on 3G_MSC-B (GSM to UMTS Ho)
MAP-S ENDEND-SIG NA L req. [A-HO-CO MP LE TE] from 3G_MSC-B
A-CLE ARREQUEST from BS S-A
MAP-PAS req. [A-H O-DE TECT] from 3G_MSC-B
Reset T503
MAP-PA S req. [A-CLEARREQ UE ST] from 3G_MSC-B
(Allowed once in this state) Yes
Re lease Re sources on BSS-A
W ait for UE/MS on 3G_MSC-B? No
Forward queu ed messages for UE/MS via 3G_MSC-B
Us e M AP FORWA RD- ACCESSSIGNALLING req.
Cal l Release
to Network and U E/MS
UE/MS on 3G_MSC-B (UTRAN)
W ait for UE/MS o n 3G_MSC-B (GSM to UMTS Ho)
IDLE
W ait for UE/MS on 3G_MSC-B (G SM to UMTS Ho)
3GPP
Release 6
179
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet28(78)
Wai t for UE/MS on 3G_MS C-B (GS M to UM TS Ho)
from 3 G_ MSC-B
Expi ry T503
Call Re lease
from Netw ork
Res et T503
Forward q ueued me ssages for UE /MS vi a B SS-A
Release Reso urces BSS-A
Release Resourc es BS S-A
Call in P rogress on 3G_MS C-A (GSM)
Wait for UE /MS on 3G_MSC-B (GSM to UMT S Ho)
IDLE
W ait for UE/MS on 3G_MSC-B (G SM to UMTS Ho)
3GPP
Release 6
180
3GPP TS 23.009 V6.5.0 (2008-12)
Procedur e for Handove r in 3G_MSC-A UE/MS Established on M SC-B without a Circ uit Connection
Sheet29(78)
UE /MS on MSC-B (GSM)
Reque st for Circuit Es tablishment
F rom MSC-B
Call Releas e
M AP -PREPARES UBS EQ UE NTHAN DO VER req. [A-HO-REQUEST] from MS C- B MAPPREPAREHANDOVER re q. [NUL L] [A-ASGREQ UE ST] to MSC-B
Call Release
to Network
Wai t F or Response from MSC-B (UMTS to GSM Ho)
IDLE
3GPP
Release 6
181
3GPP TS 23.009 V6.5.0 (2008-12)
Procedure 3G_MSC_A_HO
Procedure for Handover in 3G_MSC-A Circuit Connection Establishment to 3G_MSC-B
Sheet30(78)
Wait For Response from 3G_MSC-B (GSM to UMTS Ho)
MAP-PREPAREHANDOVER resp. [Handover Number] [A-ASG-COMPLETE] from 3G_MSC-B I_CONNECT (IAM) to 3G_MSC-B using Handover Number
Call Release
MAP-PREPAREHANDOVER -SUBSEQUENTHANDOVER req [A-HO-REQUEST] from 3G_MSC-B
MAP-SENDEND-SIGNAL resp. to 3G_MSC-B
Wait for Complete from 3G_MSC-B (GSM to UMTS Ho)
IDLE
19
3GPP
Release 6
182
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet31(78)
W ait For Response from 3G_MSC-B (GSM to UMTS Ho)
MAP-P REPAREHAND OVER res p. [M AP ERROR] from 3G_MSC-B
MAP -PREPAREHANDOVER resp. [A- ASG-FAILURE] from 3G_MS C- B
Cance l MAP Proce dures
from 3G_MSC-B
MA P-PAS re q. [A-CLEAR-REQUEST] from 3G_MSC-B
(A llowed once in this state )
Call Re lease
to Netwo rk
Failure
Failure
Res po nse to Circuit Establishment Request
UE/MS on 3 G_MS C-B (UTRAN)
UE/MS on 3G_MSC-B (UT RAN)
IDLE
3GPP
Release 6
183
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet32(78)
W ait for Comp lete from 3G_MSC-B (GSM to UMTS Ho)
I_COM PLE TE (ACM) from 3G_MSC-B
MAP-PAS req. [A -CLEARREQ UEST] from 3G_MSC-B
Call Re lease
from 3G_MSC-B
MAP-S EN DEN D-SIGNAL res p. to 3G_MSC-B
Succes s
Respons e to Ci rcu it E stablishme nt Request
F ailure
W ait for Comp lete from 3G_MSC-B (GSM to UMTS Ho)
Call on 3G_MS C-B (UTRAN)
IDLE
3GPP
Release 6
184
3GPP TS 23.009 V6.5.0 (2008-12)
Procedur e for Handove r in 3G_MSC-A Sub sequent GSM to UMTS Handover from MSC-B to 3G_ MSC-B' no Circuit Connection requ ired.
Sheet33(78)
MAP-P REPARESUBSEQUENTHA ND OVER res p. [A-HO-RE QUES T-A CK] to 3G_MS C- B Queue M es sages for UE/MS in 3G_MSC-A
Set T503
W ait for UE/MS on 3G _MSC-B' (GSM to UMTS Ho)
MAP-S ENDEND-SIGNAL req [A-HO-CO MP LE TE] from 3G_MSC-B'
MAP-P AS req. [A-HO -DETECT] from 3G _MSC-B'
(Allowed once in this st ate)
MAP-PAS req. [A -C LEARREQ UEST] from MSC-B
Reset T503
MAP-P AS req. [A-CLEARREQUEST] from 3G_ MSC-B '
Yes
Forward queu ed messages for UE/MS via 3G _MSC-B'
to 3G_MSC- B and 3G_MSC-B'
Call Re lease
W ait for UE/MS on 3G_MSC-B' (GSM to U MT S H o)
IDLE
3GPP
Release 6
185
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet34(78)
W ait for UE/MS on 3G _MSC-B' (GSM to UMTS Ho)
Expiry T503
MA P-PAS re q. [A-HOFAILU RE] from MSC-B
from 3G_MSC-B'
Cal l Rel eas e
from Network or MSC-B
Res et T503
from MSC-B
Forward queu ed messages for UE/MS vi a MS C-B
Yes W ait for access by UE/MS? No
to 3G_MSC- B'
to 3G_MSC-B '
UE/MS on MS C-B (GSM )
IDLE
Wa it for UE/MS on 3G_MSC-B' (G SM to UMTS Ho)
3GPP
Release 6
186
3GPP TS 23.009 V6.5.0 (2008-12)
Procedur e for Handove r in 3G_MSC-A Basic U MT S to GSM Hand over to MS C-B Crcuit Connec tion required
Sheet35(78)
14
MAP-P REPAREHA ND OVER req. [A-HO-REQ UEST] to MS C-B
Wait For Ack nowledgement from MSC-B (UMTS to GSM Ho)
MAP-PREPAREHAND OVER es p. [A-HO-REQU EST-ACK] from MSC-B
MAP-PREPARE HANDOVER r esp. [A-HO-FA ILUR E] from MSC-B
MAP-P REPAREHA NDOVER res p. [MAP ERROR] from MSC-B
Handover Number? Requested
N ot Requested
I_CONNECT (IAM) to MSC-B using Handover Number
W ait for Connection from MSC-B (UMTS to GSM Ho)
18
12
3GPP
Release 6
187
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet36(78)
Wait For Ack nowledgement from MSC-B (UMTS to GSM Ho)
ERRO R
from MSC-B
Iu-RELEASE-R EQ UE ST from RNS-A
Call Re lease
in 3G_MSC-A
to Network
Call Release
Release Resources i n RNS-A
to MS C-B
12
IDLE
3GPP
Release 6
188
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet37(78)
W ait for Connection from MSC-B (UMTS to GSM Ho)
From UE /MS or Netwo rk
Call Releas e
MAP-PA S req. [A-CLEAR-REQUEST ] from MSC-B
Call Release
to UE /MS and Network
Wait f or Connec ti on from MSC-B (UMTS to GSM Ho)
ERROR
from MSC-B or Network
Iu-Relocation Command to RNS-A
Set T303
to MSC-B in 3G_MSC-A
W ait for Comp letion on MS C-B (UMTS to GSM Ho)
12
IDLE
3GPP
Release 6
189
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet38(78)
W ait for Comp letion on MS C-B (UMTS to GSM Ho)
MAP-PAS req. [A-H O-DE TECT] from MSC-B
Reset T303
MA P-PAS re q. [A-CLEAR-REQUEST] from MSC-B
Iu-R ELEASE-REQ UE ST from RNS-A
Release Resourc es on RNS-A
Yes
W ait for UE/MS on MSC-B? No
Wai t f or Completion on MSC-B (UMTS to GSM Ho)
Call Release
to Ne twork and UE/MS
Release Resources on RNS-A
I_DIS CO NNECT (REL) to MS C-B
IDLE
Wai t f or C ompletion on MSC-B (UMTS to GSM Ho)
3GPP
Release 6
190
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet39(78)
Wai t f or Completion on MSC-B (UMTS to GSM Ho)
IuR ELO CATIONC ANCE L from RNS-A
I_DISCONNECT (RE L) from MSC-B
Expiry T3 03
Cal l Rel eas e
from Network
Res et T303
In 3G_MSC -A and to MSC-B
Forward q ueued me ssages for UE/MS vi a RNS-A
Wa it for Comp letion on MS C-B (UMTS to GSM Ho)
in 3G_MSC-A to MSC-B
f rom MS C-B
In 3G _MSC-A and to MS C-B
Release Resources RNS-A
W ait for Completion on MSC-B (UMT S to GS M Ho)
IDLE
3GPP
Release 6
191
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet40(78)
19
MAP-PREPARESUB SEQUENTHAND OVER req. [A-HO-REQU EST] from 3G_MSC-B Known MSC? Yes No Call on 3G_MSC-B (UTRAN)
MAP-P AS req. [A-CLEARREQUEST] from 3 G_MS C-B
Call Releas e
MAP-SEND-ENDS IG NAL resp. to 3G_MSC-B
No
from 3G_MSC-B
MSC-B '
Which MSC? 3G_MSC-A
Call Release
20
Known BSS? Yes
No
Res ourc es on new BSS? Yes
No
I_DISCONNECT ( RE L) to 3G_MS C-B
A -HANDOV ERREQ UEST to BSS-B
MAP-P REPARESUBSEQUENTHANDOVER resp. [A-HO-FAILURE] to 3G_MS C-B Set T301 No Circuit Connection? Yes Wait for Channel Allocation (UMTS to GSM Ho) UE/MS o n 3G_MSC-B (UTRAN) Call on 3G_MSC-B (UTRAN)
MAP-PRE PA RESUBSEQUENTHANDOVER resp. [MAP E RROR] to 3G_MSC-B
IDLE
3GPP
Release 6
192
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet41(78)
Wait for Channel Allocation (UMTS to GSM Ho)
A-H ANDOV ERREQUEST -ACK. from B SS-B
AHAND OVERFAILU RE from BSS-B
Expi ry T301
Call Re lease
Res et T301
Reset T301
Cancel Channel BSS-B
Queue Mess ages for UE /MS in 3G_MSC-A
MAP-PAS req. [A -CLEAR-REQUE ST] from 3G_MSC-B
MAP-SEN D-ENDSIGNAL resp to 3G_MS C-B
MAP-PRE PA RESUBSEQU ENTHAN DOV ER resp [A-HO REQUEST-ACK] to 3G_MSC-B No Circui t Conn ection? Yes
Release Reso urces in BSS-B
Set Up Handove r Device
Set T304
MAP-P REPARESUBSEQUENTHA NDOVER resp. [A-HO-FAILURE] to 3G_MS C-B Call on 3G_MSC-B (UTRAN)
Wai t for Acces s by UE /MS (UMTS to GSM Ho)
IDLE
3GPP
Release 6
193
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet42(78)
Wa it f or acces s by UE /MS (UMTS to GSM Ho)
A-HANDOVER DETECT from BS S-B
Expiry T304
Res et T304
No
Call Release
to Network
Connect Han dov er Device (option)
C onnec t H andover Device ( option)
Forward queued messages for UE /MS v ia BSS-B
in 3G_MSC-A to 3G_MS C-B
MA P-SEND-ENDSIGNAL resp. to 3G_MS C-B
I_ DISCONNECT (RE L) to 3G_MSC-B
No
Releas e Han dov er Device
I_DISCON NECT (REL) to 3G_MSC-B
Call in P rogress on 3G_MS C-A (G SM )
W ait for access by UE/MS (UMTS to GSM Ho)
IDLE
3GPP
Release 6
194
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet43(78)
W ait for acces s by UE/MS (UMTS to GSM Ho)
MAP-PAS req. [A-HOFAILU RE] from 3G_MSC-B
MAP-PAS req. [A -CLEARRE QUES T] from 3G_MSC-B
fro m Network
Call Releas e
Re lease Re sources on BSS-B
No
UE /MS on 3G_MS C-B (UTRAN)
Wait for access by UE /MS (UMTS to GSM Ho)
3GPP
Release 6
195
3GPP TS 23.009 V6.5.0 (2008-12)
Procedur e for Handove r in 3G_MSC-A Sub sequent UMTS to GSM Handover from 3G_MSC-B to MSC-B' Circ uit Connection required
Sheet44(78)
20
MAP-PREPARE-H ANDOVER req [A-HO-REQ UEST] to MSC-B'
W ai t for Ack from MSC-B' (UMTS to GSM Ho)
MAP-P REPAREHAND OVER res p.. [A-HO-RE QUES T-A CK] from MSC-B'
MAP-PRE PA REHANDOVER resp. [A-HO-FAILURE] from MSC -B'
Handover Number?
Not Requested
Requested
I_CONNECT (IAM) to MS C-B' using Han dov er Number
MAP-P REPARESUBSEQUENTHA NDOVER resp. [A-HO-FAILURE] to 3G_MS C-B Call on 3G_MSC-B (UTRAN)
W ait for Connection from MSC-B' (UMTS to GSM Ho)
21
3GPP
Release 6
196
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet45(78)
W ai t for Ack from MSC-B' (UMTS to GSM Ho)
ERRO R
from MSC-B'
from 3G_MSC-B or Network
ERRO R
Call Release
to MSC-B'
to MSC-B'
MAP-PAS req. [A-CLEAR- REQUEST] from 3G_MSC-B
MAP-S ENDEND-SIGNA L resp. to 3G_MS C- B
to MSC-B'
ERROR
MAP-P REPARESUBSEQUENTHA ND OVER res p. to 3G_MS C- B
I_DISC ONNECT (REL) to 3G_MSC-B
W ait for Ack fr om MSC-B' (UMT S to GSM Ho)
IDLE
3GPP
Release 6
197
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet46(78)
W ait for Connection from MSC-B' (UMTS to GSM Ho)
I_ COMPLETE (ACM) from MSC-B'
from MS C- B' or Network
ERRO R
from UE/MS or Network
Call Releas e
MAP-PAS req. [A -CLEARREQ UEST] from MSC -B'
MAP-PA S req. [A-CLEARREQ UEST] from 3G_MSC-B
W ait f or Connection f rom MSC-B' (UMTS to GSM Ho)
MAP-P REPARESUBSEQUENTHA ND OVER res p. [A-HO-RE QUES T-A CK] to 3G_MS C- B Cancel MAP Procedures Canc el MAP Procedures
to MSC -B'
to MSC-B'
to 3G_MSC-B and MSC-B'
Queue m es sages for UE/MS in 3G_MSC-A
I_ DISCONNECT (RE L) to MSC-B'
MAP -SENDE ND-SIGNAL resp to 3G_MSC-B
Call Release
to Network and UE /MS
Set T303
E RROR
M AP -PREPARES UBS EQ UE NT H ANDO VER resp. to 3G_MSC-B
I_DISCO NNECT (REL) to 3G_MSC-B and MSC-B'
W ait for Comp letion on MSC-B' (UMTS to GSM Ho)
Call o n 3G_MSC-B (UTRAN)
IDLE
3GPP
Release 6
198
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet47(78)
MAP-S ENDEND-SIG NA L req. [A-HO-CO MP LE TE] from MSC-B'
MAP-P AS req. [A-HO-DETECT] from MSC-B '
MAP-P AS req. [A-CLEARREQUEST] from 3G_MS C-B
Reset T303
I_ANSWER (ANM) from MSC-B'
MAP-P AS req. [A-CLEARREQUEST] from MSC-B'
Yes
Wait for access by UE/MS? No
Forward queu ed messages for UE/MS via MSC-B'
MAP-S ENDEND-SIG NA L resp. to 3G_MS C- B
to 3G_MSC-B and MSC -B'
I_DISC ONNE CT (REL) to 3G_MSC-B
Call Release
I_D ISCO NNECT (REL ) to 3G_MSC-B and MSC-B'
W ait for Completion fr om MSC-B' (UMT S to GSM Ho)
IDLE
3GPP
Release 6
199
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet48(78)
Expiry T303
MA P-PAS re q. [A-HO-FAILU RE] from 3G_MSC-B
from MSC-B'
From Network or 3G_MSC-B
Call Releas e
Res et T303
from 3G_MSC-B
I_DISCONNEC T (REL) to MSC-B '
to MSC-B'
I_DISCONNECT (REL) to 3 G_ MSC-B
I_ DISC ONNECT (REL) to MSC-B'
Yes
3G_MSC-B Connection? No
Yes
to MSC-B'
Forward queued mes sages for UE/MS via 3G_MSC-B
I_DISCONN ECT (REL) to MSC-B'
Call Re lease
to Netwo rk
IDLE
IDLE
Wait f or Co mpleti on on MSC-B ' (UMTS to GSM Ho)
3GPP
Release 6
200
3GPP TS 23.009 V6.5.0 (2008-12)
Procedur e for Handove r in 3G_MSC-A Basic U MT S to GSM Hand over to MS C-B no Circuit Connection requ ired
Sheet49(78)
18
Set T303
W ait for UE/MS on MS C-B (UMTS to GSM Ho)
Iu-RE LEA SE REQUEST from RNS-A
MAP-PAS req. [A-H O-DE TECT] from MSC-B
Reset T303
MAP-PAS req. [A -CLEARREQ UEST] from MSC -B
Re lease Re sources on RNS-A
Yes
W ait for UE/MS on MSC-B? No Cal l Release to Network and U E/MS
Forward queu ed messages for UE/MS vi a MS C-B
W ait for UE/MS o n MSC -B (UMTS to GSM Ho)
IDLE
3GPP
Release 6
201
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet50(78)
Wait for UE /MS on MSC -B (UMTS to GSM Ho)
Iu-RELO CATIONCANCEL from RNS-A
from MS C-B
Expiry T3 03
Call Re lease
from Network
Reset T303
In 3G _MSC-A and to MSC-B
Forward queued mes sages for UE/MS via RNS-A
in 3G_MSC-A to MS C-B
W ait for UE/MS o n MSC -B (UMTS to GSM Ho)
IDLE
3GPP
Release 6
202
3GPP TS 23.009 V6.5.0 (2008-12)
Procedur e for Handove r in 3G_MSC-A UE/MS Established on 3G_MSC- B without a Circ uit Connection
Sheet51(78)
UE /MS on 3G_MSC-B
From 3G_MS C-B
Call Releas e
M AP -PREPARES UBS EQ UE NTHAN DO VER req. [A-HO-REQUEST] from 3G_MSC-B MAPPREPAREHANDOVER re q. [NULL] [A-ASGREQ UE ST] to 3G_MSC-B
Call Release
to Network
Wai t F or Response from 3G_MSC-B (GS M to UM TS Ho)
19
IDLE
3GPP
Release 6
203
3GPP TS 23.009 V6.5.0 (2008-12)
Procedur e for Handove r in 3G_MSC-A Circ uit Connection Es tablis hment to MS C-B
Sheet52(78)
W ait For Response from MSC-B (UMTS to GSM Ho)
MAP-P REPAREHAND OVER res p. [Handover Number] [A -ASG-COMPLE TE] from MSC-B I_CONNECT (IAM) to MS C-B using Han dov er Number
Cal l Release
MAP-SEND END -SIGN AL res p. to MSC-B
W ait for Comp lete from MSC-B (UMTS to GSM Ho)
IDLE
3GPP
Release 6
204
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet53(78)
W ait For Response from MSC-B (UMTS to GSM Ho)
MAP-P REPAREHAND OVER res p. [M AP ERROR] from MSC-B
MAP -PREPAREHANDOVER resp. [A- ASG-FAILURE] from MS C-B
from MSC-B
MA P-PAS re q. [A-CLEAR-REQUEST] from MSC-B
Call Re lease
to Netwo rk
Failure
Failure
UE/MS on MSC-B (GSM)
UE/MS on MSC-B (GSM)
IDLE
3GPP
Release 6
205
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet54(78)
Call Re lease
I-ANSW ER (AN M) from MSC-B
from MS C- B
MAP-S EN DEN D-SIGNAL res p. to MSC-B
Succes s
F ailure
Call on MSC-B (GSM)
IDLE
3GPP
Release 6
206
3GPP TS 23.009 V6.5.0 (2008-12)
Procedur e for Handove r in 3G_MSC-A Sub sequent UMTS to GSM Handov er from 3G_MSC-B to MS C-B' no Circuit Connection requ ired.
Sheet55(78)
21
MAP-P REPARESUBSEQUENTHA ND OVER res p. [A-HO-RE QUES T-A CK] to 3G_MS C- B Queue M es sages for UE/MS in 3G_MSC-A
Set T303
W ait for UE/MS on MSC-B' (UMTS to GSM Ho)
MAP-S ENDEND-SIGNAL req [A-HO-CO MP LE TE] from MSC-B'
MAP-P AS req. [A-HO -DETECT] from MSC-B '
MAP-PAS req. [A -C LEARREQ UEST] from 3G_MSC-B
Reset T303
MAP-PAS req. [A -CLEARREQ UEST] from MSC -B'
Yes
W ait for acces s by UE/MS? No
Forward queu ed messages for UE/MS via MSC-B'
to 3G_MSC -B and MSC-B'
Call Re lease
W ait for UE/MS on MSC-B' (UMTS to GS M H o)
IDLE
3GPP
Release 6
207
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet56(78)
W ait for UE/MS on MSC-B' (UMTS to GSM Ho)
Expiry T303
MA P-PAS re q. [A-HOFAILU RE] from 3G_MSC-B
from MSC-B'
Cal l Rel eas e
from Network or 3G_MSC-B
Res et T303
from 3G_MSC-B
Forward queu ed messages for UE/MS via 3G_MSC-B
W ait for a ccess by UE/MS ? No
Yes
to MSC-B'
to MSC-B'
IDLE
Wa it for UE/MS on MSC-B' (UMTS to GSM Ho)
3GPP
Release 6
208
3GPP TS 23.009 V6.5.0 (2008-12)
Procedur e for Handove r in 3G_MSC-A Bas ic SRNS Rel ocation to 3G_MS C-B Crcuit Connec tion required
Sheet57(78)
17
MAP-P REPAREHA ND OVER req. [Iu-RLC-REQ UE ST ] to 3G_MS C- B
Wait For Ack nowledgement from 3G_MSC-B (SRNS Relocation)
MAP-PREPAREHAND OVER resp. [IU-RLC-REQUEST-ACK] from 3G_MSC-B
MAP-PREPARE HANDOVER r esp. [IU-RLC-FA ILURE] from 3G_MS C-B
MAP-P REPAREHA NDOVER res p. [MAP ERROR] from 3G_MSC-B
Handover Number? Requested
N ot Requested
I_CONNECT (IAM) to 3G_MSC-B using Handover Number
W ait for Connection from 3G_MSC-B (SRNS Relocation)
22
16
3GPP
Release 6
209
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet58(78)
W ait For Ack nowledgement from 3G_MSC-B (SRNS Relocation)
ERRO R
from 3G_MSC-B
Call Re lease
From UE or Network
in 3G_MSC-A
to Network
Call Release
to 3G_MS C-B
16
IDLE
3GPP
Release 6
210
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet59(78)
W ait for Connection from 3G_MSC-B (SRNS Relocation)
I_COMPLETE (AC M) from 3G_MSC-B
Iu -RELE ASEREQ UEST from RNS-A
From UE or Netwo rk
Call Releas e
MAP-PAS req. [IU-IREL-REQUEST ] from 3G_MS C-B
Call Release
to UE and Network
Wait f or Connec ti on from 3G_MSC-B (SRNS Relo cation)
ERROR
from 3G_MS C-B or Network
Iu-RELOCATION C OMMAND to RNS-A
Set T703
I_D ISCONNECT (REL) to 3G_MS C-B
W ait for Comp letion on 3G_MSC-B (SRNS Relocation)
16
IDLE
3GPP
Release 6
211
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet60(78)
W ait for Comp letion on 3G_MSC-B (SRNS Relocation)
MAP-S ENDEND-SIG NA L req. [I U-RLC-COMPLETE] from 3G_MSC-B
MAP-PAS req. [I U-RLC-DETECT] from 3G_MSC-B
Reset T703
MA P-PAS re q. [IU-IRE L-REQ UE ST] from 3G_MSC-B
Iu-R ELEASE-REQ UE ST from RNS-A
Release Resourc es on RNS-A
Yes
W ait for UE on 3G_MSC-B? No
Wai t f or Completion on 3G_MS C-B (SRNS Rel ocation)
Call Release
to Ne twork and UE
I_DIS CO NNECT (REL) t o 3G_MSC -B
IDLE
Wai t f or C ompletion on 3G_MS C-B (SRNS Rel ocation)
3GPP
Release 6
212
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet61(78)
Wai t f or Completion on 3G_MS C-B (SRNS Rel ocation)
IuR ELO CATIONC ANCE L from RNS-A
I_DISCONNECT (REL) from 3 G_ MSC-B
Expiry T7 03
Cal l Rel eas e
from Network
Res et T703
In 3G_MSC -A and to 3G_MSC -B
Forward q ueued messages for UE via RN S-A
Wa it for Comp letion on 3G_MS C-B ( SRNS Re location)
from 3G_MSC-B
I_DISCONNE CT (REL) to 3G_MSC-B
W ait for Completion on 3G_MSC-B (SRNS Reloc ation)
IDLE
3GPP
Release 6
213
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet62(78)
24
MAP-PREPARESUB SEQUENTHAND OVER req. [IU-RLCREQU EST] from 3G_MSC-B Known 3G_MSC? Yes No Call on 3G_MSC-B (UTRAN)
MAP-P AS req. [IU-IRELREQUEST] from 3 G_MS C-B
From UE or Network
Call Releas e
from 3G_MSC-B
3G_ MSC-B '
Which 3G_MSC? 3G_MSC-A
Call Release
to Network and UE
25
Known RNS? Yes
No
Res ourc es on new RNS? Yes
No
I_DISCONNECT ( RE L) to 3G_MS C-B
IuR ELO CATIONR EQ UEST to RNS-B
MAP-P REPARESUBSEQUENTHA NDOVER resp. [IU-RLC-FAILURE] to 3G_MS C-B Set T701 No Circuit Connection? Yes
MAP-PRE PA RESUBSEQUENTHANDOVER resp. [MAP E RROR] to 3G_MSC-B
Wait for Channel Allocation (SRNS Rel ocation)
UE o n 3G_MSC-B (UTRAN)
IDLE
3GPP
Release 6
214
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet63(78)
Wait for Channel Allocation (SRNS Relocation)
Iu-RELO CATIONREQUEST-ACK. from RNS-B
IuRELOCATIONFA ILURE from RNS-B
Expiry T7 01
Call Re lease
From UE or Network
Reset T701
Reset T701
Ca nc el Channel RNS-B
Queue Messages for UE in 3G_MSC-A
MAP-PAS req. [IU-I REL-REQ UEST] from 3G_MSC-B
MAP-S ENDENDSIGNAL resp to 3G_MS C-B
M AP -PR EPARES UBS EQ UE NT HANDOVER resp [IU-RLC-REQUESTA CK] to 3G_MSC-B No Circuit Connect ion? Yes
I_DISCON NE CT (REL) to 3G_MSC-B
Se t Up Handove r Dev ice
Set T704
MAP-PREPARESUB SEQU ENTHANDOVER resp. [IU-RLC-FAILURE] to 3 G_ MSC-B Call on 3G_MSC-B (UT RAN)
Wait for Acces s by UE (SRNS Relocation)
IDLE
3GPP
Release 6
215
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet64(78)
Wai t for access by UE (SRNS Rel ocation)
I u-RELO CAT IONCOMPLETE f rom RNS-B
Iu-RELOC ATIO N DETE CT from RNS-B
Expiry T704
Res et T704
No
Cal l Rel eas e
to Network
Connect Handover Device (option)
Conn ec t Handover Device (option)
Rel eas e Res ources on RNS-B
Forward queued messages for UE via RNS-B
in 3G_MS C-A to 3G_MSC-B
MAP-SEND-ENDS IGNAL resp. t o 3G_MSC-B
I_DISCO NNECT (REL) to 3G_MS C-B
No
Circuit Connection? Yes Rele as e Handover Device
I _DISC ONNECT (RE L) to 3G_MSC-B
Call in Progress on MSC-A (U TRAN )
W ait for ac cess by UE (SRNS Reloca tio n)
IDLE
3GPP
Release 6
216
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet65(78)
W ait for acces s by UE (SRNS Relocation)
MAP-PAS req. [I U-RLCFAILU RE] from 3G_MSC-B
MAP-PAS req. [I U-IRELRE QUES T] from 3G_MSC-B
fro m Network
Call Releas e
Iu-RELEASEREQUEST from RNS-B
Re lease Re sources on RNS-B
No
UE on 3G_MS C-B (UTRAN)
Wait for access by UE (SRNS Relocation)
3GPP
Release 6
217
3GPP TS 23.009 V6.5.0 (2008-12)
Procedur e for Handove r in 3G_MSC-A Sub sequent SRNS Relocation from 3G_MSC-B to 3G _MSC-B' Circ uit Connection required
Sheet66(78)
25
MAP-PREPARE-H ANDOVER req [IU-RL C-REQ UEST] to 3G_MSC- B'
W ai t for Ack from 3G_MSC-B' (SRNS Relocation)
MAP-P REPAREHAND OVER res p.. [I U-RLC-REQUEST-ACK] from 3G_MSC-B'
MAP-PRE PA REHANDOVER resp. [IU-RLC-FAILURE] from 3G_MSC-B '
Handover Number?
Not Requested
Requested
I_CONNECT (IAM) to 3G_MS C- B' using Han dov er Number
MAP-PREPARESUBSEQUENTHA NDOVER resp. [IU -RLC- FAILURE] to 3 G_MS C-B Call on 3G_MSC-B (UTRAN)
W ait for Connection from 3G_MSC-B' (SRNS Relocation)
26
3GPP
Release 6
218
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet67(78)
W ai t for Ack from 3G_MSC-B' (SRNS Relocation)
ERRO R
from 3G_MSC-B'
from 3G_MSC-B or Network
ERRO R
Call Release
From UE or Network
to 3G_MSC- B'
to 3G_MSC- B'
MAP-P AS req. [IU-IREL- REQUEST] from 3G_MS C-B
MAP-S ENDEND-SIGNA L resp. to 3G_MS C- B
to 3G_MSC-B'
ERROR
MAP-P REPARESUBSEQUENTHA ND OVER res p. to 3G_MS C- B
I_DISC ONNECT (REL) to 3G_MSC-B
W ait for Ack fr om 3G _MSC-B' (SRNS Reloc ation)
IDLE
3GPP
Release 6
219
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet68(78)
W ait for Connection from 3G_MSC-B' (SRNS Relocation)
I_COM PLE TE (ACM) from 3G_MSC-B'
fr om 3G_MSC-B' or Network
ERRO R
fro m UE or Network
Call Releas e
MAP-P AS req. [IU-IRE LREQUEST] from 3G_ MSC-B '
MAP-PA S req. [IU-IREL REQ UEST] from 3G_MSC-B
W ait f or Connection f rom 3G _MSC -B' (SRNS Relo cation)
MAP-PREPARE-SUBSEQ UENT-HA NDOVER res p. [I U-RLC-REQUEST-ACK] to 3G_MS C- B
to 3G _MSC-B'
to 3G_MSC-B'
to 3G_MSC-B and 3G _MSC-B'
Queue m es sages for UE in 3G_MSC-A
I_ DISCONNECT (RE L) to 3G_MSC-B'
MAP -SENDE ND-SIGNAL resp to 3G_MSC-B
Call Release
to Network and UE
Set T703
E RROR
M AP -PREPARES UBS EQ UE NT H ANDO VER resp. to 3G_MSC-B
I_D ISCO NNECT (REL) to 3G_MSC-B and 3G_MSC-B'
W ait for Comp letion on 3G _MSC-B' (SRNS Relocation)
IDLE
3GPP
Release 6
220
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet69(78)
MAP-SEND-ENDSIGNAL req. [I U-RLC-COMPLETE] from 3G_MSC-B'
MAP-P AS req. [IU-RLC-DETECT] from 3G _MSC-B'
MAP-P AS req. [IU-IRELREQUEST] from 3G_MS C-B
Reset T703
I_ANSWER (ANM) from 3G_MSC -B '
MA P-PAS req. [IU-IRELREQUEST] from 3G_MSC-B'
Yes
Wait for access by UE? No
Forward queu ed messages f or UE via 3G _MSC-B'
MAP-S ENDEND-SIG NA L resp. to 3G_MS C- B
to 3G_MS C-B and 3G _MSC-B'
I_DISC ONNE CT (REL) to 3G_MSC-B
to Network and UE
Call Release
I_DISCO NNECT (REL) to 3G_MSC-B and 3G _MSC-B'
W ait for Completion fr om 3G _MSC-B' (SRNS Reloc ation)
IDLE
3GPP
Release 6
221
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet70(78)
Expiry T703
MA P-PAS re q. [IU-RLCFAILU RE] from 3G_MSC-B
from 3G_MSC-B'
From Network or 3G_MSC-B
Call Releas e
Res et T703
from 3G_MSC-B
I_DISCONNEC T (REL) to 3G_ MSC-B '
to 3G_MSC- B'
I_ DISCONNECT (REL) to 3G_MS C-B
I_ DISC ONNECT (REL) to 3G_MSC-B '
W ait for a ccess by UE? No
Yes
3G_MSC-B Connection? No
Yes
to 3G_MSC-B'
Forward queued mes sages for UE via 3G_MSC-B
I_DISCONN ECT (REL) to 3G _MSC-B'
Call Re lease
to Netwo rk
IDLE
IDLE
Wait f or Co mpleti on on 3G _MSC -B ' (SRNS Relocation)
3GPP
Release 6
222
3GPP TS 23.009 V6.5.0 (2008-12)
Procedur e for Handove r in 3G_MSC-A Bas ic SRNS Rel ocation to 3G_MS C-B no Circuit Connection requ ired
Sheet71(78)
22
Set T703
Wait for UE on 3G_MSC-B (SRNS Relocation)
MAP-S ENDEND-SIG NA L req. [I U-RLC-COMPLETE] from 3G_MSC-B
Iu-RE LEA SE REQUEST from RNS-A
MAP-PAS req. [I U-RLC-DETECT] from 3G_MSC-B
Reset T703
MAP-PA S req. [IU-IRE LREQ UE ST] from 3G_MSC-B
Yes
W ait for UE on 3G_MSC-B? No Cal l Release to Network and UE
Forward queu ed messages f or UE via 3G_MSC-B
UE on 3G_MSC-B (UTRAN)
W ait for UE o n 3G_MSC-B (SRNS Relo cation)
IDLE
3GPP
Release 6
223
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet72(78)
Wait for UE on 3 G_MS C-B (SRNS Relocation)
Iu-RELO CATIONCANCEL from RNS-A
from 3G_ MSC-B
Expiry T7 03
Call Re lease
from Network
Reset T703
In 3G _MSC-A and to 3 G_MS C-B
Forward queued mes sages for UE via RNS-A
W ait for UE o n 3G_MSC-B (SRNS Relo cation)
IDLE
3GPP
Release 6
224
3GPP TS 23.009 V6.5.0 (2008-12)
Procedur e for Handove r in 3G_MSC-A UE Es tablished on 3G_MSC-B without a Circ uit Connection
Sheet73(78)
UE on 3G_MS C-B (UTRAN)
From 3G_MS C-B
From UE or Network
Call Releas e
M AP -PREPARES UBS EQ UE NTHAN DO VER req. [IU-RLCREQUEST] from 3G_MSC-B MAPPREPAREHANDOVER re q. [NULL] [IU-RASGREQ UE ST] to 3G_MSC-B
Call Release
to Network
Wai t F or Response from 3G_MSC-B (SRNS Rel ocation)
24
IDLE
3GPP
Release 6
225
3GPP TS 23.009 V6.5.0 (2008-12)
Procedure 3G_MSC_A_HO
Procedure for Handover in 3G_MSC-A Circuit Connection Establishment to 3G_MSC-B
Sheet74(78)
Wait For Response from 3G_MSC-B (SRNS Relocation)
MAP-PREPAREHANDOVER resp. [Handover Number] [IU-RASG-COMPLETE] from 3G_MSC-B I_CONNECT (IAM) to 3G_MSC-B using Handover Number
Call Release
From UE or Network
MAP-SENDEND-SIGNAL resp. to 3G_MSC-B
Wait for Complete from 3G_MSC-B (SRNS Relocation)
IDLE
MAP-PREPAREHANDOVER-SUBSEQUENT -HANDOVER req [IU-RLC-REQUEST] from 3G_MSC-B 24
3GPP
Release 6
226
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet75(78)
W ait For Response from 3G_MSC-B (SRNS Relocation)
MAP-P REPAREHAND OVER res p. [M AP ERROR] from 3G_MSC-B
MAP -PREPAREHANDOVER resp. [IU -RASGFA ILURE] from 3G_MS C- B
from 3G_MSC-B
Call Re lease
to Netwo rk
Failure
MAP-PA S req. [IU-IREL-REQUEST] fr om 3G_MSC-B
Failure
UE on 3 G_MS C-B (UTRAN)
UE on 3G_MSC-B (UT RAN)
IDLE
3GPP
Release 6
227
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet76(78)
W ait for Comp lete from 3G_MSC-B (SRNS Relocation)
I_COM PLE TE (ACM) from 3G_MSC-B
MAP-PAS req. [I U-IRELREQ UEST] from 3G_MSC-B
Call Re lease
From UE or Network
from 3G_MSC-B
MAP-S EN DEN D-SIGNAL res p. to 3G_MSC-B
Succes s
F ailure
W ait for Comp lete from 3G_MSC-B (SRNS Relocation)
IDLE
3GPP
Release 6
228
3GPP TS 23.009 V6.5.0 (2008-12)
Procedur e for Handove r in 3G_MSC-A Subsequent SRNS Relocation from 3G_MSC-B to 3G_MSC-B' no Circuit Connection requ ired.
Sheet77(78)
26
MAP-P REPARESUBSEQUENTHA ND OVER res p. [I U-RLC-REQUEST-ACK] to 3G_MS C- B Queue M es sages for UE in 3G_MSC-A
Set T703
W ait for UE on 3G _MSC-B' (SRNS Relocation)
MAP-S ENDEND-SIGNAL req [I U-RLC-COMPLETE] from 3G_MSC-B'
MAP-P AS req. [IU-RLC-DETECT] from 3G _MSC-B'
MAP-PAS req. [I U-IRELREQ UEST] from 3G_MSC-B
Reset T703
MAP-P AS req. [IU-IRE LREQUEST] from 3G_ MSC-B '
(Allowed once in thi s state)
Yes
W ait for acces s by UE? No
Forward queu ed messages f or UE via 3G _MSC-B'
to 3G_MSC- B and 3G_MSC-B'
to Network and UE
Call Re lease
W ait for UE on 3G_MSC-B' (SRNS Relocation)
IDLE
3GPP
Release 6
229
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet78(78)
Wait for UE on 3G _MSC-B' (SRNS Relocation)
Expiry T703
MA P-PAS re q. [IU-RLCFAILU RE] from 3G_MSC-B
from 3G_MSC-B'
Cal l Rel eas e
from Network or 3G_MSC-B
Res et T703
from 3G_MSC-B
Forward queu ed messages f or UE via 3G_MSC-B
W ait for a ccess by UE ? No
Yes
to 3G_MSC- B'
to 3G_MSC-B '
IDLE
Wait for UE on 3G_MSC-B' ( SRNS Re location)
3GPP
Release 6
230
3GPP TS 23.009 V6.5.0 (2008-12)
Procedure 3G_MSC_B_H O
Procedur es for Handov er in 3G_MSC-B
Sheet1 (54)
IDLE
MAP-P REPARE-HANDO VER req. [A-H O-REQ UEST] from 3G_MSC-A
MAP-PREP ARE -HAND OVER req. [IU-RLC-REQUEST] from 3G_ MSC-A
Type of handover? To UMTS No
To GSM
Known RNS? Yes Not Requested Han dover Number?
Requested
MA P-A LLOCATE HANDOVER-NUMBER req. to VLR
MAP-PREPARE HANDOV ER resp [A-HO-FAILURE] to MSC-A
Set T601
Iu-RELOCATIONREQUE ST to RNS-B
Wait f or Channel or Handover Number (G SM to UMTS Ho)
IDLE
Figure 44 (sheet 1 of 54): Handover control procedure in 3G_MSC-B
3GPP
Release 6
231
3GPP TS 23.009 V6.5.0 (2008-12)
Procedure 3G_MSC_B_HO
Procedures for Handover in 3G_ MSC-B
Sheet2(54)
Wait for Channel or Handover Number (GSM to UMTS Ho)
MAP-ALLOCATEHANDOVERNUMBER resp. from VLR
Reset T6 01
Wait fo r Ch annel Allocation Iu-LOCATIONREPORTINGCONTROL to RNS-B
Iu-RELO CATIONREQUEST-ACK from RNS-B
Hando ver Number?
Reque sted
Re set T601
No t Requested MAP-PREPAREHA NDOVER resp. [A-HO-REQUE ST-ACK] to MSC-A Wait fo r Ha ndo ver Number Allocation LOCATIONRE PORTING
No t Supported
Supporte d MAP-ALLOCATEHANDOVERNUMBER resp. from VLR Iu-LOCA TIONREPORTINGCONTROL to RNS-B
MAP-PREPAREHANDOVER resp. [A-HO-REQUEST- ACK] [Hand over Number] to MSC-A Set T6 04 Set T610
Wait fo r UE/MS on RNS-B (GSM to UMTS Ho)
Wait fo r Connection from MSC-A (GSM to UMTS Ho)
3GPP
Release 6
232
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet3 (54)
Wait for Channel or Handover Number (G SM to UMTS Ho)
Wait for Channel Allocati on (GSM to UMT S Ho)
Wa it for Chann el or Handover Number (GSM to UMTS Ho)
W ait for Hand ov er Number Allocati on (G SM to UMTS Ho)
Iu-RELOCATIONFAILU RE from RNS-B
Ex piry T601
Iu-Rel as eREQUEST from RNS-B
ERRO R
Indication from VLR
Re lease Re sources in RNS-B
MAP-P REPAREHA NDOVER res p. [M AP ERROR] to MS C-A
MAP-PRE PARE HANDOVER resp. [A-HO-FAILURE] to MSC-A
Ca nc el Ch annel on RN S-B
I DLE
IDLE
3GPP
Release 6
233
3GPP TS 23.009 V6.5.0 (2008-12)
Procedur es for Handov er in 3G_MSC-B Basic GSM to UMTS handover from MSC-A to 3G_MSC-B Circ uit Connection required
Sheet4 (54)
W ait for Connection from MSC-A (GSM to UMTS Ho)
Expiry T 610
Iu-RELEA SE REQUEST from RNS-B
Reset T610
To MSC-A in 3G_MSC-B
e.g. MAPABORT from MSC-A
MAP-PAS req. [A -CLEARRE QUES T] to MSC -A
To MSC-A in 3G_MSC-B
Set T604
I_COMPLETE (AC M) to MS C-A
Release Radio Resourc es on R NS-B
W ait for acces s by UE/MS on RNS-B (GSM to UMTS Ho)
IDLE
3GPP
Release 6
234
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet5 (54)
W ait for acces s by UE/MS on RNS-B (GSM to UMTS Ho)
Iu-RELOCATIONCOMPLE TE from RNS-B
Iu-RE LE ASEREQ UEST from RNS-B
Expiry T6 04
from MSC-A
MAP-P AS req [A -C LEARREQ UEST] to MSC-A
Res et T604
Reset T604
I_DISC ONNE CT (REL) to MSC-A
ANM Sent? No
Yes
I_DISCO NNECT (REL) from MSC-A
Release Res ources on RNS-B
I_ANS WER (ANM) to MS C-A
Iu-RELOCATIONDETECT from RNS-B
to MSC-A in 3G_MSC-B
I_ANSW ER (ANM ) to MSC-A
MAP-S ENDEND-SIG NA L req. [A-HO-CO MP LE TE] to MS C-A
MAP-P AS req [A-HO-DE TECT ] to MS C-A
Call in Progress on 3G_MSC-B (UTRAN)
IDLE
W ait for ac cess by UE /MS on RNS-B (G SM to UMTS Ho)
Wait for Disconnect (GS M to UMTS Ho)
3GPP
Release 6
235
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet6(54)
Ca ll in Progress on 3G_MSC-B (GSM)
Forward Messages to UE/MS
MAP-SENDEND-SIGNAL resp. from 3G_MSC-A
A-HO-PERFORMED from BSS
MAP-PAS req . [A-CLEAR-RE QUEST] to 3G_MSC-A
MAP-PAS req. [A-HO-PERFORMED] to 3G_MSC-A
Cance l MAP Procedures
Call in Pr ogress on 3G_ MSC-B (GSM)
Release Resou rces in BSS-A
I_DISCONNECT (REL) from 3G_MSC- A
from 3G_MSC-A
3G_MSC-A disconnected? No Wait for Disconnect (UMTS to GSM Ho)
Yes
Release Resou rces in BSS-A
A-HANDOVERREQUIRED fro m BSS-A
I_DISCONNECT (REL) to 3G_MSC-A
IDLE
Ca ll in Pr ogress on 3G_MSC-B (GSM)
IDLE
3GPP
Release 6
236
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet7 (54)
Known 3G_MSC? No
Yes
No
Handover allowed to Cell? Yes
Wh ich 3G _MSC?
3G_MSC-A/3G_ MSC-B '
3G_MSC-B
Known RN S? No Yes 1 Resources on RN S-B? No Yes No Send Reje ct? Yes
MAP-PRE PA RESUBSEQUENTHANDOVER req. [A-HO-REQUE ST ] to 3G_MSC-A
A-HANDOVERREJEC T to B SS-A
Set T 611
No
Call in P rogress on 3G_MS C-B (G SM )
UE/MS on 3 G_ MSC-B (GSM)
W ait for Response (G SM to UMTS Ho)
3GPP
Release 6
237
3GPP TS 23.009 V6.5.0 (2008-12)
Procedures for Handover in 3G_ MSC-B Handover fr om BSS-A to RNS-B on 3G_MSC-B
Sheet8(54)
Iu-RELOCATION-REQUEST to RNS-B
Set T6 01
Wait for Channel (GSM to UMTS Ho)
IuRELOCATIONREQUESTACK from RNS-B Re set T6 01
Expiry T601
IuRELOCATIONFAILURE from RNS-B
MAP- SEND-ENDSIG NAL resp. from 3G_ MSC-A
Re set T6 01
A-CLEAR- REQUEST from BSS-A
LOCATIONREPORTING
Supporte d
No t Supported
Iu-LOCATIONREPORTINGCONTROL to RNS-B
Queue Messages in 3G_MSC-B
Handover Command to UE/MS via BSS-A Release Resources on RNS-B Cancel MA P Procedures
MAP-PAS req [A-CLEA RREQUEST] to 3G_ MSC-A
Cancel Channel request on RNS-B
Set Up Handover Device
To 3 G_MSC-A in 3G_MSC-B
Set T6 02
Wait for access by UE/MS (GSM to UMTS Ho)
Wait fo r Disconnect (GSM to UMTS Ho)
3GPP
Release 6
238
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet9 (54)
Iu-RELO CATIOND ETECT fo rm RNS-B
A-HANDOVER FAILURE from BS S-A
Reset T602
MAP-PAS req. [A-HO-PERFORMED] to 3G_MS C- A
No
Circuit Connecti on? Yes
No
Co nnect Handov er De vice (Optional)
Connect Handover Device (Op tio nal )
Reset T602
Forward queu ed messages via RN S-B
Forward queued messages via BS S-A
Rel eas e Res ources in RNS-B
No
No
Circuit Con nec tion? Yes
Rel eas e Han dov er Dev ice
UE /MS on 3G_MS C-B (UTRAN)
W ait for access b y UE/MS (GSM to UMTS Ho)
UE/MS on 3G_MSC-B (G SM)
Call in P rogres s on 3G_MS C-B (G SM )
3GPP
Release 6
239
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet10(54)
Expiry T602
A -CLEARR EQ UEST from B SS-A
MAP-SEND-ENDSIGNAL resp. from 3G_MSC-A
Release Resources in RNS -B and B SS-A
Release Reso urces in RNS-B
Yes
W ait for access by UE /MS? No
MAP-PAS req. [A-CLEAR-REQUEST] to 3G_MS C- A
MA P-PAS re q. [A-CLEAR-REQUEST] to 3G_MSC-A
Release Resources in RNS-B and B SS-A
To 3G_MSC -A in 3G_MSC-B
T o 3G_MS C-A i n 3G_ MSC-B
I_DISC ONNE CT (REL) to 3G_MSC-A
IDLE
Wait for access by UE/MS (GSM to UMT S Ho)
W ait for Disconnect (GSM to UMTS Ho)
3GPP
Release 6
240
3GPP TS 23.009 V6.5.0 (2008-12)
Procedur es for Handov er in 3G_MSC-B Subsequent GS M to UMTS Handov er from 3G_MSC-B to 3G_MS C-A
Sheet11(54)
Wait for Re spons e (GS M to UMTS Ho)
MAP-PREPARE SUBSEQ UENTH ANDOVER resp. [A-HO -R EQUESTACK] from 3 G_ MSC-A Reset T611 Reset T611
M AP -PREPARES UBS EQ UE NT H ANDO VER resp. [A-HO -FA ILURE or MAP E RROR] from 3G_MSC-A
Expiry T6 11
A-CLEARREQUEST fro m BSS-A
MAP-PA S req. [A-CLEARREQUE ST ] to 3G_MSC-A
in 3G_MSC-B to 3G_MSC-A
Handover Command to UE /MS via B SS-A
Set T604
Release Res ources in BSS-A
Wait for Ack. from 3G_MSC-A (GS M to UMTS Ho)
Wait for Disconnect (GS M to UMTS Ho)
3GPP
Release 6
241
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet12(54)
Wai t for Ack. from 3G_MSC-A (GS M to UM TS Ho)
MAP-SENDENDSIGNAL res p. fro m 3G_MSC-A Res et T604
Ex pi ry T604
A -C LEARREQ UEST from B SS-A
A-HANDOVERFAILURE from BSS-A
Release Reso urces in BSS-A
MAP-PAS req. [A-CLE ARREQUEST] to 3G_MSC -A
Re set T604
Releas e Resources in BSS-A
to 3G_MSC -A in 3 G_ MSC-B
MAP-PAS req. [A-H O-FAILURE] to 3G_MS C-A
to 3G_MSC -A
No
Ci rcu it Connection? Yes
No
Wai t for Disconnect (GS M to UM TS Ho)
IDLE
Call in Progress on 3G_MSC-B (G SM )
UE /MS on 3G_MS C-B (GSM)
3GPP
Release 6
242
3GPP TS 23.009 V6.5.0 (2008-12)
Procedur es for Handov er in 3G_MSC-B Bas ic G SM to UMTS handover from MSC-A to 3G_MSC-B no Circuit Connectio n requ ired
Sheet13(54)
Wait for UE /MS on RNS-B (GS M to UMTS Ho)
Iu-RELEASEREQ UEST from RNS- B
Expiry T6 04
from MSC-A
Reset T604
MAP -PAS req [A-C LE ARREQUEST] to MSC-A
MAP-SENDEND-SIGNAL req. [A-HO COMPLETE] to MSC-A
Iu R ELO CATI OND ETECT from RNS-B
to MS C-A in 3G_MSC-B
MAP-PAS req. [A-HO-D ETECT] to MSC-A
W ait for UE/MS o n RNS-B (GSM to UMTS Ho)
IDLE
3GPP
Release 6
243
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet14(54)
Forward Mess ages to UE/MS
UE/MS on 3 G_MS C-B (GSM)
MA P-S ENDEND-SIG NA L resp. fr om MSC-A
A-HANDOVERREQ UIRED fro m BSS-A
MAP-PREPAREHANDOVER req. [NU LL] [A-ASG-R EQ UE ST] from 3G_MSC-A MAP-ALLOCATEHANDOV ER-NUMBER req. to VLR
Rel ease Res ources in BSS-B
A-ASSIGNMENTREQUEST to B SS-A
IDLE
Wa it f or Assignment or Handover Number (UMTS to GSM Ho)
3GPP
Release 6
244
3GPP TS 23.009 V6.5.0 (2008-12)
Procedur es for Handov er in 3G_MSC-B Circ uit Connection Es tablis hment on 3G_MS C-B
Sheet15(54)
Wai t for Assi gnment or Handover Numb er (GS M to UMTS Ho)
Iu-RAB-AS SIGNMENTRESPO NSE from RNS-B
MAP -ALLOCATEHANDOVERNUMBE R resp. from VL R
Wai t for Handover Number Alloc ation
MAP -ALLOCATEHANDOVERNU MBE R resp. from VL R
Iu-RA B-ASSIGNMENTRESPO NSE from RNS-B
MAP -PREPAREHANDOVER resp. [Handover Number] [A-ASG-CO MPLETE] to MSC-A Set T610
Wai t for Connect from MSC-A (GS M to UMTS Ho)
3GPP
Release 6
245
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet16(54)
Wai t for Assignme nt (GS M to UM TS Ho)
W ait for Handover Number Allocation (GSM to UMTS Ho)
Wa it for Assignment (G SM to UMTS Ho)
W ait for Assignment or Handover Number (GSM to UMTS Ho)
W ait for Assign ment o r Handov er Number (GSM to UMTS Ho)
W ait for Assignment or Handover Number (G SM to UMTS Ho)
Wait for Handover Number Allocation (GS M to UMTS Ho)
Iu -RABASSIGNME NTRE SP ONSE with unsucces sful result from RNS-B MAP-P REPAREHA ND OVER res p. [A-AS G-FA ILURE] to MS C-A
E RR OR
Indic ation from VLR
MA P-S ENDEND-SIGNA L resp. from MSC-A
M AP -PREPAREH ANDO VER resp. [MAP ERROR] to MSC-A
Iu-RELEASEREQUEST fro m RNS-B
MAP-PA S req. [A-CLEAR-REQUEST] to MS C-A
to MSC-A and VLR-B
to VLR-B
Release Res ources in RNS-B
IDLE
3GPP
Release 6
246
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet17(54)
W ait for Conn ec t from MSC-A (GSM to UMTS Ho)
Expiry T 610
Iu-RELEASE-REQ UE ST from RNS-A
Reset T610
MAP-P AS req. [A- CLEA R_REQUEST] to MSC-A
I_ COMPLETE (ACM) to MSC-A
Release Radio Resourc es on R NS-B
IDLE
3GPP
Release 6
247
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet18(54)
Wait for Co nnect from MSC-A (GS M to UMTS Ho)
I_DISC ONNECT (REL) from MSC-A
MAP-SENDEND-SIGNAL res p. from MS C-A
from MSC-A
Cance l MAP Procedure
Re lease Re sourc es on RNS-B
IDLE
IDLE
3GPP
Release 6
248
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet19(54)
Known BSS? Yes Not Requested Han dover Number?
No
Requested
MAP-PREPARE HANDOV ER resp [A-HO-FAILURE] to 3G_MSC-A
Set T401
A-HANDOVERREQUE ST to BS S-B
Wait f or Channel or Handover Number (UMTS to GSM Ho)
IDLE
3GPP
Release 6
249
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet20(54)
Wait for Channel or Handover Numb er (UMTS to GSM Ho)
A-HANDOV ERREQ UEST-ACK from B SS-B
Res et T401
Handover Number? Not Requested M AP -PREPAREHANDOVER resp. [ A- HO-REQUEST-ACK] t o 3G_MSC-A
Requested
W ait for Handover Number A ll oc ation
W ait for Channel All ocation
MAP-ALLOCATEHANDOVER NUMBE R resp. from VLR
Reset T401
MAP-PREPARE HANDO VE R resp. [A-HO-REQUEST -ACK] [Handov er Number ] to 3G_MSC-A Set T404 S et T410
Wai t for UE /MS on B SS-B (UMTS to GSM Ho)
W ait for Connection from 3G_MSC-A (UMTS to GSM Ho)
3GPP
Release 6
250
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet21(54)
Wait for Channel or Handover Number (UMTS to GSM Ho)
Wait for Channel Alloc ation (UMTS to GSM Ho)
Wa it for Chann el or Handover Number (U MTS to GS M Ho)
W ait for Hand ov er Number Allocati on (UMTS to GSM Ho)
A-HANDOVERFAILU RE from BSS-B
Ex piry T401
A_CLEARREQUEST from BS S-B
ERRO R
Indication from VLR
Re lease Re sources in BSS-B
Release Resources in B SS-B
MAP-P REPAREHA NDOVER res p. [M AP ERROR] to 3G_MS C-A
MAP-PRE PA REHANDOVER re sp. [A-HO-FAILURE] to 3G_MSC-A
Ca nc el Ch annel on BSS-B
I DLE
IDLE
3GPP
Release 6
251
3GPP TS 23.009 V6.5.0 (2008-12)
Procedur es for Handov er in 3G_MSC-B Bas ic U MTS to GSM han dov er from 3G_MSC-A to 3G_MSC-B Circ uit Connection required
Sheet22(54)
W ait for Connection from 3G_MSC-A (UMTS to GSM Ho)
I_CONNECT (IAM) from 3G_MSC-A (Us es Handover No.)
Expiry T 410
A-CLE AR-REQUE ST from B SS-B
Reset T410
To 3G_MSC-A in 3G_MSC-B
e.g. MAP-ABO RT from 3 G_ MSC-A
MAP-PAS req. [A -CLEARRE QUES T] to 3G_MS C-A
Set T404
I_COMPLETE (AC M) to 3G_MS C- A
Release Radio Resourc es on BS S-B
W ait for acces s by UE/MS on BSS-B (UMTS to GSM Ho)
IDLE
3GPP
Release 6
252
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet23(54)
W ait for acces s by UE/MS on BSS-B (UMTS to GSM Ho)
A -CLEAR REQ UEST from BS S-B
Expiry T4 04
fro m 3G_MSC-A
MAP-P AS req [A -C LEARREQ UEST] to MSC-A
Res et T404
Reset T404
I_DISCO NNECT (REL) to 3G_MSC-A
ANM Sent? No
Yes
I_DISCO NNECT (REL) from 3G_MSC-A
Release Res ources on BSS-B
I_ANS WER (ANM) to 3G_MS C- A
A-H ANDOVERDETECT from BSS-B
to 3G_MS C-A in 3G_MSC-B
I_ANSW ER (ANM ) to 3G_MSC-A
MAP-S ENDEND-SIG NA L req. [A-HO-CO MP LE TE] to 3G_MS C- A
Release Resources on B SS-B
MAP-P AS req [A-HO-DE TECT ] to 3G_MS C-A
Call in Progress on 3G_MSC-B (GSM )
IDLE
W ait for acce ss by UE/MS on BSS-B (UMTS to GSM Ho)
Wait for Disconnect (UMTS to GSM Ho)
3GPP
Release 6
253
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet24(54)
Ca ll in Progress on 3G_MSC-B (UTRAN)
Forward Messages to UE/MS
MAP-SENDEND-SIGNAL re sp. fro m 3G_MSC-A
Iu-RELE ASEREQUEST from RNS-A
Iu-LOCA TIONREPORT from RNS
MAP-PAS req. [A-CLEARREQUEST] to 3G_MSC-A
MAP-PAS req. [A-HOPERFORMED] to 3G_ MSC-A
Cance l MAP Procedures
Ca ll in Pr ogress on 3G_MSC-B (UTRAN)
Release Resou rces in RNS-A
from 3G_MSC-A
3G_MSC-A disconnected? No
Yes
Release Resou rces in RNS-A
Iu- RELOCATIONRE QUIRED fro m RNS-A
Wait for Disconnect (GSM to UMTS Ho)
I_DISCONNECT (REL) to 3G_MSC-A
IDLE
Ca ll in Pr ogress on 3G_MSC-B (UTRAN)
IDLE
3GPP
Release 6
254
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet25(54)
Known MSC? No
Yes
Handover allowed to Cell? No Yes
Wh ich 3G _MSC? MS C- B
MS C-A/MSC-B'
Known BSS? No Yes 7 Resources on BSS-B? No Yes No Send Reje ct?
MAP-PRE PA RESUBSEQUENTHANDOVER req. [A-HO-REQUE ST ] to MS C-A
Yes Iu-RELOCATIONPREPARATIONFAILURE to RNS-A
Set T 411
No
Call in P rogress on 3G_MS C-B (UT RAN)
UE/MS on 3 G_ MSC-B (UTRAN)
W ait for Response (UMTS t o GSM Ho)
3GPP
Release 6
255
3GPP TS 23.009 V6.5.0 (2008-12)
Procedur es for Handov er in 3G_MSC-B UMTS to GS M Handover fr om RN S-A to BSS-B on MSC-B
Sheet26(54)
A-HANDOV ER-REQUEST to BS S-B
Set T401
Wait for Channel (UMTS to GSM Ho)
A-HANDOVERRE QUES TACK from BSS-B
Ex pi ry T401
A-H ANDOVERFAILURE from BS S-B
MAP-SEND-ENDS IG NAL resp. from 3G_MSC-A
Reset T401
Reset T401
Iu-RELEASE-REQ UEST from RNS-A
Queue Messages i n MSC-B
MAP-PAS req [A-CLEARREQ UE ST] to 3G_MSC-A
Cancel Channel request on B SS-B
Han dov er Command to UE/MS via Iu-RELOCATION-COMMAND to RNS-A
Release Resourc es on BS S-B
To 3G_MSC-A in MSC-B
Release Res ources on RNS-A
Set T402
3GPP
Release 6
256
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet27(54)
A -HAND OV ERD ETECT form B SS-B
Iu-RELOCATION CANCEL from RNS-A
Reset T402
MAP-PAS req. [A-HO-PERFORMED] to 3G_MS C- A
No
Circuit Connecti on? Yes
No
Co nnect Handov er De vice (Optional)
Connect Handover Device (Op tio nal )
Reset T402
Forward queu ed messages via BS S-B
Forward queued messages via RNS-A
Re lease Re sources in RNS-A
Rel eas e Res ources in BSS-B
No
No
Circuit Con nec tion? Yes
Rel eas e Han dov er Dev ice
Call in Progress on 3G_MSC-B (GSM )
UE /MS on 3G_MS C-B (GSM)
W ait for access b y UE/MS (UMTS to GSM Ho)
Call in P rogres s on 3G_MS C-B (UT RAN)
3GPP
Release 6
257
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet28(54)
Expiry T402
Release Resources in BSS -B and RNS-A
Release Reso urces in BSS-B
No
W ait for acc ess by UE/MS? Yes
MAP-PAS req. [A -CLEARREQ UEST] to 3G_MS C- A
MAP-PAS req. [A-CLE ARREQUEST] to 3G_MSC -A
Release Resources in BSS -B and RNS-A
To 3G_MS C-A in 3 G_ MSC-B
IDLE
Wait for ac cess by U E/MS (UMTS to GSM Ho)
W ait for Dis connect (UMTS to GSM Ho)
W ait for Disc onnec t (UMTS to GSM Ho)
3GPP
Release 6
258
3GPP TS 23.009 V6.5.0 (2008-12)
Procedur es for Handov er in 3G_MSC-B Sub sequent UMTS to GSM Handover from 3G_MSC-B to MS C-A
Sheet29(54)
Wait for Re spons e (UMTS to GSM Ho)
MAP-PREPARE SUBSEQ UENTH ANDOVER resp. [A-HO -R EQUESTACK] from MSC-A Reset T411 Reset T411
M AP -PREPARES UBS EQ UE NT H ANDO VER resp. [A-HO -FA ILURE or MAP E RROR] from MS C-A
Expiry T4 11
Iu-RELEASEREQUEST fro m RNS-A
MAP-PAS req. [A-CLEARREQUE ST ] to MS C-A MAP-SEND-ENDSIGNAL resp. from MSC-A in 3G_MSC-B to MS C-A Cancel MAP Procedures
Release Resources in B SS-B
Relocati on Command to RNS-A
Set T404
Wait for Ack. from MSC-A (UMTS to GSM Ho)
3GPP
Release 6
259
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet30(54)
Wai t for Ack. from MSC-A (UMTS to GSM Ho)
MAP-SENDENDSIGNAL res p. from MSC-A
Ex pi ry T404
Iu-RELOCATIONCANCEL from RNS- A
Res et T404
Release Reso urces in RNS-A
MAP-PAS req. [A-CLE ARREQUEST] to MSC-A
Re set T404
Releas e Resources in RNS-A
to MSC-A in 3 G_ MSC-B
MAP-PAS req. [A-H O-FAILURE] to MS C-A
to MSC-A
No
No
Wai t for Disconnect (UMTS to GSM Ho)
IDLE
Call in Progress on 3G_MSC-B (UT RAN)
UE /MS on 3G_MS C-B (UT RAN)
3GPP
Release 6
260
3GPP TS 23.009 V6.5.0 (2008-12)
Procedur es for Handov er in 3G_MSC-B Basic UMT S to GSM handover from 3G _MSC-A to 3G_MSC-B no Circuit Connectio n requ ired
Sheet31(54)
Wait for UE /MS on B SS-B (UMTS to GSM Ho)
A -HANDOV ERCOMPLETE from B SS-B
A-CLEARREQ UE ST from B SS-B
Expiry T4 04
fro m 3G_MSC-A
Reset T404
MAP-PAS req [A-CLEARREQUEST] to 3G_MSC-A
MA P-SENDEND-SIG NAL req. [A-HO-CO MP LET E] to 3 G_MS C-A
A -HAND OV ERD ETECT from B SS-B
to 3G_MSC-A in 3G_MSC-B
MAP-PAS req. [A-HO-D ETECT] to 3G_MSC-A
Releas e Resources on BSS-B
UE/MS on 3 G_MS C-B (GSM)
W ait for UE/MS o n BS S-B (UMTS to GSM Ho)
IDLE
3GPP
Release 6
261
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet32(54)
Fo rward Messag es to UE/MS
UE /MS on 3G_MSC-B (UTRAN)
MAP-SENDE ND-SIGNAL r esp. from 3G_MSC-A
IuRELOCATIONREQUIRED from RNS-A
MAP-PREPAREHANDOVER req . [NULL] [A-ASG-REQUEST] from MSC-A MAP-ALLOCA TEHANDOVER- NUMBER req. to VLR
Release Resou rces in RNS-B
Iu- RAB-ASSIGNEMENTREQUEST to RNS-A
IDLE
Wait fo r Assignment or Handover Number (GSM to UMTS Ho)
Iu-LOCA TIONREPORT from RNS
MAP-PAS req. [A-HOPERFORMED] to 3G_ MSC-A
UE /MS on 3G_MSC-B (UTRAN)
3GPP
Release 6
262
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet33(54)
Wait for Assignme nt or Handover Numb er (UMTS to GSM Ho)
A-AS SIGNMENTCOMPL ETE from BSS-B
MAP -ALLOCATEH ANDOVERN UMBER resp. from VLR
Wait for Handover Number Allocation
W ait for As signment
MAP -ALLOCATEHANDOVERNUMBER resp. from VLR
A-ASSIGNMENTC OMPLETE from B SS-A
MAP-PREPAREHANDOVER resp. [Handover Number] [A-ASG-CO MP LETE] to 3G_MSC-A Set T410
Wait for Co nnect from 3G_MSC-A (UMTS to GSM Ho)
3GPP
Release 6
263
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet34(54)
Wai t for Assignme nt (UMTS to GSM Ho)
W ait for Handover Number Allocation (UMT S to GS M Ho)
Wa it for Assignment (UMTS to GSM Ho)
W ait for Assignment or Handover Number (UMTS to GSM Ho)
W ait for Assign ment o r Handov er Number (UMTS to GSM Ho)
W ait for Assignment or Handover Number (UMTS t o GSM Ho)
Wait for Handover Number Allocation (UMTS to GSM Ho)
A-ASSIGNMENTFAILU RE from BSS-A
E RR OR
MA P-S ENDEND-SIGNA L resp. from 3G_MSC-A
MAP-P REPAREHA ND OVER res p. [A-AS G-FA ILURE] to 3G_MS C- A
M AP -PREPAREH ANDO VER resp. [MAP ERROR] to 3G_MSC-A
A-CLEAR-REQUEST fro m BSS-B
MAP-PA S req. [A-CLEAR-REQUEST] to 3G_MSC-A
to 3G_MSC-A and VLR-B
to VLR-B
Release Res ources in BSS-B
UE/MS on 3G_MSC-B (GSM )
IDLE
3GPP
Release 6
264
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet35(54)
W ait for Conn ec t from 3G_MSC-A (UMTS to GSM Ho)
Expiry T 410
A-CLEAR-REQ UEST from BSS-A
Reset T410
MAP-P AS req. [A- CLEA R_REQUEST] to 3G_MSC-A
I_ COMPLETE (ACM) to 3G_MSC-A
Release Radio Resourc es on BS S-B
Call on 3G_MSC-B (GSM )
IDLE
3GPP
Release 6
265
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet36(54)
Wai t for Connect from 3G_MSC-A (UMTS to GSM Ho)
I_DISCONNECT (REL) from 3 G_MS C-A
MAP-SENDEND-SIGNAL resp. from 3G_MS C-A
from 3G_MS C- A
Release Resources on BS S-B
UE/MS on 3 G_ MSC-B (GSM)
IDLE
IDLE
3GPP
Release 6
266
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet37(54)
Known RNS? Yes Not Requested Han dover Number?
No
Requested
MAP-PREPARE HANDOV ER resp [IU -RLC-FA ILU RE] To 3G_MSC-A
Set T801
Iu-RELOCATIONREQUE ST to RNS-B
Wait f or Channel or Handover Number (SRNS Re location)
IDLE
3GPP
Release 6
267
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet38(54)
Wait for Channel or Handover Numbe r (SRNS Relocation)
Iu-REL OCATIONREQUEST -ACK from RNS-B
Res et T801
Handover Number? Not Requested
Requested
MAP-PREPAREHA NDOVER resp. [IU-RLC-REQUEST -ACK] to 3 G_MSC-A
W ait for Handover Number A llocati on
Wait for Channel All ocation (SRNS Relocation)
Reset T801
MAP-PREPARE HANDO VE R r esp. [IU-RLC-REQUEST-ACK] [Handover Number] to 3G_MSC-A Set T804 S et T 810
Wait for UE on RNS-B (SRNS Relocation)
W ait for Connection fr om 3G_MS C-A (SRNS Reloc ation)
3GPP
Release 6
268
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet39(54)
Wait for Channel or Handover Number (SRNS Re location)
Wait for Channel Alloc ation (SRNS Relo cation)
Wa it for Chann el or Handover Number (SRNS Reloc ation)
W ait for Hand ov er Number Allocati on (SRNS Relocation)
Iu-RELOCATIONFAILU RE from RNS-B
Ex piry T801
Iu-RE LEA SE REQUEST from RNS-B
ERRO R
Indication from VLR
Re lease Re sources in RNS-B
MAP-P REPAREHA NDOVER res p. [M AP ERROR] to 3G_MS C-A
MAP-PRE PA REHANDOVER re sp. [IU-R LC-FAI LURE] to 3G_MSC-A
Ca nc el Ch annel on RN S-B
I DLE
IDLE
3GPP
Release 6
269
3GPP TS 23.009 V6.5.0 (2008-12)
Procedur es for Handov er in 3G_MSC-B Bas ic S RNS R el ocation from 3G_MSC-A to 3G_MSC -B Circ uit Connection required
Sheet40(54)
W ait for Connection from 3G_MSC-A (SRNS Relocation)
Expiry T 810
Iu-RELEA SE REQUEST from RNS-B
Reset T810
e.g. MAP-ABORT from 3G_MSC-A
MAP-PAS req. [IU-IRELRE QUES T] to 3G_MS C-A
Set T804
I_COMPLETE (AC M) to 3G_MS C- A
Release Radio Resources on R NS-B
W ait for acces s by UE on RNS-B (SRNS Relocation)
IDLE
3GPP
Release 6
270
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet41(54)
Iu-RE LE ASEREQ UEST from RNS-B
Expiry T8 04
fro m 3G_MSC-A
MAP-P AS req [IU_IRELREQ UEST] to 3G_MS C-A
Res et T804
Reset T804
I_DISCO NNECT (REL) to 3G_MSC-A
ANM Sent? No
Yes
I_DISCO NNECT (REL) from 3G_MSC-A
I_ANS WER (ANM) to 3G_MS C- A
Iu-RELO CATIONDETECT from RNS-B
I _AN SW ER (ANM ) t o 3G_MSC-A
MAP-S ENDEND-SIG NA L req. [IU_ RLC-COMPLETE] to 3G_MS C- A
MAP-PAS req [IU-R LC-DE TECT] to 3G_MSC-A
IDLE
Wait for Disconnect (SRNS Relocation)
3GPP
Release 6
271
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet42(54)
Forward Mess ages to UE
MAP-S ENDEND-SIG NA L resp. from 3G_MSC-A
Iu-RELEASE-REQUEST from RNS-A
MAP-PAS req. [IU-IREL-REQUEST] to 3G_MSC-A
Releas Resources in RNS-A
I_DISCONNECT (R EL) from 3G_MSC -A
from 3G_MSC-A
3G_MSC-A dis connected? No
Yes
Iu-RELOCATIONREQUIRED from RNS-A
W ait for Disconnect
I_DIS CONN ECT (REL) to 3G_MSC-A
I_ DISC ONNECT (REL) from 3 G_ MSC-A
IDLE
IDLE
12
3GPP
Release 6
272
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet43(54)
12
Known 3G_MSC? No
Yes
Wh ich 3G _MSC? MS C-B
3G_MS C-A/3G_MSC-B'
Known RNS? No Yes 11 Resources on RNS-B? No Yes No Send Reject?
MAP-P REPA RESUBSEQUENTHANDOVER req. [IU-RLC-REQ UE ST] to 3G_MSC-A
Yes Iu-R ELOCATIONPREPARA TION-F AIL URE to RNS-A
Set T8 11
Circuit C on nec tion? Yes
No
C al l i n P rogres s on 3G_MS C-B (UTRAN)
UE on 3G_MSC -B (UTRAN)
13
W ait for Response (SRNS Relocation)
3GPP
Release 6
273
3GPP TS 23.009 V6.5.0 (2008-12)
Procedures for Handover in 3G_ MSC-B SRNS Rel ocation from RNS-A to RNS-B o n 3G_MSC-B
Sheet44(54)
13
Iu-RELOCATION-REQUEST to RNS-B
Set T8 01
Wait for Channel (SRNS Relocation)
IuRELOCATIONREQUEST-ACK from RNS-B Re set T8 01
Expiry T801
Iu-RELO CATIONFAILURE from RNS-B
MAP-SENDEND-SIGNAL resp. fro m 3G_ MSC-A
Re set T8 01
Iu-RELE ASE-REQUEST from RNS-A
Queue Messages in 3G_MSC-B MAP-PAS req [IU-IRELREQUEST] to 3G_ MSC-A Cancel Ch annel request on RNS-B
No t supported Loca tion Reporting Supported Iu-LOCATION REPORTING CONTROL to RNS-B Release Resources on RNS-B Cancel MA P Procedures
To 3 G_MSC-A in 3G_MSC-B
Relocation Command to RNS-A
Set Up Handover Device
Set T8 02 11 Wait for access by UE (SRNS Relocation)
Wait fo r Disconnect (SRNS Relocation)
3GPP
Release 6
274
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet45(54)
Wait fo r access by UE (SRNS Relocation)
IuRELOCATIONCOMPLETE from RNS-B Re set T8 02
IuRELOCATIONDETECT form RNS-B
IuRELOCATION CANCEL from RNS-A
Ha ve security alg or it hms been chan ged? Yes Protocol on E-in terface BSSMAP MAP-PAS req. [A-HOPERFORMED] to 3G_MSC-A
No
RANAP MAP-PAS req. [Iu -L OC-REPORT] to 3G_ MSC-A
Ci rcuit Co nne cti on? Yes Connect Handover Device (O ptional)
No Ci rcuit Co nne cti on? Yes No
Re set T802
Forward queued me ssage s via RNS-A
Fo rward queued message s via RNS-B Release Resou rces in RNS-A No
Connect Handover Device (Optional)
Release Resou rces in RNS-B
No
Ci rcuit Co nnecti on ? Yes
Ci rcuit Co nne cti on? Yes Release Handover Device Ca ll in Pr ogress on 3G_MSC-B (UTRAN)
Wait fo r access by UE (SRNS Relocation)
UE on 3G_ MSC-B (UTRAN)
Ca ll in Pr ogress on 3G_ MSC-B (UTRAN)
3GPP
Release 6
275
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet46(54)
W ait for acces s by UE (SRNS Relocation)
Expiry T802
Iu -RELE ASER EQ UEST from RNS-A
Release Resources in RNS -B and RNS-A
Release Reso urces in RNS-B
Yes
W ait for access by UE? No
MAP-PAS req. [IU-IREL-REQUEST] to 3G_MS C- A
MAP-PA S req. [IU-IREL-REQUEST] to 3G_MSC-A
Release Resources in RNS -B and RNS-A
T o 3G_MS C-A i n 3G_ MSC-B
IDLE
Wait for access by U E (SRNS Relo cation)
W ait for Disconnect (SRNS Reloca tio n)
3GPP
Release 6
276
3GPP TS 23.009 V6.5.0 (2008-12)
Procedur es for Handov er in 3G_MSC-B Subsequent SRNS Relocation from 3G_MSC-B to 3G_MSC-A
Sheet47(54)
Wait for Re spons e (SRNS Relocation)
MAP-PREPARE S UBS EQUENTHANDO VE R resp. [IU-RLCREQUESTA CK] fr om 3G_MS C-A
M AP -PREPARES UBS EQ UE NT H ANDO VER resp. [IU-RLC-F AILURE or MAP E RROR] from 3G_MSC-A Reset T811 Reset T811
Expiry T8 11
MAP-PAS req. [IU-IREL REQUE ST ] to 3G_MSC-A MAP-SEND-ENDSIGNAL resp. from 3G_MSC-A in 3G_MSC-B to 3G_MSC-A Cancel MAP Procedures
Relocati on Command to RNS-A
Set T804
Wait for Ack. from 3G_MSC-A (SRNS Relocation)
11
Wait for Disconnect (SRNS Relocation)
3GPP
Release 6
277
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet48(54)
Wai t for Ack. from 3G_MSC-A (SRNS Rel ocation)
MAP-SENDENDSIGNAL res p. fro m 3G_MSC-A Res et T804
Ex pi ry T804
IuRELOCAT IONCANCEL from RNS- A
Release Reso urces in RNS-A
MAP-PAS req. [IU-IRELREQUEST] to 3G_MSC -A
Re set T804
Releas e Resources in RNS-A
to 3G_MSC -A in 3 G_ MSC-B
MAP-PAS req. [I U-RLCFAILURE] to 3G_MS C-A
to 3G_MSC -A
No
No
Wai t for Disconnect (SRNS Rel ocation)
IDLE
Call in Progress on 3G_MSC-B (UT RAN)
UE on 3G_MS C-B (UT RAN)
3GPP
Release 6
278
3GPP TS 23.009 V6.5.0 (2008-12)
Procedur es for Handov er in 3G_MSC-B Bas ic S RNS R el ocation from 3G_MSC-A to 3G_MSC -B no Circuit Connectio n requ ired
Sheet49(54)
Wait for UE on RNS-B (SRNS Relocation)
Iu-RELEASEREQ UEST from RNS- B
Expiry T8 04
fro m 3G_MSC-A
Reset T804
MAP -PAS req [IU-IRELREQUEST] to 3G_MSC-A
MAP-SENDEND-SIGNAL req. [IU-RLCCOMPLETE] to 3G_MSC-A
IuRELO CATIONDET ECT from RNS-B
MAP-PAS req. [IU -RLC-DETECT] to 3G_MSC-A
W ait for UE o n RNS-B (SRNS Reloc ation)
IDLE
3GPP
Release 6
279
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet50(54)
Forward Mess ages to UE
MA P-S ENDEND-SIG NA L resp. fr om 3G_MSC-A
Iu-RELOCATIONREQ UIRED from RN S-A
MAP-PREPARE HANDO VE R req. [N ULL] [IU-RASG-REQUEST] fr om 3 G_MS C-A MAP-ALL OCATEH ANDOV ER-NUMBER req. to VLR
Rel ease R esources in RNS-B
Iu-R AB-A SSIGNE MENTREQUEST to RNS-A
IDLE
12
Wai t fo r Assignment or Handover Number (SRNS Rel ocation)
3GPP
Release 6
280
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet51(54)
Wai t for Assi gnment or Handover Numb er (SRNS Rel ocation)
Iu-RAB-AS SIGNMENTRESPO NSE from RNS-A
Wai t for Handover Number Allocation
W ait for Assignment (SRNS Reloc ation)
MAP -ALLOCATEHANDOVERNU MBE R resp. from VL R
Iu-RA B-ASSIGNMENTRESPONSE from RNS-A
MAP -PREPAREHANDOVER resp. [Handover Number] [IU-RASG -COMPLETE] to 3G_MSC-A Set T810
Wai t for Connect from 3G_MSC-A (SRNS Rel ocation)
3GPP
Release 6
281
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet52(54)
Wai t for Assignme nt (SRNS Rel ocation)
W ait for Handover Number Allocation (SRNS Reloc ation)
Wa it for Assignment ( SRNS Re location)
W ait for Assignment or Handover Number (SRNS Relocation)
W ait for Assign ment o r Handov er Number (SRNS Relo cation)
W ait for Assignment or Handover Number ( SRNS Relocation )
Wait for Handover Number Allocation (SRNS Relocation)
Iu -RABASSIGNME NTRE SP ONSE with Unsuccessful result from RNS-B MAP-P REPAREHA ND OVER res p. [IU-RA SGRESPONSE] to 3G_MS C- A
E RR OR
MA P-S ENDEND-SIGNA L resp. from 3G_MSC-A
M AP -PREPAREH ANDO VER resp. [MAP ERROR] to 3G_MSC-A
MAP-PA S req. [IU-IREL-REQUEST] to 3G_MSC-A
to 3G_MSC-A and VLR-B
to VLR-B
IDLE
3GPP
Release 6
282
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet53(54)
W ait for Conn ec t from 3G_MSC-A (SRNS Relocation)
Expiry T 810
Iu-RELEASE-REQ UE ST from RNS-A
Reset T810
MAP-P AS req. [IU -IREL-REQUEST] to 3G_MSC-A
I_ COMPLETE (ACM) to 3G_MSC-A
Release Radio Resourc es on R NS-A
IDLE
3GPP
Release 6
283
3GPP TS 23.009 V6.5.0 (2008-12)
Sheet54(54)
Wai t for Connect from 3G_MSC-A (SRNS Rel ocation)
I_DISCONNECT (REL) from 3 G_MS C-A
MAP-SENDEND-SIGNAL resp. from 3G_MS C-A
from 3G_MS C- A
UE on 3 G_ MSC-B (UTRAN)
IDLE
IDLE
3GPP
Release 6
284
3GPP TS 23.009 V6.5.0 (2008-12)
Annex A (informative): Change history

Change history
TSG CN# Spec Version Apr 1999 GSM 03.09 6.0.0 CN#03 CN#06 CN#7 CN#7 CN#7 CN#7 CN#7 CN#7 23.009 23.009 23.009 23.009 23.009 23.009 23.009 23.009 CR Rel N_Ver Subject Comment Transferred to 3GPP CN1 Approved at CN#03
3.0.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0 3.1.0
3.0.0 CR001r2 R99 3.1.0 CR003 CR004 CR005 CR006 CR007 R99 3.2.0 R99 3.2.0 R99 3.2.0 R99 3.2.0 R99 3.2.0
Introduction of UMTS functionalities in 23.009 Functional requirements for the use of RANAP over the E i/f SDLs SDLs Introduction of RANAP for intraUMTS inter-MSC relocation Clarifications of 3G_MSC-A and 3G_MSC-B roles Transcoder handling in the CN at inter-system handover and relocation Missing SDLs re-inserted by SDLs MCC for Figures 41 - 42 (GSM Handover control procedure in MSC-A and MSC-B)
CR008r2 R99 3.2.0
15/05/00
23.009
3.2.0
R99 3.2.1
TSG# NP-08 NP-08 NP-08 NP-09 NP-10 NP-10
NP-Tdoc NP-000278 NP-000270 NP-000270 NP-000444 NP-000671 NP-000671
WG Tdoc N1-000638 N1-000607 N1-000608 N1-000922 N1-001174 N1-001175
Spec 23.009 23.009 23.009 23.009 23.009 23.009
CR 002 009 010 012 013 014
Rev Rel 4 R99 R99 R99 1 R99 R99 R99
C Old at vers B 3.2.1 C C F F F 3.2.1 3.2.1 3.3.0 3.4.0 3.4.0
New ver 3.3.0 3.3.0 3.3.0 3.4.0 3.5.0 3.5.0
Title CR to 23.009 on Handover scenario for Multicall Clean-up of 3G_MSC-A_HO SDLs Clean-up of 3G_MSC-B_HO SDLs Correction to transcoder handling for R99 GSM to UMTS Handover: Directed Retry GSM to UMTS Handover: MAP parameter Target Cell ID GSM to UMTS Handover: Location Reporting in 3G MSC B Subsequent Handover procedure corrections Missing Subsequent Handover scenarios Reference clean-up ndication of Intra-MSC Intersystem handover from 3G_MSC-B to MSCA/3G_MSC-A UMTS to GSM handover: Directed Retry GSM to UMTS Handover: Location Reporting in 3G_MSC-B GSM to UMTS handover: addition of MAP parameter Target RNC ID Directed Retry procedure allignment Applicability of intra3G_MSC SRNS Relocation Indication of Intra MSC
WI Multicall GSM/UMTS Interworking GSM/UMTS Interworking TrFo/OoBTC GSM/UMTS Interworking GSM/UMTS Interworking GSM/UMTS Interworking GSM/UMTS Interworking GSM/UMTS Interworking TEI GSM/UMTS Interworking
NP-10
NP-000724
N1-001412
23.009
015
R99
3.4.0
3.5.0
NP-10 NP-10 NP-10 NP-10
NP-000671 NP-000671 NP-000673 NP-000671
N1-001347 N1-001408 N1-001304 N1-001372
23.009 23.009 23.009 23.009
016 017 019 020
1 3
R99 R99 R99 R99
F F F F
3.4.0 3.4.0 3.4.0 3.4.0
3.5.0 3.5.0 3.5.0 3.5.0
NP-10 NP-11
NP-000671 NP-010123
N1-001403 N1-010086
23.009 23.009
021 018
1 2
R99 R99
F F
3.4.0 3.5.0
3.5.0 3.6.0
GSM/UMTS Interworking GSM/UMTS Interworking GSM/UMTS Interworking GSM/UMTS Interworking TRFOOOBTC Handover
NP-11
NP-010207
N1-010321
23.009
024
R99
3.5.0
3.6.0
NP-11 NP-11 NP-12
NP-010207 NP-010161 NP-010270
N1-010427 N1-010232 N1-010914
23.009 23.009 23.009
026 022 035 2 3
R99
3.5.0 3.6.0 4.0.0
3.6.0 4.0.0 4.1.0
Rel-4 C Rel-4 A
3GPP
Release 6
285
3GPP TS 23.009 V6.5.0 (2008-12)
NP-13
NP-010494
N1-011112
23.009
041
Rel-4 A
4.1.0
4.2.0
NP-13
NP-010495
N1-011229
23.009
047
Rel-4 A
4.1.0
4.2.0
NP-13
NP-010494
N1-011311
23.009
049
Rel-4 A
4.1.0
4.2.0
NP-14 NP-14
NP-010651 NP-010682
N1-011557 N1-011972
23.009 23.009
055 057
Rel-4 A Rel-4 A
4.2.0 4.2.0
4.3.0 4.3.0
NP-14 NP-14
NP-010682 NP-010691
N1-011807 N1-012027 revised twice N1-012042 N1-012055
23.009 23.009
060 063 3
Rel-4 A Rel-4 A
4.2.0 4.2.0
4.3.0 4.3.0
NP-14 NP-14
NP-010659 NP-010661
23.009 23.009
052 061
3 4
Rel-5 B Rel-5 B
4.3.0 4.3.0
5.0.0 5.0.0
handover from 3G_MSC-B to MSC-A/3G_MSC-A GSM to UMTS Handover: Location Reporting in 3G_MSC-B for no call up case Correction of SDL figures in CRs 034 and 035 (N1010913, N1-010914) Usage of Location Reporting for Relocation and Intersystem Handover Multicall bearer selection Usage of Location Reporting for Relocation and Intersystem Handover E-interface protocol during the supervision phase GSM to UMTS Handover: Iu-LOCATION-REPORTING message reception Introduction of Intra Domain Connection of RAN Reflection of RRC changes in 44.018 to 23.009
GSM/UMTS Interworking
Handover
GSM/UMTS Interworking Multicall GSM/UMTS Interworking GSM/UMTS Interworking GSM/UMTS Interworking IUFLEX
NP-16
NP-020243
N1-020879
23.009
066
Rel-5 C
5.0.0
5.1.0
NP-16
NP-020218
N1-021282
23.009
071
Rel-5 A
5.0.0
5.1.0
NP-16
NP-020243
N1-021426
23.009
074
Rel-5 F
5.0.0
5.1.0
NP-16
NP-020218
N1-021395
23.009
077
Rel-5 A
5.0.0
5.1.0
NP-17
NP-020383
N1-021789
23.009
080
Rel-5 B Rel-5
5.1.0 5.2.0
5.2.0 5.3.0
NP-18 NP-18
NP-020549 NP-020548
N1-022272 N1-022239
23.009 23.009
083 084
2 3
Rel-5 A Rel-5 F
5.2.0 5.2.0
5.3.0 5.3.0
NP-18
NP-020630
N1-022236
23.009
090
Rel-5 A
5.2.0
5.3.0
NP-19
NP-030041
N1-030294
23.009
093
Rel-5 A
5.3.0
5.4.0
NP-20
NP-030268
N1-030908
23.009
096
Rel-5 A
5.4.0
5.5.0
NP-20
NP-030283
N1-030875
23.009
097
Rel-5 F
5.4.0
5.5.0
NP-21 NP-22
NP-030417 NP-030473
N1-031099 N1-031510
23.009 23.009
099 101
Rel-5 F Rel-5 A
5.5.0 5.6.0
5.6.0 5.7.0
NP-23
NP-040031
N1-040468
23.009
102
Rel-5 F
5.7.0
5.8.0
NP-26 CP-28
CP-050071
C1-050764
23.009
104
Rel-6 Rel-6 F
5.8.0 6.0.0
6.0.0 6.1.0
Alignment of 3G functional split and Iu. Sending of RANAP Location TEI5 Reporting Control on the E Interface Clarification of the end of GSM/UMTS supervision after inter-MSC Interworking handover Clarification that Multicall is TEI5 not supported in GERAN Iumode Handling of Service GSM/UMTS Handover parameter in non- Interworking anchor Support for Shared Network TEI5 Area ETSI/MCC updated with correct release to references [2], [3], [4], [6], and [7]. MSC_A_HO SDL correction TEI Inter-MSC relocation and TRFOintersystem handover for OOBTC multiple codecs Clarification of the protocol GSM/UMTS to be used on the EInterworking interface Further clarification of the GSM/UMTS protocol to the be used on Interworking the E-interface Correct text related to timer GSM/UMTS expiry for receipt of AInterworking HANDOVER-COMPLETE / Iu-RELOCATIONCOMPLETE Addition of UESBI-Iu to LATE_UE handover and relocation procedures Correction to UESBI-Iu LATE_UE definition Correcting a mistake in GSM/UMTS previously approved interworking category A of its Rel99 category F CR 091 Rev 1 in NP-030041 Renaming of the Available TEI5 Codecs List to Iu Supported Codecs List Rel-6 published after CN#26 Full RANAP support of TEI6 network initiated SCUDIF
3GPP
Release 6
286
3GPP TS 23.009 V6.5.0 (2008-12)
CP-28
CP-050072
C1-050741
23.009
105
Rel-6 F
6.0.0
6.1.0
Directed Retry Handover for CS_VSS Bearer Service
CP-29
CP-050443
23.009
Rel-6 A
6.1.0
6.2.0
Intra-3G_MSC-B handover/relocation interactions with other RANAP procedures Subsequent Inter-MSC handover/relocation interactions with other RANAP procedures
TEI5
109 CP-30 CP-050536 C1-051306 23.009
5 Rel-6 A 6.2.0 6.3.0 TEI5
113 CP-30 CP-050536 C1-051308 23.009 Rel-6 A 6.2.0 6.3.0 Correction to Intra-3G_MSC- TEI5 B handover/relocation interactions with other RANAP procedures for the security mode control procedure Clarification of directed retry handover failure cases TEI5 Aligning release 6 with release 5
115 CP-31 CP-060108 CP-31 CP-060113 CP-42 CP-080871 C1-083805 23.009 0123 Rel-6 C1-060508 23.009 0120 Rel-6 A 6.4.0 6.5.0 Correction of white-on-white text in 23.009 TEI5 C1-060564 23.009 0119 1 Rel-6 F 6.3.0 6.4.0 TEI6 A 6.3.0 6.4.0
3GPP

23009-650 Handover CN and UE

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

23009-650 Handover CN and UE

Uploaded by

Copyright:

Available Formats

3GPP TS 23.009 V6.5.

GLOBAL SYSTEM FOR MOBILE COMMUNICATIONS

3GPP TS 23.009 V6.5.0 (2008-12)

3GPP Postal address

3GPP support office address

3GPP TS 23.009 V6.5.0 (2008-12)

Role, functional composition of MSCs and interfaces for handover ...................................................11

General description of the procedures for inter - MSC handovers ......................................................32

General Description of the procedures for inter - 3G_MSC handovers ...............................................41

3GPP TS 23.009 V6.5.0 (2008-12)

Detailed procedures in MSC-A .........................................................................................................73

Detailed procedures in MSC-B..........................................................................................................77

Detailed procedures in 3G_MSC-A...................................................................................................79

Detailed procedures in 3G_MSC-B ...................................................................................................84

3GPP TS 23.009 V6.5.0 (2008-12)

Directed retry handover...................................................................................................................103

SDL diagrams .................................................................................................................................107 Change history .........................................................................................284

3GPP TS 23.009 V6.5.0 (2008-12)

3GPP TS 23.009 V6.5.0 (2008-12)

3GPP TS 23.009 V6.5.0 (2008-12)

3GPP TS 23.009 V6.5.0 (2008-12)

[1] [2] [2a] [3] [4] [5] [6] [7] [8]

Abbreviations and definitions

3GPP TS 23.009 V6.5.0 (2008-12)

3GPP TS 23.009 V6.5.0 (2008-12)

Role, functional composition of MSCs and interfaces for handover

3GPP TS 23.009 V6.5.0 (2008-12)

Functional composition of MSC-A and its interfaces for handover

3GPP TS 23.009 V6.5.0 (2008-12)

1 BSC/MSC (MS/BSC) Procedures MSC-A

Switching control Switching functions

Switch and Handover Device MSC-A

Figure 2a) Figure 2b) Figure 2c)

3GPP TS 23.009 V6.5.0 (2008-12)

A a) Intra-MSC Handover case. A B

B b) Basic Handover case and handover of MS to MS call in the same MSC.

B B c) Subsequent Handover case

Figure 2: Connections in the handover device (Unit 5)

3GPP TS 23.009 V6.5.0 (2008-12)

Functional composition of MSC-B and its interfaces for handover

3GPP TS 23.009 V6.5.0 (2008-12)

1 BSC/MSC (MS/BSC) Procedures MSC-B

Switching control Switching functions

Figure 3: Functional composition of MSC-B for supporting handover

3GPP TS 23.009 V6.5.0 (2008-12)

3GPP TS 23.009 V6.5.0 (2008-12)

Functional composition of 3G_MSC-A and its interfaces for handover/relocation

3GPP TS 23.009 V6.5.0 (2008-12)

RNC/BSC/ 3G_MSC (UE/MS/RNC/BSC) Procedures 1

Switching control Switching functions

Switch and HO/Rel Device 3G_MSC-A

3GPP TS 23.009 V6.5.0 (2008-12)

Table 2: States of the handover/relocation device

Figure 5b) Figure 5c)

Iu/A a) Intra-3G_MSC Handover/Relocation case. Iu B

B B c) Subsequent Handover/Relocation case

Figure 5: Connections in the handover/relocation device (Unit 5)

3GPP TS 23.009 V6.5.0 (2008-12)

3GPP TS 23.009 V6.5.0 (2008-12)

3GPP TS 23.009 V6.5.0 (2008-12)

Functional composition of 3G_MSC-B and its interfaces for handover/relocation

3GPP TS 23.009 V6.5.0 (2008-12)

RNC/BSC/ 3G_MSC (UE/MS/RNC/BSC) Procedures 1