Description
Within 3GPP, Next Generation Networks (NGN) represents the overarching architectural evolution from traditional, siloed telecommunication networks (PSTN, legacy mobile core) towards a unified, packet-based infrastructure capable of delivering a wide range of multimedia services. The core technical realization of NGN in 3GPP is the IP Multimedia Subsystem (IMS), defined as a subsystem within the packet-switched domain. IMS provides a standardized service delivery platform that uses Session Initiation Protocol (SIP) for session control and runs over IP transport, decoupling service logic from access technology.
NGN/IMS works by introducing a layered architecture. The transport layer provides IP connectivity, the control layer (comprising CSCF - Call Session Control Functions) handles SIP signaling for session establishment, modification, and termination, and the application layer hosts the actual service logic (Application Servers). Key components include the HSS (Home Subscriber Server) for user data, and various border control functions (P-CSCF, I-CSCF, S-CSCF) that manage network access and routing. This setup allows for the delivery of voice (VoIP), video, messaging, and other rich communication services with appropriate quality of service (QoS) and charging controls, independent of whether the user is on a GSM, WCDMA, LTE, or even fixed broadband access.
Its role expanded with later 3GPP releases to encompass the entire Evolved Packet Core (EPC) for LTE, which is the pure-IP core network for 4G. Here, NGN principles are fully realized with a flat, all-IP architecture supporting high-speed data and voice via IMS (VoLTE). The NGN framework ensures service continuity, interoperability with legacy systems, and a migration path for operators. It is the foundation for Fixed-Mobile Convergence (FMC), enabling seamless services across different access networks, and it paved the way for the fully cloud-native, service-based architecture of the 5G Core (5GC).
Purpose & Motivation
NGN was conceived to solve critical limitations of legacy telecom networks, which were built on dedicated, circuit-switched technology for each service (e.g., one network for voice, another for data). This model was inefficient, costly to scale, and inflexible for introducing new multimedia services. The primary problem was the inability to converge services onto a single, efficient infrastructure and the high operational cost of maintaining multiple parallel networks.
The motivation for NGN, and specifically IMS within 3GPP, was to leverage the ubiquity and efficiency of Internet Protocol (IP) to create a future-proof service platform. It aimed to enable rich, real-time multimedia communications (beyond simple voice) and to break down the barriers between fixed, mobile, and internet services. This addressed the operator's need to compete with Over-the-Top (OTT) service providers and to generate new revenue streams from bundled communication packages.
Historically, starting from 3GPP Release 5 (where IMS was first specified), NGN provided the strategic answer to the 'all-IP' transformation. It solved the problem of how to deliver carrier-grade voice and messaging over packet networks with the required reliability, security, and charging capabilities that best-effort internet services lacked. By standardizing IMS, 3GPP ensured global interoperability for multimedia services, facilitating the eventual sunset of circuit-switched networks and enabling the successful transition to 4G LTE and 5G, where all services, including voice, are delivered as data over IP.
Classification
Evolution Across Releases
Laid the initial groundwork for NGN evolution within 3GPP by introducing a packet-switched core network domain alongside the circuit-switched core. This release defined the GPRS core network architecture, establishing the foundational IP transport capability and setting the stage for the full IMS-based NGN introduced in subsequent releases.
Explore further
Broader topics and technologies where NGN plays a role.
Defining Specifications
3GPP specifications that define or reference NGN, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 21.202 vj00 | Common IMS Specifications List | Rel-19 |
| TS 22.273 v1700 | IMS Multimedia Telephony with PSTN/ISDN Simulation | Rel-7 |
| TS 22.401 v1800 | Videotelephony Service Requirements for NGN | Rel-8 |
| TS 22.495 v1700 | NGN Requirements for IMS Services | Rel-7 |
| TS 22.519 vj00 | NGN Business Communication Requirements | Rel-19 |
| TS 23.221 vj00 | 3GPP System Architectural Requirements | Rel-19 |
| TS 23.417 v1700 | IMS Core Component for NGN Architecture | Rel-7 |
| TS 23.517 v1800 | IMS Core Component for NGN Architecture | Rel-8 |
| TS 24.173 vj00 | Multimedia Telephony Service and Supplementary Services in IMS | Rel-19 |
| TS 24.404 v1700 | Communication Diversion Services (CDIV) | Rel-7 |
| TS 24.405 v1700 | Conference Service Protocol Description | Rel-7 |
| TS 24.406 v810 | Message Waiting Indication (MWI) Protocol | Rel-8 |
| TS 24.407 v830 | OIP and OIR Simulation Services Protocol | Rel-8 |
| TS 24.408 v1700 | TIP/TIR Services Protocol Specification | Rel-7 |
| TS 24.410 v810 | Protocol Description of HOLD Services | Rel-8 |
| TS 24.416 v1700 | Malicious Call Identification Service | Rel-7 |
| TS 24.423 v850 | PSTN/ISDN Simulation Services XCAP Protocol | Rel-8 |
| TS 24.428 v1700 | Common Basic Communication Procedures | Rel-7 |
| TS 24.447 v800 | Advice Of Charge (AOC) Service Protocol | Rel-8 |
| TS 24.454 v840 | Closed User Group (CUG) Protocol Specification | Rel-8 |
| TS 24.504 v8m0 | Communication Diversion Services Stage 3 | Rel-8 |
| TS 24.505 v810 | Protocol Description of the Conference Service | Rel-8 |
| TS 24.508 v820 | TIP and TIR Service Protocol Description | Rel-8 |
| TS 24.516 v830 | MCID Protocol Specification for NGN | Rel-8 |
| TS 24.523 vj00 | NGCN-NGN Interconnection Scenarios | Rel-19 |
| TS 24.524 vj00 | Hosted Enterprise Services Architecture | Rel-19 |
| TS 24.525 vj00 | Business Trunking Architecture & Requirements | Rel-19 |
| TS 24.528 v830 | Common Basic Communication Procedures for IMS Services | Rel-8 |
| TS 24.607 vj10 | OIP and OIR Supplementary Services Stage 3 | Rel-19 |
| TS 24.623 vj00 | XCAP Protocol for Supplementary Services | Rel-19 |
| TS 24.819 v1700 | IMS Services via Fixed Broadband Access | Rel-7 |
| TR 24.930 vj00 | IMS Session Setup Signalling Flows | Rel-19 |
| TS 29.424 v801 | H.248 Profile for Trunking Media Gateways | Rel-8 |
| TS 29.458 v850 | SIP Transfer of Tariff Info for Charging | Rel-8 |
| TS 29.658 vj00 | SIP Transfer of Tariff Information | Rel-19 |
| TS 32.102 vj00 | Telecom Management Physical Architecture Framework | Rel-19 |
| TS 32.808 v1800 | Common User Profile Storage Framework | Rel-8 |
| TS 33.812 v920 | M2M Remote Subscription Management Security | Rel-9 |