TR 23.885 ★
Feasibility Study of
Single Radio Voice Call Continuity (SRVCC)
from UTRAN/GERAN to E-UTRAN/HSPA

Use "3GPP‑Page" to get the Word version
the left border in eToC indicates whether the content is: "available", "not available yet", or "not planned"

V11.0.0 (Wzip) 2011/09 83 p.

essential Table of Contents for TR 23.885 Word version: 11.0.0

each title, in the "available" or "not available yet" area, links to the equivalent title in the CONTENT

2 References Word‑p. 7

3 Definitions and abbreviations Word‑p. 8

4 Requirements and Assumptions Word‑p. 8

4.1 Assumptions Word‑p. 8

4.2 Architectural requirements Word‑p. 8

4.3 Performance requirements Word‑p. 9

4.4 Reverse SRVCC deployment scenarios Word‑p. 10

5 Architecture model and reference points Word‑p. 10

5.1 General Word‑p. 10

5.2 Reference architecture Word‑p. 11

5.3 Functional Entities Word‑p. 12

5.4 Reference points Word‑p. 12

6 Solutions Word‑p. 12

6.1 Solution 1: Session transfer initiated on E-UTRAN/HSPA Word‑p. 12

6.2 Solution 2: Session transfer initiated on E-UTRAN/HSPA Word‑p. 20

6.3 Solution 3+5: Media anchoring in serving network with Access Transfer Control Functionality Word‑p. 25

6.4 Solution 4: Session transfer by local anchoring with Indirect Forwarding Word‑p. 53

6.5 Solution 5: IMS procedure is initiated by MSC Server to ATCF Word‑p. 59

7 Assessment of the solutions Word‑p. 73

7.1 Assessment Criteria Word‑p. 73

7.2 Assessment of the solution 3+5 access transfer preparation alternatives Word‑p. 74

8 Conclusion Word‑p. 77

8.1 General Word‑p. 77

8.2 Access Transfer preparation / How to reserve bearer for VoIP Word‑p. 77

8.3 Source SGSN selection by MSC Server Word‑p. 77

8.4 Maintaining IMS registration over PS access during the CS session Word‑p. 77

8.5 Summary Word‑p. 77

A Mechanisms to re-enable E-UTRAN capability Word‑p. 78

A.1 Functional description Word‑p. 78

A.2 Information flows Word‑p. 79

B Mechanisms for GERAN/UTRAN sending Handover/Relocation Required message Word‑p. 82

$ Change history Word‑p. 83