Tech-invite 3GPPspace IETFspace

21 22 23 24 25 26 27 28 29 31 32 33 34 35 36 37 38 4‑5x

Content for TR 23.892 Word version: 8.0.1

0… 4…

4 Overall requirements p. 15

5 Architectural requirements and considerations p. 15

5.1 Basic assumptions p. 15

5.1.1 Domain Transfer principles p. 15

5.2 Architectural requirements p. 16

5.2.1 Service consistency p. 16

5.2.2 Core network requirements p. 16

5.2.2.1 IMS Core Network p. 16

5.2.2.2 CS Core Network p. 16

5.2.3 Use of VCC Application Domain Transfer with ICS p. 16

5.2.4 Access domain selection p. 16

5.2.5 Redirection of CS calls to IMS p. 17

5.3 UE requirements p. 17

5.3.1 Support of ICS UEs p. 17

5.3.2 Support of Pre-Rel-08 non ICS Enhanced UEs p. 17

5.4 Service continuity requirements p. 17

5.4.1 Priority Service (ETS) p. 17

5.4.2 Supplementary services p. 17

5.5 Session scenarios p. 17

5.5.1 Session scenarios when a PS network is used that supports the full duplex speech component of the IMS multimedia telephony service p. 17

5.5.2 Session scenarios when a PS network is used that does not support the full duplex speech component of the IMS multimedia telephony service p. 18

5.5.3 Session scenarios when a CS network is used to access IMS services p. 18

5.5.3.1 Session scenarios for an ICS UE p. 18

5.5.3.2 Additional session scenarios for ICS UE capable of VCC p. 18

5.5.3.3 Session scenarios for non-ICS UEs p. 19

5.5.3.3.1 When using CS networks upgraded with ICS capability p. 19

5.5.3.3.2 When using CS networks not upgraded with ICS capability p. 19

5.5.3.3.3 Additional session scenarios for non-ICS UE capable of VCC p. 19

5.5.4 Session scenarios for co-existence of ICS UE and Non ICS UEs solutions p. 19

6 Architecture alternatives p. 20

6.1 Introduction p. 20

6.1.1 IMS CS Control Channel (ICCC) p. 20

6.2 Reference architecture for ICS UEs p. 21

6.2.1 Reference architecture diagram p. 21

6.2.2 IMS CS Control Function (ICCF) p. 21

6.2.2.1 Remote User Agent (RUA) p. 21

6.2.2.2 Realization of the ICCF p. 22

6.2.2.2.1 I1-ps approach p. 22

6.2.2.2.2 I1-cs approach p. 22

6.2.2.3 CS Access Adaptation Function (CAAF) p. 24

6.2.2.4 Remote Provisioning Client (RPC) p. 25

6.2.3 ICS UE p. 25

6.3 Architecture for support of non-ICS UE p. 25

6.3.1 L-CAAF-n approach p. 25

6.3.1.1 Reference architecture p. 25

6.3.1.2 Extensions to the CAAF in the ICCF for support of non ICS UEs p. 25

6.3.1.3 Service Support for non ICS UE using L-CAAF-n p. 26

6.3.1.3.1 Line ID Services (OIP, OIR, TIP, TIR) p. 26

6.3.1.3.2 Communication Diversion Services p. 26

6.3.1.3.3 Communication Deflection p. 26

6.3.1.3.4 Communication Barring p. 26

6.3.1.3.5 Mid call services (Communication Hold, CW, Conf, Communication Transfer) p. 26

6.3.1.3.6 Voice Call Continuity p. 26

6.3.1.3.7 User configuration of Supplementary Services p. 26

6.3.1.3.8 Serving Domain Considerations p. 27

6.3.1.4 Physical realization of ICCF with L-CAAF-n approach p. 27

6.3.2 CAMEL approach p. 28

6.3.2.1 Service Support for non ICS UE, using the Architecture with CAMEL approach p. 28

