Tech-invite  3GPPspecsRELsGlossariesSIP
21222324252627282931323334353637384‑5x

Top   in Index   Prev   Next

TS 23.503SA2
PCC Framework for the 5G System

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.3.0 (Wzip)2019/12  112 p.
V15.8.0 (PDF)2019/12  85 p.

WI Acronym:  5GS_Ph1
Rapporteur:  Mr. Schramm, MirkoHuawei Technologies Co. Ltd.

The present document defines the Stage 2 Policy and Charging Control (PCC) framework for the 5G System. The PCC framework encompasses the following high level functions:
  • Flow Based Charging for network usage, including charging control and online credit control, for service data flows;
  • Policy control for session management and service data flows (e.g. gating control, QoS control, etc.);
  • Management for access and mobility related policies;
  • Management for UE access selection and PDU Session selection related policies.

It refers to the PCC functionality specified in TS 23.203 for policy and charging control for PDU Sessions, depicting the differences where those exist. For references to TS 23.203 made in this document,
  • the IP-CAN session of TS 23.203 maps to the PDU Session in 5GC.
  • the APN of TS 23.203 maps to DNN in 5GC.
  • the IP-CAN bearer of TS 23.203 maps to the QoS Flow in 5GC.
  • The PCRF of TS 23.203 maps to the PCF in 5GC.
  • The PCEF of TS 23.203 maps to the combination of SMF and UPF in 5GC.
  • The BBF shall be considered as being located in the PCEF.
  • TDF related description does not apply.
  • NBIFOM related description does not apply.

short Table of Contents for  TS 23.503  Word version:   16.3.0

each title links to the equivalent title in the full ToC
Here   Top
1  ScopeWord-p. 7
2  ReferencesWord-p. 7
3  Definitions and abbreviationsWord-p. 8
4  High level architectural requirementsWord-p. 11
4.1  General requirementsWord-p. 11
4.2  Non-session management related policy control requirementsWord-p. 11
4.3  Session management related policy control requirementsWord-p. 12
5  Architecture model and reference pointsWord-p. 17
5.1  GeneralWord-p. 17
5.2  Reference architectureWord-p. 17
5.3  Service-based interfaces and reference pointsWord-p. 20
6  Functional descriptionWord-p. 23
6.1  Overall descriptionWord-p. 23
6.1.1  GeneralWord-p. 23
6.1.1.1  PCF Discovery and SelectionUpWord-p. 23
6.1.1.2  Binding an AF request targeting an UE address to the relevant PCFWord-p. 24
6.1.1.3  Policy decisions based on network analyticsWord-p. 25
6.1.2  Non-session management related policy controlWord-p. 26
6.1.2.1  Access and mobility related policy controlWord-p. 26
6.1.2.2  UE access selection and PDU Session selection related policy (UE policy) controlWord-p. 27
6.1.2.3  Management of packet flow descriptionsWord-p. 30
6.1.2.4  Negotiation for future background data transferWord-p. 32
6.1.2.5  Policy Control Request Triggers relevant for AMFWord-p. 34
6.1.3  Session management related policy controlWord-p. 36
6.1.3.1  GeneralWord-p. 36
6.1.3.2  Binding mechanismWord-p. 36
6.1.3.3  ReportingWord-p. 38
6.1.3.4  Credit managementWord-p. 38
6.1.3.5  Policy Control Request Triggers relevant for SMFWord-p. 39
6.1.3.6  Policy controlWord-p. 45
6.1.3.7  Service (data flow) prioritization and conflict handlingWord-p. 46
6.1.3.8  Termination actionWord-p. 46
6.1.3.9  Handling of packet filters provided to the UE by SMFWord-p. 46
6.1.3.10  IMS emergency session supportWord-p. 46
6.1.3.11  Multimedia Priority Service supportWord-p. 47
6.1.3.12  RedirectionWord-p. 48
6.1.3.13  Resource sharing for different AF sessionsWord-p. 48
6.1.3.14  Traffic steering controlWord-p. 49
6.1.3.15  Resource reservation for services sharing priorityWord-p. 49
6.1.3.16  3GPP PS Data OffWord-p. 50
6.1.3.17  Policy decisions based on spending limitsWord-p. 51
6.1.3.18  Event reporting from the PCFWord-p. 52
6.1.3.19  Mission Critical Services supportWord-p. 54
6.1.3.20  Access Traffic Steering, Switching and Splitting [R16]Word-p. 54
6.1.3.21  QoS Monitoring to assist URLLC Service [R16]Word-p. 55
6.1.3.22  AF session with required QoS [R16]Word-p. 56
6.1.3.23  Support of integration with Time Sensitive Networking [R16]Word-p. 56
6.2  Network functions and entitiesWord-p. 57
6.2.1  Policy Control Function (PCF)Word-p. 57
6.2.1.1  GeneralWord-p. 57
6.2.1.2  Input for PCC decisionsWord-p. 59
6.2.1.3  Policy control subscription information managementWord-p. 62
6.2.1.4  V-PCFWord-p. 65
6.2.1.5  H-PCFWord-p. 65
6.2.1.6  Application specific policy information managementWord-p. 66
6.2.2  Session Management Function (SMF)Word-p. 66
6.2.2.1  GeneralWord-p. 66
6.2.2.2  Service data flow detectionWord-p. 68
6.2.2.3  MeasurementWord-p. 68
6.2.2.4  QoS controlWord-p. 70
6.2.2.5  Application detectionWord-p. 70
6.2.2.6  Traffic steeringWord-p. 71
6.2.2.7  Access Traffic Steering, Switching and Splitting [R16]Word-p. 71
6.2.3  Application Function (AF)Word-p. 71
6.2.4  Unified Data Repository (UDR)Word-p. 72
6.2.5  Charging Function (CHF)Word-p. 72
6.2.6Void
6.2.7  Network Exposure Function (NEF)Word-p. 72
6.2.8  Access and Mobility Management Function (AMF)Word-p. 72
6.2.9  Network Data Analytics Function (NWDAF)Word-p. 72
6.3  Policy and charging control ruleWord-p. 72
6.3.1  GeneralWord-p. 72
6.3.2  Policy and charging control rule operationsWord-p. 83
6.4  PDU Session related policy informationWord-p. 84
6.5  Access and mobility related policy informationWord-p. 89
6.6  UE access selection and PDU Session selection related policy informationWord-p. 90
6.6.1  Access Network Discovery & Selection Policy InformationWord-p. 90
6.6.1.1  GeneralWord-p. 90
6.6.1.2  UE selecting a WLANSP ruleWord-p. 90
6.6.1.3  UE procedure for selecting a WLAN access based on WLANSP rulesWord-p. 91
6.6.2  UE Route Selection Policy informationWord-p. 91
6.6.2.1  Structure DescriptionWord-p. 91
6.6.2.2  Configuration and Provision of URSPWord-p. 95
6.6.2.3  UE procedure for associating applications to PDU Sessions based on URSPWord-p. 95
A  URSP rules exampleWord-p. 97
B  Deployment option to support of BSF and DRA coexistence due to network migrationWord-p. 100
C (Normative)  Support for Application Functions supporting Rx interface [R16]Word-p. 101
D  PCC usage for sponsored data connectivity [R16]Word-p. 103
E  Change historyWord-p. 105

Up   Top