1 / 5

Diameter Credit Control Application

Diameter Credit Control Application. draft-hakala-diameter-credit-control-06.txt IETF 56 john.loughney@nokia.com Harri Hakala / Jukka-Pekka Koskinen / John Loughney / Leena Mattila / Marco Stura. Motivation.

joycei
Download Presentation

Diameter Credit Control Application

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Diameter Credit Control Application draft-hakala-diameter-credit-control-06.txt IETF 56 john.loughney@nokia.com Harri Hakala / Jukka-Pekka Koskinen / John Loughney / Leena Mattila / Marco Stura

  2. Motivation • On-line / real-time / pre-paid accounting or has become very popular in mobile networks. • SS7 based protocols and IN–based solutions approach are used • A new IP-based accounting protocol is urgently needed to support credit based accounting for Internet services • Diameter base accounting is not sufficient for real-time pre-paid services. • By adding an optional credit-control application, theDiameter base accounting the needed functionality the can be provided by ‘existing’ AAA infrastructure.

  3. Overview • A general purpose real-time accounting protocol. • Enhance diameter accounting messages (ACR/ACA): • with new mandatory controlling AVPs • application defined state machines (session &event based state machines for client and server) • application specific fault handling • No new commands. • Supports On-line credit control with credit reservation (using session records) and operations (using event records), such as: • Price Enquiry • Balance Check • Direct Debiting • Refund

  4. Updates • Now a working group document • Draft now officially included in 3GPP specifications - TS 32.225. • Major changes: • A server or client is not required to implement all functionality in the CCA. • Optionality has been clarified in the draft • Unknown/unsupported value responded with error Subscription-Id-Type • Unknown AVPs can be ignored, i.e. 'M'-bit removed from AVP Flag table • New Result-Code value 'DIAMETER_RATING_FAILED'.

  5. To Do • Editorial clean-up; fix some keywords; clarification on some points. • Fix all ’ID-nits’ • Clarify with 3GPP if draft meets their needs. • Nearly ready for WG last call?

More Related