6.3.2.1.1 Line ID Services (OIP, OIR, TIP, TIR) p. 28

6.3.2.1.2 Communication Diversion Services p. 29

6.3.2.1.3 Communication Barring Services (CB) p. 29

6.3.2.1.4 Mid call services (Communication Hold, CW, Conf, Communication Transfer) p. 29

6.3.2.1.5 Session continuity p. 29

6.3.2.1.6 User configuration of Supplementary Services p. 29

6.3.2.1.7 Serving domain considerations p. 29

6.3.3 Architecture with Enhanced MSC Server p. 31

6.3.3.1 Reference architecture p. 31

6.3a ICS Architecture for ICS UE and non-ICS UE p. 31

6.3a.1 IMS CS Control Channel (ICCC) p. 31

6.3a.2 Reference architecture diagram p. 32

6.3a.2.1 IMS CS Control Function (ICCF) p. 32

6.3a.2.2 ICS Enhanced MSC Server (IMSC) p. 32

6.3a.2.3 ICS UE p. 33

6.3a.2.4 Remote Provisioning Client (RPC) p. 33

6.3a.2.5 Reference Points p. 33

6.3a.2.5.1 I1 Reference Points p. 33

6.3a.2.5.2 I2 Reference Point p. 33

6.3a.2.5.3 I5 Reference Point p. 33

6.3a.2.5.4 I6 Reference Point p. 33

6.3a.3 Signalling and Bearer Architecture for ICS UE: I1-ps with Bearer Control Signalling Path established via standard VMSC p. 33

6.3a.4 Signalling and Bearer Architecture for ICS UE: I1-ps with Bearer Control Signalling Path established via IMSC p. 33

6.3a.5 Signalling and Bearer Architecture for ICS UE: I1-cs using a standard VMSC p. 34

6.3a.6 Signalling and Bearer Architecture for ICS UE with I1-cs using an IMSC and non ICS UE p. 34

6.3a.7 Signalling and Bearer Architecture for an ICS User who only owns a non ICS UE which is capable of receiving voice telephony services only over GSM/UMTS CS access p. 35

6.4 ICS Reference Points p. 35

6.4.1 I1 Reference Point p. 35

6.4.2 I2 Reference Point p. 35

6.4.3 I3 Reference Point p. 36

6.4.4 I4 Reference Point p. 36

6.4.5 I5 Reference Point p. 36

6.4.6 I6 Reference Point p. 36

6.4.7 I7 Reference Point p. 36

6.4a Applicability of the Domain Selection Function to ICS p. 36

6.4a.1 Service Domain Selection (SDS) for ICS p. 36

6.4a.2 Access Domain Selection (ADS) for ICS p. 37

6.4a.2.1 ADS for originating sessions p. 37

6.4a.2.2 ADS for terminating sessions p. 37

6.4a.2.2.1 Interactions with VCC for ADS of terminating sessions p. 38

6.5 Architectural alternative: I1-ps approach p. 38

6.5.1 Signalling and bearer architecture for full duplex speech over CS access p. 38

6.5.2 Information flows p. 40

6.5.2.1 Registration p. 40

6.5.2.2 Origination p. 41

6.5.2.2.1 Calls established using CS bearers with use of I1-ps p. 41

6.5.2.2.2 Calls established using CS bearers with use of I1-ps (Dynamic RUA DN allocation) p. 42

6.5.2.3 Termination p. 44

6.5.2.3.1 Calls established using CS bearers with use of I1-ps p. 44

6.5.2.3.2 Using CS Origination procedures to set up the Bearer Control Signalling session p. 46

6.5.2.4 Mid-call services p. 48

6.5.2.4.1 Calls established using CS bearers with use of I1-ps p. 48

6.5.2.5 Domain Transfer to CS p. 49

6.5.2.5.3 Assignment of Session Transfer Identifier p. 51

6.5.2.6 I1-ps to I1-cs fallback p. 51

6.5.3 I1-ps handover scenarios p. 51

