3GPP2 TSG-A.

2 IOS Features and Requirements

TITLE: Intergenerational Handoff for Voice Services rev 3. SOURCE:
Samsung Electronics Co., Ltd. Bill Semper

(972) 761-7996 (972) 761-7909 (fax) bsemper@sta.samsung.com

ABSTRACT: This contribution provides call flow scenarios for inter-generational voice handoff between 2G and 3G base stations. RECOMMENDATION: Accept into IOS V5.0 Features Document baseline text.

Samsung Electronics grants a free, irrevocable license to 3GPP2 and its Organizational Partners to incorporate text or other copyrightable material contained in the contribution and any modifications thereof in the creation of 3GPP2 publications; to copyright and sell in Organizational Partner's name any Organizational Partner's standards publication even though it may include all or portions of this contribution; and at the Organizational Partner's sole discretion to permit others to reproduce in whole or in part such contribution or the resulting Organizational Partner's standards publication. Samsung Electronics is also willing to grant licenses under such contributor copyrights to third parties on reasonable, non-discriminatory terms and conditions for purpose of practicing an Organizational Partners standard which incorporates this contribution. This document has been prepared by Samsung Electronics to assist the development of specifications by 3GPP2. It is proposed to the Committee as a basis for discussion and is not to be construed as a binding proposal on Samsung Electronics. Samsung Electronics specifically reserves the right to amend or modify the material contained herein and to any intellectual property of Samsung Electronics other than provided in the copyright statement above.

1.0

Overview

This contribution proposes two new call flows for inter-generational voice handoff. Intergenerational voice handoff is a growing concern as 3G 1xRTT networks are being deployed. Samsung feels that adding these call flows to the IOS would help vendors and operators manage the integration of 2G and 3G systems. 2.0 Proposed Text Changes

All text changes cited below apply to IOS V4.3 Baseline Text.

2.19.5 Intergeneration Packet Data Handoff

Intergenerational handoff is defined to be the handoff of a mobile between a system that supports packet data service as specified inis based on Error! Reference source not found.[11] to Error! Reference source not found.[17] (referred to as 3G in this section) and a system that supports a packet data service asthe air interface specified in Error! Reference source not found.[10] (referred to as 2G in this section). Note that packet data service based on the Error! Reference source not found.[10] air interface standard is not explicitly supported in this version of the standard. A packet data service session needs to be re-established following an intergeneration packet data handoff. Refer to section 3.19.5 for details on this feature.

[] 3.19.5 Intergeneration Packet Data Handoff This section provides exa mple call flows indicating how hard handoff between 2G systems (defined as a system that only supports the air interface defined in [10]) and 3G systems (defined as a system that supports the air interface defined in [1]-[6]) can be accomplished. Throughout this sectionFor all packet data handoff examples (sections 3.19.5.1-5), it is assumed that that MS is capable of supporting both 3G and 2G packet data services and both air interfaces as defined in [1-6] and [10]. For voice handoff examples (sections 3.19.5.6-7), the mobile is assumed to be either 3G (compliant to {1]-[6] and therefore backward compatible with [10]) or 2G (compliant with [10] only). Throughout this section, 3G BS refers to a base station that supports the cdma2000 air interface (as defined in [1]-[6]) and is connected to an MSC via an A1/A2 interface as defined in [14]. The term 2G BS refers to a base station that supports the air interface defined in [10], and is connected to an MSC. The interface between the 2G BS and the MSC may or may not be based on a previous version of the IOS.
3.19.5.1 Packet Data Hard Handoff from 2G System to 3G System

(also change figure title)

3.19.5.2 Packet Data Hard Handoff from 3G System to 2G System

(also change figure title)

3.19.5.3 Intra-PCF Packet Data Hard Handoff from 3G System to 2G System

(also change figure title)

3.19.5.4 Packet Data Dormant Handoff from 2G System to 3G System

[]
3.19.5.5 Packet Data Dormant Handoff from 3G System to 2G System

[]

3.19.5.6

Voice Handoff from 3G System to 2G System

