Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Content for  TS 24.229  Word version:  17.0.0

Top   Top   None   None   Next
1…   3…   4…   4.5…   5…   5.1.1.4…   5.1.2…   5.1.4…   5.2…   5.2.3…   5.2.6…   5.2.7…   5.3…   5.4…   5.4.1.2.2…   5.4.1.3…   5.4.2   5.4.3…   5.4.3.3…   5.4.4…   5.5…   5.7…   5.7.2…   5.8…   5.11…   6…   6.6…   7…   7.2A…   7.2A.6…   7.3…   7.9A…   8…   A…   B…   C…   E…   F…   H…   I…   K…   L…   L.2A…   M…   N…   O…   Q…   R…   S…   U…   U.2A…   V…   W…

 

1  Scope Word‑p. 40
The present document defines a call control protocol for use in the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP), and the associated Session Description Protocol (SDP).
The present document is applicable to:
  • the interface between the User Equipment (UE) and the Call Session Control Function (CSCF);
  • the interface between the CSCF and any other CSCF;
  • the interface between the CSCF and an Application Server (AS);
  • the interface between the CSCF and an ISC gateway function;
  • the interface between the ISC gateway function and an Application Server (AS);
  • the interface between the CSCF and the Media Gateway Control Function (MGCF);
  • the interface between the S-CSCF and the Multimedia Resource Function Controller (MRFC);
  • the interface between the Application Server (AS) and the Multimedia Resource Function Controller (MRFC);
  • the interface between the S-CSCF and the Media Resource Broker (MRB);
  • the interface between the AS and the MRB;
  • the interface between the MRB and the MRFC;
  • the interface between the CSCF and the Breakout Gateway Control Function (BGCF);
  • the interface between the BGCF and the MGCF;
  • the interface between the CSCF and an IBCF;
  • the interface between the IBCF and AS, MRFC or MRB;
  • the interface between the E-CSCF and the Location Retrieval Function (LRF);
  • the interface between the BGCF and any other BGCF;
  • the interface between the CSCF and an external Multimedia IP network;
  • the interface between the E-CSCF and the EATF;
  • the interface between the E-CSCF and the terminating IMS network;
  • the interface between the P-CSCF and the ATCF;
  • the interface between the ATCF and the I-CSCF;
  • the interface between the ATCF and the IBCF; and
  • the interface between the transit function and the AS.
Where possible the present document specifies the requirements for this protocol by reference to specifications produced by the IETF within the scope of SIP and SDP. Where this is not possible, extensions to SIP and SDP are defined within the present document. The document has therefore been structured in order to allow both forms of specification.
As the IM CN subsystem is designed to interwork with different IP-Connectivity Access Networks (IP-CANs), the IP-CAN independent aspects of the IM CN subsystem are described in the main body and Annex A of this specification. Aspects for connecting a UE to the IM CN subsystem through specific types of IP-CANs are documented separately in the annexes or in separate documents.
The document also specificies:
  • HTTP for use by an AS and by an MRB in support of the provision of media resources; and
  • HTTP for use by an IBCF and by an AS in support of the invocation of attestation and verification functions.
The document also specifies media-related requirements for the NAT traversal mechanisms defined in this specification.
Up

