1、 ETSI TS 124 238 V14.0.0 (2017-03) Universal Mobile Telecommunications System (UMTS); LTE; Session Initiation Protocol (SIP) based user configuration; Stage 3 (3GPP TS 24.238 version 14.0.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 124 238 V14.0.0 (2017-03)13GPP TS 24.238 version 14.0.0 Relea
2、se 14Reference RTS/TSGC-0124238ve00 Keywords 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 (06) N 7803/88 Important
3、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 the prior written autho
4、rization 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 present document should
5、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 comment to one of the follow
6、ing 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. The content of the PDF ve
7、rsion 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 Trade Marks of ETSI regi
8、stered 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 TS 124 238 V14.0.0 (2017-03)23GPP TS 24.238 ver
9、sion 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 found in ETSI SR 000 314:
10、“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 Policy, no investigation,
11、 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 This Technical Specification (
12、TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present 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 c
13、ross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as desc
14、ribed in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 124 238 V14.0.0 (2017-03)33GPP TS 24.238 version 14.0.0 Release 14Contents Intellectual Propert
15、y Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g31 Scope 5g32 References 5g33 Definitions, symbols and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 6g34 SIP based user configuration 6g34.1 General description. 6g34.2 Syntax requirements . 6g34.3 Signalling requirements
16、 6g34.3.1 General 6g34.3.2 Actions at the originating UE (SIP-based user configuration client) 6g34.3.3 Actions at the AS serving the originating UE . 7g34.3.4 Password option 7g34.3.4.1 General 7g34.3.4.2 Procedures at the UE . 7g34.3.4.3 Procedures at the AS . 7g34.3.4.3.1 General 7g34.3.4.3.2 Pas
17、sword check . 8g34.3.4.3.3 Password change . 8g3Annex A (informative): Signalling flows 9g3A.1 User provisioning by SIP-based user configuration, announcement on established dialog . 9g3A.2 User provisioning by SIP-based user configuration, announcement on early dialog . 10g3Annex B (informative): C
18、hange history . 13g3History 14g3ETSI ETSI TS 124 238 V14.0.0 (2017-03)43GPP TS 24.238 version 14.0.0 Release 14Foreword This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The contents of the present document are subject to continuing work within th
19、e TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for in
20、formation; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second 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 bee
21、n incorporated in the document. ETSI ETSI TS 124 238 V14.0.0 (2017-03)53GPP TS 24.238 version 14.0.0 Release 141 Scope The present document provides a Session Initiation Protocol (SIP) based protocol framework that serves as a means of user configuration of supplementary services in the IP Multimedi
22、a (IM) Core Network (CN) subsystem. The protocol framework relies upon the contents of the Request-URI in a SIP INVITE request to enable basic configuration of services without requiring use of the Ut interface. The present document is applicable to User Equipment (UE) and Application Servers (AS) w
23、hich are intended to support user configuration of supplementary services. 2 References 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
24、, 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 versi
25、on of that document in the same Release as the present document. 1 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TS 24.173: “IMS multimedia telephony communication service and supplementary services; Stage 3“. 3 3GPP TS 24.229: “IP Multimedia Call Control Protocol based on Session Ini
26、tiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3“. 4 RFC 4967 (July 2007): “Dial String Parameter for the Session Initiation Protocol Uniform Resource Identifier“. 5 RFC 3966 (December 2004): “The tel URI for Telephone Numbers“. 6 3GPP TS 24.315: “IP Multimedia Subsystem (IMS)
27、Operator Determined Barring (ODB); Stage 3“. 7 3GPP TS 24.628: “Common Basic Communication procedures using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification“. 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, the terms and defini
28、tions given in 3GPP 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 3GPP TR 21.905 1. ETSI ETSI TS 124 238 V14.0.0 (2017-03)63GPP TS 24.238 version 14.0.0 Release 143.2 Abbreviations For the purposes of the
29、 present document, the abbreviations given in 3GPP 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 3GPP TR 21.905 1. 4 SIP based user configuration 4.1 General description SIP-based protoco
30、l framework serves as a means of user configuration of supplementary services in the IM CN subsystem specified in 3GPP TS 24.173 2. The contents of the Request-URI in a SIP INVITE request is used to convey the configuration code to the Application Server that hosts the supplementary service. Upon se
31、ssion initiation, the contents of the Request-URI are delivered by means of normal session setup signalling, as described in 3GPP TS 24.229 3 to an Application Server. The Application Server then acts upon the Request-URI contents to effect the desired configuration data change (e.g., register and a
32、ctivate Communication Forwarding unconditional). Procedures regarding Operator Determined Barring (ODB) are defined in 3GPP TS 24.315 6. 4.2 Syntax requirements The precise digit sequences within the Request-URI that comprise the effective dialstrings for user configuration are defined by the IM CN
33、subsystem service provider and are not subject to standardisation. NOTE 1: The digit sequence corresponding to the feature code can begin with a special character such as “#“ or “*“ according to network operator preferences. The length of the digit sequence is also defined by the network operator. T
34、he digit sequences corresponding to the feature code shall be transported to the AS in the Request-URI of a SIP INVITE request as follows: 1) as a SIP URI dial string conforming to RFC 4967 4 where the “phone-context“ parameter is set to the home network domain name and the “user“ parameter is set t
35、o “dialstring“; 2) as a SIP URI that is not a GRUU, with the user part preceded with a “+“, the “user“ parameter set to “phone“ and the domain part set to the home network domain; or 3) as a tel URI with a “phone-context“ parameter set to the home network domain as defined in RFC 3966 5. NOTE 2: The
36、 format for encoding of the digit sequence defined in the first bullet is the preferred format. The other two formats are now deprecated. 4.3 Signalling requirements 4.3.1 General Two roles are recognized for the implementation of SIP-based user configuration: 1) UE (SIP-based user configuration cli
37、ent); and 2) Application Server. 4.3.2 Actions at the originating UE (SIP-based user configuration client) When performing SIP-based user configuration, the UE shall create a SIP URI, as described in RFC 4967 4, with: ETSI ETSI TS 124 238 V14.0.0 (2017-03)73GPP TS 24.238 version 14.0.0 Release 14a)
38、a dialstring, set to either the concatenation of feature code and the number to be provisioned or the feature code alone if no number information needs to be provided for the service; and b) a “phone-context“ parameter, set to the home network domain name. The UE shall construct and initiate an appr
39、opriate INVITE in accordance with 3GPP TS 24.229 3 with the Request-URI set to the URI created above. 4.3.3 Actions at the AS serving the originating UE Upon receiving an INVITE request with a Request-URI containing a URI configured as defined in bullet 1 of subclause 4.2, the AS shall perform servi
40、ce activation, deactivation, or configuration data modification based on the recognized contents of the Request-URI. An AS can receive an INVITE request with a Request-URI containing a URI configured as defined in bullets 2 and 3 of subclause 4.2. In which case, the AS may treat this Request-URI as
41、a dial-string, as specified above. Based on the outcome of the service configuration operation, the AS may: - play an appropriate announcement using the methods specified in 3GPP TS 24.628 7 to notify the user of the result of the operation; or - send an appropriate error response in case the AS was
42、 unable to perform the requested service configuration operation. 4.3.4 Password option 4.3.4.1 General By using the subscription option “control of supplementary service“, the service configuration may be restricted by a password. The subscription option “control of supplementary service“ can be se
43、t to “by the service provider“ or “by subscriber using a password“. 4.3.4.2 Procedures at the UE When the subscription option “control of supplementary service“ is set to “by subscriber using a password“, the UE shall create the INVITE request as described in subclause 4.3.2 with a dialstring includ
44、ing either a password with a feature code or both the current password and a new password to be registered. 4.3.4.3 Procedures at the AS 4.3.4.3.1 General When the AS receives a Request URI in the INVITE request as defined in subclause 4.2 with a service configuration or a password change request, a
45、nd the subscription option “control of supplementary service“ is set to “by the service provider“, the AS shall send a 403 (Forbidden) error response. As a network option, the AS may play an appropriate announcement using the methods specified in 3GPP TS 24.628 7 to notify the user that the operatio
46、n is rejected. When the subscription option “control of supplementary service“ is set to “by subscriber using a password“, the AS shall perform the password management procedures that consist of two independent procedures: - password check; and - password change; The password check procedure is used
47、 for verifying the current password stored against the user: - when the user requests a password change; and ETSI ETSI TS 124 238 V14.0.0 (2017-03)83GPP TS 24.238 version 14.0.0 Release 14- when the user requests modification of a supplementary service configuration document for a service that has p
48、assword control. The password change procedure is used by the AS to set a new password for the user. The AS shall maintain a Wrong Password Attempts (WPA) counter. When the password is set by the service provider the AS shall reset the WPA counter to zero. If the AS receives a password that does not
49、 match the current password stored for the service, the AS shall increment the WPA counter by 1. If a password check passes at the AS, the AS shall reset the WPA counter to zero. If the WPA counter exceeds the value three, the AS shall set the subscription option “control of supplementary service“ to “by the service provider“. 4.3.4.3.2 Password check If the subscription option “control of supplementary service“ is set to “by subscriber using a password“ for a supplementary service configuration and a password change request is received
