Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.503  Word version:  19.0.0

Top   Top   None   None   Next
0…   4…   5…   6…   6.1.2…   6.1.2.4…   6.1.3…   6.1.3.6…   6.1.3.18…   6.1.3.21…   6.1.4…   6.2…   6.2.2…   6.3…   6.4…   6.6…   A…   C   D…

 

0  Introductionp. 7

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.
Up

1  Scopep. 8

The present document defines the Stage 2 policy and charging control framework for the 5G System specified in TS 23.501 and TS 23.502.
The policy and charging control 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 of UE policy information.
Interworking with E-UTRAN connected to EPC is described in TS 23.501.
TS 23.502 contains the stage 2 procedures and flows for the policy and charging control framework and it is a companion specification to this specification.
TS 32.255 contains the functional description of the converged offline and online charging functionality for the 5G System.
Up

2  Referencesp. 8

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
  • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
  • For a specific reference, subsequent revisions do not apply.
  • For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 23.501: "Technical Specification Group Services and System Aspects; System Architecture for the 5G System".
[3]
TS 23.502: "Procedures for the 5G System; Stage 2".
[4]
TS 23.203: "Policies and Charging control architecture; Stage 2".
[5]
TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".
[6]
TS 23.179: "Functional architecture and information flows to support mission-critical communication service; Stage 2".
[7]  Void.
[8]
TS 32.240: "Charging management; Charging architecture and principles".
[9]
TS 23.402: "Architecture enhancements for non-3GPP accesses".
[10]
TS 23.161: "Network-Based IP Flow Mobility (NBIFOM); Stage 2".
[11]
TS 23.261: "IP flow mobility and seamless Wireless Local Area Network (WLAN) offload; Stage 2".
[12]
TS 23.167: "3rd Generation Partnership Project; Technical Specification Group Services and Systems Aspects; IP Multimedia Subsystem (IMS) emergency sessions".
[13]
TS 29.507: "Access and Mobility Policy Control Service; Stage 3".
[14]  Void.
[15]
TS 22.011: "Service Accessibility".
[16]
TS 23.221: "Architectural requirements".
[17]
TS 29.551: "5G System; Packet Flow Description Management Service; Stage 3".
[18]
TS 32.421: "Telecommunication management; Subscriber and equipment trace; Trace concepts and requirements".
[19]
TS 24.526: "UE Equipment (UE) policies for 5G System (5GS); Stage 3".
[20]
TS 32.291: "Charging management; 5G system, Charging service; stage 3".
[21]
TS 32.255: "Telecommunication management; Charging management; 5G Data connectivity domain charging; Stage 2".
[22]
TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3".
[23]
TS 23.280: "Common functional architecture to support mission critical services; Stage 2".
[24]
TS 23.288: "Architecture enhancements for 5G System (5GS) to support network data analytics services".
[25]
TS 23.216: "Single Radio Voice Call Continuity (SRVCC); Stage 2".
[26]
TS 23.272: "Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2".
[27]
TS 23.316: "Wireless and wireline convergence access support for the 5G System (5GS)".
[28]
TS 23.287: "Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services".
[29]
TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".
[30]
TS 24.237: "IP Multimedia (IM) Core Network (CN) subsystem IP Multimedia Subsystem (IMS) Service Continuity; Stage 3".
[31]
TS 26.114: "IP Multimedia Subsystem (IMS); Multimedia telephony; Media handling and interaction".
[32]
TS 29.510: "5G System; Network Function Repository Services; Stage 3".
[33]
TS 23.548: "5G System Enhancements for Edge Computing; Stage 2".
[34]
TS 23.304: "Proximity based Services (ProSe) in the 5G System (5GS)".
[35]
TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".
[36]
TS 29.514: "Policy Authorization Service; Stage 3".
[37]
draft-ietf-detnet-yang-00:  "Deterministic Networking (DetNet) YANG Model".
[38]
RFC 5279:  "A Uniform Resource Name (URN) Namespace for the 3rd Generation Partnership Project (3GPP)".
[39]
GSMA PRD NG.135, Version 3.0: "E2E Network Slicing Requirements".
[40]
TS 26.522: "5G Real-time Media Transport Protocol Configurations".
[41]
TS 23.586: "Architectural Enhancements to support Ranging based services and Sidelink Positioning".
[42]
RFC 8939:  "Deterministic Networking (DetNet) Data Plane: IP".
[43]
TS 23.256: "Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2".
[44]
TS 29.512: "Session Management Policy Control Service; Stage 3".
Up

3  Definitions and abbreviationsp. 10

3.1  Definitionsp. 10

