Description
The Intelligent Network (IN) is a service architecture framework defined by 3GPP, based on earlier ITU-T standards, which introduces a fundamental separation between the basic call/service switching functions and the advanced service logic. This separation is achieved through a distributed network architecture where service control is centralized in dedicated network nodes, while call switching remains in the traditional switching nodes. The core principle is the use of standardized triggers, known as Detection Points (DPs), embedded within the Basic Call State Model (BCSM) of a switch or call control function. When a call event matches a configured trigger, the switch suspends call processing and sends a query, via a standardized protocol, to an external entity containing the service logic.
The key architectural components of IN include the Service Switching Point (SSP), which is the switching node (like an MSC or GMSC) equipped with IN capabilities; the Service Control Point (SCP), which is a dedicated server hosting the service logic programs (SLPs) and databases; and the Service Data Point (SDP), which stores subscriber and service-related data. Communication between the SSP and SCP is standardized, primarily using the Intelligent Network Application Protocol (INAP). The service logic on the SCP processes the query, executes the service (e.g., number translation, credit checking), and returns instructions (e.g., connect, play announcement, collect digits) to the SSP to resume and complete the call.
IN's role in the network is to provide a vendor-independent, flexible platform for value-added services. It allows network operators to deploy and manage services centrally, reducing time-to-market and operational costs. The architecture supports services like Customized Applications for Mobile network Enhanced Logic (CAMEL) for mobile networks, which extends IN principles to provide operator-specific services like prepaid, location-based services, and call screening across different network domains and even while roaming. IN forms the foundational concept for later service delivery platforms and the separation of control and user planes seen in modern networks.
Purpose & Motivation
The Intelligent Network was created to solve the critical problem of slow and costly service innovation in traditional telephony networks. Historically, new telecommunication services were tightly integrated into the proprietary software of circuit switches from vendors like Ericsson, Nokia, or Siemens. To introduce a service like freephone (800-number) or televoting, operators had to request vendor-specific software upgrades for each switch, a process that was time-consuming, expensive, and led to vendor lock-in. This stifled competition and delayed the rollout of new revenue-generating features.
The IN architecture addressed these limitations by standardizing the interface between the switching function and the service logic function. This decoupling meant that service logic could be developed and hosted on centralized, standard computing platforms (SCPs) independent of the switch vendors. Operators could now create and modify services rapidly by updating logic and data on the central SCPs, without needing to touch every individual switch in the network. This shift not only accelerated service deployment but also fostered a more open ecosystem where third-party service providers could potentially develop applications for the network.
In the context of 3GPP, IN principles were essential for bringing intelligent services to GSM and later mobile networks. The need for advanced, operator-controlled services that worked seamlessly in home networks and while roaming was a key driver. The CAMEL standard, which is an implementation of IN for mobile networks, was developed to provide services like prepaid roaming, which was commercially crucial but impossible with traditional switch-based logic. Thus, IN provided the architectural blueprint for the programmable, service-aware core network that underpins modern telecommunications.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (36 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, the Intelligent Network (IN) function was updated to support the 5G System (5GS), specifically through the support of 5GS in the Terminating Access Domain Selection (T-ADS) procedure. This integration ensures that IN services can correctly handle session routing and termination for users connected via the new 5G core network. Additionally, modifications were made to align with the 5G-capable IMS, including updates to registration procedures for UEs in Dual Registration mode and clarifications on access network information during IMS calls in 5G dual connectivity scenarios.
- Addition of 5G in the definition of 3GPP system TS 21.905CR0116
- IMS registration procedures for UE in Dual Registration mode TS 23.228CR1188
- Clarification on access network information during IMS call in 5G dual connectivity scenario TS 23.228CR1191
- Support of 5GS in T-ADS TS 23.292CR0246
- Modification on PS Data Off support in IMS Client - TS 23.228 TS 23.228CR1186
In Release 16, the Intelligent Network (IN) function introduced support for RLOS (Redirection of Leg of Service) in the IMS, enhancing service control capabilities. It also added procedures for bearer establishment mode negotiation between network entities. These updates were defined within the 3GPP system framework to improve service interaction and network resource management.
In Release 17, the primary update for the Intelligent Network function was a correction to the HSSGID procedures. This change aimed to ensure the precise handling of user profile data within the 3GPP system core network. The enhancement focused on maintaining the integrity of standardized procedures for accessing the Generic User Profile (GUP) data that affects a user's service experience.
- Correction in HSSGID procedures TS 23.228CR1248
In Release 18, the Intelligent Network (IN) updates included clarifications to the functional description and a correction to the depiction of the P2A2P procedure figure. The release also provided clarification on DC QoS handling within the Application Data Channel setup procedures. These changes refined the existing specifications without introducing new major capabilities or interfaces.
In Release 19, the Intelligent Network (IN) function was enhanced to support UE-Satellite-UE communication within the IMS, including specific call setup, mobility, and early media handling procedures for this scenario. The release also introduced support for third-party user identity information in the IMS and addressed the resolution of Edge Nodes (ENs) within the IMS Application Server Session Management Service. These updates expanded IN capabilities to manage novel satellite-based user equipment communication and more complex identity handling.
- Terminating local BDC establishment without BDC media component in SDP of incoming INVITE request TS 23.228CR1416
- Support of UE-Satellite-UE communication in IMS - Functionality TS 23.228CR1428
- Support of third party user identity information in IMS TS 23.228CR1478
- Address ENs in IMS AS Session Management Service TS 23.228CR1483
- Call setup of UE-Satellite-UE communication in IMS with IMS-AGW on board TS 23.228CR1492
- Procedure for supporting of third party user identity information in IMS TS 23.228CR1524
+ 18 more changes
Explore further
Broader topics and technologies where IN plays a role.
Defining Specifications
3GPP specifications that define or reference IN, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj00 | 3GPP Technical Terms and Definitions | Rel-19 |
| TS 22.038 vj00 | USIM Application Toolkit (USAT) Stage 1 | Rel-19 |
| TS 22.057 vj00 | Mobile Execution Environment (MExE) Stage 1 | Rel-19 |
| TS 22.101 vk00 | Service Principles for PLMNs | Rel-20 |
| TS 22.105 vj00 | Telecommunication Services Framework | Rel-19 |
| TS 22.121 v1400 | Virtual Home Environment Requirements | Rel-5 |
| TS 23.153 vj00 | Out-of-Band Transcoder Control Stage 2 | Rel-19 |
| TS 23.228 vj50 | IMS Stage-2 Service Description | Rel-19 |
| TS 23.292 vj00 | IMS Centralized Services (ICS) Architecture | 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.524 vj00 | Hosted Enterprise Services Architecture | Rel-19 |
| TS 29.078 vj00 | CAMEL Phase 4 CAP Specification | Rel-19 |
| TS 29.278 vj00 | CAMEL Application Part (CAP) for IMS Phase 4 | Rel-19 |
| TS 32.101 vj00 | Management principles and high-level requirements | Rel-19 |
| TS 32.408 vj00 | UMTS/GSM Performance Management Measurements | Rel-19 |
| TS 32.808 v1800 | Common User Profile Storage Framework | Rel-8 |