ETSI TS 124 238-2016 Universal Mobile Telecommunications System (UMTS) LTE Session Initiation Protocol (SIP) based user configuration Stage 3 (V13 0 0 3GPP TS 24 238 version 13 0 0.pdf

1、 ETSI TS 1Universal Mobile TelSession Initiation Prot(3GPP TS 24.2TECHNICAL SPECIFICATION124 238 V13.0.0 (2016elecommunications System (LTE; rotocol (SIP) based user confiStage 3 .238 version 13.0.0 Release 1316-01) (UMTS); figuration; 13) ETSI ETSI TS 124 238 V13.0.0 (2016-01)13GPP TS 24.238 versio

2、n 13.0.0 Release 13Reference RTS/TSGC-0124238vd00 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

3、/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 the prior

4、 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 present do

5、cument 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 http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the fo

6、llowing 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 PD

7、F 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 2016. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI

8、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 TS 124 238 V13.0.0 (2016-01)23GPP TS 24.238

9、 version 13.0.0 Release 13Intellectual 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 3

10、14: “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 investigat

11、ion, 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 Specificati

12、on (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. T

13、he cross 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

14、described 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 V13.0.0 (2016-01)33GPP TS 24.238 version 13.0.0 Release 13Contents Intellectual Pro

15、perty 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 requirem

16、ents 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 . 7g3Annex A (informative): Signalling flows 8g3A.1 User provisioning by SIP-based user configuration, announcement on established dialog . 8g3A.2

17、User provisioning by SIP-based user configuration, announcement on early dialog . 9g3Annex B (informative): Change history . 12g3History 13g3ETSI ETSI TS 124 238 V13.0.0 (2016-01)43GPP TS 24.238 version 13.0.0 Release 13Foreword This Technical Specification has been produced by the 3rdGeneration Par

18、tnership Project (3GPP). The contents of the present document are subject to continuing work within the 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 in

19、crease in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 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 enhancem

20、ents, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TS 124 238 V13.0.0 (2016-01)53GPP TS 24.238 version 13.0.0 Release 131 Scope The present document provides a Session Initiation Protocol (SIP) based protoco

21、l framework that serves as a means of user configuration of supplementary services in the IP Multimedia (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

22、Ut interface. The present document is applicable to User Equipment (UE) and Application Servers (AS) which 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

23、 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 doc

24、ument (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“. 2 3GPP TS 24.173: “IMS multimedia telephony communication service and supplementary

25、 services; Stage 3“. 3 3GPP TS 24.229: “IP Multimedia Call Control Protocol based on Session Initiation 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 (Decemb

26、er 2004): “The tel URI for Telephone Numbers“. 6 3GPP TS 24.315: “IP Multimedia Subsystem (IMS) 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

27、and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions 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 V13

28、.0.0 (2016-01)63GPP TS 24.238 version 13.0.0 Release 133.2 Abbreviations For the purposes of the 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 an

29、y, in 3GPP TR 21.905 1. 4 SIP based user configuration 4.1 General description SIP-based protocol 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 conve

30、y the configuration code to the Application Server that hosts the supplementary service. Upon session 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 upo

31、n the Request-URI contents to effect the desired configuration data change (e.g., register and activate 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 Requ

32、est-URI that comprise the effective dialstrings for user configuration are defined by the IM CN 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 o

33、perator preferences. The length of the digit sequence is also defined by the network operator. The 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 “p

34、hone-context“ parameter is set to the home network domain name and the “user“ parameter is set to “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

35、a “phone-context“ parameter set to the home network domain as defined in RFC 3966 5. NOTE 2: The 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

36、 for the implementation of SIP-based user configuration: 1) UE (SIP-based user configuration client); 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

37、4967 4, with: ETSI ETSI TS 124 238 V13.0.0 (2016-01)73GPP TS 24.238 version 13.0.0 Release 13a) 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-cont

38、ext“ parameter, set to the home network domain name. The UE shall construct and initiate an appropriate 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

39、 containing a URI configured as defined in bullet 1 of subclause 4.2, the AS shall perform service 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 d

40、efined in bullets 2 and 3 of subclause 4.2. In which case, the AS may treat this Request-URI as 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

41、 user of the result of the operation; or - send an appropriate error response in case the AS was unable to perform the requested service configuration operation. ETSI ETSI TS 124 238 V13.0.0 (2016-01)83GPP TS 24.238 version 13.0.0 Release 13Annex A (informative): Signalling flows A.1 User provisioni

42、ng by SIP-based user configuration, announcement on established dialog The signalling flow below illustrates the use of the SIP-based user configuration capability. This basic capability is used for activation, deactivation and configuration data modification. Figure A-1: User provisioning using fea

43、ture code 1-3. SIP INVITE request including the provisioning information to the provisioning AS as part of the Request URI - see example in table A.1-1. 4-9. Completion of call setup following normal procedures. Table A.1-1: INVITE request (UE-1 to P-CSCF) INVITE sip:*12345;phone-context=;user=dials

44、tring SIP/2.0 Via: SIP/2.0/UDP 5555:aaa:bbb:ccc:ddd:1357;comp=sigcomp;branch=z9hG4bKnashds7 Max-Forwards: 70 Route: , Accept-Contact: *;+g.3gpp.icsi-ref=“urn%3Aurn-7%3gpp-service.ims.icsi.mmtel“ P-Preferred-Identity: “John Doe“ P-Access-Network-Info: 3GPP-UTRAN-TDD; utran-cell-id-3gpp=234151D0FCE11

45、Privacy: none From: ;tag=171828 To: Call-ID: cb03a0s09a2sdfglkj490333 Cseq: 127 INVITE Require: sec-agree Supported: precondition, 100rel, gruu Proxy-Require: sec-agree Security-Verify: ipsec-3gpp; q=0.1; alg=hmac-sha-1-96; ealg=aes-cbc; spi-c=98765432; spi-s=87654321; port-c=8642; port-s=7531 ETSI

46、ETSI TS 124 238 V13.0.0 (2016-01)93GPP TS 24.238 version 13.0.0 Release 13Contact: ;comp=sigcomp;+g.3gpp.icsi-ref=“urn%3Aurn-7%3gpp-service.ims.icsi.mmtel“ Allow: INVITE, ACK, CANCEL, BYE, PRACK, UPDATE, REFER, MESSAGE Accept: application/sdp; application/3gpp-ims+xml Content-Type: application/sdp C

47、ontent-Length: () v=0 o=- 2987933615 2987933615 IN IP6 5555:aaa:bbb:ccc:ddd s=- c=IN IP6 5555:aaa:bbb:ccc:ddd t=0 0 m=audio 3456 RTP/AVP 97 96 b=AS:25.4 a=curr:qos local none a=curr:qos remote none a=des:qos mandatory local sendrecv a=des:qos none remote sendrecv a=inactive a=rtpmap:97 AMR a=fmtp:97

48、 mode-set=0,2,5,7; maxframes=2 a=rtpmap:96 telephone-event Request-URI: in this example, the configuration feature code is set to *12345 and is represented as a dialstring. SDP: the SDP is included for audio media, facilitating possible usage of audio announcements, DTMF tones and IVR interaction de

49、pending on how the network operator deploys the service configuration. 10. The AS performs feature activation, deactivation or configuration data modification based on the information received from the UE. 11. The AS can also, by interaction with an MRFC, announce the result of the configuration operation to UE-1. 12-17. After the provisioning is completed, UE-1 sends a BYE request to terminate the call with the AS. A.2 User provisioning by SIP-based user configuration, announcement on early dialog The signa