For the purposes of the present document, the terms and definitions given in TR 21.905, TS 23.501, TS 23.502 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
Application detection filter:
A logic used to detect packets generated by an application based on extended inspection of these packets, e.g. header and/or payload information, as well as dynamics of packet flows. The logic is entirely internal to a UPF, and is out of scope of this specification.
Application identifier:
An identifier referring to a specific application detection filter.
Application service provider:
A business entity responsible for the application that is being / will be used by a UE, which may be either an AF operator or has an association with the AF operator.
Authorised QoS:
The maximum QoS that is authorised for a service data flow. In the case of an aggregation of multiple service data flows within one QoS Flow, the combination of the "Authorised QoS" information of the individual service data flows is the "Authorised QoS" for the QoS Flow. It contains the 5QI and the data rate.
Binding:
The association between a service data flow and the QoS Flow transporting that service data flow.
Binding mechanism:
The method for creating, modifying and deleting bindings.
Charging control:
The process of associating packets, belonging to a service data flow, to a charging key and applying online charging and/or offline charging, as appropriate.
Charging key:
Information used by the CHF for rating purposes.
Detected application traffic:
An aggregate set of packet flows that are generated by a given application and detected by an application detection filter.
Dynamic PCC Rule:
a PCC rule, for which the definition is provided to the SMF by the PCF.
Gating control:
The process of blocking or allowing packets, belonging to a service data flow / detected application's traffic, to pass through to the UPF.
Monitoring key:
information used by the SMF and PCF for usage monitoring control purposes as a reference to a given set of service data flows or application (s), that all share a common allowed usage on a per UE and DNN basis.
Multi-modal service:
A multi-modal service is a communication service that consists of several data flows that relate to each other and are subject to application coordination. The data flows can transfer different types of data (for example audio, video, positioning, haptic data) and may come from different sources (e.g. a single UE, a single device or multiple devices connected to the single UE, or multiple UEs).
Non-3GPP access network selection information:
It consists of ePDG identifier configuration, N3IWF identification and non-3GPP access node selection information, as defined in clause 6.3.6.1 in TS 23.501.
Non-Seamless Offload:
A capability of the UE to access the data networks via non-3GPP access (e.g. WLAN radio access) outside of a PDU Session.
Operator-controlled service:
A service for which complete PCC rule information, including service data flow filter information, is available in the PCF through configuration and/or dynamic interaction with an AF.
Operating System (OS):
Collection of UE software that provides common services for applications.
Operating System Identifier (OSId):
An identifier identifying the operating system.
OS specific Application Identifier (OSAppId):
An identifier associated with a given application and uniquely identifying the application within the UE for a given operating system.
Packet flow:
A specific user data flow from and/or to the UE.
Packet Flow Description (PFD):
A set of information enabling the detection of application traffic provided by a 3rd party service provider.
PCC decision:
A PCF decision for policy and charging control provided to the SMF (consisting of PCC rules and PDU Session related attributes), a PCF decision for access and mobility related policy control provided to the AMF, a PCF decision for UE policy information provided to the UE or a PCF decision for service related policy (e.g. background data transfer policy) provided to the AF.
PCC rule:
A set of information enabling the detection of a service data flow and providing parameters for policy control and/or charging control and/or other control or support information. The possible information is described in clause 6.3.1.
Policy control:
The process whereby the PCF indicates to the SMF how to control the QoS Flow. Policy control includes QoS control and/or gating control.
Policy Control Request trigger report:
a notification, possibly containing additional information, of an event which occurs that corresponds with a Policy Control Request trigger.
Policy Control Request trigger:
defines a condition when the SMF shall interact again with the PCF.
Policy counter:
A mechanism within the CHF to track spending applicable to a subscriber.
Policy counter identifier:
A reference to a policy counter in the CHF for a subscriber.
Policy counter status:
A label whose values are not standardized and that is associated with a policy counter's value relative to the spending limit(s) (the number of possible policy counter status values for a policy counter is one greater than the number of thresholds associated with that policy counter, i.e. policy counter status values describe the status around the thresholds). This is used to convey information relating to subscriber spending from CHF to PCF. Specific labels are configured jointly in CHF and PCF.
Policy Section:
A Policy Section is identified by a Policy Section Identifier and consists of one or multiple URSP rule(s) or one or multiple WLANSP rule(s) or non-3GPP access network selection information or a combination of WLANSP rule(s) and non-3GPP access network selection information.
Predefined PCC Rule:
a PCC rule that has been provisioned directly into the SMF by the operator.
Redirection:
Redirect the detected service traffic to an application server (e.g. redirect to a top-up / service provisioning page).
Service data flow:
An aggregate set of packet flows carried through the UPF that matches a service data flow template.
Service data flow filter:
A set of packet flow header parameter values/ranges used to identify one or more of the packet flows in the UPF. The possible service data flow filters are defined in clause 6.2.2.2.
Service data flow filter identifier:
A scalar that is unique for a specific service data flow (SDF) filter within a PDU Session.
Service data flow template:
The set of service data flow filters in a PCC Rule or an application identifier in a PCC rule referring to an application detection filter in the SMF or in the UPF, required for defining a service data flow.
Service identifier:
An identifier for a service. The service identifier provides the most detailed identification, specified for flow based charging, of a service data flow. A concrete instance of a service may be identified if additional AF information is available (further details to be found in clause 6.3.1).
Session based service:
An end user service requiring application level signalling, which is separated from service rendering.
Spending limit:
A spending limit is the usage limit of a policy counter (e.g. monetary, volume, duration) that a subscriber is allowed to consume.
Spending limit report:
a notification, containing the current policy counter status generated from the CHF to the PCF.
Subscribed guaranteed bandwidth QoS:
The per subscriber, authorized cumulative guaranteed bandwidth QoS which is provided by the UDR to the PCF.
Subscriber category:
is a means to group the subscribers into different classes, e.g. gold user, silver user and bronze user.
UE Local Configuration:
Information about the association of an application to either a PDU Session or to non-seamless Offload is configured in the Mobile Termination (MT) and in the Terminal Equipment (TE). For example, UE Local Configuration can include operator specific configuration (e.g. operator provided S-NSSAI(s)), or application specific parameters to set up a PDU Session or end user configuration for specific applications.
UE policy information:
Policy information preconfigured in the UE and/or provisioned to the UE for access selection (i.e. ANDSP), PDU Session selection (i.e. URSP), V2X communications (i.e. V2XP), ProSe operations (i.e. ProSeP), A2X communications (i.e. A2XP) and/or Ranging/Sidelink Positioning operations (i.e. RSLPP).
Uplink binding verification:
The network enforcement of terminal compliance with the negotiated uplink traffic mapping to QoS Flows.
User Preferences On Non-3GPP Access Selection:
The list of configuration parameters provided by a layer (e.g. application) above NAS and used by the UE for access network discovery and selection.
VPLMN specific URSP Rules:
A VPLMN specific URSP Rule is applicable when the UE is registered in that VPLMN or its equivalent PLMNs. A VPLMN specific URSP Rule may be used to route traffic to the VPLMN, if the V-PCF provides a local DNN to the AMF, using the PCRT on SMF selection management. A VPLMN specific URSP Rule may be used to route traffic to the Home PLMN if the HPLMN operator wants to provide a different list of RSDs for the same Traffic Descriptor for a VPLMN and for the HPLMN. When provided, the Time and Location criteria in the RSD(s) contain values that are based on agreements with the VPLMN or service parameters that were received from the VPLMN.
Up

