Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Core Network

P-CSCF

Proxy Call Session Control Function

Also written as: PCSCF

Core Network →

P-CSCF is the first IMS contact point for a User Equipment, acting as a SIP proxy that forwards messages and enforces policies to establish, manage, and terminate multimedia sessions.

Introduced
Rel-5
Where
Services › IMS
Specifications
69 specs
Also in
Core Network
P-CSCF Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The Proxy Call Session Control Function (P-CSCF) is a fundamental node within the 3GPP-defined IP Multimedia Subsystem (IMS) architecture, which delivers multimedia services over IP networks. It is the first IMS entity with which the User Equipment (UE) interacts after obtaining IP connectivity, typically via LTE or 5G access. Functionally, the P-CSCF operates as a Session Initiation Protocol (SIP) proxy and user agent, but its role extends far beyond simple message routing. It resides in the user's home network or a visited network and serves as the secure gateway for all SIP signaling between the UE and the rest of the IMS core, which includes the Interrogating-CSCF (I-CSCF) and Serving-CSCF (S-CSCF).

From a protocol perspective, the P-CSCF handles the entire lifecycle of SIP dialogues. When a UE initiates a SIP registration or session request (like a voice or video call), it sends the SIP message to the discovered P-CSCF address. The P-CSCF validates the message format, applies network policies—such as checking that the requested service is allowed—and then routes the request toward the appropriate I-CSCF or S-CSCF based on the user's profile and domain. Crucially, it maintains a security association with the UE using IPsec or TLS, ensuring the integrity and confidentiality of SIP signaling. It also performs SIP message compression (SigComp) to optimize transmission over wireless links and manages emergency session routing.

A key architectural responsibility of the P-CSCF is its interaction with the Policy and Charging Control (PCC) framework. It acts as the Policy and Charging Enforcement Function (PCEF) for the IMS media plane or interfaces with a separate PCEF (like the PGW in 4G or UPF in 5G). During session establishment, the P-CSCF extracts the media parameters (e.g., codec types, IP addresses, ports) from the SIP Session Description Protocol (SDP) and communicates them to the Policy and Charging Rules Function (PCRF) via the Rx interface. This allows the network to authorize the appropriate Quality of Service (QoS) resources (e.g., dedicated bearers for VoLTE) and apply charging rules before the media flow begins. The P-CSCF also generates charging data records (CDRs) for offline billing. Its deployment can be colocated with other functions in modern cloud-native implementations, but its logical role as the UE's entry point and policy enforcer remains constant across 4G and 5G.

Purpose & Motivation

The P-CSCF was created as part of the IMS architecture, first standardized in 3GPP Release 5, to enable the delivery of rich, real-time multimedia services over packet-switched IP networks. Prior to IMS, circuit-switched networks handled voice and SMS, while packet-switched networks like GPRS were primarily for best-effort data. IMS aimed to converge these by offering voice, video, and messaging over IP with carrier-grade reliability, security, and charging. The P-CSCF solves the problem of securely connecting millions of potentially mobile UEs to this complex service core, acting as a trusted intermediary that shields the internal IMS network from direct exposure to the access network.

Historically, without a dedicated proxy function at the edge, managing SIP signaling from diverse UEs across different access types (e.g., LTE, Wi-Fi) would be chaotic and insecure. The P-CSCF provides a standardized first contact point that handles access-specific adaptations, such as IP address translation and signaling compression. It also enforces network policies uniformly, preventing unauthorized service use and ensuring that media flows receive the necessary QoS. This was particularly critical for the launch of Voice over LTE (VoLTE), where the P-CSCF ensures that voice packets are prioritized through the EPS bearer system.

The evolution toward 5G and network slicing further underscores the P-CSCF's importance. In 5G Core (5GC), the P-CSCF remains a key component for IMS-based telephony (VoNR) and multimedia services. It interacts with the 5G Policy Control Function (PCF) via the N5 interface, analogous to the Rx interface with PCRF in 4G, to orchestrate session-aware QoS. Its design allows operators to deploy IMS independently of the underlying access technology, future-proofing investments and enabling seamless service continuity as networks evolve from 4G to 5G and beyond.

What changed in its specifications

The latest release-to-release comparison of specifications that define P-CSCF. Each summary describes the whole specification, not only this term.

TS 23.141Rel-7 → Rel-8

Added 3GPP2-specific support for presence reference points in Common IMS, referencing X.S0027-004 and X.S0004.

Full comparison in TS 23.141 →
TS 23.218Rel-18 → Rel-19

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

