draft-ietf-dime-rfc4006bis-00.txt   draft-ietf-dime-rfc4006bis-01.txt 
Network Working Group L. Bertz, Ed. Network Working Group L. Bertz, Ed.
Internet-Draft Sprint Internet-Draft Sprint
Intended status: Standards Track D. Dolson, Ed. Intended status: Standards Track D. Dolson, Ed.
Expires: March 25, 2017 Y. Lifshitz, Ed. Expires: August 27, 2017 Y. Lifshitz, Ed.
Sandvine Sandvine
H. Hakala February 23, 2017
L. Mattila
Oy L M Ericsson Ab
J-P. Koskinen
M. Stura
Nokia Networks
J. Loughney
Nokia Research Center
September 21, 2016
Diameter Credit-Control Application Diameter Credit-Control Application
draft-ietf-dime-rfc4006bis-00 draft-ietf-dime-rfc4006bis-01
Abstract Abstract
This document specifies a Diameter application that can be used to This document specifies a Diameter application that can be used to
implement real-time credit-control for a variety of end user services implement real-time credit-control for a variety of end user services
such as network access, Session Initiation Protocol (SIP) services, such as network access, Session Initiation Protocol (SIP) services,
messaging services, and download services. messaging services, and download services.
Status of This Memo Status of This Memo
skipping to change at page 1, line 43 skipping to change at page 1, line 35
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 25, 2017. This Internet-Draft will expire on August 27, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 32 skipping to change at page 2, line 24
outside the IETF Standards Process, and derivative works of it may outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other it for publication as an RFC or to translate it into languages other
than English. than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 5 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 5
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 6 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 6
1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 6 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 6
1.3. Advertising Application Support . . . . . . . . . . . . . 7 1.3. Advertising Application Support . . . . . . . . . . . . . 8
2. Architecture Models . . . . . . . . . . . . . . . . . . . . . 8 2. Architecture Models . . . . . . . . . . . . . . . . . . . . . 8
3. Credit-Control Messages . . . . . . . . . . . . . . . . . . . 9 3. Credit-Control Messages . . . . . . . . . . . . . . . . . . . 10
3.1. Credit-Control-Request (CCR) Command . . . . . . . . . . 10 3.1. Credit-Control-Request (CCR) Command . . . . . . . . . . 10
3.2. Credit-Control-Answer (CCA) Command . . . . . . . . . . . 11 3.2. Credit-Control-Answer (CCA) Command . . . . . . . . . . . 11
4. Credit-Control Application Overview . . . . . . . . . . . . . 12 4. Credit-Control Application Overview . . . . . . . . . . . . . 12
4.1. Service-Specific Rating Input and Interoperability . . . 14 4.1. Service-Specific Rating Input and Interoperability . . . 14
4.1.1. Specifying Rating Input AVPs . . . . . . . . . . . . 14 4.1.1. Specifying Rating Input AVPs . . . . . . . . . . . . 14
4.1.2. Service-Specific Documentation . . . . . . . . . . . 15 4.1.2. Service-Specific Documentation . . . . . . . . . . . 15
4.1.3. Handling of Unsupported/Incorrect Rating Input . . . 16 4.1.3. Handling of Unsupported/Incorrect Rating Input . . . 16
4.1.4. RADIUS Vendor-Specific Rating Attributes . . . . . . 16 4.1.4. RADIUS Vendor-Specific Rating Attributes . . . . . . 16
5. Session Based Credit-Control . . . . . . . . . . . . . . . . 16 5. Session Based Credit-Control . . . . . . . . . . . . . . . . 16
5.1. General Principles . . . . . . . . . . . . . . . . . . . 16 5.1. General Principles . . . . . . . . . . . . . . . . . . . 16
skipping to change at page 3, line 7 skipping to change at page 2, line 48
5.1.2. Credit-Control for Multiple Services within a 5.1.2. Credit-Control for Multiple Services within a
(sub-)Session . . . . . . . . . . . . . . . . . . . . 18 (sub-)Session . . . . . . . . . . . . . . . . . . . . 18
5.2. First Interrogation . . . . . . . . . . . . . . . . . . . 22 5.2. First Interrogation . . . . . . . . . . . . . . . . . . . 22
5.2.1. First Interrogation after Authorization and 5.2.1. First Interrogation after Authorization and
Authentication . . . . . . . . . . . . . . . . . . . 24 Authentication . . . . . . . . . . . . . . . . . . . 24
5.2.2. Authorization Messages for First Interrogation . . . 25 5.2.2. Authorization Messages for First Interrogation . . . 25
5.3. Intermediate Interrogation . . . . . . . . . . . . . . . 28 5.3. Intermediate Interrogation . . . . . . . . . . . . . . . 28
5.4. Final Interrogation . . . . . . . . . . . . . . . . . . . 30 5.4. Final Interrogation . . . . . . . . . . . . . . . . . . . 30
5.5. Server-Initiated Credit Re-Authorization . . . . . . . . 31 5.5. Server-Initiated Credit Re-Authorization . . . . . . . . 31
5.6. Graceful Service Termination . . . . . . . . . . . . . . 33 5.6. Graceful Service Termination . . . . . . . . . . . . . . 33
5.6.1. Terminate Action . . . . . . . . . . . . . . . . . . 35 5.6.1. Terminate Action . . . . . . . . . . . . . . . . . . 36
5.6.2. Redirect Action . . . . . . . . . . . . . . . . . . . 35 5.6.2. Redirect Action . . . . . . . . . . . . . . . . . . . 37
5.6.3. Restrict Access Action . . . . . . . . . . . . . . . 37 5.6.3. Restrict Access Action . . . . . . . . . . . . . . . 39
5.6.4. Usage of the Server-Initiated Credit Re-Authorization 38 5.6.4. Usage of the Server-Initiated Credit Re-Authorization 40
5.7. Failure Procedures . . . . . . . . . . . . . . . . . . . 39
6. One Time Event . . . . . . . . . . . . . . . . . . . . . . . 41
6.1. Service Price Enquiry . . . . . . . . . . . . . . . . . . 42
6.2. Balance Check . . . . . . . . . . . . . . . . . . . . . . 43
6.3. Direct Debiting . . . . . . . . . . . . . . . . . . . . . 43
6.4. Refund . . . . . . . . . . . . . . . . . . . . . . . . . 44
6.5. Failure Procedure . . . . . . . . . . . . . . . . . . . . 45
7. Credit-Control Application State Machine . . . . . . . . . . 47
8. Credit-Control AVPs . . . . . . . . . . . . . . . . . . . . . 55
8.1. CC-Correlation-Id AVP . . . . . . . . . . . . . . . . . . 58
8.2. CC-Request-Number AVP . . . . . . . . . . . . . . . . . . 58
8.3. CC-Request-Type AVP . . . . . . . . . . . . . . . . . . . 58
8.4. CC-Session-Failover AVP . . . . . . . . . . . . . . . . . 59
8.5. CC-Sub-Session-Id AVP . . . . . . . . . . . . . . . . . . 59
8.6. Check-Balance-Result AVP . . . . . . . . . . . . . . . . 60
8.7. Cost-Information AVP . . . . . . . . . . . . . . . . . . 60
8.8. Unit-Value AVP . . . . . . . . . . . . . . . . . . . . . 61
8.9. Exponent AVP . . . . . . . . . . . . . . . . . . . . . . 61
8.10. Value-Digits AVP . . . . . . . . . . . . . . . . . . . . 61
8.11. Currency-Code AVP . . . . . . . . . . . . . . . . . . . . 61
8.12. Cost-Unit AVP . . . . . . . . . . . . . . . . . . . . . . 62
8.13. Credit-Control AVP . . . . . . . . . . . . . . . . . . . 62
8.14. Credit-Control-Failure-Handling AVP . . . . . . . . . . . 62
8.15. Direct-Debiting-Failure-Handling AVP . . . . . . . . . . 63
8.16. Multiple-Services-Credit-Control AVP . . . . . . . . . . 64
8.17. Granted-Service-Unit AVP . . . . . . . . . . . . . . . . 65
8.18. Requested-Service-Unit AVP . . . . . . . . . . . . . . . 66
8.19. Used-Service-Unit AVP . . . . . . . . . . . . . . . . . . 66
8.20. Tariff-Time-Change AVP . . . . . . . . . . . . . . . . . 67
8.21. CC-Time AVP . . . . . . . . . . . . . . . . . . . . . . . 67
8.22. CC-Money AVP . . . . . . . . . . . . . . . . . . . . . . 67
8.23. CC-Total-Octets AVP . . . . . . . . . . . . . . . . . . . 68
8.24. CC-Input-Octets AVP . . . . . . . . . . . . . . . . . . . 68
8.25. CC-Output-Octets AVP . . . . . . . . . . . . . . . . . . 68
8.26. CC-Service-Specific-Units AVP . . . . . . . . . . . . . . 68
8.27. Tariff-Change-Usage AVP . . . . . . . . . . . . . . . . . 68
8.28. Service-Identifier AVP . . . . . . . . . . . . . . . . . 69
8.29. Rating-Group AVP . . . . . . . . . . . . . . . . . . . . 69
8.30. G-S-U-Pool-Reference AVP . . . . . . . . . . . . . . . . 69
8.31. G-S-U-Pool-Identifier AVP . . . . . . . . . . . . . . . . 70
8.32. CC-Unit-Type AVP . . . . . . . . . . . . . . . . . . . . 70
8.33. Validity-Time AVP . . . . . . . . . . . . . . . . . . . . 70
8.34. Final-Unit-Indication AVP . . . . . . . . . . . . . . . . 71
8.35. Final-Unit-Action AVP . . . . . . . . . . . . . . . . . . 72
8.36. Restriction-Filter-Rule AVP . . . . . . . . . . . . . . . 73
8.37. Redirect-Server AVP . . . . . . . . . . . . . . . . . . . 73
8.38. Redirect-Address-Type AVP . . . . . . . . . . . . . . . . 73
8.39. Redirect-Server-Address AVP . . . . . . . . . . . . . . . 74
8.40. Multiple-Services-Indicator AVP . . . . . . . . . . . . . 74
8.41. Requested-Action AVP . . . . . . . . . . . . . . . . . . 74
8.42. Service-Context-Id AVP . . . . . . . . . . . . . . . . . 75
8.43. Service-Parameter-Info AVP . . . . . . . . . . . . . . . 76
8.44. Service-Parameter-Type AVP . . . . . . . . . . . . . . . 76
8.45. Service-Parameter-Value AVP . . . . . . . . . . . . . . . 77
8.46. Subscription-Id AVP . . . . . . . . . . . . . . . . . . . 77
8.47. Subscription-Id-Type AVP . . . . . . . . . . . . . . . . 77
8.48. Subscription-Id-Data AVP . . . . . . . . . . . . . . . . 78
8.49. User-Equipment-Info AVP . . . . . . . . . . . . . . . . . 78
8.50. User-Equipment-Info-Type AVP . . . . . . . . . . . . . . 78
8.51. User-Equipment-Info-Value AVP . . . . . . . . . . . . . . 79
9. Result Code AVP Values . . . . . . . . . . . . . . . . . . . 79
9.1. Transient Failures . . . . . . . . . . . . . . . . . . . 79
9.2. Permanent Failures . . . . . . . . . . . . . . . . . . . 80
10. AVP Occurrence Table . . . . . . . . . . . . . . . . . . . . 80
10.1. Credit-Control AVP Table . . . . . . . . . . . . . . . . 81
10.2. Re-Auth-Request/Answer AVP Table . . . . . . . . . . . . 82
11. RADIUS/Diameter Credit-Control Interworking Model . . . . . . 82
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 85
12.1. Application Identifier . . . . . . . . . . . . . . . . . 86
12.2. Command Codes . . . . . . . . . . . . . . . . . . . . . 86
12.3. AVP Codes . . . . . . . . . . . . . . . . . . . . . . . 86
12.4. Result-Code AVP Values . . . . . . . . . . . . . . . . . 86
12.5. CC-Request-Type AVP . . . . . . . . . . . . . . . . . . 86
12.6. CC-Session-Failover AVP . . . . . . . . . . . . . . . . 86
12.7. CC-Unit-Type AVP . . . . . . . . . . . . . . . . . . . . 86
12.8. Check-Balance-Result AVP . . . . . . . . . . . . . . . . 87
12.9. Credit-Control AVP . . . . . . . . . . . . . . . . . . . 87
12.10. Credit-Control-Failure-Handling AVP . . . . . . . . . . 87
12.11. Direct-Debiting-Failure-Handling AVP . . . . . . . . . . 87
12.12. Final-Unit-Action AVP . . . . . . . . . . . . . . . . . 87
12.13. Multiple-Services-Indicator AVP . . . . . . . . . . . . 87
12.14. Redirect-Address-Type AVP . . . . . . . . . . . . . . . 87
12.15. Requested-Action AVP . . . . . . . . . . . . . . . . . . 88
12.16. Subscription-Id-Type AVP . . . . . . . . . . . . . . . . 88
12.17. Tariff-Change-Usage AVP . . . . . . . . . . . . . . . . 88
12.18. User-Equipment-Info-Type AVP . . . . . . . . . . . . . . 88
13. Credit-Control Application Related Parameters . . . . . . . . 88
14. Security Considerations . . . . . . . . . . . . . . . . . . . 89
14.1. Direct Connection with Redirects . . . . . . . . . . . . 90
15. References . . . . . . . . . . . . . . . . . . . . . . . . . 91 5.7. Failure Procedures . . . . . . . . . . . . . . . . . . . 40
15.1. Normative References . . . . . . . . . . . . . . . . . . 91 6. One Time Event . . . . . . . . . . . . . . . . . . . . . . . 43
15.2. Informative References . . . . . . . . . . . . . . . . . 92 6.1. Service Price Enquiry . . . . . . . . . . . . . . . . . . 44
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 93 6.2. Balance Check . . . . . . . . . . . . . . . . . . . . . . 45
Appendix B. Credit-Control Sequences . . . . . . . . . . . . . . 93 6.3. Direct Debiting . . . . . . . . . . . . . . . . . . . . . 45
B.1. Flow I . . . . . . . . . . . . . . . . . . . . . . . . . 93 6.4. Refund . . . . . . . . . . . . . . . . . . . . . . . . . 46
B.2. Flow II . . . . . . . . . . . . . . . . . . . . . . . . . 96 6.5. Failure Procedure . . . . . . . . . . . . . . . . . . . . 47
B.3. Flow III . . . . . . . . . . . . . . . . . . . . . . . . 98 7. Credit-Control Application State Machine . . . . . . . . . . 49
B.4. Flow IV . . . . . . . . . . . . . . . . . . . . . . . . . 98 8. Credit-Control AVPs . . . . . . . . . . . . . . . . . . . . . 57
B.5. Flow V . . . . . . . . . . . . . . . . . . . . . . . . . 100 8.1. CC-Correlation-Id AVP . . . . . . . . . . . . . . . . . . 60
B.6. Flow VI . . . . . . . . . . . . . . . . . . . . . . . . . 101 8.2. CC-Request-Number AVP . . . . . . . . . . . . . . . . . . 60
B.7. Flow VII . . . . . . . . . . . . . . . . . . . . . . . . 102 8.3. CC-Request-Type AVP . . . . . . . . . . . . . . . . . . . 61
B.8. Flow VIII . . . . . . . . . . . . . . . . . . . . . . . . 104 8.4. CC-Session-Failover AVP . . . . . . . . . . . . . . . . . 62
B.9. Flow IX . . . . . . . . . . . . . . . . . . . . . . . . . 106 8.5. CC-Sub-Session-Id AVP . . . . . . . . . . . . . . . . . . 62
Appendix C. Changes relative to RFC4006 . . . . . . . . . . . . 111 8.6. Check-Balance-Result AVP . . . . . . . . . . . . . . . . 62
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 112 8.7. Cost-Information AVP . . . . . . . . . . . . . . . . . . 63
8.8. Unit-Value AVP . . . . . . . . . . . . . . . . . . . . . 64
8.9. Exponent AVP . . . . . . . . . . . . . . . . . . . . . . 64
8.10. Value-Digits AVP . . . . . . . . . . . . . . . . . . . . 64
8.11. Currency-Code AVP . . . . . . . . . . . . . . . . . . . . 64
8.12. Cost-Unit AVP . . . . . . . . . . . . . . . . . . . . . . 64
8.13. Credit-Control AVP . . . . . . . . . . . . . . . . . . . 65
8.14. Credit-Control-Failure-Handling AVP . . . . . . . . . . . 65
8.15. Direct-Debiting-Failure-Handling AVP . . . . . . . . . . 66
8.16. Multiple-Services-Credit-Control AVP . . . . . . . . . . 67
8.17. Granted-Service-Unit AVP . . . . . . . . . . . . . . . . 68
8.18. Requested-Service-Unit AVP . . . . . . . . . . . . . . . 69
8.19. Used-Service-Unit AVP . . . . . . . . . . . . . . . . . . 69
8.20. Tariff-Time-Change AVP . . . . . . . . . . . . . . . . . 70
8.21. CC-Time AVP . . . . . . . . . . . . . . . . . . . . . . . 70
8.22. CC-Money AVP . . . . . . . . . . . . . . . . . . . . . . 70
8.23. CC-Total-Octets AVP . . . . . . . . . . . . . . . . . . . 71
8.24. CC-Input-Octets AVP . . . . . . . . . . . . . . . . . . . 71
8.25. CC-Output-Octets AVP . . . . . . . . . . . . . . . . . . 71
8.26. CC-Service-Specific-Units AVP . . . . . . . . . . . . . . 71
8.27. Tariff-Change-Usage AVP . . . . . . . . . . . . . . . . . 71
8.28. Service-Identifier AVP . . . . . . . . . . . . . . . . . 72
8.29. Rating-Group AVP . . . . . . . . . . . . . . . . . . . . 72
8.30. G-S-U-Pool-Reference AVP . . . . . . . . . . . . . . . . 72
8.31. G-S-U-Pool-Identifier AVP . . . . . . . . . . . . . . . . 73
8.32. CC-Unit-Type AVP . . . . . . . . . . . . . . . . . . . . 73
8.33. Validity-Time AVP . . . . . . . . . . . . . . . . . . . . 73
8.34. Final-Unit-Indication AVP . . . . . . . . . . . . . . . . 74
8.35. Final-Unit-Action AVP . . . . . . . . . . . . . . . . . . 75
8.36. Restriction-Filter-Rule AVP . . . . . . . . . . . . . . . 76
8.37. Redirect-Server AVP . . . . . . . . . . . . . . . . . . . 76
8.38. Redirect-Address-Type AVP . . . . . . . . . . . . . . . . 77
8.39. Redirect-Server-Address AVP . . . . . . . . . . . . . . . 77
8.40. Multiple-Services-Indicator AVP . . . . . . . . . . . . . 77
8.41. Requested-Action AVP . . . . . . . . . . . . . . . . . . 78
8.42. Service-Context-Id AVP . . . . . . . . . . . . . . . . . 79
8.43. Service-Parameter-Info AVP . . . . . . . . . . . . . . . 79
8.44. Service-Parameter-Type AVP . . . . . . . . . . . . . . . 80
8.45. Service-Parameter-Value AVP . . . . . . . . . . . . . . . 80
8.46. Subscription-Id AVP . . . . . . . . . . . . . . . . . . . 80
8.47. Subscription-Id-Type AVP . . . . . . . . . . . . . . . . 81
8.48. Subscription-Id-Data AVP . . . . . . . . . . . . . . . . 81
8.49. User-Equipment-Info AVP . . . . . . . . . . . . . . . . . 82
8.50. User-Equipment-Info-Type AVP . . . . . . . . . . . . . . 82
8.51. User-Equipment-Info-Value AVP . . . . . . . . . . . . . . 83
8.52. User-Equipment-Info-Extension AVP . . . . . . . . . . . . 83
8.53. User-Equipment-Info-IMEISV AVP . . . . . . . . . . . . . 83
8.54. User-Equipment-Info-MAC AVP . . . . . . . . . . . . . . . 83
8.55. User-Equipment-Info-EUI64 AVP . . . . . . . . . . . . . . 83
8.56. User-Equipment-Info-ModifiedEUI64 AVP . . . . . . . . . . 84
8.57. User-Equipment-Info-IMEI AVP . . . . . . . . . . . . . . 84
8.58. Subscription-Id-Extension AVP . . . . . . . . . . . . . . 84
8.59. Subscription-Id-E164 AVP . . . . . . . . . . . . . . . . 85
8.60. Subscription-Id-IMSI AVP . . . . . . . . . . . . . . . . 85
8.61. Subscription-Id-SIP-URI AVP . . . . . . . . . . . . . . . 85
8.62. Subscription-Id-NAI AVP . . . . . . . . . . . . . . . . . 85
8.63. Subscription-Id-Private AVP . . . . . . . . . . . . . . . 85
8.64. Redirect-Server-Extension AVP . . . . . . . . . . . . . . 85
8.65. Redirect-Address-IPv4Address AVP . . . . . . . . . . . . 86
8.66. Redirect-Address-IPv6Address AVP . . . . . . . . . . . . 86
8.67. Redirect-Address-URL AVP . . . . . . . . . . . . . . . . 86
8.68. Redirect-Address-SIP-URI AVP . . . . . . . . . . . . . . 87
8.69. QoS-Final-Unit-Indication AVP . . . . . . . . . . . . . . 87
9. Result Code AVP Values . . . . . . . . . . . . . . . . . . . 88
9.1. Transient Failures . . . . . . . . . . . . . . . . . . . 89
9.2. Permanent Failures . . . . . . . . . . . . . . . . . . . 89
10. AVP Occurrence Table . . . . . . . . . . . . . . . . . . . . 90
10.1. Credit-Control AVP Table . . . . . . . . . . . . . . . . 90
10.2. Re-Auth-Request/Answer AVP Table . . . . . . . . . . . . 91
11. RADIUS/Diameter Credit-Control Interworking Model . . . . . . 92
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 95
12.1. Application Identifier . . . . . . . . . . . . . . . . . 95
12.2. Command Codes . . . . . . . . . . . . . . . . . . . . . 95
12.3. AVP Codes . . . . . . . . . . . . . . . . . . . . . . . 95
12.4. Result-Code AVP Values . . . . . . . . . . . . . . . . . 95
12.5. CC-Request-Type AVP . . . . . . . . . . . . . . . . . . 95
12.6. CC-Session-Failover AVP . . . . . . . . . . . . . . . . 95
12.7. CC-Unit-Type AVP . . . . . . . . . . . . . . . . . . . . 96
12.8. Check-Balance-Result AVP . . . . . . . . . . . . . . . . 96
12.9. Credit-Control AVP . . . . . . . . . . . . . . . . . . . 96
12.10. Credit-Control-Failure-Handling AVP . . . . . . . . . . 96
12.11. Direct-Debiting-Failure-Handling AVP . . . . . . . . . . 96
12.12. Final-Unit-Action AVP . . . . . . . . . . . . . . . . . 96
12.13. Multiple-Services-Indicator AVP . . . . . . . . . . . . 96
12.14. Redirect-Address-Type AVP . . . . . . . . . . . . . . . 97
12.15. Requested-Action AVP . . . . . . . . . . . . . . . . . . 97
12.16. Subscription-Id-Type AVP . . . . . . . . . . . . . . . . 97
12.17. Tariff-Change-Usage AVP . . . . . . . . . . . . . . . . 97
12.18. User-Equipment-Info-Type AVP . . . . . . . . . . . . . . 97
13. Credit-Control Application Related Parameters . . . . . . . . 97
14. Security Considerations . . . . . . . . . . . . . . . . . . . 98
14.1. Direct Connection with Redirects . . . . . . . . . . . . 99
15. References . . . . . . . . . . . . . . . . . . . . . . . . . 100
15.1. Normative References . . . . . . . . . . . . . . . . . . 100
15.2. Informative References . . . . . . . . . . . . . . . . . 102
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 102
Appendix B. Credit-Control Sequences . . . . . . . . . . . . . . 102
B.1. Flow I . . . . . . . . . . . . . . . . . . . . . . . . . 102
B.2. Flow II . . . . . . . . . . . . . . . . . . . . . . . . . 105
B.3. Flow III . . . . . . . . . . . . . . . . . . . . . . . . 107
B.4. Flow IV . . . . . . . . . . . . . . . . . . . . . . . . . 107
B.5. Flow V . . . . . . . . . . . . . . . . . . . . . . . . . 109
B.6. Flow VI . . . . . . . . . . . . . . . . . . . . . . . . . 110
B.7. Flow VII . . . . . . . . . . . . . . . . . . . . . . . . 111
B.8. Flow VIII . . . . . . . . . . . . . . . . . . . . . . . . 113
B.9. Flow IX . . . . . . . . . . . . . . . . . . . . . . . . . 115
Appendix C. Changes relative to RFC4006 . . . . . . . . . . . . 120
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 121
1. Introduction 1. Introduction
This document specifies a Diameter application that can be used to This document specifies a Diameter application that can be used to
implement real-time credit-control for a variety of end user services implement real-time credit-control for a variety of end user services
such as network access, Session Initiation Protocol (SIP) services, such as network access, Session Initiation Protocol (SIP) services,
messaging services, and download services. It provides a general messaging services, and download services. It provides a general
solution to real-time cost and credit-control. solution to real-time cost and credit-control.
The prepaid model has been shown to be very successful, for instance, The prepaid model has been shown to be very successful, for instance,
skipping to change at page 7, line 27 skipping to change at page 7, line 37
event. event.
Rating The act of determining the cost of the service event. Rating The act of determining the cost of the service event.
Service A type of task performed by a service element for an end Service A type of task performed by a service element for an end
user. user.
Service Element A network element that provides a service to the end Service Element A network element that provides a service to the end
users. The Service Element may include the Diameter credit- users. The Service Element may include the Diameter credit-
control client, or another entity (e.g., RADIUS AAA server) that control client, or another entity (e.g., RADIUS AAA server) that
can act as a Credit- control client on behalf of the Service can act as a credit-control client on behalf of the Service
Element. In the latter case, the interface between the Service Element. In the latter case, the interface between the Service
Element and the Diameter credit- control client is outside the Element and the Diameter credit-control client is outside the
scope of this specification. Examples of the Service Elements scope of this specification. Examples of the Service Elements
include Network Access Server (NAS), SIP Proxy, and Application include Network Access Server (NAS), SIP Proxy, and Application
Servers such as messaging server, content server, and gaming Servers such as messaging server, content server, and gaming
server. server.
Service Event An event relating to a service provided to the end Service Event An event relating to a service provided to the end
user. user.
Session based credit-control A credit-control process that makes use Session based credit-control A credit-control process that makes use
of several interrogations: the first, a possible intermediate, and of several interrogations: the first, a possible intermediate, and
the final. The first interrogation is used to reserve money from the final. The first interrogation is used to reserve money from
the user's account and to initiate the process. The intermediate the user's account and to initiate the process. The intermediate
interrogations may be needed to request new quota while the interrogations may be needed to request new quota while the
service is being rendered. The final interrogation is used to service is being rendered. The final interrogation is used to
exit the process. The credit-control server is required to exit the process. The credit-control server is required to
maintain session state for session-based credit- control. maintain session state for session-based credit-control.
1.3. Advertising Application Support 1.3. Advertising Application Support
Diameter nodes conforming to this specification MUST advertise Diameter nodes conforming to this specification MUST advertise
support by including the value of 4 in the Auth-Application-Id of the support by including the value of 4 in the Auth-Application-Id of the
Capabilities-Exchange-Request and Capabilities-Exchange-Answer Capabilities-Exchange-Request and Capabilities-Exchange-Answer
command [RFC6733]. command [RFC6733].
2. Architecture Models 2. Architecture Models
skipping to change at page 10, line 5 skipping to change at page 10, line 17
If Diameter credit-control proxies exist between the credit-control If Diameter credit-control proxies exist between the credit-control
client and the credit-control server, they MUST advertise the client and the credit-control server, they MUST advertise the
Diameter credit-control application support. Diameter credit-control application support.
3. Credit-Control Messages 3. Credit-Control Messages
This section defines new Diameter message Command-Code values that This section defines new Diameter message Command-Code values that
MUST be supported by all Diameter implementations that conform to MUST be supported by all Diameter implementations that conform to
this specification. The Command Codes are as follows: this specification. The Command Codes are as follows:
+------------------------+---------+------+-----------+ +------------------------+--------+------+-----------+
| Command-Name | Abrrev. | Code | Reference | | Command-Name | Abrev. | Code | Reference |
+------------------------+---------+------+-----------+ +------------------------+--------+------+-----------+
| Credit-Control-Request | CCR | 272 | 3.1 | | Credit-Control-Request | CCR | 272 | 3.1 |
| Credit-Control-Answer | CCA | 272 | 3.2 | | Credit-Control-Answer | CCA | 272 | 3.2 |
+------------------------+---------+------+-----------+ +------------------------+--------+------+-----------+
Table 1: Credit-Control Commands Table 1: Credit-Control Commands
Diameter Base [RFC6733] defines in the section 3.2 the Command Code Diameter Base [RFC6733] defines in the section 3.2 the Command Code
format specification. These formats are observed in Credit-Control format specification. These formats are observed in Credit-Control
messages. messages.
3.1. Credit-Control-Request (CCR) Command 3.1. Credit-Control-Request (CCR) Command
The Credit-Control-Request message (CCR) is indicated by the command- The Credit-Control-Request message (CCR) is indicated by the command-
skipping to change at page 11, line 12 skipping to change at page 11, line 12
Message Format Message Format
<Credit-Control-Request> ::= < Diameter Header: 272, REQ, PXY > <Credit-Control-Request> ::= < Diameter Header: 272, REQ, PXY >
< Session-Id > < Session-Id >
{ Origin-Host } { Origin-Host }
{ Origin-Realm } { Origin-Realm }
{ Destination-Realm } { Destination-Realm }
{ Auth-Application-Id } { Auth-Application-Id }
{ Service-Context-Id } { Service-Context-Id }
{ CC-Request-Type } { CC-Request-Type }
{ CC-Request-Number } { CC-Request-Number }
[ Destination-Host ] [ Destination-Host ]
[ User-Name ] [ User-Name ]
[ CC-Sub-Session-Id ] [ CC-Sub-Session-Id ]
[ Acct-Multi-Session-Id ] [ Acct-Multi-Session-Id ]
[ Origin-State-Id ] [ Origin-State-Id ]
[ Event-Timestamp ] [ Event-Timestamp ]
*[ Subscription-Id ] *[ Subscription-Id ]
[ Service-Identifier ] *[ Subscription-Id-Extension ]
[ Termination-Cause ] [ Service-Identifier ]
[ Requested-Service-Unit ] [ Termination-Cause ]
[ Requested-Action ] [ Requested-Service-Unit ]
*[ Used-Service-Unit ] [ Requested-Action ]
[ Multiple-Services-Indicator ] *[ Used-Service-Unit ]
*[ Multiple-Services-Credit-Control ] [ Multiple-Services-Indicator ]
*[ Service-Parameter-Info ] *[ Multiple-Services-Credit-Control ]
[ CC-Correlation-Id ] *[ Service-Parameter-Info ]
[ User-Equipment-Info ] [ CC-Correlation-Id ]
*[ Proxy-Info ] [ User-Equipment-Info ]
*[ Route-Record ] [ User-Equipment-Info-Extension ]
*[ AVP ] *[ Proxy-Info ]
*[ Route-Record ]
*[ AVP ]
3.2. Credit-Control-Answer (CCA) Command 3.2. Credit-Control-Answer (CCA) Command
The Credit-Control-Answer message (CCA) is indicated by the command- The Credit-Control-Answer message (CCA) is indicated by the command-
code field being set to 272 and the 'R' bit being cleared in the code field being set to 272 and the 'R' bit being cleared in the
Command Flags field. It is used between the credit-control server Command Flags field. It is used between the credit-control server
and the Diameter credit-control client to acknowledge a Credit- and the Diameter credit-control client to acknowledge a Credit-
Control-Request command. Control-Request command.
Message Format Message Format
skipping to change at page 12, line 22 skipping to change at page 12, line 22
[ User-Name ] [ User-Name ]
[ CC-Session-Failover ] [ CC-Session-Failover ]
[ CC-Sub-Session-Id ] [ CC-Sub-Session-Id ]
[ Acct-Multi-Session-Id ] [ Acct-Multi-Session-Id ]
[ Origin-State-Id ] [ Origin-State-Id ]
[ Event-Timestamp ] [ Event-Timestamp ]
[ Granted-Service-Unit ] [ Granted-Service-Unit ]
*[ Multiple-Services-Credit-Control ] *[ Multiple-Services-Credit-Control ]
[ Cost-Information] [ Cost-Information]
[ Final-Unit-Indication ] [ Final-Unit-Indication ]
[ QoS-Final-Unit-Indication ]
[ Check-Balance-Result ] [ Check-Balance-Result ]
[ Credit-Control-Failure-Handling ] [ Credit-Control-Failure-Handling ]
[ Direct-Debiting-Failure-Handling ] [ Direct-Debiting-Failure-Handling ]
[ Validity-Time] [ Validity-Time ]
*[ Redirect-Host] *[ Redirect-Host ]
[ Redirect-Host-Usage ] [ Redirect-Host-Usage ]
[ Redirect-Max-Cache-Time ] [ Redirect-Max-Cache-Time ]
*[ Proxy-Info ] *[ Proxy-Info ]
*[ Route-Record ] *[ Route-Record ]
*[ Failed-AVP ] *[ Failed-AVP ]
*[ AVP ] *[ AVP ]
4. Credit-Control Application Overview 4. Credit-Control Application Overview
The credit authorization process takes place before and during The credit authorization process takes place before and during
skipping to change at page 14, line 5 skipping to change at page 14, line 5
time event. Session state is not maintained. time event. Session state is not maintained.
A flexible credit-control application specific failure handling is A flexible credit-control application specific failure handling is
defined in which the home service provider can model the credit- defined in which the home service provider can model the credit-
control client behavior according to its own credit risk management control client behavior according to its own credit risk management
policy. policy.
The Credit-Control-Failure-Handling AVP and the Direct-Debiting- The Credit-Control-Failure-Handling AVP and the Direct-Debiting-
Failure-Handling AVP are defined to determine what is done if the Failure-Handling AVP are defined to determine what is done if the
sending of credit-control messages to the credit-control server has sending of credit-control messages to the credit-control server has
been temporarily prevented. The usage of the Credit-Control- been temporarily prevented. The usage of the Credit-Control-Failure-
Failure-Handling AVP and the Direct-Debiting-Failure-Handling AVP Handling AVP and the Direct-Debiting-Failure-Handling AVP allows
allows flexibility, as failure handling for the credit-control flexibility, as failure handling for the credit-control session and
session and one time event direct debiting may be different. one-time event direct debiting may be different.
4.1. Service-Specific Rating Input and Interoperability 4.1. Service-Specific Rating Input and Interoperability
The Diameter credit-control application defines the framework for The Diameter credit-control application defines the framework for
credit-control; it provides generic credit-control mechanisms credit-control; it provides generic credit-control mechanisms
supporting multiple service applications. The credit-control supporting multiple service applications. The credit-control
application, therefore, does not define AVPs that could be used as application, therefore, does not define AVPs that could be used as
input in the rating process. Listing the possible services that input in the rating process. Listing the possible services that
could use this Diameter application is out of scope for this generic could use this Diameter application is out of scope for this generic
mechanism. mechanism.
skipping to change at page 15, line 33 skipping to change at page 15, line 33
4.1.2. Service-Specific Documentation 4.1.2. Service-Specific Documentation
The service specific rating input AVPs, the contents of the Service- The service specific rating input AVPs, the contents of the Service-
Parameter-Info AVP or Service-Context-Id AVP (defined in Parameter-Info AVP or Service-Context-Id AVP (defined in
Section 8.42) are not within the scope of this document. To Section 8.42) are not within the scope of this document. To
facilitate interoperability, it is RECOMMENDED that the rating input facilitate interoperability, it is RECOMMENDED that the rating input
and the values of the Service-Context-Id be coordinated via an and the values of the Service-Context-Id be coordinated via an
informational RFC or other permanent and readily available reference. informational RFC or other permanent and readily available reference.
The specification of another cooperative standardization body (e.g., The specification of another cooperative standardization body (e.g.,
3GPP, OMA, and 3GPP2) SHOULD be used. However, private services may 3GPP, OMA, or 3GPP2) SHOULD be used. However, private services may
be deployed that are subject to agreements between providers of the be deployed that are subject to agreements between providers of the
credit-control server and client. In this case, vendor specific AVPs credit-control server and client. In this case, vendor specific AVPs
can be used. can be used.
This specification, together with the above service specific This specification, together with the above service specific
documents, governs the credit-control message. Service specific documents, governs the credit-control message. Service specific
documents define which existing AVPs or new AVPs are used as input to documents define which existing AVPs or new AVPs are used as input to
the rating process (i.e., those that do not define new credit-control the rating process (i.e., those that do not define new credit-control
applications), and thus have to be included in the Credit-Control- applications), and thus have to be included in the Credit-Control-
Request command by a Diameter credit-control client supporting a Request command by a Diameter credit-control client supporting a
skipping to change at page 16, line 41 skipping to change at page 16, line 41
the Vendor-Specific flag MUST be set to 1 and the Vendor-ID MUST be the Vendor-Specific flag MUST be set to 1 and the Vendor-ID MUST be
set to the IANA Vendor identification value. The Diameter AVP data set to the IANA Vendor identification value. The Diameter AVP data
field contains only the attribute value of the RADIUS attribute. field contains only the attribute value of the RADIUS attribute.
5. Session Based Credit-Control 5. Session Based Credit-Control
5.1. General Principles 5.1. General Principles
For a session-based credit-control, several interrogations are For a session-based credit-control, several interrogations are
needed: the first, intermediate (optional) and the final needed: the first, intermediate (optional) and the final
interrogations. This is illustrated in Figures 2 and 3. interrogations. This is illustrated in Figure 3 and Figure 4.
If the credit-control client performs credit-reservation before If the credit-control client performs credit-reservation before
granting service to the end user, it MUST use several interrogations granting service to the end user, it MUST use several interrogations
toward the credit-control server (i.e., session based credit- toward the credit-control server (i.e., session based credit-
control). In this case, the credit-control server MUST maintain the control). In this case, the credit-control server MUST maintain the
credit-control session state. credit-control session state.
Each credit-control session MUST have a globally unique Session-Id as Each credit-control session MUST have a globally unique Session-Id as
defined in [RFC6733], which MUST NOT be changed during the lifetime defined in [RFC6733], which MUST NOT be changed during the lifetime
of a credit-control session. of a credit-control session.
skipping to change at page 19, line 8 skipping to change at page 19, line 8
credit-control (sub-)session. This is achieved by including the credit-control (sub-)session. This is achieved by including the
optional Multiple-Services-Credit-Control AVP in Credit-Control- optional Multiple-Services-Credit-Control AVP in Credit-Control-
Request/Answer messages. It is possible to request and allocate Request/Answer messages. It is possible to request and allocate
resources as a credit pool shared between multiple services. The resources as a credit pool shared between multiple services. The
services can be grouped into rating groups in order to achieve even services can be grouped into rating groups in order to achieve even
further aggregation of credit allocation. It is also possible to further aggregation of credit allocation. It is also possible to
request and allocate quotas on a per service basis. Where quotas are request and allocate quotas on a per service basis. Where quotas are
allocated to a pool by means of the Multiple-Services-Credit-Control allocated to a pool by means of the Multiple-Services-Credit-Control
AVP, the quotas remain independent objects that can be re-authorized AVP, the quotas remain independent objects that can be re-authorized
independently at any time. Quotas can also be given independent independently at any time. Quotas can also be given independent
result codes, validity times, and Final-Unit-Indications. result codes, validity times, and Final-Unit-Indications or QoS-
Final-Unit-Indications.
A Rating-Group gathers a set of services, identified by a Service- A Rating-Group gathers a set of services, identified by a Service-
Identifier, and subject to the same cost and rating type (e.g., $0.1/ Identifier, and subject to the same cost and rating type (e.g., $0.1/
minute). It is assumed that the service element is provided with minute). It is assumed that the service element is provided with
Rating-Groups, Service-Identifiers, and their associated parameters Rating-Groups, Service-Identifiers, and their associated parameters
that define what has to be metered by means outside the scope of this that define what has to be metered by means outside the scope of this
specification. (Examples of parameters associated to Service- specification. (Examples of parameters associated to Service-
Identifiers are IP 5-tuple and HTTP URL.) Service-Identifiers enable Identifiers are IP 5-tuple and HTTP URL.) Service-Identifiers enable
authorization on a per-service based credit as well as itemized authorization on a per-service based credit as well as itemized
reporting of service usage. It is up to the credit-control server reporting of service usage. It is up to the credit-control server
skipping to change at page 19, line 44 skipping to change at page 19, line 45
\ / Rating-Group 1.......Rating-Group n \ / Rating-Group 1.......Rating-Group n
\ / | | \ / | |
Quota ---------------Quota Quota Quota ---------------Quota Quota
| / | | / |
| / | | / |
Credit-Pool Credit-Pool Credit-Pool Credit-Pool
Figure 2: Multiple-Service (sub)-Session Example Figure 2: Multiple-Service (sub)-Session Example
If independent credit-control of multiple services is used, the If independent credit-control of multiple services is used, the
validity-time and final-unit-indication SHOULD be present either in Validity-Time AVP and Final-Unit-Indication AVP or QoS-Final-Unit-
the Multiple-Services-Credit-Control AVP(s) or at command level as Indication AVP SHOULD be present either in the Multiple-Services-
single AVPs. However, the Result-Code AVP MAY be present both on the Credit-Control AVP(s) or at command level as single AVPs. However,
command level and within the Multiple-Services-Credit-Control AVP. the Result-Code AVP MAY be present both on the command level and
If the Result-Code on the command level indicates a value other than within the Multiple-Services-Credit-Control AVP. If the Result-Code
SUCCESS, then the Result-Code on command level takes precedence over AVP on the command level indicates a value other than SUCCESS, then
any included in the Multiple-Services-Credit-Control AVP. the Result-Code AVP on command level takes precedence over any
included in the Multiple-Services-Credit-Control AVP.
The credit-control client MUST indicate support for independent The credit-control client MUST indicate support for independent
credit-control of multiple services within a (sub-)session by credit-control of multiple services within a (sub-)session by
including the Multiple-Services-Indicator AVP in the first including the Multiple-Services-Indicator AVP in the first
interrogation. A credit-control server not supporting this feature interrogation. A credit-control server not supporting this feature
MUST treat the Multiple-Services-Indicator AVP and any received MUST treat the Multiple-Services-Indicator AVP and any received
Multiple-Services-Credit-Control AVPs as invalid AVPs. Multiple-Services-Credit-Control AVPs as invalid AVPs.
If the client indicated support for independent credit-control of If the client indicated support for independent credit-control of
multiple services, a credit-control server that wishes to use the multiple services, a credit-control server that wishes to use the
skipping to change at page 21, line 10 skipping to change at page 21, line 12
then the total credit is adjusted appropriately. Note that when the then the total credit is adjusted appropriately. Note that when the
total credit is adjusted because services or rating groups are total credit is adjusted because services or rating groups are
removed from the pool, the value that need to be removed is the removed from the pool, the value that need to be removed is the
consumed one (i.e., Cx*Mx). consumed one (i.e., Cx*Mx).
Re-authorizations for an individual service or rating group may be Re-authorizations for an individual service or rating group may be
sought at any time; for example, if a 'non-pooled' quota is used up sought at any time; for example, if a 'non-pooled' quota is used up
or the Validity-Time expires. or the Validity-Time expires.
Where multiple G-S-U-Pool-Reference AVPs (Section 8.30) with the same Where multiple G-S-U-Pool-Reference AVPs (Section 8.30) with the same
G-S-U-Pool-Identifier are provided within a Multiple-Services- G-S-U-Pool-Identifier are provided within a Multiple-Services-Credit-
Credit-Control AVP (Section 8.16) along with the Granted-Service-Unit Control AVP (Section 8.16) along with the Granted-Service-Unit AVP,
AVP, then these MUST have different CC-Unit-Type values, and they all then these MUST have different CC-Unit-Type values, and they all draw
draw from the credit pool separately. For instance, if one from the credit pool separately. For instance, if one multiplier for
multiplier for time (M1t) and one multiplier for volume (M1v) are time (M1t) and one multiplier for volume (M1v) are given, then the
given, then the used resources from the pool is the sum C1t*M1t + used resources from the pool is the sum C1t*M1t + C1v*M1v, where C1t
C1v*M1v, where C1t is the time unit and C1v is the volume unit. is the time unit and C1v is the volume unit.
Where service units are provided within a Multiple-Services-Credit- Where service units are provided within a Multiple-Services-Credit-
Control AVP without a corresponding G-S-U-Pool-Reference AVP, then Control AVP without a corresponding G-S-U-Pool-Reference AVP, then
these are handled independently from any credit pool and from any these are handled independently from any credit pool and from any
other services or rating groups within the session. other services or rating groups within the session.
The credit pool concept is an optimal tool to avoid the over- The credit pool concept is an optimal tool to avoid the over-
reservation effect of the basic single quota tariff time change reservation effect of the basic single quota tariff time change
mechanism (the mechanism described in Section 5.1.1). Therefore, mechanism (the mechanism described in Section 5.1.1). Therefore,
Diameter credit-control clients and servers implementing the Diameter credit-control clients and servers implementing the
skipping to change at page 22, line 31 skipping to change at page 22, line 34
When session based credit-control is required (e.g., the When session based credit-control is required (e.g., the
authentication server indicated a prepaid user), the first authentication server indicated a prepaid user), the first
interrogation MUST be sent before the Diameter credit-control client interrogation MUST be sent before the Diameter credit-control client
allows any service event to the end user. The CC-Request-Type is set allows any service event to the end user. The CC-Request-Type is set
to the value INITIAL_REQUEST in the request message. to the value INITIAL_REQUEST in the request message.
If the Diameter credit-control client knows the cost of the service If the Diameter credit-control client knows the cost of the service
event (e.g., a content server delivering ringing tones may know their event (e.g., a content server delivering ringing tones may know their
cost) the monetary amount to be charged is included in the Requested- cost) the monetary amount to be charged is included in the Requested-
Service-Unit AVP. If the Diameter credit-control client does not Service-Unit AVP. If the Diameter credit-control client does not
know the cost of the service event, the Requested-Service- Unit AVP know the cost of the service event, the Requested-Service-Unit AVP
MAY contain the number of requested service events. Where the MAY contain the number of requested service events. Where the
Multiple-Services-Credit-Control AVP is used, it MUST contain the Multiple-Services-Credit-Control AVP is used, it MUST contain the
Requested-Service-Unit AVP to indicate that the quota for the Requested-Service-Unit AVP to indicate that the quota for the
associated service/rating-group is requested. In the case of associated service/rating-group is requested. In the case of
multiple services, the Service-Identifier AVP or the Rating-Group AVP multiple services, the Service-Identifier AVP or the Rating-Group AVP
within the Multiple-Services-Credit-Control AVP always indicates the within the Multiple-Services-Credit-Control AVP always indicates the
service concerned. Additional service event information to be rated service concerned. Additional service event information to be rated
MAY be sent as service specific AVPs or MAY be sent within the MAY be sent as service specific AVPs or MAY be sent within the
Service-Parameter-Info AVP at command level. The Service-Context-Id Service-Parameter-Info AVP at command level. The Service-Context-Id
AVP indicates the service specific document applicable to the AVP indicates the service specific document applicable to the
request. request.
The Event-Timestamp AVP SHOULD be included in the request and The Event-Timestamp AVP SHOULD be included in the request and
contains the time when the service event is requested in the service contains the time when the service event is requested in the service
element. The Subscription-Id AVP SHOULD be included to identify the element. The Subscription-Id AVP or the Subscription-Id-Extension
end user in the credit-control server. The credit-control client MAY AVP SHOULD be included to identify the end user in the credit-control
include the User-Equipment-Info AVP so that the credit-control server server. The credit-control client MAY include the User-Equipment-
has some indication of the type and capabilities of the end user Info AVP or User-Equipment-Info-Extension AVP so that the credit-
access device. How the credit-control server uses this information control server has some indication of the type and capabilities of
is outside the scope of this document. the end user access device. How the credit-control server uses this
information is outside the scope of this document.
The credit-control server SHOULD rate the service event and make a The credit-control server SHOULD rate the service event and make a
credit-reservation from the end user's account that covers the cost credit-reservation from the end user's account that covers the cost
of the service event. If the type of the Requested-Service-Unit AVP of the service event. If the type of the Requested-Service-Unit AVP
is money, no rating is needed, but the corresponding monetary amount is money, no rating is needed, but the corresponding monetary amount
is reserved from the end user's account. is reserved from the end user's account.
The credit-control server returns the Granted-Service-Unit AVP in the The credit-control server returns the Granted-Service-Unit AVP in the
Answer message to the Diameter credit-control client. The Granted- Answer message to the Diameter credit-control client. The Granted-
Service-Unit AVP contains the amount of service units that the Service-Unit AVP contains the amount of service units that the
skipping to change at page 23, line 38 skipping to change at page 23, line 42
server wants to make a distinction between the granted quota before server wants to make a distinction between the granted quota before
and after tariff change. and after tariff change.
If the credit-control server determines that no further control is If the credit-control server determines that no further control is
needed for the service, it MAY include the result code indicating needed for the service, it MAY include the result code indicating
that the credit-control is not applicable (e.g., if the service is that the credit-control is not applicable (e.g., if the service is
free of charge). This result code at command level implies that the free of charge). This result code at command level implies that the
credit-control session is to be terminated. credit-control session is to be terminated.
The Credit-Control-Answer message MAY also include the Final-Unit- The Credit-Control-Answer message MAY also include the Final-Unit-
Indication AVP to indicate that the answer message contains the final Indication AVP or the QoS-Final-Unit-Indication AVP to indicate that
units for the service. After the end user has consumed these units, the answer message contains the final units for the service. After
the Diameter credit-control-client MUST behave as described in the end user has consumed these units, the Diameter credit-control-
Section 5.6. client MUST behave as described in Section 5.6.
This document defines two different approaches to perform the first This document defines two different approaches to perform the first
interrogation to be used in different network architectures. The interrogation to be used in different network architectures. The
first approach uses credit-control messages after the user's first approach uses credit-control messages after the user's
authorization and authentication takes place. The second approach authorization and authentication takes place. The second approach
uses service specific authorization messages to perform the first uses service specific authorization messages to perform the first
interrogation during the user's authorization/authentication phase, interrogation during the user's authorization/authentication phase,
and credit-control messages for the intermediate and final and credit-control messages for the intermediate and final
interrogations. If an implementation of the credit-control client interrogations. If an implementation of the credit-control client
supports both the methods, determining which method to use SHOULD be supports both the methods, determining which method to use SHOULD be
skipping to change at page 24, line 25 skipping to change at page 24, line 30
received request forward to the credit-control server. received request forward to the credit-control server.
In other service environments, such as the 3GPP network and some SIP In other service environments, such as the 3GPP network and some SIP
scenarios, there is a substantial decoupling between registration/ scenarios, there is a substantial decoupling between registration/
access to the network and the actual service request (i.e., the access to the network and the actual service request (i.e., the
authentication/authorization is executed once at registration/access authentication/authorization is executed once at registration/access
to the network and is not executed for every service event requested to the network and is not executed for every service event requested
by the subscriber). In these environments, it is more appropriate to by the subscriber). In these environments, it is more appropriate to
perform the first interrogation after the user has been authenticated perform the first interrogation after the user has been authenticated
and authorized. The first, the intermediate, and the final and authorized. The first, the intermediate, and the final
interrogations are executed with credit- control commands defined in interrogations are executed with credit-control commands defined in
this specification. this specification.
Other IETF standards or standards developed by other standardization Other IETF standards or standards developed by other standardization
bodies may define the most suitable method in their architectures. bodies may define the most suitable method in their architectures.
5.2.1. First Interrogation after Authorization and Authentication 5.2.1. First Interrogation after Authorization and Authentication
The Diameter credit-control client in the service element may get The Diameter credit-control client in the service element may get
information from the authorization server as to whether credit- information from the authorization server as to whether credit-
control is required, based on its knowledge of the end user. If control is required, based on its knowledge of the end user. If
skipping to change at page 26, line 4 skipping to change at page 26, line 4
5.2.2. Authorization Messages for First Interrogation 5.2.2. Authorization Messages for First Interrogation
The Diameter credit-control client in the service element MUST The Diameter credit-control client in the service element MUST
actively co-operate with the authorization/authentication client in actively co-operate with the authorization/authentication client in
the construction of the AA request by adding appropriate credit- the construction of the AA request by adding appropriate credit-
control AVPs. The credit-control client MUST add the Credit-Control control AVPs. The credit-control client MUST add the Credit-Control
AVP to indicate credit-control capabilities and MAY add other AVP to indicate credit-control capabilities and MAY add other
relevant credit-control specific AVPs to the proper authorization/ relevant credit-control specific AVPs to the proper authorization/
authentication command to perform the first interrogation toward the authentication command to perform the first interrogation toward the
home Diameter AAA server. The Auth- Application-Id is set to the home Diameter AAA server. The Auth-Application-Id is set to the
appropriate value, as defined in the relevant service specific appropriate value, as defined in the relevant service specific
authorization/authentication application document (e.g., [RFC7155], authorization/authentication application document (e.g., [RFC7155],
[RFC4004]). The home Diameter AAA server authenticates/authorizes [RFC4004]). The home Diameter AAA server authenticates/authorizes
the subscriber and determines whether credit-control is required. the subscriber and determines whether credit-control is required.
If credit-control is not required for the subscriber, the home If credit-control is not required for the subscriber, the home
Diameter AAA server will respond as usual, with an appropriate AA Diameter AAA server will respond as usual, with an appropriate AA
answer message. If credit-control is required for the subscriber and answer message. If credit-control is required for the subscriber and
the Credit-Control AVP with the value set to CREDIT_AUTHORIZATION was the Credit-Control AVP with the value set to CREDIT_AUTHORIZATION was
present in the authorization request, the home AAA server MUST present in the authorization request, the home AAA server MUST
skipping to change at page 29, line 25 skipping to change at page 29, line 25
When the used units are reported to the credit-control server, the When the used units are reported to the credit-control server, the
credit-control client will not have any units in its possession credit-control client will not have any units in its possession
before new granted units are received from the credit-control server. before new granted units are received from the credit-control server.
When the new granted units are received, these units apply from the When the new granted units are received, these units apply from the
point where the measurement of the reported used units stopped. point where the measurement of the reported used units stopped.
Where independent credit-control of multiple services is supported, Where independent credit-control of multiple services is supported,
this process may be executed for one or more services, a single this process may be executed for one or more services, a single
rating-group, or a pool within the (sub)session. rating-group, or a pool within the (sub)session.
The CC-Request-Type AVP is set to the value UPDATE_REQUEST in the The CC-Request-Type AVP is set to the value UPDATE_REQUEST in the
intermediate request message. The Subscription-Id AVP SHOULD be intermediate request message. The Subscription-Id AVP or
included in the intermediate message to identify the end user in the Subscription-Id-Extension AVP SHOULD be included in the intermediate
credit-control server. The Service-Context-Id AVP indicates the message to identify the end user in the credit-control server. The
service specific document applicable to the request. Service-Context-Id AVP indicates the service specific document
applicable to the request.
The Requested-Service-Unit AVP MAY contain the new amount of The Requested-Service-Unit AVP MAY contain the new amount of
requested service units. Where the Multiple-Services-Credit-Control requested service units. Where the Multiple-Services-Credit-Control
AVP is used, it MUST contain the Requested-Service-Unit AVP if a new AVP is used, it MUST contain the Requested-Service-Unit AVP if a new
quota is requested for the associated service/rating-group. The quota is requested for the associated service/rating-group. The
Used-Service-Unit AVP contains the amount of used service units Used-Service-Unit AVP contains the amount of used service units
measured from the point when the service became active or, if interim measured from the point when the service became active or, if interim
interrogations are used during the session, from the point when the interrogations are used during the session, from the point when the
previous measurement ended. The same unit types used in the previous previous measurement ended. The same unit types used in the previous
message SHOULD be used. If several unit types were included in the message SHOULD be used. If several unit types were included in the
skipping to change at page 30, line 11 skipping to change at page 30, line 11
user's account. It MAY rate the new request and make a new credit- user's account. It MAY rate the new request and make a new credit-
reservation from the end user's account that covers the cost of the reservation from the end user's account that covers the cost of the
requested service event. requested service event.
A Credit-Control-Answer message with the CC-Request-Type AVP set to A Credit-Control-Answer message with the CC-Request-Type AVP set to
the value UPDATE_REQUEST MAY include the Cost-Information AVP the value UPDATE_REQUEST MAY include the Cost-Information AVP
containing the accumulated cost estimation for the session, without containing the accumulated cost estimation for the session, without
taking any credit-reservation into account. taking any credit-reservation into account.
The Credit-Control-Answer message MAY also include the Final-Unit- The Credit-Control-Answer message MAY also include the Final-Unit-
Indication AVP to indicate that the answer message contains the final Indication AVP or the QoS-Final-Unit-Indication AVP to indicate that
units for the service. After the end user has consumed these units, the answer message contains the final units for the service. After
the Diameter credit-control-client MUST behave as described in the end user has consumed these units, the Diameter credit-control-
Section 5.6. client MUST behave as described in Section 5.6.
There can be several intermediate interrogations within a session. There can be several intermediate interrogations within a session.
5.4. Final Interrogation 5.4. Final Interrogation
When the end user terminates the service session, or when the When the end user terminates the service session, or when the
graceful service termination described in Section 5.6 takes place, graceful service termination described in Section 5.6 takes place,
the Diameter credit-control client MUST send a final Credit-Control- the Diameter credit-control client MUST send a final Credit-Control-
Request message to the credit-control server. The CC-Request-Type Request message to the credit-control server. The CC-Request-Type
AVP is set to the value TERMINATION_REQUEST. The Service-Context-Id AVP is set to the value TERMINATION_REQUEST. The Service-Context-Id
skipping to change at page 31, line 42 skipping to change at page 31, line 42
| | STA | | | | STA | |
| |<-------------------| | | |<-------------------| |
Figure 5: User disconnected due to exhausted account Figure 5: User disconnected due to exhausted account
5.5. Server-Initiated Credit Re-Authorization 5.5. Server-Initiated Credit Re-Authorization
The Diameter credit-control application supports server-initiated re- The Diameter credit-control application supports server-initiated re-
authorization. The credit-control server MAY optionally initiate the authorization. The credit-control server MAY optionally initiate the
credit re-authorization by issuing a Re-Auth-Request (RAR) as defined credit re-authorization by issuing a Re-Auth-Request (RAR) as defined
in the Diameter base protocol [RFC6733]. The Auth- Application-Id in in the Diameter base protocol [RFC6733]. The Auth-Application-Id in
the RAR message is set to 4 to indicate Diameter Credit Control, and the RAR message is set to 4 to indicate Diameter Credit Control, and
the Re-Auth-Request-Type is set to AUTHORIZE_ONLY. the Re-Auth-Request-Type is set to AUTHORIZE_ONLY.
Section 5.1.2 defines the feature to enable credit-control for Section 5.1.2 defines the feature to enable credit-control for
multiple services within a single (sub-)session where the server can multiple services within a single (sub-)session where the server can
authorize credit usage at a different level of granularity. Further, authorize credit usage at a different level of granularity. Further,
the server may provide credit resources to multiple services or the server may provide credit resources to multiple services or
rating groups as a pool (see Section 5.1.2 for details and rating groups as a pool (see Section 5.1.2 for details and
definitions). Therefore, the server, based on its service logic and definitions). Therefore, the server, based on its service logic and
its knowledge of the ongoing session, can decide to request credit its knowledge of the ongoing session, can decide to request credit
skipping to change at page 33, line 31 skipping to change at page 33, line 31
When the user's account runs out of money, the user may not be When the user's account runs out of money, the user may not be
allowed to compile additional chargeable events. However, the home allowed to compile additional chargeable events. However, the home
service provider may offer some services; for instance, access to a service provider may offer some services; for instance, access to a
service portal where it is possible to refill the account, for which service portal where it is possible to refill the account, for which
the user is allowed to benefit for a limited time. The length of the user is allowed to benefit for a limited time. The length of
this time is usually dependent on the home service provider policy. this time is usually dependent on the home service provider policy.
This section defines the optional graceful service termination This section defines the optional graceful service termination
feature that MAY be supported by the credit-control server. Credit- feature that MAY be supported by the credit-control server. Credit-
control client implementations MUST support the Final-Unit-Indication control client implementations MUST support the Final-Unit-Indication
with at least the teardown of the ongoing service session once the AVP or QoS-Final-Unit-Indication AVP with at least the teardown of
subscriber has consumed all the final granted units. the ongoing service session once the subscriber has consumed all the
final granted units.
Where independent credit-control of multiple services in a single Where independent credit-control of multiple services in a single
credit-control (sub-)session is supported, it is possible to use the credit-control (sub-)session is supported, it is possible to use the
graceful service termination for each of the services/rating-groups graceful service termination for each of the services/rating-groups
independently. Naturally, the graceful service termination process independently. Naturally, the graceful service termination process
defined in the following sub-sections will apply to the specific defined in the following sub-sections will apply to the specific
service/rating-group as requested by the server. service/rating-group as requested by the server.
In some service environments (e.g., NAS), the graceful service In some service environments (e.g., NAS), the graceful service
termination may be used to redirect the subscriber to a service termination may be used to redirect the subscriber to a service
skipping to change at page 34, line 12 skipping to change at page 34, line 13
These actions may be communicated explicitly from the server to the These actions may be communicated explicitly from the server to the
client or may be configured per-service at the client. Explicitly client or may be configured per-service at the client. Explicitly
signaled redirect or restrict instructions always take precedence signaled redirect or restrict instructions always take precedence
over configured ones. over configured ones.
It is also possible use the graceful service termination to connect It is also possible use the graceful service termination to connect
the prepaid user to a top-up server that plays an announcement and the prepaid user to a top-up server that plays an announcement and
prompts the user to replenish the account. In this case, the credit- prompts the user to replenish the account. In this case, the credit-
control server sends only the address of the top-up server where the control server sends only the address of the top-up server where the
prepaid user shall be connected after the final granted units have prepaid user shall be connected after the final granted units have
been consumed. An example of this is given in Appendix A (Flow VII). been consumed. An example of this is given Appendix B.7.
The credit-control server MAY initiate the graceful service The credit-control server MAY initiate the graceful service
termination by including the Final-Unit-Indication AVP in the Credit- termination by including the Final-Unit-Indication AVP or the QoS-
Control-Answer to indicate that the message contains the final units Final-Unit-Indication AVP in the Credit-Control-Answer to indicate
for the service. that the message contains the final units for the service.
When the credit-control client receives the Final-Unit-Indication AVP When the credit-control client receives the Final-Unit-Indication AVP
in the answer from the server, its behavior depends on the value or the QoS-Final-Unit-Indication AVP in the answer from the server,
indicated in the Final-Unit-Action AVP. The server may request the its behavior depends on the value indicated in the Final-Unit-Action
following actions: TERMINATE, REDIRECT, or RESTRICT_ACCESS. AVP. The server may request the following actions: TERMINATE,
REDIRECT, or RESTRICT_ACCESS.
A following figure illustrates the graceful service termination The following figure illustrates the graceful service termination
procedure described in the following sub-sections. procedure described in the following sub-sections.
Diameter Diameter
End User Service Element AAA Server CC Server End User Service Element AAA Server CC Server
(CC Client) (CC Client)
| Service Delivery | | | | Service Delivery | | |
|<----------------->| | | |<----------------->| | |
| |CCR(Update,Used-Units) | | |CCR(Update,Used-Units) |
| |------------------->|CCR(Update,Used-Units) | |------------------->|CCR(Update,Used-Units)
| : | |------------------->| | : | |------------------->|
skipping to change at page 35, line 26 skipping to change at page 36, line 4
| Restrictions ->+ |<===================| | | Restrictions ->+ |<===================| |
| removed | | | | removed | | |
| : | | | | : | | |
| OR | CCR(Update) | | | OR | CCR(Update) | |
| Validity-Time ->|------------------->| CCR(Update) | | Validity-Time ->|------------------->| CCR(Update) |
| expires | |------------------->| | expires | |------------------->|
| | | CCA(Granted-Unit)| | | | CCA(Granted-Unit)|
| | CCA(Granted-Unit)|<-------------------| | | CCA(Granted-Unit)|<-------------------|
| Restrictions ->|<-------------------| | | Restrictions ->|<-------------------| |
| removed | | | | removed | | |
Figure 6: Optional graceful service termination procedure Figure 6: Optional graceful service termination procedure
In addition, the credit-control server MAY reply with Final-Unit-
Indication AVP or QoS-Final-Unit-Indication AVP holding a G-S-U AVP
with a zero grant, indicating that the service SHOULD be terminated
immediately, and no further reporting is required. A following
figure illustrates a graceful service termination procedure that
applies immediately after receiving a zero grant.
Diameter
End User Service Element AAA Server CC Server
(CC Client)
| Service Delivery | | |
|<----------------->| | |
| |CCR(Update,Used-Units) |
| |------------------->|CCR(Update,Used-Units)
| : | |------------------->|
| : | |CCA(Final-Unit,Action,
| : | | Zero G-S-U)
| : | |<-------------------|
| |CCA(Final-Unit,Action, |
| | Zero G-S-U) |
| |<-------------------| |
| /////////////// | | |
|/Action and // | | |
|/Restrictions // | | |
|/Start // | | |
| ///////////// | | |
| : | | |
| : | | |
Figure 7: Optional immediate graceful service termination procedure
5.6.1. Terminate Action 5.6.1. Terminate Action
The Final-Unit-Indication AVP with Final-Unit-Action TERMINATE does The Final-Unit-Indication AVP or the QoS-Final-Unit-Indication AVP
not include any other information. When the subscriber has consumed with Final-Unit-Action TERMINATE does not include any other
the final granted units, the service element MUST terminate the information. When the subscriber has consumed the final granted
service. This is the default handling applicable whenever the units, the service element MUST terminate the service. This is the
credit-control client receives an unsupported Final-Unit-Action value default handling applicable whenever the credit-control client
and MUST be supported by all the Diameter credit-control client receives an unsupported Final-Unit-Action value and MUST be supported
implementations conforming to this specification. A final Credit- by all the Diameter credit-control client implementations conforming
Control-Request message to the credit-control server MUST be sent if to this specification. A final Credit-Control-Request message to the
the Final-Unit-Indication AVP indicating action TERMINATE was present credit-control server MUST be sent if the Final-Unit-Indication AVP
at command level. The CC-Request-Type AVP in the request is set to or the QoS-Final-Unit-Indication AVP indicating action TERMINATE was
the value TERMINATION_REQUEST. present at command level. The CC-Request-Type AVP in the request is
set to the value TERMINATION_REQUEST.
5.6.2. Redirect Action 5.6.2. Redirect Action
The Final-Unit-Indication AVP with Final-Unit-Action REDIRECT The Final-Unit-Indication AVP or the QoS-Final-Unit-Indication AVP
indicates to the service element supporting this action that, upon with Final-Unit-Action REDIRECT indicates to the service element
consumption of the final granted units, the user MUST be re-directed supporting this action that, upon consumption of the final granted
to the address specified in the Redirect-Server AVP as follows. units, the user MUST be re-directed to the address specified in the
Redirect-Server AVP or Redirect-Server-Extension AVP as follows.
The credit-control server sends the Redirect-Server AVP in the The credit-control server sends the Redirect-Server AVP or Redirect-
Credit-Control-Answer message. In such a case, the service element Server-Extension AVP in the Credit-Control-Answer message. In such a
MUST redirect or connect the user to the destination specified in the case, the service element MUST redirect or connect the user to the
Redirect-Server AVP, if possible. When the end user is redirected destination specified in the Redirect-Server AVP or Redirect-Server-
(by using protocols others than Diameter) to the specified server or Extension AVP, if possible. When the end user is redirected (by
using protocols others than Diameter) to the specified server or
connected to the top-up server, an additional authorization (and connected to the top-up server, an additional authorization (and
possibly authentication) may be needed before the subscriber can possibly authentication) may be needed before the subscriber can
replenish the account; however, this is out of the scope of this replenish the account; however, this is out of the scope of this
specification. specification.
In addition to the Redirect-Server AVP, the credit-control server MAY In addition to the Redirect-Server AVP or Redirect-Server-Extension
include one or more Restriction-Filter-Rule AVPs or one or more AVP, the credit-control server MAY include one or more Restriction-
Filter-Rule AVPs, one or more Filter-Rule AVPs, or one or more
Filter-Id AVPs in the Credit-Control-Answer message to enable the Filter-Id AVPs in the Credit-Control-Answer message to enable the
user to access other services (for example, zero-rated services). In user to access other services (for example, zero-rated services). In
such a case, the access device MUST drop all the packets not matching such a case, the access device MUST drop all the packets not matching
the IP filters specified in the Credit-Control-Answer message and, if the IP filters specified in the Restriction-Filter-Rule AVPs, Filter-
possible, redirect the user to the destination specified in the Rule AVPs or Filter-Id AVPs. If enforcement actions other than
Redirect-Server AVP. allowing the packets (e.g., QoS), are indicated in the Filter-Rule
AVPs or Filter-Id AVPs, they SHOULD be performed as well. In
addition, if possible, to redirecting the user to the destination
specified in the Redirect-Server AVP or Redirect-Server-Extension
AVP.
An entity other than the credit-control server may provision the An entity other than the credit-control server may provision the
access device with appropriate IP packet filters to be used in access device with appropriate IP packet filters to be used in
conjunction with the Diameter credit-control application. This case conjunction with the Diameter credit-control application. This case
is considered in Section 5.6.3. is considered in Section 5.6.3.
When the final granted units have been consumed, the credit-control When the final granted units have been consumed, the credit-control
client MUST perform an intermediate interrogation. The purpose of client MUST perform an intermediate interrogation. The purpose of
this interrogation is to indicate to the credit-control server that this interrogation is to indicate to the credit-control server that
the specified action started and to report the used units. The the specified action started and to report the used units. The
skipping to change at page 37, line 22 skipping to change at page 38, line 38
Answer message in order to implement the policy-defined action. Answer message in order to implement the policy-defined action.
Otherwise, new quota will be returned, the service element MUST Otherwise, new quota will be returned, the service element MUST
remove all the possible restrictions activated by the graceful remove all the possible restrictions activated by the graceful
service termination process and continue the credit-control session service termination process and continue the credit-control session
and service session as usual. and service session as usual.
The credit-control client may not wait until the expiration of the The credit-control client may not wait until the expiration of the
Validity-Time and may send a spontaneous update (a new Credit- Validity-Time and may send a spontaneous update (a new Credit-
Control-Request) if the service element can determine, for instance, Control-Request) if the service element can determine, for instance,
that communication between the end user and the top-up server took that communication between the end user and the top-up server took
place. An example of this is given in Appendix A (Figure A.8). place. An example of this is given in Appendix B.8 (Figure 18).
Note that the credit-control server may already have initiated the Note that the credit-control server may already have initiated the
above-described process for the first interrogation. However, the above-described process for the first interrogation. However, the
user's account might be empty when this first interrogation is user's account might be empty when this first interrogation is
performed. In this case, the subscriber can be offered a chance to performed. In this case, the subscriber can be offered a chance to
replenish the account and continue the service. The credit-control replenish the account and continue the service. The credit-control
client receives a Credit-Control-Answer or service specific client receives a Credit-Control-Answer or service specific
authorization answer with the Final-Unit-Indication and Validity-Time authorization answer with the Final-Unit-Indication or the QoS-Final-
AVPs but no Granted-Service-Unit AVP. It immediately starts the Unit-Indication AVP and Validity-Time AVPs but no Granted-Service-
graceful service termination without sending any message to the Unit AVP. It immediately starts the graceful service termination
server. An example of this case is illustrated in Appendix A. without sending any message to the server. An example of this case
is illustrated in Appendix B.
5.6.3. Restrict Access Action 5.6.3. Restrict Access Action
A Final-Unit-Indication AVP with the Final-Unit-Action A Final-Unit-Indication AVP with the Final-Unit-Action
RESTRICT_ACCESS indicates to the device supporting this action that RESTRICT_ACCESS indicates to the device supporting this action that,
the user's access MUST be restricted according to the IP packet upon consumption of the final granted units, the user's access MUST
filters given in the Restriction-Filter-Rule AVP(s) or according to be restricted according to the IP packet filters given in the
the IP packet filters identified by the Filter-Id AVP(s). The Restriction-Filter-Rule AVP(s) or according to the IP packet filters
credit-control server SHOULD include either the Restriction-Filter- identified by the Filter-Id AVP(s). The credit-control server SHOULD
Rule AVP or the Filter-Id AVP in the Credit-Control-Answer message. include either the Restriction-Filter-Rule AVP or the Filter-Id AVP
in the Credit-Control-Answer message.
A QoS-Final-Unit-Indication AVP with the Final-Unit-Action
RESTRICT_ACCESS indicates to the device supporting this action that,
upon consumption of the final granted units, the actions specified in
Filter-Rule AVP(s) MUST restrict the traffic according to the
classifiers in the Filter-Rule AVP(s). If Filter-Id AVP(s) are
provided in the Credit-Control-Answer message, the credit control
client MUST restrict the traffic according to the IP packet filters
identified by the Filter-Id AVP(s). The credit-control server SHOULD
include either the Filter-Rule AVP or the Filter-Id AVP in the
Credit-Control-Answer message.
If both Final-Unit-Indication AVP and QoS-Final-Unit-Indication AVP
exist in the Credit-Control-Answer message, a credit control client
which supports the QoS-Final-Unit-Indication AVP SHOULD follow the
directives included in it.
An entity other than the credit-control server may provision the An entity other than the credit-control server may provision the
access device with appropriate IP packet filters to be used in access device with appropriate IP packet filters to be used in
conjunction with the Diameter credit-control application. Such an conjunction with the Diameter credit-control application. Such an
entity may, for instance, configure the access device with IP flows entity may, for instance, configure the access device with IP flows
to be passed when the Diameter credit-control application indicates to be passed when the Diameter credit-control application indicates
RESTRICT_ACCESS or REDIRECT. The access device passes IP packets RESTRICT_ACCESS or REDIRECT. The access device passes IP packets
according to the filter rules that may have been received in the according to the filter rules that may have been received in the
Credit-Control-Answer message in addition to those that may have been Credit-Control-Answer message in addition to those that may have been
configured by the other entity. However, when the user's account configured by the other entity. However, when the user's account
cannot cover the cost of the requested service, the action taken is cannot cover the cost of the requested service, the action taken is
the responsibility of the credit-control server that controls the the responsibility of the credit-control server that controls the
prepaid subscriber. prepaid subscriber.
If another entity working in conjunction with the Diameter credit- If another entity working in conjunction with the Diameter credit-
control application already provisions the access device with all the control application already provisions the access device with all the
required filter rules for the end user, the credit-control server required filter rules for the end user, the credit-control server
presumably need not send any additional filter. Therefore, it is presumably need not send any additional filter. Therefore, it is
RECOMMENDED that credit-control server implementations supporting the RECOMMENDED that credit-control server implementations supporting the
graceful service termination be configurable for sending the graceful service termination be configurable for sending the
Restriction-Filter-Rule AVP, the Filter-Id AVP, or none of the above. Restriction-Filter-Rule AVP, the Filter-Rule AVP, the Filter-Id AVP,
or none of the above.
When the final granted units have been consumed, the credit-control When the final granted units have been consumed, the credit-control
client MUST perform an intermediate interrogation. The credit- client MUST perform an intermediate interrogation. The credit-
control client and the credit-control server process this control client and the credit-control server process this
intermediate interrogation and execute subsequent procedures, as intermediate interrogation and execute subsequent procedures, as
specified in the previous section for the REDIRECT action. specified in the previous section for the REDIRECT action.
The credit-control server may initiate the graceful service The credit-control server may initiate the graceful service
termination with action RESTRICT_ACCESS already for the first termination with action RESTRICT_ACCESS already for the first
interrogation, as specified in the previous section for the REDIRECT interrogation, as specified in the previous section for the REDIRECT
action. action.
5.6.4. Usage of the Server-Initiated Credit Re-Authorization 5.6.4. Usage of the Server-Initiated Credit Re-Authorization
Once the subscriber replenishes the account, she presumably expects Once the subscriber replenishes the account, she presumably expects
all the restrictions placed by the graceful termination procedure to all the restrictions placed by the graceful termination procedure to
be removed immediately and unlimited service' access to be resumed. be removed immediately and unlimited service access to be resumed.
For the best user experience, the credit-control server For the best user experience, the credit-control server
implementation MAY support the server-initiated credit re- implementation MAY support the server-initiated credit re-
authorization (see Section 5.5). In such a case, upon the successful authorization (see Section 5.5). In such a case, upon the successful
account top-up, the credit-control server sends the Re-Auth-Request account top-up, the credit-control server sends the Re-Auth-Request
(RAR) message to solicit the credit re-authorization. The credit- (RAR) message to solicit the credit re-authorization. The credit-
control client initiates the credit re-authorization by sending the control client initiates the credit re-authorization by sending the
Credit-Control-Request message with the CC-Request-Type AVP set to Credit-Control-Request message with the CC-Request-Type AVP set to
the value UPDATE_REQUEST. The Used-Service-Unit AVP is not included the value UPDATE_REQUEST. The Used-Service-Unit AVP is not included
in the request, as there is no allotted quota to report. The in the request, as there is no allotted quota to report. The
Requested-Service-Unit AVP MAY be included in the request. After the Requested-Service-Unit AVP MAY be included in the request. After the
skipping to change at page 39, line 25 skipping to change at page 41, line 8
The authorization server MAY include the Accounting-Realtime-Required The authorization server MAY include the Accounting-Realtime-Required
AVP to determine what to do if the sending of accounting records to AVP to determine what to do if the sending of accounting records to
the accounting server has been temporarily prevented, as defined in the accounting server has been temporarily prevented, as defined in
[RFC6733]. It is RECOMMENDED that the client complement the credit- [RFC6733]. It is RECOMMENDED that the client complement the credit-
control failure procedures with backup accounting flow toward an control failure procedures with backup accounting flow toward an
accounting server. By using different combinations of Accounting- accounting server. By using different combinations of Accounting-
Realtime-Required and Credit-Control-Failure-Handling AVPs, different Realtime-Required and Credit-Control-Failure-Handling AVPs, different
safety levels can be built. For example, by choosing a Credit- safety levels can be built. For example, by choosing a Credit-
Control-Failure-Handling AVP equal to CONTINUE for the credit-control Control-Failure-Handling AVP equal to CONTINUE for the credit-control
flow and a Accounting-Realtime-Required AVP equal to flow and an Accounting-Realtime-Required AVP equal to
DELIVER_AND_GRANT for the accounting flow, the service can be granted DELIVER_AND_GRANT for the accounting flow, the service can be granted
to the end user even if the connection to the credit-control server to the end user even if the connection to the credit-control server
is down, as long as the accounting server is able to collect the is down, as long as the accounting server is able to collect the
accounting information and information exchange is taking place accounting information and information exchange is taking place
between the accounting server and credit-control server. between the accounting server and credit-control server.
As the credit-control application is based on real-time bi- As the credit-control application is based on real-time bi-
directional communication between the credit-control client and the directional communication between the credit-control client and the
credit-control server, the usage of alternative destinations and the credit-control server, the usage of alternative destinations and the
buffering of messages may not be sufficient in the event of buffering of messages may not be sufficient in the event of
skipping to change at page 40, line 50 skipping to change at page 42, line 34
When Tx expires, the Diameter credit-control client always terminates When Tx expires, the Diameter credit-control client always terminates
the service if the Credit-Control-Failure-Handling (CCFH) AVP is set the service if the Credit-Control-Failure-Handling (CCFH) AVP is set
to the value TERMINATE. The credit-control session may be moved to to the value TERMINATE. The credit-control session may be moved to
an alternative server only if a protocol error DIAMETER_TOO_BUSY or an alternative server only if a protocol error DIAMETER_TOO_BUSY or
DIAMETER_UNABLE_TO_DELIVER is received before Tx expires. Therefore, DIAMETER_UNABLE_TO_DELIVER is received before Tx expires. Therefore,
the value TERMINATE is not appropriate if proper failover behavior is the value TERMINATE is not appropriate if proper failover behavior is
desired. desired.
If the Credit-Control-Failure-Handling AVP is set to the value If the Credit-Control-Failure-Handling AVP is set to the value
CONTINUE or RETRY_AND_TERMINATE, the service will be granted to the CONTINUE or RETRY_AND_TERMINATE, the service will be granted to the
end user when the timer Tx expires. An answer message with granted- end user when the timer Tx expires. An answer message with granted
units may arrive later if the base protocol transport failover units may arrive later if the base protocol transport failover
occurred in the path to the credit-control server. (The Twinit occurred in the path to the credit-control server. (The Twinit
default value is 3 times more than the Tx recommended value.) The default value is 3 times more than the Tx recommended value.) The
credit-control client SHOULD grant the service to the end user, start credit-control client SHOULD grant the service to the end user, start
monitoring the resource usage, and wait for the possible late answer monitoring the resource usage, and wait for the possible late answer
until the timeout of the request (e.g., 120 seconds). If the request until the timeout of the request (e.g., 120 seconds). If the request
fails and the CC-Session-Failover AVP is set to fails and the CC-Session-Failover AVP is set to
FAILOVER_NOT_SUPPORTED, the credit-control client terminates or FAILOVER_NOT_SUPPORTED, the credit-control client terminates or
continues the service depending on the value set in the CCFH and MUST continues the service depending on the value set in the CCFH and MUST
free all the reserved resources for the credit-control session. If free all the reserved resources for the credit-control session. If
skipping to change at page 41, line 50 skipping to change at page 43, line 34
regarded as an implementation issue and is outside of the scope of regarded as an implementation issue and is outside of the scope of
this specification. this specification.
6. One Time Event 6. One Time Event
The one-time event is used when there is no need to maintain any The one-time event is used when there is no need to maintain any
state in the Diameter credit-control server; for example, enquiring state in the Diameter credit-control server; for example, enquiring
about the price of the service. The use of a one-time event implies about the price of the service. The use of a one-time event implies
that the user has been authenticated and authorized beforehand. that the user has been authenticated and authorized beforehand.
The one time event can be used when the credit-control client wants The one-time event can be used when the credit-control client wants
to know the cost of the service event or to check the account balance to know the cost of the service event or to check the account balance
without any credit-reservation. It can also be used for refunding without any credit-reservation. It can also be used for refunding
service units on the user's account or for direct debiting withouts service units on the user's account or for direct debiting without
any credit-reservation. The one time event is shown in Figure 7. any credit-reservation. The one-time event is shown in Figure 8.
Diameter Diameter
End User Service Element AAA Server CC Server End User Service Element AAA Server CC Server
(CC Client) (CC Client)
| Service Request | | | | Service Request | | |
|------------------>| | | |------------------>| | |
| | CCR(Event) | | | | CCR(Event) | |
| |------------------->| CCR(Event) | | |------------------->| CCR(Event) |
| | |------------------->| | | |------------------->|
| | | CCA(Granted-Units)| | | | CCA(Granted-Units)|
| | CCA(Granted-Units)|<-------------------| | | CCA(Granted-Units)|<-------------------|
| Service Delivery |<-------------------| | | Service Delivery |<-------------------| |
|<----------------->| | | |<----------------->| | |
Figure 7: One time event Figure 8: One time event
In environments such as the 3GPP architecture, the one time event can In environments such as the 3GPP architecture, the one-time event can
be sent from the service element directly to the credit-control be sent from the service element directly to the credit-control
server. server.
6.1. Service Price Enquiry 6.1. Service Price Enquiry
The credit-control client may need to know the price of the services The credit-control client may need to know the price of the services
event. Services offered by application service providers whose event. Services offered by application service providers whose
prices are not known in the credit-control client might exist. The prices are not known in the credit-control client might exist. The
end user might also want to get an estimation of the price of a end user might also want to get an estimation of the price of a
service event before requesting it. service event before requesting it.
A Diameter credit-control client requesting the cost information MUST A Diameter credit-control client requesting the cost information MUST
set the CC-Request-Type AVP equal to EVENT_REQUEST, include the set the CC-Request-Type AVP equal to EVENT_REQUEST, include the
Requested-Action AVP set to PRICE_ENQUIRY, and set the requested Requested-Action AVP set to PRICE_ENQUIRY, and set the requested
service event information into the Service-Identifier AVP in the service event information into the Service-Identifier AVP in the
Credit-Control-Request message. Additional service event information Credit-Control-Request message. Additional service event information
may be sent as service specific AVPs or within the Service- may be sent as service specific AVPs or within the Service-Parameter-
Parameter-Info AVP. The Service-Context-Id AVP indicates the service Info AVP. The Service-Context-Id AVP indicates the service specific
specific document applicable to the request. document applicable to the request.
The credit-control server calculates the cost of the requested The credit-control server calculates the cost of the requested
service event, but it does not perform any account balance check or service event, but it does not perform any account balance check or
credit-reservation from the account. credit-reservation from the account.
The estimated cost of the requested service event is returned to the The estimated cost of the requested service event is returned to the
credit-control client in the Cost-Information AVP in the Credit- credit-control client in the Cost-Information AVP in the Credit-
Control-Answer message. Control-Answer message.
6.2. Balance Check 6.2. Balance Check
skipping to change at page 43, line 17 skipping to change at page 45, line 17
The Diameter credit-control client may only have to verify that the The Diameter credit-control client may only have to verify that the
end user's account balance covers the cost of a certain service end user's account balance covers the cost of a certain service
without reserving any units from the account at the time of the without reserving any units from the account at the time of the
inquiry. This method does not guarantee that credit would be left inquiry. This method does not guarantee that credit would be left
when the Diameter credit-control client requests the debiting of the when the Diameter credit-control client requests the debiting of the
account with a separate request. account with a separate request.
A Diameter credit-control client requesting the balance check MUST A Diameter credit-control client requesting the balance check MUST
set the CC-Request-Type AVP equal to EVENT_REQUEST, include a set the CC-Request-Type AVP equal to EVENT_REQUEST, include a
Requested-Action AVP set to CHECK_BALANCE, and include the Requested-Action AVP set to CHECK_BALANCE, and include the
Subscription-Id AVP in order to identify the end user in the credit- Subscription-Id AVP or Subscription-Id-Extension AVP in order to
control server. The Service-Context-Id AVP indicates the service identify the end user in the credit-control server. The Service-
specific document applicable to the request. Context-Id AVP indicates the service specific document applicable to
the request.
The credit-control server makes the balance check, but it does not The credit-control server makes the balance check, but it does not
make any credit-reservation from the account. make any credit-reservation from the account.
The result of balance check (ENOUGH_CREDIT/NO_CREDIT) is returned to The result of balance check (ENOUGH_CREDIT/NO_CREDIT) is returned to
the credit-control client in the Check-Balance-Result AVP in the the credit-control client in the Check-Balance-Result AVP in the
Credit-Control-Answer message. Credit-Control-Answer message.
6.3. Direct Debiting 6.3. Direct Debiting
skipping to change at page 43, line 42 skipping to change at page 45, line 43
service invocation and the actual service delivery to the end user service invocation and the actual service delivery to the end user
can be sufficiently long that the use of the session-based credit- can be sufficiently long that the use of the session-based credit-
control would lead to unreasonably long credit-control sessions. In control would lead to unreasonably long credit-control sessions. In
these cases, the Diameter credit-control client can use the one-time these cases, the Diameter credit-control client can use the one-time
event scenario for direct debiting. The Diameter credit-control event scenario for direct debiting. The Diameter credit-control
client SHOULD be sure that the requested service event execution client SHOULD be sure that the requested service event execution
would be successful when this scenario is used. would be successful when this scenario is used.
In the Credit-Control-Request message, the CC-Request-Type is set to In the Credit-Control-Request message, the CC-Request-Type is set to
the value EVENT_REQUEST and the Requested-Action AVP is set to the value EVENT_REQUEST and the Requested-Action AVP is set to
DIRECT_DEBITING. The Subscription-Id AVP SHOULD be included to DIRECT_DEBITING. The Subscription-Id AVP or Subscription-Id-
identify the end user in the credit-control server. The Event- Extension AVP SHOULD be included to identify the end user in the
Timestamp AVP SHOULD be included in the request and contain the time credit-control server. The Event-Timestamp AVP SHOULD be included in
when the service event is requested in the service element. The the request and contain the time when the service event is requested
Service-Context-Id AVP indicates the service specific document in the service element. The Service-Context-Id AVP indicates the
applicable to the request. service specific document applicable to the request.
The Diameter credit-control client MAY include the monetary amount to The Diameter credit-control client MAY include the monetary amount to
be charged in the Requested-Service-Unit AVP, if it knows the cost of be charged in the Requested-Service-Unit AVP, if it knows the cost of
the service event. If the Diameter credit-control client does not the service event. If the Diameter credit-control client does not
know the cost of the service event, the Requested-Service-Unit AVP know the cost of the service event, the Requested-Service-Unit AVP
MAY contain the number of requested service events. The Service- MAY contain the number of requested service events. The Service-
Identifier AVP always indicates the service concerned. Additional Identifier AVP always indicates the service concerned. Additional
service event information to be rated MAY be sent as service specific service event information to be rated MAY be sent as service specific
AVPs or within the Service-Parameter-Info AVP. AVPs or within the Service-Parameter-Info AVP.
skipping to change at page 44, line 38 skipping to change at page 46, line 39
include the Cost-Information AVP containing the estimated total cost include the Cost-Information AVP containing the estimated total cost
of the requested service. of the requested service.
6.4. Refund 6.4. Refund
Some services may refund service units to the end user's account; for Some services may refund service units to the end user's account; for
example, gaming services. example, gaming services.
The credit-control client MUST set CC-Request-Type to the value The credit-control client MUST set CC-Request-Type to the value
EVENT_REQUEST and the Requested-Action AVP to REFUND_ACCOUNT in the EVENT_REQUEST and the Requested-Action AVP to REFUND_ACCOUNT in the
Credit-Control-Request message. The Subscription-Id AVP SHOULD be Credit-Control-Request message. The Subscription-Id AVP or
included to identify the end user in the credit-control server. The Subscription-Id-Extension AVP SHOULD be included to identify the end
Service-Context-Id AVP indicates the service specific document user in the credit-control server. The Service-Context-Id AVP
applicable to the request. indicates the service specific document applicable to the request.
The Diameter credit-control client MAY include the monetary amount to The Diameter credit-control client MAY include the monetary amount to
be refunded in the Requested-Service-Unit AVP. The Service- be refunded in the Requested-Service-Unit AVP. The Service-
Identifier AVP always indicates the concerned service. If the Identifier AVP always indicates the concerned service. If the
Diameter credit-control client does not know the monetary amount to Diameter credit-control client does not know the monetary amount to
be refunded, in addition to the Service-Identifier AVP it MAY send be refunded, in addition to the Service-Identifier AVP it MAY send
service specific AVPs or the Service-Parameter-Info AVP containing service specific AVPs or the Service-Parameter-Info AVP containing
additional service event information to be rated. additional service event information to be rated.
For informative purposes, the Credit-Control-Answer message MAY also For informative purposes, the Credit-Control-Answer message MAY also
skipping to change at page 50, line 13 skipping to change at page 52, line 13
request request
+----------+-------------------------------+-------------+----------+ +----------+-------------------------------+-------------+----------+
| State | Event | Action | New | | State | Event | Action | New |
| | | | State | | | | | State |
+----------+-------------------------------+-------------+----------+ +----------+-------------------------------+-------------+----------+
| Idle | Client or device requests | Send CC | PendingI | | Idle | Client or device requests | Send CC | PendingI |
| | access/service | initial | | | | access/service | initial | |
| | | req., start | | | | | req., start | |
| | | Tx | | | | | Tx | |
| PendingI | Successful CC intial answer | Stop Tx | Open | | PendingI | Successful CC initial answer | Stop Tx | Open |
| | received | | | | | received | | |
| PendingI | Failure to send, or temporary | Grant | Idle | | PendingI | Failure to send, or temporary | Grant | Idle |
| | error and CCFH equal to | service to | | | | error and CCFH equal to | service to | |
| | CONTINUE | end user | | | | CONTINUE | end user | |
| PendingI | Failure to send, or temporary | Terminate | Idle | | PendingI | Failure to send, or temporary | Terminate | Idle |
| | error and CCFH equal to | end user's | | | | error and CCFH equal to | end user's | |
| | TERMINATEor to | service | | | | TERMINATE or to | service | |
| | RETRY_AND_TERMINATE | | | | | RETRY_AND_TERMINATE | | |
| PendingI | Tx expired and CCFH equal to | Terminate | Idle | | PendingI | Tx expired and CCFH equal to | Terminate | Idle |
| | TERMINATE | end user's | | | | TERMINATE | end user's | |
| | | service | | | | | service | |
| PendingI | Tx expired and CCFH equal to | Grant | Idle | | PendingI | Tx expired and CCFH equal to | Grant | Idle |
| | CONTINUE or to | service to | | | | CONTINUE or to | service to | |
| | RETRY_AND_TERMINATE | end user | | | | RETRY_AND_TERMINATE | end user | |
| PendingI | CC initial answer received | Terminate | Idle | | PendingI | CC initial answer received | Terminate | Idle |
| | with result code | end user's | | | | with result code | end user's | |
| | END_USER_SERVICE_DENIED or | service | | | | END_USER_SERVICE_DENIED or | service | |
skipping to change at page 56, line 10 skipping to change at page 58, line 10
authorization commands defined in authorization-specific authorization commands defined in authorization-specific
applications, such as [RFC7155] and [RFC4004], if the first applications, such as [RFC7155] and [RFC4004], if the first
interrogation is performed as part of the authorization/ interrogation is performed as part of the authorization/
authentication process, as described in Section 5.2. authentication process, as described in Section 5.2.
The Diameter AVP rules are defined in the Diameter Base [RFC6733], The Diameter AVP rules are defined in the Diameter Base [RFC6733],
Section 4. These AVP rules are observed in AVPs defined in this Section 4. These AVP rules are observed in AVPs defined in this
section. section.
The following table describes the Diameter AVPs defined in the The following table describes the Diameter AVPs defined in the
credit-control application, their AVP Code values, types, possible credit-control application, their AVP Code values, types, and
flag values, and whether the AVP MAY be encrypted. The Diameter base possible flag values. The AVP Flag rules are explained in the
[RFC6733] specifies the AVP Flag rules for AVPs in section 4.5. Diameter base [RFC6733], section 4.1.
+---------------+ +---------------+
|AVP Flag rules | |AVP Flag rules |
|----+-----+----| |----+-----+----|
AVP Section | | |MUST| AVP Section | | |MUST|
Attribute Name Code Defined Data Type |MUST| MAY |NOT | Attribute Name Code Defined Data Type |MUST| MAY |NOT |
-----------------------------------------|----+-----+----| -----------------------------------------|----+-----+----|
CC-Correlation-Id 411 8.1 OctetString| | M | V | CC-Correlation-Id 411 8.1 OctetString| | M | V |
CC-Input-Octets 412 8.24 Unsigned64 | M | | V | CC-Input-Octets 412 8.24 Unsigned64 | M | | V |
CC-Money 413 8.22 Grouped | M | | V | CC-Money 413 8.22 Grouped | M | | V |
skipping to change at page 56, line 48 skipping to change at page 58, line 48
Credit-Control 426 8.13 Enumerated | M | | V | Credit-Control 426 8.13 Enumerated | M | | V |
Credit-Control- 427 8.14 Enumerated | M | | V | Credit-Control- 427 8.14 Enumerated | M | | V |
Failure-Handling | | | | Failure-Handling | | | |
Currency-Code 425 8.11 Unsigned32 | M | | V | Currency-Code 425 8.11 Unsigned32 | M | | V |
Direct-Debiting- 428 8.15 Enumerated | M | | V | Direct-Debiting- 428 8.15 Enumerated | M | | V |
Failure-Handling | | | | Failure-Handling | | | |
Exponent 429 8.9 Integer32 | M | | V | Exponent 429 8.9 Integer32 | M | | V |
Final-Unit-Action 449 8.35 Enumerated | M | | V | Final-Unit-Action 449 8.35 Enumerated | M | | V |
Final-Unit- 430 8.34 Grouped | M | | V | Final-Unit- 430 8.34 Grouped | M | | V |
Indication | | | | Indication | | | |
QoS-Final-Unit- TBD18 8.69 Grouped | | M | V |
Indication | | | |
Granted-Service- 431 8.17 Grouped | M | | V | Granted-Service- 431 8.17 Grouped | M | | V |
Unit | | | | Unit | | | |
G-S-U-Pool- 453 8.31 Unsigned32 | M | | V | G-S-U-Pool- 453 8.31 Unsigned32 | M | | V |
Identifier | | | | Identifier | | | |
G-S-U-Pool- 457 8.30 Grouped | M | | V | G-S-U-Pool- 457 8.30 Grouped | M | | V |
Reference | | | | Reference | | | |
Multiple-Services 456 8.16 Grouped | M | | V | Multiple-Services 456 8.16 Grouped | M | | V |
-Credit-Control | | | | -Credit-Control | | | |
Multiple-Services 455 8.40 Enumerated | M | | V | Multiple-Services 455 8.40 Enumerated | M | | V |
-Indicator | | | | -Indicator | | | |
Rating-Group 432 8.29 Unsigned32 | M | | V | Rating-Group 432 8.29 Unsigned32 | M | | V |
Redirect-Address 433 8.38 Enumerated | M | | V | Redirect-Address 433 8.38 Enumerated | M | | V |
-Type | | | | -Type | | | |
Redirect-Server 434 8.37 Grouped | M | | V | Redirect-Server 434 8.37 Grouped | M | | V |
Redirect-Server 435 8.39 UTF8String | M | | V | Redirect-Server 435 8.39 UTF8String | M | | V |
-Address | | | | -Address | | | |
Redirect-Server TBD13 8.64 Grouped | | M | V |
-Extension | | | |
Redirect-Address TBD14 8.65 UTF8String | | M | V |
-IPv4Address | | | |
Redirect-Address TBD15 8.66 UTF8String | | M | V |
-IPv6Address | | | |
Redirect-Address TBD16 8.67 UTF8String | | M | V |
-URL | | | |
Redirect-Address TBD17 8.68 UTF8String | | M | V |
-SIP-URI | | | |
Requested-Action 436 8.41 Enumerated | M | | V | Requested-Action 436 8.41 Enumerated | M | | V |
Requested-Service 437 8.18 Grouped | M | | V | Requested-Service 437 8.18 Grouped | M | | V |
-Unit | | | | -Unit | | | |
Restriction 438 8.36 IPFiltrRule| M | | V | Restriction 438 8.36 IPFiltrRule| M | | V |
-Filter-Rule | | | | -Filter-Rule | | | |
Service-Context 461 8.42 UTF8String | M | | V | Service-Context 461 8.42 UTF8String | M | | V |
-Id | | | | -Id | | | |
Service- 439 8.28 Unsigned32 | M | | V | Service- 439 8.28 Unsigned32 | M | | V |
Identifier | | | | Identifier | | | |
Service-Parameter 440 8.43 Grouped | | M | V | Service-Parameter 440 8.43 Grouped | | M | V |
-Info | | | | -Info | | | |
Service- 441 8.44 Unsigned32 | | M | V | Service- 441 8.44 Unsigned32 | | M | V |
Parameter-Type | | | | Parameter-Type | | | |
Service- 442 8.45 OctetString| | M | V | Service- 442 8.45 OctetString| | M | V |
Parameter-Value | | | | Parameter-Value | | | |
Subscription-Id 443 8.46 Grouped | M | | V | Subscription-Id 443 8.46 Grouped | M | | V |
Subscription-Id 444 8.48 UTF8String | M | | V | Subscription-Id 444 8.48 UTF8String | M | | V |
-Data | | | | -Data | | | |
Subscription-Id 450 8.47 Enumerated | M | | V | Subscription-Id 450 8.47 Enumerated | M | | V |
-Type | | | | -Type | | | |
Subscription-Id TBD7 8.58 Grouped | | M | V |
-Extension | | | |
Subscription-Id TBD8 8.59 UTF8String | | M | V |
-E164 | | | |
Subscription-Id TBD9 8.60 UTF8String | | M | V |
-IMSI | | | |
Subscription-Id TBD10 8.61 UTF8String | | M | V |
-SIP-URI | | | |
Subscription-Id TBD11 8.62 UTF8String | | M | V |
-NAI | | | |
Subscription-Id TBD12 8.63 UTF8String | | M | V |
-Private | | | |
Tariff-Change 452 8.27 Enumerated | M | | V | Tariff-Change 452 8.27 Enumerated | M | | V |
-Usage | | | | -Usage | | | |
Tariff-Time 451 8.20 Time | M | | V | Tariff-Time 451 8.20 Time | M | | V |
-Change | | | | -Change | | | |
Unit-Value 445 8.8 Grouped | M | | V | Unit-Value 445 8.8 Grouped | M | | V |
Used-Service-Unit 446 8.19 Grouped | M | | V | Used-Service-Unit 446 8.19 Grouped | M | | V |
User-Equipment 458 8.49 Grouped | | M | V | User-Equipment 458 8.49 Grouped | | M | V |
-Info | | | | -Info | | | |
User-Equipment 459 8.50 Enumerated | | M | V | User-Equipment 459 8.50 Enumerated | | M | V |
-Info-Type | | | | -Info-Type | | | |
User-Equipment 460 8.51 OctetString| | M | V | User-Equipment 460 8.51 OctetString| | M | V |
-Info-Value | | | | -Info-Value | | | |
User-Equipment TBD1 8.52 Grouped | | M | V |
-Info-Extension | | | |
User-Equipment TBD2 8.53 OctetString| | M | V |
-Info-IMEISV | | | |
User-Equipment TBD3 8.54 OctetString| | M | V |
-Info-MAC | | | |
User-Equipment TBD4 8.55 OctetString| | M | V |
-Info-EUI64 | | | |
User-Equipment TBD5 8.56 OctetString| | M | V |
-Info-ModifiedEUI64 | | | |
User-Equipment TBD6 8.57 OctetString| | M | V |
-Info-IMEI | | | |
Value-Digits 447 8.10 Integer64 | M | | V | Value-Digits 447 8.10 Integer64 | M | | V |
Validity-Time 448 8.33 Unsigned32 | M | | V | Validity-Time 448 8.33 Unsigned32 | M | | V |
8.1. CC-Correlation-Id AVP 8.1. CC-Correlation-Id AVP
The CC-Correlation-Id AVP (AVP Code 411) is of type OctetString and The CC-Correlation-Id AVP (AVP Code 411) is of type OctetString and
contains information to correlate credit-control requests generated contains information to correlate credit-control requests generated
for different components of the service; e.g., transport and service for different components of the service; e.g., transport and service
level. The one who allocates the Service-Context-Id (i.e., unique level. The one who allocates the Service-Context-Id (i.e., unique
identifier of a service specific document) is also responsible for identifier of a service specific document) is also responsible for
skipping to change at page 59, line 11 skipping to change at page 61, line 44
A Termination request is sent to terminate a credit-control session A Termination request is sent to terminate a credit-control session
and contains credit-control information relevant to the existing and contains credit-control information relevant to the existing
session. session.
EVENT_REQUEST 4 EVENT_REQUEST 4
An Event request is used when there is no need to maintain any An Event request is used when there is no need to maintain any
credit-control session state in the credit-control server. This credit-control session state in the credit-control server. This
request contains all information relevant to the service, and is the request contains all information relevant to the service, and is the
only request of the service. The reason for the Event request is only request of the service. The reason for the Event request is
further detailed in the Requested-Action AVP. The Requested- Action further detailed in the Requested-Action AVP. The Requested-Action
AVP MUST be included in the Credit-Control-Request message when CC- AVP MUST be included in the Credit-Control-Request message when CC-
Request-Type is set to EVENT_REQUEST. Request-Type is set to EVENT_REQUEST.
8.4. CC-Session-Failover AVP 8.4. CC-Session-Failover AVP
The CC-Session-Failover AVP (AVP Code 418) is type of Enumerated and The CC-Session-Failover AVP (AVP Code 418) is type of Enumerated and
contains information as to whether moving the credit-control message contains information as to whether moving the credit-control message
stream to a backup server during an ongoing credit-control session is stream to a backup server during an ongoing credit-control session is
supported. In communication failures, the credit-control message supported. In communication failures, the credit-control message
streams can be moved to an alternative destination if the credit- streams can be moved to an alternative destination if the credit-
skipping to change at page 59, line 34 skipping to change at page 62, line 24
Diameter AAA server, can be used as an address of the backup server. Diameter AAA server, can be used as an address of the backup server.
An implementation is not required to support moving a credit-control An implementation is not required to support moving a credit-control
message stream to an alternative server, as this also requires moving message stream to an alternative server, as this also requires moving
information related to the credit-control session to backup server. information related to the credit-control session to backup server.
The following values are defined for the CC-Session-Failover AVP: The following values are defined for the CC-Session-Failover AVP:
FAILOVER_NOT_SUPPORTED 0 FAILOVER_NOT_SUPPORTED 0
When the CC-Session-Failover AVP is set to FAILOVER_NOT_SUPPORTED, When the CC-Session-Failover AVP is set to FAILOVER_NOT_SUPPORTED,
the credit-control message stream MUST NOT to be moved to an the credit-control message stream MUST NOT be moved to an alternative
alternative destination in the case of communication failure. This destination in the case of communication failure. This is the
is the default behavior if the AVP isn't included in the reply from default behavior if the AVP isn't included in the reply from the
the authorization or credit-control server. authorization or credit-control server.
FAILOVER_SUPPORTED 1 FAILOVER_SUPPORTED 1
When the CC-Session-Failover AVP is set to FAILOVER_SUPPORTED, the When the CC-Session-Failover AVP is set to FAILOVER_SUPPORTED, the
credit-control message stream SHOULD be moved to an alternative credit-control message stream SHOULD be moved to an alternative
destination in the case of communication failure. Moving the credit- destination in the case of communication failure. Moving the credit-
control message stream to a backup server MAY require that control message stream to a backup server MAY require that
information related to the credit-control session should also be information related to the credit-control session should also be
forwarded to alternative server. forwarded to an alternative server.
8.5. CC-Sub-Session-Id AVP 8.5. CC-Sub-Session-Id AVP
The CC-Sub-Session-Id AVP (AVP Code 419) is of type Unsigned64 and The CC-Sub-Session-Id AVP (AVP Code 419) is of type Unsigned64 and
contains the credit-control sub-session identifier. The combination contains the credit-control sub-session identifier. The combination
of the Session-Id and this AVP MUST be unique per sub-session, and of the Session-Id and this AVP MUST be unique per sub-session, and
the value of this AVP MUST be monotonically increased by one for all the value of this AVP MUST be monotonically increased by one for all
new sub-sessions. The absence of this AVP implies that no sub- new sub-sessions. The absence of this AVP implies that no sub-
sessions are in use. sessions are in use.
skipping to change at page 62, line 33 skipping to change at page 65, line 22
If the home Diameter AAA server determines that the user has prepaid If the home Diameter AAA server determines that the user has prepaid
subscription, this value indicates that the credit-control server subscription, this value indicates that the credit-control server
MUST be contacted to perform the first interrogation. The value of MUST be contacted to perform the first interrogation. The value of
the Credit-Control AVP MUST always be set to 0 in an AA request sent the Credit-Control AVP MUST always be set to 0 in an AA request sent
to perform the first interrogation and to initiate a new credit- to perform the first interrogation and to initiate a new credit-
control session. control session.
RE_AUTHORIZATION 1 RE_AUTHORIZATION 1
This value indicates to the Diameter AAA server that a credit- This value indicates to the Diameter AAA server that a credit-control
control session is ongoing for the subscriber and that the credit- session is ongoing for the subscriber and that the credit-control
control server MUST not be contacted. The Credit-Control AVP set to server MUST not be contacted. The Credit-Control AVP set to the
the value of 1 is to be used only when the first interrogation has value of 1 is to be used only when the first interrogation has been
been successfully performed and the credit- control session is successfully performed and the credit-control session is ongoing
ongoing (i.e., re-authorization triggered by Authorization-Lifetime). (i.e., re-authorization triggered by Authorization-Lifetime). This
This value MUST NOT be used in an AA request sent to perform the value MUST NOT be used in an AA request sent to perform the first
first interrogation. interrogation.
8.14. Credit-Control-Failure-Handling AVP 8.14. Credit-Control-Failure-Handling AVP
The Credit-Control-Failure-Handling AVP (AVP Code 427) is of type The Credit-Control-Failure-Handling AVP (AVP Code 427) is of type
Enumerated. The credit-control client uses information in this AVP Enumerated. The credit-control client uses information in this AVP
to decide what to do if sending credit-control messages to the to decide what to do if sending credit-control messages to the
credit-control server has been, for instance, temporarily prevented credit-control server has been, for instance, temporarily prevented
due to a network problem. Depending on the service logic, the due to a network problem. Depending on the service logic, the
credit-control server can order the client to terminate the service credit-control server can order the client to terminate the service
immediately when there is a reason to believe that the service cannot immediately when there is a reason to believe that the service cannot
skipping to change at page 63, line 25 skipping to change at page 66, line 13
failed, and the end user's service session is terminated. failed, and the end user's service session is terminated.
This is the default behavior if the AVP isn't included in the reply This is the default behavior if the AVP isn't included in the reply
from the authorization or credit-control server. from the authorization or credit-control server.
CONTINUE 1 CONTINUE 1
When the Credit-Control-Failure-Handling AVP is set to CONTINUE, the When the Credit-Control-Failure-Handling AVP is set to CONTINUE, the
credit-control client SHOULD re-send the request to an alternative credit-control client SHOULD re-send the request to an alternative
server in the case of transport or temporary failures, provided that server in the case of transport or temporary failures, provided that
a failover procedure is supported in the credit- control server and a failover procedure is supported in the credit-control server and
the credit-control client, and that an alternative server is the credit-control client, and that an alternative server is
available. Otherwise, the service SHOULD be granted, even if credit- available. Otherwise, the service SHOULD be granted, even if credit-
control messages can't be delivered. control messages can't be delivered.
RETRY_AND_TERMINATE 2 RETRY_AND_TERMINATE 2
When the Credit-Control-Failure-Handling AVP is set to When the Credit-Control-Failure-Handling AVP is set to
RETRY_AND_TERMINATE, the credit-control client SHOULD re-send the RETRY_AND_TERMINATE, the credit-control client SHOULD re-send the
request to an alternative server in the case of transport or request to an alternative server in the case of transport or
temporary failures, provided that a failover procedure is supported temporary failures, provided that a failover procedure is supported
skipping to change at page 64, line 11 skipping to change at page 66, line 48
When the Direct-Debiting-Failure-Handling AVP is set to When the Direct-Debiting-Failure-Handling AVP is set to
TERMINATE_OR_BUFFER, the service MUST be granted for as long as there TERMINATE_OR_BUFFER, the service MUST be granted for as long as there
is a connection to the credit-control server. If the credit-control is a connection to the credit-control server. If the credit-control
client does not receive any Credit-Control-Answer message within the client does not receive any Credit-Control-Answer message within the
Tx timer (as defined in Section 13) the credit-control request is Tx timer (as defined in Section 13) the credit-control request is
regarded as failed. The client SHOULD terminate the service if it regarded as failed. The client SHOULD terminate the service if it
can determine from the failed answer that units have not been can determine from the failed answer that units have not been
debited. Otherwise the credit-control client SHOULD grant the debited. Otherwise the credit-control client SHOULD grant the
service, store the request in application level non-volatile storage, service, store the request in application level non-volatile storage,
and try to re-send the request. These requests MUST be marked as and try to re-send the request. These requests MUST be marked as
possible duplicates by setting the T- flag in the command header as possible duplicates by setting the T-flag in the command header as
described in [RFC6733] section 3. This is the default behavior if described in [RFC6733] section 3. This is the default behavior if
the AVP isn't included in the reply from the authorization server. the AVP isn't included in the reply from the authorization server.
CONTINUE 1 CONTINUE 1
When the Direct-Debiting-Failure-Handling AVP is set to CONTINUE, the When the Direct-Debiting-Failure-Handling AVP is set to CONTINUE, the
service SHOULD be granted, even if credit-control messages can't be service SHOULD be granted, even if credit-control messages can't be
delivered, and the request should be deleted. delivered, and the request should be deleted.
8.16. Multiple-Services-Credit-Control AVP 8.16. Multiple-Services-Credit-Control AVP
Multiple-Services-Credit-Control AVP (AVP Code 456) is of type Multiple-Services-Credit-Control AVP (AVP Code 456) is of type
Grouped and contains the AVPs related to the independent credit- Grouped and contains the AVPs related to the independent credit-
control of multiple services feature. Note that each instance of control of multiple services feature. Note that each instance of
this AVP carries units related to one or more services or related to this AVP carries units related to one or more services or related to
skipping to change at page 65, line 6 skipping to change at page 67, line 40
specifies Unit-Type TIME, then the CC-Time AVP MUST be present. specifies Unit-Type TIME, then the CC-Time AVP MUST be present.
The Requested-Service-Unit AVP MAY contain the amount of requested The Requested-Service-Unit AVP MAY contain the amount of requested
service units or the requested monetary value. It MUST be present in service units or the requested monetary value. It MUST be present in
the initial interrogation and within the intermediate interrogations the initial interrogation and within the intermediate interrogations
in which new quota is requested. If the credit-control client does in which new quota is requested. If the credit-control client does
not include the Requested-Service-Unit AVP in a request command, not include the Requested-Service-Unit AVP in a request command,
because for instance, it has determined that the end-user terminated because for instance, it has determined that the end-user terminated
the service, the server MUST debit the used amount from the user's the service, the server MUST debit the used amount from the user's
account but MUST NOT return a new quota in the corresponding answer. account but MUST NOT return a new quota in the corresponding answer.
The Validity-Time, Result-Code, and Final-Unit-Indication AVPs MAY be The Validity-Time, Result-Code, and Final-Unit-Indication or QoS-
present in an answer command as defined in sections 5.1.2 and 5.6 for Final-Unit-Indication AVPs MAY be present in an answer command as
the graceful service termination. defined in Section 5.1.2 and Section 5.6 for the graceful service
termination.
When both the Tariff-Time-Change and Tariff-Change-Usage AVPs are When both the Tariff-Time-Change and Tariff-Change-Usage AVPs are
present, the server MUST include two separate instances of the present, the server MUST include two separate instances of the
Multiple-Services-Credit-Control AVP with the Granted-Service-Unit Multiple-Services-Credit-Control AVP with the Granted-Service-Unit
AVP associated to the same service-identifier and/or rating-group. AVP associated to the same service-identifier and/or rating-group.
Where the two quotas are associated to the same pool or to different Where the two quotas are associated to the same pool or to different
pools, the credit pooling mechanism defined in Section 5.1.2 applies. pools, the credit pooling mechanism defined in Section 5.1.2 applies.
The Tariff-Change-Usage AVP MUST NOT be included in request commands The Tariff-Change-Usage AVP MUST NOT be included in request commands
to report used units before, and after tariff time change the Used- to report used units before, and after tariff time change the Used-
Service-Unit AVP MUST be used. Service-Unit AVP MUST be used.
A server not implementing the independent credit-control of multiple A server not implementing the independent credit-control of multiple
services functionality MUST treat the Multiple-Services-Credit- services functionality MUST treat the Multiple-Services-Credit-
Control AVP as an invalid AVP. Control AVP as an invalid AVP.
The Multiple-Services-Control AVP is defined as follows (per the The Multiple-Services-Control AVP is defined as follows (per the
grouped-avp-def of [RFC6733]): grouped-avp-def of [RFC6733]):
Multiple-Services-Credit-Control ::= < AVP Header: 456 > Multiple-Services-Credit-Control ::= < AVP Header: 456 >
[ Granted-Service-Unit ] [ Granted-Service-Unit ]
[ Requested-Service-Unit ] [ Requested-Service-Unit ]
*[ Used-Service-Unit ] *[ Used-Service-Unit ]
[ Tariff-Change-Usage ] [ Tariff-Change-Usage ]
*[ Service-Identifier ] *[ Service-Identifier ]
[ Rating-Group ] [ Rating-Group ]
*[ G-S-U-Pool-Reference ] *[ G-S-U-Pool-Reference ]
[ Validity-Time ] [ Validity-Time ]
[ Result-Code ] [ Result-Code ]
[ Final-Unit-Indication ] [ Final-Unit-Indication ]
*[ AVP ] [ QoS-Final-Unit-Indication ]
*[ AVP ]
8.17. Granted-Service-Unit AVP 8.17. Granted-Service-Unit AVP
Granted-Service-Unit AVP (AVP Code 431) is of type Grouped and Granted-Service-Unit AVP (AVP Code 431) is of type Grouped and
contains the amount of units that the Diameter credit-control client contains the amount of units that the Diameter credit-control client
can provide to the end user until the service must be released or the can provide to the end user until the service must be released or the
new Credit-Control-Request must be sent. A client is not required to new Credit-Control-Request must be sent. A client is not required to
implement all the unit types, and it must treat unknown or implement all the unit types, and it must treat unknown or
unsupported unit types in the answer message as an incorrect CCA unsupported unit types in the answer message as an incorrect CCA
answer. In this case, the client MUST terminate the credit-control answer. In this case, the client MUST terminate the credit-control
skipping to change at page 66, line 44 skipping to change at page 69, line 41
[ CC-Output-Octets ] [ CC-Output-Octets ]
[ CC-Service-Specific-Units ] [ CC-Service-Specific-Units ]
*[ AVP ] *[ AVP ]
8.19. Used-Service-Unit AVP 8.19. Used-Service-Unit AVP
The Used-Service-Unit AVP is of type Grouped (AVP Code 446) and The Used-Service-Unit AVP is of type Grouped (AVP Code 446) and
contains the amount of used units measured from the point when the contains the amount of used units measured from the point when the
service became active or, if interim interrogations are used during service became active or, if interim interrogations are used during
the session, from the point when the previous measurement ended. the session, from the point when the previous measurement ended.
Note: The values reported in a Used-Service-Unit AVP does not
necessarily have a relation to the grant provided in a Granted-
Service-Unit AVP, e.g., the value in this AVP may exceed the value in
the grant.
The Used-Service-Unit AVP is defined as follows (per the grouped- The Used-Service-Unit AVP is defined as follows (per the grouped-avp-
avp-def of [RFC6733]): def of [RFC6733]):
Used-Service-Unit ::= < AVP Header: 446 > Used-Service-Unit ::= < AVP Header: 446 >
[ Tariff-Change-Usage ] [ Tariff-Change-Usage ]
[ CC-Time ] [ CC-Time ]
[ CC-Money ] [ CC-Money ]
[ CC-Total-Octets ] [ CC-Total-Octets ]
[ CC-Input-Octets ] [ CC-Input-Octets ]
[ CC-Output-Octets ] [ CC-Output-Octets ]
[ CC-Service-Specific-Units ] [ CC-Service-Specific-Units ]
*[ AVP ] *[ AVP ]
skipping to change at page 68, line 29 skipping to change at page 71, line 29
The CC-Output-Octets AVP (AVP Code 414) is of type Unsigned64 and The CC-Output-Octets AVP (AVP Code 414) is of type Unsigned64 and
contains the number of requested, granted, or used octets that can contains the number of requested, granted, or used octets that can
be/have been sent to the end user. be/have been sent to the end user.
8.26. CC-Service-Specific-Units AVP 8.26. CC-Service-Specific-Units AVP
The CC-Service-Specific-Units AVP (AVP Code 417) is of type The CC-Service-Specific-Units AVP (AVP Code 417) is of type
Unsigned64 and specifies the number of service-specific units (e.g., Unsigned64 and specifies the number of service-specific units (e.g.,
number of events, points) given in a selected service. The service- number of events, points) given in a selected service. The service-
specific units always refer to the service identified in the Service- specific units always refer to the service identified in the Service-
Identifier AVP (or Rating-Group AVP when the Multiple- Services- Identifier AVP (or Rating-Group AVP when the Multiple-Services-
Credit-Control AVP is used). Credit-Control AVP is used).
8.27. Tariff-Change-Usage AVP 8.27. Tariff-Change-Usage AVP
The Tariff-Change-Usage AVP (AVP Code 452) is of type Enumerated and The Tariff-Change-Usage AVP (AVP Code 452) is of type Enumerated and
defines whether units are used before or after a tariff change, or defines whether units are used before or after a tariff change, or
whether the units straddled a tariff change during the reporting whether the units straddled a tariff change during the reporting
period. Omission of this AVP means that no tariff change has period. Omission of this AVP means that no tariff change has
occurred. occurred.
skipping to change at page 69, line 23 skipping to change at page 72, line 23
When present in the Multiple-Services-Credit-Control AVP, this value When present in the Multiple-Services-Credit-Control AVP, this value
indicates the amount of the units allocated for use after a tariff indicates the amount of the units allocated for use after a tariff
change occurs. change occurs.
When present in the Used-Service-Unit AVP, this value indicates the When present in the Used-Service-Unit AVP, this value indicates the
amount of resource units used after tariff change had occurred. amount of resource units used after tariff change had occurred.
UNIT_INDETERMINATE 2 UNIT_INDETERMINATE 2
The used unit contains the amount of units that straddle the tariff The used unit contains the amount of units that straddle the tariff
change (e.g., the metering process reports to the credit- control change (e.g., the metering process reports to the credit-control
client in blocks of n octets, and one block straddled the tariff client in blocks of n octets, and one block straddled the tariff
change). This value is to be used only in the Used- Service-Unit change). This value is to be used only in the Used-Service-Unit AVP.
AVP.
8.28. Service-Identifier AVP 8.28. Service-Identifier AVP
The Service-Identifier AVP is of type Unsigned32 (AVP Code 439) and The Service-Identifier AVP is of type Unsigned32 (AVP Code 439) and
contains the identifier of a service. The specific service the contains the identifier of a service. The specific service the
request relates to is uniquely identified by the combination of request relates to is uniquely identified by the combination of
Service-Context-Id and Service-Identifier AVPs. Service-Context-Id and Service-Identifier AVPs.
A usage example of this AVP is illustrated in Appendix A (Flow IX). A usage example of this AVP is illustrated in Appendix B.9.
8.29. Rating-Group AVP 8.29. Rating-Group AVP
The Rating-Group AVP is of type Unsigned32 (AVP Code 432) and The Rating-Group AVP is of type Unsigned32 (AVP Code 432) and
contains the identifier of a rating group. All the services subject contains the identifier of a rating group. All the services subject
to the same rating type are part of the same rating group. The to the same rating type are part of the same rating group. The
specific rating group the request relates to is uniquely identified specific rating group the request relates to is uniquely identified
by the combination of Service-Context-Id and Rating-Group AVPs. by the combination of Service-Context-Id and Rating-Group AVPs.
A usage example of this AVP is illustrated in Appendix A (Flow IX). A usage example of this AVP is illustrated in Appendix B.9.
8.30. G-S-U-Pool-Reference AVP 8.30. G-S-U-Pool-Reference AVP
The G-S-U-Pool-Reference AVP (AVP Code 457) is of type Grouped. It The G-S-U-Pool-Reference AVP (AVP Code 457) is of type Grouped. It
is used in the Credit-Control-Answer message, and associates the is used in the Credit-Control-Answer message, and associates the
Granted-Service-Unit AVP within which it appears with a credit pool Granted-Service-Unit AVP within which it appears with a credit pool
within the session. within the session.
The G-S-U-Pool-Identifier AVP specifies the credit pool from which The G-S-U-Pool-Identifier AVP specifies the credit pool from which
credit is drawn for this unit type. credit is drawn for this unit type.
skipping to change at page 72, line 15 skipping to change at page 75, line 13
not accessible through the address given in the Redirect-Server AVP. not accessible through the address given in the Redirect-Server AVP.
If the Final-Unit-Action AVP is set to RESTRICT_ACCESS, either the If the Final-Unit-Action AVP is set to RESTRICT_ACCESS, either the
Restriction-Filter-Rule AVP or the Filter-Id AVP SHOULD be present. Restriction-Filter-Rule AVP or the Filter-Id AVP SHOULD be present.
The Filter-Id AVP is defined in [RFC7155]. The Filter-Id AVP can be The Filter-Id AVP is defined in [RFC7155]. The Filter-Id AVP can be
used to reference an IP filter list installed in the access device by used to reference an IP filter list installed in the access device by
means other than the Diameter credit-control application, e.g., means other than the Diameter credit-control application, e.g.,
locally configured or configured by another entity. locally configured or configured by another entity.
If the type of Final-Unit-Action AVP is set to REDIRECT and the type
of server is not one of the types in the Redirect-Server-Type AVP,
then the QoS-Final-Unit-Indication AVP SHOULD be used together with
the Redirect-Server-Extension AVP instead of the Final-Unit-
Indication AVP.
If the type of Final-Unit-Action AVP is set to RESTRICT_ACCESS or
REDIRECT and the classification of the restricted traffic cannot be
expressed using IPFilterRule, or different actions (e.g., QoS) than
just allowing QoS needs to be enforced traffic, then the QoS-Final-
Unit-Indication AVP SHOULD be used instead of the Final-Unit-
Indication AVP. However, if the credit control server wants to
preserve backward compatibility with credit-control clients that
support only [RFC4006], the Final-Unit-Indication AVP SHOULD be used
together with the Filter-Id AVP.
The Final-Unit-Indication AVP is defined as follows (per the grouped- The Final-Unit-Indication AVP is defined as follows (per the grouped-
avp-def of [RFC6733]): avp-def of [RFC6733]):
Final-Unit-Indication ::= < AVP Header: 430 > Final-Unit-Indication ::= < AVP Header: 430 >
{ Final-Unit-Action } { Final-Unit-Action }
*[ Restriction-Filter-Rule ] *[ Restriction-Filter-Rule ]
*[ Filter-Id ] *[ Filter-Id ]
[ Redirect-Server ] [ Redirect-Server ]
8.35. Final-Unit-Action AVP 8.35. Final-Unit-Action AVP
The Final-Unit-Action AVP (AVP Code 449) is of type Enumerated and The Final-Unit-Action AVP (AVP Code 449) is of type Enumerated and
indicates to the credit-control client the action to be taken when indicates to the credit-control client the action to be taken when
the user's account cannot cover the service cost. the user's account cannot cover the service cost.
The Final-Unit-Action can be one of the following: The Final-Unit-Action can be one of the following:
TERMINATE 0 TERMINATE 0
The credit-control client MUST terminate the service session. This The credit-control client MUST terminate the service session. This
is the default handling, applicable whenever the credit- control is the default handling, applicable whenever the credit-control
client receives an unsupported Final-Unit-Action value, and it MUST client receives an unsupported Final-Unit-Action value, and it MUST
be supported by all the Diameter credit-control client be supported by all the Diameter credit-control client
implementations conforming to this specification. implementations conforming to this specification.
REDIRECT 1 REDIRECT 1
The service element MUST redirect the user to the address specified The service element MUST redirect the user to the address specified
in the Redirect-Server-Address AVP. The redirect action is defined in the Redirect-Server-Address AVP or one of the AVPs included in the
in Section 5.6.2. Redirect-Server-Extension AVP. The redirect action is defined in
Section 5.6.2.
RESTRICT_ACCESS 2 RESTRICT_ACCESS 2
The access device MUST restrict the user access according to the IP The access device MUST restrict the user access according to the IP
packet filters defined in the Restriction-Filter-Rule AVP or packet filters defined in the Restriction-Filter-Rule AVP, the
according to the IP packet filters identified by the Filter-Id AVP. Filter-Rule AVP or according to the IP packet filters identified by
the Filter-Id AVP. All the packets not matching the filters MUST be
All the packets not matching the filters MUST be dropped (see dropped (see Section 5.6.3). In the case that Restriction-Filter-
Section 5.6.3). Rule AVP is used, all the packets matching the filters MUST be
allowed. In the case that Filter-Rule AVP or Filter-Id AVP are used,
other actions (e.g., QoS) may be deployed on the packets matching the
filters.
8.36. Restriction-Filter-Rule AVP 8.36. Restriction-Filter-Rule AVP
The Restriction-Filter-Rule AVP (AVP Code 438) is of type The Restriction-Filter-Rule AVP (AVP Code 438) is of type
IPFilterRule and provides filter rules corresponding to services that IPFilterRule and provides filter rules corresponding to services that
are to remain accessible even if there are no more service units are to remain accessible even if there are no more service units
granted. The access device has to configure the specified filter granted. The access device has to configure the specified filter
rules for the subscriber and MUST drop all the packets not matching rules for the subscriber and MUST drop all the packets not matching
these filters. Zero, one, or more such AVPs MAY be present in a these filters. Zero, one, or more such AVPs MAY be present in a
Credit-Control-Answer message or in an AA answer message. Credit-Control-Answer message or in an AA answer message.
skipping to change at page 73, line 48 skipping to change at page 77, line 21
The address type can be one of the following: The address type can be one of the following:
IPv4 Address 0 IPv4 Address 0
The address type is in the form of "dotted-decimal" IPv4 address, as The address type is in the form of "dotted-decimal" IPv4 address, as
defined in [RFC0791]. defined in [RFC0791].
IPv6 Address 1 IPv6 Address 1
The address type is in the form of IPv6 address, as defined in The address type is in the form of IPv6 address, as defined in
[RFC4291]. The address is a text representation of the address in [RFC4291]. The address is a text representation of the address
either the preferred or alternate text form [RFC4291]. Conformant according to [RFC5952].
implementations MUST support the preferred form and SHOULD support
the alternate text form for IPv6 addresses.
URL 2 URL 2
The address type is in the form of Uniform Resource Locator, as The address type is in the form of Uniform Resource Locator, as
defined in [RFC1738]. defined in [RFC1738].
SIP URI 3 SIP URI 3
The address type is in the form of SIP Uniform Resource Identifier, The address type is in the form of SIP Uniform Resource Identifier,
as defined in [RFC3261]. as defined in [RFC3261].
skipping to change at page 75, line 10 skipping to change at page 78, line 30
The Requested-Action AVP (AVP Code 436) is of type Enumerated and The Requested-Action AVP (AVP Code 436) is of type Enumerated and
contains the requested action being sent by Credit-Control-Request contains the requested action being sent by Credit-Control-Request
command where the CC-Request-Type is set to EVENT_REQUEST. The command where the CC-Request-Type is set to EVENT_REQUEST. The
following values are defined for the Requested-Action AVP: following values are defined for the Requested-Action AVP:
DIRECT_DEBITING 0 DIRECT_DEBITING 0
This indicates a request to decrease the end user's account according This indicates a request to decrease the end user's account according
to information specified in the Requested-Service-Unit AVP and/or to information specified in the Requested-Service-Unit AVP and/or
Service-Identifier AVP (additional rating information may be included Service-Identifier AVP (additional rating information may be included
in service-specific AVPs or in the Service- Parameter-Info AVP). The in service-specific AVPs or in the Service-Parameter-Info AVP). The
Granted-Service-Unit AVP in the Credit- Control-Answer command Granted-Service-Unit AVP in the Credit-Control-Answer command
contains the debited units. contains the debited units.
REFUND_ACCOUNT 1 REFUND_ACCOUNT 1
This indicates a request to increase the end user's account according This indicates a request to increase the end user's account according
to information specified in the Requested-Service-Unit AVP and/or to information specified in the Requested-Service-Unit AVP and/or
Service-Identifier AVP (additional rating information may be included Service-Identifier AVP (additional rating information may be included
in service-specific AVPs or in the Service- Parameter-Info AVP). The in service-specific AVPs or in the Service-Parameter-Info AVP). The
Granted-Service-Unit AVP in the Credit- Control-Answer command Granted-Service-Unit AVP in the Credit-Control-Answer command
contains the refunded units. contains the refunded units.
CHECK_BALANCE 2 CHECK_BALANCE 2
This indicates a balance check request. In this case, the checking This indicates a balance check request. In this case, the checking
of the account balance is done without any credit reservation from of the account balance is done without any credit reservation from
the account. The Check-Balance-Result AVP in the Credit-Control- the account. The Check-Balance-Result AVP in the Credit-Control-
Answer command contains the result of the balance check. Answer command contains the result of the balance check.
PRICE_ENQUIRY 3 PRICE_ENQUIRY 3
skipping to change at page 75, line 31 skipping to change at page 79, line 4
contains the refunded units. contains the refunded units.
CHECK_BALANCE 2 CHECK_BALANCE 2
This indicates a balance check request. In this case, the checking This indicates a balance check request. In this case, the checking
of the account balance is done without any credit reservation from of the account balance is done without any credit reservation from
the account. The Check-Balance-Result AVP in the Credit-Control- the account. The Check-Balance-Result AVP in the Credit-Control-
Answer command contains the result of the balance check. Answer command contains the result of the balance check.
PRICE_ENQUIRY 3 PRICE_ENQUIRY 3
This indicates a price enquiry request. In this case, neither This indicates a price enquiry request. In this case, neither
checking of the account balance nor reservation from the account will checking of the account balance nor reservation from the account will
be done; only the price of the service will be returned in the Cost- be done; only the price of the service will be returned in the Cost-
Information AVP in the Credit-Control-Answer Command. Information AVP in the Credit-Control-Answer Command.
8.42. Service-Context-Id AVP 8.42. Service-Context-Id AVP
The Service-Context-Id AVP is of type UTF8String (AVP Code 461) and The Service-Context-Id AVP is of type UTF8String (AVP Code 461) and
contains a unique identifier of the Diameter credit-control service contains a unique identifier of the Diameter credit-control service
specific document that applies to the request (as defined in section specific document that applies to the request (as defined in
4.1.2). This is an identifier allocated by the service provider, by Section 4.1.2). This is an identifier allocated by the service
the service element manufacturer, or by a standardization body, and provider, by the service element manufacturer, or by a
MUST uniquely identify a given Diameter credit-control service standardization body, and MUST uniquely identify a given Diameter
specific document. The format of the Service-Context-Id is: credit-control service specific document. The format of the Service-
Context-Id is:
"service-context" "@" "domain" "service-context" "@" "domain"
service-context = Token service-context = Token
The Token is an arbitrary string of characters and digits. The Token is an arbitrary string of characters and digits.
'domain' represents the entity that allocated the Service-Context-Id. 'domain' represents the entity that allocated the Service-Context-Id.
It can be ietf.org, 3gpp.org, etc., if the identifier is allocated by It can be ietf.org, 3gpp.org, etc., if the identifier is allocated by
a standardization body, or it can be the FQDN of the service provider a standardization body, or it can be the FQDN of the service provider
skipping to change at page 79, line 14 skipping to change at page 82, line 40
The identifier contains the International Mobile Equipment Identifier The identifier contains the International Mobile Equipment Identifier
and Software Version in the international IMEISV format according to and Software Version in the international IMEISV format according to
3GPP TS 23.003 [TGPPIMEI]. 3GPP TS 23.003 [TGPPIMEI].
MAC 1 MAC 1
The 48-bit MAC address is formatted as described in [RFC3580]. The 48-bit MAC address is formatted as described in [RFC3580].
EUI64 2 EUI64 2
The 64-bit identifier used to identify hardware instance of the The 64-bit identifier used to identify the hardware instance of the
product, as defined in [EUI64]. product, as defined in [EUI64].
MODIFIED_EUI64 3 MODIFIED_EUI64 3
There are a number of types of terminals that have identifiers other There are a number of types of terminals that have identifiers other
than IMEI, IEEE 802 MACs, or EUI-64. These identifiers can be than IMEI, IEEE 802 MACs, or EUI-64. These identifiers can be
converted to modified EUI-64 format as described in [RFC4291] or by converted to modified EUI-64 format as described in [RFC4291] or by
using some other methods referred to in the service-specific using some other methods referred to in the service-specific
documentation. documentation.
8.51. User-Equipment-Info-Value AVP 8.51. User-Equipment-Info-Value AVP
The User-Equipment-Info-Value AVP (AVP Code 460) is of type The User-Equipment-Info-Value AVP (AVP Code 460) is of type
OctetString. The User-Equipment-Info-Type AVP defines which type of OctetString. The User-Equipment-Info-Type AVP defines which type of
identifier is used. identifier is used.
8.52. User-Equipment-Info-Extension AVP
The User-Equipment-Info-Extension AVP (AVP Code TBD1) is of type
Grouped and allows the credit-control client to indicate the identity
and capability of the terminal the subscriber is using for the
connection to network. If the type of the equipment is one of the
types listed in the User-Equipment-Info-Type AVP, then the credit-
control client SHOULD send the information in the User-Equipment-Info
AVP, in addition to or instead of the User-Equipment-Info-Extension
AVP. This is in order to preserve backward compatibility with
credit-control servers that support only RFC4006. Exactly one AVP
MUST be included inside the User-Equipment-Info-Extension AVP.
It is defined as follows (per the grouped-avp-def of [RFC6733]):
User-Equipment-Info-Extension ::= < AVP Header: TBD1 >
[ User-Equipment-Info-IMEISV ]
[ User-Equipment-Info-MAC ]
[ User-Equipment-Info-EUI64 ]
[ User-Equipment-Info-ModifiedEUI64 ]
[ User-Equipment-Info-IMEI ]
*[ AVP ]
8.53. User-Equipment-Info-IMEISV AVP
The User-Equipment-Info-IMEISV (AVP Code TBD2) is of type
OctetString. The User-Equipment-Info-IMEISV AVP contains the
International Mobile Equipment Identifier and Software Version in the
international IMEISV format according to 3GPP TS 23.003 [TGPPIMEI].
8.54. User-Equipment-Info-MAC AVP
The User-Equipment-Info-MAC (AVP Code TBD3) is of type OctetString.
The User-Equipment-Info-MAC AVP contains the 48-bit MAC address is
formatted as described in [RFC3580].
8.55. User-Equipment-Info-EUI64 AVP
The User-Equipment-Info-EUI64 (AVP Code TBD4) is of type OctetString.
The UUser-Equipment-Info-EUI64 AVP contains the 64-bit identifier
used to identify the hardware instance of the product, as defined in
[EUI64].
8.56. User-Equipment-Info-ModifiedEUI64 AVP
The User-Equipment-Info-ModifiedEUI64 (AVP Code TBD5) is of type
OctetString. There are a number of types of terminals that have
identifiers other than IMEI, IEEE 802 MACs, or EUI-64. These
identifiers can be converted to modified EUI-64 format as described
in [RFC4291] or by using some other methods referred to in the
service-specific documentation. The User-Equipment-Info-
ModifiedEUI64 AVP contains such identifiers.
8.57. User-Equipment-Info-IMEI AVP
The User-Equipment-Info-IMEI (AVP Code TBD6) is of type OctetString.
The User-Equipment-Info-IMEI AVP contains the International Mobile
Equipment Identifier in the international IMEI format according to
3GPP TS 23.003 [TGPPIMEI].
8.58. Subscription-Id-Extension AVP
The Subscription-Id-Extension AVP (AVP Code TBD7) is used to identify
the end user's subscription and is of type Grouped. The
Subscription-Id-Extension AVP contains an included AVP holding the
subscription identifier itself. The type of this included AVP
indicates the type of the subscription identifier. The existing
identifier types are listed in the Subscription-Id-Type AVP. For
each existing identifier type there is a separate sub-AVP
corresponding to it. If a new identifier type is required a
corresponding new sub-AVP SHOULD be defined.
If full backward compatibility with [RFC4006] is required, then the
Subscription-Id AVP MUST be used to carry out identifier types listed
in the Subscription-Id-Type AVP. While Subscription-Id-Extension AVP
MUST be used only for newly defined identifier types. If full
backward compatibility with [RFC4006] is not required, then the
Subscription-Id-Extension AVP MAY be used to carry out the existing
identifier types. In this case, Subscription-Id-Extension AVP MAY be
sent together with Subscription-Id AVP.
Exactly one sub-AVP MUST be included inside the Subscription-Id-
Extension AVP.
It is defined as follows (per the grouped-avp-def of [RFC6733]):
Subscription-Id-Extension ::= < AVP Header: TBD7 >
[ Subscription-Id-E164 ]
[ Subscription-Id-IMSI ]
[ Subscription-Id-SIP-URI ]
[ Subscription-Id-NAI ]
[ Subscription-Id-Private ]
*[ AVP ]
8.59. Subscription-Id-E164 AVP
The Subscription-Id-E164 (AVP Code TBD8) is of type UTF8String. The
Subscription-Id-E164 AVP contains the international E.164 format
(e.g., MSISDN), according to the ITU-T E.164 numbering plan defined
in [E164] and [CE164].
8.60. Subscription-Id-IMSI AVP
The Subscription-Id-IMSI (AVP Code TBD9) is of type UTF8String. The
Subscription-Id-IMSI AVP contains the international IMSI format,
according to the ITU-T E.212 numbering plan as defined in [E212] and
[CE212].
8.61. Subscription-Id-SIP-URI AVP
The Subscription-Id-SIP-URI (AVP Code TBD10) is of type UTF8String.
The Subscription-Id-SIP-URI AVP contains the identifier in the form
of a SIP URI, as defined in [RFC3261].
8.62. Subscription-Id-NAI AVP
The Subscription-Id-NAI (AVP Code TBD11) is of type UTF8String. The
Subscription-Id-NAI AVP contains the identifier in the form of a
Network Access Identifier, as defined in [RFC2486].
8.63. Subscription-Id-Private AVP
The Subscription-Id-Private (AVP Code TBD12) is of type UTF8String.
The Subscription-Id-Private AVP contains a credit-control server
private identifier.
8.64. Redirect-Server-Extension AVP
The Redirect-Server-Extension AVP (AVP Code TBD13) is of type Grouped
and contains the address information of the redirect server (e.g.,
HTTP redirect server, SIP Server) with which the end user is to be
connected when the account cannot cover the service cost. It MUST be
present inside the QoS-Final-Unit-Indication AVP when the Final-Unit-
Action AVP is set to REDIRECT. If the type of the redirect server is
one of the types listed in the Redirect-Address-Type AVP, then the
credit-control server SHOULD send the information in the Redirect-
Server AVP, in addition to or instead of the Redirect-Server-
Extension AVP. This is in order to preserve backward compatibility
with credit-control clients that support only [RFC4006]. Exactly
only one AVP MUST be included inside the Redirect-Server-Extension
AVP.
It is defined as follows (per the grouped-avp-def of [RFC6733]):
Redirect-Server-Extension ::= < AVP Header: TBD13 >
[ Redirect-Address-IPv4Address ]
[ Redirect-Address-IPv6Address ]
[ Redirect-Address-URL ]
[ Redirect-Address-SIP-URI ]
*[ AVP ]
8.65. Redirect-Address-IPv4Address AVP
The Redirect-Address-IPv4Address AVP (AVP Code TBD14) is of type
UTF8String and defines the address of the redirect server with which
the end user is to be connected when the account cannot cover the
service cost. When the address type of the redirect server is in the
form of "dotted-decimal" IPv4 address, as defined in [RFC0791].
8.66. Redirect-Address-IPv6Address AVP
The Redirect-Address-IPv6Address AVP (AVP Code TBD15) is of type
UTF8String and defines the address of the redirect server with which
the end user is to be connected when the account cannot cover the
service cost. When the address type is in the form of IPv6 address,
as defined in [RFC4291]. The address is a text representation of the
address according to [RFC5952].
8.67. Redirect-Address-URL AVP
The Redirect-Address-URL AVP (AVP Code TBD16) is of type UTF8String
and defines the address of the redirect server with which the end
user is to be connected when the account cannot cover the service
cost. When the address type is in the form of Uniform Resource
Locator, as defined in [RFC1738].
8.68. Redirect-Address-SIP-URI AVP
The Redirect-Address-SIP-URI AVP (AVP Code TBD17) is of type
UTF8String and defines the address of the redirect server with which
the end user is to be connected when the account cannot cover the
service cost. When the address type is in the form of SIP Uniform
Resource Identifier, as defined in [RFC3261].
8.69. QoS-Final-Unit-Indication AVP
The QoS-Final-Unit-Indication AVP (AVP Code TBD18) is of type Grouped
and indicates that the Granted-Service-Unit AVP in the Credit-
Control-Answer, or in the AA answer, contains the final units for the
service. After these units have expired, the Diameter credit-control
client is responsible for executing the action indicated in the
Final-Unit-Action AVP (see Section 5.6).
If more than one unit type is received in the Credit-Control-Answer,
the unit type that first expired SHOULD cause the credit-control
client to execute the specified action.
In the first interrogation, the QoS-Final-Unit-Indication AVP with
Final-Unit-Action REDIRECT or RESTRICT_ACCESS can also be present
with no Granted-Service-Unit AVP in the Credit-Control-Answer or in
the AA answer. This indicates to the Diameter credit-control client
to execute the specified action immediately. If the home service
provider policy is to terminate the service, naturally, the server
SHOULD return the appropriate transient failure (see Section 9.1) in
order to implement the policy-defined action.
The Final-Unit-Action AVP defines the behavior of the service element
when the user's account cannot cover the cost of the service and MUST
always be present if the QoS-Final-Unit-Indication AVP is included in
a command.
If the Final-Unit-Action AVP is set to TERMINATE, no other AVPs MUST
be present.
If the Final-Unit-Action AVP is set to REDIRECT at least the
Redirect-Server-Extension AVP MUST be present. The Filter-Rule AVP
or the Filter-Id AVP MAY be present in the Credit-Control-Answer
message if the user is also allowed to access other services that are
not accessible through the address given in the Redirect-Server-
Extension AVP or if the access to these services needs to be limited
in some way (e.g., QoS).
If the QoS-Final-Unit-Action AVP is set to RESTRICT_ACCESS, either
the Filter-Rule AVP or the Filter-Id AVP SHOULD be present.
The Filter-Rule AVP is defined in [RFC5777]. The Filter-Rule AVP can
be used to define a specific condition and action combination. If
used only with traffic conditions, it should define which traffic
should allowed when no more service units are granted. However, if
QoS or treatment information exists in the AVP, these actions should
be executed, e.g., limiting the allowed traffic with certain QoS.
When multiple Filter-Rule AVPs exist, precedence should be determined
as defined in [RFC5777].
The Filter-Id AVP is defined in [RFC7155]. The Filter-Id AVP can be
used to reference an IP filter list installed in the access device by
means other than the Diameter credit-control application, e.g.,
locally configured or configured by another entity.
If the type of Final-Unit-Action AVP is set TERMINATE, or set to
RESTRICT_ACCESS and the action required is allow only traffic that
could be classified using an IPFilterRule, or set to REDIRECT of a
type which is one of the types in the Redirect-Address-Type AVP, then
the credit-control server SHOULD send the information in the Final-
Unit-Indication AVP, in addition to or instead of the QoS-Final-Unit-
Indication AVP. This is in order to preserve backward compatibility
with credit-control clients that support only [RFC4006].
The QoS-Final-Unit-Indication AVP is defined as follows (per the
grouped-avp-def of [RFC6733]):
QoS-Final-Unit-Indication ::= < AVP Header: TBD18 >
{ Final-Unit-Action }
*[ Filter-Rule ]
*[ Filter-Id ]
[ Redirect-Server-Extension ]
*[ AVP ]
9. Result Code AVP Values 9. Result Code AVP Values
This section defines new Result-Code AVP [RFC6733] values that must This section defines new Result-Code AVP [RFC6733] values that must
be supported by all Diameter implementations that conform to this be supported by all Diameter implementations that conform to this
specification. specification.
The Credit-Control-Answer message includes the Result-Code AVP, which The Credit-Control-Answer message includes the Result-Code AVP, which
may indicate that an error was present in the Credit-Control-Request may indicate that an error was present in the Credit-Control-Request
message. A rejected Credit-Control-Request message SHOULD cause the message. A rejected Credit-Control-Request message SHOULD cause the
user's session to be terminated. user's session to be terminated.
skipping to change at page 81, line 45 skipping to change at page 91, line 5
Cost-Information | 0 | 0-1 | Cost-Information | 0 | 0-1 |
Credit-Control-Failure- | 0 | 0-1 | Credit-Control-Failure- | 0 | 0-1 |
Handling | | | Handling | | |
Destination-Host | 0-1 | 0 | Destination-Host | 0-1 | 0 |
Destination-Realm | 1 | 0 | Destination-Realm | 1 | 0 |
Direct-Debiting-Failure- | 0 | 0-1 | Direct-Debiting-Failure- | 0 | 0-1 |
Handling | | | Handling | | |
Event-Timestamp | 0-1 | 0-1 | Event-Timestamp | 0-1 | 0-1 |
Failed-AVP | 0 | 0+ | Failed-AVP | 0 | 0+ |
Final-Unit-Indication | 0 | 0-1 | Final-Unit-Indication | 0 | 0-1 |
QoS-Final-Unit-Indication | 0 | 0-1 |
Granted-Service-Unit | 0 | 0-1 | Granted-Service-Unit | 0 | 0-1 |
Multiple-Services-Credit- | 0+ | 0+ | Multiple-Services-Credit- | 0+ | 0+ |
Control | | | Control | | |
Multiple-Services-Indicator | 0-1 | 0 | Multiple-Services-Indicator | 0-1 | 0 |
Origin-Host | 1 | 1 | Origin-Host | 1 | 1 |
Origin-Realm | 1 | 1 | Origin-Realm | 1 | 1 |
Origin-State-Id | 0-1 | 0-1 | Origin-State-Id | 0-1 | 0-1 |
Proxy-Info | 0+ | 0+ | Proxy-Info | 0+ | 0+ |
Redirect-Host | 0 | 0+ | Redirect-Host | 0 | 0+ |
Redirect-Host-Usage | 0 | 0-1 | Redirect-Host-Usage | 0 | 0-1 |
Redirect-Max-Cache-Time | 0 | 0-1 | Redirect-Max-Cache-Time | 0 | 0-1 |
Requested-Action | 0-1 | 0 | Requested-Action | 0-1 | 0 |
Requested-Service-Unit | 0-1 | 0 | Requested-Service-Unit | 0-1 | 0 |
Route-Record | 0+ | 0+ | Route-Record | 0+ | 0+ |
Result-Code | 0 | 1 | Result-Code | 0 | 1 |
Service-Context-Id | 1 | 0 | Service-Context-Id | 1 | 0 |
Service-Identifier | 0-1 | 0 | Service-Identifier | 0-1 | 0 |
Service-Parameter-Info | 0+ | 0 | Service-Parameter-Info | 0+ | 0 |
Session-Id | 1 | 1 | Session-Id | 1 | 1 |
Subscription-Id | 0+ | 0 | Subscription-Id | 0+ | 0 |
Subscription-Id-Extension | 0+ | 0 |
Termination-Cause | 0-1 | 0 | Termination-Cause | 0-1 | 0 |
User-Equipment-Info | 0-1 | 0 | User-Equipment-Info | 0-1 | 0 |
User-Equipment-Info-Extension | 0-1 | 0 |
Used-Service-Unit | 0+ | 0 | Used-Service-Unit | 0+ | 0 |
User-Name | 0-1 | 0-1 | User-Name | 0-1 | 0-1 |
Validity-Time | 0 | 0-1 | Validity-Time | 0 | 0-1 |
------------------------------|-----+-----+ ------------------------------|-----+-----+
10.2. Re-Auth-Request/Answer AVP Table 10.2. Re-Auth-Request/Answer AVP Table
This section defines AVPs that are specific to the Diameter credit- This section defines AVPs that are specific to the Diameter credit-
control application and that MAY be included in the Diameter Re- control application and that MAY be included in the Diameter Re-Auth-
Auth-Request/Answer (RAR/RAA) message [RFC6733]. Request/Answer (RAR/RAA) message [RFC6733].
Re-Auth-Request/Answer command MAY include the following additional Re-Auth-Request/Answer command MAY include the following additional
AVPs: AVPs:
+---------------+ +---------------+
| Command Code | | Command Code |
|-------+-------+ |-------+-------+
Attribute Name | RAR | RAA | Attribute Name | RAR | RAA |
------------------------------+-------+-------+ ------------------------------+-------+-------+
CC-Sub-Session-Id | 0-1 | 0-1 | CC-Sub-Session-Id | 0-1 | 0-1 |
skipping to change at page 83, line 15 skipping to change at page 92, line 35
specification. specification.
The Diameter credit-control architecture may have a Translation Agent The Diameter credit-control architecture may have a Translation Agent
capable of translation between RADIUS prepaid and Diameter credit- capable of translation between RADIUS prepaid and Diameter credit-
control protocols. An AAA server (usually the home AAA server) may control protocols. An AAA server (usually the home AAA server) may
act as a Translation Agent and as a Diameter credit-control client act as a Translation Agent and as a Diameter credit-control client
for service elements that use credit-control mechanisms other than for service elements that use credit-control mechanisms other than
Diameter credit control for instance, RADIUS prepaid. In this case, Diameter credit control for instance, RADIUS prepaid. In this case,
the home AAA server contacts the Diameter credit-control server as the home AAA server contacts the Diameter credit-control server as
part of the authorization process. The interworking architecture is part of the authorization process. The interworking architecture is
illustrated Figure 8, and interworking flow in Figure 9. In a illustrated Figure 9, and interworking flow in Figure 10. In a
roaming situation the service element (e.g., the NAS) may be located roaming situation the service element (e.g., the NAS) may be located
in the visited network, and a visited AAA server is usually in the visited network, and a visited AAA server is usually
contacted. The visited AAA server connects then to the home AAA contacted. The visited AAA server connects then to the home AAA
server. server.
RADIUS Prepaid RADIUS Prepaid
+--------+ +---------+ protocol +------------+ +--------+ +--------+ +---------+ protocol +------------+ +--------+
| End |<----->| Service |<---------->| Home AAA | |Business| | End |<----->| Service |<---------->| Home AAA | |Business|
| User | | Element | | Server | |Support | | User | | Element | | Server | |Support |
+--------+ +-->| | |+----------+|->|System | +--------+ +-->| | |+----------+|->|System |
| +---------+ ||CC Client || | | | +---------+ ||CC Client || | |
| |+----------+| | | | |+----------+| | |
+--------+ | +------^-----+ +----^---+ +--------+ | +------^-----+ +----^---+
| End |<--+ Credit-Control | | | End |<--+ Credit-Control | |
| User | Protocol | | | User | Protocol | |
+--------+ +-------V--------+ | +--------+ +-------V--------+ |
|Credit-Control |----+ |Credit-Control |----+
| Server | | Server |
+----------------+ +----------------+
Figure 8: Credit-control architecture with service element containing Figure 9: Credit-control architecture with service element containing
translation agent, translating RADIUS prepaid to Diameter credit- translation agent, translating RADIUS prepaid to Diameter credit-
control protocol control protocol
When the AAA server acting as a Translation Agent receives an initial When the AAA server acting as a Translation Agent receives an initial
RADIUS Access-Request message from service element (e.g., NAS RADIUS Access-Request message from service element (e.g., NAS
access), it performs regular authentication and authorization. If access), it performs regular authentication and authorization. If
the RADIUS Access-Request message indicates that the service element the RADIUS Access-Request message indicates that the service element
is capable of credit-control, and if the home AAA server finds that is capable of credit-control, and if the home AAA server finds that
the subscriber is a prepaid subscriber, then a Diameter credit- the subscriber is a prepaid subscriber, then a Diameter credit-
control request SHOULD be sent toward the credit-control server to control request SHOULD be sent toward the credit-control server to
skipping to change at page 85, line 40 skipping to change at page 94, line 47
|----------------------->| | |----------------------->| |
| | CCR (terminate, | | | CCR (terminate, |
| | Used-Units) | | | Used-Units) |
| |----------------------->| | |----------------------->|
| | CCA | | | CCA |
| |<-----------------------| | |<-----------------------|
| Access-Accept | | | Access-Accept | |
|<-----------------------| | |<-----------------------| |
| | | | | |
Figure 9: Message flow example with RADIUS prepaid - Diameter credit- Figure 10: Message flow example with RADIUS prepaid - Diameter
control interworking credit-control interworking
12. IANA Considerations 12. IANA Considerations
This section contains the namespaces that have either been created in This section contains the namespaces that have either been created in
this specification, or the values assigned to existing namespaces this specification, or the values assigned to existing namespaces
managed by IANA. managed by IANA.
In the subsections below, when we speak about review by a Designated In the subsections below, when we speak about review by a Designated
Expert, please note that the designated expert will be assigned by Expert, please note that the designated expert will be assigned by
the IESG. Initially, such Expert discussions take place on the AAA the IESG. Initially, such Expert discussions take place on the AAA
skipping to change at page 89, line 20 skipping to change at page 98, line 25
Credit-Control-Failure-Handling and Direct-Debiting-Failure-Handling Credit-Control-Failure-Handling and Direct-Debiting-Failure-Handling
Client implementations may offer the possibility of locally Client implementations may offer the possibility of locally
configuring these AVPs. In such a case their value and behavior is configuring these AVPs. In such a case their value and behavior is
defined in Section 5.7 for the Credit-Control-Failure-Handling and in defined in Section 5.7 for the Credit-Control-Failure-Handling and in
Section 6.5 for the Direct-Debiting-Failure-Handling. Section 6.5 for the Direct-Debiting-Failure-Handling.
14. Security Considerations 14. Security Considerations
The Diameter base protocol [RFC6733] requires that each Diameter Security considerations regarding the Diameter protocol itself are
implementation use underlying security; i.e., TLS/TCP, DTLS/SCTP or discussed in [RFC6733]. Use of this application of Diameter MUST
IPsec. These mechanisms are believed to provide sufficient take into consideration the security issues and requirements of the
protection under the normal Internet threat model; that is, assuming base protocol.
that the authorized nodes engaging in the protocol have not been
compromised, but that the attacker has complete control over the This application includes a mechanism for application layer replay
communication channels between them. This includes eavesdropping, protection by means of the Session-Id from [RFC6733] and CC-Request-
message modification, insertion, and man-in-the-middle and replay Number, which is specified in this document. The Diameter credit-
attacks. Note also that this application includes a mechanism for control application is often used within one domain, and there may be
application layer replay protection by means of the Session-Id from a single hop between the peers. In these environments, the use of
[RFC6733] and CC- Request-Number, which is specified in this TLS/TCP, DTLS/SCTP or IPsec is sufficient. The details of TLS/TCP,
document. The Diameter credit-control application is often used DTLS/SCTP or IPsec related security considerations are discussed in
within one domain, and there may be a single hop between the peers. the [RFC6733].
In these environments, the use of TLS/TCP, DTLS/SCTP or IPsec is
sufficient. The details of TLS/TCP, DTLS/SCTP or IPsec related
security considerations are discussed in the [RFC6733].
Because this application handles monetary transactions (directly or Because this application handles monetary transactions (directly or
indirectly), it increases the interest for various security attacks. indirectly), it increases the interest for various security attacks.
Therefore, all parties communicating with each other MUST be Therefore, all parties communicating with each other MUST be
authenticated, including, for instance, TLS client-side authenticated, including, for instance, TLS client-side
authentication. In addition, authorization of the client SHOULD be authentication. In addition, authorization of the client SHOULD be
emphasized; i.e., that the client is allowed to perform credit- emphasized; i.e., that the client is allowed to perform credit-
control for a certain user. The specific means of authorization are control for a certain user. The specific means of authorization are
outside of the scope of this specification but can be, for instance, outside of the scope of this specification but can be, for instance,
manual configuration. manual configuration.
skipping to change at page 92, line 22 skipping to change at page 101, line 22
Accounting (AAA) Transport Profile", RFC 3539, Accounting (AAA) Transport Profile", RFC 3539,
DOI 10.17487/RFC3539, June 2003, DOI 10.17487/RFC3539, June 2003,
<http://www.rfc-editor.org/info/rfc3539>. <http://www.rfc-editor.org/info/rfc3539>.
[RFC3580] Congdon, P., Aboba, B., Smith, A., Zorn, G., and J. Roese, [RFC3580] Congdon, P., Aboba, B., Smith, A., Zorn, G., and J. Roese,
"IEEE 802.1X Remote Authentication Dial In User Service "IEEE 802.1X Remote Authentication Dial In User Service
(RADIUS) Usage Guidelines", RFC 3580, (RADIUS) Usage Guidelines", RFC 3580,
DOI 10.17487/RFC3580, September 2003, DOI 10.17487/RFC3580, September 2003,
<http://www.rfc-editor.org/info/rfc3580>. <http://www.rfc-editor.org/info/rfc3580>.
[RFC4006] Hakala, H., Mattila, L., Koskinen, J-P., Stura, M., and J.
Loughney, "Diameter Credit-Control Application", RFC 4006,
DOI 10.17487/RFC4006, August 2005,
<http://www.rfc-editor.org/info/rfc4006>.
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, DOI 10.17487/RFC4291, February Architecture", RFC 4291, DOI 10.17487/RFC4291, February
2006, <http://www.rfc-editor.org/info/rfc4291>. 2006, <http://www.rfc-editor.org/info/rfc4291>.
[RFC5777] Korhonen, J., Tschofenig, H., Arumaithurai, M., Jones, M.,
Ed., and A. Lior, "Traffic Classification and Quality of
Service (QoS) Attributes for Diameter", RFC 5777,
DOI 10.17487/RFC5777, February 2010,
<http://www.rfc-editor.org/info/rfc5777>.
[RFC5952] Kawamura, S. and M. Kawashima, "A Recommendation for IPv6
Address Text Representation", RFC 5952,
DOI 10.17487/RFC5952, August 2010,
<http://www.rfc-editor.org/info/rfc5952>.
[RFC6733] Fajardo, V., Ed., Arkko, J., Loughney, J., and G. Zorn, [RFC6733] Fajardo, V., Ed., Arkko, J., Loughney, J., and G. Zorn,
Ed., "Diameter Base Protocol", RFC 6733, Ed., "Diameter Base Protocol", RFC 6733,
DOI 10.17487/RFC6733, October 2012, DOI 10.17487/RFC6733, October 2012,
<http://www.rfc-editor.org/info/rfc6733>. <http://www.rfc-editor.org/info/rfc6733>.
[RFC7155] Zorn, G., Ed., "Diameter Network Access Server [RFC7155] Zorn, G., Ed., "Diameter Network Access Server
Application", RFC 7155, DOI 10.17487/RFC7155, April 2014, Application", RFC 7155, DOI 10.17487/RFC7155, April 2014,
<http://www.rfc-editor.org/info/rfc7155>. <http://www.rfc-editor.org/info/rfc7155>.
[TGPPCHARG] [TGPPCHARG]
skipping to change at page 94, line 45 skipping to change at page 103, line 45
| | | (term.,Used-Units) | | | (term.,Used-Units)
| | |------------------->| | | |------------------->|
| | | (16)CCA | | | | (16)CCA |
| | (17)CCA |<-------------------| | | (17)CCA |<-------------------|
| |<-------------------| | | |<-------------------| |
| |(18)STR | | | |(18)STR | |
| |------------------->| | | |------------------->| |
| | (19)STA | | | | (19)STA | |
| |<-------------------| | | |<-------------------| |
Figure 10: Flow I Figure 11: Flow I
A credit-control flow for Network Access Services prepaid is shown in A credit-control flow for Network Access Services prepaid is shown in
Figure A.1. The Diameter [RFC7155] is implemented in the Network Figure 11. The Diameter [RFC7155] is implemented in the Network
Access Server (NAS). The focus of this flow is in the credit Access Server (NAS). The focus of this flow is in the credit
authorization. authorization.
The user logs on to the network (1). The Diameter NAS sends a The user logs on to the network (1). The Diameter NAS sends a
Diameter AA-Request (AAR) to the home Diameter AAA server. The Diameter AA-Request (AAR) to the home Diameter AAA server. The
credit-control client populates the AAR with the Credit-Control AVP credit-control client populates the AAR with the Credit-Control AVP
set to CREDIT_AUTHORIZATION, and service-specific AVPs are included, set to CREDIT_AUTHORIZATION, and service-specific AVPs are included,
as usual [RFC7155]. The home Diameter AAA server performs service- as usual [RFC7155]. The home Diameter AAA server performs service-
specific Authentication and Authorization, as usual. The home specific Authentication and Authorization, as usual. The home
Diameter AAA server determines that the user is a prepaid user and Diameter AAA server determines that the user is a prepaid user and
skipping to change at page 95, line 32 skipping to change at page 104, line 32
AAA server sends the reserved quota to the NAS in the Diameter AA- AAA server sends the reserved quota to the NAS in the Diameter AA-
Answer (AAA). Upon successful AAA, the NAS starts the credit-control Answer (AAA). Upon successful AAA, the NAS starts the credit-control
session and starts monitoring the granted units (5). The NAS grants session and starts monitoring the granted units (5). The NAS grants
access to the end user (6). At the expiry of the allocated quota, access to the end user (6). At the expiry of the allocated quota,
the NAS sends a Diameter Credit-Control-Request with CC-Request-Type the NAS sends a Diameter Credit-Control-Request with CC-Request-Type
set to UPDATE_REQUEST to the Home Diameter AAA server (7). This set to UPDATE_REQUEST to the Home Diameter AAA server (7). This
message contains the units used thus far. The home Diameter AAA message contains the units used thus far. The home Diameter AAA
server forwards the CCR to the Diameter credit-control server (8). server forwards the CCR to the Diameter credit-control server (8).
The Diameter credit-control server debits the used units from the end The Diameter credit-control server debits the used units from the end
user's account and allocates a new quota that is returned to the home user's account and allocates a new quota that is returned to the home
Diameter AAA server in the Diameter Credit- Control-Answer (9). The Diameter AAA server in the Diameter Credit-Control-Answer (9). The
message is forwarded to the NAS (10). During the ongoing credit- message is forwarded to the NAS (10). During the ongoing credit-
control session, the authorization lifetime expires, and the control session, the authorization lifetime expires, and the
authorization/authentication client in the NAS performs service authorization/authentication client in the NAS performs service
specific re-authorization to the home Diameter AAA server, as usual. specific re-authorization to the home Diameter AAA server, as usual.
The credit-control client populates the AAR with the Credit-Control The credit-control client populates the AAR with the Credit-Control
AVP set to RE_AUTHORIZATION, indicating that the credit-control AVP set to RE_AUTHORIZATION, indicating that the credit-control
server shall not be contacted, as the credit authorization is server shall not be contacted, as the credit authorization is
controlled by the burning rate of the granted units (11). The home controlled by the burning rate of the granted units (11). The home
Diameter AAA server performs service-specific re- authorization as Diameter AAA server performs service-specific re-authorization as
usual and returns the AA-Answer to the NAS (12). The end user logs usual and returns the AA-Answer to the NAS (12). The end user logs
off from the network (13). To debit the used units from the end off from the network (13). To debit the used units from the end
user's account and to stop the credit-control session, the NAS sends user's account and to stop the credit-control session, the NAS sends
a Diameter Credit-Control-Request with CC-Request-Type set to a Diameter Credit-Control-Request with CC-Request-Type set to
TERMINATION_REQUEST to the home Diameter AAA server (14). The home TERMINATION_REQUEST to the home Diameter AAA server (14). The home
Diameter AAA server forwards the CCR to the credit-control server Diameter AAA server forwards the CCR to the credit-control server
(15). The Diameter credit-control server acknowledges the session (15). The Diameter credit-control server acknowledges the session
termination by sending a Diameter Credit-Control-Answer to the home termination by sending a Diameter Credit-Control-Answer to the home
Diameter AAA server (16). The home Diameter AAA server forwards the Diameter AAA server (16). The home Diameter AAA server forwards the
answer to the NAS (17). STR/STA takes place between the NAS and home answer to the NAS (17). STR/STA takes place between the NAS and home
skipping to change at page 96, line 42 skipping to change at page 105, line 42
|(7) BYE | | | |(7) BYE | | |
|------------->| | | |------------->| | |
| |(8) BYE | | | |(8) BYE | |
| |---------------------------->| | | |---------------------------->| |
| |(9) CCR (termination, Used-Units) | | |(9) CCR (termination, Used-Units) |
| |------------------------------------------->| | |------------------------------------------->|
| |(10) CCA () | | |(10) CCA () |
| |<-------------------------------------------| | |<-------------------------------------------|
| | | | | | | |
Figure 11: Flow II Figure 12: Flow II
This is an example of Diameter credit-control for SIP sessions. This is an example of Diameter credit-control for SIP sessions.
Although the flow focuses on illustrating the usage of credit-control Although the flow focuses on illustrating the usage of credit-control
messages, the SIP signaling is inaccurate, and the diagram is not by messages, the SIP signaling is inaccurate, and the diagram is not by
any means an attempt to define a service provider's SIP network. any means an attempt to define a service provider's SIP network.
However, for the sake of this example, some assumptions are made However, for the sake of this example, some assumptions are made
below. below.
Typically, prepaid services based, for example, on time usage for SIP Typically, prepaid services based, for example, on time usage for SIP
session require an entity in the service provider network to session require an entity in the service provider network to
skipping to change at page 98, line 28 skipping to change at page 107, line 28
| |(5) Notify MMS | | | |(5) Notify MMS | |
| |--------------->| | | |--------------->| |
: : : : : : : :
| |(6) Retrieve MMS| | | |(6) Retrieve MMS| |
| |<---------------| | | |<---------------| |
| |(7) Retrieve MMS| | | |(7) Retrieve MMS| |
| | Ack | | | | Ack | |
| |--------------->| | | |--------------->| |
| | | | | | | |
Figure 12: Flow III Figure 13: Flow III
A credit-control flow for Multimedia Messaging Services is shown in A credit-control flow for Multimedia Messaging Services is shown in
Figure A.3. The sender is charged as soon as the messaging server Figure 13. The sender is charged as soon as the messaging server
successfully stores the message. successfully stores the message.
The end user A sends a Multimedia Message (MMS) to the MMS server The end user A sends a Multimedia Message (MMS) to the MMS server
(1). The MMS server stores the message and sends a Diameter Credit- (1). The MMS server stores the message and sends a Diameter Credit-
Control-Request (EVENT_REQUEST with Requested-Action DIRECT_DEBITING) Control-Request (EVENT_REQUEST with Requested-Action DIRECT_DEBITING)
to the Diameter credit-control server (2). The Credit-Control- to the Diameter credit-control server (2). The Credit-Control-
Request contains information about the MMS message (e.g., size, Request contains information about the MMS message (e.g., size,
recipient address, image coding type). The Diameter credit-control recipient address, image coding type). The Diameter credit-control
server checks the end user's account balance, rates the service, and server checks the end user's account balance, rates the service, and
debits the service from the end user's account. The granted quota is debits the service from the end user's account. The granted quota is
skipping to change at page 99, line 30 skipping to change at page 108, line 30
| |(7) CCR (event, DIRECT_DEBITING,| | |(7) CCR (event, DIRECT_DEBITING,|
| | MMS specific AVP) | | | MMS specific AVP) |
| |-------------------------------->| | |-------------------------------->|
| |(8) CCA (Granted-Units) | | |(8) CCA (Granted-Units) |
| |<--------------------------------| | |<--------------------------------|
| |(9) Retrieve MMS| | | |(9) Retrieve MMS| |
| | Ack | | | | Ack | |
| |--------------->| | | |--------------->| |
| | | | | | | |
Figure 13: Flow IV Figure 14: Flow IV
This is an example of Diameter credit-control for direct debiting This is an example of Diameter credit-control for direct debiting
using the Multimedia Messaging Service environment. Although the using the Multimedia Messaging Service environment. Although the
flow focuses on illustrating the usage of credit-control messages, flow focuses on illustrating the usage of credit-control messages,
the MMS signaling is inaccurate, and the diagram is not by any means the MMS signaling is inaccurate, and the diagram is not by any means
an attempt to define any service provider's MMS configuration or an attempt to define any service provider's MMS configuration or
billing model. billing model.
A credit-control flow for Multimedia Messaging Service is shown in A credit-control flow for Multimedia Messaging Service is shown in
Figure A.4. The recipient is charged at the message delivery. Figure 14. The recipient is charged at the message delivery.
A content server sends a Multimedia Message (MMS) to the MMS server A content server sends a Multimedia Message (MMS) to the MMS server
(1) that stores the message. The message recipient will be charged (1) that stores the message. The message recipient will be charged
for the MMS message in this case. As there can be a substantially for the MMS message in this case. As there can be a substantially
long time between the receipt of the message at the MMS server and long time between the receipt of the message at the MMS server and
the actual retrieval of the message, the MMS server does not the actual retrieval of the message, the MMS server does not
establish any credit-control session to the Diameter credit-control establish any credit-control session to the Diameter credit-control
server but performs first only a balance check (without any credit server but performs first only a balance check (without any credit
reservation) by sending a Diameter Credit-Control-Request reservation) by sending a Diameter Credit-Control-Request
(EVENT_REQUEST with Requested-Action CHECK_BALANCE) to verify that (EVENT_REQUEST with Requested-Action CHECK_BALANCE) to verify that
skipping to change at page 100, line 46 skipping to change at page 109, line 46
|<---------------| | | |<---------------| | |
|(5)HTTP GET | | | |(5)HTTP GET | | |
|--------------->| | | |--------------->| | |
|(6)HTTP POST | | | |(6)HTTP POST | | |
|--------------->|(7)INVITE(SDP) | | |--------------->|(7)INVITE(SDP) | |
| |--------------->| | | |--------------->| |
| | (8)200 OK | | | | (8)200 OK | |
| (9)200 OK |<---------------| | | (9)200 OK |<---------------| |
|<---------------| | | |<---------------| | |
Figure 14: Flow V Figure 15: Flow V
This is an example of Diameter credit-control for SIP sessions. This is an example of Diameter credit-control for SIP sessions.
Although the flow focuses on illustrating the usage of credit-control Although the flow focuses on illustrating the usage of credit-control
messages, the SIP signaling is inaccurate, and the diagram is not by messages, the SIP signaling is inaccurate, and the diagram is not by
any means an attempt to define a service provider's SIP network. any means an attempt to define a service provider's SIP network.
Figure A.5 is an example of Advice of Charge (AoC) service for SIP Figure 15 is an example of Advice of Charge (AoC) service for SIP
call. User A can be either a postpaid or prepaid subscriber using call. User A can be either a postpaid or prepaid subscriber using
the AoC service. It is assumed that the SIP controller also has HTTP the AoC service. It is assumed that the SIP controller also has HTTP
capabilities and delivers an interactive AoC web page with, for capabilities and delivers an interactive AoC web page with, for
instance, the cost information, the details of the call derived from instance, the cost information, the details of the call derived from
the SDP, and a button to accept/not accept the charges. (There may the SDP, and a button to accept/not accept the charges. (There may
be many other ways to deliver AoC information; however, this flow be many other ways to deliver AoC information; however, this flow
focuses on the use of the credit-control messages.) The user has focuses on the use of the credit-control messages.) The user has
been authenticated and authorized prior to initiating the call and been authenticated and authorized prior to initiating the call and
subscribed to AoC service. subscribed to AoC service.
skipping to change at page 101, line 51 skipping to change at page 110, line 51
: : : : : :
: : : : : :
| |(2)CCR(event,REFUND,Requested- | |(2)CCR(event,REFUND,Requested-
| |Service-Unit,Service-Parameter-Info) | |Service-Unit,Service-Parameter-Info)
| |----------------------->| | |----------------------->|
| | (3)CCA(Cost-Information) | | (3)CCA(Cost-Information)
| |<-----------------------| | |<-----------------------|
| (4)Notification | | | (4)Notification | |
|<-----------------------| | |<-----------------------| |
Figure 15: Flow VI Figure 16: Flow VI
Figure A.6 illustrates a credit-control flow for the REFUND case. It Figure 16 illustrates a credit-control flow for the REFUND case. It
is assumed that there is a trusted relationship and secure connection is assumed that there is a trusted relationship and secure connection
between the Gaming server and the Diameter credit-control server. between the Gaming server and the Diameter credit-control server.
The end user may be a prepaid subscriber or a postpaid subscriber. The end user may be a prepaid subscriber or a postpaid subscriber.
While the end user is playing the game (1), she enters a new level While the end user is playing the game (1), she enters a new level
that entitles her to a bonus. The Gaming server sends a Diameter that entitles her to a bonus. The Gaming server sends a Diameter
Credit-Control-Request (EVENT_REQUEST with Requested-Action: Credit-Control-Request (EVENT_REQUEST with Requested-Action:
REFUND_ACCOUNT) to the Diameter credit-control server (2). The REFUND_ACCOUNT) to the Diameter credit-control server (2). The
Credit-Control-Request Request contains the Requested-Service-Unit Credit-Control-Request Request contains the Requested-Service-Unit
AVP with the CC-Service-Specific-Units containing the number of AVP with the CC-Service-Specific-Units containing the number of
skipping to change at page 103, line 32 skipping to change at page 112, line 32
|..............................| | | |..............................| | |
| | (8)BYE | | | | | (8)BYE | | |
| |<-------------| | | | |<-------------| | |
| | (9)CCR(Update) | | | | (9)CCR(Update) | |
| |------------------------------------------>| | |------------------------------------------>|
| | (10)CCA(Granted-Unit) | | | (10)CCA(Granted-Unit) |
| |<------------------------------------------| | |<------------------------------------------|
| (12)INVITE | (11)INVITE | | | (12)INVITE | (11)INVITE | |
|<--------------|--------------------------->| | |<--------------|--------------------------->| |
Figure 16: Flow VII Figure 17: Flow VII
Figure A.7 is an example of the graceful service termination for a Figure 17 is an example of the graceful service termination for a SIP
SIP call. It is assumed that the call is set up so that the call. It is assumed that the call is set up so that the controller
controller is in the call as a B2BUA (Back to Back User Agent) is in the call as a B2BUA (Back to Back User Agent) performing third-
performing third-party call control (3PCC). Note that the SIP party call control (3PCC). Note that the SIP signaling is
signaling is inaccurate, as the focus of this flow is in the graceful inaccurate, as the focus of this flow is in the graceful service
service termination and credit-control authorization. The best termination and credit-control authorization. The best practice for
practice for 3PCC is defined in [RFC3725]. 3PCC is defined in [RFC3725].
The call is ongoing between users A and B; user A has a prepaid The call is ongoing between users A and B; user A has a prepaid
subscription. At the expiry of the allocated quota, the SIP subscription. At the expiry of the allocated quota, the SIP
controller sends a Diameter Credit-Control-Request (UPDATE_REQUEST) controller sends a Diameter Credit-Control-Request (UPDATE_REQUEST)
to the Diameter credit-control server (1). This message contains the to the Diameter credit-control server (1). This message contains the
units used thus far. The Diameter credit-control server debits the units used thus far. The Diameter credit-control server debits the
used units from the end user's account and allocates the final quota used units from the end user's account and allocates the final quota
returned to the SIP controller in the Diameter Credit-Control-Answer returned to the SIP controller in the Diameter Credit-Control-Answer
(2). This message contains the Final-Unit-Indication AVP with the (2). This message contains the Final-Unit-Indication AVP with the
Final-Unit-Action set to REDIRECT, the Redirect-Address-Type set to Final-Unit-Action set to REDIRECT, the Redirect-Address-Type set to
skipping to change at page 104, line 22 skipping to change at page 113, line 22
Control-Answer message, which contains the Validity-Time to supervise Control-Answer message, which contains the Validity-Time to supervise
the graceful service termination, is returned to the SIP controller the graceful service termination, is returned to the SIP controller
(4). The SIP controller establishes a SIP session between the (4). The SIP controller establishes a SIP session between the
prepaid user and the Top-up server (5, 6). The Top-up server plays prepaid user and the Top-up server (5, 6). The Top-up server plays
an announcement and prompts the user to enter a credit card number an announcement and prompts the user to enter a credit card number
and the amount of money to be used to replenish the account (7). The and the amount of money to be used to replenish the account (7). The
Top-up server validates the credit card number and replenishes the Top-up server validates the credit card number and replenishes the
user's account (using some means outside the scope of this user's account (using some means outside the scope of this
specification) and releases the SIP session (8). The SIP controller specification) and releases the SIP session (8). The SIP controller
can now assume that communication between the prepaid user and the can now assume that communication between the prepaid user and the
Top-up server took place. It sends a spontaneous Credit- Control- Top-up server took place. It sends a spontaneous Credit-Control-
Request (UPDATE_REQUEST) to the Diameter credit-control server to Request (UPDATE_REQUEST) to the Diameter credit-control server to
check whether the account has been replenished (9). The Diameter check whether the account has been replenished (9). The Diameter
credit-control server reserves credit from the end user's account and credit-control server reserves credit from the end user's account and
returns the reserved quota to the SIP controller in the Credit- returns the reserved quota to the SIP controller in the Credit-
Control-Answer (10). At this point, the SIP controller re- connects Control-Answer (10). At this point, the SIP controller re-connects
the caller and the called party (11,12). the caller and the called party (11,12).
B.8. Flow VIII B.8. Flow VIII
NAS Top-up CC NAS Top-up CC
End-User (CC Client) AAA Server Server Server End-User (CC Client) AAA Server Server Server
|(1)User Logon |(2)AA Request (CC AVPs) | | |(1)User Logon |(2)AA Request (CC AVPs) | |
|------------------>|------------------->| | | |------------------>|------------------->| | |
| | |(3)CCR(initial, CC AVPs) | | |(3)CCR(initial, CC AVPs)
| | |------------------->| | | |------------------->|
| | |(4)CCA(Final-Unit, | | | |(4)CCA(Final-Unit, |
skipping to change at page 105, line 33 skipping to change at page 114, line 33
| |<-------------------|<-------------------| | |<-------------------|<-------------------|
| | (11) RAA | | | | (11) RAA | |
| |------------------->|------------------->| | |------------------->|------------------->|
| |(12)CCR(update) | | | |(12)CCR(update) | |
| |------------------->|(13)CCR(Update) | | |------------------->|(13)CCR(Update) |
| | |------------------->| | | |------------------->|
| | |(14)CCA(Granted-Units) | | |(14)CCA(Granted-Units)
| |(15)CCA(Granted-Units)<------------------| | |(15)CCA(Granted-Units)<------------------|
| |<-------------------| | | |<-------------------| |
Figure 17: Flow VIII Figure 18: Flow VIII
Figure A.8 is an example of the graceful service termination Figure 18 is an example of the graceful service termination initiated
initiated when the first interrogation takes place because the user's when the first interrogation takes place because the user's account
account is empty. In this example, the credit-control server is empty. In this example, the credit-control server supports the
supports the server-initiated credit re-authorization. The Diameter server-initiated credit re-authorization. The Diameter [RFC7155] is
[RFC7155] is implemented in the Network Access Server (NAS). implemented in the Network Access Server (NAS).
The user logs on to the network (1). The Diameter NAS sends a The user logs on to the network (1). The Diameter NAS sends a
Diameter AA-Request to the home Diameter AAA server. The credit- Diameter AA-Request to the home Diameter AAA server. The credit-
control client populates the AAR with the Credit-Control AVP set to control client populates the AAR with the Credit-Control AVP set to
CREDIT_AUTHORIZATION, and service specific AVPs are included, as CREDIT_AUTHORIZATION, and service specific AVPs are included, as
usual [RFC7155]. The home Diameter AAA server performs service usual [RFC7155]. The home Diameter AAA server performs service
specific Authentication and Authorization, as usual. The home specific Authentication and Authorization, as usual. The home
Diameter AAA server determines that the user has a prepaid Diameter AAA server determines that the user has a prepaid
subscription and notices from the Credit-Control AVP that the NAS has subscription and notices from the Credit-Control AVP that the NAS has
credit-control capabilities. It sends a Diameter Credit-Control- credit-control capabilities. It sends a Diameter Credit-Control-
skipping to change at page 106, line 31 skipping to change at page 115, line 31
the user's device opens the transport connection redirected by the the user's device opens the transport connection redirected by the
NAS to the Top-up server (7,8). The user is displayed an appropriate NAS to the Top-up server (7,8). The user is displayed an appropriate
web page on which to enter the credit card number, and the amount of web page on which to enter the credit card number, and the amount of
money to be used to replenish the account, and with a notification money to be used to replenish the account, and with a notification
message that she is granted unlimited access if the replenishment message that she is granted unlimited access if the replenishment
operation will be successfully executed within the next, for example, operation will be successfully executed within the next, for example,
10 minutes. The Top-up server validates the credit card number and 10 minutes. The Top-up server validates the credit card number and
replenishes the user's account (using some means outside the scope of replenishes the user's account (using some means outside the scope of
this specification)(9). After successful account top-up, the credit- this specification)(9). After successful account top-up, the credit-
control server sends a Re-Auth-Request message to the NAS (10). The control server sends a Re-Auth-Request message to the NAS (10). The
NAS acknowledges the request by returning the Re-Auth- Answer message NAS acknowledges the request by returning the Re-Auth-Answer message
(11) and initiates the credit re-authorization by sending a Credit- (11) and initiates the credit re-authorization by sending a Credit-
Control-request (UPDATE_REQUEST) to the Diameter credit-control Control-request (UPDATE_REQUEST) to the Diameter credit-control
server (12,13). server (12,13).
The Diameter credit-control server reserves credit from the end The Diameter credit-control server reserves credit from the end
user's account and returns the reserved quota to the NAS via the home user's account and returns the reserved quota to the NAS via the home
Diameter AAA server in the Credit-Control-Answer (14,15). The NAS Diameter AAA server in the Credit-Control-Answer (14,15). The NAS
removes the restriction placed by the graceful service termination removes the restriction placed by the graceful service termination
and starts monitoring the granted units. and starts monitoring the granted units.
skipping to change at page 109, line 18 skipping to change at page 118, line 18
| | Multiple-Services-CC ( | | | Multiple-Services-CC ( |
| | Used-Units(Time), | | | Used-Units(Time), |
| | Service-Id 1, Rating-Group 1), | | | Service-Id 1, Rating-Group 1), |
| | Multiple-Services-CC ( | | | Multiple-Services-CC ( |
| | Used-Units(Time), | | | Used-Units(Time), |
| | Service-Id 2, Rating-Group 1)) | | | Service-Id 2, Rating-Group 1)) |
| |---------------------------------------->| | |---------------------------------------->|
| |(17)CCA(term) | | |(17)CCA(term) |
| |<----------------------------------------| | |<----------------------------------------|
Figure 18: Flow example independent credit-control of multiple Figure 19: Flow example independent credit-control of multiple
services in a credit-control (sub-)Session services in a credit-control (sub-)Session
The user logs on to the network (1). The service element sends a The user logs on to the network (1). The service element sends a
Diameter Credit-Control-Request with CC-Request-Type set to Diameter Credit-Control-Request with CC-Request-Type set to
INITIAL_REQUEST to the Diameter credit-control server to perform INITIAL_REQUEST to the Diameter credit-control server to perform
credit authorization for the bearer service (e.g., Internet access credit authorization for the bearer service (e.g., Internet access
service) and to establish a credit-control session (2). In this service) and to establish a credit-control session (2). In this
message, the credit-control client indicates support for independent message, the credit-control client indicates support for independent
credit-control of multiple services within the session by including credit-control of multiple services within the session by including
the Multiple-Service-Indicator AVP. The Diameter credit-control the Multiple-Service-Indicator AVP. The Diameter credit-control
skipping to change at page 109, line 45 skipping to change at page 118, line 45
with a quota of 5MB associated to the Service-Id (access), to a with a quota of 5MB associated to the Service-Id (access), to a
multiplier value of 10, and to the Pool-Id 1 (3). multiplier value of 10, and to the Pool-Id 1 (3).
The user uses Service 1 (4). The service element sends a Diameter The user uses Service 1 (4). The service element sends a Diameter
Credit-Control-Request with CC-Request-Type set to UPDATE_REQUEST to Credit-Control-Request with CC-Request-Type set to UPDATE_REQUEST to
the credit-control server to perform credit authorization for service the credit-control server to perform credit authorization for service
1 (5). This message includes the Multiple-Services-Credit-Control 1 (5). This message includes the Multiple-Services-Credit-Control
AVP to request service units for Service 1 that belong to Rating- AVP to request service units for Service 1 that belong to Rating-
Group 1. The Diameter credit-control server determines that Service Group 1. The Diameter credit-control server determines that Service
1 draws credit resources from the same account as the access service 1 draws credit resources from the same account as the access service
(i.e., pool 1). It rates the request according to Service- Id/ (i.e., pool 1). It rates the request according to Service-Id/Rating-
Rating-Group and updates the existing reservation by requesting more Group and updates the existing reservation by requesting more credit.
credit. Suppose that the server reserves $5 more (now the Suppose that the server reserves $5 more (now the reservation is $10)
reservation is $10) and determines that the cost is $0.1/minute. The and determines that the cost is $0.1/minute. The server authorizes
server authorizes the whole Rating-Group. It then returns to the the whole Rating-Group. It then returns to the service element a
service element a Credit-Control-Answer message that includes the Credit-Control-Answer message that includes the Multiple-Services-
Multiple-Services-Credit-Control AVP with a quota of 50min. Credit-Control AVP with a quota of 50min. associated to the Rating-
Group 1, to a multiplier value of 1, and to the Pool-Id 1 (6). The
associated to the Rating-Group 1, to a multiplier value of 1, and to client adjusts the total amount of resources for pool 1 according the
the Pool-Id 1 (6). The client adjusts the total amount of resources received quota, which gives S for Pool 1 = 100.
for pool 1 according the received quota, which gives S for Pool 1 =
100.
The user uses Service 2, which belongs to the authorized Rating- The user uses Service 2, which belongs to the authorized Rating-
Group, 1 (7). Resources are then consumed from the pool 1. Group, 1 (7). Resources are then consumed from the pool 1.
The user now requests Services 3 and 4 as well, which are not The user now requests Services 3 and 4 as well, which are not
authorized (8). The service element sends a Diameter Credit- authorized (8). The service element sends a Diameter Credit-Control-
Control-Request with CC-Request-Type set to UPDATE_REQUEST to the Request with CC-Request-Type set to UPDATE_REQUEST to the credit-
credit-control server in order to perform credit authorization for control server in order to perform credit authorization for Services
Services 3 and 4 (9). This message includes two instances of the 3 and 4 (9). This message includes two instances of the Multiple-
Multiple-Services-Credit-Control AVP to request service units for Services-Credit-Control AVP to request service units for Service 3
Service 3 that belong to Rating-Group 2 and for Service 4 that belong that belong to Rating-Group 2 and for Service 4 that belong to
to Rating-Group 3. The Diameter credit-control server determines Rating-Group 3. The Diameter credit-control server determines that
that Services 3 and 4 draw credit resources from another account Services 3 and 4 draw credit resources from another account (i.e.,
(i.e., pool 2). It checks the end user's account balance and, pool 2). It checks the end user's account balance and, according to
according to Service-Ids/Rating-Groups information, rates the Service-Ids/Rating-Groups information, rates the request. Then it
request. Then it reserves credit from pool 2. reserves credit from pool 2.
For example, the server reserves $5 and determines that Service 3 For example, the server reserves $5 and determines that Service 3
costs $0.2/MB and Service 4 costs $0.5/MB. The server authorizes costs $0.2/MB and Service 4 costs $0.5/MB. The server authorizes
only Services 3 and 4. It returns to the service element a Credit- only Services 3 and 4. It returns to the service element a Credit-
Control-Answer message that includes two instances of the Multiple- Control-Answer message that includes two instances of the Multiple-
Services-Credit-Control AVP (10). One instance grants a quota of Services-Credit-Control AVP (10). One instance grants a quota of
12.5MB associated to the Service-Id 3 to a multiplier value of 2 and 12.5MB associated to the Service-Id 3 to a multiplier value of 2 and
to the Pool-Id 2. The other instance grants a quota of 5 MB to the Pool-Id 2. The other instance grants a quota of 5 MB
associated to the Service-Id 4 to a multiplier value of 5 and to the associated to the Service-Id 4 to a multiplier value of 5 and to the
Pool-Id 2. Pool-Id 2.
skipping to change at page 111, line 47 skipping to change at page 120, line 44
Control-Answer to the service element (17). Control-Answer to the service element (17).
Appendix C. Changes relative to RFC4006 Appendix C. Changes relative to RFC4006
The following changes were made relative to RFC4006: The following changes were made relative to RFC4006:
Update references to obsolete RFC 3588 to refer to RFC 6733. Update references to obsolete RFC 3588 to refer to RFC 6733.
Update references to obsolete RFC 4005 to refer to RFC 7155. Update references to obsolete RFC 4005 to refer to RFC 7155.
Update references to current 3GPP documents.
Update AVP per Errata ID 3329.
Update reference to "IPsec or TLS" to be "TLS/TCP, DTLS/SCTP or Update reference to "IPsec or TLS" to be "TLS/TCP, DTLS/SCTP or
IPsec" IPsec".
Update AVP per Errata ID 3329 Clarify Filter-Rule AVP in Restrict Access Action.
Remove Encr column from AVP flag rules.
Clarify that RESTRICT_ACCESS action applies after consumption of
final granted units (Section 5.6.3).
Clarify that values in Used-Service-Unit AVP may exceed Granted-
Service-Unit AVP (Section 8.19).
Clarify that IPv6 representation in Redirect-Address-Type AVP
conforms to RFC5952 (Section 8.38).
Describe immediate graceful service termination procedure (in
Section 5.6).
Add extensible User-Equipment-Info-Extension AVP and included
types (from Section 8.52 to Section 8.57).
Add extensible Subscription-Id-Extension AVP and included types
(from Section 8.58 to Section 8.63).
Add extensible Redirect-Server-Extension AVP and included types
(from Section 8.64 to Section 8.68).
Add extensible QoS-Final-Unit-Indication AVP (in Section 8.69).
Updated Security Section to include language consistent with
structures of latest base protocol specification.
Authors' Addresses Authors' Addresses
Lyle Bertz (editor) Lyle Bertz (editor)
Sprint Sprint
6220 Sprint Parkway 6220 Sprint Parkway
Overland Park, KS 66251 Overland Park, KS 66251
United States United States
Email: lyleb551144@gmail.com Email: lyleb551144@gmail.com
skipping to change at page 112, line 23 skipping to change at page 122, line 4
Email: lyleb551144@gmail.com Email: lyleb551144@gmail.com
David Dolson (editor) David Dolson (editor)
Sandvine Sandvine
408 Albert Street 408 Albert Street
Waterloo, ON N2L 3V3 Waterloo, ON N2L 3V3
Canada Canada
Phone: +1 519 880 2400 Phone: +1 519 880 2400
Email: ddolson@sandvine.com Email: ddolson@sandvine.com
Yuval Lifshitz (editor) Yuval Lifshitz (editor)
Sandvine Sandvine
408 Albert Street 408 Albert Street
Waterloo, ON N2L 3V3 Waterloo, ON N2L 3V3
Canada Canada
Phone: +1 519 880 2400 Phone: +1 519 880 2400
Email: ylifshitz@sandvine.com Email: ylifshitz@sandvine.com
Harri Hakala
Oy L M Ericsson Ab
Joukahaisenkatu 1
Turku 20520
Finland
Phone: +358 2 265 3722
Email: Harri.Hakala@ericsson.com
Leena Mattila
Oy L M Ericsson Ab
Joukahaisenkatu 1
Turku 20520
Finland
Phone: +358 2 265 3731
Email: Leena.Mattila@ericsson.com
Juha-Pekka Koskinen
Nokia Networks
Hatanpaanvaltatie 30
Tampere 33100
Finland
Phone: +358 7180 74027
Email: juha-pekka.koskinen@nokia.com
Marco Stura
Nokia Networks
Hiomotie 32
Tampere 00380
Helsinki
Phone: +358 7180 64308
Email: marco.stura@nokia.com
John Loughney
Nokia Research Center
Itamerenkatu 11-13
Tampere 00180
Helsinki
Phone: +358 50 483 642
Email: John.Loughney@nokia.com
 End of changes. 129 change blocks. 
418 lines changed or deleted 856 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/