Tech-invite  3GPPspecsRELsGlossariesSIP

Top   in Index   Prev   Next

TR 29.816CT3
Study on PCRF
Failure and Restoration

use "3GPP‑Page" to get the Word version
for a better overview, the Table of Contents (ToC) is reproduced
V10.0.0 (Wzip)  2010/10  63 p.

Rapporteur:  Mr. Punz, Gottfried

This TR contains the results of the study on PCRF failure and restoration.
Target failure and recovery scenarios are detailed; the following scenarios are addressed (incl. roaming):
  • Single PCRF deployment (covering also the equivalent scenario of multiple PCRFs with a fixed assignment of PCRFs);
  • Multiple PCRFs and the DRA is used;
PCRF node failures of different type (e.g. complete outage, loss of dynamic data) and the aspect of reliability in signaling connections will be studied.
Functional requirements for solutions to handle such cases in a standardized way are defined, considering the network elements PCRF, PCEF, BBERF, AF and DRA and taking operators' preferences into account (e.g. minimal impact on user experience versus maximal control/minimum risk for the operator).
The study describes the potential solutions, which include procedures and signalling between PCRF and other PCC related network nodes, and procedures and signalling between Diameter clients (i.e. PCEF/BBERF/AF) and the DRA.
Per solution the impacted 3GPP specifications and the necessary changes therein are listed.
The study report finally evaluates the solutions and draws conclusions with respect to the type of solutions and their feasibility in terms of implementation effort/complexity.

full Table of Contents for  TR 29.816  Word version:   10.0.0

Here   Top


1  ScopeWord-p. 8
2  References
3  Definitions and abbreviationsWord-p. 9
4  Failure and restoration scenariosWord-p. 10
5  Functional requirements for solutionsWord-p. 19
6  SolutionsWord-p. 20
6.0  General
6.1  Solution 1: Solution for the PCRF failure reselection for the DRA
6.2  Solution 2: use of DIAMETER base protocol in Single PCRF deployment (with Direct Client-Server Connection)Word-p. 23
6.3  Solution 3: Graceful termination of servicesUp
6.4  Solution 4: Strict termination of bearer services
6.5  Solution 5: PCRF session state restorationWord-p. 25
6.6  Solution 6: Soft recovery after a PCRF restartWord-p. 28
6.7  Solution 7: Bulk SignalingWord-p. 37
6.8  Solution 8: Adding explicit resilience to PCRF sessionsUp
6.9  Solution 9: Unified solution for termination of bearer servicesWord-p. 43
7  EvaluationWord-p. 46
8  ConclusionWord-p. 51
A  coding examplesWord-p. 52
B  Change historyWord-p. 64

Up   Top