TS 24.206
Voice Call Continuity between Circuit Switched (CS) and IP Multimedia Subsystem
V7.5.0 (PDF)
2008/06 122 p.
- Rapporteur:
- Mr. Drage, Keith
full Table of Contents for TS 24.206 Word version: 7.5.0
1 Scope Word‑p. 6
2 References Word‑p. 6
3 Definitions, symbols and abbreviations Word‑p. 7
3.1 Definitions Word‑p. 7
3.2 Abbreviations Word‑p. 7
4 Overview of voice call continuity between the Circuit-Switched (CS) domain and the IP Multimedia (IM) Core Network (CN) subsystem Word‑p. 8
4.1 General Word‑p. 8
4.2 Underlying network capabilities Word‑p. 9
4.3 URI and address assignments Word‑p. 9
5 Functional entities Word‑p. 10
5.1 Introduction Word‑p. 10
5.2 User Equipment (UE) Word‑p. 10
5.3 Media Resource Function Controller (MRFC) Word‑p. 10
5.4 Application Server (AS) Word‑p. 10
5.5 Media Gateway Control Function (MGCF) Word‑p. 10
6 Roles for registration in the IM CN subsystem Word‑p. 10
7 Roles for call origination Word‑p. 11
7.1 Introduction Word‑p. 11
7.2 VCC UE Word‑p. 11
7.3 VMSC Word‑p. 12
7.4 VCC application Word‑p. 12
8 Roles for call termination Word‑p. 15
8.1 Introduction Word‑p. 15
8.2 VCC UE Word‑p. 15
8.3 GMSC Word‑p. 15
8.4 VCC application Word‑p. 15
9 Roles for domain transfer of a call from the CS domain to the IM CN subsystem Word‑p. 18
9.1 Introduction Word‑p. 18
9.2 VCC UE Word‑p. 18
9.3 VCC application Word‑p. 19
9.3.1 Distinction of requests sent to the VCC application Word‑p. 19
9.3.2 Domain transfer in the IM CN subsystem Word‑p. 19
9.4 MGCF Word‑p. 20
10 Roles for domain transfer of a call from the IM CN subsystem to the CS domain Word‑p. 20
10.1 Introduction Word‑p. 20
10.2 VCC UE Word‑p. 20
10.3 VMSC Word‑p. 21
10.4 VCC application Word‑p. 21
A Example signalling flows of voice call continuity between the Circuit-Switched (CS) domain and the IP Multimedia (IM) Core Network (CN) subsystem Word‑p. 23
A.1 Scope of signalling flows Word‑p. 23
A.2 Introduction Word‑p. 23
A.2.1 General Word‑p. 23
A.2.2 Key required to interpret signalling flows Word‑p. 23
A.3 Signalling flows for registration and exchange of mobility status information Word‑p. 24
A.4 Signalling flows for call origination Word‑p. 24
A.4.1 Introduction Word‑p. 24
A.4.2 Signalling flows for origination from the IM CN subsystem Word‑p. 25
A.4.3 Signalling flows for origination from CS domain Word‑p. 30
A.4.4 Signalling flows for origination from CS domain, using ISUP call diversion mechanisms Word‑p. 38
A.4.5 Signalling flows for origination from CS domain with no anchoring Word‑p. 46
A.4.6 Signalling flows for origination from CS domain for a user that is not registered within the IM CN subsystem Word‑p. 47
A.5 Signalling flows for call termination Word‑p. 52
A.5.1 Introduction Word‑p. 52
A.5.2 Signalling flows for termination to the IM CN subsystem Word‑p. 52
A.5.3 Signalling flows for termination to CS domain Word‑p. 58
A.5.4 Signalling flows for termination directed to IM CN subsystem (coming from the CS domain) (using CAMEL) Word‑p. 63
A.5.5 Signalling flow for termination directed to CS domain (coming from the CS domain) Word‑p. 70
A.5.6 Signalling flows with call termination delivery attempt failure to the IM CN subsystem Word‑p. 80
A.5.7 Signalling flow for termination directed to CS domain, unsuccessful delivery, redirect to IM CN Subsystem Word‑p. 82
A.5.8 Signalling flows for termination from CS domain with no anchoring (using CAMEL) Word‑p. 95
A.6 Signalling flows for CS domain to IM CN subsystem transfer Word‑p. 96
A.6.1 Introduction Word‑p. 96
A.6.2 Signalling flows for CS domain to IM CN subsystem transfer Word‑p. 97
A.6.3 Signalling flows for unsuccessful CS domain to IM CN subsystem transfer Word‑p. 104
A.7 Signalling flows for IM CN subsystem to CS domain transfer Word‑p. 105
B Example of filter criteria Word‑p. 118
B.1 Introduction Word‑p. 118
B.2 Example 1 - Service profile for UE originating for a VCC subscriber Word‑p. 118
B.3 Example 2 - Service profile for UE terminating for a VCC subscriber Word‑p. 119
$ Change history Word‑p. 121
