Description
An IP-CAN bearer is a fundamental concept in 3GPP policy and charging control (PCC) architecture, defined in specifications such as TS 23.203, TS 29.212, TS 29.214, and TS 32.251. It represents an IP transmission path within an IP Connectivity Access Network (IP-CAN) that has defined capacity, delay, bit error rate, and other QoS parameters. The term 'bearer' itself is defined in 3GPP TR 21.905 as a transmission path with specific characteristics.
In the context of EPS (Evolved Packet System), an IP-CAN bearer is typically an EPS bearer, which can be a default bearer or a dedicated bearer. The default bearer is established when the UE attaches to the network and provides always-on IP connectivity. Dedicated bearers are established on demand to provide additional QoS treatment for specific services, such as VoIP or video streaming. Each bearer is associated with a set of QoS parameters, including QCI (QoS Class Identifier), GBR (Guaranteed Bit Rate), MBR (Maximum Bit Rate), and ARP (Allocation and Retention Priority).
The IP-CAN bearer is the unit of QoS enforcement in the network. The PCRF (Policy and Charging Rules Function) or PCF (Policy Control Function) makes policy decisions and installs PCC rules in the PCEF (Policy and Charging Enforcement Function) or SMF (Session Management Function). These rules are mapped to IP-CAN bearers, which are then established or modified by the access network (e.g., eNodeB, gNodeB) and the core network (e.g., SGW, PGW, UPF). The bearer's QoS parameters are enforced at various nodes along the path, ensuring that the service receives the appropriate treatment.
From a charging perspective, the IP-CAN bearer is used to correlate charging data. The charging system can generate records per bearer, allowing operators to charge differently based on the QoS and service associated with the bearer. For example, a dedicated bearer for IMS voice may be charged differently from a default bearer used for best-effort internet access.
The IP-CAN bearer concept is access-specific. In 3GPP accesses like LTE and 5G NR, the bearer is implemented as an EPS bearer or a QoS flow, respectively. In non-3GPP accesses (e.g., WLAN, fixed broadband), the bearer may be implemented differently, but the PCC architecture still uses the IP-CAN bearer abstraction to apply policies and charging. This abstraction allows the core network to manage QoS and charging uniformly across heterogeneous access networks.
Overall, the IP-CAN bearer is a crucial element in the 3GPP QoS and policy framework, enabling differentiated treatment of IP flows and providing the foundation for service-level agreements and charging.
Purpose & Motivation
The IP-CAN bearer concept was introduced to provide a standardized way to manage QoS and charging for IP-based services across different access networks. Before its introduction, QoS was often managed at the access level with limited coordination with the core network, making it difficult to offer end-to-end QoS guarantees and to apply consistent charging policies. The IP-CAN bearer abstraction allows the core network to request and enforce QoS on a per-bearer basis, independent of the underlying access technology.
The primary motivation was to enable the deployment of services that require specific QoS, such as VoIP, video conferencing, and interactive gaming, over packet-switched networks. By defining bearers with specific QoS parameters, operators can ensure that these services receive the necessary network resources and are not degraded by best-effort traffic. This is essential for meeting user expectations and for complying with regulatory requirements for emergency services.
Furthermore, the IP-CAN bearer supports flexible charging models. Operators can charge based on the QoS of the bearer, the volume of data, or the duration of the session. This granularity enables innovative pricing plans and helps operators monetize their investments in network infrastructure. The bearer concept also facilitates roaming, as QoS and charging policies can be applied consistently even when the user is visiting a foreign network.
What changed in its specifications
The latest release-to-release comparison of specifications that define IP-CAN bearer. 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-19 adds an EPC function health monitoring reporting procedure to TS 29.212. It also adds a session recovery status AVP and a CnHealthMonitor supported feature.
Full comparison in TS 29.212 →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 10 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-7 specifies IP-CAN bearer handling in PCC: bearer binding, QoS authorization and enforcement, network-initiated bearer establishment or modification, and Gx bearer-level signalling with Bearer-Identifier and Bearer-Operation AVPs.
- “the enforcement of the authorised QoS may, depending on operator policy and network capabilities, lead to network initiated IP-CAN bearer establishment or modification” TS 23.203 v7.14.1
- “binding: The association between a service data flow and the IP-CAN bearer (for GPRS the PDP context) transporting that service data flow.” TS 23.203 v7.14.1
- “a new IP-CAN bearer is being established, the PCEF shall assign a new bearer identifier to this IP-CAN bearer” TS 29.212 v7.16.0
IP-CAN bearer handling changed: TS 23.203 adds a Bearer Binding Function and QoS-rule bearer binding, and TS 29212 revises Gx bearer establishment and termination procedures; TS 32.251 charges per IP-CAN bearer.
- “Bearer binding is the association of the PCC rule and the QoS rule (if applicable) to an IP‑CAN bearer within that IP‑CAN session.” TS 23.203 v8.15.0
- “the PCEF shall instantly start the procedures to terminate the related IP-CAN bearer.” TS 29.212 v8.24.0
- “Every IP-CAN bearer shall be assigned a unique identity number for billing purposes.” TS 32.251 v8.16.0
In Rel-9 the PCC specs add behaviour for IP-CAN bearers: the PCEF/BBERF report PS-to-CS handover termination of an IP-CAN bearer to the PCRF, and a new IP-CAN bearer is established for emergency service.
Compared with Rel-7: intermediate versions are not available, so this change may date from any release since Rel-7.
- “If the PS to CS handover indicator is set for an IP-CAN bearer that is deleted, the PCEF reports termination of transmission resources” TS 23.203 v9.14.0
- “The PCEF shall execute the procedures described in subclause 4.5.2 and subclause 4.5.5.3 to ensure that a new IP-CAN bearer is established for the Emergency service.” TS 29.212 v9.19.0
- “If the IP-CAN bearer termination is caused by the PS to CS handover, the PCEF shall report related PCC rules for this IP-CAN bearer” TS 29.212 v9.19.0
Rel-10 changes IP-CAN bearer handling: charging now covers IFOM and WLAN flow transfer between IP-CAN bearers, PMIP wording is generalised, and Gx/Gxx negotiation of bearer establishment mode is revised.
- “results in PCC Rule(s) removed from the IP-CAN bearer(s) of the source access, leading to 'termination of service data flow'” TS 32.251 v10.15.0
- “For non-3GPP IP‑CANs specified in TS 23.402 [18] negotiation of bearer establishment mode takes place via Gx when GTP is used” TS 23.203 v10.10.0
- “charging for each service data flow, is performed within the IP-CAN bearer charging session of the IP-CAN bearer it belongs to” TS 32.251 v10.15.0
IP-CAN bearer charging is extended to the ePDG, which now opens ePDG-CDRs at IP-CAN bearer activation, and UE SDP handling now also covers a released IP-CAN bearer.
- “The following chargeable events are defined for SGSN, S-GW and ePDG IP-CAN bearer charging:” TS 32.251 v11.13.0
- “If the SDP is affected due to a rejected IP-CAN bearer, a modified IP-CAN bearer or a released IP-CAN bearer then the UE shall:” TS 24.229 v11.31.0
IP-CAN bearer modification triggers now include a change of UE presence in a Presence Reporting Area, and credit pooling extends to TDF sessions.
- “user CSG information change, change of UE presence in a Presence Reporting Area), tariff time change” TS 32.251 v12.13.0
- “Multiple pools of credit shall be allowed per IP‑CAN bearer/TDF session.” TS 23.203 v12.11.0
IP-CAN bearer charging and PCC bearer binding were extended for multi-access/NBIFOM PDN connections and non-IP data, adding new chargeable events and access-based binding of PCC rules to IP-CAN bearers.
- “The bearer binding mechanism in the PCEF shall, in addition to the requirements defined in 6.1.1.4, ensure that a PCC Rule is associated to an IP-CAN bearer belonging to the allowed access.” TS 23.203 v13.10.0
- “Access of a multi-access PDN connection becomes usable: when this event is encountered, new volume counts are started for the IP-CAN bearer of the access that has become usable.” TS 32.251 v13.6.1
- “IP-CAN bearer, when described for PS Charging in S-GW and P-GW, refers to bearer related to IP data and Non-IP data as well.” TS 32.251 v13.6.1
In TS 32.251, IP-CAN bearer modification charging triggers and CDR container conditions now include change of 3GPP PS Data Off status and UE presence in Presence Reporting Area(s).
- “change of UE presence in Presence Reporting Area(s), change of 3GPP PS Data Off status, Serving PLMN Rate Control change, APN Rate Control change” TS 32.251 v14.4.0
- “A change of IP-CAN bearer conditions (e.g. QoS change, SGSN/S-GW/ePDG/TWAG change, user location change” TS 32.251 v14.4.0
IP-CAN bearer handling was extended: charging conditions now include Serving PLMN and APN Rate Control changes, and IP-CAN bearer establishment procedures were added for 5GS, where each IP-CAN bearer is provided by a 5GS QoS flow.
- “When using the 5GS, each IP-CAN bearer is provided by a 5GS QoS flow.” TS 24.229 v15.20.0
- “Serving PLMN Rate Control Change, APN Rate Control Change) shall result in a set of "List of Service Data" containers” TS 32.251 v15.5.0
- “U.2.2.1 Establishment of IP-CAN bearer and P-CSCF discovery” TS 24.229 v15.20.0
UE emergency registration procedures changed: on emerg-reg timer handling and IP-CAN bearer establishment, the UE now retries on another P-CSCF and restarts the emerg-reg-retry timer, stopping emerg-reg timer if none remain.
- “The UE shall retry registration on a different P-CSCF if available and restart the emerg-reg-retry timer.” TS 24.229 v18.11.0
- “if the UE has successfully established an IP-CAN bearer for an emergency session, consider that the attempt to set up the emergency call via the IM CN subsystem has failed” TS 24.229 v18.11.0
Defining Specifications
3GPP specifications that define or reference IP-CAN bearer, 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.212 vk00 | Diameter-Based PCC Reference Points | Rel-20 read |
| TS 29.214 vk00 | Rx Interface for Policy and Charging Control | Rel-20 read |
| TS 32.251 vj00 | PS Domain Charging Management | Rel-19 read |