Content for TR 23.719 Word version: 14.0.0
1 Scope
2 References
3 Definitions and abbreviations
3.1 Definitions
3.2 Abbreviations
4 Architectural Assumptions
...
...
1 Scope p. 6
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.
2 References p. 6
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 22.101: "Service aspects; Service principles ".
[3]
TS 23.292: "Multimedia Subsystem (IMS) centralized services".
[4]
TS 24.292: "IP Multimedia (IM) Core Network (CN) subsystem Centralized Services (ICS)".
[4a]
GSMA PRD IR.64: "IMS Service Centralization and Continuity Guidelines".
[5]
TS 24.008: "Mobile radio interface Layer 3 specification".
[6]
TR 23.883: "Study on enhancements to IMS Centralized Services (ICS)".
[7]
TR 23.892: "IP Multimedia Subsystem (IMS) centralized services".
[8]
TS 23.236: "Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes".
[9]
TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".
[10]
TS 23.002: "Network architecture".
[11]
TS 23.335: "User Data Convergence (UDC); Technical realization and information flows; Stage 2".
[12]
TS 29.335: "User Data Convergence (UDC); User Data Repository Access Protocol over the Ud interface; Stage 3".
[13]
TS 23.237: "IP Multimedia Subsystem (IMS) Service Continuity".
[14]
TS 23.216: "Single Radio Voice Call Continuity (SRVCC); Stage 2".
[15]
TS 23.167: "IP Multimedia Subsystem (IMS) emergency sessions".
[16]
TS 23.278: "Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 4; Stage 2; IM CN Interworking".
[17]
TS 29.002: "Mobile Application Part (MAP) specification".
3 Definitions and abbreviations p. 7
3.1 Definitions p. 7
For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
SeDoC Enhanced Network:
A network which supports the features or functions required for SeDoC
ICS Enhanced Network:
A network that supports ICS but does not support SeDoC.
Non-Enhanced Network:
A network that supports neither ICS nor SeDoC.
ICS UE:
A UE which supports the I1 Interface.
Non-ICS Enhanced UE:
A UE which does not support the I1 interface.
3.2 Abbreviations p. 7
For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
B2BUA
Back to Back User Agent
CS
Circuit Switched
eMSC
enhanced MSC
ICS
IMS Centralized Services
IMS
IP Multimedia Subsystem
IP
Internet Protocol
SeDoC
Service Domain Centralization
TAS
Telecom Application Server
4 Architectural Assumptions p. 7
The following architectural assumptions are valid to all potential solutions:
- There shall not be any impacts to the UE or the Access Networks.
- There shall be no changes to TS 24.008 to support SeDoC.
- Where possible SS7 based interfaces should be replaced with IP based interfaces (e.g. SIP/Diameter).
- A network enhanced for SeDoC shall support UEs enhanced for ICS and non-ICS enhanced UEs.
- The network enhanced for SeDoC shall not impact other networks interacting with it (e.g. roaming partners).
