Content for TS 29.212 Word version: 18.1.0
1 Scope p. 16
The present document provides the stage 3 specification of the Gx, Gxx and Sd reference points for the present release. The present document also provides the Diameter variant of St reference point for the present release. The functional requirements and the stage 2 specifications of the Gx, Gxx, Sd and St reference points are contained in TS 23.203. The Gx reference point lies between the Policy and Charging Rule Function and the Policy and Charging Enforcement Function. The Gxx reference point lies between the Policy and Charging Rule Function and the Bearer Binding and Event Reporting Function. The Sd reference point lies between the Policy and Charging Rule Function and the Traffic Detection Function. The St reference point lies between the Policy and Charging Rule Function and the Traffic Steering Support Function.
Whenever it is possible the present document specifies the requirements for the protocol by reference to specifications produced by the IETF within the scope of Diameter. Where this is not possible, extensions to Diameter are defined within the present document.
2 References p. 16
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 and/or edition number or version number) 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 29.210: "Charging Rule Provisioning over Gx Interface".
[3] Void.
[4] Void.
[5]
RFC 3588: "Diameter Base Protocol".
[6] Void.
[7]
TS 23.203: "Policy Control and Charging architecture".
[8]
TS 29.213: "Policy and charging control signalling flows and Quality of Service (QoS) parameter mapping".
[9] Void.
[10]
TS 29.214: "Policy and Charging Control over Rx reference point".
[11]
TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN)".
[12]
RFC 4005: "Diameter Network Access Server Application".
[13]
TS 24.008: "Mobile radio interface Layer 3 specification".
[14]
TS 29.229: "Cx and Dx interfaces based on Diameter protocol; Protocol details".
[15]
RFC 3162: "Radius and Ipv6".
[16]
TS 32.295: "Telecommunication management; Charging management; Charging Data Record (CDR) transfer".
[17]
TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".
[18]
TS 29.060: "General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface".
[19]
TS 32.299: "Telecommunication management; Charging management; Diameter charging applications ".
[20]
3GPP2 X.S0011-E: "cdma2000 Wireless IP Network Standard".
[21]
TS 32.240: "Telecommunication management; Charging management; Charging architecture and principles".
[22]
TS 29.274: "3GPP Evolved Packet System. Evolved GPRS Tunnelling Protocol for EPS (GTPv2)".
[23]
TS 23.402: "Architecture enhancements for non-3GPP accesses".
[24]
3GPP2 X.S0057-B: "E-UTRAN - eHRPD Connectivity and Interworking: Core Network Aspects".
[25]
TS 23.003: "Numbering, addressing and identification".
[26]
TS 29.272: "3GPP Evolved Packet System. Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol".
[27]
TS 32.422: "Telecommunication management; Subscriber and equipment trace; Trace control and configuration management".
[28]
TS 29.275: "Proxy Mobile Ipv6 (PMIPv6) based Mobility and Tunnelling Protocols; Stage 3".
[29]
TS 43.318: "Generic access to the A/Gb interface; Stage 2".
[30]
3GPP2 X.S0062-0: "PCC for cdma2000 1x and HRPD Networks ".
[31]
TS 23.228: "IP multimedia subsystem; Stage 2".
[32]
TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access.
[33]
TS 23.380: "IMS Restoration Procedures".
[34]
Void.
[35]
TS 23.261: "IP flow mobility and seamless Wireless Local Area Network (WLAN) offload; Stage 2".
[36]
RFC 3046: "DHCP Relay Agent Information Option".
[37]
ETSI TS 283 034 v2.2.0: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Network Attachment Sub-System (NASS); e4 interface based on the DIAMETER protocol".
[38] Void.
[39] Void.
[40]
TS 23.216: "Single Radio Voice Call Continuity (SRVCC); Stage 2".
[41]
TS 23.107: "Quality of Service (QoS) concept and architecture".
[42]
TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet".
[43]
TS 23.007: "Restoration Procedures".
[44]
Broadband Forum TR-134: "Policy Control Framework ".
[45]
Broadband Forum TR-124 Issue 3: "Functional Requirements for Broadband Residential Gateway Devices ".
[46]
Broadband Forum TR-146: "Internet Protocol (IP) Sessions".
[47]
Broadband Forum TR-300: "Nodal Requirements for Converged Policy Management".
[48]
TS 29.273: "3GPP EPS AAA interfaces".
[49]
RFC 7683: "Diameter Overload Indication Conveyance".
[50]
TS 23.468: "Group Services and System Aspects; Group Communication System Enablers for LTE (GCSE LTE)".
[51]
TS 23.161: "Network-based IP flow mobility and Wireless Local Area Network (WLAN) offload; Stage 2".
[52]
TS 29.155: "Traffic Steering Control; Representational State Transfer (REST) over St reference point".
[53]
RFC 7944: "Diameter Routing Message Priority".
[54]
RFC 5719: "Updated IANA Considerations for Diameter Command Code Allocations".
[55]
RFC 2234: "Augmented BNF for syntax specifications".
[56]
TS 23.303: "Proximity-based services (ProSe); Stage 2".
[57]
TS 26.114: "IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction".
[58]
RFC 3948: " UDP Encapsulation of IPsec ESP Packets".
[59]
TS 24.302: "Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; stage 3".
[60]
RFC 8583: "Diameter Load Information Conveyance".
[61]
RFC 6733: "Diameter Base Protocol".
[62]
TS 29.251: "Gw and Gwn reference points for sponsored data connectivity; stage 3".
[63]
TS 29.244: "Interface between the Control Plane and the User Plane of EPC Nodes; Stage 3".
[64]
TS 22.101: "Service aspects; Service principles".
[65]
TS 23.221: "Architectural requirements".
[66]
RFC 8506: "Diameter Credit Control Application".
3 Definitions and abbreviations p. 18
3.1 Definitions p. 18
For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply:
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 TDF or a PCEF enhanced with ADC, and is out of scope of this specification.
Application identifier:
An identifier, referring to a specific application detection filter.
ADC decision:
A decision consists of references to ADC rules, associated enforcement actions (for dynamic ADC rules) and TDF session attributes and is provided by the PCRF to the TDF for application detection and control.
ADC rule:
A set of information enabling the detection of application traffic and associated enforcement actions. ADC rules are directly provisioned into the TDF and referenced by the PCRF.
Bit rate:
The number of bits (denoted in units of bits, kbits, etc.) that are conveyed or processed per unit of time. The bit rate in bit/s can be abbreviated with bps. This specification uses SI (International System of Units) prefixes as unit prefixes, which strictly refer to the power of 10, and shall not be used for the power of 2. For example, 1 kbit/s represents 1000 bit/s or 1 Mbit/s represents 1000 kbit/s and so on.
Detected application traffic:
An aggregate set of packet flows that are generated by a given application and detected by an application detection filter.
IP-CAN bearer:
IP transmission path of defined capacity, delay and bit error rate, etc. See TR 21.905 for the definition of bearer.
IP-CAN session:
association between a UE and an IP network. The association is identified by one or more UE Ipv4 addresses/ and/or Ipv6 prefix together with a UE identity information, if available, and a PDN represented by a PDN ID (e.g. an APN). An IP-CAN session incorporates one or more IP-CAN bearers. Support for multiple IP-CAN bearers per IP-CAN session is IP-CAN specific. An IP-CAN session exists as long as the related UE Ipv4 address and/or Ipv6 prefix are assigned and announced to the IP network.
IP flow:
unidirectional flow of IP packets with the same source IP address and port number and the same destination IP address and port number and the same transport protocol. Port numbers are only applicable if used by the transport protocol.
IP Flow mapping:
IP flow mapping is used in Network-initiated NBIFOM mode when the UE wants to request the network to apply specific mapping of IP flows to 3GPP access or WLAN access. It applies to the same parameters as the NBIFOM routing rule.
Gateway Control Session:
An association between a BBERF and a PCRF (when GTP is not used in the EPC), used for transferring access specific parameters, BBERF events and QoS rules between the PCRF and BBERF. In the context of this specification this is implemented by use of the Gxx procedures.
GC1 signalling:
Signalling between the GCS AS and the application client on the UE over the GC1 reference point as defined in TS 23.468.
Monitoring key:
Identifies a usage monitoring control instance.
Multi-access IP-CAN session:
An IP-CAN session whose traffic can be routed over either a 3GPP access or a WLAN access or both. Each IP flow is routed at any single time only over one access.
TDF session:
An association between an IP-CAN session and the assigned TDF for the purpose of application detection and control by the PCRF. The association is identified by one UE Ipv4 address and/or Ipv6 prefix together with optionally a PDN represented by a PDN ID and a set of ADC rules to be applied by the TDF.
Usage monitoring control instance:
the monitoring and reporting of the usage threshold for input, output or total data volume or time of usage for the IP-CAN session/TDF session or the service data flows/application's traffic associated with the same monitoring key.
Presence Reporting Area:
An area defined within 3GPP Packet Domain for the purposes of reporting of UE presence within that area due to policy control and/or charging reasons. There are two types of Presence Reporting Area: "UE-dedicated Presence Reporting Area", and "Core Network pre-configured Presence Reporting Area".
Packet Flow Description (PFD):
A set of information enabling the detection of application traffic provided by a 3rd party service provider (from TS 23.203).
RAN rules:
In this specification, RAN rules refers to the set of RAN assistance parameter and RAN steering command handling for the steering of traffic between E-UTRAN or UTRAN and WLAN associated with RAN-controlled LTE-WLAN interworking or RAN-assisted WLAN interworking.
RAN user plane congestion:
RAN user plane congestion occurs when the demand for RAN resources exceeds the available RAN capacity to deliver the user data for a prolonged period of time.
Restricted local operator services:
communication services provided by an operator that involve either automated or human assistance (e.g. credit card billing, directory assistance, customer care) for which successful authentication is not necessary.
Service data flow:
An aggregate set of packet flows carried through the PCEF that matches a service data flow template (from TS 23.203).
Service data flow filter:
a set of packet flow header parameter values/ranges used to identify one or more of the packet flows (from TS 23.203).
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, required for defining a service data flow (from TS 23.203).
(S)Gi-LAN:
The network infrastructure connected to the 3GPP network over the SGi or Gi reference point that provides various IP-based services.
(S)Gi-LAN service function:
A function located in the (S)Gi-LAN that provides value-added IP-based services e.g. NAT, anti-malware, parental control, DDoS protection.
3.2 Abbreviations p. 20
For the purpose of the present document, the abbreviations given in TR 21.905 and the following apply:
ADC
Application Detection and Control
AF
Application Function
AMBR
Aggregate Maximum Bit Rate
BBERF
Bearer Binding and Event Reporting Function
CCA
Credit-Control-Answer (CC-Answer)
CCR
Credit-Control-Request (CC-Request)
CHEM
Coverage and Handoff Enhancements using Multimedia error robustness feature
CSG
Closed Subscriber Group
CSG-ID
Closed Subscriber Group Identity
DCC
Diameter Credit Control
DRMP
Diameter Routing Message Priority
DTS
Data Transport Service
GBR
Guaranteed Bit Rate
GCS
Group Communication Service
GCS AS
Group Communication Service Application Server
GEO
Geosynchronous Orbit
LEO
Low Earth Orbit
MEO
Medium Earth Orbit
MPS
Multimedia Priority Service
NBIFOM
Network-based IP flow mobility
NB-IoT
Narrowband IoT
OCS
Online charging system
OFCS
Offline charging system
PCEF
Policy and Charging Enforcement Function
PCRF
Policy and Charging Rule Function
PFD
Packet Flow Description
PFDF
Packet Flow Description Function
PRA
Presence Reporting Area
RAA
Re-Auth-Answer (RA-Answer)
RAB
Radio Access Bearer
RAR
Re-Auth-Request (RA-Request)
RCAF
RAN Congestion Awareness Function
RLOS
Restricted Local Operator Services
RUCI
RAN User Plane Congestion Information
SCEF
Service Capability Exposure Function
SUPL
Secure User Plane for Location
TDF
Traffic Detection Function
TSA
TDF-Session-Answer
TSR
TDF-Session-Request
TSSF
Traffic Steering Support Function
UDC
User Data Convergence
UDR
User Data Repository
WB-E-UTRAN
Wide Band E-UTRAN
