1、 ETSI TR 129 962 V6.1.0 (2003-09)Technical Report Universal Mobile Telecommunications System (UMTS);Signalling interworking between the 3GPP profile of theSession Initiation Protocol (SIP) and non-3GPP SIP usage(3GPP TR 29.962 version 6.1.0 Release 6)ETSI ETSI TR 129 962 V6.1.0 (2003-09) 1 3GPP TR 2
2、9.962 version 6.1.0 Release 6 Reference DTR/TSGN-0329962v610 Keywords 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)
3、 N 7803/88 Important notice Individual copies of the present document can be downloaded from: http:/www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the referenc
4、e version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change
5、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 following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright No
6、tification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2003. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI register
7、ed for the benefit of its Members. TIPHONTMand the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI TR 129 962 V6.1.0 (2003-09) 2
8、3GPP TR 29.962 version 6.1.0 Release 6 Intellectual 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
9、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 (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETS
10、I IPR Policy, 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
11、 This Technical Report (TR) 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
12、ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp . ETSI ETSI TR 129 962 V6.1.0 (2003-09) 3 3GPP TR 29.962 version 6.1.0 Release 6 Contents Intellectual Property Rights2 Foreword.2 Foreword.5 1 Scope 6 2 Refe
13、rences 6 3 Definitions and Abbreviations7 3.1 Definitions7 3.2 Abbreviations .7 4 Session setup from calling 3GPP UA towards called non-3GPP UA 7 4.1 Session setup towards a non-3GPP UA not making use of the SIP 100rel extension, the SIP preconditions extension and the SIP update extension.8 4.1.1 D
14、escription of interworking issue.8 4.1.2 Proposed Resolution B2BUA .8 4.1.3 Proposed Resolution Modified end-to-end call flow 13 4.2 Session setup towards a non-3GPP UA not making use of the SIP preconditions extension and the SIP update extension.15 4.2.1 Description of interworking issue.15 4.2.2
15、Proposed resolution B2BUA.15 4.2.3 Proposed resolution modified end-to-end call flow20 4.3 Session Setup towards non-3GPP UA not making use of the SIP preconditions extension.22 4.3.1 Description of interworking issue.22 4.3.2 Proposed Resolution B2BUA .22 4.3.3 Proposed Resolution Modified end-to-e
16、nd call flow 22 5 Session setup from calling non-3GPP UA towards called 3GPP UA 22 5.1 Session Setup from non-3GPP SIP UA not making use of the SIP 100rel extension, the SIP preconditions extension and the SIP update extension.23 5.1.1 Description of interworking issue.23 5.1.2 Proposed Resolution B
17、2BUA .23 5.1.3 Proposed Resolution Modified end-to-end call flow 26 5.2 Session setup from non-3GPP SIP UA not making use of the SIP preconditions extension and the SIP update extension.29 5.2.1 Description of interworking issue.29 5.2.2 Proposed resolution B2BUA.30 5.2.3 Proposed Resolution Modifie
18、d end-to-end call flow 31 5.3 Session setup from non-3GPP UA not making use of the SIP preconditions extension 33 5.3.1 Description of interworking issue.33 5.3.2 Proposed Resolution B2BUA .34 5.3.3 Proposed Resolution Modified end-to-end call flow 34 6 Implications of the Proposed Solutions34 6.1 B
19、2BUA.34 6.2 Modified end-to-end call flow35 Annex A: Interworking topic template 36 A.1 Description of interworking issue 36 A.2 Proposed Resolution yy 36 Annex B: Mechanisms allowing optional Additions within SIP 37 Annex C: Impacts of Session Setup Call flows where SIP extensions mandated by 3GPP
20、are not applied. 40 ETSI ETSI TR 129 962 V6.1.0 (2003-09) 4 3GPP TR 29.962 version 6.1.0 Release 6 C.1 Impacts of session setup call flows from calling 3GPP UA.40 C.1.1 Session setup towards non-3GPP UA not making use of the SIP 100rel extension, the SIP preconditions extension and the SIP update ex
21、tension .40 C.1.1.1 Description of interworking issue.40 C.1.1.2 Impacts of Identified interworking issue 42 C.1.2 Session Setup towards non-3GPP UA not making use of the SIP preconditions extension and the SIP update extension.42 C.1.2.1 Description of interworking issue.42 C.1.2.2 Impacts of ident
22、ified interworking issue.43 C.1.3 Session setup towards non-3GPP UA not making use of the SIP preconditions extension .44 C.2 Impacts of session setup towards called 3GPP UA44 C.2.1 Non-3GPP SIP UA not making use of the SIP 100rel extension, the SIP preconditions extension and the SIP update extensi
23、on 44 C.2.1.1 Description of interworking issue.44 C.2.1.2 Impacts of identified interworking issue.45 C.2.2 Non-3GPP SIP UA not making use of the SIP preconditions extension and the SIP update extension.46 C.2.2.1 Description of interworking issue.46 C.2.2.2 Impacts of identified interworking issue
24、47 C.2.3 Non-3GPP UA not making use of the SIP preconditions extension.47 Annex D: Reference call flow from 3GPP UA to 3GPP UA.48 Annex E: Scenarios without identified interworking issues.50 E.1 Calling non-3GPP UA supporting the 100rel SIP extension, the SIP preconditions extension and the SIP upd
25、ate extension, but not performing QoS reservation, to called 3GPP UA.51 E.2 Calling non-3GPP UA supporting the 100rel SIP extension, the SIP preconditions extension and the SIP update extension, but not including the SDP offer in the initial INVITE request, to called 3GPP UA51 Annex F: Change histor
26、y 53 History 54 ETSI ETSI TR 129 962 V6.1.0 (2003-09) 5 3GPP TR 29.962 version 6.1.0 Release 6 Foreword This Technical Report has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following
27、 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 information; 2 presented to TSG
28、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 been incorporated in the document
29、 ETSI ETSI TR 129 962 V6.1.0 (2003-09) 6 3GPP TR 29.962 version 6.1.0 Release 6 1 Scope The present document investigates the SIP signalling interworking between entities of IM CN subsystems behaving as specified in the 3GPP profile of SIP and SDP in 3GPP TS 24.229 1, with related call flow example
30、s in 3GPP TS 24.228 2, and SIP network entities external to the IM CN subsystems, which may not adhere to the 3GPP profile of SIP and SDP. The present document assumes that GPRS access and service based local policy using the Go interface is applied. Non-GPRS access to IMS may have implications on t
31、he TR, which are not yet discussed. The considered SIP network entities external to the IM CN subsystems may feature different SIP capabilities, such as the support of arbitrary SIP options. The document focuses on scenarios where the non-3GPP UA does not support one or more of the following SIP ext
32、ensions: Preconditions: “Integration of Resource Management and SIP“ RFC 3312 5; Update: “The Session Initiation Protocol UPDATE Method“ RFC 3311 7; 100rel: “Reliability of Provisional Responses in SIP“ RFC 3262 6. The present document focuses on the preconditions, the update and 100rel extensions b
33、ecause only these extensions imply interworking issues since they require the end-to-end cooperation of both UAs. Security interworking may also have implications on the TR, which are not yet discussed. The present document does not make any a priori assumptions where a possible interworking is perf
34、ormed within the IM CN subsystem. Any SIP network entity within the IM CN subsystem may take part in the interworking. The network entities that may become involved in a certain interworking topic are identified for each of these topics separately. The present document features a discussion of topic
35、s, where an interworking is possibly required. Aspects of the 3GPP profile of SIP and SDP, which obviously do not require any interworking, are not discussed. An assessment of the impact and probability of occurrence of the discussed scenarios is also provided. Problems due to network elements withi
36、n the IM CN subsystem, which do not or only partly satisfy the 3GPP profile of SIP and SDP, in particular non 3GPP compliant SIP UAs, are out of scope of the present document. The present document is dedicated exclusively to issues inherent in the SIP and SDP signalling. Related topics in a wider se
37、nse, such as IPv6 to IPv4 address translation or user plane transcoding are out of scope. For brevity, in what follows the above SIP extensions are only mentioned if a SIP UA does not make use of them. Otherwise, it is understood that the UA makes use of them. 2 References The following documents co
38、ntain 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-spec
39、ific 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 3GPP TS 24.229: “IP Multimedia Call Control Protocol
40、based on SIP and SDP; Stage 3“. ETSI ETSI TR 129 962 V6.1.0 (2003-09) 7 3GPP TR 29.962 version 6.1.0 Release 6 2 3GPP TS 24.228: “Signalling flows for the IP multimedia call control based on SIP and SDP; Stage 3“. 3 3GPP TS 23.228: “IP Multimedia Subsystem (IMS); Stage 2“. 4 IETF RFC 3261: “SIP: Ses
41、sion Initiation Protocol“. 5 IETF RFC 3312: “Integration of Resource Management and Session Initiation Protocol (SIP)“. 6 IETF RFC 3262: “Reliability of Provisional Responses in Session Initiation Protocol (SIP)“. 7 IETF RFC 3311: “The Session Initiation Protocol (SIP) UPDATE Method“. 8 IETF RFC 326
42、4: “An Offer/Answer Model with Session Description Protocol (SDP)“. 9 3GPP TS 29.208: “End to end Quality of Service (QoS) signalling flows“. 10 3GPP TS 32.225: “Telecommunication management; Charging management; Charging data description for the IP Multimedia Subsystem (IMS)“. 11 3GPP TS 29.207: “P
43、olicy control over Go interface“. 3 Definitions and Abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in 3GPP TS 24.229 1, RFC 3261 4 and the following apply: 3GPP profile of SIP: specification of the usage of SIP within 3GPP networks in 3GPP TS
44、24.229 1. SIP-preconditions extension: SIP and SDP “precondition“ extensions, as defined in RFC 3312 5 SIP update extension: SIP “update“ extension, including the SIP “UPDATE“ method, as defined in RFC 3311 7 SIP 100rel extension: SIP “100rel“ extension, including the SIP “PRACK“ method, as defined
45、in RFC 3262 6 Not making use of the SIP 100rel extension: the UA is either supporting the SIP 100rel extension but not willing to use it, or not supporting it at all. Not making use of the SIP update extension: the UA is either supporting the SIP update extension but not willing to use it, or not su
46、pporting it at all. Not making use of the SIP precondition extension: the UA is either supporting the SIP precondition extension but not willing to use it, or not supporting it at all. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in 3GPP TS 24.229 1 and RFC 326
47、1 4 apply. 4 Session setup from calling 3GPP UA towards called non-3GPP UA Each topic is contained in its own subclause with the structure defined in annex A. The following scenarios are not considered, since they are not compliant with RFC 3312 5, clause 11: Session Setup towards non-3GPP UA not ma
48、king use of the SIP 100rel extension. ETSI ETSI TR 129 962 V6.1.0 (2003-09) 8 3GPP TR 29.962 version 6.1.0 Release 6 Session Setup towards non-3GPP UA not making use of the SIP update extension. Session Setup towards non-3GPP UA not making use of the SIP 100rel extension and the SIP update extension
49、 A UA that supports the SIP preconditions extension shall also support the SIP 100rel extension and the SIP update extension. Therefore it includes the “precondition“ tag in the Require or in the Supported header, the “100rel“ tag in the Supported header and the “Update“ tag in the Allow header. 4.1 Session setup towards a non-3GPP UA not making use of the SIP 100rel extension, the SIP preconditions extension and the SIP update extension 4.1.1 Description of interworking issue Since the originating 3GPP UA requires
