Description
The Call Session Control Function (CSCF) is a fundamental element within the 3GPP IP Multimedia Subsystem (IMS) architecture, acting as a SIP (Session Initiation Protocol) server. It is responsible for processing SIP signaling to establish, modify, and terminate multimedia sessions, such as Voice over LTE (VoLTE), video calls, and instant messaging. The CSCF is not a single monolithic entity but is logically separated into distinct functional types: the Proxy-CSCF (P-CSCF), Serving-CSCF (S-CSCF), and Interrogating-CSCF (I-CSCF), each with specific roles in the session control path. The P-CSCF is the first contact point for the User Equipment (UE) within the IMS, handling SIP message compression, security, and acting as a firewall. The S-CSCF is the central node, performing session control, user authentication via the HSS (Home Subscriber Server), and service triggering based on user profiles. The I-CSCF acts as an entry point within an operator's network, querying the HSS to determine the appropriate S-CSCF for a user and providing topology hiding.
Architecturally, the CSCF operates within the IMS control plane, interfacing with other key network functions. It communicates with the HSS via the Cx interface to fetch user authentication data and service profiles. For routing, it interacts with ENUM/DNS servers to resolve SIP addresses and may interface with Application Servers (AS) via the ISC interface to execute value-added services. The CSCF also supports emergency services through the Emergency-CSCF (E-CSCF), which routes emergency calls to the correct Public Safety Answering Point (PSAP). Its design is stateless for scalability, with session state maintained externally when necessary, allowing for load balancing and high availability in large-scale deployments.
In operation, the CSCF processes SIP methods like INVITE, REGISTER, BYE, and SUBSCRIBE. When a user initiates a call, the P-CSCF receives the SIP INVITE, applies policies, and forwards it to the S-CSCF via the I-CSCF if needed. The S-CSCF authenticates the user, checks the service profile, and routes the request to the destination, potentially involving AS for services like call forwarding. It also handles registration procedures, where the S-CSCF authenticates the UE and updates its location in the HSS. The CSCF supports quality of service (QoS) by interacting with the Policy and Charging Rules Function (PCRF) over the Rx interface to authorize media resources. Its role extends to security, enforcing integrity protection and encryption via IPSec for signaling between the UE and P-CSCF, and managing fraud prevention through lawful interception interfaces.
The evolution of CSCF has integrated it with 5G core networks, where it functions alongside the Session Management Function (SMF) and User Plane Function (UPF) to support converged multimedia services. In 5G, the CSCF is part of the 5G IMS, enabling services like Voice over New Radio (VoNR) and ensuring backward compatibility with 4G IMS. It also supports network slicing by being instantiated in slices dedicated to IMS services, allowing customized performance for different use cases. The CSCF's implementation is often virtualized in cloud-native environments, using containers and microservices for agility, which aligns with 3GPP's move towards service-based architecture (SBA) in 5G. This adaptability ensures the CSCF remains critical for real-time communication services across generations.
Purpose & Motivation
The CSCF was created to address the limitations of circuit-switched networks in handling multimedia services over IP. Before IMS, mobile networks primarily used circuit-switched domains for voice, which were inefficient for data-rich services like video and messaging. The rise of internet protocols demanded a standardized way to deliver IP-based multimedia with carrier-grade reliability, leading 3GPP to introduce IMS in Release 5, with CSCF as its core control element. It solves problems such as fragmented service delivery, lack of interoperability between operators, and inefficient session management by providing a unified SIP-based framework.
Historically, pre-IMS approaches relied on proprietary solutions or overlay networks that struggled with scalability and integration. The CSCF enables seamless convergence of voice, video, and data services over all-IP networks, supporting mobility and roaming. It addresses key issues like user authentication across domains, dynamic service triggering, and policy enforcement, which were challenging in earlier systems. By centralizing session control, the CSCF allows operators to deploy new services rapidly, reduce costs through IP infrastructure, and meet evolving consumer demands for rich communication experiences. Its creation was motivated by the need for a standardized, future-proof architecture that could support both legacy and emerging applications, paving the way for services like VoLTE and RCS (Rich Communication Services).
What changed in its specifications
The latest release-to-release comparison of specifications that define CSCF. Each summary describes the whole specification, not only this term.
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 →Added 3GPP2-specific support for presence reference points in Common IMS, referencing X.S0027-004 and X.S0004.
Full comparison in TS 23.141 →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
- CSCF split into P-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
- CSCF split into S-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
- CSCF split into I-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
- CSCF split into E-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 CSCF and its P-, I- and S-CSCF roles, reference points (Cx, ISC, Mg, Mi, Mm, Mr, Mw) and authentication/registration handling are specified for the first time in Rel-5 IMS specifications.
- “The CSCF may take on various roles as used in the IP multimedia subsystem.” TS 23.228 v5.15.0
- “Mw Reference Point between a CSCF and another CSCF.” TS 23.228 v5.15.0
- “Upon receiving the SIP REGISTER the S‑CSCF CSCF shall use an Authentication Vector (AV) for authenticating and agreeing a key with the user.” TS 33.203 v5.12.0
Rel-6 changes CSCF behaviour: the S-CSCF gains Application Server filtering (ISC) and forking based on UE capabilities, and the P-CSCF gains IMS-specific confidentiality and algorithm negotiation.
- “The S‑CSCF shall decide whether an Application Server is required to receive information related to an incoming initial SIP request” TS 23.228 v6.16.0
- “then the S‑CSCF shall use it to generate a target contact set using the matching mechanism described in RFC 3841 [42]” TS 23.228 v6.16.0
- “The P‑CSCF shall decide whether the IMS specific encryption mechanism is used.” TS 33.203 v6.11.0
In Rel-7 the CSCF roles gained new behaviour: ENUM translation failure routing to a BGCF, I-CSCF and S-CSCF transit routing functions, and P-CSCF subscription to IMS signalling connectivity status.
- “the S‑CSCF may be provisioned as the contact point within an operator's network for transit IMS scenarios and may perform transit routing functions” TS 23.228 v7.16.0
- “Prior to an HSS Location Query, the I‑CSCF shall translate an E.164 address contained in a Request‑URI” TS 23.228 v7.16.0
- “The P‑CSCF may subscribe to notifications of the status of the IMS Signalling connectivity after successful initial user IMS Registration.” TS 23.228 v7.16.0
In Rel-8, S-CSCF/I-CSCF/P-CSCF behaviour was extended: multiple-service filter/ordering for ASs, AS-originated requests via I-CSCF, E.164/ENUM translation policy, and P-CSCF access network type handling.
- “It shall be possible to include a service indication in the filter information, which is used to identify services and the order that they are executed” TS 23.228 v8.12.0
- “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
- “the P‑CSCF may insert in any SIP message (request or response) the access network type currently used by the UE” TS 23.228 v8.12.0
In Rel-9 IMS architecture, the IBCF can act as network entry point instead of the I-CSCF, and the CSCF roles gain new reference-point and AS-originated request handling.
- “the IBCF acts as an entry point for this network (instead of the I‑CSCF). In this case the IBCF and the I‑CSCF can be co-located” TS 23.228 v9.4.0
- “The Mx reference point allows S‑CSCF/I‑CSCF/P‑CSCF/MSC Server enhanced for ICS or MSC Server enhanced for SRVCC to communicate with an IBCF” TS 23.228 v9.4.0
- “Requests originating sessions on behalf of a user are forwarded to the S‑CSCF serving the user” TS 23.228 v9.4.0
CSCF behaviour was updated: P-CSCF now handles priority sessions and MPS termination, S-CSCF forwards the INVITE with the Service User's priority level, and P-CSCF security handling of REGISTER over NASS/TLS was revised.
- “When the INVITE message includes priority indication, the S-CSCF forwards the INVITE, including the Service User's priority level if available.” TS 23.228 v10.9.0
- “If the P-CSCF determines that the termination is for an MPS session, the P-CSCF derives the session information and invokes dynamic policy” TS 23.228 v10.9.0
- “then the P‑CSCF shall perform the steps required for NBA as well as the steps required for SIP Digest without TLS” TS 33.203 v10.3.0
Rel-11 adds CSCF behaviour: I-CSCF/S-CSCF load balancing, S-CSCF limits on simultaneous registrations, P-CSCF retrieval of user location and time zone via PCC, and S-CSCF reference location insertion.
- “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
- “The S‑CSCF shall reject the registration if the number of registered contact addresses for a Public User Identity from the same UE exceeds the limit” TS 23.228 v11.11.0
- “The P‑CSCF can retrieve the user location and/or UE Time Zone information using PCC mechanisms” TS 23.228 v11.11.0
P-CSCF retrieval of user location and UE Time Zone via PCC mechanisms is extended to cover TWAN access, and I-CSCF handling now forwards to a Transit Function when the IP-PBX has no HSS subscription.
- “NOTE 4: For the 3GPP access networks and for TWAN access (as defined in clause 16 of TS 23.402 [82])” TS 23.228 v12.11.0
- “If there is no subscription in the HSS, the I‑CSCF forwards the request to a Transit Function” TS 23.228 v12.11.0
In the LBO roaming model with the P-CSCF in the VPLMN, the home network now determines the UE's serving PLMN from the P-CSCF location and network identifier during initial IMS registration.
- “the home network determines the serving PLMN of the UE from the location of the P-CSCF during initial IMS Registration” TS 23.228 v14.7.0
P-CSCF interaction for policy and QoS authorization and for location/time zone retrieval is extended from PCRF only to PCRF/PCF, and 5G PCC (TS 23.503) and non-3GPP accesses are now covered.
- “forwards it to the PCRF/PCF. The PCRF/PCF shall use the received information to calculate the proper authorization.” TS 23.228 v15.5.0
- “For the 3GPP and non-3GPP accesses, the P‑CSCF can retrieve user location information and/or UE Time Zone” TS 32.260 v15.2.0
P-CSCF may now derive access network type and subscribe to IMS signalling connectivity status via 5GC PCF specifications (TS 23.503, TS 29.514), not only the EPC PCC specifications.
- “or in TS 23.503 [95] and in TS 29.514 [96].” TS 23.228 v16.7.0
- “(see TS 23.203 [54] and TS 23.503 [95] for more details)” TS 23.228 v16.7.0
S-CSCF authentication behaviour changed: it now offers AKAv2-SHA-256 preferred over AKAv1-MD5 and verifies SIP Digest responses using stored SHA-256 and MD5 hashes (H(A1)_256, H(A1)).
- “The S‑CSCF shall offer both "AKAv2-SHA-256" [65] and "AKAv1-MD5" [17] starting with "AKAv2-SHA-256" as most preferred.” TS 33.203 v17.1.0
- “the S-CSCF selects the stored hashes (i.e., H(A1)_256 and H(A1)) based on the received algorithm selected by UE” TS 33.203 v17.1.0
TS 23.228 in Rel-18 adds an N70/Cx/Dx reference point between the CSCF and HSS, and removes text on determining the serving PLMN from the P-CSCF location during IMS registration in LBO roaming.
- “N70/Cx/Dx: Reference point between the CSCF and HSS.” TS 23.228 v18.12.0
- “the home network determines the serving PLMN of the UE from the location of the P-CSCF during initial IMS Registration” TS 23.228 v18.12.0
S-CSCF now receives the MPS for Messaging indication from the HSS, and P-CSCF uses it to request PCC bearer modification and to set Resource-Priority in MESSAGE requests.
- “In addition to the names/addresses information, security information and the MPS for Messaging indication may also be sent for use within the S‑CSCF.” TS 23.228 v19.8.0
- “The P‑CSCF may send an MPS for Messaging indication to the PCRF/PCF using PCC procedures” TS 23.228 v19.8.0
- “P-CSCF#1 sets the Resource-Priority information in the MESSAGE to a value appropriate for MPS.” TS 23.228 v19.8.0
Defining Specifications
3GPP specifications that define or reference CSCF, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj20 | 3GPP Terminology and Definitions | 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.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.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.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 |
| TS 23.806 v700 | Voice Call Continuity between CS and IMS | 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.141 vj00 | Presence Service Protocol Details | Rel-19 read |
| TS 24.147 vj00 | IMS Conferencing Protocol Details | 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.206 v750 | Voice Call Continuity Between CS and IMS | Rel-7 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.371 vj00 | WebRTC IMS Client Access Specification | Rel-19 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.429 v700 | Explicit Communication Transfer (ECT) Service Specification | Rel-7 read |
| TS 24.454 v840 | Closed User Group (CUG) Protocol Specification | Rel-8 read |
| TS 24.504 v8m0 | Communication Diversion (CDIV) Protocol Specification | Rel-8 read |
| TS 24.508 v820 | TIP and TIR Service Protocol Description | Rel-8 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.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.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.629 vj00 | Explicit Communication Transfer (ECT) Protocol | Rel-19 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 26.114 vk11 | IMS Multimedia Telephony Client | Rel-20 read |
| TR 26.914 vj00 | Multimedia Telephony over IP Optimization | Rel-19 read |
| TR 26.944 vj00 | QoE, ESQoS and SQoS metrics for 3G multimedia services | Rel-19 read |
| TR 26.998 vj00 | 5G AR/MR Glasses Integration Study | 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.328 vk00 | IMS Sh, Dh and Ph Interface Procedures | Rel-20 read |
| TS 29.421 v810 | IMS Interworking with External IP Networks | Rel-8 read |
| TS 29.433 v811 | TISPAN endorsement of 3GPP Cx and Dx interfaces | Rel-8 read |
| TS 29.562 vk10 | HSS Nhss Services for IMS and GBA | Rel-20 read |
| TS 29.866 vj00 | IMS Disaster Prevention & Restoration Enhancement | Rel-19 read |
| TS 31.829 vd00 | ISIM-ME Interface Conformance Requirements | Rel-13 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.250 vj00 | Circuit Switched Offline Charging | Rel-19 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.409 vj00 | IMS Performance Management Measurements | Rel-19 read |
| TS 32.422 vk30 | Trace, MDT and UE Measurement Control | Rel-20 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.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.978 v800 | Early IMS Security Interim Solution | Rel-8 read |