Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Protocol

SIP

Session Initiation Protocol

Protocol →

SIP is the IETF-defined application-layer signaling protocol used to create, modify, and terminate multimedia sessions, and it is the core protocol for IMS services in 3GPP networks.

Introduced
Rel-5
Where
Services › IMS
Specifications
139 specs
Also in
Core Network
SIP Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The Session Initiation Protocol (SIP) is a text-based, application-layer control protocol standardized by the IETF (RFC 3261 and others). Its primary function is to establish, manage, and tear down interactive communication sessions between participants. These sessions can include voice, video, instant messaging, online games, and virtual reality—essentially any real-time data exchange. SIP operates on a client-server model but is inherently peer-to-peer in its session management. It is independent of the underlying transport layer, commonly running over UDP, TCP, or TLS.

SIP works through the exchange of request and response messages between User Agents (UAs), which can be clients (UAC) initiating requests or servers (UAS) responding to them. A typical SIP transaction for establishing a voice call involves several key messages: the caller's UA sends an INVITE request to the callee's address (a SIP URI). This request is routed through SIP proxy servers, which help locate the callee and enforce routing policies. The callee's UA responds with provisional responses (e.g., 180 Ringing) and a final success response (200 OK), which includes session description parameters typically formatted using the Session Description Protocol (SDP). The caller confirms with an ACK, and the media session (using RTP/RTCP) is established directly between the endpoints. To terminate the session, a BYE request is sent.

Within the 3GPP architecture, SIP is the cornerstone signaling protocol of the IP Multimedia Subsystem (IMS). The IMS provides a standardized framework for delivering multimedia services over IP. Key 3GPP network elements that act as SIP servers include the Proxy-Call Session Control Function (P-CSCF), which is the first contact point for the UE; the Serving-CSCF (S-CSCF), which performs session control and interacts with application servers; and the Interrogating-CSCF (I-CSCF), which interfaces with other networks. SIP in IMS is used for registration, authentication (often using IMS Authentication and Key Agreement (AKA)), and session control for services like Voice over LTE (VoLTE), Voice over NR (VoNR), Rich Communication Services (RCS), and Video Telephony. The protocol is extended with 3GPP-specific headers and parameters to support cellular requirements such as emergency calling, access network information, and policy control integration.

Purpose & Motivation

SIP was created to solve the problem of establishing and managing multimedia sessions in the evolving internet landscape. Prior to SIP, proprietary signaling protocols were common, hindering interoperability between different vendors' equipment and service providers. The growth of IP networks created a need for a standardized, flexible, and extensible signaling protocol that could support the burgeoning variety of real-time applications beyond simple voice. SIP was designed to be simple, modular, and text-based (like HTTP), making it easier to implement, debug, and extend compared to binary protocols like H.323.

3GPP adopted SIP as the signaling protocol for IMS to enable the convergence of cellular telephony with Internet multimedia services. This addressed a critical strategic need: to evolve circuit-switched voice services to a more efficient, feature-rich, all-IP architecture. SIP allowed mobile operators to offer standardized, interoperable voice and video services over their LTE and 5G data networks (VoLTE/VoNR), ensuring service continuity and quality. It also provided the foundation for new revenue-generating services like RCS (branded as Chat) and seamless integration with over-the-top (OTT) applications. By leveraging an IETF standard, 3GPP ensured that IMS-based services could interoperate with fixed-line VoIP networks and the broader internet, facilitating fixed-mobile convergence and fostering a rich ecosystem of application developers and service enablers.

What changed in its specifications

The latest release-to-release comparison of specifications that define SIP. Each summary describes the whole specification, not only this term.

TR 21.905Rel-17 → Rel-18

Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TR 21.905 →
TS 22.228Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 22.228: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 22.228 →

Technology family

Core signalling protocols · Core Network

  1. Phase 1 MAP
  2. Phase 2 ISUP
  3. R96 CAP
  4. R99 GTP-C, GTP-U, GTPv1-C
  5. Rel-4 BICC
  6. Rel-5 Diameter, SIP
  7. Rel-8 GTPv2-C
  8. Rel-14 PFCP
  9. Rel-15 HTTP/2 SBI

Also in this family (introduction release not pinned to a single defining specification): INAP, M2PA, SIGTRAN

  • SIP counterpart in another generation: ISUP (not stated verbatim in the specifications)

Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.

Release Timeline

Detected Changes Across Releases

verified against 3GPP sources

Documented changes in 16 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.