6.5.3.1 Introduction p. 51

6.5.3.2 Handovers within 3G access for IMS sessions using CS voice bearer established with I1-ps p. 52

6.5.3.3 Handovers of IMS sessions using CS voice bearer established in 3G access with I1-ps to 2G access p. 52

6.5.3.3.1 PS Domain available after HO to 2G access p. 52

6.5.3.3.2 PS Domain is not available after HO to 2G access p. 53

6.5.3.4 Handovers of IMS sessions using CS voice bearer established in 2G access with I1-ps to 2G/3G access p. 54

6.5.3.4.1 PS Domain is available after HO to target access p. 54

6.5.3.4.2 PS Domain is not available after HO to target access p. 55

6.6 Architectural alternative: I1-cs Application Server approach p. 56

6.6.1 Signalling and bearer architecture for full duplex speech over CS access p. 56

6.6.1.1 Calls established using CS bearers p. 56

6.6.1.1.1 Introduction p. 56

6.6.2 Assignment of Session Transfer Identifier p. 57

6.6.2a Registration p. 58

6.6.2a.1 IMS Registration via CS access p. 58

6.6.2a.1.1 Introduction p. 58

6.6.2a.1.2 IMS Registration via CS access using ISC p. 58

6.6.2a.1.3 CS Registration Status Push and Pull over Cx and Sh p. 60

6.6.2a.1.4 RUA Registration in IMS when attached to CS access p. 67

6.6.2b Video call p. 67

6.6.2b.1 Fallback to speech at session establishment p. 67

6.6.2b.2 Service change with SCUDIF p. 67

6.6.2b.2.1 IM CN subsystem originated change p. 67

6.6.2b.2.2 CS network originated change p. 67

6.6.2b.3 Non-SCUDIF case (ISUP or BICC without SCUDIF) p. 67

6.6.2b.4 Normal video call flow p. 68

6.6.2b.4.1 Origination p. 68

6.6.2b.4.2 Termination p. 70

6.6.2b.5 Session continuity p. 72

6.6.3 Information flows p. 72

6.6.3.1 I1-cs unregistered user solution p. 72

6.6.3.1.1 Origination p. 72

6.6.3.1.2 Termination p. 76

6.6.3.1.3 Mid-call services p. 80

6.6.3.1.4 Domain Transfer p. 85

6.6.3.1.5 Managing Network Services related Information p. 89

6.6.3.2 I1-cs: registered user solution - ISC model p. 90

6.6.3.2.1 IMS Registration via CS access p. 90

6.6.3.2.2 Origination, termination, Mid-call services and Domain Transfer p. 90

6.6.3.2.3 Managing Network Services related Information p. 90

6.7 Architectural alternative: I1-cs IMS Adaptor approach p. 90

6.7.1 Signalling and bearer architecture for full duplex speech over CS access p. 90

6.7.1a Registration p. 91

6.7.1a.1 RUA Registration in IMS when attached to CS access p. 91

6.7.1a.1.1 Triggers for RUA Registration / De-registration p. 91

6.7.1a.1.2 RUA Registration by the ICCF p. 92

6.7.1a.1.3 Originating / terminating call p. 93

6.7.1a.1.4 RUA De-Registration by the ICCF p. 93

6.7.1a.1.5 Network De-Registration p. 93

6.7.1a.1.6 RUA registration use cases p. 93

6.7.2 Information flows p. 97

6.7.2.1 Origination p. 97

6.7.2.1.1 Use of USSD transport in IMS Adaptor approach for session control p. 97

6.7.2.2 Termination p. 98

6.7.2.2.1 Use of USSD transport in IMS Adaptor approach for session control p. 98

6.7.2.2.2 Use of USSD transport in IMS Adaptor approach for session control p. 98

6.7.2.3 Mid-call services p. 100

6.7.2.3.1 General p. 100

6.7.2.3.2 Mid-call event handling p. 100