The following call flow diagram provides an illustration for a successful intergenerational hard handoff of a voice call from a 3G base station to a 2G base station. It is assumed that the call is not in inter-BS soft/softer handoff prior to the hard handoff, and thus no A3 connections need to be removed. In this call flow, the box marked MSC may represent one or two MSCs. In the case of inter-MSC handoff, ANSI-41 signaling is not specified. The message flows between the MSC and the 2G BS are not required.
MS 3G BS Handoff Required (Handoff Request) T7 Null forward traffic channel frames b T11 c (Handoff Request Ack) Handoff Command Handoff Direction Message f MS Ack Order Twaitho x Handoff Commenced Reverse Traffic Channel Frames or Traffic Channel Preamble Handoff Completion Message j (T9) g h i d e MSC 2G BS Time Comment

BS Ack Order
T306 Clear Command Clear Complete T315 (Handoff Complete)

k l m n

Figure 3.19.5.6-1 Successful Voice Intergenerational Hard Handoff 3G to 2G a. Based on an MS report that it crossed a network specified threshold for signal strength or for other reasons, the 3G BS recommends a hard handoff to one or more cells in the domain of the 2G BS. The 3G BS sends a Handoff Required message with the list of cells to the MSC and starts timer T . The 3G BS 7 formats the Handoff Required message as shown in [A-Interface], including the IS-2000 Channel Identity information element. The MSC shall then properly format the equivalent of the Handoff Request message sent to the 2G BS. The MSC sends the equivalent of a Handoff Request message to the target BS with the equivalent of the IS-95 Channel Identity element present, since the hard handoff bit was set and/or the Handoff Type element in the Handoff Required message indicated hard handoff. The MSC starts timer T11 . Upon receipt of this message from the MSC, the 2G BS allocates appropriate radio resources as specified in the message and connects the call. The 2G BS sends null forward traffic channel frames to the MS.

b.

c.

d.

The 2G BS sends the equivalent of a Handoff Request Acknowledge message to the MSC and starts the equivalent of timer T9 to wait for arrival of the MS on its radio channel. The MSC stops timer T upon the receipt of this 11 message. If the service option being requested in the handoff is not available at the 2G BS, the 2G BS rejects the handoff request (see procedures for Handoff Failure message in [A-Interface]). The MSC prepares to switch from the 3G BS to the 2G BS and sends a Handoff Command to the 3G BS. This message contains the IS-95 Channel Identity information element, and does not contain any IS-2000 related information elements. The 3G BS stops timer T7 upon receipt of this message. The source BS sends the handoff direction message to the MS across the air interface. If the MS was operating in a 3G radio configuration (a radio configuration greater than or equal to 3), the 3G BS directs the MS to change radio configurations to either RC1 or RC2 (depending on the service option being handed off). If the MS is allowed to return to the 3G BS, then timer Twaitho is also started by the 3G BS. The MS may acknowledge the handoff direction message by sending an MS Ack Order to the 3G BS. If the handoff direction message is sent using quick repeats, the 3G BS might not request an acknowledgment from the MS.
1

e.

f.

g.

h.

The 3G BS sends a Handoff Commenced message to the MSC to notify it that the MS has been ordered to move to the 2G BS channel. The 3G BS starts timer T306 to await the Clear Command message from the MSC. If timer Twaitho has been started, the 3G BS shall wait for that timer to expire before sending the Handoff Co mmenced message. The MS sends reverse traffic channel frames or the traffic channel preamble to the target cell(s). The MS sends a Handoff Completion Message to the 2G BS. The 2G BS sends the BS Ack Order to the MS over the air interface. The 2G BS stops the equivalent of timer T9 . The 2G BS sends the equivalent of the Handoff Complete message to the MSC to notify it that the MS has successfully completed the hard handoff.

i. j. k. l.

m. The MSC sends a Clear Command to the 3G BS and starts timer T315 . The 3G BS stops timer T306 . n. The 3G BS sends a Clear Complete message to the MSC to notify it that clearing has been accomplished. The MSC stops timer T315 .

This may be a Handoff Direction Message, a General Handoff Direction Message, an Extended Handoff Direction Message, or a Universal Handoff Direction Message as appropriate.

3.19.5.7

Voice Handoff from 2G System to 3G System

