Professional Documents
Culture Documents
Issue Date
02 2008-07-30
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For any assistance, please contact our local office or company headquarters.
Notice
The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute the warranty of any kind, express or implied.
Contents
Contents
1 Inter-RAT Handover Change History ................................................................................1-1 2 Inter-RAT Handover Introduction......................................................................................2-1 3 Inter-RAT Handover Algorithms........................................................................................3-1
3.1 UMTS-to-GSM Handover Types............................................................................................................. 3-1 3.2 UMTS-to-GSM Handover Procedure ...................................................................................................... 3-2 3.2.1 Coverage-based UMTS-to-GSM Handover Procedure.................................................................... 3-3 3.2.2 QoS-based UMTS-to-GSM Handover Procedure............................................................................ 3-4 3.2.3 Load-based UMTS-to-GSM Handover Procedure........................................................................... 3-5 3.2.4 Service-based UMTS-to-GSM Handover Procedure ....................................................................... 3-6 3.3 Preconditions for UMTS-to-GSM Handover ........................................................................................... 3-6 3.3.1 Service Handover Indicator............................................................................................................ 3-7 3.3.2 Capabilities of Deciding UMTS-to-GSM Handover...................................................................... 3-17 3.3.3 Rules for Enabling UMTS-to-GSM Handover .............................................................................. 3-17 3.4 UMTS-to-GSM Handover Measurement............................................................................................... 3-20 3.4.1 UMTS-to-GSM Handover Measurement Switches ....................................................................... 3-20 3.4.2 UMTS-to-GSM Handover Measurement Report Modes................................................................ 3-21 3.4.3 UMTS-to-GSM Handover Measurement Events........................................................................... 3-22 3.4.4 UMTS-to-GSM Handover Neighboring Cell Combination Algorithm ........................................... 3-25 3.4.5 UMTS-to-GSM Handover Measurement Quantity........................................................................ 3-25 3.4.6 UMTS-to-GSM Handover L3 Filtering ........................................................................................ 3-25 3.4.7 UMTS-to-GSM Handover Compressed Mode .............................................................................. 3-25 3.4.8 BSIC Verification Requirements for GSM Cells ........................................................................... 3-25 3.5 UMTS-to-GSM Handover Decision and Execution ............................................................................... 3-25 3.5.1 Coverage-Based and QoS-Based UMTS-to-GSM Handover Decision and Execution .................... 3-25 3.5.2 Load-Based and Service-Based UMTS-to-GSM Handover Decision and Execution...................... 3-25 3.5.3 UMTS-to-GSM Handover Retry .................................................................................................. 3-25 3.5.4 UMTS-to-GSM Multimedia Fallback........................................................................................... 3-25 3.5.5 UMTS-to-GSM Handover in the PS Domain with NACC or PS Handover.................................... 3-25 3.6 Inter-RAT Handover of HSDPA ............................................................................................................ 3-25 3.7 Inter-RAT Handover of HSUPA ............................................................................................................ 3-25 3.8 GSM-to-UMTS Handover .................................................................................................................... 3-25 3.9 Interoperability Between Inter-RAT Handover and Inter-Frequency Handover ....................................... 3-25
Issue 02 (2008-07-30)
Contents
3.10 Signaling Procedures for Inter-RAT Handover..................................................................................... 3-25 3.10.1 UMTS-to-GSM Handover in CS Domain ................................................................................... 3-25 3.10.2 UMTS to GSM Handover in PS Domain .................................................................................... 3-25 3.10.3 UMTS-to-GSM Handover in Both CS Domain and PS Domain .................................................. 3-25 3.10.4 GSM-to-UMTS Handover in CS Domain ................................................................................... 3-25 3.10.5 GSM-to-UMTS Handover in PS Domain ................................................................................... 3-25
ii
Issue 02 (2008-07-30)
Inter-RAT Handover Change History provides information on the changes between different document versions.
V100R010C01B050 V200R010C01B041
01 (2008-05-30)
10.0
V200R010C01B051
V100R010C01B049 V200R010C01B040
Draft (2008-03-20)
10.0
V200R010C01B050
V100R010C01B045
Feature change: refers to the change in the feature of a specific product version. Editorial change: refers to the change in information that has already been included, or the addition of information that was not provided in the previous version.
02 (2008-07-30)
This is the document for the second commercial release of RAN10.0. Compared with 01 (2008-05-30) of RAN10.0, issue 02 (2008-07-30) of RAN10.0 incorporates the changes described in the following table.
Issue 02 (2008-07-30)
1-1
Parameter Change The parameters that are changed to be non-configurable are listed as follows:
l l l l
Service Handover Indicator Service parameter index Required 2G Capability Inter-RAT H handover decision THD
Editorial change
None
01 (2008-05-30)
This is the document for the first commercial release of RAN10.0. Compared with draft (2008-03-20) of RAN10.0, issue 01 (2008-05-30) of RAN10.0 incorporates the changes described in the following table. Change Type Feature change Editorial change Change Description None General documentation change:
l
The Inter-RAT Handover Parameters is removed because of the creation of RAN10.0 parameter reference. The structure is optimized.
Draft (2008-03-20)
This is a draft of the document for the first commercial release of RAN10.0. Compared with issue 02 (2007-12-24) of RAN6.1, issue Draft (2008-03-20) of RAN10.0 incorporates the changes described in the following table.
1-2
Issue 02 (2008-07-30)
Change Description The description of inter-RAT handover based on QoS is added, as listed below:
l
Parameter Change Added parameters The following parameter is described in 3.4.3 UMTS-to-GSM Handover Measurement Events.
3.1 UMTS-to-GSM Handover Types 3.2 UMTS-to-GSM Handover Procedure "Triggering of Event 3A" in 3.4.3 UMTS-to-GSM Handover Measurement Events "Measurement Timer Length" in 3.4.7 UMTS-to-GSM Handover Compressed Mode 3.5.1 Coverage-Based and QoS-Based UMTS-to-GSM Handover Decision and Execution
Down Link RSCP Used-Freq THD Hyst The following parameters are described in 3.4.7 UMTS-to-GSM Handover Compressed Mode.
l l
Down Link QoS Measure timer length Up Link Qos Measure timer length
The inter-RAT handover measurement quantities are changed, as described in 3.4.5 UMTS-to-GSM Handover Measurement Quantity. The cell individual offset of a cell is used together with the neighboring cell oriented individual offset. For detailed information, see 3.4.3 UMTS-to-GSM Handover Measurement Events. UMTS-to-GSM Handover Penalty algorithm is changed to UMTS-to-GSM Handover Retry algorithm, see 3.5.3 UMTS-to-GSM Handover Retry
2D2F Measure Quantity 3A Used-Freq Measure Quantity for Qos Cell offset
l
Cell oriented Cell Individual Offset Neigbhoring cell oriented CIO 3A event retry period 3A event retry max times 3C event retry period 3C event retry max times
Added parameters
Issue 02 (2008-07-30)
1-3
Change Type
Change Description Interchanging Load Information in UMTS-to-GSM and GSM-to-UMTS Load/Service-Based Handover, see
l
Send Load Info to GSM Ind NCOV Reloc Ind based on GSM cell load CS domain Reloc GSM load THD PS domain Reloc GSM load THD
3.5.2 Load-Based and Service-Based UMTS-to-GSM Handover Decision and Execution 3.8 GSM-to-UMTS Handover
None.
The description of inter-RAT handover of HSDPA is moved from the HSDPA feature document, see 3.6 Inter-RAT Handover of HSDPA. The description of inter-RAT handover of HSUPA is moved from the HSUPA feature document, see 3.7 Inter-RAT Handover of HSUPA. Editorial change The default value of Service Parameter Index is changed.
None.
The default value of Service Parameter Index is changed from 49 to 99. The default value table of service handover indicators is changed.
The default value of 3C hysteresis is changed. General documentation change: Implementation information has been moved to a separate document.
1-4
Issue 02 (2008-07-30)
Inter-RAT handover provides coverage expansion, load sharing, and layered services. It saves cost by utilizing the existing GSM network resources. Inter-RAT handover refers to the handover between UMTS and GSM. The reason for the handover can be coverage limitation, link stability control or load limitation of the 3G system. For detailed information on the relation to other handover types, see Intra-Frequency Handover Introduction. Inter-RAT handover can be UMTS-to-GSM or GSM-to-UMTS handover. As shown in the following figure, for a UE in CELL_DCH state, the UMTS-to-GSM handover procedure is triggered when the UMTS Radio Access Network (RAN) initiates handover or cell reselection to the GSM. Figure 2-1 Inter-RAT handover
In this handover, however, GSM and UMTS dual-mode mobile stations (MSs) are required, and both the GSM MSC and the GSM BSS must be upgraded.
Impact
l
Impact on System Performance Inter-RAT handover measurement may be implemented in compressed mode; therefore, one of the impacts on the system is from the compressed mode. When too many UEs
Issue 02 (2008-07-30)
2-1
stay at the cell edge, the downlink capacity and uplink coverage of the system may decrease. Another impact is from the QoS requirement for the delay-sensitive services, because hard handover can introduce handover delay.
l
Impact on Other Features This feature has no impact on other features. Miscellaneous A dual-mode UE is required to support inter-RAT handover. That is, the UE must support both GSM and UMTS, and its network selection mode must be set to auto.
= NE involved
UE = User Equipment, RNC = Radio Network Controller, MSC Server = Mobile Service Switching Center Server, MGW = Media Gateway, SGSN = Serving GPRS Support Node, GGSN = Gateway GPRS Support Node, HLR = Home Location Register
2-2
Issue 02 (2008-07-30)
3
l l l l l l l l l l
Inter-RAT Handover Algorithms covers the technical aspects of the feature UMTS-to-GSM Handover Types UMTS-to-GSM Handover Procedure Preconditions for UMTS-to-GSM Handover UMTS-to-GSM Handover Measurement UMTS-to-GSM Handover Decision and Execution Inter-RAT Handover of HSDPA Inter-RAT Handover of HSUPA GSM-to-UMTS Handover Interoperability Between Inter-RAT Handover and Inter-Frequency Handover Signaling Procedures for Inter-RAT Handover
Issue 02 (2008-07-30)
3-1
UMTS-to-GSM handover Types QoS-based UMTS-to-GSM handover Load-based UMTS-to-GSM handover Service-based UMTS-to-GSM handover Speed-based UMTS-to-GSM handover
Description According to the Link Stability Control Algorithm, the RNC needs to trigger the QoS-based UMTS-to-GSM handover to avoid call drops. If the load of the UMTS is heavy and all the RAB of the UE are supported by the GSM, the load-based UMTS-to-GSM handover is triggered. Based on layered services, the traffic of different classes is handed over to different systems. For example, when an Adaptive Multi Rate (AMR) speech service is requested, this service can be handed over to the GSM. When the Hierarchical Cell Structure (HCS) is used, the cells are divided into different layers on the basis of coverage. Typically, a marco cell has large coverage and low priority, whereas a micro cell has small coverage and high priority. UMTS-to-GSM handover can be triggered by the UE speed estimation algorithm of the HCS. A UE moving at high speed is handed over to a cell with larger coverage to reduce the times of handover, whereas a UE moving at low speed is handed over to a cell with smaller coverage. For detailed information, see HCS Handover. NOTE: The principles of the UMTS-to-GSM handover based on HCS speed estimation are similar to those of inter-frequency handover, which will not be elaborated in this feature.
The coverage-based UMTS-to-GSM measurement and the QoS-based UMTS-to-GSM measurement can coexist.
Coverage-based UMTS-to-GSM Handover Procedure QoS-based UMTS-to-GSM Handover Procedure Load-based UMTS-to-GSM Handover Procedure Service-based UMTS-to-GSM Handover Procedure
3-2
Issue 02 (2008-07-30)
In the triggering phase The RNC sends a MEASUREEMNT CONTROL message to the UE, notifying the UE to measure the current carrier quality. This message defines the reporting rules and thresholds of events 2D and 2F. If the quality of the pilot signal in the current cell deteriorates, the CPICH Ec/No or CPICH RSCP of the UMTS cell that the UE accesses is lower than the corresponding threshold and the UE reports event 2D.
In the measurement phase If the RNC receives a report of event 2D, the RNC may request the NodeB and UE to start the compressed mode to measure the qualities of GSM cells. Then, the RNC may send an inter-RAT measurement control message that defines the neighboring cell information, reporting period, and reporting rule.
In the measurement phase, either periodical measurement report mode or event-triggered measurement report mode can be used.
Issue 02 (2008-07-30)
3-3
After the UE reports event 3A, the RNC makes a handover decision. Or, after the UE periodically sends the measurement reports, the RNC evaluates the reports first and then makes a handover decision.
l
In the triggering phase The Link Stability Control Algorithm makes a handover measurement decision. In the measurement phase The RNC requests the NodeB and the UE to start the compressed mode to measure the qualities of inter-RAT neighboring cells. Then, the RNC sends an inter-RAT measurement control message. This message defines neighboring cell information, reporting period, and reporting rule.
In the measurement phase, the method of periodical measurement report or event-triggered measurement report can be used.
In the decision phase After the UE reports event 3A, the RNC performs the handover. Otherwise, the UE periodically generates measurement reports, and the RNC makes a decision after evaluation.
3-4
Issue 02 (2008-07-30)
In the triggering phase When the load of the UMTS cell that the UE accesses is higher than the related threshold, the Load Reshuffling (LDR) algorithm makes a handover decision.
For detailed information of the LDR, see Load Reshuffling.
In the measurement phase The RNC enables the compressed mode and starts the inter-RAT handover measurement. In the decision phase After the UE reports event 3C, the RNC makes a handover decision. In the execution phase The RNC initiates a handover procedure.
Issue 02 (2008-07-30)
3-5
In the triggering phase When a service is established, the RNC requests the handover to the GSM based on the service type and service handover indicator assigned by the Core Network (CN).
In the measurement phase The RNC enables the compressed mode and starts the inter-RAT handover measurement. In the decision phase After the UE reports event 3C, the RNC makes a handover decision. In the execution phase The RNC initiates a handover procedure.
Service Handover Indicator Capabilities of Deciding UMTS-to-GSM Handover Rules for Enabling UMTS-to-GSM Handover
3-6
Issue 02 (2008-07-30)
If the switch is set to ON, the service attribute of inter-RAT handover is based on the parameter configured on the RNC side. If the switch is set to OFF, the service attribute of inter-RAT handover is first based on the CN when the indicator is contained in the RAB assignment signaling assigned by the CN. If the CN doesn't allocate service indicator, the service attribute of inter-RAT handover is based on the RNC side.
HO_TO_GSM_SHOULD_BE_PERFORM: means that the handover to the 2G network is performed when 2G signals are available. HO_TO_GSM_SHOULD_NOT_BE_PERFORM: means that the handover to the 2G network is performed when 3G signals are weak but 2G signals are strong. HO_TO_GSM_SHALL_NOT_BE_PERFORM: means that the handover to the 2G network is not performed even when 3G signals are weak but 2G signals are strong.
The following figure shows an example of rules for the indicator of the UMTS-to-GSM handover based on load and service.
Issue 02 (2008-07-30)
3-7
Figure 3-5 Example of rules for indicator of UMTS-to-GSM handover based on load and service
For a UE with a single signaling RAB, the RNC supports the handover to the GSM. But it is not recommended. For the UE accessing combined services (with CS services), the RNC sets the service handover indicator of the UE to that of the CS service, because the CS service has the highest QoS priority. For the UE accessing combined services (with only PS services), the RNC sets the service handover indicator of the UE to that of the PS service, which has the highest QoS priority.
3-8
Issue 02 (2008-07-30)
Table 3-2 Service handover indicators (default values) Service Paramet er Index 0 Traffic Class Source Description CN Domain ID CS_DOMAIN Max Rate (bit/s) 12200 Service Handover Indicator HO_TO_GSM _SHOULD_N OT_BE_PERF ORM HO_TO_GSM _SHOULD_N OT_BE_PERF ORM HO_TO_GSM _SHALL_NO T_BE_PERFO RM HO_TO_GSM _SHALL_NO T_BE_PERFO RM HO_TO_GSM _SHALL_NO T_BE_PERFO RM HO_TO_GSM _SHALL_NO T_BE_PERFO RM HO_TO_GSM _SHALL_NO T_BE_PERFO RM N.A. N.A. N.A. N.A. HO_TO_GSM _SHALL_NO T_BE_PERFO RM HO_TO_GSM _SHALL_NO T_BE_PERFO RM Required 2G Capability
CONVERSATIONAL SPEECH
GSM
CONVERSATIONAL UNKNOWN
CS_DOMAIN
23850
GSM
CONVERSATIONAL UNKNOWN
CS_DOMAIN
28800
GSM
CONVERSATIONAL UNKNOWN
CS_DOMAIN
32000
GSM
CONVERSATIONAL UNKNOWN
CS_DOMAIN
56000
GSM
STREAMING
UNKNOWN
CS_DOMAIN
64000
GSM
STREAMING
UNKNOWN
PS_DOMAIN
57600
EDGE
7 8 9 10 11
CONVERSATIONAL UNKNOWN
12
CONVERSATIONAL UNKNOWN
PS_DOMAIN
16000
EDGE
Issue 02 (2008-07-30)
3-9
Traffic Class
Source Description
CN Domain ID PS_DOMAIN
Service Handover Indicator HO_TO_GSM _SHALL_NO T_BE_PERFO RM N.A. HO_TO_GSM _SHALL_NO T_BE_PERFO RM HO_TO_GSM _SHALL_NO T_BE_PERFO RM HO_TO_GSM _SHALL_NO T_BE_PERFO RM HO_TO_GSM _SHALL_NO T_BE_PERFO RM HO_TO_GSM _SHALL_NO T_BE_PERFO RM N.A. HO_TO_GSM _SHALL_NO T_BE_PERFO RM HO_TO_GSM _SHALL_NO T_BE_PERFO RM HO_TO_GSM _SHALL_NO T_BE_PERFO RM HO_TO_GSM _SHALL_NO T_BE_PERFO RM
Required 2G Capability
CONVERSATIONAL UNKNOWN
EDGE
14 15
N.A.
N.A.
N.A. PS_DOMAIN
N.A. 64000
GSM EDGE
CONVERSATIONAL UNKNOWN
16
CONVERSATIONAL UNKNOWN
PS_DOMAIN
38800
EDGE
17
CONVERSATIONAL UNKNOWN
PS_DOMAIN
39200
EDGE
18
CONVERSATIONAL UNKNOWN
PS_DOMAIN
40000
EDGE
19
CONVERSATIONAL UNKNOWN
PS_DOMAIN
42800
EDGE
20 21
N.A. STREAMING
N.A. UNKNOWN
N.A. PS_DOMAIN
N.A. 8000
N.A. GSM
22
STREAMING
UNKNOWN
PS_DOMAIN
16000
GSM
23
STREAMING
UNKNOWN
PS_DOMAIN
32000
GSM
24
STREAMING
UNKNOWN
PS_DOMAIN
64000
GSM
3-10
Issue 02 (2008-07-30)
Traffic Class
CN Domain ID PS_DOMAIN
Service Handover Indicator HO_TO_GSM _SHALL_NO T_BE_PERFO RM HO_TO_GSM _SHALL_NO T_BE_PERFO RM HO_TO_GSM _SHALL_NO T_BE_PERFO RM HO_TO_GSM _SHALL_NO T_BE_PERFO RM N.A. N.A. HO_TO_GSM _SHALL_NO T_BE_PERFO RM HO_TO_GSM _SHALL_NO T_BE_PERFO RM HO_TO_GSM _SHALL_NO T_BE_PERFO RM HO_TO_GSM _SHOULD_N OT_BE_PERF ORM HO_TO_GSM _SHOULD_N OT_BE_PERF ORM HO_TO_GSM _SHOULD_N OT_BE_PERF ORM
Required 2G Capability
STREAMING
GSM
26
STREAMING
UNKNOWN
PS_DOMAIN
144000
GSM
27
STREAMING
UNKNOWN
PS_DOMAIN
256000
EDGE
28
STREAMING
UNKNOWN
PS_DOMAIN
384000
EDGE
29 30 31
32
N.A.
N.A.
N.A.
N.A.
EDGE
33
N.A.
N.A.
N.A.
N.A.
EDGE
34
N.A.
N.A.
N.A.
N.A.
EDGE
35
N.A.
N.A.
N.A.
N.A.
EDGE
36
N.A.
N.A.
N.A.
N.A.
EDGE
Issue 02 (2008-07-30)
3-11
Traffic Class
Service Handover Indicator N.A. N.A. N.A. HO_TO_GSM _SHOULD_N OT_BE_PERF ORM HO_TO_GSM _SHOULD_N OT_BE_PERF ORM HO_TO_GSM _SHOULD_N OT_BE_PERF ORM HO_TO_GSM _SHOULD_N OT_BE_PERF ORM HO_TO_GSM _SHOULD_N OT_BE_PERF ORM HO_TO_GSM _SHOULD_N OT_BE_PERF ORM HO_TO_GSM _SHOULD_N OT_BE_PERF ORM HO_TO_GSM _SHOULD_N OT_BE_PERF ORM HO_TO_GSM _SHOULD_N OT_BE_PERF ORM
Required 2G Capability
41
INTERACTIVE
UNKNOWN
PS_DOMAIN
8000
GPRS
42
INTERACTIVE
UNKNOWN
PS_DOMAIN
16000
GPRS
43
INTERACTIVE
UNKNOWN
PS_DOMAIN
32000
GPRS
44
INTERACTIVE
UNKNOWN
PS_DOMAIN
64000
GPRS
45
INTERACTIVE
SPEECH
PS_DOMAIN
128000
EDGE
46
INTERACTIVE
UNKNOWN
PS_DOMAIN
144000
EDGE
47
INTERACTIVE
UNKNOWN
PS_DOMAIN
256000
EDGE
48
INTERACTIVE
UNKNOWN
PS_DOMAIN
384000
EDGE
3-12
Issue 02 (2008-07-30)
Traffic Class
CN Domain ID PS_DOMAIN
Service Handover Indicator HO_TO_GSM _SHALL_NO T_BE_PERFO RM HO_TO_GSM _SHALL_NO T_BE_PERFO RM HO_TO_GSM _SHALL_NO T_BE_PERFO RM HO_TO_GSM _SHALL_NO T_BE_PERFO RM HO_TO_GSM _SHALL_NO T_BE_PERFO RM HO_TO_GSM _SHALL_NO T_BE_PERFO RM HO_TO_GSM _SHALL_NO T_BE_PERFO RM HO_TO_GSM _SHALL_NO T_BE_PERFO RM HO_TO_GSM _SHALL_NO T_BE_PERFO RM HO_TO_GSM _SHALL_NO T_BE_PERFO RM
Required 2G Capability
INTERACTIVE
EDGE
50
INTERACTIVE
UNKNOWN
PS_DOMAIN
768000
EDGE
51
INTERACTIVE
UNKNOWN
PS_DOMAIN
102400 0
EDGE
52
INTERACTIVE
UNKNOWN
PS_DOMAIN
145000 0
EDGE
53
INTERACTIVE
UNKNOWN
PS_DOMAIN
153600 0
EDGE
54
INTERACTIVE
UNKNOWN
PS_DOMAIN
180000 0
EDGE
55
INTERACTIVE
UNKNOWN
PS_DOMAIN
204800 0
EDGE
56
INTERACTIVE
UNKNOWN
PS_DOMAIN
289000 0
EDGE
57
INTERACTIVE
UNKNOWN
PS_DOMAIN
364800 0
EDGE
58
INTERACTIVE
UNKNOWN
PS_DOMAIN
576000 0
EDGE
Issue 02 (2008-07-30)
3-13
Traffic Class
CN Domain ID PS_DOMAIN
Service Handover Indicator HO_TO_GSM _SHALL_NO T_BE_PERFO RM HO_TO_GSM _SHALL_NO T_BE_PERFO RM HO_TO_GSM _SHALL_NO T_BE_PERFO RM N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. HO_TO_GSM _SHOULD_N OT_BE_PERF ORM HO_TO_GSM _SHOULD_N OT_BE_PERF ORM HO_TO_GSM _SHOULD_N OT_BE_PERF ORM HO_TO_GSM _SHOULD_N OT_BE_PERF ORM
Required 2G Capability
INTERACTIVE
EDGE
60
INTERACTIVE
UNKNOWN
PS_DOMAIN
101000 00
EDGE
61
INTERACTIVE
UNKNOWN
PS_DOMAIN
144000 00
EDGE
62 63 64 65 66 67 68 69 70
71
BACKGROUND
UNKNOWN
PS_DOMAIN
8000
GPRS
72
BACKGROUND
UNKNOWN
PS_DOMAIN
16000
GPRS
73
BACKGROUND
UNKNOWN
PS_DOMAIN
32000
GPRS
3-14
Issue 02 (2008-07-30)
Traffic Class
CN Domain ID PS_DOMAIN
Service Handover Indicator HO_TO_GSM _SHOULD_N OT_BE_PERF ORM HO_TO_GSM _SHOULD_N OT_BE_PERF ORM HO_TO_GSM _SHOULD_N OT_BE_PERF ORM HO_TO_GSM _SHOULD_N OT_BE_PERF ORM HO_TO_GSM _SHOULD_N OT_BE_PERF ORM HO_TO_GSM _SHALL_NO T_BE_PERFO RM HO_TO_GSM _SHALL_NO T_BE_PERFO RM HO_TO_GSM _SHALL_NO T_BE_PERFO RM HO_TO_GSM _SHALL_NO T_BE_PERFO RM HO_TO_GSM _SHALL_NO T_BE_PERFO RM
Required 2G Capability
BACKGROUND
GPRS
75
BACKGROUND
UNKNOWN
PS_DOMAIN
128000
EDGE
76
BACKGROUND
UNKNOWN
PS_DOMAIN
144000
EDGE
77
BACKGROUND
UNKNOWN
PS_DOMAIN
256000
EDGE
78
BACKGROUND
UNKNOWN
PS_DOMAIN
384000
EDGE
79
BACKGROUND
UNKNOWN
PS_DOMAIN
608000
EDGE
80
BACKGROUND
UNKNOWN
PS_DOMAIN
768000
EDGE
81
BACKGROUND
UNKNOWN
PS_DOMAIN
102400 0
EDGE
82
BACKGROUND
UNKNOWN
PS_DOMAIN
145000 0
EDGE
83
BACKGROUND
UNKNOWN
PS_DOMAIN
153600 0
EDGE
Issue 02 (2008-07-30)
3-15
Traffic Class
CN Domain ID PS_DOMAIN
Service Handover Indicator HO_TO_GSM _SHALL_NO T_BE_PERFO RM HO_TO_GSM _SHALL_NO T_BE_PERFO RM HO_TO_GSM _SHALL_NO T_BE_PERFO RM HO_TO_GSM _SHALL_NO T_BE_PERFO RM HO_TO_GSM _SHALL_NO T_BE_PERFO RM HO_TO_GSM _SHALL_NO T_BE_PERFO RM HO_TO_GSM _SHALL_NO T_BE_PERFO RM HO_TO_GSM _SHALL_NO T_BE_PERFO RM N.A. N.A. N.A. N.A. N.A. N.A. N.A.
Required 2G Capability
BACKGROUND
EDGE
85
BACKGROUND
UNKNOWN
PS_DOMAIN
204800 0
EDGE
86
BACKGROUND
UNKNOWN
PS_DOMAIN
289000 0
EDGE
87
BACKGROUND
UNKNOWN
PS_DOMAIN
364800 0
EDGE
88
BACKGROUND
UNKNOWN
PS_DOMAIN
576000 0
EDGE
89
BACKGROUND
UNKNOWN
PS_DOMAIN
720000 0
EDGE
90
BACKGROUND
UNKNOWN
PS_DOMAIN
101000 00
EDGE
91
BACKGROUND
UNKNOWN
PS_DOMAIN
144000 00
EDGE
92 93 94 95 96 97 98
3-16
Issue 02 (2008-07-30)
Traffic Class
CN Domain ID N.A.
Required 2G Capability
N.A.
N.A.
Service Capability
The Required 2G Capability specifies the capability of 2G cells required by inter-RAT handover. This indicates whether the service is supported by the GSM, GPRS, or EDGE.The default value provided by RNC see Table 3-2.
UE Capability
Upon the reception of the UE capability information message, the RNC decides whether to start the inter-RAT measurement. The information indicates whether the UE supports the GSM, GPRS, or EDGE.
HO_TO_GSM_SHOULD_BE_PERFORM HO_TO_GSM_SHOULD_NOT_BE_PERFORM
In addition, the RNC initiates inter-RAT handover based on the following capabilities:
l l l
The following tables describe the capability of the coverage-based and QoS-based UMTS-to-GSM handover in the combination of the three "capabilities" listed above.
Issue 02 (2008-07-30)
3-17
Table 3-3 GSM neighboring cell with EDGE capability UE Capability Service capability (required by 2G) EDGE EDGE GPRS GSM Not supported by 2G Allowed Allowed Not allowed Not allowed GPRS Allowed Allowed Not allowed Not allowed GSM Allowed Allowed Allowed Not allowed
Table 3-4 GSM neighboring cell with GPRS capability UE Capability Service capability (required by 2G) EDGE EDGE GPRS GSM Not supported by 2G Allowed Allowed Not allowed Not allowed GPRS Allowed Allowed Not allowed Not allowed GSM Allowed Allowed Allowed Not allowed
Table 3-5 GSM neighboring cell with GSM capability UE Capability Service capability (required by 2G) EDGE EDGE GPRS GSM Not supported by 2G Not allowed Not allowed Not allowed Not allowed GPRS Not allowed Not allowed Not allowed Not allowed GSM Allowed Allowed Allowed Not allowed
If the capability of all the GSM neighboring cells is "No capability", the inter-RAT measurement cannot be started.
HO_TO_GSM_SHOULD_BE_PERFORM HO_TO_GSM_SHOULD_NOT_BE_PERFORM
3-18
Issue 02 (2008-07-30)
The RNC initiates the service-based UMTS-to-GSM handover only when Service Handover Indicator is set as follows:
l
HO_TO_GSM_SHOULD_BE_PERFORM In addition, the RNC initiates UMTS-to-GSM handover based on the following capabilities:
l l l
The following tables describe the capability of the load and service-based UMTS-to-GSM handover in the combination of the three "capabilities" listed above. Table 3-6 GSM neighboring cell with EDGE capability UE Capability Service capability (required by 2G) EDGE EDGE GPRS GSM Not supported by 2G Allowed Not allowed Not allowed Not allowed GPRS Allowed Allowed Not allowed Not allowed GSM Allowed Allowed Allowed Not allowed
Table 3-7 GSM neighboring cell with GPRS capability UE Capability Service capability (required by 2G) EDGE EDGE GPRS GSM Not supported by 2G Not allowed Not allowed Not allowed Not allowed GPRS Allowed Allowed Not allowed Not allowed GSM Allowed Allowed Allowed Not allowed
Table 3-8 GSM neighboring cell with GSM capability UE Capability Service capability (required by 2G) EDGE EDGE GPRS GSM Not supported by 2G Not allowed Not allowed Not allowed Not allowed GPRS Not allowed Not allowed Not allowed Not allowed GSM Allowed Allowed Allowed Not allowed
Issue 02 (2008-07-30)
3-19
If the capability of all the GSM neighboring cells is "No capability", the inter-RAT measurement cannot be started.
If the "Required 2G Capability" is "GPRS", "GSM", or "EDGE", the RNC does not consider whether the UE supports the EDGE. Only when the "Required 2G Capability" is "EDGE", the RNC checks the UE capability.
When a single CS service is initially set up by the UE, the RNC allows the UMTS-to-GSM service-based handover if Inter-RAT CS handover switch is set to ON. When a single PS service is initially set up by the UE, the RNC allows the UMTS-to-GSM service-based handover if Inter-RAT PS handover switch is set to ON. For the CS and PS combined services, no service-based handover is triggered.
UMTS-to-GSM Handover Measurement Switches UMTS-to-GSM Handover Measurement Report Modes UMTS-to-GSM Handover Measurement Events UMTS-to-GSM Handover Neighboring Cell Combination Algorithm UMTS-to-GSM Handover Measurement Quantity UMTS-to-GSM Handover L3 Filtering UMTS-to-GSM Handover Compressed Mode BSIC Verification Requirements for GSM Cells
3-20
Issue 02 (2008-07-30)
Table 3-9 Switches of UMTS-to-GSM Handover Measurement Switch Description The switch decides when the RNC performs the inter-frequency/inter-RAT coverage-based handover measurement. If the switch is set to ON, the RNC checks whether the inter-frequency or inter-RAT coverage-based handover measurement can be triggered after the RRC connection setup is completed (before the RB setup). If the switch is set to OFF, the RNC checks whether the inter-frequency or inter-RAT coverage-based handover measurement can be triggered after the RB setup is completed. Default Value OFF
SIGNAL_HO_SWITCH
ACT_SET_QUAL_SWITCH
The switch decides whether the RNC enables the active set quality measurement. If the switch is set to ON, the RNC enables the signal quality measurement to all the cells in active set after the RRC setup is completed (if the SIGNAL_HO_SWITCH is set to ON), or after the RB connection setup is completed (if the SIGNAL_HO_SWITCH is set to OFF). If the switch is set to OFF, the RNC does not initiate the active set quality measurement.
ON
INTER_RAT_PS_OUT_SWITCH
The switch decides whether the RNC will initiate inter-RAT measurement to trigger inter-RAT handover of the PS domain from the UTRAN.
ON
INTER_RAT_CS_OUT_SWITCH The switch decides whether the RNC will initiate inter-RAT measurement to trigger inter-RAT handover of the CS domain from the UTRAN.
ON
Issue 02 (2008-07-30)
3-21
For load or service based UMTS-to-GSM handover, the measurement report is event-triggered only. The measurement report mode is configured through the parameter Inter-RAT report mode. In periodical measurement report mode, the report interval also needs to be configured through the parameter Inter-RAT period report interval. The UE sends measurement reports periodically to the RNC according to the values of the report interval.
Event 3C
Triggering of Event 2D
Event 2D is triggered on the basis of the following formula: QUsed <= TUsed2d - H2d/2 where
l l
QUsed is the measurement value of the cell at the currently used frequency. TUsed2d is the absolute quality threshold of the cell at the currently used frequency. Based on the service type (CS , PS domain R99 service, or PS domain HSPA service) and measurement quantity (CPICH Ec/No or RSCP), this threshold can be configured through the following parameters:
3-22
Issue 02 (2008-07-30)
Inter-RAT R99 PS measure start Ec/No THD Inter-RAT H measure start Ec/No THD Inter-RAT CS measure start RSCP THD Inter-RAT R99 PS measure start RSCP THD Inter-RAT H measure start RSCP THD
H2d is 2D hysteresis, the hysteresis value of event 2D. For the PS and CS combined services, the threshold(s) for CS services is (are) used.
When the conditions for event 2D are met and maintained in time-to-trigger specified by the parameter 2D event trigger delay time, the UE sends the measurement report of event 2D.
Triggering of Event 2F
Event 2F is triggered on the basis of the following formula: QUsed >= TUsed2f + H2f/2 where
l l
QUsed is the measurement value of the cell at the currently used frequency. TUsed2f is the absolute quality threshold of the cell at the currently used frequency. Based on the service type (CS , PS domain R99 service, or PS domain HSPA service) and measurement quantity (CPICH Ec/No or RSCP), this threshold can be configured through the following parameters:
Inter-RAT CS measure stop Ec/No THD Inter-RAT R99 PS measure stop Ec/No THD Inter-RAT H measure stop Ec/No THD Inter-RAT CS measure stop RSCP THD Inter-RAT R99 PS measure stop RSCP THD Inter-RAT H measure stop RSCP THD
l l
H2f is 2F hysteresis, the hysteresis value of event 2F. For the PS and CS combined services, the threshold(s) for CS services is (are) used.
When the conditions for event 2F are met and maintained in time-to-trigger specified by 2F event trigger delay time, the UE sends the measurement report of event 2F.
Triggering of Event 3A
Event 3A is triggered on the basis of the following formula: QUsed <= TUsed - H3a/2 and MOtherRAT + CIOOtherRAT >= TOtherRAT + H3a/2 where
l l
QUsed is the measurement value of the cell at the currently used frequency. TUsed is the absolute quality threshold of the cell that uses the current frequency. Based on the service type (CS , PS domain R99 service, or PS domain HSPA service) and measurement quantity (CPICH Ec/No or RSCP) in the coverage-based handover, TUsed can be configured through the following parameters (These parameters are shared by the inter-freq and inter-RAT handover.):
Issue 02 (2008-07-30)
3-23
Inter-RAT R99 PS Used frequency trigger Ec/No THD Inter-RAT H Used frequency trigger Ec/No THD Inter-RAT CS Used frequency trigger RSCP THD Inter-RAT R99 PS Used frequency trigger RSCP THD Inter-RAT H Used frequency trigger RSCP THD
In the uplink QoS-based handover, based on the measurement quantity (CPICH Ec/No or RSCP), TUsed is configured as the maximum value according to 3GPP specifications, as described below:
If the measurement quantity is CPICH Ec/No, TUsed is configured as the maximum value 0 dB. If the measurement quantity is CPICH RSCP, TUsed is configured as the maximum value -25 dBm. If the measurement quantity is CPICH Ec/No, TUsed is configured as the maximum value 0 dB. If the measurement quantity is CPICH RSCP, based on the service type (CS, PS domain R99 service, or PS domain HSPA service), TUsed can be configured as one of the following sums:
Inter-RAT CS Used frequency trigger RSCP THD and Down Link RSCP Used-Freq THD Hyst Inter-RAT R99 PS Used frequency trigger RSCP THD and Down Link RSCP Used-Freq THD Hyst Inter-RAT H Used frequency trigger RSCP THD and Down Link RSCP Used-Freq THD Hyst
MOtherRAT is the measurement value of the cell (in another RAT) in the reporting range. CIOOtherRAT is the cell individual offset value of the cell (in another RAT) in the reporting range which is equal to the sum of Cell oriented Cell Individual Offset and Neighboring cell oriented CIO. TOtherRAT is the absolute inter-RAT handover threshold. Based on the service type (CS , PS domain R99 service, or PS domain HSPA service), this threshold can be configured through the following parameters:
l l
Inter-RAT H handover decision THD H3a is 3A hysteresis, the hysteresis value of event 3A.
For the PS and CS combined services, the threshold(s) for CS services is (are) used.
When the conditions for event 3A are met and maintained in time-to-trigger specified by 3A event trigger delay time the UE sends the measurement report of event 3A.
Triggering of Event 3C
Event 3C is triggered on the basis of the following formula: MOtherRAT + CIOOtherRAT >= TOtherRAT + H3c/2 where
3-24
Issue 02 (2008-07-30)
MOtherRAT is the measurement value of the cell (in another RAT) in the reporting range. CIOOtherRAT is the cell individual offset value of the cell (in another RAT) in the reporting range, which is equal to the sum of Cell oriented Cell Individual Offset and Neighboring cell oriented CIO. TOtherRAT is the absolute inter-RAT handover threshold. Based on the service type (CS , PS domain R99 service, or PS domain HSPA service), this threshold can be configured through the following parameters:
l l
Inter-RAT PS handover decision THD H3c is 3C hysteresis, the hysteresis value of event 3C. For the PS and CS combined services, the threshold(s) for CS services is (are) used.
When the conditions for event 3C are met and the delay requirement specified by the 3C event trigger delay time parameter can be satisfied, the UE sends the measurement report of event 3C.
If the switch is set to ON, measurement objects are chosen from the neighboring cells of all the cells in the active set. If the switch is set to OFF, measurement objects are chosen from the neighboring cells of the best cell.
l
The maximum number of neighboring cells is 32, no matter whether the measurement range is the neighboring cells of the active set or those of the monitored set. In default, the NCELL_COMBINE_SWITCH is set to ON.
When receiving an event 1A or 1C report, the RNC uses this algorithm to update the neighboring cell list. If the Radio Links (RLs) from the DRNC are added to the active set, the SRNC buffers the intra-frequency, inter-frequency, and inter-RAT neighboring cells list from the DRNC until the RLs from DRNC are removed from the active set. When receiving an event 1B or 1D report or an RL OUT-OF-SYNCHRONIZATION message from the NodeB, the RNC uses this algorithm to update the neighboring cell list.
Issue 02 (2008-07-30)
3-25
When The flag of the priority is switched to FALSE from TRUE, The priority of neighbor cell is cleared. When The flag of the priority is switched to TRUE from FALSE, the Priority of neighbor cell is set simultaneously.
----End
Event 2D/2F or periodical measurement takes both CPICH Ec/No and RSCP as measurement quantities. Event 3A takes CPICH Ec/No, CPICH RSCP, and Auto as measurement quantities.
In QoS-based UMTS-to-GSM handover, event 3A takes CPICH Ec/No and CPICH RSCP as measurement quantities.
The related parameter is 3A Measure Quantity and 3A Used-Freq Measure Quantity for Qos.
3-26
Issue 02 (2008-07-30)
The smoothed filter coefficient for layer 3 inter-RAT measurement is Inter-RAT filter coeff, and the smoothed filter coefficient for events 2D and 2F is 2D2F filter coeff.
Which type of the compressed mode to use is automatically decided by the RNC on the basis of the spreading factor used in the uplink or the downlink.
l l
When the downlink spreading factor is greater than or equal to the parameter DL SF threshold, the SF/2 approach is preferred. Otherwise, the high layer scheduling is used. When the uplink spreading factor is greater than or equal to the parameter UL SF threshold, the SF/2 approach is preferred. Otherwise, the high layer scheduling is used.
To initiate the high layer scheduling, set the following two switches:
l
If the algorithm switch CMCF_DL_HLS_SWITCH of CMCF Algorithm Switch parameter is set to ON, the DL high-layer scheduling for the compressed mode is allowed. If the algorithm switch CMCF_UL_HLS_SWITCH of CMCF Algorithm Switch parameter is set to ON, the UL high-layer scheduling for the compressed mode is allowed.
Issue 02 (2008-07-30)
3-27
CMCF_UL_PRECFG_TOLER ANCE_SWITCH
OFF
3-28
Issue 02 (2008-07-30)
Switch
Description
Default Value
OFF CMCF_WITHOUT_UE_CAP_R The UE can start the compressed mode on some frequency ranges that are not in EPORT_SWITCH the reported measurement range. Whether to start the compressed mode to take measurements on the frequencies within the frequency range depends on the switch. This switch is used to decide whether the UE need initiate the compressed mode to start the inter-frequency measurement for such frequencies. If the switch is set to ON for such frequencies, the UE must initiate the compressed mode to start the inter-frequency measurement. If the switch is set to OFF for such frequencies, the compressed mode need not be initiated before the inter-frequency measurement. Thus, the UE need not initiate the compressed mode to start the inter-frequency measurement.
Generally, it is recommended that the previously mentioned two switches are set to OFF.
The timer is specified by Inter-RAT measure timer length in inter-RAT handover based on coverage, load or service. The timer is specified by Down Link Qos Measure timer length/Up Link Qos Measure timer length in inter-RAT handover based on downlink/uplink QoS.
Issue 02 (2008-07-30)
3-29
Coverage-Based and QoS-Based UMTS-to-GSM Handover Decision and Execution Load-Based and Service-Based UMTS-to-GSM Handover Decision and Execution UMTS-to-GSM Handover Retry UMTS-to-GSM Multimedia Fallback UMTS-to-GSM Handover in the PS Domain with NACC or PS Handover
Mother_RAT is the measurement result of inter-RAT handover received by the RNC. CIOother_RAT is the cell individual offset value of the target cell. It is equal to the sum of Cell oriented Cell Individual Offset and Neighboring cell oriented CIO. Neigbhoring cell oriented CIO indicates the offset of the measurement cell relative to the best cell. Tother_RAT is the decision threshold of inter-RAT hard handover. Based on the service type (CS or PS service) and measurement quantity (CPICH Ec/No or RSCP), this threshold can be configured through the following parameters:
Inter-RAT CS handover decision THD Inter-RAT R99 PS handover decision THD Inter-RAT H handover decision THD
These thresholds are the same as the quality threshold of event 3A. For detailed information, see 3.4.3 UMTS-to-GSM Handover Measurement Events.
H is the inter-frequency hard handover hysteresis value Inter-RAT hysteresis. For the PS and CS combined services, one or more handover thresholds for CS services are used.
3-30
Issue 02 (2008-07-30)
Step 2 Start the evaluation of the cells that meet the quality requirement and start the time-to-trigger timer. If the measurement report meet the following formula and time-to-trigger timer doesn't expire, stop the time-to-trigger timer. Mother_RAT + CIOother_RAT < Tother_RAT - H/2 Where the parameters are the same as those previously described. Step 3 Select the cells in sequence, that is, from high quality cells to low quality ones, to initiate UMTS-to-GSM handover in the cells where the handover time-to-trigger timer expires. The length of the time-to-trigger timer is configured through the parameter Time to trigger for verified GSM cell (with BSIC acknowledged) or the parameter Time to trigger for non-verified GSM cell (with BSIC unacknowledged). ----End
Issue 02 (2008-07-30)
3-31
If the switch Send Load Info to GSM Ind is set to ON, the RELOCATION REQUIRED message includes the Information Element, Old BSS To New BSS Information that includes the load information of the 3G source cell. If the switch Send Load Info to GSM Ind is set to OFF, then the RELOCATION REQUIRED message does not include the Information Element, Old BSS To New BSS Information.
Step 2 When the RNC receives the RELOCATION COMMAND message from the 2G CN,
l
If the switch NCOV Reloc Ind based on GSM cell load is set to ON, the RNC obtains the load information of the 2G target cell by reading the Information Element, Inter-System Information Transparent Container, which is included in the RELOCATION COMMAND message.
If the 2G load is lower than CS domain Reloc GSM load THD (for CS service), or if the 2G load is lower than PS domain Reloc GSM load THD (for PS service), the RNC continues the inter-RAT handover procedure; otherwise, the RNC returns the Relocation Cancel message to the CN to cancel this inter-RAT handover and makes another handover attempt to the next candidate cell generated in the cell list based on inter-RAT measurement. If the Information Element, Inter-System Information Transparent Container, is not included in the RELOCATION COMMAND message, the load information of the 2G target cell is not considered and this inter-RAT handover is continued.
If the switch NCOV Reloc Ind based on GSM cell load is set to OFF, the RNC continues the inter-RAT handover procedure without considering the thresholds.
----End
Relocation Failure in Target CN/RNC or Target System, or Relocation not supported in Target RNC or Target System, or
3-32
Issue 02 (2008-07-30)
Otherwise, the related retry timer for the cell is started. After the retry timer expires, the UE makes handover attempts to the cell again until the retry number exceeds the maximum retry number. Step 3 If the RNC receives the RELOCATION COMMAND message, the handover on the Uu interface continues. Step 4 If the handover succeeds or the new event 3A or 3C report is received, the periodical retry is stopped. ----End
For CS services or CS and PS combined services, the HANDOVER FROM UTRAN signaling procedure on the Uu interface is performed only when the handover based on CS services is made. For a PS service or combined PS services, the CELL CHANGE ORDER FROM UTRAN or HANDOVER FROM UTRAN signaling procedure on the Uu interface is performed. If the HANDOVER FROM UTRAN FAILURE or CELL CHANGE ORDER FROM UTRAN FAILURE message is received, the handover on the Uu interface fails.
If the "Inter-RAT handover failure cause" in HANDOVER FROM UTRAN FAILURE message is "Configuration unacceptable", or if the "Inter-RAT change failure cause" in CELL CHANGE ORDER FROM UTRAN FAILURE message is "Configuration unacceptable", the RNC does not make a handover retry to the cell. Otherwise, the related retry timer for the cell is started. After the retry timer expires, the UE makes a handover attempt to the cell again until the retry number exceeds the maximum number. If the handover succeeds or the new event 3A or 3C report is received, the periodical retry is stopped. The retry timer and maximum retry number for coverage-based and QoS-based inter-RAT handover are:
l l
The retry timer and maximum retry number for load-based and service-based inter-RAT handover are:
l l
Issue 02 (2008-07-30)
3-33
Fallback: the process of changing multimedia services back to speech services during call setup. The RNC doesn't take part in the process. Therefore the detailed description of Fall back process is not given hereinafter. Service change: the process of changing multimedia services back to speech services during the call.
The two types are both referred to as multimedia fallback in this feature.
The RNC decides to send an inter-RAT handover request after receiving periodical measurement reports of event 1F, 3A, or 3C. The service is combined with a VP, and the "Alternative RAB Para" in the RAB ASSIGNMENT message is a valid AMR speech format.
3-34
Issue 02 (2008-07-30)
The procedure for the fallback service is described as follows: Step 1 The CN sends the SRNC a RANAP RAB ASSIGNMENT REQUIREMENT message to set up the VP service. The message includes the "Alternative RAB Para" that has QoS parameters required for setting up the speech service. Step 2 During UMTS-to-GSM handover, the SRNC sends a RANAP MODIFY REQUEST message to change the VP service to the AMR speech service. In the 3GPP R6 protocol, the Alternative RAB Configuration is also added to the RAB MODIFY REQUEST message, which enables the RNC to request the CN to change the VP service to the AMR speech service. Step 3 The MSC initiates the Bearer Capability (BC) negotiation with the UE. Step 4 After the negotiation is modified, the RNC is informed of performing service change. The multimedia fallback ends when the service change is completed. When the multimedia fallback ends, the RNC decides whether to perform the UMTS-to-GSM handover according to the current measurements reported by the UE. At the beginning of the service setup, the RNC saves the RAB Para and "Alternative RAB Para" in the RAB ASSIGNMENT or REQUEST RELOCATION REQUEST message. This makes preparations for notifying the CN of changing the VP service to the AMR speech service. The CN initiates the RAB reconfiguration to inform the two calling parties of performing the multimedia fallback. The multimedia fallback of the calling party is consistent with that of the called party. The single VP service falls back to the single AMR speech service. The multi-RAB service combined with VP falls back to the multi-RAB service combined with AMR. If the multimedia fallback succeeds, that is, the video phone in the service falls back to speech successfully, the inter-RAT handover is initiated. Otherwise, the inter-RAT handover fails. ----End
Issue 02 (2008-07-30)
3-35
The procedure is as follows: Step 1 After the SRNC receives a measurement report from the UE, the UE is reselected to the GERAN cell according to the decision. Step 2 The SRNC sends a RAN INFORMATION REQUEST message to the SGSN. Step 3 The SGSN forwards the message to the corresponding BSS. Step 4 The BSS sends a GERAN SI/PSI message to the SRNC via the SGSN. RAN INFORMATION message can either be On-demand (single report) or On-modification (multiple reports). Step 5 The SGSN forwards the report message to the SRNC through Iu interface. Step 6 If there are several report messages, the SRNC terminates reporting by the TERMINATION/END message. To enable the NACC function, do as follows:
l
Run the SET CORRMALGOSWITCH command to set PS_3G2G_CELLCHG_NACC_SWITCH of Handover Algorithm switch to ON.
3-36
Issue 02 (2008-07-30)
Run the ADD GSMCELL/MOD GSMCELL command to set Inter-RAT cell support RIM indicator to TRUE.
----End
Run the SET CORRMALGOSWITCH command to set PS_3G2G_RELOCATION_SWITCH of Handover Algorithm switch parameter to ON. Run the ADD GSMCELL/MOD GSMCELL command to set Inter-RAT cell support PS HO indicator to TRUE.
Issue 02 (2008-07-30)
3-37
If the switch Send Load Info to GSM Ind is set to ON, the Relocation Request Acknowledge message includes the Information Element, New BSS To Old BSS Information, which includes the load information of the 3G target cell. If the switch Send Load Info to GSM Ind is set to OFF, the Relocation Request Acknowledge message does not include the Information Element, New BSS To Old BSS Information.
Depending on the network requirement, GSM decides whether to use the load information sent to 3G for judgement. Step 2 When the RNC receives the RELOCATION REQUEST message from the 3G CN,
l l
If the 3G cell is not in the basic congestion state, the RNC continues the inter-RAT handover procedure. If the 3G cell is in the basic congestion state, the RNC returns RELOCATION FAILURE message to the CN to cancel the inter-RAT handover.
For the concept of "basic congestion", see Basic Congestion Triggering.
----End
3-38
Issue 02 (2008-07-30)
Both inter-frequency and inter-RAT neighboring cells are available. Inter-freq and Inter-RAT coexist switch is set to SIMINTERFREQRAT.
Inter-frequency measurement, which means that the RNC allows the UE to perform only this type of measurement. Inter-RAT measurement, which means that the RNC allows the UE to perform only this type of measurement. Concurrent inter-frequency and inter-RAT measurement, which means that the RNC allows the UE to perform both types of measurement in compressed mode at the same time.
During the concurrent inter-frequency and inter-RAT measurement, the values of the parameter InterFreq and InterRat coexist measure threshold choice for events 2D and 2F are chosen as follows:
l l
When the value COEXIST_MEAS_THD_CHOICE_INTERFREQ is chosen, the inter-frequency measurement threshold for event 2D is used. When the value COEXIST_MEAS_THD_CHOICE_INTERRAT is chosen, the inter-RAT measurement threshold for event 2D is used.
UMTS-to-GSM Handover in CS Domain UMTS to GSM Handover in PS Domain UMTS-to-GSM Handover in Both CS Domain and PS Domain GSM-to-UMTS Handover in CS Domain GSM-to-UMTS Handover in PS Domain
Issue 02 (2008-07-30)
3-39
The signaling procedures are described as follows: Step 1 The SRNC sends the 3G MSC a RANAP message RELOCATION REQUIRED if the condition of inter-RAT outgoing handover is met. Step 2 As indicated in the received message, the 3G MSC forwards this request to the 2G MSC on the MAP/E interface through a MAP message PREPARE HANDOVER. Step 3 The 2G MSC forwards the request to the BSC. The message shown in the figure is for reference only and is subject to the actual condition of the GSM. Step 4 The BSC responds to this request. The message shown in the figure is for reference only and is subject to the actual condition of the GSM. Step 5 Once the initial procedures are completed in the 2G MSC/BSS, the 2G MSC returns a MAP/E message PREPARE HANDOVER RESPONSE. Step 6 The 3G MSC sends the SRNC a RANAP message RELOCATION COMMAND.
3-40
Issue 02 (2008-07-30)
Step 7 The SRNC sends the UE an RRC message HANDOVER FROM UTRAN through the existing RRC connection. This message may include information from one or several other systems. Step 8 The BSC performs handover detection. The figure does not show such procedures as GSM BSS synchronization. The message shown in the figure is for reference only and is subject to the actual condition of the GSM. Step 9 The UE sends the BSC a HANDOVER COMPLETE message. Step 10 The BSC sends the MSC a HANDOVER COMPLETE message. The message shown in the figure is for reference only and is subject to the actual condition of the GSM. Step 11 After detecting the UE in the coverage area of the GSM, the MSC sends the CN a MAP/E message SEND END SIGNAL REQUEST. Step 12 The CN sends the former SRNC an IU RELEASE COMMAND message, requesting the former SRNC to release the allocated resource. Step 13 After the bearer resource is released in the UMTS, the former SRNC sends the CN an IU RELEASE COMPLETE message. Step 14 After the call ends, the CN sends the MSC a MAP/E message SEND END SIGNAL RESPONSE. ----End
When the UE is in CELL_DCH state The UMTS-to-GSM handover in the PS domain is triggered after the UTRAN sends a CELL CHANGE ORDER FROM UTRAN message.
When the UE is in CELL_FACH, CELL_PCH, or URA_PCH state The UMTS-to-GSM handover in the PS domain is triggered through the cell reselection.
The following figure shows an example of handover for the UE in CELL_FACH, CELL_PCH, or URA_PCH state.
Issue 02 (2008-07-30)
3-41
The signaling procedures are described as follows: Step 1 The UE in CELL_DCH state or the UTRAN (when the UE is in CELL_FACH state) decides to initiate an inter-RAT handover in the PS domain to hand over the UE to a new GSM cell and stop the data transmission between the UE and the network. Step 2 The UE sends a ROUTING AREA UPDATE REQUEST message to the 2G SGSN. The Update Type in the message indicates RA update, combined RA/LA update, or combined
3-42
Issue 02 (2008-07-30)
RA/LA update with IMSI attach. The BSS adds the CGI including the RAC and LAC of the cell to the received message before forwarding the message to a new 2G SGSN. Step 3 The new 2G SGSN sends an SGSN CONTEXT REQUEST message to the old 3G SGSN to obtain the MM and PDP contexts. The old 3G SGSN validates the old P-TMSI Signature. If the old P-TMSI Signature is valid, the old 3G SGSN starts a timer. Otherwise, the old 3G SGSN responds with an error cause. Step 4 If the UE stays in connected mode before handover, the old 3G SGSN sends an SRNS CONTEXT REQUEST message. After receiving this message, the SRNS buffers the PDUs, stops sending the PDUs to the UE, and sends an SRNS CONTEXT RESPONSE message to the old 3G SGSN. Step 5 The old 3G SGSN sends an SGSN CONTEXT RESPONSE message to the 2G SGSN, including the MM and PDP contexts. Step 6 The security functions can be executed. Step 7 The new 2G SGSN sends an SGSN CONTEXT ACKNOWLEDGE message to the old 3G SGSN. This informs the old 3G SGSN that the new 2G SGSN is ready to receive the PDUs belonging to the activated PDP contexts. Step 8 The old 3G SGSN sends a DATA FORWARD COMMAND message to the SRNS. The SRNS starts a data-forwarding timer and sends the buffered PDUs to the old 3G SGSN. Step 9 The old 3G SGSN tunnels the GTP PDUs to the new 2G SGSN. In the PDUs, the sequence numbers in the GTP header remain unchanged. Step 10 The new 2G SGSN sends an UPDATE PDP CONTEXT REQUEST message to each related GGSN. Each GGSN sends an UPDATE PDP CONTEXT RESPONSE message after updating its PDP context fields. Step 11 The new 2G SGSN sends an UPDATE GPRS LOCATION message, requesting the HLR to modify the SGSN number. Step 12 The HLR sends a CANCEL LOCATION message to the old 3G SGSN. The old 3G SGSN responds with a CANCEL LOCATION ACK message. After the timer expires, the old 3G SGSN removes the MM and PDP contexts. Step 13 The old 3G SGSN sends an IU RELEASE COMMAND message to the SRNS. After the data-forwarding timer expires, the SRNS responds with an IU RELEASE COMPLETE message. Step 14 The HLR sends an INSERT SUBSCRIBER DATA message to the new 2G SGSN. The 2G SGSN constructs an MM context and PDP contexts for the UE and returns an INSERT SUBSCRIBER DATA ACK message to the HLR. Step 15 The HLR sends an UPDATE GPRS LOCATION ACK message to the new 2G SGSN. Step 16 If the association has to be established, the new 2G SGSN sends a LOCATION UPDATE REQUEST message to the VLR. The VLR stores the SGSN number for creating or updating the association. Step 17 If the subscriber data in the VLR is marked as not confirmed by the HLR, the new VLR informs the HLR. The HLR cancels the old VLR and inserts subscriber data in the new VLR. 1. 2. The new VLR sends an UPDATE LOCATION message to the HLR. The HLR cancels the data in the old VLR by sending a CANCEL LOCATION message to the old VLR.
Issue 02 (2008-07-30)
3-43
3. 4. 5. 6.
The old VLR acknowledges the message by responding with a CANCEL LOCATION ACK message. The HLR sends an INSERT SUBSCRIBER DATA message to the new VLR. The new VLR acknowledges the message by responding with an INSERT SUBSCRIBER DATA ACK message. The HLR responds with a UPDATE LOCATION ACK message to the new VLR.
Step 18 The new VLR allocates a new TMSI and responds with a LOCATION UPDATE ACCEPT message to the 2G SGSN. Step 19 The new 2G SGSN checks the presence of the MS in the new RA. If all checks are successful, the new 2G SGSN constructs the MM and PDP contexts for the MS. A logical link is established between the new 2G SGSN and the UE. The 2G SGSN responds to the UE with a ROUTING AREA UPDATE ACCEPT message. Step 20 The UE acknowledges the new P-TMSI by returning a ROUTING AREA UPDATE COMPLETE message, including all PDUs successfully sent to the UE before the routing area update procedure. Step 21 The new 2G SGSN sends a TMSI REALLOCATION COMPLETE message to the new VLR if the UE confirms the VLR TMSI. Step 22 The 2G SGSN and the BSS perform the BSS PACKET FLOW CONTEXT procedure. ----End
3-44
Issue 02 (2008-07-30)
The signaling procedures are described as follows: Step 1 The UE in connection with both CS and PS domains performs the UMTS-to-GSM handover, during which the CS service is handed over to the GSM. Step 2 The UE sends a SUSPEND message to the BSS. Step 3 The BSS forwards the SUSPEND message to the SGSN. The SGSN sends an SRNS CONTEXT REQUEST message to the SRNS, requesting the SRNS to stop sending downlink PDUs. After receiving the message, the SRNS buffers downlink PDUs and responds to the SGSN with an SRNS CONTEXT RESPONSE message. The SGSN returns a SUSPEND ACK message to the BSS. Step 4 When the CS connection is terminated, the BSS may send a RESUME message to the SGSN. However, resume is impossible since the radio access system has changed. Therefore, the SGSN acknowledges the resume through a RESUME NACK message. Step 5 The BSS sends an RR message CHANNEL RELEASE to the UE, indicating that the BSS fails to request the SGSN to resume the GPRS service for the UE. Step 6 The UE sends a ROUTING AREA UPDATE REQUEST message to the SGSN to resume the GPRS service. The update mode depends on the network operation mode in use. ----End
Issue 02 (2008-07-30)
3-45
The signaling procedures are described as follows: Step 1 The UE in connection with both CS and PS domains performs the UMTS-to-GSM handover, during which the CS service is handed over to the GSM. Step 2 The UE sends a SUSPEND message to the BSS. Step 3 The BSS forwards the SUSPEND message to the 2G SGSN. The 2G SGSN sends a SUSPEND ACK message to the BSS. Step 4 After the CS connection is terminated, the BSS may send a RESUME message to the 2G SGSN. Since the resume is not required for the 3G SGSN, the 2G SGSN acknowledges the resume through a RESUME NACK message. Step 5 The BSS sends an RR message CHANNEL RELEASE to the UE, indicating that the BSS fails to request the SGSN to resume the GPRS service for the UE. Step 6 The UE sends a ROUTING AREA UPDATE REQUEST message to the SGSN to resume the GPRS service. The update mode depends on the network operation mode in use. ----End
3-46
Issue 02 (2008-07-30)
The signaling procedures are described as follows: Step 1 The GSM decides to hand over the UE to the UMTS based on the measurement. The BSC sends a HANDOVER REQUIRED message to the 2G MSC, requesting the UMTS to prepare for handover. Step 2 The 2G MSC forwards a MAP/E message PREPARE HANDOVER to the 3G MSC. Step 3 The 3G MSC sends a RELOCATION REQUEST message to the RNC. Step 4 After preparation, the RNC sends a RELOCATION REQUEST ACK message to 3G MSC. Step 5 The 3G MSC sends a MAP/E message PREPARE HANDOVER RESPONSE to the 2G MSC. Step 6 The 2G MSC sends a HANDOVER COMMAND message as a response to the initial request of the BSC. Step 7 If the radio link exists, the BSC sends an INTER-SYSTEM TO UTRAN HANDOVER COMMAND message to the UE, instructing the GSM-to-UMTS handover. Step 8 When detecting the UE, the RNC sends a RELOCATION DETECT message to the 3G MSC. Step 9 After the handover, the UE sends a HANDOVER COMPLETE message to the RNC. Step 10 The RNC sends a RELOCATION COMPLETE message to the 3G MSC.
Issue 02 (2008-07-30)
3-47
Step 11 When detecting that the UE is in the coverage area of the UMTS, the 3G MSC sends a SEND END SIGNAL REQUEST message to the 2G MSC, indicating that the handover is completed and the GSM resources occupied by the UE can be released. Step 12 The 2G MSC sends a CLEAR COMMAND message to the BSC, requesting the BSC to release related resources. Step 13 After the release, the GSM BSC sends a CLEAR COMPLETE message to the 2G MSC. Step 14 The 2G MSC sends a SEND END SIGNAL RESPONSE message to the 3G MSC. ----End
3-48
Issue 02 (2008-07-30)
The signaling procedures are described as follows: Step 1 The GSM decides to perform an inter-RAT handover in the PS domain and stops the data transmission between the UE and the network. Step 2 The UE sends a ROUTING AREA UPDATE REQUEST message to the 3G SGSN. The Update Type parameter indicates RA update, combined RA/LA update, or combined RA/LA
Issue 02 (2008-07-30)
3-49
update with IMSI attach. The SRNC adds the RAC and LAC of the cell to the received message before forwarding the message to the new 3G SGSN. Step 3 The 3G SGSN obtains the address of the old 2G SGSN, and then sends an SGSN CONTEXT REQUEST message to the old 2G SGSN to construct the MM and PDP contexts for the UE. The old 2G SGSN validates the P-TMSI signature of the UE. If the signature is valid or is validated by the 3G SGSN, the 2G SGSN starts a timer. Step 4 The old 2G SGSN responds with an SGSN CONTEXT RESPONSE message, including the MM and PDP contexts. Step 5 The security functions can be executed. Step 6 The 3G SGSN sends an SGSN CONTEXT ACKNOWLEDGE message to the 2G SGSN. The message informs the 2G SGSN that the 3G SGSN is ready to receive the PDUs belonging to the activated PDP contexts. Step 7 The 2G SGSN copies and buffers N-PDUs, and then sends them to the 3G SGSN. Before the timer expires, if there are other N-PDUs from the GGSN, the 2G SGSN copies and sends them to the 3G SGSN. After the timer expires, the 2G SGSN does not send N-PDUs to the 3G SGSN any more. Step 8 The 3G SGSN sends an UPDATE PDP CONTEXT REQUEST message to each related GGSN. Each GGSN updates its PDP context and responds with an UPDATE PDP CONTEXT RESPONSE message. Step 9 The 3G SGSN sends an UPDATE GPRS LOCATION message to the HLR. Step 10 The HLR sends a CANCEL LOCATION message to the 2G SGSN. After the timer expires, the 2G SGSN removes the MM and PDP contexts. The 2G SGSN responds with a CANCEL LOCATION ACK message. Step 11 The HLR sends an INSERT SUBSCRIBER DATA message to the 3G SGSN. The 3G SGSN constructs an MM context and sends an INSERT SUBSCRIBER DATA ACK message to the HLR. Step 12 The HLR sends an UPDATE GPRS LOCATION BY RETURNING AN UPDATE GPRS LOCATION ACK message to the 3G SGSN. Step 13 If the association has to be established, that is, if the Update Type parameter indicates a combined RA/LA update with IMSI attach requested, or if the LA changed with the RA update, the 2G SGSN sends a LOCATION UPDATE REQUEST message to the VLR. The VLR stores the SGSN number for creating or updating the association. Step 14 If the subscriber data in the VLR is marked as not confirmed by the HLR, the new VLR informs the HLR. The HLR cancels the old VLR and inserts subscriber data in the new VLR. 1. 2. 3. 4. 5. 6. The new VLR sends an UPDATE LOCATION message to the HLR. The HLR cancels the data in the old VLR by sending a CANCEL LOCATION message to the old VLR. The old VLR acknowledges the message by responding with a CANCEL LOCATION ACK message. The HLR sends an INSERT SUBSCRIBER DATA message to the new VLR. The new VLR acknowledges the message by responding with an INSERT SUBSCRIBER DATA ACK message. The HLR responds with an UPDATE LOCATION ACK message to the new VLR.
3-50
Issue 02 (2008-07-30)
Step 15 The new VLR allocates a new TMSI and notifies the 3G SGSN by sending a LOCATION UPDATE ACCEPT message. Step 16 The 3G SGSN checks the presence of the MS in the new RA. If all checks are successful, the 3G SGSN constructs MM and PDP contexts for the MS. The 3G SGSN sends a ROUTING AREA UPDATE ACCEPT message to the UE. Step 17 The UE sends a ROUTING AREA UPDATE COMPLETE message to confirm the allocated P-TMSI. Step 18 The 3G SGSN sends a TMSI REALLOCATION COMPLETE message to the new VLR. Step 19 If the UE has uplink data or signaling to send, the UE sends a SERVICE REQUEST message to the SGSN. The service type indicates the required service (data or signaling). Step 20 The 3G SGSN sends a RAB ASSIGNMENT REQUEST message to the SRNS. The SRNS sends a RADIO BEARER SETUP REQUEST message to the UE. The UE responds with a RADIO BEARER SETUP COMPLETE message. The SRNS sends a RAB ASSIGNMENT RESPONSE message to the SGSN. The SRNS sends N-PDUs to the UE. ----End
Issue 02 (2008-07-30)
3-51
Inter-RAT Handover Parameters provides information on the effective level and configuration of the parameters related to the feature. Table 4-1 Parameters related to Inter-RAT Handover Parameter Name Parameter ID Effective Level Cell(ADD CELLINTERRATHO COV) 2D event trigger delay time TrigTime2D RNC(SET INTERRATHOCOV) Cell(ADD CELLINTERRATHO COV) RNC(SET INTERRATHOCOV) Cell(ADD CELLINTERRATHO COV) RNC(SET INTERRATHOCOV) Cell(ADD CELLINTERRATHO COV) 2F event trigger delay time TrigTime2F RNC(SET INTERRATHOCOV) Cell(ADD CELLINTERRATHO COV) RNC(SET INTERRATHOCOV) Cell(ADD CELLINTERRATHO COV) RNC RNC Configuration on ...
2D hysteresis
HystFor2D
RNC
FilterCoefOf2D2F
RNC
HystFor2F
RNC
AmntOfRpt3A
RNC
Issue 02 (2008-07-30)
4-1
Parameter Name
Parameter ID
Effective Level RNC(SET INTERRATHOCOV) Cell(ADD CELLINTERRATHO COV) RNC(SET INTERRATHOCOV) Cell(ADD CELLINTERRATHO COV) RNC(SET INTERRATHOCOV) Cell(ADD CELLINTERRATHO COV) RNC(SET INTERRATHOCOV) Cell(ADD CELLINTERRATHO COV) RNC(SET INTERRATHOCOV) Cell(ADD CELLQOSHO) RNC(SET QOSHO) Cell(ADD CELLINTERRATHO NCOV) RNC(SET INTERRATHONCO V) Cell(ADD CELLINTERRATHO NCOV) RNC(SET INTERRATHONCO V) Cell(ADD CELLINTERRATHO NCOV) RNC(SET INTERRATHONCO V) Cell(ADD CELLINTERRATHO NCOV)
Configuration on ...
PeriodFor3A
RNC
TrigTime3A
RNC
3A hysteresis
Hystfor3A
RNC
RNC
RNC
AmntOfRpt3C
RNC
PeriodFor3C
RNC
TrigTime3C
RNC
3C hysteresis
Hystfor3C
RNC
4-2
Issue 02 (2008-07-30)
Parameter Name
Parameter ID
Effective Level RNC(SET INTERRATHONCO V) Cell(ADD CELLINTERRATHO NCOV) Cell(ADD CELLINTERRATHO COV) RNC(SET INTERRATHONCO V) RNC(SET INTERRATHOCOV) Cell(ADD CELLSETUP) RNC(ADD NRNCCELL) RNC(SET CMCF) RNC(SET CORRMALGOSWIT CH) Cell(ADD CELLINTERRATHO NCOV) RNC(SET INTERRATHONCO V) RNC(SET CMCF) Cell(ADD CELLCMCF) RNC(SET CMCF) RNC(SET CMCF) Cell(ADD CELLQOSHO) RNC(SET QOSHO) Cell(ADD CELLQOSHO) RNC(SET QOSHO) RNC(SET CORRMALGOSWIT CH)
Configuration on ...
BSICVerify
RNC
Cell oriented Cell Individual Offset CM permission ind on HSDPA CMCF Algorithm Switch
CIO HsdpaCMPermissionIn d
RNC RNC
CmcfSwitch
RNC
CSHOOut2GloadThd DlSFLimitCMInd
RNC RNC
DL SF threshold Dl SF threshold to limit CM Down Link Qos Measure timer length Down Link RSCP Used-Freq THD Hyst Handover Algorithm Switch
DlSFTurnPoint LimitCMDlSFThd
RNC RNC
DLQosMcTimerLen
RNC
DlRscpQosHyst
RNC
HoSwitch
RNC
Issue 02 (2008-07-30)
4-3
Parameter Name InterFreq and InterRat coexist measure threshold choice Inter-freq and Inter-RAT coexist switch
Parameter ID
Effective Level Cell(ADD CELLHOCOMM) RNC(SET HOCOMM) Cell(ADD CELLHOCOMM) Cell(ADD CELLINTERRATHO COV) RNC(SET INTERRATHOCOV) Cell(ADD CELLINTERRATHO COV) RNC(SET INTERRATHOCOV) Cell(ADD CELLINTERRATHO COV) RNC(SET INTERRATHOCOV) Cell(ADD CELLINTERRATHO COV) RNC(SET INTERRATHOCOV) Cell(ADD CELLINTERRATHO COV) RNC(SET INTERRATHOCOV) Cell(ADD CELLINTERRATHO COV) RNC(SET INTERRATHOCOV) Cell(ADD GSMCELL) Cell(ADD GSMCELL) Cell(ADD GSMCELL)
Configuration on ...
CoexistMeasThdChoic e
RNC
InterFreqRATSwitch
RNC
UsedFreqCSThdEcN0
RNC
UsedFreqCSThdRSCP
RNC
UsedFreqHThdEcN0
RNC
UsedFreqHThdRSCP
RNC
UsedFreqR99PsThdEc N0
RNC
Inter-RAT R99 PS Used frequency trigger RSCP THD Inter-RAT cell support PS HO indicator Inter-RAT cell support RIM indicator Inter-RAT cell type
UsedFreqR99PsThdRS CP
RNC
SuppPSHOFlag
RNC
SuppRIMFlag RatCellType
RNC RNC
4-4
Issue 02 (2008-07-30)
Parameter Name
Parameter ID
Configuration on ...
TargetRatCsThd
RNC(SET INTERRATHOCOV) Cell(ADD CELLINTERRATHO NCOV) RNC(SET INTERRATHONCO V) Cell(ADD CELLHOCOMM) Cell(ADD CELLINTERRATHO COV) RNC(SET INTERRATHOCOV) Cell(ADD CELLINTERRATHO COV) RNC(SET INTERRATHOCOV) Cell(ADD CELLINTERRATHO COV) RNC(SET INTERRATHOCOV) Cell(ADD CELLINTERRATHO COV) RNC(SET INTERRATHOCOV) Cell(ADD CELLINTERRATHO COV) RNC(SET INTERRATHOCOV) Cell(ADD CELLINTERRATHO NCOV) RNC(SET INTERRATHONCO V) Cell(ADD CELLINTERRATHO
RNC
RNC RNC
InterRATCSThd2DEc N0
RNC
InterRATCSThd2DRS CP
RNC
InterRATCSThd2FEc N0
RNC
InterRATCSThd2FRS CP
RNC
InterRATFilterCoef TargetRatHThd
RNC RNC
Issue 02 (2008-07-30)
4-5
Parameter ID
Effective Level COV) RNC(SET INTERRATHOCOV) Cell(ADD CELLINTERRATHO COV) RNC(SET INTERRATHOCOV) Cell(ADD CELLINTERRATHO COV) RNC(SET INTERRATHOCOV) Cell(ADD CELLINTERRATHO COV) RNC(SET INTERRATHOCOV) Cell(ADD CELLINTERRATHO COV) RNC(SET INTERRATHOCOV) Cell(ADD CELLINTERRATHO NCOV) RNC(SET INTERRATHONCO V) Cell(ADD CELLINTERRATHO COV) RNC(SET INTERRATHOCOV) Cell(ADD CELLINTERRATHO COV) RNC(SET INTERRATHOCOV) Cell(ADD CELLINTERRATHO NCOV) RNC(SET INTERRATHONCO V) Cell(ADD CELLINTERRATHO
Configuration on ...
InterRATHThd2DEcN 0
RNC
InterRATHThd2DRSC P
RNC
InterRATHThd2FEcN 0
RNC
InterRATHThd2FRSC P
RNC
InterRATHOAttempts
RNC
Inter-RAT hysteresis
HystforInterRAT
RNC
InterRATMeasTime InterRATPingPongHys
RNC RNC
Issue 02 (2008-07-30)
Parameter ID t
Effective Level COV) RNC(SET INTERRATHOCOV) Cell(ADD CELLINTERRATHO COV) RNC(SET INTERRATHOCOV) Cell(ADD CELLINTERRATHO NCOV)
Configuration on ...
InterRATPingPongTim er
RNC
InterRATNCovHOPST hd PSServiceHOSwitch
RNC(SET INTERRATHONCO V) Cell(ADD CELLHOCOMM) Cell(ADD CELLINTERRATHO COV) RNC(SET INTERRATHOCOV) Cell(ADD CELLINTERRATHO COV) RNC(SET INTERRATHOCOV) Cell(ADD CELLINTERRATHO COV) RNC(SET INTERRATHOCOV) Cell(ADD CELLINTERRATHO COV) RNC(SET INTERRATHOCOV) Cell(ADD CELLINTERRATHO COV) RNC(SET INTERRATHOCOV) Cell(ADD CELLINTERRATHO COV) RNC(SET
RNC RNC
TargetRatR99PsThd
RNC
InterRATR99PsThd2D EcN0
RNC
InterRATR99PsThd2D RSCP
RNC
InterRATR99PsThd2F EcN0
RNC
InterRATR99PsThd2F RSCP
RNC
InterRatReportMode
RNC
Issue 02 (2008-07-30)
4-7
Parameter Name
Parameter ID
Configuration on ...
NcovHoOn2GldInd
RNC
CIOOffset
Cell(ADD GSMNCELL) Cell(ADD CELLINTERRATHO NCOV) RNC(SET INTERRATHONCO V) RNC(SET INTERRATHONCO V) Cell(ADD INTERFREQNCELL ) Cell(ADD INTRAFREQNCELL ) Cell(ADD GSMNCELL) Cell(ADD INTRAFREQNCELL ) RNC(SET INTERRATHOCOV)
RNC
PS domain Reloc GSM load THD Send Load Info to GSM Ind
PSHOOut2GloadThd
RNC
SndLdInfo2GsmInd
RNC
NPrioFlag
RNC
NPrio
RNC
TimeToTrigForNonVe rify
Cell(ADD CELLINTERRATHO COV) Cell(ADD CELLINTERRATHO COV) RNC(SET INTERRATHOCOV) Cell(ADD CELLCMCF) RNC(SET CMCF)
RNC
TimeToTrigForVerify
RNC
UL SF threshold
UlSFTurnPoint
RNC
4-8
Issue 02 (2008-07-30)
Parameter Name
Parameter ID
Effective Level Cell(ADD CELLQOSHO) RNC(SET QOSHO) Cell(ADD CELLINTERFREQH OCOV) RNC(SET INTERFREQHOCO V) Cell(ADD CELLINTERRATHO COV) RNC(SET INTERRATHOCOV)
Configuration on ...
ULQosMcTimerLen
RNC
WeightForUsedFreq
RNC
Issue 02 (2008-07-30)
4-9
5 Reference Documents
5
l l l l l l
Reference Documents
Inter-RAT Handover Reference Documents lists the reference documents related to the feature. 3GPP TS 23.122: Non Access Stratum functions related to Mobile Station (MS) in idle mode 3GPP TS 24.008: Mobile radio interface layer 3 specification; Core Network Protocols Stage 3 3GPP TS 25.304: UE Procedures in Idle Mode and Procedures for Cell Reselection in Connected Mode 3GPP TS 25.331: RRC Protocol Specification 3GPP TS 23.060: General Packet Radio Service (GPRS); Service description 3GPP TS 25.931: UTRAN Functions, Examples on Signalling Procedures
Issue 02 (2008-07-30)
5-1