Rel-5 introduced

TS 24.229 Rel-5 adds SIP handling requirements for IMS entities: loose routeing, charging headers (ICID, access-network-charging-info), integrity protection checks, SDP media policy with 488 responses, and SIP compression.

  • “Each IM CN subsytem functional entity shall apply loose routeing policy as described in RFC 3261 [26], when processing a SIP request.” TS 24.229 v5.26.0
  • “The UE shall discard any SIP request that is not integrity protected and is received from the P-CSCF” TS 24.229 v5.26.0
  • “the P-CSCF shall return a 488 (Not Acceptable Here) response containing SDP payload” TS 24.229 v5.26.0
Rel-6 specification text

TS 24.229 Rel-6 changed SIP procedures: ICID generation now applies per SIP request outside INVITE dialogs, UEs discard requests not protected by the security association, and P-CSCF/S-CSCF examine SDP offers.

  • “For a dialog relating to a session, this will be performed only on the INVITE request, for all other transactions, it will occur on each SIP request.” TS 24.229 v6.30.0
  • “The UE shall discard any SIP request that is not protected by the security association and is received from the P-CSCF” TS 24.229 v6.30.0
  • “When the P-CSCF receives any SIP request containing an SDP offer, the P-CSCF shall examine the media parameters in the received SDP.” TS 24.229 v6.30.0
Rel-7 specification text

TS 24.229 changed SIP procedures in IMS: loose/strict routeing now covers IBCF and E-CSCF, P-CSCF and S-CSCF SDP media checks add PCRF bandwidth limits, and the IBCF gets SIP handling roles.

  • “In cases where the I-CSCF, IBCF, S-CSCF and the E-CSCF may interact with strict routers in non IM CN subsystem networks” TS 24.229 v7.34.0
  • “or if available by bandwidth authorisation limitation information coming from the PCRF, the P-CSCF shall return a 488 (Not Acceptable Here) response” TS 24.229 v7.34.0
  • “The IBCF may add, remove, or modify, the P-Early-Media header within forwarded SIP requests and responses” TS 24.229 v7.34.0
Rel-8 3 CRs

Cx interface specifications were changed to support SIP Digest authentication, including password push, AVP flag settings and AVP assignments, plus canonical form for SIP URI/tel URI.

  • SIP Digest password push TS 29.228CR0398
  • AVP assignments to support SIP Digest Authentication TS 29.230CR0101
  • Use of canonical form for SIP URI/tel URI in Cx interface TS 29.229CR0172
Rel-9 specification text

TS 24.229 changed SIP procedures at IMS entities: UE discards unprotected SIP requests also for TLS sessions, P-CSCF handles Via 'received' for GPRS-IMS-Bundled UEs, and I-CSCF discards P-Profile-Key.

Compared with Rel-7: intermediate versions are not available, so this change may date from any release since Rel-7.

  • “Where a security association or TLS session exists, the UE shall discard any SIP request that is not protected by the security association or TLS session” TS 24.229 v9.31.0
  • “the P-CSCF adds a "received" header field parameter to that Via header field value.” TS 24.229 v9.31.0
  • “The I-CSCF shall discard the P-Profile-Key header field, if the I-CSCF receives the P-Profile-Key header field in a SIP request or response.” TS 24.229 v9.31.0
Rel-10 specification text

TS 24.229 changed SIP procedures: privacy protection steps are required for requests leaving the trust domain, and P-CSCF/S-CSCF SDP offer handling was reworded to refer to an SDP message body.

  • “IBCF shall additionally to what is specified in subclause 4.4 and before sending the SIP requests or SIP responses outside the trust domain boundary perform the privacy protection” TS 24.229 v10.29.0
  • “if the SIP request is destined outside the trust domain boundary, perform the privacy protection procedures as specified in subclause 5.10.8;” TS 24.229 v10.29.0
Rel-11 1 CR

TS 24.229 changed SIP handling in IMS: ICID generation now occurs on each SIP request, loopback routeing for roaming local breakout was added, and P-header usage moved to RFC 7315.

  • “Loopback routeing: A method of routeing a SIP request back to the visited network for local breakout” TS 24.229 v11.31.0
  • “For all other transactions, generation of the ICID will occur on each SIP request and be included in that SIP request.” TS 24.229 v11.31.0
  • Update of SIP message routeing due to AS PSI TS 23.237CR0395
Rel-12 specification text