The following call flow diagram provides an illustration for a successful intergenerational hard handoff of a voice call from a 2G base station to a 3G base station. It is assumed that the call is not in inter-BS soft/softer handoff prior to the hard handoff, and thus no A3 connections need to be removed. In this call flow, the box marked MSC may represent one or two MSCs. In the case of inter-MSC handoff, ANSI-41 signaling is not specified. The message flows between the MSC and the 2G BS are not required.
Comment

MS

2G BS (Handoff Required) (T7) Null forward traffic channel frames

MSC

3G BS

Time

a Handoff Request b T11 c Handoff Request Ack d e f

(Handoff Command) Handoff Direction Message MS Ack Order x Twaitho (Handoff Commenced) T9

g h i j

Reverse Traffic Channel Frames or Traffic Channel Preamble Handoff Completion Message

BS Ack Order
(T306) (Clear Command) (Clear Complete) T315 Handoff Complete

k l m n

Figure 3.19.5.7-1 Successful Voice Intergenerational Hard Handoff 2G to 3G a. Based on an MS report that it crossed a network specified threshold for signal strength or for other reasons, the 2G BS recommends a hard handoff to one or more cells in the domain of the 3G BS. The 2G BS sends the equivalent of a Handoff Required message with the list of cells to the MSC and starts the equivalent of timer T7 . This message contains enough information to populate the IS-95 Channel Identity information element, and may be formatted according to an IOS V3.x or earlier standard. The MSC sends a Handoff Request message to the 3G BS with the IS-95 Channel Identity element present since the hard handoff bit was set and/or the Handoff Type element in the Handoff Required message indicated hard handoff. The IS-95 Channel Identity information element indicates that the mobile is operating a voice call on a 2G traffic channel. The MSC starts timer T11 .

b.

c.

Upon receipt of the Handoff Request message from the MSC, the 3G BS allocates appropriate radio resources as specified in the message and connects the call. The 3G BS sends null forward traffic channel frames to the MS. The 3G BS sends a Handoff Request Acknowledge message to the MSC and starts timer T9 to wait for arrival of the MS on its radio channel. This message contains the IS-95 Channel Identity and does not contain IS-2000 related information elements. The MSC stops timer T upon the receipt of this 11 message. If the service option received in the Handoff Request message is not available at the 3G BS, the 3G BS rejects the handoff request (see procedures for Handoff Failure message in [A-Interface]). The MSC prepares to switch from the 2G BS to the 3G BS and sends the equivalent of a Handoff Command message to the 2G BS. The 2G BS stops the equivalent of timer T7 . The 2G BS sends the handoff direction message to the MS across the air interface. If the MS is allowed to return to the 2G BS, then timer Twaitho is also started by the 2G BS. The MS may acknowledge the handoff direction message by sending a MS Ack Order to the 2G BS. If the handoff direction message is sent using quick repeats, the 2G BS might not request an acknowledgment from the MS.
2

d.

e.

f.

g.

h.

The 2G BS sends the equivalent of a Handoff Commenced message to the MSC to notify it that the MS has been ordered to move to the 3G BS channel. The 2G BS starts the equivalent of timer T306 to await the equivalent of the Clear Command message from the MSC. If timer Twaitho has been started, the 2G BS shall wait for that timer to expire before sending the message indicating the handoff has commenced. The MS sends reverse traffic channel frames or the traffic channel preamble to the target cell(s). The MS sends a Handoff Completion Message to the 3G BS. The 3G BS sends the BS Ack Order to the MS over the air interface. The 3G BS stops timer T9 . The 3G BS sends a Handoff Complete message to the MSC to notify it that the MS has successfully completed the hard handoff. At this point, the 3G BS and the mobile may change the MOB_P_REV in use to reflect a 3G call. If this happens, the 3G BS directs the MS to change its radio configuration to 3G (i.e. RC3 or higher).

i. j. k. l.

m. The MSC sends the equivalent of a Clear Command message to the 2G BS and starts timer T315 . The 2G BS stops the equivalent of timer T306 . n. The 2G BS sends the equivalent of a Clear Complete message to the MSC to notify it that clearing has been accomplished. The MSC stops timer T315 .

This may be a Handoff Direction Message, a General Handoff Direction Message or an Extended Handoff Direction Message as appropriate.