Description
The Interrogating-Call Session Control Function (I-CSCF) is a fundamental SIP proxy within the 3GPP IP Multimedia Subsystem (IMS) core, defined across numerous specifications starting from 3GPP Release 5. It is located at the edge of an operator's home IMS network. When a User Equipment (UE) registers with the IMS network, the registration request, after passing through the Proxy-CSCF (P-CSCF), reaches the I-CSCF. The I-CSCF's key task is to query the Home Subscriber Server (HSS) via the Cx interface (using Diameter protocol) to determine which Serving-CSCF (S-CSCF) should be assigned to the user or to discover the S-CSCF already assigned.
During registration, the I-CSCF receives the subscriber's public or private user identity. It sends a User Authorization Request (UAR) to the HSS. The HSS responds with the capabilities required for the S-CSCF (S-CSCF capabilities) or, if an S-CSCF is already assigned, its address. The I-CSCF then uses this information to either select an appropriate S-CSCF from a set based on the required capabilities or to forward the registration request directly to the already-assigned S-CSCF. This process ensures load balancing and efficient assignment of S-CSCFs.
For incoming session requests (e.g., an incoming VoIP call), the I-CSCF acts as the entry point into the home network from an external network (like another operator's IMS). The request is routed to the I-CSCF based on DNS lookups of the home network's domain. The I-CSCF then queries the HSS with a Location Information Request (LIR) to obtain the address of the S-CSCF currently serving the called party. Once it receives the S-CSCF address, it proxies the SIP INVITE request to that S-CSCF for further processing and delivery to the UE.
Additionally, the I-CSCF can provide topology hiding functionality. By acting as a single point of contact, it can hide the configuration, capacity, and topology of the internal network (the S-CSCFs) from external networks. It may also have a role in enforcing network security policies at the border of the home network. Its operation is stateless with respect to individual sessions, focusing on routing and HSS interaction.
Purpose & Motivation
The I-CSCF was created as part of the original IMS architecture (3GPP R5) to solve critical routing and scalability problems in a large-scale, multi-operator SIP-based service network. In a pure SIP network without such a function, finding the server responsible for a specific user would be challenging and could expose internal network structure.
Its primary purpose is to provide a discoverable, stable entry point into a home operator's IMS network. This allows other networks to route sessions to a user without needing to know the specific internal server (S-CSCF) managing that user's registration. It decouples the user's publicly routable address (the home network domain) from the internal, possibly changing, server assignment. This enables load balancing across multiple S-CSCFs and allows for S-CSCF failure recovery without impacting external routing.
Furthermore, the I-CSCF, through its interaction with the HSS, centralizes the logic for assigning S-CSCFs based on user service profiles and network capabilities. This allows for optimized resource allocation. It also fulfills a vital security and privacy role by hiding the internal network topology from outside entities, preventing potential attackers from mapping the network or targeting specific internal servers directly. It was a key innovation that made IMS a viable architecture for carrier-grade, interoperable multimedia services.
What changed in its specifications
The latest release-to-release comparison of specifications that define I-CSCF. Each summary describes the whole specification, not only this term.
Added 3GPP2-specific support for presence reference points in Common IMS, referencing X.S0027-004 and X.S0004.
Full comparison in TS 23.141 →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 →Architecture
Where it sits in the network
- Mobile Network → IMS Core → I-CSCF (Session Control)
Technology family
IMS functions · Services › IMS
- R99 OSA-SCS
- Rel-5 AS, BGCF, CSCF, I-CSCF, IM-MGW, IM-SSF, MGCF, MRFC, MRFP, P-CSCF, S-CSCF
- Rel-6 IBCF, IMS-ALG, TrGW
- Rel-7 E-CSCF, IMS-AGW
- Rel-8 MRB, SCC AS
- Rel-9 EATF
- Rel-10 ATCF, ATGW
- I-CSCF split from CSCF
“The CSCF can act as Proxy CSCF (P‑CSCF), Serving CSCF (S‑CSCF), Emergency CSCF (E‑CSCF), or Interrogating CSCF (I‑CSCF).” TS 23.002
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 sourcesDocumented changes in 14 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.
The I-CSCF is specified for the first time, with its proxy role, HSS user registration status and location queries, S-CSCF selection and registration handling.
- “When I-CSCF receives a REGISTER request, the I-CSCF starts the user registration status query procedure to the HSS as specified in 3GPP TS 29.228 [14].” TS 24.229 v5.26.0
- “The I-CSCF shall use a mechanism for determining the Serving-CSCF address based on the required capabilities.” TS 23.228 v5.15.0
- “The architecture shall support multiple I-CSCFs for each operator.” TS 23.228 v5.15.0
I-CSCF behaviour was extended in Rel-6: it selects a new S-CSCF from HSS capabilities excluding previously tried ones, checks trusted domains, and handles PSI subdomains via internal DNS without an HSS query.
- “The newly selected S-CSCF shall not be one of any S-CSCFs selected previously during this same registration procedure” TS 24.229 v6.30.0
- “The I-CSCF shall verify for all requests whether they arrived from a trusted domain or not.” TS 24.229 v6.30.0
- “the I-CSCF resolves the Request-URI by an internal DNS mechanism into the IP address of the AS hosting the PSI” TS 24.229 v6.30.0
I-CSCF behaviour was extended: it verifies the trusted domain of REGISTER requests (403 if untrusted), handles originating requests via the 'orig' Route parameter, and discards P-Profile-Key headers.
- “the I-CSCF shall verify whether or not it has arrived from a trusted domain. If the request has not arrived from a trusted domain” TS 24.229 v7.34.0
- “the I-CSCF shall perform the originating procedures as described in subclause 5.3.2.1A if the topmost Route header of the request contains the "orig" parameter” TS 24.229 v7.34.0
- “The I-CSCF shall discard the P-Profile Key header, if the I-CSCF receives the Profile Key header in a SIP request or response.” TS 24.229 v7.34.0
Rel-8 adds the Ma reference point between I-CSCF and AS, with the I-CSCF handling AS-originated requests as a SIP proxy, and revises its HSS query handling with Tel URI translation and Diameter Proxy Agent support.
- “such requests are forwarded to an I‑CSCF, and the I‑CSCF shall perform regular originating procedures for these requests.” TS 23.228 v8.12.0
- “Prior to an HSS Location Query, the I‑CSCF shall translate a SIP URI representing a telephone number contained in a Request‑URI into the Tel: URI format” TS 23.228 v8.12.0
- “the I‑CSCF acts as a SIP proxy, as shown in Figures 4.3f and 4.3g below.” TS 23.228 v8.12.0
I-CSCF REGISTER and request-handling procedures in TS 24.229 changed: it derives the private identity from the public identity, supports restoration procedures, and applies a configurable timer before re-selecting an unresponsive S-CSCF.
Compared with Rel-7: intermediate versions are not available, so this change may date from any release since Rel-7.
- “the I-CSCF shall derive the private user identity from the public user identity being registered, contained in the To header field” TS 24.229 v9.31.0
- “the REGISTER request did not include an Authorization header field and the I-CSCF supports restoration procedures;” TS 24.229 v9.31.0
- “the I-CSCF can apply a pre-configured timer based on local policy before re-selecting a new S-CSCF.” TS 24.229 v9.31.0
In Rel-10, I-CSCF behaviour in TS 24.229 was extended with an interface to the ATCF, with the P-CSCF selecting either an I-CSCF or an ATCF, and with the S-CSCF restoration wording changed.
- “- the interface between the ATCF and the I-CSCF; and” TS 24.229 v10.29.0
- “a) if the request is not to be forwarded to an ATCF according to local policy select the I-CSCF of the home network;” TS 24.229 v10.29.0
- “If the single Route header field of the request contains the "orig" parameter, the IBCF shall insert the "orig" parameter to the URI of the I-CSCF; and” TS 24.229 v10.29.0
I-CSCF behaviour changed: it can perform S-CSCF load balancing and recovery for registrations, constructs S-CSCF name from returned capabilities, and handles GRUU and unknown-user location queries differently.
- “An I‑CSCF that performs load balancing of S‑CSCFs for initial registration requests shall assign a received registration request to one of the available and suitable S‑CSCFs” TS 23.228 v11.11.0
- “shall determine failure of an S‑CSCF implicitly (i.e. via a timeout) or explicitly (i.e. via a failure message) and shall reroute the registration request to another S‑CSCF” TS 23.228 v11.11.0
- “obtain the public user identity or an identity of the UE that represents the functionality within the UE that performs the role of registrar from the Request-URI” TS 24.229 v11.31.0
I-CSCF procedures in TS 24.229 changed: it may reselect an S-CSCF if the earlier one is unavailable, appends the 'iotl' parameter when required, and replaces (not updates) the tel-URI with NP data.
- “An I-CSCF can reselect S-CSCF if the previously selected S-CSCF is not available.” TS 24.229 v12.27.0
- “if the I-CSCF supports indicating the traffic leg as specified in RFC 7549 [225] and required by local policy, append the "iotl" SIP URI parameter” TS 24.229 v12.27.0
- “then the I-CSCF shall replace the tel-URI in the Request-URI with the obtained NP data” TS 24.229 v12.27.0
I-CSCF now inserts a type 3 orig-ioi and omits term-ioi when forwarding a subsequent request directly to the AS hosting a PSI, and removes P-Charging-Vector from untrusted-domain requests.
- “the I-CSCF shall remove all P-Charging-Vector header fields, if present.” TS 24.229 v13.23.0
I-CSCF behaviour was extended: it may insert a Response-Source header field with fe-id "i-cscf" in failure responses, and charging completeness procedures at the I-CSCF were added.
- “the I-CSCF may insert a Response-Source header field with an "fe" header field parameter constructed with the URN namespace "urn:3gpp:fe"” TS 24.229 v14.21.0
- Charging Completeness: Procedures at the I-CSCF TS 24.229CR5874
- Correction in the Trigger for Charging from I-CSCF TS 32.260CR0388
I-CSCF gained S-CSCF reselection behaviour, adding the "scscf-reselection" URI parameter on failed S-CSCF contact, and RLOS-aware S-CSCF selection from HSS capabilities.
- “the I-CSCF shall select a new S-CSCF, based on the capabilities indicated from the HSS.” TS 24.229 v16.17.0
- “the I-CSCF includes the SIP URI parameter "scscf-reselection" to the Request-URI of the REGISTER request” TS 24.229 v16.17.0
- “The I-CSCF shall use the returned S-CSCF capability information and in addition configured information about S-CSCF support for RLOS to select a S-CSCF.” TS 23.228 v16.7.0
I-CSCF gained new behaviour in Rel-17: priority treatment of transactions by Resource-Priority, and use of Nhss_ims and Nnrf_NFDiscovery service operations instead of Cx for SBI-capable HSS/NRF.
- “the I-CSCF shall give priority over other transactions or dialogs.” TS 24.229 v17.19.0
- “it will apply Nnrf_NFDiscovery service operations instead of Cx procedures mentioned throughout the present document and will interact with an SBI capable NRF.” TS 24.229 v17.19.0
- “An SBI enabled I-CSCF receiving an HSS Group ID during the NRF-based HSS discovery procedure should include the HSS Group ID” TS 23.228 v17.3.0
I-CSCF must now give priority over other registrations to REGISTER requests containing a Resource-Priority header field, when priority is supported.
- “If priority is supported and the I-CSCF received a REGISTER request containing Resource-Priority header field, the I-CSCF shall give priority over other registrations.” TS 24.229 v19.7.0
When the I-CSCF re-selects an S-CSCF, it signals this with the "scscf-reselection" URI parameter in the Request-URI, and the new S-CSCF must then add "imsas-reselection" towards the IMS AS.
- “If the SIP URI parameter of the Request-URI of the REGISTER request from the I-CSCF contains "scscf-reselection"” TS 24.229 v20.1.0
- “I-CSCF re-selects an S-CSCF. The new S-CSCF selects an IMS AS to handle third party REGISTER request” TS 24.229 v20.1.0
- “or "scscf-reselection" indication is received from I-CSCF.” TS 24.229 v20.1.0
Defining Specifications
3GPP specifications that define or reference I-CSCF, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| 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.218 vj00 | IMS Call Model 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.379 vk40 | Mission Critical Push-to-Talk Architecture | 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.701 vc00 | WebRTC Access to IMS Study | Rel-12 read |
| TR 23.794 vh00 | Study on enhanced IMS to 5GC integration | Rel-17 read |
| TS 23.849 vb00 | IMS Roaming Resource Control Study | Rel-11 read |
| TR 23.981 vj00 | IPv4 IMS Interworking and Migration Study | 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.229 vk10 | IMS SIP/SDP Call Control Protocol | Rel-20 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.416 v700 | Malicious Call Identification Service | Rel-7 read |
| TS 24.428 v720 | Common Basic Communication Procedures | Rel-7 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.606 vj00 | MWI Service Protocol Description | 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.841 v600 | Presence Service IP Multimedia Subsystem | Rel-6 read |
| TR 24.930 vj00 | IMS Session Setup Signalling Flows | Rel-19 read |
| TS 28.705 vj00 | IMS NRM IRP Information Service | Rel-19 read |
| TS 29.162 vj00 | IMS-IP Network Interworking | Rel-19 read |
| TS 29.165 vk00 | Inter-IMS Network-to-Network Interface (II-NNI) | Rel-20 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.562 vk10 | HSS Nhss Services for IMS and GBA | Rel-20 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.409 vj00 | IMS Performance Management Measurements | Rel-19 read |
| TS 33.203 vk00 | IMS Security Features and Mechanisms | Rel-20 read |
| TS 33.978 v800 | Early IMS Security Interim Solution | Rel-8 read |
| TS 28.702 vj00 | Core Network NRM IRP Information Service | Rel-19 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 |