tech-invite   World Map     

3GPP     Specs     Glossaries     Architecture     IMS     UICC       IETF     RFCs     Groups     SIP     ABNFs       Search

Top          in Index          Prev          Next

TR 29.816 (CT3)
Study on PCRF failure and restoration

|   ToC   |   3GPP‑Page   |   Help   |

(W-zip) V10.0.0    2010/10    63 p.

Rapporteur:  Mr. Punz, Gottfried
See also:  PCC-related TS/TR    

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.


Here          Top


1 Scope    2 References    3 Definitions and abbreviations    3.1 Definitions    3.2 Abbreviations    4 Failure and restoration scenarios    4.1 Baseline architecture    4.2 Failure and recovery detection    4.3 PCRF node failure scenarios    4.4 Selection of restoration scheme    5 Functional requirements for solutions    5.1 General    5.2 Functional requirements for all deployments    5.3 Functional requirements for the multiple PCRF deployment with DRA    6 Solutions    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)    6.3 Solution 3: Graceful termination of services    6.4 Solution 4: Strict termination of bearer services    6.5 Solution 5: PCRF session state restoration    6.6 Solution 6: Soft recovery after a PCRF restart    6.7 Solution 7: Bulk Signaling    6.8 Solution 8: Adding explicit resilience to PCRF sessions    6.9 Solution 9: Unified solution for termination of bearer services    7 Evaluation    7.1 General    7.2 Comparison of restoration solutions    7.3 Evaluation of failure and recovery detection mechanisms    8 Conclusion    A coding examples    A.1 Bulk signaling    A.2 Restart indication    A.3 PCRF session state restoration    A.4 Adding explicit resilience to PCRF sessions    B Change history   


1   Scope   Word-p. 8
2   References
3   Definitions and abbreviations   Word-p. 9
4   Failure and restoration scenarios   Word-p. 10
5   Functional requirements for solutions   Word-p. 19
6   Solutions   Word-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 services      Up
6.4   Solution 4: Strict termination of bearer services
6.5   Solution 5: PCRF session state restoration   Word-p. 25
6.6   Solution 6: Soft recovery after a PCRF restart   Word-p. 28
6.7   Solution 7: Bulk Signaling   Word-p. 37
6.8   Solution 8: Adding explicit resilience to PCRF sessions      Up
6.9   Solution 9: Unified solution for termination of bearer services   Word-p. 43
7   Evaluation   Word-p. 46
8   Conclusion   Word-p. 51
A   coding examples   Word-p. 52      Up
B   Change history   Word-p. 64

Up          Top