6
A30-20100913-028Br0 3GPP2 TSG-A WG3 TITLE: e1x CSFB MT call flow procedure-IWS-1xBS with Hard Handoff SOURCE: Mike Dolan ( mike.dolan@alcatel- lucent.com ) Rena Zhang ( rena.zhang@alcatel- lucent.com ) Satish Kanugovi ( satish.k@alcatel- lucent.com ) Masa Shirota ([email protected]) Scott Marin ([email protected] Naveen Arulselvan ([email protected] ) ABSTRACT: This contribution provides a call flow for the delivery of calling party information to the UE which is currently on an E-UTRAN system when an incoming call for that UE arrives on the 1x system using eCSFB procedures. This contribution essentially builds over the MT eCSFB call flow described in 3GPP TS 23.272 elaborating on the 1xRTT interactions and delivery of calling party information. This call flow is relevant to the deployment where IWS is collocated with the BS and at the same time covering the case where IWS that delivers the 1x messages to the UE via E-UTRAN is different from the 1x-BS that serves the UE with the 1x traffic channel. This contribution supersedes A30-20100621-006r5 Mot MT e1xCSFB success with IWS-1xBS.doc. RECOMMENDATION: 1 1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 2

A30-20100913-029BR2 ECSFB MT Call Flow Procedure IWS-1xBS With HO

Embed Size (px)

DESCRIPTION

CS Fall back in LTE/UMTS/CDMA

Citation preview

Page 1: A30-20100913-029BR2 ECSFB MT Call Flow Procedure IWS-1xBS With HO

A30-20100913-028Br0

3GPP2 TSG-A WG3

TITLE:

e1xCSFB MT call flow procedure-IWS-1xBS with Hard Handoff

SOURCE:Mike Dolan ( [email protected] )Rena Zhang ( [email protected] )Satish Kanugovi ( [email protected] )

Masa Shirota ([email protected])

Scott Marin ([email protected] Arulselvan ([email protected])

ABSTRACT:This contribution provides a call flow for the delivery of calling party information to the UE which is currently on an E-UTRAN system when an incoming call for that UE arrives on the 1x system using eCSFB procedures. This contribution essentially builds over the MT eCSFB call flow described in 3GPP TS 23.272 elaborating on the 1xRTT interactions and delivery of calling party information. This call flow is relevant to the deployment where IWS is collocated with the BS and at the same time covering the case where IWS that delivers the 1x messages to the UE via E-UTRAN is different from the 1x-BS that serves the UE with the 1x traffic channel.

This contribution supersedes A30-20100621-006r5 Mot MT e1xCSFB success with IWS-1xBS.doc.

RECOMMENDATION:

Review and adopt for A.S0008/9-C v4.0

The contributors grant 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. The contributors are 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 Partner’s standard which incorporates this contribution.

1

1

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

2

Page 2: A30-20100913-029BR2 ECSFB MT Call Flow Procedure IWS-1xBS With HO

A30-20100721-xxx

This document has been prepared by the contributors 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 the contributors. The contributors specifically reserves the right to amend or modify the material contained herein and nothing herein shall be construed as conferring or offering licenses or rights with respect to any intellectual property of the contributors other than provided in the copyright statement above.

2

1

1

2

3

4

5

2

Page 3: A30-20100913-029BR2 ECSFB MT Call Flow Procedure IWS-1xBS With HO

A30-20100913-028Br0

Proposal:

PE: Insert the following text into Annex F created for eCSFB call flows in A.S0008/9-C v4.0

PE, Where: x0 = 3GPP TS 23.272

x.x Mobile Terminated e1xCSFB Call Success with IWS-1xBS and with Hard Handoff

This section describes the call flow associated with the mobile terminated call procedures for the

enhanced CS Fallback to cdma2000 1x. This callflow elaborates the 3GPP2 aspects of the call flow

in TS 23.272 [x0] section B.2.3a.4. The call flow includes hard handoff to a target base station. Use of

this procedure with concurrent non-optimized packet switched (PS) handoff or optimized idle-mode

PS is not addressed here.

The MS/UE is attached in an E-UTRAN system and registered with the cdma2000 1x MSC through

E-UTRAN with enhanced CS fallback to cdma2000 1x capability indication to E-UTRAN.

It is assumed that the IWS function is incorporated into 1xBS in the following procedures. The call

flow assumes that when the UE transits to cdma2000 1x network there is a handoff via MSC is

required. This call flow also additionally describes the delivery of the calling party information to the

UE.

Note that this call flow also applies to a stand alone IWS.

PE, Where: x0 = 3GPP TS 23.272

3

1

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

2

Page 4: A30-20100913-029BR2 ECSFB MT Call Flow Procedure IWS-1xBS With HO

A30-20100721-xxx

Figure [xx] MT e1xCSFB call with Hard Handoff - IWS-1xBS

PE: Replace [xx] in caption with appropriate reference

a. MS/UE is E-UTRAN attached and registers with the MSC. The MS/UE informs the eNB that it supports e1xCSFB.

4

1

1

2

3

4

5

2

Page 5: A30-20100913-029BR2 ECSFB MT Call Flow Procedure IWS-1xBS With HO

A30-20100913-028Br0

b. The MSC determines that an incoming call terminates to an MS/UE within its serving region and sends the Paging Request message to the IWS-1xBS to initiate a mobile terminated call setup scenario. The MSC then starts timer T3113.

c. The IWS-1xBS sends a Page Message to the MS/UE via GCSNA through E-UTRAN. Upon receipt of the associated A21-1x Air Interface Signaling message, the MME sends an A21-Ack message to the IWS-1xBS.

UE performs extended service request as per [x0]The e1xCSFB procedure is triggered. Refer to TS 27.272 [x0] Section B.2.3.

d. The MS/UE sends a Page Response message to the IWS-1xBS via GCSNA through E-UTRAN. Upon receipt of the associated A21-1x Air Interface Signaling message, the IWS-1xBS sends an A21-Ack message to the MME.

e. The IWS-1xBS constructs the Paging Response message, and places it in the Complete Layer 3 Information message, sends the message to the MSC and starts timer T303. The MSC stops timer T3113 upon receipt of the Paging Response message from the IWS-1xBS.

f. MSC sends the Assignment Request message to the IWS-1xBS and starts timer T10. This message may contain an MS Information Record IE with information such as Calling Party Information (CPI), if available at the MSC. This example assumes that the MSC includes the MS Information Record IE on the Assignment Request message. The IWS-1xBS stops timer T303 upon receipt of the message.

g. IWS-1xBS sends Assignment Complete to the MSC in response to Assignment Request. The MSC starts time T301. The MSC stops timer T10 upon receipt of the message.

h. The IWS-1xBS creates a Handoff Required message including the MS Information Record IE and sends it to the MSC. The IWS-1xBS starts timer T7.

i. The MSC sends a Handoff Request message to the target BS with the MS Information Record IE and the IS-95 Channel Identity IE or the IS-2000 Channel Identity IE present, based on if the corresponding MS Information Record IE and IS-2000 or IS-95 Channel Identity IE were present in the Handoff Required message. The MSC starts timer T11.

j. Upon receipt of the Handoff Request message from the MSC, the target BS allocates appropriate radio resources as specified in the message. As the Handoff Request message can have multiple cell(s) specified, the target BS can also choose to set up multiple cell(s) for the handoff request. The target BS sends null forward traffic channel frames to the MS/UE. The target BS sends a Handoff Request Acknowledge message to the MSC and starts timer T9 to wait for arrival of the MS/UE on its radio channel. The MSC stops timer T11 upon the receipt of this message. The first cell in the cell identifier list IE of the message is treated as the new designated cell by the MSC. The change of designated cell occurs upon receipt of the Handoff Complete message. If the service option received in the Handoff Request message is not available at the target BS and the target BS selected a different service option for the handoff then the target BS shall include the service option it selected in the service configuration records.

k. The MSC sends a Handoff Command message to the IWS-1xBS. The IWS-1xBS stops timer T7. The MSC shall include in the Handoff Command message the service configuration records it received in the Handoff Request Acknowledge message.

l. The IWS-1xBS sends a handoff direction message to the MS/UE via the E-UTRAN using GCSNA, to instruct the MS/UE to handoff to the 1x system. Upon receipt of the associated A21-1x air interface signaling message, the MME sends an A21-Ack message to the IWS-1xBS.

m. The IWS-1xBS sends the Handoff Commenced message to the MSC. The IWS-1xBS starts timer T306

to await the Clear Command message from the MSC.

n. The S1 release procedure and PS service suspend procedure are described in [x0].

5

1

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

2

Page 6: A30-20100913-029BR2 ECSFB MT Call Flow Procedure IWS-1xBS With HO

A30-20100721-xxx

o. The MS/UE tunes to the 1x radio network and performs traffic channel acquisition with the target BS.

p. The MS/UE sends a 1x Handoff Complete Message to the target BS. The target BS stops timer T9.

q. The target BS sends a Handoff Complete message to the MSC.

r. The MSC sends a Clear Command message to the IWS-1xBS and starts timer T315. The IWS-1xBS stops timer T306.

s. The IWS-1xBS sends a Clear Complete message to the MSC to notify it that clearing has been accomplished. The MSC stops timer T315.

t. The target BS sends the Alert with Information Message to the MS/UE to cause ringing at the MS. Any cdma2000 Information Records in the MS Information Record IE from the Handoff Request message in step i, such as CPI and signal, are included in the Alert with Information Message. This step can occur in parallel withanytime after step q.

u. When the call is answered at the MS/UE, a Connect Order is transmitted to the target BS.

v. The target BS sends a Connect message to the MSC to indicate that the call has been answered at the MS/UE. The MSC stops timer T301 upon receipt of the Connect message.

6

1

1

2

3

4

5

6

7

8

9

10

11

12

13

14

2