Technology family

IMS functions · Services › IMS

  1. R99 OSA-SCS
  2. Rel-5 AS, BGCF, CSCF, I-CSCF, IM-MGW, IM-SSF, MGCF, MRFC, MRFP, P-CSCF, S-CSCF
  3. Rel-6 IBCF, IMS-ALG, TrGW
  4. Rel-7 E-CSCF, IMS-AGW
  5. Rel-8 MRB, SCC AS
  6. Rel-9 EATF
  7. Rel-10 ATCF, ATGW
  • P-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
  • P-CSCF used together with IMS-AGW
    “The P-CSCF A allocates an IMS-AGW on the ground as default. P-CSCF A interacts with IMS-AGW on the ground to allocate transport resources based on the mechanism defined in TS 23.334 [74].” TS 23.228
  • P-CSCF coexists with ATCF
    “The ATCF may be co-located with one of the existing functional entities within the serving network (i.e. P-CSCF or IBCF).” TS 23.237

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 sources

Documented 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 introduced

P-CSCF is specified for the first time in Rel-5: first IMS contact point acting as a SIP proxy (with limited UA role), handling registration, header checks and security.

  • “The Proxy-CSCF (P-CSCF) is the first contact point within the IM CN subsystem.” TS 23.228 v5.15.0
  • “The P-CSCF shall provide the proxy role, with the exceptions and additional capabilities to SIP as described in subclause 5.2” TS 24.229 v5.26.0
  • “When the P-CSCF receives a REGISTER request from the UE, the P-CSCF shall:” TS 24.229 v5.26.0
Rel-6 specification text

P-CSCF behaviour was extended in Rel-6: new IPsec response-port handling, Security-Server/Security-Client registration procedures, reg-event NOTIFY handling, and P-CSCF discovery generalised from GPRS to any IP-CAN.

  • “the P-CSCF shall use the ports used for establishing the IPsec security association to forward responses” TS 24.229 v6.30.0
  • “Upon receipt of a NOTIFY request on the dialog which was generated during subscription to the reg event package of the user” TS 24.229 v6.30.0
  • “Alternatively, the P‑CSCF discovery may be performed after the IP connectivity has been established.” TS 23.228 v6.16.0
Rel-7 specification text

P-CSCF behaviour was extended in Rel-7: it controls IMS-ALG/NAT handling, interacts with the PCRF over Rx/Gx, receives unprotected REGISTERs on default ports and selects among IMS flows.

  • “the P-CSCF may include the IMS-ALG function that is defined in Annex I of this specification.” TS 23.228 v7.16.0
  • “The P-CSCF shall be prepared to receive only the unprotected REGISTER requests on the SIP default port values” TS 24.229 v7.34.0
  • “the P-CSCF selects the flow from the IMS flow set denoted by the IMS flow token” TS 24.229 v7.34.0
Rel-8 specification text

P-CSCF gained new responsibilities in Rel-8: inserting and ensuring access network type information in SIP messages, subscribing to access network type changes, and storing IBCF names; IMS Restoration behaviour was also specified.

  • “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
  • “The P‑CSCF shall cancel any active subscription e.g. to notifications of the status of the IMS Signalling connectivity” TS 23.228 v8.12.0
  • “the P-CSCF shall return a specific error response to the UE to trigger a new registration” TS 23.380 v8.5.0
Rel-9 1 CR

P-CSCF/IMS-ALG gained gate control and media policing over the Iq interface to the IMS Access Gateway, and P-CSCF restoration procedures after P-CSCF failure were specified.

Compared with Rel-7: intermediate versions are not available, so this change may date from any release since Rel-7.

  • “The IMS-ALG function in the P-CSCF shall be able to request opening and closing of gates on the IMS Access Gateway.” TS 23.228 v9.4.0
  • “The P-CSCF sends Rx Push (see 3GPP TS 29.214 [7]) to provide the PCRF with the P-CSCF selected by the UE.” TS 23.380 v9.6.0
  • P-CSCF includes access-network-charging-info in reliable response TS 24.229CR5657
Rel-10 specification text

P-CSCF gained new behaviour in Rel-10: MPS priority handling and policy interaction with the PCRF, ATCF-aware REGISTER forwarding with retry, combined NASS-IMS bundled/SIP digest authentication, and ECN disallowance.

  • “The P-CSCF shall control the priority of IMS based MPS sessions, using PCC procedures.” TS 23.228 v10.9.0
  • “the P-CSCF shall repeat the actions of this bullet with a different exit point or a different ATCF.” TS 24.229 v10.29.0
  • “The P-CSCF shall be able to disallow the negotiation of ECN during SDP offer/answer exchanges” TS 23.228 v10.9.0