6.7.2.4 Domain Transfer p. 101

6.7.2.4.1 Single Call Continuity from CS access to PS access p. 101

6.7.2.4.2 Single call continuity from PS access to CS access p. 102

6.7.2.4.3 Assignment of Session Transfer Identifier p. 105

6.7.2.5 Managing Network Services related Information p. 105

6.8 Architectural alternative: L-CAAF-n approach p. 105

6.8.1 Signalling and bearer architecture p. 105

6.8.1.3 Calls established using CS bearers with non ICS UE p. 105

6.8.2 Information flows p. 106

6.8a Architectural alternative: Enhanced MSC Server approach p. 106

6.8a.1 Signalling and bearer architecture p. 106

6.8a.1.1 Calls established using CS bearers with non ICS UE p. 106

6.8a.1a IMS Address Discovery p. 106

6.8a.2 Information Flows p. 106

6.8a.2.1 Registration p. 106

6.8a.2.2 Origination p. 110

6.8a.2.3 Termination p. 112

6.8a.2.4 Session Transfer p. 113

6.8a.3 Originated Service Domain Selection for enhanced MSC server p. 115

6.8a.4 Co-existences of ICS UE and MSC Server approach p. 117

6.8a.4.1 Use of IMSI-derived IMPU/IMPI by both ICS UE and enhanced MSC Server p. 117

6.8a.4.2 ISIM registered UE and enhanced MSC Server p. 118

6.8a.4.3 Co-existence of ICCF and enhanced MSC server p. 119

6.8a.5 Subscription to the registration event package p. 121

6.9 CAMEL redirection of CS call to IMS p. 121

6.9.1 Call origination using CAMEL redirection of CS call to IMS p. 121

6.9.2 Use of CS call control procedures for first session setup, CAMEL used to redirect CS calls to IMS p. 122

6.9a Deriving ICS specific IMPI/IMPU p. 122

6.10 Requirements on ICCP when using CS access p. 123

6.10.1 General p. 123

6.10.2 ICCP functional requirements p. 123

6.10.3 ICCP Non-functional requirements p. 123

6.11 Media Handling p. 123

6.12 ICS Data Management p. 123

6.12.0 Introduction p. 123

6.12.1 Alternative 1: Different data models are not allowed under the same subscription p. 124

6.12.2 Alternative 2: One-time upgrade p. 124

6.12.3 Alternative 3: Convert the settings whenever possible p. 126

6.12.4 Option: Limited MMTel Service Set p. 127

6.12.5 Non-transparent data solution alternative p. 127

6.12.6 Transparent data solution alternative p. 129

6.12.7 Data validation discussion p. 130

6.13 Service Support for ICS UE, using I1-ps and I1-cs approach, ICCC for call setup p. 131

6.13.1 Line ID Services (OIP, OIR, TIP, TIR) p. 131

6.13.2 Communication Diversion Services p. 131

6.13.2.1 Communication Diversion services exclusively controlled in home IMS (CFU, CFNL) p. 131

6.13.2.2 Communication Diversion services requiring participation of serving network (CFNRy, CFNRc and CFB) p. 131

6.13.2.2.1 Communication Forwarding on mobile subscriber not reachable (CFNRc) over I1-CS p. 131

6.13.2.2.2 Communication Forwarding on Busy User (CFB) p. 133

6.13.3 Communication Deflection p. 133

6.13.3.1 Communication Deflection (CD) over I1-cs p. 134

6.13.3.2 Communication Deflection (CD) over I1-ps p. 134

6.13.4 Communication Barring p. 134

6.13.5 Mid call services (Communication Hold, CW, Conf, Communication Transfer) p. 134

6.13.6 Session continuity p. 134

6.13.7 User configuration of Supplementary Services p. 135

6.13.8 Serving Domain Considerations p. 135

6.14 Service Support for ICS UE using I1-cs approach, CS call control with CAMEL for call setup p. 135

