Description
The Serving Call Session Control Function (S-CSCF) is the central processing node within the IP Multimedia Subsystem (IMS) architecture. It acts as a SIP registrar and SIP proxy server, handling all session control for IMS-registered users within its assigned home network. Upon user registration, the S-CSCF downloads the user's service profile from the Home Subscriber Server (HSS) and uses this information to apply service logic, trigger application servers, and manage the user's service sessions. It is responsible for routing SIP messages, interacting with other CSCFs (P-CSCF, I-CSCF), and enforcing the policies of the network operator.
Architecturally, the S-CSCF is a stateful SIP server that maintains the registration state and session state for its assigned users. It performs session establishment, modification, and termination procedures. A key component of its operation is the Initial Filter Criteria (iFC), which are part of the user's service profile. The iFC contains a set of rules that determine when and to which Application Servers (AS) SIP messages should be forwarded for value-added service execution, such as call forwarding, voicemail, or presence services.
Its role extends beyond basic SIP routing; it is integral to security, performing authentication and authorization of users in conjunction with the HSS. It also handles charging functions by generating Charging Data Records (CDRs) and interfaces with the Policy and Charging Rules Function (PCRF) for policy control related to bearer resources. The S-CSCF is a critical element for enabling rich communication services, ensuring interoperability, and providing a platform for service innovation in 4G, 5G, and fixed networks.
Purpose & Motivation
The S-CSCF was created to provide a standardized, SIP-based core for delivering multimedia services over IP networks, independent of the underlying access technology (e.g., LTE, 5G NR, Wi-Fi). Prior to IMS, telecom services were tightly coupled with circuit-switched networks, making service innovation slow and access-dependent. The S-CSCF solves this by centralizing session control, separating the service layer from the connectivity layer, and enabling the convergence of voice, video, and messaging over IP.
Its creation was motivated by the need for a flexible, scalable architecture to support the vision of 'all-IP' networks. It addresses the limitations of previous siloed service platforms by providing a common service delivery engine. This allows operators to deploy services like Voice over LTE (VoLTE), Rich Communication Services (RCS), and eventually Voice over New Radio (VoNR) efficiently, using a single core network that can serve multiple access types and facilitate interoperability between different operators' networks.
What changed in its specifications
The latest release-to-release comparison of specifications that define S-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 →Rel-5 added IMS provisioning with new network element definitions (HSS, IMS, ISC, MRF). It also added OSA enhancements covering HE-VASP support, policy management, presence, and removing User Profile Management.
Full comparison in TS 23.127 →Architecture
Where it sits in the network
- Mobile Network → IMS Core → S-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
- S-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
- S-CSCF used together with AS
“The Serving‑CSCF to AS interface is used to provide services residing in an AS.” TS 23.002
- S-CSCF used together with BGCF
“This reference point allows the Serving CSCF to forward the session signalling to the Breakout Gateway Control Function for the purpose of interworking to the circuit switched networks.” 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 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 specifies the S-CSCF for the first time: SIP registrar and proxy/UA roles in 24.229, plus application server service control over ISC and S-CSCF assignment in 23.228.
- “The S-CSCF shall act as the SIP registrar for all UAs of the IM CN subsystem with public user identities.” TS 24.229 v5.26.0
- “The S-CSCF shall decide whether an Application Server is required to receive information related to an incoming SIP session request” TS 23.228 v5.15.0
- “a S-CSCF shall be assigned to serve the UE.” TS 23.228 v5.15.0
In Rel-6 the S-CSCF gained new requirements: selection of a new S-CSCF excluding earlier ones, registration handling and forking across multiple contact addresses, and filtering for ISC interaction with application servers.
- “The S‑CSCF shall support forking so that an incoming SIP request addressed to a Public User Identity is proxied to multiple registered contact addresses.” TS 23.228 v6.16.0
- “For an incoming SIP request, the S‑CSCF shall perform any filtering for ISC interaction before performing other routing procedures towards the terminating user” TS 23.228 v6.16.0
- The S-CSCF name needs to be checked always in MAR TS 29.228CR061
Rel-7 changed S-CSCF behaviour: it assigns and returns GRUU sets, supports Outbound, handles Path headers and implicit registration updates, and S-CSCF reselection was removed.
- “the S-CSCF shall assign a unique P‑GRUU and a new and unique T‑GRUU to the combination of Public User Identity and Instance ID.” TS 23.228 v7.16.0
- “When supporting Outbound, the S-CSCF should be responsible for indicating to the UE that Outbound procedures are supported.” TS 23.228 v7.16.0
- S-CSCF reselection removal TS 29.228CR0285
S-CSCF behaviour was extended in Rel-8: it supplies AS with info for ordered multi-service execution, handles ENUM/DNS translation of E.164 and SIP URIs per operator policy, and supports NP parameters.
- “The S‑CSCF shall be able to supply the AS with information to allow it to execute multiple services in order within a single SIP transaction.” TS 23.228 v8.12.0
- “network operator policy shall dictate whether the procedure shall be carried out for all the domains of the SIP URI where those domains belong to the home network” TS 23.228 v8.12.0
- IMS Restoration after an S-CSCF failure TS 29.228CR0393
TS 24.229 adds S-CSCF rules for choosing the authentication mechanism from the REGISTER request and HSS data, covering NASS-IMS bundled, GPRS-IMS-Bundled, SIP digest and TLS cases, and for I-CSCF re-selection of the S-CSCF.
Compared with Rel-7: intermediate versions are not available, so this change may date from any release since Rel-7.
- “The S-CSCF shall determine which authentication mechanism applies based on the contents of the REGISTER request and the authentication mechanism assigned in the HSS:” TS 24.229 v9.31.0
- “the S-CSCF shall perform the initial registration procedures with GPRS-IMS-Bundled authentication described in subclause 5.4.1.2.1E;” TS 24.229 v9.31.0
- “the S-CSCF performs the network initiated deregistration procedure for the previously registered public user identities and the associated old contact address” TS 24.229 v9.31.0
S-CSCF registration handling was extended: it selects the authentication mechanism (SIP digest, NASS-IMS bundled, GPRS-IMS bundled) by access network type and supported schemes, and it forwards MPS priority information.
- “the S-CSCF sends an authentication request for the user to the HSS indicating that the authentication scheme is unknown” TS 24.229 v10.29.0
- “If the S-CSCF receives the priority information of the MPS subscribed-UE as a part of user profile from the HSS, the S-CSCF provides the priority information to the P-CSCF” TS 23.228 v10.9.0
- “During registration process, the S-CSCF shall provide policy information, if available, for a Public User Identity from the HSS to the P-CSCF and/or UE.” TS 23.228 v10.9.0
S-CSCF behaviour changed in Rel-11: it rejects REGISTER with 403 when the maximum simultaneous registration flows are reached, and it can subscribe to the load-control event package.
- “the S-CSCF shall reject the REGISTER by generating a 403 (Forbidden) response.” TS 24.229 v11.31.0
- “Based on operator policy, the S-CSCF may subscribe to the load-control event package with one or more target SIP entities.” TS 24.229 v11.31.0
- “The S-CSCF shall also reject the registration from separate UEs if the allowed number of simultaneous registrations” TS 23.228 v11.11.0
S-CSCF gained new behaviour in Rel-12: initiating HSS- and PCRF-based P-CSCF restoration, and handling AKAv2 authentication and WebRTC WAF/WWSF token checks in REGISTER processing.
- “When the neighbouring entity is the S-CSCF, the S-CSCF can in this case initiate the P-CSCF restoration.” TS 24.229 v12.27.0
- “the S-CSCF shall check whether the WAF or WWSF is not barred” TS 24.229 v12.27.0
- “the S-CSCF shall consider this P-CSCF as being in a working state.” TS 24.229 v12.27.0
S-CSCF may reduce registration duration based on local policy criteria such as the authentication mechanism, and stores the AS IP address to send third-party REGISTER towards it.
- “The local policy can take into account specific criteria such as the used authentication mechanism” TS 24.229 v13.23.0
- “the S-CSCF shall send SIP REGISTER request towards the IP address associated with the corresponding registered public user identity” TS 24.229 v13.23.0
S-CSCF procedures in TS 24.229 changed: it may insert a Response-Source header in failure responses, adds fe-addr to P-Charging-Vector, handles logging stop triggers, and forwards to a stored AS IP address.
- “based on local policy, the S-CSCF shall add an "fe-addr" element of the "fe-identifier" header field parameter to the P-Charging-Vector header field” TS 24.229 v14.21.0
- “depending on operator policy, the S-CSCF may insert a Response-Source header field with an "fe" header field parameter” TS 24.229 v14.21.0
- S-CSCF storing AS IP address TS 24.229CR5867
In Rel-15 the S-CSCF gained new responsibilities: initiating UDM/HSS or PCF/PCRF based P-CSCF restoration and attesting the originating user's identity, inserting Origination-Id, based on local policy.
- “When the neighbouring entity is the S-CSCF, the S-CSCF can in this case initiate the P-CSCF restoration.” TS 24.229 v15.20.0
- “the S-CSCF shall based on local policy perform attestation of the user identity by inserting:” TS 24.229 v15.20.0
- S-CSCF performing attestation TS 24.229CR6091
In Rel-16 the S-CSCF gained RLOS support, I-CSCF-driven S-CSCF reselection with the "scscf-reselection" parameter, unregistered-user temporary records and Nhss_ims use, plus restoration and selection corrections.
- “S-CSCF supports RLOS as specified in TS 23.228 [7] and the REGISTER request contains a "+g.3gpp.rlos" Contact header field parameter” TS 24.229 v16.17.0
- “the I-CSCF includes the SIP URI parameter "scscf-reselection" to the Request-URI of the request.” TS 24.229 v16.17.0
- S-CSCF restoration after registration timer expiry TS 23.380CR0110
S-CSCF digest authentication now follows RFC 7616/8760, creating a WWW-Authenticate header per supported algorithm in order of preference, replacing the RFC 2617-based MD5 handling.
- “for each supported digest algorithm the S-CSCF shall create a WWW-Authenticate header field as defined in RFC 7616 [286] and RFC 8760 [287]” TS 24.229 v17.19.0
- “The S-CSCF shall include the WWW-Authenticate header fields to the 401 (Unauthorized) response in order of preference, starting with the most preferred algorithm.” TS 24.229 v17.19.0
- S-CSCF reselection in eIMS TS 29.562CR0059
S-CSCF gains new behaviour in Rel-18: it advertises IMS data channel capability via Feature-Caps in REGISTER 200 OK, and handles access update and re-authentication requests triggered by P-CSCF or regulatory requirements.
- “the S-CSCF includes a Feature-Caps header field indicating its data channel capability in the 200 OK response to the initial and any subsequent REGISTER request” TS 23.228 v18.12.0
- “In addition to the functions defined in clause 4.6.3, the S-CSCF is enhanced to support the following functionalities:” TS 23.228 v18.12.0
- “the P-CSCF shall send a MESSAGE request towards the S-CSCF populated as follows:” TS 24.229 v18.11.0
S-CSCF gains new Rel-19 behaviour: it signs and verifies RCD info via an AS, may extend registration timers, and includes Feature-Caps for data channel multiplexing in REGISTER responses.
- “the S-CSCF sends a signingRequest to the AS for signing over the Ms reference point, as specified in annex V.” TS 24.229 v19.7.0
- “the S-CSCF includes a Feature-Caps header field indicating its capability of supporting data channel multiplexing in the 200 OK response” TS 23.228 v19.8.0
- “the S-CSCF may perform signature verification of the RCD information or RCD URL of the originating subscriber for terminating requests” TS 23.228 v19.8.0
S-CSCF gains new behaviour: when it or an I-CSCF reselects, it includes the "imsas-reselection" URI parameter in third-party REGISTER and in requests to a newly selected IMS AS, and handles optimised SIP message support.
- “the S-CSCF shall include the SIP URI parameter "imsas-reselection" to the Request-URI of the third-party REGISTER request.” TS 24.229 v20.1.0
- “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
- “it includes the indication of support of optimised SIP messages in the third-party REGISTER request towards the IMS-AS.” TS 23.228 v20.1.0
Defining Specifications
3GPP specifications that define or reference S-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.127 v610 | Virtual Home Environment Stage 2 Specification | Rel-6 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.198 v900 | Open Service Access (OSA) Stage 2 | Rel-9 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.976 vj00 | Push Service Requirements Analysis | 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.259 vj00 | Personal Network Management (PNM) Protocol Details | Rel-19 read |
| TS 24.404 v750 | Communication Diversion Services Stage 3 | Rel-7 read |
| TS 24.406 v810 | Message Waiting Indication (MWI) Protocol | 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.428 v720 | Common Basic Communication Procedures | 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.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.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.528 v830 | Common Basic Communication Procedures for IMS Services | 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.608 vj00 | 3GPP TS 24608: TIP/TIR Services 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.628 vj00 | Common Basic Communication Procedures in IMS | Rel-19 read |
| TS 24.647 vj00 | Advice of Charge (AOC) service protocol | 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 |
| 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 28.705 vj00 | IMS NRM IRP Information Service | 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.562 vk10 | HSS Nhss Services for IMS and GBA | Rel-20 read |
| TS 29.826 vd10 | P-CSCF Restoration Enhancements for WLAN | Rel-13 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.409 vj00 | IMS Performance Management Measurements | Rel-19 read |
| TS 32.808 v800 | Common Profile Storage Framework for User Data | Rel-8 read |
| TS 33.107 vj00 | Lawful Interception Architecture & Functions | Rel-19 read |
| TS 33.127 vj80 | Lawful Interception Architecture | Rel-19 read |
| TS 33.804 vc00 | Non-UICC SSO using SIP Digest credentials | Rel-12 read |
| TS 33.871 vc00 | Security for WebRTC IMS Client Access | Rel-12 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 |