TS 24.229 SIP procedures changed: the "iotl" SIP URI parameter identifies the II-NNI traversal scenario, mid-dialog SIP messages get priority under overload, and the P-CSCF handles static-mode external attached networks.

  • “Dialog creating SIP requests and standalone requests can contain an "iotl" SIP URI parameter as specified in RFC 7549 [225]” TS 24.229 v12.27.0
  • “Mid-dialog SIP messages have higher priority with regard to initial SIP requests, and therefore are last to be dropped or rejected” TS 24.229 v12.27.0
  • “the P-CSCF shall initiate a TLS session towards the UE performing the functions of an external attached network operating in static mode” TS 24.229 v12.27.0
Rel-13 specification text

SIP procedures were specified or changed: the MCPTT server and clients gained rules for SIP request/response handling (Warning header, SIP 2xx/4xx responses), and the IMS SIP profile gained new overload responses and header fields.

  • “The MCPTT server can include a free text string in a SIP response to a SIP request.” TS 24.379 v13.19.0
  • “if the P-CSCF is unable to handle further requests from the UE (i.e. P-CSCF is overloaded by SIP requests)” TS 24.229 v13.23.0
  • “The Service-Interact-Info header field can be included in initial SIP requests and responses to initial SIP requests.” TS 24.229 v13.23.0
Rel-14 1 CR

SIP signalling procedures changed in Rel-14: MCPTT SIP requests now copy MIME bodies but exclude the <MKFC-GKTP> element, and new SIP MESSAGE request types for private call call-back were added.

  • “the <MKFC-GKTP> element shall not be copied into the application/vnd.3gpp.mcptt-info+xml MIME body included in the outgoing SIP request.” TS 24.379 v14.16.0
  • Correction of missing mcptt-client-id in SIP REGISTER TS 24.379CR0311
  • “the MCPTT server may insert a SIP Response-Source header field with an "fe" header field parameter” TS 24.379 v14.16.0
Rel-15 2 CRs

SIP procedures were changed in Rel-15: MCPTT SIP requests carry functional-alias-URI handling and location triggering criteria, and UEs must use SIP requests for updated SDP offers on all existing dialogs.

  • “if the received SIP request contains a <functional-alias-URI> element of the application/vnd.3gpp.mcptt-info+xml MIME body, then check if the status of the functional alias is activated” TS 24.379 v15.16.0
  • Using functional alias in initial SIP INVITE request – server procedures TS 24.379CR0395
  • Removing SIP COMET method TS 24.229CR6231
Rel-16 specification text

Rel-16 added SIP behaviour: new SIP MESSAGE types for MCPTT preconfigured regroup, a loc-src parameter in the SIP Geolocation header, and the SIP URI parameter "scscf-reselection" for S-CSCF re-selection.

  • “SIP MESSAGE requests routed to the MCPTT client with the Request-URI set to a public service identity of the MCPTT user” TS 24.379 v16.14.0
  • “include a loc-src parameter in the Geolocation header field set to the domain name of the visited network” TS 24.229 v16.17.0
  • “The "scscf-reselection" parameter is a SIP URI parameter intended to:” TS 24.229 v16.17.0
Rel-17 specification text

SIP signalling procedures changed in Rel-17: MCX gateway servers handle SIP requests/responses for interconnection with 403 rejection, and TS 24.229 added Priority-Verstat handling in forwarded SIP requests.

  • “the MCPTT gateway server receives SIP requests and SIP responses intended for the controlling, non-controlling or participating function in the interconnected MCPTT system.” TS 24.379 v17.15.0
  • “the MCPTT gateway shall reject the request by sending back a SIP 403 (Forbidden) response” TS 24.379 v17.15.0
  • “The AS shall populate the Priority-Verstat header field associated with the Resource-Priority header field and include the Priority-Verstat header field in the forwarded SIP request.” TS 24.229 v17.19.0
Rel-18 1 CR

Rel-18 changed SIP procedures: MCPTT/MCData/MCVideo SIP requests and responses for priority adhoc group calls, imminent peril and adhoc emergency alerts were added, and 24.229 gained a Handover-Info header and multiple Reason header values.

  • “6.2.8.1.22 Receiving a SIP 2xx response to a SIP request for a priority adhoc group call” TS 24.379 v18.14.0
  • “A SIP proxy that supports this extension and receives a request may as part of its procedures insert a Handover-Info header field” TS 24.229 v18.11.0
  • Correction of SIP INVITE from NCF to CF TS 24.379CR0874
Rel-19 specification text

