Content for TR 24.969 Word version: 17.0.0
1 Scope p. 7
The purpose of the present document is to give an implementation guide to the relevant Common IMS specifications and functions used in the interconnection of a Next Generation Corporate Network site (NGCN site) to the NGN.
The present document addresses control plane signalling (usage of SIP and SDP protocols, required SIP headers) as well as other interconnecting aspects like security, numbering/naming/addressing and user plane issues such as transport protocol, media and codecs actually covered in a widespread set of 3GPP and ETSI TISPAN specifications, as seen from the perspective of an NGCN site.
Advice-of-charge aspects are addressed as far as SIP signalling is concerned.
The present document is based on TS 24.229.
2 References p. 7
The following documents contain 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-specific 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]
[93] Void.
[94]
RFC 3261 (2002): "SIP: Session Initiation Protocol".
[2]
TS 22.519: "; Business communication requirements, stage 1".
[3]
TS 24.525: "Business trunking; Architecture and functional description".
[4]
TS 24.523: "Core and enterprise NGN interaction scenarios; Architecture and functional description".
[5]
RFC 2976 (2000): "The SIP INFO Method".
[6]
RFC 3262 (2002): "Reliability of Provisional Responses in the Session Initiation Protocol (SIP)".
[7]
RFC 3515 (2003): "The Session Initiation Protocol (SIP) Refer Method".
[8]
RFC 3311 (2002): "The Session Initiation Protocol (SIP) UPDATE method".
[9]
RFC 6665 (2012): "Session Initiation Protocol (SIP) Specific Event Notification".
[10]
RFC 3428: "Session Initiation Protocol (SIP) Extension for Instant Messaging".
[11]
RFC 3903: "An Event State Publication Extension to the Session Initiation Protocol (SIP)".
[12]
TS 24.229: " Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ".
[13]
RFC 791 (1981): "DARPA Internet Program Protocol Specification".
[14]
RFC 2460 (1998): "Internet Protocol, Version 6 (IPv6) Specification".
[15] Void.
[16]
ETSI ES 282 001 (V2.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture".
[17]
TS 23.228: " IP Multimedia Subsystem (IMS); Stage 2".
[18]
RFC 3966 (2004): "The tel URI for Telephone Numbers".
[19]
RFC 3860 (2004): "Common Profile for Instant Messaging (CPIM)".
[20]
RFC 3859 (2004): "Common Profile for Presence (CPP)".
[21]
TS 29.162: "Interworking between IM CN Sub-system and IP networks".
[22]
ECMA TR/96 "NGCN-Identity: "Next Generation Corporate Networks (NGCN) - Identification and routing".
[23]
RFC 3841 (2004): "Caller Preferences for the Session Initiation Protocol (SIP)".
[24]
RFC 6442 (December 2011): "Location Conveyance for the Session Initiation Protocol".
[25]
RFC 7044 (2014): "An Extension to the Session Initiation Protocol (SIP) for Request History Information".
[26]
RFC 3911 (2004): "The Session Initiation Protocol (SIP) "Join" Header".
[27]
RFC 4028 (April 2005): "Session Timers in the Session Initiation Protocol (SIP)".
[28]
RFC 7315 (2014): "Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3rd-Generation Partnership Project (3GPP)".
[29]
RFC 3325 (2002): "Private Extensions to the Session Initiation Protocol (SIP) for Network Asserted Identity within Trusted Networks".
[30]
RFC 3323 (2002): "A Privacy Mechanism for the Session Initiation Protocol (SIP)".
[31]
RFC 3326 (2002): "The Reason Header Field for the Session Initiation Protocol (SIP)".
[32]
RFC 3329 (2003): "Security Mechanism Agreement for the Session Initiation Protocol (SIP)".
[33]
RFC 3892 (2004): "The Session Initiation Protocol (SIP) Referred-By Mechanism".
[34]
RFC 6050 (November 2010): "A Session Initiation Protocol (SIP) Extension for the Identification of Services".
[35]
RFC 5002 (2007): "The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header)".
[36]
RFC 4457 (2006): "The Session Initiation Protocol (SIP) P-User-Database Private-Header (P-header)".
[37]
RFC 3313 (2003): "Private Session Initiation Protocol (SIP) Extensions for Media Authorization".
[38]
RFC 5009 (2007): "Private Header (P-Header) Extension to the Session Initiation Protocol (SIP) for Authorization of Early Media".
[39]
RFC 3891 (2004): "The Session Initiation Protocol (SIP) "Replaces" Header".
[40]
RFC 4412 (2006): "Communications Resource Priority for the Session Initiation Protocol (SIP)".
[41]
ISO/IEC 9646-7 (1995): "Information technology -- Open Systems Interconnection -- Conformance testing methodology and framework -- Part 7: Implementation Conformance Statements".
[42]
ETSI ES 282 007: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia Subsystem (IMS); Functional architecture".
[43]
RFC 3856 (2004): "A Presence Event Package for the Session Initiation Protocol (SIP)".
[44]
RFC 4662 (2006): "A Session Initiation Protocol (SIP) Event Notification Extension for Resource Lists".
[45]
RFC 3680 (2004): "A Session Initiation Protocol (SIP) Event Package for Registrations".
[46]
RFC 5628 (October 2009): "Registration Event Package Extension for Session Initiation Protocol (SIP) Globally Routable User Agent URIs (GRUUs)".
[47]
RFC 3857 (2004): "A Watcher Information Event Template Package for the Session Initiation Protocol (SIP)".
[48]
RFC 5875 (May 2010): "An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Diff Event Package".
[49]
RFC 4575 (2006): "A Session Initiation Protocol (SIP) Event Package for Conference State".
[50]
RFC 3842 (2004) "A Message Summary and Message Waiting Indication Event Package for the Session Initiation Protocol (SIP)".
[51]
RFC 4354 (2006): "A Session Initiation Protocol (SIP) Event Package and Data Format for Various Settings in Support for the Push-to-Talk over Cellular (PoC) Service".
[52]
TS 33.203: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; 3G security; Access security for IP-based services ".
[53]
RFC 5393 (2008): "Addressing an Amplification Vulnerability in Session Initiation Protocol (SIP) Forking Proxies".
[54]
RFC 3312 (2002): "Integration of resource management and Session Initiation Protocol (SIP)".
[55]
RFC 4032 (2005): "Update to the Session Initiation Protocol (SIP) Preconditions Framework".
[56]
RFC 3327 (2002): "Session Initiation Protocol Extension Header Field for Registering Non-Adjacent Contacts".
[57]
RFC 3608 (2003): "Session Initiation Protocol (SIP) Extension Header Field for Service Route Discovery During Registration".
[58]
RFC 3581 (2003): "An Extension to the Session Initiation Protocol (SIP) for Symmetric Response Routing".
[59]
RFC 3840 (2004): "Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)".
[60]
RFC 5079 (December 2007): "Rejecting Anonymous Requests in the Session Initiation Protocol (SIP)".
[61]
RFC 4320 (2006): "Actions Addressing Identified Issues with the Session Initiation Protocol's (SIP) Non-INVITE Transaction".
[62]
RFC 5031 (2008): "A Uniform Resource Name (URN) for Emergency and Other Well-Known Services".
[63]
RFC 5627 (2009): "Obtaining and Using Globally Routable User Agent (UA) URIs (GRUU) in the Session Initiation Protocol (SIP)".
[64]
Void.
[65] RFC 5626 (2009): "Managing Client Initiated Connections in the Session Initiation Protocol (SIP)".
[66]
RFC 4964 (2007): "The P-Answer-State Header Extension to the Session Initiation Protocol for the Open Mobile Alliance Push to Talk over Cellular".
[67]
RFC 4733 (2006): "RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals".
[68]
RFC 3388 (2002): "Grouping of Media Lines in the Session Description Protocol (SDP)".
[69]
RFC 3524 (2003): "Mapping of Media Streams to Resource Reservation Flows".
[70]
RFC 3556 (2003): "Session Description Protocol (SDP) Bandwidth Modifiers for RTP Control Protocol (RTCP) Bandwidth".
[71]
RFC 4145 (2005): "TCP-Based Media Transport in the Session Description Protocol (SDP)".
[72]
RFC 5245 (2010): "Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols".
[73]
RFC 4583 (2006): "Session Description Protocol (SDP) Format for Binary Floor Control Protocol (BFCP) Streams".
[74]
RFC 4585 (2006): " Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/AVPF)".
[75]
RFC 5939 (2010): "Session Description Protocol (SDP) Capability Negotiation".
[76]
RFC 4566 (2006): "SDP: Session Description Protocol".
[77]
RFC 7316 (2014): "The Session Initiation Protocol (SIP) P-Private-Network-Indication Private-Header (P-Header)".
[78]
RFC 4119 (2005): "A Presence-based GEOPRIV Location Object Format".
[79]
ETSI TS 181 005 (V2.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Service and Capability Requirements".
[80]
TS 24.647: "Advice Of Charge (AOC) using IP Multimedia (IM) Core Network (CN) subsystem".
[81]
RFC 6086 (October 2009): "Session Initiation Protocol (SIP) INFO Method and Package Framework".
[82]
RFC 3324 (2002): "Short Term Requirements for Network Asserted Identity".
[83] Void.
[84] Void.
[85]
ETSI TR 180 000: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Terminology".
[86]
RFC 3263 (2002): "Session Initiation Protocol (SIP): Locating SIP Servers".
[87]
RFC 5621 (2009): "Message Body Handling in the Session Initiation Protocol (SIP)".
[88]
ECMA TR/100: "Next Generation Corporate Networks (NGCN) - Security of Session-based Communications".
[89]
ITU-T Recommendation G.711 (1988): "Pulse code modulation (PCM) of voice frequencies".
[90]
TS 24.173: "IMS Multimedia telephony service and supplementary services; Stage 3".
[91]
RFC 3264 (June 2002): "An Offer/Answer Model with Session Description Protocol (SDP)".
[92]
draft-dawes-sipping-debug-02 (February 2010) "Private Extension to the Session Initiation Protocol (SIP) for Debugging".
TR 23.812: "3rd Generation Partnership Project (3GPP), Feasibility Study on IMS Evolution".
[95]
TR-69: "CPE WAN Management Protocol v1.1".
[96]
TR-104: "DSLHomeTM Provisioning Parameters for VoIP CPE".
[97]
RFC 3551 (2003): "RTP Profile for Audio and Video Conferences with Minimal Control".
[98]
RFC 6228 (2011): "Response Code for Indication of Terminated Dialog".
3 Definitions and abbreviations p. 11
3.1 Definitions p. 11
For the purposes of the present document, the terms and definitions given in ETSI TR 180 000 [85], TS 22.519, TS 24.525 and the following apply:
NGCN Attachment Point:
SIP entity inside the NGCN with a direct SIP interface to the NGN
3.2 Abbreviations p. 11
