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

Glossary term · Services

AS

Application Server

Services →

AS is a network element that hosts and executes value-added service logic, such as calling or messaging, and interfaces with the core network to provide these services to users.

Introduced
Rel-5
Where
Services › Codecs
Specifications
201 specs
Also in
Radio Access Network, Core Network
AS Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The Application Server (AS) is a functional entity within the 3GPP service architecture, specifically defined in the IP Multimedia Subsystem (IMS) and other service delivery frameworks. It resides in the service layer, separate from the transport and control layers of the core network. The AS hosts and executes service logic for value-added services, such as telephony application server (TAS) functions for voice/video over LTE (VoLTE), rich communication services (RCS), instant messaging, presence, group management, and location-based applications. It acts as the endpoint for service execution, often implementing business logic defined in service capability interaction manager (SCIM) patterns or using protocols like SIP for service invocation.

Architecturally, the AS interfaces with core network elements via standardized reference points. In IMS, the primary interface is the ISC (IMS Service Control) reference point towards the Serving-Call Session Control Function (S-CSCF), using the Session Initiation Protocol (SIP). This allows the S-CSCF to delegate session control and service logic execution to the AS based on initial filter criteria (iFC) stored in the subscriber profile. The AS can also interact with other network functions, such as the Home Subscriber Server (HSS) via the Sh interface for subscriber data, or with media resource functions (MRF) for media processing. It may be deployed as a physical server or as a virtualized network function (VNF) in cloud-native architectures.

In operation, when a user initiates a service (e.g., a call), the S-CSCF evaluates the iFC and may forward the SIP request to a designated AS. The AS then executes the service logic, which may involve modifying the SIP message, interacting with databases, performing number translation, applying charging policies, or interacting with external application servers via open APIs (e.g., Parlay X, RESTful APIs). The AS plays a critical role in service personalization, enabling features like call forwarding, voicemail, prepaid billing integration, and multimedia conferencing. Its design allows for the decoupling of service logic from core network switching functions, fostering innovation and rapid service deployment by operators and third-party providers.

Purpose & Motivation

The Application Server was introduced to enable the creation and delivery of advanced, value-added services in mobile networks beyond basic voice and SMS. Prior to its formalization in 3GPP, service logic was often tightly integrated into switching centers, making service creation complex, slow, and vendor-locked. The AS concept, particularly with the advent of IMS in Release 5, aimed to provide a standardized, open, and scalable platform for service execution. It solves the problem of service silos by providing a common point for service interaction, allowing for the blending of services (e.g., combining voice with video and messaging) and consistent user experiences across different access networks.

Historically, the motivation stemmed from the desire to move towards an all-IP network and compete with internet-based service providers. The AS allows network operators to leverage their control over the network (e.g., quality of service, authentication, billing) to offer reliable, carrier-grade services. It addresses the limitations of intelligent network (IN) approaches by using internet protocols like SIP and HTTP, enabling richer multimedia services and easier integration with web technologies. The AS model supports both network-operator-provided services and exposure to third-party developers through standardized APIs, creating an ecosystem for service innovation.

What changed in its specifications

The latest release-to-release comparison of specifications that define AS. 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 23.218Rel-18 → Rel-19

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

Full comparison in TS 23.218 →

Technology family

IMS functions · Services › IMS

  1. R99 OSA-SCS
  2. Rel-5 AS, BGCF, CSCF, I-CSCF, IM-MGW, IM-SSF, MGCF, MRFC, MRFP, P-CSCF, S-CSCF
  3. Rel-6 IBCF, IMS-ALG, TrGW
  4. Rel-7 E-CSCF, IMS-AGW
  5. Rel-8 MRB, SCC AS
  6. Rel-9 EATF
  7. Rel-10 ATCF, ATGW
  • AS extended by SCC AS
    “IMS Service Continuity requires a Service Centralization and Continuity (SCC) AS, which is an Application Server as described in TS 23.228 [4]” TS 23.237
  • AS used together with S-CSCF
    “The Serving‑CSCF to AS interface is used to provide services residing in an AS.” TS 23.002
  • AS used together with MRFC
    “In addition the Application Servers can also interact with the MRFC via the S-CSCF (ISC, Mr), directly via the Mr' interface and via the Cr interface in order to control Multimedia Resource Function processing” TS 23.218

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