2  ReferencesWord‑p. 41
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]
TR 21.905: "Vocabulary for 3GPP Specifications".
[1A]
TS 22.101: "Service aspects; Service principles".
[1B]
TS 22.003: "Circuit Teleservices supported by a Public Land Mobile Network (PLMN)".
[1C]
TS 22.011: "Service accessibility".
[2]
TS 23.002: "Network architecture".
[3]
TS 23.003: "Numbering, addressing and identification".
[4]
TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".
[4A]
TS 23.107: "Quality of Service (QoS) concept and architecture".
[4B]
TS 23.167: "IP Multimedia Subsystem (IMS) emergency sessions".
[4C]
TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode".
[4D]
TS 23.140: Release 6: "Multimedia Messaging Service (MMS); Functional description; Stage 2".
[5]
TS 23.218: "IP Multimedia (IM) Session Handling; IM call model".
[6]
TS 23.221: "Architectural requirements".
[7]
TS 23.228: "IP multimedia subsystem; Stage 2".
[7A]
TS 23.234: "3GPP system to Wireless Local Area Network (WLAN) interworking; System description".
[7B]
TS 23.401: "GPRS enhancements for E-UTRAN access".
[7C]
TS 23.292: "IP Multimedia Subsystem (IMS) Centralized Services; Stage 2".
[7D]
TS 23.380: "IMS Restoration Procedures".
[7E]
TS 23.402: "Architecture enhancements for non-3GPP accesses".
[7F]
TS 23.334: "IMS Application Level Gateway (IMS-ALG) - IMS Access Gateway (IMS-AGW) interface".
[7G]
TS 24.103: "Telepresence using the IP Multimedia (IM) Core Network (CN) Subsystem (IMS); Stage 3".
[8]
TS 24.008: "Mobile radio interface layer 3 specification; Core Network protocols; Stage 3".
[8A]
TS 24.141: "Presence service using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3".
[8B]
TS 24.147: "Conferencing using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3".
[8C]
TS 24.234: "3GPP System to Wireless Local Area Network (WLAN) interworking; WLAN User Equipment (WLAN UE) to network protocols; Stage 3".
[8D]  Void.
[8E]
TS 24.279: "Combining Circuit Switched (CS) and IP Multimedia Subsystem (IMS) services, stage 3, Release 7".
[8F]
TS 24.247: "Messaging service using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3".
[8G]
TS 24.167: "3GPP IMS Management Object (MO); Stage 3".
[8H]
TS 24.173: "IMS Multimedia telephony communication service and supplementary services; Stage 3".
[8I]
TS 24.606: "Message Waiting Indication (MWI) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification".
[8J]
TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3".
[8K]
TS 24.323: "3GPP IMS service level tracing management object (MO)".
[8L]
TS 24.341: "Support of SMS over IP networks; Stage 3".
[8M]
TS 24.237: "IP Multimedia Subsystem (IMS) Service Continuity; Stage 3".
[8N]
TS 24.647: "Advice Of Charge (AOC) using IP Multimedia (IM) Core Network (CN) subsystem".
[8O]
TS 24.292: "IP Multimedia (IM) Core Network (CN) subsystem Centralized Services (ICS); Stage 3".
[8P]
TS 24.623: "Extensible Markup Language (XML) Configuration Access Protocol (XCAP) over the Ut interface for Manipulating Supplementary Services".
[8Q]
TS 24.182: "IP Multimedia Subsystem (IMS) Customized Alerting Tones (CAT); Protocol specification".
[8R]
TS 24.183: "IP Multimedia Subsystem (IMS) Customized Ringing Signal (CRS); Protocol specification".
[8S]
TS 24.616: "Malicious Communication Identification (MCID) using IP Multimedia (IM) Core Network (CN) subsystem".
[8T]
TS 24.305: "Selective Disabling of 3GPP User Equipment Capabilities (SDoUE) Management Object (MO)".
[8U]
TS 24.302: "Access to the Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3".
[8V]
TS 24.303: "Mobility management based on Dual-Stack Mobile IPv6".
[8W]
TS 24.390: "Unstructured Supplementary Service Data (USSD) using IP Multimedia (IM) Core Network (CN) subsystem IMS".
[8X]
TS 24.139: "3GPP System-Fixed Broadband Access Network Interworking; Stage 3".
[8Y]
TS 24.322: "UE access to IMS services via restrictive access networks - stage 3".
[8Z]
TS 24.371: "Web Real Time Communication (WebRTC) Access to IMS".
[8ZA]
TS 24.525: "Business trunking; Architecture and functional description".
[8ZB]
TS 24.244: "Wireless LAN control plane protocol for trusted WLAN access to EPC; Stage 3".
[8ZC]
TS 24.337: "IP Multimedia (IM) Core Network (CN) subsystem IP Multimedia Subsystem (IMS) inter-UE transfer; Stage 3".
[8ZD]
TS 24.334: "Proximity-services (ProSe) User Equipment (UE) to Proximity-services (ProSe) Function Protocol aspects; Stage 3".
[8ZE]
TS 24.379: "Mission Critical Push To Talk (MCPTT) call control; Stage 3".
[8ZF]
TS 24.628: "Common Basic Communication procedures using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification".
[8ZG]
TS 24.604: "Communication Diversion (CDIV) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification".
[9]
TS 25.304: "User Equipment (UE) procedures in idle mode and procedures for cell reselection in connected mode".
[9A]
TS 25.331: "Radio Resource Control (RRC); Protocol Specification".
[9B]
TS 26.114: "IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction".
[9C]
TS 26.267: "eCall Data Transfer; In-band modem solution; General description".
[10]  Void.
[10A]
TS 27.060: "Mobile Station (MS) supporting Packet Switched Services".
[11]
TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting Packet Based Services and Packet Data Networks (PDN)".
[11A]
TS 29.162: "Interworking between the IM CN subsystem and IP networks".
[11B]
TS 29.163: "Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks".
[11C]
TS 29.161: "Interworking between the Public Land Mobile Network (PLMN) supporting Packet Based Services with Wireless Local Access and Packet Data Networks (PDN)"
[11D]
TS 29.079: "Optimal Media Routeing within the IP Multimedia Subsystem".
[12]
TS 29.207: Release 6: "Policy control over Go interface".
[12A]
TS 29.273: "Evolved Packet System (EPS); 3GPP EPS AAA interfaces".
[13]  Void.
[13A]
TS 29.209: Release 6: "Policy control over Gq interface".
[13B]
TS 29.212: "Policy and Charging Control (PCC); Reference points".
[13C]
TS 29.213: "Policy and charging control signalling flows and Quality of Service (QoS) parameter mapping".
[13D]
TS 29.214: "Policy and Charging Control over Rx reference point".
[14]
TS 29.228: "IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and message contents".
[15]
TS 29.229: "Cx and Dx Interfaces based on the Diameter protocol, Protocol details".
[15A]
TS 29.311: "Service Level Interworking for Messaging Services".
[15B]
TS 31.103: "Characteristics of the IP multimedia services identity module (ISIM) application".
[15C]
TS 31.102: "Characteristics of the Universal Subscriber Identity Module (USIM) application".
[15D]
TS 31.111: "Universal Subscriber Identity Module (USIM) Application Toolkit (USAT)".
[16]
TS 32.240: "Telecommunication management; Charging management; Charging architecture and principles".
[17]
TS 32.260: "Telecommunication management; Charging management; IP Multimedia Subsystem (IMS) charging".
[17A]
TS 32.422: "Telecommunication management; Subscriber and equipment trace; Trace control and configuration management".
[18]
TS 33.102: "3G Security; Security architecture".
[19]
TS 33.203: "Access security for IP based services".
[19A]
TS 33.210: "3G security; Network Domain Security (NDS); IP network layer security".
[19B]
TS 36.304: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode".
[19C]
TS 33.328: "IP Multimedia Subsystem (IMS) media plane security".
[19D]
TS 33.310: "Network Domain Security (NDS); Authentication Framework (AF)".
[19E]
TS 36.413: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP)".
[19F]
TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification".
[19G]
TS 38.331: " NR; Radio Resource Control (RRC); Protocol specification".
[20]
TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol".
[20A]
RFC 2401  (November 1998): "Security Architecture for the Internet Protocol".
[20B]
RFC 1594  (March 1994): "FYI on Questions and Answers to Commonly asked "New Internet User" Questions".
[20C]  Void.
[20D]  Void.
[20E]
RFC 2462  (November 1998): "IPv6 Stateless Address Autoconfiguration".
[20F]
RFC 2132  (March 1997): "DHCP Options and BOOTP Vendor Extensions".
[20G]
RFC 2234  (November 1997): "Augmented BNF for Syntax Specification: ABNF".
[21]
RFC 2617  (June 1999): "HTTP Authentication: Basic and Digest Access Authentication".
[22]
RFC 3966  (December 2004): "The tel URI for Telephone Numbers".
[23]
RFC 4733  (December 2006): "RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals".
[24]
RFC 6116  (March 2011): "The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)".
[25]
RFC 6086  (October 2009): "Session Initiation Protocol (SIP) INFO Method and Package Framework".
[25A]
RFC 3041  (January 2001): "Privacy Extensions for Stateless Address Autoconfiguration in IPv6".
[26]
RFC 3261  (June 2002): "SIP: Session Initiation Protocol".
[27]
RFC 3262  (June 2002): "Reliability of provisional responses in Session Initiation Protocol (SIP)".
[27A]
RFC 3263  (June 2002): "Session Initiation Protocol (SIP): Locating SIP Servers".
[27B]
RFC 3264  (June 2002): "An Offer/Answer Model with Session Description Protocol (SDP)".
[28]
RFC 6665  (July 2012): "SIP Specific Event Notification".
[28A]  Void.
[29]
RFC 3311  (September 2002): "The Session Initiation Protocol (SIP) UPDATE method".
[30]
RFC 3312  (October 2002): "Integration of resource management and Session Initiation Protocol (SIP)".
[31]
RFC 3313  (January 2003): "Private Session Initiation Protocol (SIP) Extensions for Media Authorization".
[32]
RFC 3320  (March 2002): "Signaling Compression (SigComp)".
[33]
RFC 3323  (November 2002): "A Privacy Mechanism for the Session Initiation Protocol (SIP)".
[34]
RFC 3325  (November 2002): "Private Extensions to the Session Initiation Protocol (SIP) for Network Asserted Identity within Trusted Networks".
[34A]
RFC 3326  (December 2002): "The Reason Header Field for the Session Initiation Protocol (SIP)".
[35]
RFC 3327  (December 2002): "Session Initiation Protocol Extension Header Field for Registering Non-Adjacent Contacts".
[35A]
RFC 3361  (August 2002): "Dynamic Host Configuration Protocol (DHCP-for-IPv4) Option for Session Initiation Protocol (SIP) Servers".
[36]
RFC 3515  (April 2003): "The Session Initiation Protocol (SIP) REFER method".
[37]
RFC 3420  (November 2002): "Internet Media Type message/sipfrag".
[37A]
RFC 3605  (October 2003): "Real Time Control Protocol (RTCP) attribute in Session Description Protocol (SDP)".
[38]
RFC 3608  (October 2003): "Session Initiation Protocol (SIP) Extension Header Field for Service Route Discovery During Registration".
[39]
RFC 4566  (June 2006): "SDP: Session Description Protocol".
[40]
RFC 3315  (July 2003): "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)".
[40A]
RFC 2131  (March 1997): "Dynamic host configuration protocol".
[41]
RFC 3319  (July 2003): "Dynamic Host Configuration Protocol (DHCPv6) Options for Session Initiation Protocol (SIP) Servers".
[42]
RFC 3485  (February 2003): "The Session Initiation Protocol (SIP) and Session Description Protocol (SDP) static dictionary for Signaling Compression (SigComp)".
[43]
RFC 3680  (March 2004): "A Session Initiation Protocol (SIP) Event Package for Registrations".
[44]  Void.
[45]  Void.
[46]  Void.
[47]  Void.
[48]
RFC 3329  (January 2003): "Security Mechanism Agreement for the Session Initiation Protocol (SIP)".
[49]
RFC 3310  (September 2002): "Hypertext Transfer Protocol (HTTP) Digest Authentication Using Authentication and Key Agreement (AKA)".
[50]
RFC 3428  (December 2002): "Session Initiation Protocol (SIP) Extension for Instant Messaging".
[51]  Void.
[52]
RFC 7315  (July 2014): "Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3GPP".
[52A]
RFC 7976  (September 2016): "Updates to Private Header (P-Header) Extension Usage in Session Initiation Protocol (SIP) Requests and Responses".
[52B]
draft-jesske-update-p-visited-network-01 (March 2019): "Update to Private Header Field P-Visited-Network-ID in Session Initiation Protocol (SIP) Requests and Responses".
[53]
RFC 3388  (December 2002): "Grouping of Media Lines in Session Description Protocol".
[54]
RFC 3524  (April 2003): "Mapping of Media Streams to Resource Reservation Flows".
[55]
RFC 3486  (February 2003): "Compressing the Session Initiation Protocol (SIP)".
[55A]
RFC 3551  (July 2003): "RTP Profile for Audio and Video Conferences with Minimal Control".
[56]
RFC 3556  (July 2003): "Session Description Protocol (SDP) Bandwidth Modifiers for RTP Control Protocol (RTCP) Bandwidth".
[56A]
RFC 3581  (August 2003): "An Extension to the Session Initiation Protocol (SIP) for Symmetric Response Routing".
[56B]
RFC 3841  (August 2004): "Caller Preferences for the Session Initiation Protocol (SIP)".
[56C]
RFC 3646  (December 2003): "DNS Configuration options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)".
[57]
ITU-T Recommendation E.164: "The international public telecommunication numbering plan".
[58]
RFC 4028  (April 2005): "Session Timers in the Session Initiation Protocol (SIP)".
[59]
RFC 3892  (September 2004): "The Session Initiation Protocol (SIP) Referred-By Mechanism".
[60]
RFC 3891  (September 2004): "The Session Inititation Protocol (SIP) "Replaces" Header".
[61]
RFC 3911  (October 2004): "The Session Inititation Protocol (SIP) "Join" Header".
[62]
RFC 3840  (August 2004): "Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)".
[63]
RFC 3861  (August 2004): "Address Resolution for Instant Messaging and Presence".
[63A]
RFC 3948  (January 2005): "UDP Encapsulation of IPsec ESP Packets".
[64]
RFC 4032  (March 2005): "Update to the Session Initiation Protocol (SIP) Preconditions Framework".
[65]
RFC 3842  (August 2004) "A Message Summary and Message Waiting Indication Event Package for the Session Initiation Protocol (SIP)"
[65A]
RFC 4077  (May 2005): "A Negative Acknowledgement Mechanism for Signaling Compression".
[66]
RFC 7044  (February 2014): "An Extension to the Session Initiation Protocol (SIP) for Request History Information".
[67]
RFC 5079  (December 2007): "Rejecting Anonymous Requests in the Session Initiation Protocol (SIP)".
[68]
RFC 4458  (January 2006): "Session Initiation Protocol (SIP) URIs for Applications such as Voicemail and Interactive Voice Response (IVR)".
[69]
RFC 5031  (January 2008): "A Uniform Resource Name (URN) for Emergency and Other Well-Known Services".
[70]
RFC 3903  (October 2004): "An Event State Publication Extension to the Session Initiation Protocol (SIP)".
[71]  Void.
[72]
RFC 3857  (August 2004): "A Watcher Information Event Template Package for the Session Initiation Protocol (SIP)".
[74]
RFC 3856  (August 2004): "A Presence Event Package for the Session Initiation Protocol (SIP)".
[74A]
RFC 3603  (October 2003): "Private Session Initiation Protocol (SIP) Proxy-to-Proxy Extensions for Supporting the PacketCable Distributed Call Signaling Architecture".
[74B]
RFC 3959  (December 2004): "The Early Session Disposition Type for the Session Initiation Protocol (SIP)".
[75]
RFC 4662  (August 2006): "A Session Initiation Protocol (SIP) Event Notification Extension for Resource Lists".
[77]
RFC 5875  (May 2010): "An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Diff Event Package".
[78]
RFC 4575  (August 2006): "A Session Initiation Protocol (SIP) Event Package for Conference State".
[79]
RFC 5049  (December 2007): "Applying Signaling Compression (SigComp) to the Session Initiation Protocol (SIP)".
[80]  Void.
[81]  Void.
[82]
RFC 4457  (April 2006): "The Session Initiation Protocol (SIP) P-User-Database Private-Header (P-header)".
[83]
RFC 4145  (September 2005): "TCP-Based Media Transport in the Session Description Protocol (SDP)".
[84]
RFC 4320  (January 2006): "Actions Addressing Identified Issues with the Session Initiation Protocol's (SIP) Non-INVITE Transaction".
[85]
3GPP2 C.S0005-D (March 2004): "Upper Layer (Layer 3) Signaling Standard for cdma2000 Standards for Spread Spectrum Systems".
[86]
3GPP2 C.S0024-B v3.0 (September 2009): "cdma2000 High Rate Packet Data Air Interface Standard".
[86A]
3GPP2 C.S0084-000 (April 2007): "Overview for Ultra Mobile Broadband (UMB) Air Interface Specification".
[86B]
3GPP2 X.S0060-0 v1.0: "HRPD Support for Emergency Services".
[86C]
3GPP2 X.S0057-B v2.0: "E-UTRAN - eHRPD Connectivity and Interworking: Core Network Aspects".
[86D]
3GPP2 C.S0014-C v1.0: "Enhanced Variable Rate Codec, Speech Service Options 3, 68, and 70 for Wideband Spread Spectrum Digital Systems".
[86E]
3GPP2 X.S0059-200-A v1.0: "cdma2000 Femtocell Network: 1x and IMS Network Aspects".
[86F]
3GPP2 S.R0048-A v4.0: "3G Mobile Equipment Identifier (MEID) - Stage 1".
[87]
ITU-T Recommendation J.112: "Transmission Systems for Interactive Cable Television Services"
[88]
PacketCable Release 2 Technical Report: PacketCable™ Architecture Framework Technical Report, PKT-TR-ARCH-FRM.
[89]
RFC 6442  (December 2011): "Location Conveyance for the Session Initiation Protocol".
[90]
RFC 4119  (December 2005) "A Presence-based GEOPRIV Location Object Format".
[91]
RFC 5012  (January 2008): "Requirements for Emergency Context Resolution with Internet Technologies".
[91A]  Void.
[92]
RFC 5626  (October 2009): "Managing Client Initiated Connections in the Session Initiation Protocol (SIP)".
[93]
RFC 5627  (October 2009): "Obtaining and Using Globally Routable User Agent URIs (GRUUs) in the Session Initiation Protocol (SIP)".
[94]
RFC 5628  (October 2009): "Registration Event Package Extension for Session Initiation Protocol (SIP) Globally Routable User Agent URIs (GRUUs)".
[95]  Void.
[96]
RFC 4168  (October 2005): "The Stream Control Transmission Protocol (SCTP) as a Transport for the Session Initiation Protocol (SIP)".
[97]
RFC 5002  (August 2007): "The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header)".
[98]
ETSI ES 283 035 (V1.1.1): "Telecommunications and Internet Converged Services and Protocols for Advanced Networks (TISPAN); Network Attachment Sub-System (NASS); e2 interface based on the DIAMETER protocol".
[99]
RFC 5245  (April 2010): "Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols".
[100]
RFC 5389  (October 2008): "Session Traversal Utilities for NAT (STUN)".
[101]
RFC 5766  (April 2010): "Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)".
[102]
RFC 5768  (April 2010): "Indicating Support for Interactive Connectivity Establishment (ICE) in the Session Initiation Protocol (SIP)".
[103]
RFC 4967  (July 2007): "Dial String Parameter for the Session Initiation Protocol Uniform Resource Identifier".
[104]
RFC 5365  (October 2008): "Multiple-Recipient MESSAGE Requests in the Session Initiation Protocol (SIP)".
[105]
RFC 5368  (October 2008): "Referring to Multiple Resources in the Session Initiation Protocol (SIP)".
[106]
RFC 5366  (October 2008): "Conference Establishment Using Request-Contained Lists in the Session Initiation Protocol (SIP)".
[107]
RFC 5367  (October 2008): "Subscriptions to Request-Contained Resource Lists in the Session Initiation Protocol (SIP)".
[108]
RFC 4583  (November 2006): "Session Description Protocol (SDP) Format for Binary Floor Control Protocol (BFCP) Streams".
[109]
RFC 5009  (September 2007): "Private Header (P-Header) Extension to the Session Initiation Protocol (SIP) for Authorization of Early Media".
[110]
RFC 4354  (January 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".
[111]
RFC 4964  (September 2007): "The P-Answer-State Header Extension to the Session Initiation Protocol for the Open Mobile Alliance Push to Talk over Cellular".
[112]
RFC 4694  (October 2006): "Number Portability Parameters for the 'tel' URI".
[113]  Void.
[114]
RFC 4769  (November 2006): "IANA Registration for an Enumservice Containing Public Switched Telephone Network (PSTN) Signaling Information".
[115]
RFC 4411  (February 2006): "Extending the Session Initiation Protocol (SIP) Reason Header for Preemption Events".
[116]
RFC 4412  (February 2006): "Communications Resource Priority for the Session Initiation Protocol (SIP)".
[117]
RFC 5393  (December 2008): "Addressing an Amplification Vulnerability in Session Initiation Protocol (SIP) Forking Proxies".
[118]
RFC 4896  (June 2007): "Signaling Compression (SigComp) Corrections and ClarificationsImplementer's Guide for SigComp".
[119]
RFC 5112  (January 2008): "The Presence-Specific Static Dictionary for Signaling Compression (Sigcomp)".
[120]
RFC 5688  (January 2010): "A Session Initiation Protocol (SIP) Media Feature Tag for MIME Application Subtype".
[121]
RFC 6050  (November 2010): "A Session Initiation Protocol (SIP) Extension for the Identification of Services".
[122]  Void.
[123]  Void.
[124]
RFC 3986  (January 2005): "Uniform Resource Identifiers (URI): Generic Syntax".
[125]
RFC 5360  (October 2008): "A Framework for Consent-Based Communications in the Session Initiation Protocol (SIP)".
[126]
RFC 7433  (January 2015): "A Mechanism for Transporting User-to-User Call Control Information in SIP".
[126A]
RFC 7434  (January 2015): "Interworking ISDN Call Control User Information with SIP".
[127]
3GPP2 X.S0011-E: "cdma2000 Wireless IP Network Standard ".
[130]
RFC 6432  (November 2011): "Carrying Q.850 Codes in Reason Header Fields in SIP (Session Initiation Protocol) Responses".
[131]
RFC 6544  (March 2012): "TCP Candidates with Interactive Connectivity Establishment (ICE)".
[132]
RFC 3023  (January 2001): "XML Media Types".
[133]
RFC 5502  (April 2009): "The SIP P-Served-User Private-Header (P-Header) for the 3GPP IP Multimedia (IM) Core Network (CN) Subsystem".
[134]
RFC 7316  (July 2014): "The Session Initiation Protocol (SIP) P-Private-Network-Indication PrivateHeader (P-Header)".
[135]
RFC 4585  (July 2006): "Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/AVPF)".
[136]
RFC 5104  (February 2008): "Codec Control Messages in the RTP Audio-Visual Profile with Feedback (AVPF)".
[137]
RFC 5939  (September 2010): "Session Description Protocol (SDP) Capability Negotiation".
[138]
ETSI ES 282 001: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture Release 1".
[139]  Void.
[140]
RFC 8497  (November 2018): "Marking SIP Messages to Be Logged".
[141]  Void.
[142]
RFC 6228  (May 2011): "Response Code for Indication of Terminated Dialog".
[143]
RFC 6223  (April 2011): "Indication of support for keep-alive".
[144]
RFC 4240  (December 2005): "Basic Network Media Services with SIP".
[145]
RFC 5552  (May 2009): "SIP Interface to VoiceXML Media Services".
[146]
RFC 6230  (May 2011): "Media Control Channel Framework".
[147]
RFC 6231  (May 2011): "An Interactive Voice Response (IVR) Control Package for the Media Control Channel Framework".
[148]
RFC 6505  (March 2012): "A Mixer Control Package for the Media Control Channel Framework".
[149]
RFC 2046  (November 1996): "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types".
[150]
RFC 5621  (September 2009): "Message Body Handling in the Session Initiation Protocol (SIP)".
[151]
RFC 3862  (August 2004): "Common Presence and Instant Messaging (CPIM): Message Format".
[152]
RFC 3890  (September 2004): "A Transport Independent Bandwidth Modifier for the Session Description Protocol (SDP)".
[153]
RFC 7254  (May 2014): "A Uniform Resource Name Namespace for the Global System for Mobile Communications Association (GSMA) and the International Mobile station Equipment Identity (IMEI)".
[154]
RFC 4122  (July 2005): "A Universally Unique IDentifier (UUID) URN Namespace".
[155]
RFC 7195  (May 2014): "Session Description Protocol (SDP) Extension for Setting Audio Media Streams over Circuit-Switched Bearers in the Public Switched Telephone Network (PSTN)".
[156]
RFC 7006  (September 2013): "Miscellaneous Capabilities Negotiation in the Session Description Protocol (SDP)".
[157]
RFC 5438  (January 2009): "Instant Message Disposition Notification (IMDN)".
[158]
RFC 5373  (November 2008): "Requesting Answering Modes for the Session Initiation Protocol (SIP)".
[160]  Void.
[161]
RFC 4288  (December 2005): "Media Type Specifications and Registration Procedures".
[162]
RFC 7989  (October 2016): "End-to-End Session Identification in IP-Based Multimedia Communication Networks".
[163]
RFC 6026  (September 2010): "Correct Transaction Handling for 2xx Responses to Session Initiation Protocol (SIP) INVITE Requests".
[164]
RFC 5658  (October 2009): "Addressing Record-Route issues in the Session Initiation Protocol (SIP)".
[165]
RFC 5954  (August 2010): "Essential Correction for IPv6 ABNF and URI Comparison in RFC3261".
[166]
RFC 4117  (June 2005): "Transcoding Services Invocation in the Session Initiation Protocol (SIP) using Third Party Call Control (3pcc)".
[167]
RFC 4567  (July 2006): "Key Management Extensions for Session Description Protocol (SDP) and Real Time Streaming Protocol (RTSP)".
[168]
RFC 4568  (July 2006): "Session Description Protocol (SDP) Security Descriptions for Media Streams".
[169]
RFC 3711  (March 2004): "The Secure Real-time Transport Protocol (SRTP)".
[170]
RFC 6043  (March 2011): "MIKEY-TICKET: Ticket-Based Modes of Key Distribution in Multimedia Internet KEYing (MIKEY)".
[171]
RFC 4235  (November 2005): "An INVITE-Initiated Dialog Event Package for the Session Initiation Protocol (SIP)".
[172]
RFC 6871  (February 2013): "SDP media capabilities Negotiation".
[173]
RFC 4488  (May 2006): "Suppression of Session Initiation Protocol (SIP) REFER Method Implicit Subscription".
[174]  Void.
[175]
RFC 7462  (March 2015): "URNs for the Alert-Info Header Field of the Session Initiation Protocol (SIP)".
[176]
ANSI/J-STD-036-B: "Enhanced Wireless 9-1-1, Phase 2".
[177]  Void.
[178]
RFC 4975  (September 2007): "The Message Session Relay Protocol (MSRP)".
[179]
RFC 3859  (August 2004): "Common Profile for Presence (CPP)".
[180]
RFC 3860  (August 2004): "Common Profile for Instant Messaging (CPIM)".
[181]
RFC 2368  (July 1998): "The mailto URL scheme".
[182]
RFC 4745  (February 2007): "Common Policy: A Document Format for Expressing Privacy Preferences".
[183]
RFC 5318  (December 2008): "The Session Initiation Protocol (SIP) P-Refused-URI-List Private-Header (P-Header)".
[184]
RFC 4538  (June 2006): "Request Authorization through Dialog Identification in the Session Initiation Protocol (SIP)".
[185]
RFC 5547  (May 2009): "A Session Description Protocol (SDP) Offer/Answer Mechanism to Enable File Transfer".
[186]
RFC 4483  (May 2006): "A Mechanism for Content Indirection in Session Initiation Protocol (SIP) Messages".
[187]
RFC 8464  (September 2018): "A URN Namespace for Device Identity and Mobile Equipment Identity (MEID)".
[188]
RFC 6679  (August 2012): "Explicit Congestion Notification (ECN) for RTP over UDP".
[189]
RFC 3168  (September 2001): "The Addition of Explicit Congestion Notification (ECN) to IP".
[190]
RFC 6809  (November 2012): "Mechanism to Indicate Support of Features and Capabilities in the Session Initiation Protocol (SIP)".
[191]
RFC 6140  (March 2011): "Registration for Multiple Phone Numbers in the Session Initiation Protocol (SIP)".
[192]
RFC 6917  (April 2013): "Media Resource Brokering".
[193]
ETSI TS 101 454-1 v1.1.1: "Digital Video Broadcasting (DVB); Second Generation DVB Interactive Satellite System (DVB-RCS2); Part 1: Overview and System Level specification".
[194]
ETSI EN 301 545-2 v1.1.1: "Digital Video Broadcasting (DVB); Second Generation DVB Interactive Satellite System (DVB-RCS2); Part 2: Lower Layers for Satellite standard".
[195]
ETSI TS 101 545-3 v1.1.1: "Digital Video Broadcasting (DVB); Second Generation DVB Interactive Satellite System (DVB-RCS2); Part 3: Higher Layers Satellite Specification".
[196]
RFC 2616  (June 1999): "Hypertext Transfer Protocol -- HTTP/1.1".
[197]
RFC 7135  (May 2014): "IANA Registering a SIP Resource Priority Header Field Namespace for Local Emergency Communications".
[198]
RFC 6357  (August 2011): "Design Considerations for Session Initiation Protocol (SIP) Overload Control".
[199]
RFC 7339  (September 2014): "Session Initiation Protocol (SIP) Overload Control".
[200]
RFC 7415  (February 2015): "Session Initiation Protocol (SIP) Rate Control".
[201]
RFC 7200  (April 2014): "A Session Initiation Protocol (SIP) Load-Control Event Package".
[202]
ITU-T Recommendation T.38 (September 2010): "Procedures for real-time Group 3 facsimile communication over IP networks".
[203]
ISO 8601 (December 2004): "Date elements and interchange formats - Information interchange - Representation of dates and times".
[204]
RFC 5506  (April 2009): "Support for Reduced-Size Real-Time Transport Control Protocol (RTCP)".
[205]
RFC 3611  (November 2003): "RTP Control Protocol Extended Reports (RTCP XR)".
[206]
RFC 4796  (February 2007): "The Session Description Protocol (SDP) Content Attribute".
[207]
ISO 3166-1 (2006): "Codes for the representation of names of countries and their subdivisions - Part 1: Country codes".
[208]
RFC 8055  (January 2017): "Session Initiation Protocol (SIP) Via Header Field Parameter to Indicate Received Realm".
[209]
RFC 7090  (April 2014): "Public Safety Answering Point (PSAP) Callback".
[210]
RFC 5285  (July 2008): "A General Mechanism for RTP Header Extensions".
[211]
RFC 6236  (May 2011): "Negotiation of Generic Image Attributes in the Session Description Protocol (SDP)".
[212]
RFC 20  (May 2011): "ASCII format for Network Interchange".
[213]
RFC 5280  (May 2008): "Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile".
[214]
RFC 6714  (August 2012): "Connection Establishment for Media Anchoring (CEMA) for the Message Session Relay Protocol (MSRP)".
[215]
RFC 6135  (February 2011): "An Alternative Connection Model for the Message Session Relay Protocol (MSRP)".
[216]  Void.
[217]
RFC 7345  (August 2014): "UDP Transport Layer (UDPTL) over Datagram Transport Layer Security (DTLS)".
[218]
RFC 4279  (December 2005): "Pre-Shared Key Ciphersuites for Transport Layer Security (TLS)".
[219]
draft-ietf-mmusic-sctp-sdp-26 (April 2017): "Session Description Protocol (SDP) Offer/Answer Procedures For Stream Control Transmission Protocol (SCTP) over Datagram Transport Layer Security (DTLS) Transport".
[220]
RFC 2817  (May 2000): "Upgrading to TLS Within HTTP/1.1".
[221]
RFC 6062  (November 2010): "Using Relays around NAT (TURN) Extensions for TCP Allocations".
[222]
RFC 5763  (May 2010): "Framework for Establishing a Secure Real-time Transport Protocol (SRTP) Security Context Using Datagram Transport Layer Security (DTLS)".
[223]
RFC 5764  (May 2010): " Datagram Transport Layer Security (DTLS) Extension to Establish Keys for the Secure Real-time Transport Protocol (SRTP)".
[224]
RFC 7675  (October 2015): "STUN Usage for Consent Freshness".
[225]
RFC 7549  (May 2015): "3GPP SIP URI Inter Operator Traffic Leg Parameter".
[226]  Void.
[227]
RFC 4169  (November 2005): "Hypertext Transfer Protocol (HTTP) Digest Authentication Using Authentication and Key Agreement (AKA) Version-2".
[228]
RFC 6947  (May 2013): "The Session Description Protocol (SDP) Alternate Connectivity (ALTC) Attribute".
[229]  Void.
[230]
RFC 8119  (March 2017): "SIP "cause" URI Parameter for Service Number Translation".
[231]
RFC 7647  (September 2015): "Clarifications for the Use of REFER with RFC6665".
[232]
RFC 7614  (August 2015): "Explicit Subscriptions for the REFER Method".
[233]
RFC 7621  (August 2015): "A Clarification on the Use of Globally Routable User Agent URIs (GRUUs) in the Session Initiation Protocol (SIP) Event Notification Framework".
[234]
RFC 7913  (June 2016): "P-Access-Network-Info ABNF Update".
[235]
RFC 7519  (May 2015): "JSON Web Token (JWT)".
[236]
Void.
[237]
RFC 5761  (April 2010): "Multiplexing RTP Data and Control Packets on a Single Port".
[237A]
RFC 8035  (November 2016): "Session Description Protocol (SDP) Offer/Answer Clarifications for RTP/RTCP Multiplexing".
[238]
draft-ietf-mmusic-data-channel-sdpneg-11 (January 2017): "SDP-based Data Channel Negotiation".
[239]
RFC 8498  (February 2019): "A P-Served-User Header Field Parameter for an Originating Call Diversion (CDIV) Session Case in the Session Initiation Protocol (SIP)".
[240]
draft-ietf-mmusic-dtls-sdp-32 (October 2017): "Session Description Protocol (SDP) Offer/Answer Considerations for Datagram Transport Layer Security (DTLS) and Transport Layer Security (TLS)".
[241]
RFC 8122  (March 2017): "Connection-Oriented Media Transport over the Transport Layer Security (TLS) Protocol in the Session Description Protocol (SDP)".[242] RFC 3863 (August 2004): "Presence Information Data Format".
[243]
RFC 4661  (September 2006): "An Extensible Markup Language (XML) Based Format for Event Notification Filtering".
[244]
RFC 8147  (May 2017): "Next-Generation Pan-European eCall".
[245]
CEN EN 15722:2015 (April 2015): "Intelligent transport systems - ESafety - ECall minimum set of data".
[246]
draft-ietf-mmusic-mux-exclusive-12 (May 2017): "Indicating Exclusive Support of RTP/RTCP Multiplexing using SDP".
[247]
RFC 7303  (July 2014): "XML Media Types".
[248]
IEEE Std 802.11-2016: "IEEE Standard for Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications".
[249]
draft-ietf-mmusic-sdp-simulcast-08 (March 2017): "Using Simulcast in SDP and RTP Sessions".
[250]
draft-ietf-mmusic-rid-10 (March 2017): "RTP Payload Format Restrictions".
[251]
RFC 7728  (February 2016): "RTP Stream Pause and Resume".
[252]
RFC 8224  (February 2018): "Authenticated Identity Management in the Session Initiation Protocol (SIP)".
[253]
RFC 5279  (July 2008): "A Uniform Resource Name (URN) Namespace for the 3rd Generation Partnership Project (3GPP)".
[254]
RFC 8197  (July 2017): "A SIP Response Code for Unwanted Calls".
[255]
RFC 8606  (June 2019): "ISDN User Part (ISUP) Cause Location Parameter for the SIP Reason Header Field".
[256]
RFC 8262  (October 2017): "Content-ID Header Field in the Session Initiation Protocol (SIP)".
[257]
TS 23.501: "System Architecture for the 5G System; Stage 2".
[258]
TS 24.501: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (5GS); Stage 3".
[259]
RFC 4715  (November 2006): "The Integrated Services Digital Network (ISDN) Subaddress Encoding Type for tel URI".
[260]
TS 38.304: " NR; User Equipment (UE) procedures in idle mode and in RRC Inactive state".
[261]
RFC 8588  (May 2019): "Personal Assertion Token (PaSSporT) Extension for Signature-based Handling of Asserted information using toKENs (SHAKEN)".
[262]
RFC 8225  (February 2018): "PASSporT: Personal Assertion Token"
[263]
TS 24.502: " Access to the 3GPP 5G Core Network (5GCN) via Non-3GPP Access Networks (N3AN); Stage 3".
[264]
TS 37.340: "Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Stage 2".
[265]
IETF draft-ietf-stir-passport-divert-08 (March 2020): "PASSporT Extension for Diverted Calls".
[266]
RFC 8787  (May 2020): "Location Source Parameter for the SIP Geolocation Header Field".
[267]
RFC 5491  (March 2009): "GEOPRIV Presence Information Data Format Location Object (PIDF-LO) Usage Clarification, Considerations, and Recommendations".
[268]
TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2".
[269]
TS 36.321: "Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification".
[270]
TS 38.300: "NR; NR and NG-RAN Overall Description; Stage 2".
[271]
TS 38.321: "NR; Medium Access Control (MAC) protocol specification".
[272]
TS 23.221: "Architectural requirements".
[273]
TS 29.514: "5G System; Policy Authorization Service; Stage 3".
[274]
TS 29.562: "Home Subscriber Server (HSS) Services for Interworking with the IP Multimedia Subsystem (IMS); Stage 3".
[275]
TS 23.502: "Procedures for the 5G System; Stage 2".
[276]
TS 26.238: "Uplink Streaming".
[277]
RFC 4574  (August 2006): "The Session Description Protocol (SDP) Label Attribute".
Up

Up   Top   ToC