Description
An IP-CAN session is a central concept in the 3GPP policy and charging control (PCC) architecture, defined in specifications such as TS 23.203, TS 29.061, TS 29.212, TS 29.213, TS 29.214, TS 29.215, and TS 32.251. It represents the association between a User Equipment (UE) and an IP network (PDN), identified by the UE's IP address(es) and UE identity information, if available. The IP-CAN session is the context within which one or more IP-CAN bearers are established, and it exists as long as the UE's IP addresses are assigned and announced to the IP network.
In the PCC architecture, the IP-CAN session is the point of policy control and charging for a UE's connectivity to a PDN. When a UE attaches to the network and establishes a PDN connection, an IP-CAN session is created. The PCRF (Policy and Charging Rules Function) or PCF (Policy Control Function) maintains session state and makes policy decisions based on subscription information, network policies, and service requirements. These decisions are communicated to the PCEF (Policy and Charging Enforcement Function) or SMF (Session Management Function) via the Gx or N7 interface.
The IP-CAN session can incorporate multiple IP-CAN bearers. The support for multiple bearers per session is IP-CAN specific; for example, in EPS, a PDN connection can have multiple EPS bearers (default and dedicated). The session aggregates the charging and policy information for all bearers, allowing the network to manage the overall connectivity for the UE. The session is identified by the UE's IP address(es) and, if available, additional UE identity information such as IMSI or access line identifier.
For fixed broadband access, the IP-CAN session can also be identified primarily by an IP address(es). In this context, the term UE corresponds to the device accessing the services (e.g., residential gateway, 3GPP UE, or fixed end-device), the PDN identifies the IP network where the device gets IP connectivity, and the UE identity information may be the IMSI, user-name, or access line identifier. In a Fixed Broadband Access, an IP-CAN session corresponds to a Subscriber IP Session as defined in TR-146.
The IP-CAN session is also used for charging purposes. The charging system generates charging data records (CDRs) per IP-CAN session, which can be correlated with the bearers within the session. This allows operators to charge based on the session's characteristics, such as the PDN connected to, the QoS of the bearers, and the volume of data transferred.
Overall, the IP-CAN session is a key abstraction that enables the core network to manage policy, QoS, and charging for a UE's IP connectivity in a technology-agnostic manner, supporting both 3GPP and non-3GPP access networks.
Purpose & Motivation
The IP-CAN session concept was introduced to provide a unified framework for managing policy, QoS, and charging for IP connectivity across different access technologies. Prior to its introduction, policy and charging were often handled at the access level, leading to fragmentation and inconsistent treatment of services. The IP-CAN session abstraction allows the core network to maintain a single context for a UE's IP connectivity, regardless of whether the access is via LTE, 5G, WLAN, or fixed broadband.
The primary motivation was to enable the deployment of advanced services that require end-to-end policy control and charging, such as IMS-based voice and video, and to support roaming and interworking between different networks. By defining a session that encompasses all bearers for a UE's PDN connection, the network can apply consistent policies and generate accurate charging records. This is essential for operators to monetize their services and to ensure a good user experience.
Furthermore, the IP-CAN session supports the evolution towards all-IP networks and the Internet of Things (IoT), where a vast number of devices require connectivity with varying QoS and charging requirements. The session concept scales to handle multiple devices and sessions, and it provides the necessary hooks for network slicing and edge computing in 5G and beyond.
What changed in its specifications
The latest release-to-release comparison of specifications that define IP-CAN session. Each summary describes the whole specification, not only this term.
NB-IoT/eMTC support for Non-Terrestrial Networks: adds QCI characteristic for satellite access, note on GEO/LEO delays, and PCRF policy control for satellite PDN connections.
Full comparison in TS 23.203 →Rel-17 added NR RedCap as a 3GPP RAT type identifier for the core network and extended the headset interface tests of UE.
Full comparison in TS 29.061 →Technology family
Sessions, bearers and QoS · Core Network
- R96 PDP context
- R99 ARP, GBR, Radio Access Bearer (RAB), TFT, UMTS bearer service
- Rel-7 IP-CAN bearer, IP-CAN session, QCI
- Rel-8 APN-AMBR, Dedicated EPS bearer, Default EPS bearer, EPS bearer, EPS Bearer Identity (EBI), UE-AMBR
- Rel-9 Evolved ARP
- Rel-15 5QI, GFBR, MFBR, PDU Session, QoS Flow, Session-AMBR
- Rel-16 MA PDU Session
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 11 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 IP-CAN session is defined for the first time as the association between a UE and a PDN, incorporating one or more IP-CAN bearers and existing while the UE IP address is established.
- “An IP-CAN session exists as long as the UE IP address is established and announced to the IP network.” TS 23.203 v7.14.1
- “An IP-CAN session incorporates one or more IP-CAN bearers.” TS 29.212 v7.16.0
The IP-CAN session definition was revised to a UE identified by IPv4 address and/or IPv6 prefix plus a PDN ID (e.g. an APN), and session handling in Gx procedures was updated.
- “The association between a UE represented by an IPv4 and/or an IPv6 address, and UE identity information, if available, and a PDN represented by a PDN ID” TS 23.203 v8.15.0
- “the PCEF shall inform the PCRF about the mobility protocol tunnelling header of the service data flows at IP-CAN session establishment” TS 29.212 v8.24.0
- “Each IP-CAN session is handled in a separate Gateway Control Session.” TS 29.213 v8.19.0
Rel-9 adds usage monitoring per IP-CAN session and an emergency-only IP-CAN session with restricted traffic and an inactivity timer, with matching Gx procedures and AVPs.
- “It shall be possible to apply usage monitoring for the accumulated usage of network resources on a per IP-CAN session and user basis.” TS 23.203 v9.14.0
- “An IP-CAN session serving an IMS emergency session shall not serve any other service and shall not be converted to/from any IP-CAN session serving other services.” TS 23.203 v9.14.0
- “the PCEF shall initiate an inactivity timer if all PCC Rules with a QCI other than the default bearer QCI or the QCI used for IMS signalling were removed” TS 29.212 v9.19.0
The IP-CAN session definition was revised and IP flow mobility added, so one IP-CAN session may be associated with multiple Gateway Control Sessions and IP flow mobility routing rules are provided at establishment or modification.
- “An IP‑CAN session exists as long as UE IP addresses/prefix are established and announced to the IP network.” TS 23.203 v10.10.0
- “When flow mobility applies for the IP-CAN Session, one IP‑CAN session may be associated to multiple Gateway Control Sessions with separate BBRFs.” TS 23.203 v10.10.0
- “The PCEF may install, modify, and remove IP flow mobility routing rules at IP-CAN session modification.” TS 29.212 v10.17.0
Rel-11 adds the TDF session as an association with an IP-CAN session and restricts session binding to one and only one IP-CAN session, plus IP-CAN session-specific parameter exchange with the TDF.
- “Session binding is the association of the AF session information to one and only one IP‑CAN session.” TS 23.203 v11.15.0
- “TDF session: An association between an IP-CAN session and the assigned TDF for the purpose of application detection and control.” TS 23.203 v11.15.0
- “Request and delivery of IP‑CAN session specific parameters between the PCRF and the TDF.” TS 23.203 v11.15.0
Rel-12 specifies IP-CAN session establishment rules for fixed broadband access (routed, bridged and PPP pass-through RG), where a session corresponds to a Subscriber IP Session, and adds charging and enforcement in either PCEF or TDF per IP-CAN session.
- “An IP-CAN session shall be established on the IP-Edge per IPv4 address and/or IPv6 address or IPv6 prefix known in the IP-Edge.” TS 23.203 v12.11.0
- “In a Fixed Broadband Access an IP-CAN session corresponds to a Subscriber IP Session defined in TR-146 [36].” TS 23.203 v12.11.0
- “This specification supports charging and enforcement being done in either the PCEF or the TDF for a certain IP-CAN session, but not both” TS 23.203 v12.11.0
Rel-13 extends the IP-CAN session to multi-access operation with NBIFOM, with per-access PCC rule association, and adds usage monitoring exclusion of individual flows from IP-CAN session level monitoring.
- “In a multi access IP-CAN session, every PCC Rule is associated to one allowed access within the IP-CAN session.” TS 23.203 v13.10.0
- “Multiple IP-CAN types (3GPP EPS and Non 3GPP EPS) may be simultaneously associated with the same IP-CAN session.” TS 23.203 v13.10.0
- “it shall be possible to exclude an individual SDF or a group of service data flow(s) from the usage monitoring for all traffic of this IP-CAN session” TS 23.203 v13.10.0
IP-CAN session handling changed: default EPS bearer QoS can now be changed over time for the session, PS Data Off status is signalled at IP-CAN session establishment, and Presence Reporting Area handling is provisioned per IP-CAN session.
- “If the PCEF is informed that the 3GPP PS Data Off status of the UE is set to active for the IP-CAN session establishment” TS 29.212 v14.11.0
- “the PCEF shall apply the corresponding subsequent default EPS bearer QoS as the new authorized default EPS bearer QoS for the IP-CAN session” TS 23.203 v14.6.0
- Correction in IP-CAN session termination procedure TS 29.213CR0702
Rel-15 adds IP-CAN session handling for UE suspend state: the PCEF reports PCC rules not enforced while the UE is suspended, and the PCRF subscribes to the resume event and defers modifications.
- “the PCEF shall indicate to the PCRF that the PCC Rules were not enforced with the reason that the UE is in suspend state” TS 23.203 v15.5.0
- “the PCRF shall not initiate any IP-CAN Session Modification procedure, except if it is initiated for the PCC rule removal only” TS 29.212 v15.9.0
- “When the IP-CAN session is being established, if the PCEF supports the Extended-BW-NR feature and for bandwidth values higher than 2^32-1 bps” TS 29.212 v15.9.0
Restricted Local Operator Services (RLOS) IP-CAN sessions are now provided by the serving network, and RLOS sessions are excluded from PCEF teardown after a PCRF restart.
- “Emergency, RLOS and eMPS sessions should not be torn down.” TS 29.212 v16.4.0
- “Restricted Local Operator Services (i.e. IP-CAN session for the Restricted Local Operator Services)” TS 23.203 v16.3.0
The PCRF/PCEF/AF now handle reporting of the UDP/IP Header Removal & Restoration capability of the IP-CAN session, with a new event trigger and capability reporting at session establishment.
- “the PCRF shall provision the event trigger to report UDP/IP Header Removal & Restoration capability of the IP-CAN session to the PCEF” TS 23.203 v20.1.0
- “optionally, the UDP/IP Header Removal & Restoration capability of the IP-CAN session” TS 23.203 v20.1.0
- “The PCEF reports when the UDP/IP Header Removal & Restoration capability of the IP-CAN session has changed.” TS 23.203 v20.1.0
Defining Specifications
3GPP specifications that define or reference IP-CAN session, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.203 vk10 | Policy and Charging Control Architecture | Rel-20 read |
| TS 29.061 vk10 | Packet Domain Interworking Requirements | Rel-20 read |
| TS 29.212 vk00 | Diameter-Based PCC Reference Points | Rel-20 read |
| TS 29.213 vj30 | PCC Procedures and Flows | Rel-19 read |
| TS 29.214 vk00 | Rx Interface for Policy and Charging Control | Rel-20 read |
| TS 29.215 vj00 | S9 Reference Point Stage 3 Specification | Rel-19 read |
| TS 32.251 vj00 | PS Domain Charging Management | Rel-19 read |