1、 ETSI TR 122 983 V14.0.0 (2017-03) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Services alignment and migration (3GPP TR 22.983 version 14.0.0 Release 14) TECHNICAL REPORT ETSI ETSI TR 122 983 V14.0.0 (2017-03)13GPP TR 22.983 v
2、ersion 14.0.0 Release 14Reference RTR/TSGS-0122983ve00 Keywords GSM,LTE,UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (0
3、6) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without
4、the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat. Users of the p
5、resent document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your comme
6、nt to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI. Th
7、e content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2017. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are T
8、rade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TR 122 983 V14.0.0 (2017
9、-03)23GPP TR 22.983 version 14.0.0 Release 14Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be fou
10、nd in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (https:/ipr.etsi.org/). Pursuant to the ETSI IPR Po
11、licy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword The pre
12、sent document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under ht
13、tp:/webapp.etsi.org/key/queryform.asp. Modal verbs terminology In the present document “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“
14、 and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TR 122 983 V14.0.0 (2017-03)33GPP TR 22.983 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g31 Scope 5g32 References 5g33 Defini
15、tions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 5g34 Definition of Service Sets in different domains . 6g34.1 CS/PS (non-IMS) domain 6g34.1.1 CS Services (teleservices 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second
16、 digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TR 122 983 V14.0.0 (2017-03)53GPP TR 22.983 version 14.0.0 Release 141 Scope This
17、 document studies how services to the end user should be delivered and managed regardless of how the user accesses the services (e.g. using CS or IMS) and to ensure a consistent user experience. The services in scope include but are not restricted to: Conversational voice and video services Messagin
18、g services Supplementary Services as applied to the above. For each of the above types, the service features that should be supported when accessing the service via CS or IMS using any appropriate access type are described. Also, how each service will behave when transferring between domains is desc
19、ribed. The work will also consider how to support existing (“traditional“) services while allowing new, innovative services to be provided to the end user using the enhanced capabilities of the IMS. It will cover possible migration paths from where services are provided on both CS and IMS to IMS Cal
20、l and Service Control. Also, this work will consider roaming and call handling, interaction with legacy terminals, and the provision of user state and location for services accessed via CS or IMS and for services transferred between them. 2 References The following documents contain provisions which
21、, 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 la
22、test 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 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 3 Definitions and abb
23、reviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TR 21.905 1 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 1. 3.2 Abbreviations For the purposes of the
24、 present document, the abbreviations given in TR 21.905 1 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 1. ETSI ETSI TR 122 983 V14.0.0 (2017-03)63GPP TR 22.983 version 14.0.0 Release 144 D
25、efinition of Service Sets in different domains 4.1 CS/PS (non-IMS) domain 4.1.1 CS Services (teleservices b) 3G (UMTS) radio access network connected to Circuit Switched and Packet Switched core; c) 2G (GSM/GPRS) radio access network connected to IMS via the PS core; d) 3G (UMTS) radio access networ
26、k connected to IMS via the PS core; e) WLAN radio access network connected to Circuit Switched and Packet Switched core (GAN); f) WLAN radio access network connected to IMS via the PS core. Each of the above connection scenarios will have its own service characteristics. There is a range of access s
27、peeds from the radio access networks and a range of capabilities from the core networks and these will determine how a particular service can be delivered and, therefore, the customer experience. 5.2 Network configurations For many operators networks, there will be a range of connection scenarios in
28、 use as described above. This will arise as the core networks and access networks are upgraded. The options for how networks are upgraded are described in Core NetworksAccess NetworksIuGbAGatewayIMSApplication ServersTransportSignallingUTRANPS(SGSN - GGSN)Other (e.g. WIMAX)Fixed IPGSM/ GPRSGatewaysC
29、S(MSC) GbAIPWLANGAN-CETSI ETSI TR 122 983 V14.0.0 (2017-03)113GPP TR 22.983 version 14.0.0 Release 14section 6, below. What is clear is that most operators will have networks in which there are mixed capabilities for a considerable period and that the way services are managed needs to be considered.
30、 The key points to consider concerning customer service experience are described below. 5.3 Service experience The users service experience needs to be consistent depending on the connection scenario used. Specifically, the following is required: The use of Supplementary Services should be applied c
31、onsistently across domains and, as a default, the setting of SS parameters in one domain should be reflected in the other domain. For example, any Call Forwarding and Call Barring numbers set by the user should be retained and used whichever domain is used. It should, however, be possible to set dif
32、ferent parameters in different domains if required. For example, capability to have different settings for Supplementary Services in IMS for enhanced services such as Multimedia Telephony Service should be possible. The smooth transition of services as the user moves from one connection scenario to
33、another. If the user moves from a high capability scenario to a low capability scenario (e.g. from 3G/IMS to 2G/Circuit Switched) the service should be degraded gracefully. An example is the degradation of Multimedia Telephony to a voice only call. Subsequently, if the user moves back to a high capa
34、bility scenario, the added features should become available again. 6 Use cases 6.1 Use case 1, MSC server control of all accesses This use case describes the situation where an operator has introduced packet access and support for the services and service control on the MSC Server. Initially users h
35、ave voice service over CS on GSM/UMTS. Service and control for this is provided by the MSC. Voice service is transferred to VoIP on UMTS and WLAN. Service and control for VoIP is provided by MSC Server. The user should be unaware of the change. For example, there should be no need for the user to ch
36、ange any settings (e.g. for supplementary services), and the services delivered should be as good as or better than before. 6.2 Use case 2, migrating to IMS This use case describes the situation where an operator is undertaking a migration and has different configurations in the network in different
37、 regions. Users on this operator use newer networks in part of the country and fallback to older networks elsewhere. For example, in the cities there is WiMAX, HSPA, UMTS and GSM/GPRS controlled by IMS; in urban areas there is HSPA, UMTS and GSM/GPRS controlled by MSC Servers and in rural areas ther
38、e is just GSM/GPRS controlled by MSCs. The user should experience a minimum service level when on the legacy part of the network and should generally be unaware that he/she is using the more advanced parts of the network except for the availability of new and improved services where provided. Additi
39、onally, there should be no need for the user to change any settings (e.g. for supplementary services) when moving from one part of the network to another. 6.3 Use case 3, after migration to IMS This use case describes the situation where an operator has migrated all services and service control onto
40、 IMS from the traditional GSM network Initially, users have voice service over CS, text messaging (SMS) over GSM and IM/Presence service over GSM/GPRS. Voice and SMS service and control are provided over MSCs/CAMEL; IM/Presence service and control is ETSI ETSI TR 122 983 V14.0.0 (2017-03)123GPP TR 2
41、2.983 version 14.0.0 Release 14provided over dedicated platform in the core network. All of these services have been migrated to IP based technology. All services are now provided and controlled by IMS. The user should be unaware of the migration except for the availability of new and improved servi
42、ces. For example, there should be no need for the user to change any settings (e.g. for supplementary services), and the services delivered should be as good as or better than before. 6.4 Use case 4, inter-working between IMS & CS based networks This use case describes the situation where users in a
43、 network that has completely migrated to IMS service and service control are communicating with users on legacy (CS based) networks. Users on their Home PLMN have VoIP voice service provided and controlled by IMS. They need to be able to connect with other users on other networks who have voice serv
44、ice over CS that is provided and controlled by MSCs/CAMEL. The user should be unaware that he/she is communicating with a user on a network with a different configuration. All supplementary services should continue to work correctly and as expected. 6.5 Use case 5, roaming This use case describes th
45、e situation where a user from a network that has completely migrated to IMS service and service control roams on a legacy (CS based) network. Users on their Home PLMN have VoIP voice service provided and controlled by IMS. A user roams onto a VPLMN that has voice services provided and controlled by
46、MSCs/CAMEL. The VPLMN does not support PS access of sufficient quality for VoIP. The user should be unaware that he/she is roaming on a legacy network except that some advanced services may not be available. There should be no difference in how the voice service is used including the use of suppleme
47、ntary services. From the operator perspective, calls to and from the user should be handled in the most cost-effective manner. For example, outgoing calls from that user in the VPLMN should be handled locally with efficient routing of connections to and from the Home PLMN. 7 Migration scenarios 7.1
48、Background Currently only one service is defined for the IMS, which is similar to an existing CS service, i.e. the Multimedia Telephony Service. Although it can be expected that also other services will be defined there will always be a set of services and features which is not available in the IMS
49、or which has slightly different behaviour, despite a possible alignment. For existing customers consistent service behaviour is very important. Adding new services and features is possible but it is nearly impossible to change or delete others (e.g. fax). Additionally more and more different access systems are integrated (such as WiFi, WiMax, LTE etc.) and subscribers want to use their services regardless of the access, even regardless if the move from one access to the other (cp. VCC). With these basic conditions several migration scenarios