Rel-5 specifies the Application Server for IMS: it hosts services, communicates with the S-CSCF over the ISC interface, and operates in SIP modes such as UA, proxy and B2BUA.

  • “The SIP Application Server may host and execute services.” TS 23.228 v5.15.0
  • “An Application Server can utilize five basic modes of operation for processing SIP Requests.” TS 23.218 v5.9.0
  • “delegates service execution to an "Application Server"” TS 23.228 v5.15.0
Rel-6 specification text

In Rel-6 the Application Server gained new IMS behaviours: subscribing to the S-CSCF registration event package, originating SIP requests on behalf of users, and hosting Public Service Identities.

  • “Application Servers can in addition subscribe to the S-CSCF Registration Event Package.” TS 23.218 v6.4.0
  • “It shall be possible for an Application Server to generate SIP requests and dialogs on behalf of users.” TS 23.228 v6.16.0
  • “Each Public Service Identity is hosted by an Application Server, which executes the service specific logic as identified by the Public Service Identity.” TS 23.228 v6.16.0
Rel-7 specification text

Rel-7 adds a Telephony Application Server (SIP-AS for multimedia telephony) and specifies Application Server roles such as discovering implicit identities via reg event subscription and UE-terminating request handling.

  • “The Telephony Application Server is a SIP-AS providing the network support for the multimedia telephony service, TS 22.173 [53].” TS 23.228 v7.16.0
  • “Application Servers can in addition subscribe to the S-CSCF reg event package.” TS 23.218 v7.10.0
  • “shall be performed by an Application Server in the subscriber's Home Network.” TS 23.228 v7.16.0
Rel-8 specification text

In Rel-8 the Application Server gained new behaviour: it can originate sessions on behalf of users or PSIs via an I-CSCF, and filter information can carry a service indication for ordered execution.

  • “It shall be possible for an Application Server to originate a session on behalf of users or Public Service Identities.” TS 23.228 v8.12.0
  • “It shall be possible to include a service indication in the filter information, which is used to identify services and the order” TS 23.228 v8.12.0
  • “forward SIP requests destined to a Public Service Identity hosted by an Application Server directly to the Application Server;” TS 23.228 v8.12.0
Rel-9 specification text

Application Server may now exchange session control messages with the MRFC directly over the new Mr' interface, without passing through the S-CSCF, instead of only via the S-CSCF over ISC.

  • “Mr' interface allows an Application Server and an MRFC to exchange session control messages without passing through an S-CSCF.” TS 23.218 v9.2.0
  • “The MRFC accepts INVITE requests sent from an Application Server, either directly using the Mr' interface or via the S-CSCF using the ISC interface” TS 23.218 v9.2.0
Rel-10 specification text

The AS origination procedure was reworded to state that an AS may initiate a session on behalf of an IMS user (Public User Identity) or a non-IMS user with no HSS profile.

  • “the user may be an IMS user (i.e. referred to by a Public User Identity) or a non-IMS user (i.e. with no profile in the HSS, e.g. a PSTN user)” TS 23.228 v10.9.0
Rel-11 specification text

Rel-11 adds Transit Function behaviour toward the Application Server over ISC (ODI, forwarding on Transit Invocation Criteria, failure handling, IOI storage) and AS overload control between CSCF and AS.

  • “forward the request via the ISC interface to the Application Server indicated in the current filter criteria.” TS 23.218 v11.6.0
  • “if the contact of the Application Server fails, the Transit Function shall use the "default handling" associated with the Transit Invocation Criteria” TS 23.218 v11.6.0
  • “Application Server overload control (i.e., between CSCF and AS).” TS 23.228 v11.11.0
Rel-12 specification text

The HSS–IM-SSF Application Server interface now covers both Si and Sh for IMS CAMEL information, and IP-PBX support specifies Application Servers performing identity assertion and terminating session routing.

  • “The Si and the Sh interfaces between HSS and the IM-SSF Application Server are used for transferring IMS CAMEL specific information.” TS 23.218 v12.3.0
  • “The IP‑PBX identity assertion and the routing of terminating sessions are performed by Application Server(s)” TS 23.228 v12.11.0
Rel-13 specification text

The Application Server is now specified to provide a priority sharing indicator for the media flow to the P-CSCF, and not to include it for emergency sessions.

  • “The P-CSCF receives a priority sharing indicator associated with the media flow from the Application Server.” TS 23.228 v13.9.0
  • “The Application Server is not supposed to include the priority sharing indicator for an emergency session.” TS 23.228 v13.9.0
Rel-14 specification text