SIP signalling usage was extended in Rel-19: new SIP MESSAGE request types and Reason header handling for ad hoc group emergency alerts and migration, plus new SIP header and parameter handling in IMS (rcd-np, satellite-id).

  • “Such requests are known as "SIP MESSAGE request with notification of ad hoc group call redirection " in the procedures in the present document;” TS 24.379 v19.8.0
  • “shall set the Reason SIP header according to IETF RFC 3326 [98] with the protocol set to SIP, the cause value set to 200” TS 24.379 v19.8.0
  • “This extension defines the "rcd-np" parameter used in the Call-Info header field in a SIP request.” TS 24.229 v19.7.0
Rel-20 1 CR

SIP handling in IMS changed: S-CSCF includes the new SIP URI parameter "imsas-reselection" towards the IMS AS, and SIP trust domain rules extend to the Server and User-Agent header fields.

  • “then the S-CSCF shall include the SIP URI parameter "imsas-reselection" to the IMS AS URI to be inserted into the Route header field” TS 24.229 v20.1.0
  • “A functional entity at the boundary of the trust domain will need to determine whether to remove the User-Agent header field” TS 24.229 v20.1.0
  • SIP Response-source definition TS 24.229CR6797

Defining Specifications

3GPP specifications that define or reference SIP, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TR 21.978 v300 CAMEL Control of VoIP Services Feasibility Study R99 read
TS 22.228 vl00 IMS Service Requirements Rel-21 read
TR 22.940 vj00 IMS Messaging Requirements Analysis Rel-19 read
TR 22.949 vj00 Privacy Requirements Study for 3GPP Services Rel-19 read
TR 22.953 vj00 Multimedia Priority Service Feasibility Study Rel-19 read
TR 22.977 vj00 Speech Enabled Services and Multimodal Framework Rel-19 read
TS 23.125 v700 Flow Based Charging Architecture Rel-7 read
TS 23.141 vj00 Presence Service Stage 2 Architecture Rel-19 read
TS 23.179 vd50 MCPTT Functional Architecture Rel-13 read
TS 23.207 vj00 End-to-End QoS Framework for GPRS Rel-19 read
TS 23.218 vj00 IMS Call Model Specification Rel-19 read
TS 23.221 vj00 3GPP System Architectural Requirements Rel-19 read
TS 23.228 vk10 IP Multimedia Core Network Subsystem Rel-20 read
TS 23.231 vj00 SIP-I based CS core network stage 2 Rel-19 read
TS 23.271 vj00 LCS Stage 2 Specification Rel-19 read
TS 23.278 vj00 CAMEL for IMS Stage 2 Specification Rel-19 read
TS 23.280 vk51 Mission Critical Services Architecture Rel-20 read
TS 23.281 vk51 Mission Critical Video Service Rel-20 read
TS 23.333 vj00 MRFC-MRFP Mp Interface Requirements Rel-19 read
TS 23.379 vk40 Mission Critical Push-to-Talk Architecture Rel-20 read
TS 23.392 vk10 MMTel Enabler Architecture and Procedures Rel-20 read
TS 23.417 v700 IMS Core Component for NGN Architecture Rel-7 read
TS 23.517 v800 IMS Core Architecture for TISPAN NGN Rel-8 read
TS 23.700 vk10 AI/ML Application Layer Support Phase 2 Rel-20 read
TS 23.701 vc00 WebRTC Access to IMS Study Rel-12 read
TS 23.802 v700 Enhanced End-to-End QoS Architecture Rel-7 read
TS 23.815 v500 IMS Charging Implications Rel-5 read
TS 23.849 vb00 IMS Roaming Resource Control Study Rel-11 read
TR 23.976 vj00 Push Service Requirements Analysis Rel-19 read
TR 23.979 vj00 PoC over 3GPP Systems Architectural Requirements Rel-19 read
TR 23.981 vj00 IPv4 IMS Interworking and Migration Study Rel-19 read
TS 24.103 vj00 Telepresence Protocol for IMS Rel-19 read
TS 24.141 vj00 Presence Service Protocol Details Rel-19 read
TS 24.147 vj00 IMS Conferencing Protocol Details Rel-19 read
TS 24.166 vj00 IMS Conferencing Management Object Rel-19 read
TS 24.167 vj10 3GPP IMS Management Object Rel-19 read
TS 24.173 vj00 Multimedia Telephony Service and Supplementary Services in IMS Rel-19 read
TS 24.196 vj00 Enhanced Calling Name (eCNAM) Stage 3 Protocol Rel-19 read
TS 24.206 v750 Voice Call Continuity Between CS and IMS Rel-7 read
TS 24.216 vj00 Communication Continuity Management Object Rel-19 read
TS 24.228 v590 IP Multimedia Call Control Signaling Flows Rel-5 read
TS 24.229 vk10 IMS SIP/SDP Call Control Protocol Rel-20 read
TS 24.247 vk00 IMS Messaging Protocol Specification Rel-20 read
TS 24.259 vj00 Personal Network Management (PNM) Protocol Details Rel-19 read
TS 24.281 vk10 MCVideo Signalling Control Rel-20 read
TS 24.282 vk10 MCData Signalling Control Protocols Rel-20 read
TS 24.315 vj00 Operator Determined Barring (ODB) for IMS Rel-19 read
TS 24.323 vj00 IMS Service Level Tracing Management Object Rel-19 read
TS 24.379 vk10 MCPTT Call Control Protocol Rel-20 read
TS 24.391 vj00 USSD over IMS Management Object Specification Rel-19 read
TS 24.404 v750 Communication Diversion Services Stage 3 Rel-7 read
TS 24.405 v700 Conference Service Protocol Description Rel-7 read
TS 24.406 v810 Message Waiting Indication (MWI) Protocol Rel-8 read
TS 24.407 v830 OIP and OIR Simulation Services Protocol Rel-8 read
TS 24.408 v700 TIP/TIR Services Protocol Specification Rel-7 read
TS 24.410 v810 Protocol Description of HOLD Services Rel-8 read
TS 24.416 v700 Malicious Call Identification Service Rel-7 read
TS 24.428 v720 Common Basic Communication Procedures Rel-7 read
TS 24.429 v700 Explicit Communication Transfer (ECT) Service Specification Rel-7 read
TS 24.447 v800 Advice Of Charge (AOC) Service Protocol Rel-8 read
TS 24.454 v840 Closed User Group (CUG) Protocol Specification Rel-8 read
TS 24.484 vk10 Mission Critical Services Configuration Management Rel-20 read
TS 24.504 v8m0 Communication Diversion (CDIV) Protocol Specification Rel-8 read
TS 24.505 v810 Protocol Description of the Conference Service Rel-8 read
TS 24.508 v820 TIP and TIR Service Protocol Description Rel-8 read
TS 24.516 v830 MCID Protocol Specification for NGN Rel-8 read
TS 24.523 vj00 NGCN-NGN Interconnection Scenarios Rel-19 read
TS 24.524 vj00 Hosted Enterprise Services Architecture Rel-19 read
TS 24.525 vj00 Business Trunking Architecture & Requirements Rel-19 read
TS 24.528 v830 Common Basic Communication Procedures for IMS Services Rel-8 read
TS 24.529 v820 Explicit Communication Transfer (ECT) Simulation Service Rel-8 read
TS 24.604 vj00 Communications Diversion (CDIV) Protocol Spec Rel-19 read
TS 24.605 vj00 3GPP CONF Service Protocol Specification Rel-19 read
TS 24.606 vj00 MWI Service Protocol Description Rel-19 read
TS 24.607 vj10 OIP and OIR Supplementary Services Stage 3 Rel-19 read
TS 24.608 vj00 3GPP TS 24608: TIP/TIR Services Protocol Rel-19 read
TS 24.610 vj00 Communication Hold (HOLD) Service Protocol Rel-19 read
TS 24.615 vj00 Communication Waiting (CW) Service Protocol Rel-19 read
TS 24.616 vj00 Malicious Call Identification (MCID) Protocol Rel-19 read
TS 24.628 vj00 Common Basic Communication Procedures in IMS Rel-19 read
TS 24.629 vj00 Explicit Communication Transfer (ECT) Protocol Rel-19 read
TS 24.642 vj00 CCBS/CCNR/CCNL SIP Protocol Specification Rel-19 read
TS 24.647 vj00 Advice of Charge (AOC) service protocol Rel-19 read
TS 24.654 vj00 Closed User Group (CUG) supplementary service Rel-19 read
TS 24.803 vc00 Telepresence Using IMS Rel-12 read
TS 24.819 v700 IMS Services via Fixed Broadband Access Rel-7 read
TS 24.841 v600 Presence Service IP Multimedia Subsystem Rel-6 read
TR 24.930 vj00 IMS Session Setup Signalling Flows Rel-19 read
TR 25.993 vj00 UTRA RAB Examples and Radio Interface Mapping Rel-19 read
TS 26.114 vk11 IMS Multimedia Telephony Client Rel-20 read
TS 26.235 vc00 Default Codecs for 3GPP IP Multimedia Subsystem Rel-12 read
TS 26.236 vc00 Packet Switched Conversational Multimedia Protocols Rel-12 read
TR 26.862 vh00 Immersive Teleconferencing & Telepresence for Remote Terminals Rel-17 read
TR 26.914 vj00 Multimedia Telephony over IP Optimization Rel-19 read
TR 26.928 vj00 Study on eXtended Reality (XR) in 5G Rel-19 read
TR 26.982 vj00 Multiparty Real-Time Text Protocol Details Rel-19 read
TR 26.998 vj00 5G AR/MR Glasses Integration Study Rel-19 read
TS 27.060 vj00 TE-MT Interworking for Packet Domain Rel-19 read
TS 29.162 vj00 IMS-IP Network Interworking Rel-19 read
TS 29.199 3GPP TS 29.199 Rel-5 read
TS 29.228 vk00 IMS Cx and Dx Interface Procedures Rel-20 read
TS 29.229 vj10 Diameter Protocol for Cx/Dx Interfaces Rel-19 read
TS 29.328 vk00 IMS Sh, Dh and Ph Interface Procedures Rel-20 read
TS 29.332 vj00 MGCF-IM-MGW Interface Protocol (Mn) Rel-19 read
TS 29.412 v810 Control Procedures for Trunk Gateways in NGN Networks Rel-8 read
TS 29.421 v810 IMS Interworking with External IP Networks Rel-8 read
TS 29.424 v801 H.248 Profile for Trunking Media Gateways Rel-8 read
TS 29.433 v811 TISPAN endorsement of 3GPP Cx and Dx interfaces Rel-8 read
TS 29.458 v850 SIP Transfer of Tariff Info for Charging Rel-8 read
TS 29.514 vk10 Policy Authorization Service Rel-20 read
TS 29.562 vk10 HSS Nhss Services for IMS and GBA Rel-20 read
TS 29.658 vj00 SIP Transfer of Tariff Information Rel-19 read
TS 31.103 vj10 IM Services Identity Module Specification Rel-19 read
TS 31.829 vd00 ISIM-ME Interface Conformance Requirements Rel-13 read
TS 32.260 vk10 IMS Charging Management Rel-20 read
TS 32.272 vj00 Charging for Push-to-Talk over Cellular (PoC) Rel-19 read
TS 32.280 vj00 Advice of Charge (AoC) Framework Rel-19 read
TS 32.281 vj00 Announcement Service for Online Charging Rel-19 read
TS 32.296 vj00 Online Charging System (OCS) Architecture Rel-19 read
TS 32.808 v800 Common Profile Storage Framework for User Data Rel-8 read
TS 33.106 vj00 Lawful Interception Requirements (Pre-Rel-15) Rel-19 read
TS 33.107 vj00 Lawful Interception Architecture & Functions Rel-19 read
TS 33.108 vj00 LI Handover Interface Specification Rel-19 read
TS 33.126 vj30 Lawful Interception Requirements Rel-19 read
TS 33.127 vj80 Lawful Interception Architecture Rel-19 read
TS 33.128 vj80 Lawful Interception Protocols and Procedures Rel-19 read
TS 33.141 vj00 Security for Presence Service (Ut reference point) Rel-19 read
TS 33.203 vk00 IMS Security Features and Mechanisms Rel-20 read
TS 33.210 vk00 Network Domain Security for IP Networks Rel-20 read
TS 33.790 vj10 Security for Next-Gen Real-Time Communication Phase 2 Rel-19 read
TS 33.804 vc00 Non-UICC SSO using SIP Digest credentials Rel-12 read
TS 33.838 vb00 PUCI High-Level Solution Study Rel-11 read
TS 33.871 vc00 Security for WebRTC IMS Client Access Rel-12 read
TS 33.978 v800 Early IMS Security Interim Solution Rel-8 read
TS 36.579 3GPP TR 36.579 Rel-5 read
TS 37.579 vi50 Mission Critical (MC) services Rel-18 read
TS 38.291 vj30 Ambient IoT Physical Layer Rel-19 read
TS 43.129 vj00 PS Handover in GERAN A/Gb and GAN Modes Rel-19 read