tech-invite   World Map     

3GPP     Specs     Glossaries     Architecture     IMS     UICC       IETF     RFCs     Groups     SIP     ABNFs       Search

Top        in Index        Prev        Next

TR 23.719 (SA2)
Feasibility Study on Service Domain Centralization

|   ToC   |   3GPP‑Page  |   Help   |

(W-zip) V14.0.0    2016/09    42 p.


Rapporteur:  Mr. Joul, Christopher
See also:  –


The objective of this Technical Report is to study and specify potential modifications to the ICS architecture in order to enable all services to be controlled via IMS rather than via CS legacy mechanisms (single service domain), for all subscribers of a network and also for inbound roamers.

As part of Release 8, 3GPP developed the concept of IMS Centralized Services which was then further extended in Release 9. While the goal of ICS was to enable an operator to provide communication services (such that all services and service control are centralized based on IMS mechanisms) on a per-subscriber basis, it has however not seen widespread deployment, as support of both domains is still necessary.

To achieve the goal of fully centralizing services and service control in the IMS domain, network based solutions will be studied that address the key issues and architectural assumptions defined in this document. In addition, these potential solutions will be evaluated against the existing mechanisms available in 3GPP technical specifications, before deciding whether to make changes to the relevant technical specifications.


 

Here        Top

 

1 Scope    2 References    3 Definitions and abbreviations    3.1 Definitions    3.2 Abbreviations    4 Architectural Assumptions    5 Key Issues    5.1 Key Issue 1 - Transition to Single Service Profile in IMS    5.2 Key Issue 2 - Emergency Calls Routed via IMS Service Domain    5.3 Key Issue 3 - Inbound Roamers from non-Enhanced Networks    5.4 Key Issue 4 - Outbound Roamers to non-Enhanced Networks    5.5 Key Issue 5 - Registration and Authentication    6 Solutions    6.1 Solution 1: Supporting inbound roamer with ICS Interworking Function    6.2 Solution 2: Supporting outbound roamer with an ICS Interworking Function    6.3 Solution 3: Re-using the existing ICS mechanism for Outbound Roamers to non-SeDoC Networks    6.4 Solution 4: Emergency Calls Routed via IMS Service Domain    6.5 Solution 5: MSC Server enhanced for SeDoC to support registration and authentication for non-roaming UEs    6.6 Solution 6: Re-using the existing mechanism for Roamers to non-Enhanced Networks    6.7 Solution 7: Control Layer ICS Interworking Function for Outbound Roamers    6.8 Solution 8: Registration and authentication for non-roaming UEs    6.9 Solution 9: Support of Single Service Profile in IMS    6.10 Solution 10: MSC Server enhanced for SeDoC registration and authentication for inbound roaming UEs    6.11 Solution 11: MSC Server enhanced for SeDoC    7 Void    8 Conclusions    A Change history   

 

1   Scope   Word-p. 6
2   References
3   Definitions and abbreviations   Word-p. 7
4   Architectural Assumptions
5   Key Issues   Word-p. 8
6   Solutions
6.1   Solution 1: Supporting inbound roamer with ICS Interworking Function
6.2   Solution 2: Supporting outbound roamer with an ICS Interworking Function   Word-p. 13
6.3   Solution 3: Re-using the existing ICS mechanism for Outbound Roamers to non-SeDoC Networks   Word-p. 17
6.4   Solution 4: Emergency Calls Routed via IMS Service Domain
6.5   Solution 5: MSC Server enhanced for SeDoC to support registration and authentication for non-roaming UEs   Word-p. 18
6.6   Solution 6: Re-using the existing mechanism for Roamers to non-Enhanced Networks
6.7   Solution 7: Control Layer ICS Interworking Function for Outbound Roamers
6.8   Solution 8: Registration and authentication for non-roaming UEs
6.9   Solution 9: Support of Single Service Profile in IMS   Word-p. 25
6.10   Solution 10: MSC Server enhanced for SeDoC registration and authentication for inbound roaming UEs   Word-p. 26      Up
6.11   Solution 11: MSC Server enhanced for SeDoC
6.11.1   Overview
6.11.2   SeDoC Architecture   Word-p. 29
6.11.3   SeDoCArchitecture for Inbound Roamers   Word-p. 34
6.11.4   Impacts on existing nodes and functionality   Word-p. 41
6.11.5   Solution Evaluation
7   Void
8   Conclusions
A   Change history   Word-p. 42

Up        Top