Rel-14 introduces V2X Application Server behaviour in TS 23.285, including V2 connection to multiple PLMNs, MBMS session and TMGI management via BM-SC, and location mapping; TS 23.228 requires AS configuration with a Data Off exempted list.

  • “The V2X Application Server may connect to V2X Control Functions belonging to multiple PLMNs.” TS 23.285 v14.9.0
  • “V2X Application Server shall map UE provided location information to a form that is understood by the 3GPP MBMS system” TS 23.285 v14.9.0
  • “each Application Server shall be configured with the applicable list of 3GPP PS Data Off Exempted Service.” TS 23.228 v14.7.0
Rel-15 specification text

Application Servers must now be configured with up to two lists of 3GPP PS Data Off Exempt Services (non-roaming and roaming), replacing the single list for all PLMNs, and a new Ms reference point between IBCF and AS is added.

  • “Each Application Server shall be configured with up to two lists of 3GPP PS Data Off Exempt Services” TS 23.228 v15.5.0
  • “Ms Reference point between an IBCF and Application Server” TS 23.228 v15.5.0
Rel-16 1 CR

V2X Application Server handling was extended to allow TCP/IP as well as UDP/IP transport and to cover AID identifiers, with the server address now including a TCP or UDP port.

  • “the V2X Application Server receives the V2X message in a TCP/IP or UDP/IP packet on a V2X Application Server address.” TS 23.285 v16.4.0
  • “V2X Application Server address (consisting of IP address/FQDN and TCP or UDP port) for unicast;” TS 23.285 v16.4.0
  • Supplement for address resolution and clarification for Localized V2X Application Server discovery and routing TS 23.287CR0019
Rel-17 specification text

TS 23.554 first specifies the Application Server role in the MSGin5G Service, covering registration, de-registration, message exchange and CAPIF API invoker support.

  • “The Application Server supports sending and receiving messages with MSGin5G Service layer protocols and procedures.” TS 23.554 v17.2.0
  • “The Application Server shall act as API invoker and support the API invoker functions” TS 23.554 v17.2.0
  • “The Application Server sends an Application Server registration request to the MSGin5G Server.” TS 23.554 v17.2.0
Rel-18 specification text

In Rel-18 the Application Server's role in MSGin5G and IMS data channel is extended: AS registration request content changed, new AS-to-Point and Point-to-AS messaging, and new DC/AR Application Server roles and interfaces.

  • “The request shall include the AS Service ID and may include Application Profile information and Requested expiration time as detailed in Table 9.1.2.3‑1.” TS 23.554 v18.10.0
  • “AS-to-Point messaging: an MSGin5G message delivery that is originated at an Application Server in the network and terminated at a UE.” TS 23.554 v18.10.0
  • “AR Application Server: An application server used to control the service logic related to AR communication via IMS data channel.” TS 23.228 v18.12.0
Rel-19 specification text

Rel-19 adds a Controlling AS role in MSGin5G group messaging, with AS registration of expected group lists, and adds a DC Application Server description for data channel handling.

  • “Controlling AS: A specific Application Server(s) which is allowed by the MSGin5G service provider to provide Application specific service logic to the group message” TS 23.554 v19.8.0
  • “Expected group list: A list of MSGin5G group which the Application Server will control.” TS 23.554 v19.8.0
  • “DC Application Server: An application server that interacts with the DCSF and the DC media function for data channel traffic handling” TS 23.228 v19.8.0
Rel-20 specification text

Rel-20 removes the DCSF steps in which the DC Application Server receives the P2A data channel establishment request, answers with an MDC2 media resource and is prepared for UE#1 traffic.

  • “DC Application Server accepts the P2A application data channel establishment request, returning an MDC2 reserved media resource as answer” TS 23.228 v20.1.0
  • “sends a P2A application data channel establishment request (including the MDC2 media resource received from MF) to the DC Application Server via DC3/DC4” TS 23.228 v20.1.0

Defining Specifications