Rel-11 1 CR

P-CSCF behaviour changed: it now inserts Feature-Caps parameters (TRF, MRB), derives a Geographical Identifier from CGI/SAI, discards non-REGISTER requests lacking an IP association, and handles P-CSCF failure recovery with S5 PMIP.

  • “the P-CSCF may insert into the request a Feature-Caps header field with the "+g.3gpp.trf" header field parameter as specified in RFC 6809 [190].” TS 24.229 v11.31.0
  • “the P-CSCF shall discard this SIP request, i.e. it shall not send back a 100 Trying SIP response to the UE” TS 24.229 v11.31.0
  • P-CSCF failure procedure with S5 PMIP TS 23.380CR0037
Rel-12 specification text

Rel-12 adds P-CSCF behaviour: HSS-based and PCRF-based P-CSCF restoration procedures, 504 error responses for S-CSCF failures, NAT keep-alive handling, and static-mode business trunking support.

  • “The P-CSCF can inform the UE about S-CSCF failures in a 504 (Server Time-out) response using the IMS XML body defined in subclause 7.6” TS 24.229 v12.27.0
  • “this mechanism shall be executed when a terminating request cannot be serviced due to a P-CSCF failure” TS 23.380 v12.5.0
  • “the P-CSCF shall add a value to the parameter, to indicate that it is willing to receive keep-alives associated with the registration” TS 24.229 v12.27.0
Rel-13 specification text

P-CSCF gained new behaviour in Rel-13: resource sharing and priority sharing indications to the PCRF, Geographical Identifier and access-info handling, and HSS-based restoration extended to WLAN.

  • “the P-CSCF shall ensure that the UE can only receive the media flow for one session at a time by closing the gates” TS 23.228 v13.9.0
  • “the P-CSCF shall convey to the PCRF the priority sharing indicator as described in TS 23.203 [54].” TS 23.228 v13.9.0
  • “The HSS-based P-CSCF restoration mechanism for WLAN extends the HSS-based P-CSCF restoration mechanism (specified for 3GPP accesses in subclause 5.4)” TS 23.380 v13.6.0
Rel-14 specification text

P-CSCF gained new behaviours in Rel-14: acquiring and forwarding the serving PLMN ID in SIP REGISTER, SIP signalling logging with the logme parameter, and handling of resource sharing and priority sharing.

  • “where P-CSCF requests the PCRF to report the PLMN identifier where the UE is currently located.” TS 23.228 v14.7.0
  • “the P-CSCF shall treat the dialog as one for which logging of signalling is in progress and start to log SIP signalling” TS 24.229 v14.21.0
  • “the P-CSCF shall convey to the PCRF the priority sharing indicator and, when available, the pre-emption control information” TS 23.228 v14.7.0
Rel-15 1 CR

P-CSCF gained 5GS support in Rel-15: PCF-based and UDM/HSS-based P-CSCF restoration, Rx Push to the PCF, and updated emergency request handling.

  • “The alternative P-CSCF shall send an Rx AAR message with the P-CSCF restoration indication to the associated PCF.” TS 23.380 v15.4.0
  • “If the P-CSCF detects that a UE uses a PDU session for emergency services for a non-emergency REGISTER request, the P-CSCF shall reject that request” TS 24.229 v15.20.0
  • PCF Based P-CSCF Restoration TS 24.229CR6262
Rel-16 specification text

In Rel-16 the P-CSCF gained NRF registration for SMF-based discovery, N5/Npcf_PolicyAuthorization interaction with the PCF, ANBR support indication, and extended restoration procedures.

  • “When the P-CSCF is configured to support SMF discovery of the P-CSCF, P-CSCF shall register in NRF their capabilities” TS 23.228 v16.7.0
  • “the P-CSCF shall include the "g.3gpp.anbr" feature-capability indicator in the Feature-Caps header field of the 200 (OK) response” TS 24.229 v16.17.0
  • “it will apply Npcf_PolicyAuthorization service operations (defined in 3GPP TS 29.514[273]) instead of Rx procedures” TS 24.229 v16.17.0
Rel-17 1 CR

