tech-invite   World Map     

3GPP     Specs     Glossaries     Architecture     IMS     UICC       IETF     RFCs     Groups     SIP     ABNFs       Search

Top          in Index          Prev          Next

TS 29.231 (CT4)
Application of SIP-I Protocols to Circuit Switched (CS) core network architecture – Stage 3

|   ToC   |   3GPP‑Page   |   ETSI‑search   |   Help   |

(P) V14.0.0    2017/03    24 p.
(P) V13.0.0    2015/12    24 p.
(P) V12.0.0    2014/09    24 p.
(P) V11.0.0    2012/09    24 p.
(P) V10.0.0    2011/04    24 p.
(P) V9.1.0    2010/04    23 p.
(P) V8.4.0    2010/04    23 p.


Rapporteur:  Mrs. Biondic, Nevenka
See also:  SIP-I-related TS/TR    


This TS describes the protocols to be used when SIP-I is optionally used as call control protocol in a 3GPP CS core network on Nc interface, see TS 23.231. The SIP-I protocol operates between (G)MSC servers.

The SIP-I architecture consists of a number of protocols. The following types of protocols are described: call control protocol, resource control protocols and user plane protocol for this architecture. The architecture complies with the requirements imposed by TS 23.231 and TS 23.153.

This TS is valid for a 3rd generation PLMN (UMTS) complying with Release 8 and later.


 

Here          Top          None          None          Next
part:    1     2

 

1 Scope    2 References    3 Definitions, symbols and abbreviations    3.1 Definitions    3.2 Symbols    3.3 Abbreviations    4 Protocols    4.1 Introduction    4.2 Call control protocol (Nc interface)    4.3 Resource control protocol (G)MSC and MGW (Mc Interface)    4.4 Bearer Framing Protocol between MGWs (Nb interface)    4.5 Signalling Transport    4.6 Payload Types    5 Amendments and Endorsements to Referenced Specifications    5.1 ITU-T Q.1912.5 (Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control protocol or ISDN User Part)    5.2 IETF RFC 2046 (Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types)    5.3 IETF RFC 4566 (SDP: Session Description Protocol)    5.4 IETF RFC 3966 (The tel URI for Telephone Numbers)    5.5 IETF RFC 2976 (The SIP INFO method)    5.6 IETF RFC 3204 (MIME media types for ISUP and QSIG Objects)    5.7 IETF RFC 3261(SIP: Session Initiation Protocol)    5.8 IETF RFC 3262 (Reliability of Provisional Responses in the Session Initiation Protocol)    5.9 IETF RFC 3264 (An Offer/Answer Model with the Session Description Protocol)    5.10 IETF RFC 3311 (The Session Initiation Protocol (SIP) UPDATE Method)    5.11 IETF RFC 3312 (Integration of Resource Management and Session Initiation Protocol)    5.12 IETF RFC 3323 (A Privacy Mechanism for the Session Initiation Protocol)    5.13 IETF RFC 3325 (Private Extensions to the Session Initiation Protocol (SIP) for Network Asserted Identity within Trusted Networks)    5.14 IETF RFC 3326 (The Reason Header Field for the Session Initiation Protocol)    5.15 IETF RFC 4028 (Session Timers in the Session Initiation Protocol)    5.16 IETF RFC 4960 (Stream Control Transmission Protocol)    5.17 Void    5.18 IETF RFC 4168 (The Stream Control Transmission Protocol (SCTP) as a Transport for the Session Initiation Protocol)    5.19 IETF RFC 791 (Internet Protocol, Version 4)    5.20 IETF RFC 2460 (Internet Protocol, Version 6)    5.21 IETF RFC 4715 (The Integrated Services Digital Network (ISDN) Subaddress Encoding Type for tel URI)    5.22 IETF RFC 4320 (Actions Addressing Identified Issues with the Session Initiation Protocol's (SIP) Non- INVITE Transaction)    5.23 IETF RFC 5079 (Rejecting Anonymous Requests in the Session Initiation Protocol (SIP))   
...

 

1   Scope   PDF-p. 6
2   References
3   Definitions, symbols and abbreviations   PDF-p. 7
4   Protocols
5   Amendments and Endorsements to Referenced Specifications   PDF-p. 11
5.1   ITU-T Q.1912.5 (Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control protocol or ISDN User Part)
5.2   IETF RFC 2046 (Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types)
5.3   IETF RFC 4566 (SDP: Session Description Protocol)
5.4   IETF RFC 3966 (The tel URI for Telephone Numbers)   PDF-p. 12      Up
5.5   IETF RFC 2976 (The SIP INFO method)
5.6   IETF RFC 3204 (MIME media types for ISUP and QSIG Objects)
5.7   IETF RFC 3261(SIP: Session Initiation Protocol)
5.8   IETF RFC 3262 (Reliability of Provisional Responses in the Session Initiation Protocol)   PDF-p. 13
5.9   IETF RFC 3264 (An Offer/Answer Model with the Session Description Protocol)
5.10   IETF RFC 3311 (The Session Initiation Protocol (SIP) UPDATE Method)
5.11   IETF RFC 3312 (Integration of Resource Management and Session Initiation Protocol)
5.12   IETF RFC 3323 (A Privacy Mechanism for the Session Initiation Protocol)
5.13   IETF RFC 3325 (Private Extensions to the Session Initiation Protocol (SIP) for Network Asserted Identity within Trusted Networks)   PDF-p. 15
5.14   IETF RFC 3326 (The Reason Header Field for the Session Initiation Protocol)
5.15   IETF RFC 4028 (Session Timers in the Session Initiation Protocol)
5.16   IETF RFC 4960 (Stream Control Transmission Protocol)
5.17   Void
5.18   IETF RFC 4168 (The Stream Control Transmission Protocol (SCTP) as a Transport for the Session Initiation Protocol)
5.19   IETF RFC 791 (Internet Protocol, Version 4)   PDF-p. 16      Up
5.20   IETF RFC 2460 (Internet Protocol, Version 6)
5.21   IETF RFC 4715 (The Integrated Services Digital Network (ISDN) Subaddress Encoding Type for tel URI)
5.22   IETF RFC 4320 (Actions Addressing Identified Issues with the Session Initiation Protocol's (SIP) Non- INVITE Transaction)
5.23   IETF RFC 5079 (Rejecting Anonymous Requests in the Session Initiation Protocol (SIP))

Up          Top          ToC