3GPP specifications that define or reference AS, 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
TS 22.870 vk00 Study on 6G Use Cases and Service Requirements Rel-20 read
TR 22.882 vj30 Study on Energy Efficiency as a Service Criteria Rel-19 read
TS 23.110 vj00 Access Stratum Services Specification Rel-19 read
TS 23.218 vj00 IMS Call Model Specification Rel-19 read
TS 23.222 vk10 Common API Framework (CAPIF) Rel-20 read
TS 23.228 vk10 IP Multimedia Core Network Subsystem Rel-20 read
TS 23.236 vj00 Intra Domain Connection of RAN Nodes to Multiple CN Nodes Rel-19 read
TS 23.279 vj00 Combined CS and IMS Services (CSI) Architecture Rel-19 read
TS 23.286 vk10 V2X Application Enabler Architecture Rel-20 read
TS 23.367 vk00 5G Application Energy Information Architecture Rel-20 read
TS 23.417 v700 IMS Core Component for NGN Architecture Rel-7 read
TS 23.468 vj00 Group Communication System Enablers for LTE Rel-19 read
TS 23.501 vk30 5G System Architecture Rel-20 read
TS 23.517 v800 IMS Core Architecture for TISPAN NGN Rel-8 read
TS 23.554 vj80 MSGin5G Service Application Architecture Rel-19 read
TS 23.682 vj30 Architecture for MTC and SCEF Enhancements Rel-19 read
TS 23.700 vk10 AI/ML Application Layer Support Phase 2 Rel-20 read
TS 23.722 vf10 Common API Framework (CAPIF) for 3GPP Northbound APIs Rel-15 read
TR 23.730 ve00 Study on extended CIoT architecture Rel-14 read
TR 23.745 vh00 Study on App Layer Support for Factories of the Future in 5G Rel-17 read
TS 23.795 vg10 V2X Application Architecture Study Rel-16 read
TR 23.799 ve00 Study on Next Generation System Architecture Rel-14 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.958 vj00 EDGEAPP alignment with ETSI MEC and GSMA OP Rel-19 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
TS 24.103 vj00 Telepresence Protocol for IMS Rel-19 read
TS 24.109 vj00 HTTP Digest AKA & GAA Stage 3 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.173 vj00 Multimedia Telephony Service and Supplementary Services in IMS Rel-19 read
TS 24.174 vj00 Multi-Device & Multi-Identity in IMS Protocol Rel-19 read
TS 24.186 vk10 IMS Data Channel and AR Communication Rel-20 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.229 vk10 IMS SIP/SDP Call Control Protocol Rel-20 read
TS 24.239 vj00 Flexible Alerting Protocol for IMS Rel-19 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.292 vj00 IMS Centralized Services (ICS) Protocol Rel-19 read
TS 24.315 vj00 Operator Determined Barring (ODB) for IMS Rel-19 read
TS 24.341 vj00 SMS over IP protocol details Rel-19 read
TS 24.380 vk10 MCPTT Media Plane Control Protocols Rel-20 read
TS 24.390 vk10 USSD over IMS Procedures Rel-20 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.410 v810 Protocol Description of HOLD Services Rel-8 read
TS 24.411 v830 3GPP TS 24411 v830: Anonymous Communication Rejection and Communication Barring Rel-8 read
TS 24.416 v700 Malicious Call Identification Service Rel-7 read
TS 24.423 v850 PSTN/ISDN Simulation Services XCAP Protocol Rel-8 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.486 vj00 V2X Application Enabler (VAE) Protocol Spec Rel-19 read
TS 24.501 vk10 5GS NAS Protocol Specification 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.538 vj40 MSGin5G Service Protocol Specification Rel-19 read
TS 24.560 vk10 AIMLE SEAL Services Stage 3 Rel-20 read
TS 24.581 vj30 MCVideo Media Plane Control Rel-19 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.611 vj00 Anonymous Communication Rejection & Barring Rel-19 read
TS 24.616 vj00 Malicious Call Identification (MCID) Protocol Rel-19 read
TS 24.623 vj00 XCAP Protocol for Supplementary Services 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.802 vc10 II-NNI Traversal Scenario Determination Rel-12 read
TS 24.819 v700 IMS Services via Fixed Broadband Access Rel-7 read
TS 24.880 v820 Media Server Control Protocol Study for IMS Rel-8 read
TR 24.930 vj00 IMS Session Setup Signalling Flows Rel-19 read
TS 25.301 vj00 UE-UTRAN Radio Interface Protocol Architecture Rel-19 read
TS 25.304 vj10 UE Idle Mode Procedures Rel-19 read
TS 25.323 vj00 Packet Data Convergence Protocol (PDCP) Specification Rel-19 read
TS 25.324 vj00 Broadcast/Multicast Control Protocol Rel-19 read
TS 25.331 vj01 UTRAN Radio Resource Control Protocol Rel-19 read
TS 25.367 vj00 Home NodeB Mobility Procedures Rel-19 read
TS 25.413 vj00 Radio Access Network Application Part (RANAP) Rel-19 read
TS 25.415 vj00 Iu Interface User Plane Protocol Rel-19 read
TS 25.800 vc10 UMTS Heterogeneous Networks Study Rel-12 read
TR 25.912 vj00 Evolved UTRA and UTRAN Technical Report Rel-19 read
TR 25.931 vj00 UTRAN Signalling Procedures Examples Rel-19 read
TR 25.996 vj00 3GPP-3GPP2 Spatial Channel Model Specification Rel-19 read
TS 26.102 vj00 Mapping of AMR and other codecs to interfaces Rel-19 read
TS 26.114 vk11 IMS Multimedia Telephony Client Rel-20 read
TS 26.202 vj00 AMR-WB Speech Codec Mapping Specification Rel-19 read
TS 26.223 vj00 IMS Telepresence Client Specification Rel-19 read
TS 26.264 vj41 IMS Conversational Augmented Reality Services Rel-19 read
TS 26.346 vj30 MBMS User Services Specification Rel-19 read
TS 26.501 vk00 5G Media Streaming Architecture Rel-20 read
TS 26.510 vj20 5G Media Streaming and Real-Time Communication APIs Rel-19 read
TS 26.511 vj00 5G Media Streaming Profiles, Codecs & Formats Rel-19 read
TS 26.512 vj30 5G Media Streaming Protocols and APIs Rel-19 read
TS 26.531 vj00 Data Collection & Reporting Architecture for 5G Rel-19 read
TS 26.532 vj10 Data Collection and Reporting API Specification Rel-19 read
TS 26.565 vj00 Split Rendering Media Service Enabler Rel-19 read
TS 26.567 vj20 IMS-Based Split Rendering Rel-19 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.919 vj00 Study on 5G Conversational Media Handling Rel-19 read
TR 26.923 vj00 Study on IMS-based Telepresence Media Handling Rel-19 read
TR 26.927 vj00 AI/ML in 5G Media Services Study Rel-19 read
TS 26.942 vk00 Sustainable Media Metrics and Architectural Impacts for 5G Rel-20 read
TR 26.944 vj00 QoE, ESQoS and SQoS metrics for 3G multimedia services Rel-19 read
TR 26.982 vj00 Multiparty Real-Time Text Protocol Details Rel-19 read
TR 26.989 vj00 MCPTT Enhancement Analysis Rel-19 read
TR 26.998 vj00 5G AR/MR Glasses Integration Study Rel-19 read
TS 28.702 vj00 Core Network NRM IRP Information Service Rel-19 read
TS 28.705 vj00 IMS NRM IRP Information Service Rel-19 read
TS 28.849 vj10 CAPIF Phase2 Charging Study Rel-19 read
TS 28.851 vj10 Charging for Next Gen Real Time Communication Phase 2 Rel-19 read
TS 29.122 vk10 T8 SCEF Service Exposure APIs Rel-20 read
TS 29.153 vj00 Ns Reference Point Protocol between SCEF and RCAF Rel-19 read
TS 29.165 vk00 Inter-IMS Network-to-Network Interface (II-NNI) Rel-20 read
TS 29.214 vk00 Rx Interface for Policy and Charging Control Rel-20 read
TS 29.222 vk10 CAPIF Northbound API Protocol Rel-20 read
TS 29.244 vk10 PFCP for Control and User Plane Separation Rel-20 read
TS 29.311 vj00 Service Level Interworking for Messaging Rel-19 read
TS 29.328 vk00 IMS Sh, Dh and Ph Interface Procedures Rel-20 read
TS 29.329 vj10 Diameter Protocol for Sh Interface Rel-19 read
TS 29.364 vj10 IMS AS Service Data Descriptions Rel-19 read
TS 29.538 vk00 MSGin5G Service API Stage 3 Rel-20 read
TS 29.561 vk10 5G Network Interworking Procedures Rel-20 read
TS 29.562 vk10 HSS Nhss Services for IMS and GBA Rel-20 read
TS 29.581 vk00 Nmbstf Service Based Interface Stage 3 Rel-20 read
TS 29.806 vc10 P-CSCF Restoration Analysis & Solutions Rel-12 read
TS 29.827 vg00 Policy and Charging for Volume Based Charging Rel-16 read
TS 29.864 v801 Application Server Service Data Definition for IMS Telephony Rel-8 read
TS 29.866 vj00 IMS Disaster Prevention & Restoration Enhancement Rel-19 read
TR 29.949 vj00 VoLTE IMS Roaming Architecture & Procedures Rel-19 read
TS 32.102 vj00 Telecom Management Physical Architecture Framework Rel-19 read
TS 32.240 vk10 3GPP Charging Architecture and Principles Rel-20 read
TS 32.254 vk00 3GPP TS 32.254: Charging for Northbound APIs Rel-20 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.281 vj00 Announcement Service for Online Charging Rel-19 read
TS 32.295 vj00 3GPP Charging: CDR Transfer via GTP' Protocol Rel-19 read
TS 32.299 vj00 Diameter Charging Applications for 3GPP Rel-19 read
TS 32.422 vk30 Trace, MDT and UE Measurement Control Rel-20 read
TS 32.632 vb00 Core Network Resources NRM Rel-11 read
TS 32.732 vb00 IMS Network Resource Model Information Service Rel-11 read
TS 32.808 v800 Common Profile Storage Framework for User Data Rel-8 read
TS 32.850 ve00 IMS Charging Correlation Methods Study Rel-14 read
TS 32.869 vf00 Diameter Overload Control for Charging Interfaces Rel-15 read
TS 33.107 vj00 Lawful Interception Architecture & Functions Rel-19 read
TS 33.127 vj80 Lawful Interception Architecture Rel-19 read
TS 33.141 vj00 Security for Presence Service (Ut reference point) Rel-19 read
TS 33.185 vj00 V2X Security in LTE Rel-19 read
TS 33.203 vk00 IMS Security Features and Mechanisms Rel-20 read
TS 33.222 vj00 Secure HTTP Access in GAA Rel-19 read
TS 33.303 vj00 ProSe Security Specification for EPS Rel-19 read
TS 33.401 vj20 EPS Security Architecture Rel-19 read
TS 33.804 vc00 Non-UICC SSO using SIP Digest credentials Rel-12 read
TS 33.821 v900 LTE/SAE Security Threat Analysis and Countermeasures Rel-9 read
TS 33.838 vb00 PUCI High-Level Solution Study Rel-11 read
TR 33.853 vh00 Study on User Plane Integrity Protection Rel-17 read
TS 33.885 ve10 Security Study for V2X Services Rel-14 read
TR 33.919 vj00 GAA Overview TR Rel-19 read
TS 33.929 3GPP TR 33.929 Rel-5 read
TR 33.937 vj00 Protection against Unsolicited Communication in IMS Rel-19 read
TR 33.980 vj00 GAA & Liberty Alliance Interworking Guidelines Rel-19 read
TS 36.300 vj20 E-UTRAN Radio Interface Protocol Architecture Rel-19 read
TS 36.302 vj00 E-UTRA Physical Layer Services Rel-19 read
TS 36.304 vj30 LTE UE Idle Mode Procedures Rel-19 read
TS 36.321 vj30 E-UTRA MAC Protocol Specification Rel-19 read
TS 36.331 vj40 E-UTRA Radio Resource Control (RRC) Protocol Rel-19 read
TS 36.401 vj00 E-UTRAN Overall Architecture Description Rel-19 read
TS 36.410 vj00 S1 Interface: General Aspects and Principles Rel-19 read
TS 36.938 v900 E-UTRAN to 3GPP2/Mobile WiMAX Mobility Rel-9 read
TS 38.304 vj30 NR UE Idle and Inactive State Procedures Rel-19 read
TS 38.331 vj40 NR Radio Resource Control (RRC) Rel-19 read
TS 38.401 vj30 NG-RAN Architecture Description Rel-19 read
TS 38.753 vj00 Spatial Channel Model Study for NR Demodulation Rel-19 read
TS 38.811 vf40 Study on NR Support for Non-Terrestrial Networks Rel-15 read
TS 38.827 vg80 NR MIMO OTA Radiated Metrics & Test Methodology Rel-16 read
TR 38.858 vi20 Technical Report on Evolution of NR Duplex Operation Rel-18 read
TR 38.900 vf00 Channel Model Study for >6 GHz Rel-15 read
TS 38.901 vj50 5G NR Channel Model Rel-19 read
TS 43.051 vj00 GERAN Stage 2 Service Description Rel-19 read
TS 43.318 vj00 Generic Access Network (GAN) Stage 2 Rel-19 read
TR 43.902 vj00 GAN Enhancements Feasibility Study Rel-19 read
TS 44.060 vj00 GERAN RLC/MAC Protocol Specification Rel-19 read