Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x
Top   in Index   Prev   Next

TR 29.962
Signalling interworking between the
3GPP profile of the Session Initiation Protocol (SIP) and
non-3GPP SIP usage

3GPP‑Page   ETSI‑search   ToC  
V6.1.0 (PDF)  2003/10  55 p.
Rapporteur:
Dr. Belling, Thomas

full Table of Contents for  TR 29.962  Word version:  6.1.0

Here   Top

1  ScopeWord‑p. 6

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 TS 24.229, with related call flow examples in TS 24.228, 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 the 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 extensions:
Preconditions:
"Integration of Resource Management and SIP" RFC 3312;
Update:
"The Session Initiation Protocol UPDATE Method" RFC 3311;
100rel:
"Reliability of Provisional Responses in SIP" RFC 3262.
The present document focuses on the preconditions, the update and 100rel extensions because 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 performed 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 topics, 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 within 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 sense, 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.
Up

2  ReferencesWord‑p. 6

3  Definitions and AbbreviationsWord‑p. 7

3.1  DefinitionsWord‑p. 7

3.2  AbbreviationsWord‑p. 7

4  Session setup from calling 3GPP UA towards called non-3GPP UAWord‑p. 7

5  Session setup from calling non-3GPP UA towards called 3GPP UAWord‑p. 22

6  Implications of the Proposed SolutionsWord‑p. 34

6.1  B2BUAWord‑p. 34

6.2  Modified end-to-end call flowWord‑p. 35

A  Interworking topic templateWord‑p. 36

B  Mechanisms allowing optional Additions within SIPWord‑p. 37

C  Impacts of Session Setup Call flows where SIP extensions mandated by 3GPP are not applied.Word‑p. 40

D  Reference call flow from 3GPP UA to 3GPP UAWord‑p. 48

E  Scenarios without identified interworking issuesWord‑p. 50

$  Change historyWord‑p. 53


Up   Top