6.14.1 Line ID Services (OIP, OIR, TIP, TIR) p. 135

6.14.2 Communication Diversion Services p. 135

6.14.2.1 Communication Diversion services exclusively controlled in home IMS (CFU, CFNL, CFNRy, CFNRc) p. 135

6.14.2.1.1 Communication Forwarding Unconditional (CFU) p. 136

6.14.2.1.2 Communication Forwarding on Not Logged-in (CFNL) p. 136

6.14.2.1.3 Communication Forwarding on Subscriber Not Reachable (CFNRc) p. 136

6.14.2.1.4 Communication Forwarding on No Reply (CFNRy) p. 137

6.14.2.2 Communication Diversion services requiring participation of serving network (CFB) p. 138

6.14.3 Communication Deflection p. 138

6.14.4 Communication Barring p. 138

6.14.5 Mid call services (Communication Hold, CW, Conf, Communication Transfer) p. 139

6.14.6 Session continuity p. 139

6.14.7 User configuration of Supplementary Services p. 139

6.14.8 Serving Domain Considerations p. 139

6.15 Domain selection function to ICS p. 140

6.15.1 Access Domain Selection (ADS) p. 140

6.15.1.1 ADS for terminating sessions (TADS) p. 140

6.15.1.2 TADS-UE Scenarios p. 140

6.16 Impact on IMS p. 141

6.17 Impact on CS Core Network p. 141

6.18 Impact on UE p. 141

6.19 Fallback Mechanisms p. 142

6.19.1 Fallback for L-CAAF-n and enhanced MSC solutions p. 142

6.19.1.1 Introduction p. 142

6.19.1.2 Possible Solutions p. 142

6.19.1.3 Conclusion p. 142

6.20 ICS capability exchange between the ICCF and the ICS UE p. 143

6.20.1 ICS capability exchange between the ICCF and the ICS UE p. 143

6.20.2 ICS Association between the ICCF and the IMSC p. 143

6.20.2.1 Alternatives for establishing ICS Association between ICCF and IMSC p. 144

7 Conclusion p. 145

7.1 Interim conclusion on registered services to ICS users when using I1-cs p. 145

7.2 Conclusion on ICS architecture solutions p. 146

7.3 Conclusion on use of ICCC p. 146

7.3.1 Conclusion on the use of I1-ps p. 146

7.3.1.1 Conclusion on the use of I1-ps to initiate the first ICS UE session p. 146

7.3.1.2 Conclusion on the use of I1-ps for Domain Transfer p. 146

7.3.2 Conclusion on the use of I1-cs p. 146

7.3.2.1 Conclusion on the use of I1-cs to initiate the first ICS UE session p. 146

7.3.2.2 Conclusion on the use of I1-cs for Domain Transfers p. 147

7.4 Conclusion on centralization of conditional call forwarding p. 147

7.5 Conclusion on ICS UE receiving home IMS services via an IMSC p. 147

7.6 Conclusion on handling of multiple media for IMS Centralized Services p. 148

7.7 Conclusion on use of ICCC for CS terminations p. 148

7.8 Conclusion on relation between ICS and Service Continuity p. 148

7.9 Conclusion on the relationship between ICS and MMSC p. 149

7.10 Conclusion on T-ADS p. 149

A ICS Service examples with I1-ps p. 150

A.1 Customized Alerting Tone p. 150

A.2 Instant Picture Presentation p. 151

A.3 Call Reject with customized reason p. 152

A.4 Caller's Location p. 153

A.5 Ad-hoc conferencing p. 154

B Information flow for mid call service using MRFC/MRFP p. 158

B.1 Information flow for using MFRP by ICCF for held call only p. 158

B.2 Information flow for using MFRP for both active and held call p. 159

B.3 information flow for using MFRP by TAS for held call p. 161

C Comparative analysis of solutions for non ICS UE support p. 163

D MGW Realization for the Enhanced MSC Server approach p. 165

$ Change history p. 167