Content for TR 23.806 Word version: 7.0.0
2 References
3 Definitions, symbols and abbreviations
4 Overall Requirements
5 Architectural Requirements and Considerations
6 Architecture Alternatives
7 Security
8 Charging
9 Comparison of the Architecture Model
10 Conclusion
A IMS based HO control Model
B Routing Selection Decision Logic
C Bearer optimisation for static anchoring of CS calls in IMS
D Evaluation Criteria
E "Call Reestablishment on Domain Transfer" for IMS-controlled static anchoring
F Service Continuity Model: IMS Controlled Alternative-Dynamic Anchoring Extensions
G UE Functions - IMS Controlled Model with static anchoring
H Operator Deployment Scenarios
$ Change history
2 References p. 9
3 Definitions, symbols and abbreviations p. 10
4 Overall Requirements p. 11
5 Architectural Requirements and Considerations p. 12
5.1 Basic Assumptions p. 12
5.2 Architectural Requirements p. 13
5.3 Session Scenarios p. 14
5.3.1 Overview p. 14
5.3.2 Two party UE to PSTN calls p. 14
5.3.3 Two party UE(A) to UE(B) calls p. 14
5.3.4 Supplementary services are active when call continuity procedures occur p. 15
5.3.5 Supplementary Services are Activated After Call Continuity Procedures Have Completed p. 15
5.4 Traffic Scenarios p. 15
6 Architecture Alternatives p. 16
6.1 General p. 16
6.2 Architecture Reference Model p. 16
6.2.1 Call Continuity Control Function (CCCF) p. 16
6.2.2 Network Domain Selection (NeDS) p. 16
6.2.2.1 Description of Network Domain Selection Functionality p. 16
6.2.2.2 Routing Selection Decision p. 17
6.2.3 Domain selection for originating call p. 17
6.2a Common procedures p. 17
6.2a.1 Registration p. 18
6.2a.1.1 CS Domain Registration p. 18
6.2a.1.2 IMS Domain Registration p. 18
6.2a.1.3 Information exchange between UE and CCCF/NeDS p. 18
6.2a.2 Origination p. 19
6.2a.2.1 UE Origination from IMS Domain p. 19
6.2a.2.2 UE Origination from CS Domain - Original Domain Control Model p. 20
6.2a.2.3 UE Origination from CS Domain - IMS Controlled Model p. 20
6.2a.3 Termination p. 27
6.2a.3.1 IMS termination p. 27
6.2a.3.1.1 IMS termination - General p. 27
6.2a.3.1.2 IMS termination - Incoming call received via IMS p. 27
6.2a.3.1.3 IMS termination - Incoming call received via CS p. 28
6.2a.3.2 CS termination p. 30
6.2a.3.2.1 CS termination - General p. 30
6.2a.3.2.2 CS termination - Incoming Call received via IMS p. 30
6.2a.3.2.3 CS termination - Incoming call received via CS p. 33
6.2a.3.3 HSS based Network Domain Selection for termination p. 38
6.3 Service Continuity Model: IMS Controlled Alternative p. 39
6.3.1 General Description p. 39
6.3.4 Origination p. 40
6.3.5 Termination p. 40
6.3.6 Call Continuity Scenarios p. 40
6.3.6.1 General p. 40
6.3.6.2 Procedures for CS to IMS Voice Call Continuity p. 41
6.3.6.3 Procedures for IMS to CS call continuity p. 42
6.3.7 Impact on Supplementary Services p. 42
6.3.7.1 Voice Call Continuity for Multi-Session calls p. 43
6.3.7.1.1 Anchoring of IMS Held and Active sessions at CCCF p. 43
6.3.7.1.2 IMS to CS VCC of IMS Held and Active sessions p. 45
6.3.7.1.3 Anchoring of CS Held and Active sessions at CCCF with active IMS Registration p. 47
6.3.7.1.4 CS to IMS VCC of CS Held and Active sessions; IMS active at the time of CS Anchoring p. 48
6.3.7.1.5 Anchoring of CS Held and Active sessions at CCCF without IMS Registration p. 49
6.3.7.1.6 CS to IMS VCC of CS Held and Active sessions; IMS not active at the time of CS Anchoring p. 50
6.3.7.2 Voice Call Continuity for MPTY service p. 50
6.3.7.2.1 Transition of a Multi-party CS Call Session to an IMS-based Service Session p. 51
6.3.7.2.2 Transition of a Multi-party IMS-based Service Session to a CS Call Session p. 52
6.3.7.3 Supplementary Service Implementation Options in the IMS Domain p. 53
6.3.7.4 IMS service control of VCC subscriber calls p. 53
6.3.7.4.1 USSD enabled Service Control in IMS-Signalling and Bearer Architecture p. 53
6.3.7.4.2 SIP enabled Service Control of CS calls in IMS-Signalling and Bearer Architecture p. 54
6.3.7.5 Supplementary Service Impact summary p. 55
6.3.7.6 TISPAN's recommendation for Mandatory, Recommended, and Optional Supplementary Services in the IMS Domain p. 56
6.3.8 Call Continuity within 3GPP radio p. 57
6.3.8a Security Impact of Handovers between the CS Domain and the IMS for IMS Controlled Method p. 58
6.3.8b Charging Impact of Handovers Between the CS Domain and the IMS Domain for IMS Controlled Method p. 58
6.3.8b.1 General Description p. 58
6.3.8b.2 Charging Strategy Analysis p. 59
6.3.8b.2.1 CS Origination p. 59
6.3.8b.2.2 CS Termination p. 59
6.3.8b.2.3 IMS Origination p. 59
6.3.8b.2.4 IMS Termination p. 60
6.3.8b.2.5 CS leg established for IMS to CS call continuity p. 60
6.3.8b.2.6 IMS leg established for CS to IMS call continuity p. 60
6.3.8b.3 Accounting Strategy Analysis p. 60
6.3.9 Analysis of the IMS Controlled model p. 61
6.3a Extended VCC IMS controlled architecture p. 62
6.3a.1 IMS registration p. 62
6.3a.2 IMS origination p. 62
6.3a.3 IMS termination p. 62
6.3a.4 Attaching/registering via the CS network p. 63
6.3a.5 CS origination p. 63
6.3a.6 CS termination p. 63
6.3a.7 Call Continuity Scenarios (dual radio) p. 63
6.3a.8 Call continuity procedures (single radio) p. 65
6.3a.9 Impact on supplementary services p. 65
6.3a.10 Impact on accounting p. 65
6.4 Service Continuity Model: Original Domain Control Model p. 66
6.4.1 General Description p. 66
6.4.1.1 Reference Architecture Model p. 66
6.4.1.2 Call Continuity Control Function p. 66
6.4.1.3 Call Continuity Control Function Reference Points p. 67
6.4.6 Call continuity scenarios p. 67
6.4.7 Impact on Supplementary Services p. 77
6.4.7.1 Supplementary services after CS to IMS call continuity procedures p. 77
6.4.7.2 Supplementary services after IMS to CS call continuity procedures p. 79
6.4.8 Charging Impact of Handovers Between the CS Domain and the IMS for Original Domain Control p. 84
6.4.9 Security Impact of Handovers Between the CS Domain and the IMS for Original Domain Control p. 84
6.5 HandOver Application Server for voice continuity between the IMS and CS domain p. 84
6.5.1 General Description p. 84
6.5.4 Origination p. 85
6.5.5 Termination p. 87
6.5.6 Call continuity scenarios p. 87
6.5.8 Evaluation of the Model p. 93
7 Security p. 93
8 Charging p. 94
9 Comparison of the Architecture Model p. 94
10 Conclusion p. 94
A IMS based HO control Model p. 95
B Routing Selection Decision Logic p. 105
B.1 NeDS function is invoked from the CS Domain p. 105
B.2 NeDS function is invoked from the IMS Domain p. 106
C Bearer optimisation for static anchoring of CS calls in IMS p. 107
D Evaluation Criteria p. 109
E "Call Reestablishment on Domain Transfer" for IMS-controlled static anchoring p. 111
E.1 Call Reestablishment on Domain Transfer (CReDT) p. 111
E.1.1 Triggers for CReDT p. 111
E.1.2 CReDT solution options p. 112
E.1.2.1 CReDT (option 1) - Uncontrolled Release of Source Radio by UE p. 112
E.1.2.1.1 2G CS to 3G PS CReDT p. 112
E.1.2.1.2 3G PS to 2G CS CReDT p. 113
E.1.2.2 CReDT (option 2) - CCCF controlled Release of Source Radio by UE p. 114
E.1.2.2.1 2G CS to 3G PS CReDT p. 115
E.1.2.2.2 3G PS to 2G CS CReDT p. 116
F Service Continuity Model: IMS Controlled Alternative-Dynamic Anchoring Extensions p. 118
F.1 ECT enabled Dynamic Anchoring p. 118
F.1.1 Supplementary Service control for ECT enablement p. 118
F.1.2 CS to IMS Voice Call Continuity using ECT p. 118
F.1.3 Subsequent Executions of VCC Procedure p. 120
F.1.4 Evaluation of Dynamic CS Anchoring for VCC using ECT p. 121
F.2 DACCI enabled Dynamic Anchoring p. 122
F.2.1 First CS to IMS Execution of VCC Procedure using DACCI p. 122
F.2.2 Subsequent VCC Transitions with DACCI enabled anchoring p. 123
F.2.3 Multi-Session services support with DACCI p. 124
F.2.4 Evaluation of Dynamic CS Anchoring for VCC using DACCI p. 126
F.3 Dynamic Anchoring using CAMEL 4 p. 126
F.3.1 Origination p. 127
F.3.2 Termination p. 128
F.3.3 Domain Transfer Scenarios p. 131
F.3.4 Handoff URI p. 134
F.3.5 Use of Join Number for Establishing Additional CS Call Leg p. 134
F.3.6 Notification of CS Call Connection State to CCCF/NeDS p. 135
F.3.7 Emergency Call Services p. 135
F.3.8 Reliable CS-to-IMS Transfer with Fallback to the CS Mode p. 135
F.3.9 Multi-Session services support with CAMEL 4 p. 135
F.3.9.1 General p. 135
F.3.9.2 Call continuity for Call Hold service (Single Session) p. 135
F.3.9.3 Call continuity for Call Waiting service (Multi-Session) p. 140
F.3.9.4 Call continuity for 3-Way Conference service (Multi-Session) p. 144
F.3.10 Evaluation of Dynamic Anchoring using CAMEL4 model p. 148
G UE Functions - IMS Controlled Model with static anchoring p. 149
G.1 UE Registration p. 149
G.2 UE Origination p. 149
G.3 UE Termination p. 149
G.4 VCC Triggers p. 150
G.5 VCC Procedures p. 150
G.5.1 From CS to IMS p. 150
G.5.2 From IMS to CS p. 150
G.5.3 Emergency Service p. 151
G.5.4 Supplementary Services p. 151
H Operator Deployment Scenarios p. 152
$ Change history p. 153