P-CSCF behaviour was extended in Rel-17: failed P-CSCF address is passed during restoration, in-call access update and eps-fallback reporting were added, and MPS priority handling was revised.

  • “If the P-CSCF supports the in-call access update procedure and if a received a response to the INVITE request contains a Feature-Caps header field” TS 24.229 v17.19.0
  • “The alternative P-CSCF includes, if received, the address of the failed P-CSCF in the request.” TS 23.380 v17.3.0
  • P-CSCF to provide eps-fallback parameter TS 24.229CR6537
Rel-18 specification text

P-CSCF gained new procedures to detect UE access or PLMN change and send a MESSAGE request to the S-CSCF, including in-call access update, and to adjust encryption for the new PLMN.

  • “If the P-CSCF is aware that the UE has changed PLMN, and the P-CSCF has a policy to require a different encryption” TS 24.229 v18.11.0
  • “if the P-CSCF supports the in-call access update procedure, has received the g.3gpp.in-call-access-update feature-capability indicator during session set-up” TS 24.229 v18.11.0
  • “3. P-CSCF sends SIP MESSAGE with new PLMN ID to S-CSCF.” TS 23.228 v18.12.0
Rel-19 specification text

P-CSCF gained new behaviour in Rel-19: MPS for Messaging priority handling and Resource-Priority insertion, optimized media routing activation based on satellite identifiers, and EPC/5GC failure detection with P-CSCF restoration triggering.

  • “the P-CSCF shall insert a Resource-Priority header field with the namespace and priority value from the reg-Event <rph> element” TS 24.229 v19.7.0
  • “the P-CSCF activates ground fallback routing by selecting an IMS-AGW on the ground.” TS 24.229 v19.7.0
  • “P-CSCF triggers existing "HSS-based P-CSCF restoration for 3GPP access" mechanism described in clause 5.4 by sending a 503 Service Unavailable response” TS 23.380 v19.1.0
Rel-20 specification text

P-CSCF gains new behaviour in Rel-20: acting as a specific B2BUA to reduce signalling, with simplified SDP call setup and NB-IoT (GEO) optimized SIP timers.

  • “To reduce the signalling, the P-CSCF shall support acting as a specific B2BUA.” TS 23.228 v20.1.0
  • “The P-CSCF sends a SIP UPDATE request with an updated SDP only upon receiving the PCRF notification” TS 23.228 v20.1.0
  • “The P-CSCF interacts with the PCRF to retrieve the MT UE's access network information.” TS 23.228 v20.1.0

Defining Specifications

3GPP specifications that define or reference P-CSCF, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
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
TS 23.894 va00 IMS Local Breakout and Optimal Media Routing Rel-10 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.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.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.405 v700 Conference Service Protocol Description 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.504 v8m0 Communication Diversion (CDIV) Protocol Specification Rel-8 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.604 vj00 Communications Diversion (CDIV) Protocol Spec Rel-19 read
TS 24.605 vj00 3GPP CONF Service Protocol Specification Rel-19 read
TS 24.606 vj00 MWI Service Protocol Description Rel-19 read
TS 24.628 vj00 Common Basic Communication Procedures in IMS 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
TR 24.980 vg00 MCPTT IMS Profile for Gm Reference Point Rel-16 read
TR 26.924 vj00 MTSI QoS Improvement Study Rel-19 read
TS 27.060 vj00 TE-MT Interworking for Packet Domain Rel-19 read
TS 28.705 vj00 IMS NRM IRP Information Service Rel-19 read
TS 29.061 vk10 Packet Domain Interworking Requirements Rel-20 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.214 vk00 Rx Interface for Policy and Charging Control Rel-20 read
TS 29.228 vk00 IMS Cx and Dx Interface Procedures Rel-20 read
TS 29.513 vk10 5G PCC Signalling Flows Rel-20 read
TS 29.514 vk10 Policy Authorization Service Rel-20 read
TS 29.562 vk10 HSS Nhss Services for IMS and GBA Rel-20 read
TS 29.806 vc10 P-CSCF Restoration Analysis & Solutions Rel-12 read
TS 29.826 vd10 P-CSCF Restoration Enhancements for WLAN Rel-13 read
TS 29.827 vg00 Policy and Charging for Volume Based Charging Rel-16 read
TR 29.949 vj00 VoLTE IMS Roaming Architecture & Procedures 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.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.127 vj80 Lawful Interception Architecture Rel-19 read
TS 33.141 vj00 Security for Presence Service (Ut reference point) Rel-19 read
TS 33.871 vc00 Security for WebRTC IMS Client Access Rel-12 read
TS 34.229 vj30 IP Multimedia Call Control Protocol Rel-19 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