3.2  Abbreviationsp. 12

For the purposes of the present document, the abbreviations given in TR 21.905, TS 23.501, TS 23.502, TS 23.316 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
5G DDNMF
5G Direct Discovery Name Management Function
A2XP
A2X Policy
AMBR
Aggregate Maximum Bitrate
ANDSP
Access Network Discovery & Selection Policy
ARP
Allocation and Retention Priority
ASP
Application Service Provider
BDT
Background Data Transfer
BSF
Binding Support Function
CHF
CHarging Function
DCCF
Data Collection Coordination Function
H-PCF
A PCF in the HPLMN
H-UDR
A UDR in the HPLMN
HR-SBO
Home Routed with Session Breakout in VPLMN
MPS
Multimedia Priority Service
NBIFOM
Network-based IP flow mobility
NSWO
Non-Seamless WLAN Offload
NWDAF
Network Data Analytics Function
OAM
Operation Administration and Maintenance
OCS
Online Charging System
PCC
Policy and Charging Control
PDTQ
Planned Data Transfer with QoS
PDUID
ProSe Discovery UE ID
PDV
Packet Delay Variation
PFD
Packet Flow Description
PFDF
Packet Flow Description Function
PRA
Presence Reporting Area
ProSe
Proximity based Services
ProSeP
ProSe Policy
RAN
Radio Access Network
RSLPP
Ranging/Sidelink Positioning Policy
SNPN
Stand-alone Non-Public Network
URSP
UE Route Selection Policy
V2XP
V2X Policy
V-PCF
A PCF in the VPLMN
V-UDR
A UDR in the VPLMN
vSRVCC
video Single Radio Voice Call Continuity
WLANSP
WLAN Selection Policy
Up

Up   Top   ToC