1、3GPP TS 24.238 V8.0.0 (2008-12)Technical Specification3rd Generation Partnership Project;Technical Specification Group Core Network and Terminals;Session Initiation Protocol (SIP) based user configuration;Stage 3(Release 8)The present document has been developed within the 3rd Generation Partnership
2、 Project (3GPP TM) and may be further elaborated for the purposes of 3GPP.The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.This Specification is provided for future development work within 3GPP only. The Organizational
3、 Partners accept no liability for any use of this Specification.Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organizational Partners Publications Offices.3GPP3GPP TS 24.238 V8.0.0 (2008-12)2Release 8KeywordsSIP, IMS, IP, Multimedia, UMTS, LTE3GP
4、PPostal address3GPP support office address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16Internethttp:/www.3gpp.orgCopyright NotificationNo part may be reproduced except as authorized by written permission.The copyright and the foregoing restr
5、iction extend to reproduction in all media. 2008, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).All rights reserved.UMTS is a Trade Mark of ETSI registered for the benefit of its members3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizat
6、ional PartnersLTE is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational PartnersGSM and the GSM logo are registered and owned by the GSM Association3GPP3GPP TS 24.238 V8.0.0 (2008-12)3Release 8ContentsForeword .41 Scope.52 References.53 Defi
7、nitions, symbols and abbreviations53.1 Definitions .53.2 Abbreviations.64 SIP based user configuration 64.1 General description64.2 Syntax requirements 64.3 Signalling requirements.64.3.1 General.64.3.2 Actions at the originating UE (SIP-based user configuration client).64.3.3 Actions at the AS serv
8、ing the originating UE7Annex A (informative): Signalling flows.8A.1 User provisioning by SIP-based user configuration .8Annex B (informative): Change history103GPP3GPP TS 24.238 V8.0.0 (2008-12)4Release 8ForewordThis Technical Specification has been produced by the 3rd Generation Partnership Project
9、 (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 increase in version
10、 number as follows:Version x.y.zwhere: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 enhancements, corrections, updat
11、es, etc.z the third digit is incremented when editorial only changes have been incorporated in the document.3GPP3GPP TS 24.238 V8.0.0 (2008-12)5Release 81 ScopeThe present document provides a Session Initiation Protocol (SIP) based protocol framework that serves as a means of user configuration of s
12、upplementary 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 Ut interface.The present document is applicable to User Equip
13、ment (UE) and Application Servers (AS) which are intended to support user configuration of supplementary services.2 ReferencesThe following documents contain provisions which, through reference in this text, constitute provisions of the present document. References are either specific (identified by
14、 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 impli
15、citly 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 services; Stage 3“.3 3GPP TS 24.229: “IP Multimedia Call Control
16、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 (December 2004): “The tel URI for Telephone Numbers“.3 Definitions, symbols
17、and abbreviations3.1 DefinitionsFor 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.3GPP3GPP TS 24.238 V8.0.0 (
18、2008-12)6Release 83.2 AbbreviationsFor 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 any, in 3GPP TR 21.905 1.4 SIP based use
19、r configuration4.1 General descriptionSIP-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 convey the configuration code to the Applicati
20、on Server that hosts the supplementary service. The “user=“ parameter within the Request-URI is set by the UE to value “dialstring“ as described in RFC 4967 4. Upon session initiation, the contents of the Request-URI are delivered by means of normal session setup signalling, as described in 3GPP TS
21、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 activate Communication Forwarding unconditional).Editors note: How the UE selects the service configuration mechanism, either use of X
22、CAP over Ut interface or SIP-based user configuration, is FFS.4.2 Syntax requirementsThe precise digit sequences within the Request-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: Th
23、e 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.The digit sequences corresponding to the feature code shall be transported to t
24、he AS in the Request-URI of a SIP INVITE request as follows:- 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 to “dialstring“;- as a SIP URI that is not a GRUU and with the user part starting
25、 with a + and the “user“ parameter equals “phone“. The domain is set to the home network domain; or- as a tel-URI with a “phone-context“ parameter set to the home network domain as defined in RFC 3966 5.4.3 Signalling requirements4.3.1 GeneralTwo roles are recognized for the implementation of SIP-ba
26、sed user configuration: 1) UE (SIP-based user configuration client); and2) 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:a) a dialstring, set to
27、 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; and3GPP3GPP TS 24.238 V8.0.0 (2008-12)7Release 8b) a “phone-context“ parameter, set to the home network domain name.The UE shall constru
28、ct 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 UEUpon receiving an INVITE request with Request-URI containing a SIP URI including a “phone-context” parameter equal to the home
29、 network domain name, a “user=“ parameter set to value “dialstring“, and a dialstring representing a feature code or a concatenation of feature code and number to be provisioned, the AS shall:a) accept the INVITE request following the procedures specified for AS acting as a terminating UA in 3GPP TS
30、 24.229 3; andb) perform service activation, deactivation, or configuration data modification based on the recognized contents of the Request-URI.Based on the outcome of the service configuration operation, the AS may play an appropriate announcement to notify the user of the result of the operation
31、.NOTE: The Request-URI of the received INVITE request can contain a SIP URI with the “user=“ parameter set to value “phone“ or a Tel-URI. The AS can treat this Request-URI as a dialstring.3GPP3GPP TS 24.238 V8.0.0 (2008-12)8Release 8Annex A (informative):Signalling flowsA.1 User provisioning by SIP-
32、based user configurationThe 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.U E - 1 P - C S C F S - C S C F A S1 . I N V I T E ( * d d - x x x x x x x x )4 . 2 0 0
33、 O K ( I N V I T E )5 . 2 0 0 O K ( I N V I T E )6 . 2 0 0 O K ( I N V I T E )7 . A C K8 . A C K9 . A C K1 1 . R e s u l t a n n o u n c e m e n t1 2 . B Y E1 3 . B Y E1 4 . B Y E1 5 . 2 0 0 O K ( B Y E )1 6 . 2 0 0 O K ( B Y E )1 7 . 2 0 0 O K ( B Y E )2 . I N V I T E ( * d d - x x x x x x x x )3 .
34、 I N V I T E ( * d d - x x x x x x x x )1 0 . F e a t u r e c o d e a c t i v a t i o n /d e - a c t i v a t i o n i s p e r f o r m e d .Figure A-1: User provisioning using feature code1-9. UE-1 establishes a call with the provisioning AS following normal call setup procedure. UE-1 sends the provis
35、ioning information as part of the Request URI.Table A.1-1: INVITE request (UE-1 to P-CSCF)INVITE sip:*12345;phone-context=;user=dialstring SIP/2.0Via: SIP/2.0/UDP 5555:aaa:bbb:ccc:ddd:1357;comp=sigcomp;branch=z9hG4bKnashds7Max-Forwards: 70Route: , Accept-Contact: *;+g.3gpp.icsi_ref=“urn%3Aurn-xxx%3g
36、pp-service.ims.icsi.mmtel“P-Preferred-Identity: “John Doe“ P-Access-Network-Info: 3GPP-UTRAN-TDD; utran-cell-id-3gpp=234151D0FCE11Privacy: noneFrom: ;tag=171828To: Call-ID: cb03a0s09a2sdfglkj490333 Cseq: 127 INVITERequire: sec-agreeSupported: precondition, 100rel, gruu Proxy-Require: sec-agreeSecuri
37、ty-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=7531Contact: ;comp=sigcomp;+g.3gpp.icsi_ref=“urn%3Aurn-xxx%3gpp-service.ims.icsi.mmtel“Allow: INVITE, ACK, CANCEL, BYE, PRACK, UPDATE, REFER, MESSAGE3GPP3GPP TS 24.238 V8.0.0 (2008-12)9
38、Release 8Accept: application/sdp; application/3gpp-ims+xmlContent-Type: application/sdp Content-Length: ()v=0o=- 2987933615 2987933615 IN IP6 5555:aaa:bbb:ccc:ddds=-c=IN IP6 5555:aaa:bbb:ccc:ddd t=0 0m=audio 3456 RTP/AVP 97 96b=AS:25.4a=curr:qos local nonea=curr:qos remote nonea=des:qos mandatory lo
39、cal sendrecva=des:qos none remote sendrecva=inactivea=rtpmap:97 AMR a=fmtp:97 mode-set=0,2,5,7; maxframes=2a=rtpmap:96 telephone-eventRequest-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, facilitatin
40、g possible usage of audio announcements, DTMF tones and IVR interaction depending 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, b
41、y 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.3GPP3GPP TS 24.238 V8.0.0 (2008-12)10Release 8Annex B (informative):Change historyChange historyDate TSG # TSG
42、 Doc. CR Rev Subject/Comment Old New2008-04 Version 0.0.0 TS Skeleton 0.0.02008-04 C1-081430: “ Scope and General description for SIP based user configuration“0.1.02008-04 C1-08146: “ Text for syntax and signalling requirements for SIP based user configuration“0.1.02008-04 C1-081112: “ Example signa
43、lling flows for SIP based used configuration“0.1.02008-05 Implemented C1-081948, C1-082046 0.2.02008-07 Implemented C1-082447 from CT1#54 0.3.02008-08 Implemented C1-082958, C1-083203, C1-083396 0.4.02008-09 Version 1.0.0 created for presentation to TSG CT#41 for information0.4.0 1.0.02008-11 Miscellaneous editorial cleanups. 1.0.0 1.0.12008-11 Version 2.0.0 created for presentation to TSG CT#42 for approval1.0.1 2.0.02008-12 CT#42 Version 8.0.0 created after approval in CT#42 2.0.0 8.0.0
