Tech-invite  3GPPspecsRELsGlossariesSIP

Top   in Index   Prev   Next

TS 23.203SA2
PCC – Policy and Charging Control Architecture

use "3GPP‑Page" to get the Word version
use "ETSI‑search" to get the PDF version
for a better overview, the Table of Contents (ToC) is reproduced
V16.2.0 (Wzip)2019/12  267 p.
V15.5.0 (PDF)  2019/09  268 p.
V14.6.0  2018/06  259 p.
V13.10.0  2016/12  248 p.
V12.11.0  2015/12  225 p.
V11.15.0  2014/12  186 p.
V10.10.0  2014/12  134 p.
V9.14.0  2014/12  127 p.
V8.15.0  2014/12  118 p.
V7.14.1  2012/07  78 p.

Rapporteur:  Mr. Bertenyi, BalazsNokia Networks

3GPP 23.203 - Architecture reference model for Policy and Charging Control
Here are some links in support of this figure:
Clause 5GwGwnGxGxxGyaGzaNpNtNuRxREST‑RxUdS9S9aS15SdStSy
Sp is not specified yet

This TS specifies the overall stage 2 level functionality for Policy and Charging Control that encompasses the following high level functions for IP-CANs (e.g. GPRS, I-WLAN, Fixed Broadband, etc.):
  • Flow Based Charging for network usage, including charging control and online credit control, for service data flows and application traffic;
  • Policy control (e.g. gating control, QoS control, QoS signalling, etc.).
The present document specifies the Policy and Charging Control functionality for Evolved 3GPP Packet Switched domain, including both 3GPP accesses GERAN/UTRAN/E-UTRAN and Non-3GPP accesses, according to TS 23.401 and TS 23.402.
The present document specifies functionality for unicast bearers. Broadcast and multicast bearers, such as MBMS contexts for GPRS, are out of scope for the present release of this document.

short Table of Contents for  TS 23.203  Word version:   16.2.0

each title links to the equivalent title in the full ToC
Here   Top
1  ScopeWord-p. 14
2  ReferencesWord-p. 14
3  Definitions, symbols and abbreviationsWord-p. 16
4  High level requirementsWord-p. 20
5  Architecture model and reference pointsWord-p. 28
6  Functional descriptionWord-p. 35
6.1  Overall descriptionUpWord-p. 35
6.2  Functional entitiesWord-p. 69
6.3  Policy and charging control ruleWord-p. 97
6.4  IP CAN bearer and IP CAN session related policy informationWord-p. 105
6.4a  TDF session related policy information [R11]Word-p. 107
6.4b  APN related policy information [R13]Word-p. 108
6.5  Quality of Service Control rule [R8]Word-p. 110
6.6  Usage Monitoring Control specific information [R9]Word-p. 112
6.7  S2c based IP flow mobility Routing rule [R10]Word-p. 113
6.8  Application Detection and Control Rule [R11]Word-p. 114
6.9  Policy decisions based on spending limits [R11]Word-p. 120
6.11  Traffic Steering Control Information [R13]Word-p. 121
6.12  NBIFOM Routing rule [R13]Word-p. 122
7  PCC Procedures and flowsWord-p. 123
A (Normative)  Access specific aspects (3GPP)Word-p. 161
A.1  GPRSWord-p. 161
A.4  3GPP Accesses (GERAN/UTRAN/E-UTRAN) - GTP-based EPC [R8]Word-p. 172
A.5  3GPP Accesses (GERAN/UTRAN/E-UTRAN) - PMIP-based EPC [R8]Word-p. 180
D  Access specific aspects (Non-3GPP)Word-p. 187
D.1  DOCSIS IP CANWord-p. 187
D.2  WiMAX IP CANWord-p. 191
G  PCC rule precedence configurationWord-p. 196
H (Normative)  Access specific aspects (EPC-based Non-3GPP) [R8]Word-p. 197
J  Standardized QCI characteristics - rationale and principles [R8]Word-p. 201
K  Limited PCC Deployment [R8]Word-p. 202
L (Normative)  Limited PCC Deployment [R8]Word-p. 202
M  Handling of UE or network responsibility for the resource management of services [R8]Word-p. 203
N  PCC usage for sponsored data connectivity [R10]Word-p. 204
P (Normative)  Fixed Broadband Access Interworking with EPC [R11]Word-p. 206
Q  How to achieve Usage Monitoring via the OCS [R12]Word-p. 235
R  Disabling/re-enabling Usage Monitoring for a PCC/ADC rule [R12]Word-p. 236
S (Normative)  Fixed Broadband Access [R12]Word-p. 237
T  How to accumulate PCC/ADC Rule usage in multiple monitoring groups [R12]Word-p. 256
U (Normative)  Policy and charging control in the downlink direction for traffic marked with DSCP by the TDF [R13]Word-p. 257
V  Policy Control for Remote UEs behind a ProSe UE-to-Network Relay UE [R13]Word-p. 258
X  Encrypted traffic detection by using domain name matching [R14]Word-p. 260
Y  Change historyWord-p. 261

Up   Top