If you liked it, or content was helpful to you please add "+1" to article you used or share it on facebook or so.
Make it easier to find for others who could need those information, allow them find these articles on the spot. But.. it's your call.
Recommendations until now


Jan 13, 2012

Offline Charging System (OFCS) - introduction to Gx interface

Last time I tried to familiarize You with Online Charging System (OCS), with was a introduction to Gy based on a diameter. But before I will go to the diameter, and all those CCRs and CCAs just I wanted to talk about Offline Charging System.

What is Offline Charging System (OFCS)?
According to TS 32.240 and TS 32.299 3GPP documentation:
Offline charging is a process where charging information for network resource usage is collected concurrently with that resource usage. The charging information is then passed through a chain of logical charging functions, which are described below. At the end of this process, CDR files are generated by the network, which are then transferred to the network operator's Billing Domain for the purpose of subscriber billing and/or inter-operator accounting (or additional functions, e.g. statistics, at the operator’s discretion). The BD typically comprises post-processing systems such as the operator's billing system or billing mediation device.

Generally offline charging is a mechanism where charging information does not affect, in real-time, the service rendered.
As it's always good to start with a high level design picture, let's start.
Fig. 1. Offline Charging high level architecture
Where:
CTF: Charging Trigger Function
CDF: Charging Data Function
CGF: Charging Gateway Function
BD: Billing Domain. This may also be a billing system/ billing mediation device.


Offline Charging functions
Below CTF, CDF and CGF functions are described.

Charging Trigger Function
The CTF (Charging Trigger Function) generates charging events based on the observation of network resource usage as described above. In every network and service element that provides charging information, the CTF is the focal point for collecting the information pertaining to chargeable events within the network element, assembling this information into matching charging events, and sending these charging events towards the  CDF (Charging Data Function). The CTF is therefore a mandatory, integrated component in all network elements that provide offline charging functionality. It is made up of two functional blocks:

Accounting Metrics Collection
The process that monitors signaling functions for calls, service events or sessions established by the network users, or the handling of user traffic for those calls, service events or sessions, or service delivery to the user via these calls, service events or sessions. It is required to provide metrics that identify the user and the user's consumption of network resource and/or services in real-time. The exact behaviour and funcionality of this process are:
  • trigger conditions for collection of charging information
  • information elements to collect
  • which service events, signaling or usertraffic to monitor
  • relationship to services/bearers/sessions
depends on functions/service that the network element provides. The Account Metrics Collection can therefore be considered as the network element dependent part of the CTF.

Accounting Data Forwarding
This process receives the collected accounting metrics and determines the occurrence of chargeable events from a set of one or more of there metrics. It then assembles charging events that match the detected chargeable events, and forwards the charging events towards the Charging Data Function via the Rf interface. (Being completely honest, Gx interface is being used between PCRF and PGW to transfer policy and charging rules, and it is described in more details in TS 29.212) The charging events provide information pertinent to the chargeable event, i.e. characterising the network resource usage together with an identification of the involved user(s). There is no assumption of any synchronisation between the reception of individual accounting metrics, however, it must be possible for the Accounting Data Forwarding to complete its overall functionality per charging event in real-time.

While the exact information received by the Account Data Forwarding from the Account Metrics Collection, and the relevant chargeable events, are specific to each type of network element, the overall functionality of receiving, assembling and forwarding the charging information can be considered generic. Hence the Accounting Data Forwarding is considered the NE independent part of the CTF.

Charging Data Function
The CDF (Charging Data Function) receives charging events from the CTF (described above) via the Rf reference point. It then uses the information contained in the charging events to construct CDRs. This procedure is characterised by the following conditions:
  • CDRs may be constructed fro single charging events, i.e. a 1:1 relation between event and CDR.
  • CDRs may be constructed from a set of serval charging events, i.e. a n:1 relation between event and CDR
  • Each charging event is used for exactly one CDR, i.e. a 1:n relation between event and CDR (with n>1) is not possible
  • Multiple charging events that are used to create a single CDR may not necessarily be of the same type
  • There is no requirement or assumption of any synchronisation between the reception of the charging event(s) and the creation of the resulting CDR. However, the CDF shall be capable of receiving and processing charging events and generating the resulting CDR in near real-time
  • The relationship between CDF and CTF may be 1:1 (integrated CDF) or 1:n (separated CDF). This includes the possibility of network elements of different types feeding charging events in the CDF
The result of the CDF tasks are Charging Data Records (CDRs) with a well-defined content and format. The content and format of these CDRs are specified per domain/subsystem/service in the related middle tier charging specification, e.g. 3GPP TS 32.250 for the CS domain and 3GPP TS 32.251 for PS domain.

Charging Gateway Function
The CDRs produced by CDF are transferred immediately to the Charging Gateway Function (CGF) via the Ga interface point. The CGDBs interface for transfer of CDR files to Billing Domain. The entity relationship between the CDF and the CGF is m:1, i.e. one or more CDFs may feed CDRs into a single CGF. The CGF comprises the following main functions:
  • CDR reception from the CDF via Ga interface in near real-time.
  • CDR pre-processing
    • Validation, Consolidation and (Re)Formatting of CDRs
    • CDR error handling
    • Persistent CDR storage
  • CDR routing and filtering, i.e. storing CDRs on separate files based on filtering criteria such as CDR type, CDR parameters, originating CDF, etc.
  • CDR File Management, e.g. file creation, file opening / closure triggers, file deletion
  • CDR file transfer to the Billing Domain

Charging scenarios
There are two basic scenarios that are being used:
  • Event based Charging
  • Session based Charging
Event Based Charging
In the following scenario, CTF asks the CDF to store event related charging data.
Fig. 2. Event Based Charging
1. Request for resource usage: UE-A requests the desired resource from the network element.
2. Content/Service Delivery: the network element delivers the content/service.
3. Charging Data Generation: the CTF generates charging data related to service delivery
4. Record Charging Data Request: the CTF requests the CDF to store event related charging data for CDR generation purposes.
5. Process Request: CDF stores received information. Whether the CDR is generated or not depends on CDR generation configuration.
6. Record Charging Data Response: the CDF informs the CTF that charging data was stored.

Session Based Charging
In the following scenario, CTF asks the CDF to store session related charging data.
Fig. 3. Session Based Charging
1. Request for resource usage: UE-A requests the desired session from the network element.
2. Session ongoing: the network element establish the session
3. Charging Data Generation: the CTF generates charging data related to session.
4. Record Charging Data Request: the CTF requests the CDF to store session related charging data for CDR generation purposes.
5. Process Request: CDF stores received information. Whether the CDR is generated or not depends on CDR generation configuration.
6. Record Charging Data Response: the CDF informs the CTF that charging data was stored
7. Charging Data Generation: the CTF generates charging data related to session due of e.g. intermediate timer expiry
8. Record Charging Data Request: the CTF requests the CDF to store session related charging data for CDR generation purposes.
9. Process Request: CDF stores received information. Whether the CDR is generated or not depends on CDR generation configuration.
10. Record Charging Data Response: the CDF informs the CTF that charging data was stored
11. Session release: the session is released
12. Charging Data Generation: the CTF generates charging data related to session due of session termination.
13. Record Charging Data Request: the CTF requests the CDF to store session related charging data for CDR generation purposes.
14. Process Request: CDF stores received information. Whether the CDR is generated or not depends on CDR generation configuration.
15. Record Charging Data Response: the CDF informs the CTF that charging data was stored.


Event and Session based charging are performed by the use of the Charging Data Transfer (CDF) operation:
  • Charging Data Request, sent from CTF --> CDF. This message is sent after detecting a chargeable event, the CTF sends a Charging Data Request to the CDF.
  • Charging Data Response, sent from CDF --> CTF. CDF replies with a Charging Data Response, which informs the CTF that charging data was recived.

Sources:

10 comments:

  1. Thank you for your informative explanations.

    One question: If the Gy is for online charging and the Gx is for offline charging, is the Gx also used for policy control of online charging or is that the sole responsibility of OCS via Gy?

    ReplyDelete
    Replies
    1. There are two procedures through which the PCRF can communicate PCC rules to PCEF over Gx interface:
      - Pull Procedure, basically this is originated by PCEF Credit Check Request (CCR) and Credit Check Answer (CCA) message from PCRF
      - Push Procedure, PCRF originated Re-Auth Request (RAR) message and Re-Auth Answer (RAA) from PCEF.

      Messages are sent through Diameter based interface.
      More on PCC related 3GPP Technical Specifications are 23.203 and 29.212.

      Hope this helps,
      Bart

      Delete
    2. Anonymous, first of all, Gx is not for offline charging, rather for usage monitorung but can be configured with charging controll manner.
      E.g. Subscriber has reported 10000000 octets from youtube today, it is the daily limit and appropriate prohibiting PCC rule could be sent for the subscriber. It is not Online or Offline charging control. It this case we can`t guarantee exact 1000000, if this amount were reported than a bit more octets were consumed already and no charging function.

      Traditional Diameter charging model is post paid. It inconvenient and risky for subscribers and ISPs. Charging control via Gy uses pre-paid model. A service won`t be granted if it has not been approved (and counted) by OCS. Here charging and control enters into the game.
      e.g. A subscriber has some account balance (in time, moneys, octets and so on). PCEF seeing the subscriber`s requests asks OCS "could I provide this service?". OCS makes reservation of some amounf of "money" and allow the service or not if quota exceeded or account balance too low.

      In reference model Sy is lying between PCRF and OCS, but now PCRF and OCS can be located on one hardware platform or be the same software.
      Gx over Gy looks obsolete, but maybe two diameter connections is not so bad. :) Or it can be one vendor desined, depending on your equipment.

      Delete
    3. Thanks Nikita for updating, really appreciate.

      BR,
      Bart

      Delete
  2. @Nikita :Nice, m fresher in telecom, understood ur clear points

    ReplyDelete
  3. Nice blog has been shared by you. it will be really helpful to many peoples who are all working under the technology.thank you for sharing this blog.
    Billing Software

    ReplyDelete
  4. I am genuinely thankful to the holder of this web page who has shared this wonderful paragraph at at this place 맞고사이트

    ReplyDelete
  5. Crypto-currency as a modern form of the digital asset has received a worldwide acclaim for easy and faster financial transactions and its awareness among people have allowed them to take more interest in the field thus opening up new and advanced ways of making payments. Crypto.com Referral Code with the growing demand of this global phenomenon more,new traders and business owners are now willing to invest in this currency platform despite its fluctuating prices however it is quite difficult to choose the best one when the market is full. In the list of crypto-currencies bit-coins is one of the oldest and more popular Crypto.com Referral Code for the last few years. It is basically used for trading goods and services and has become the part of the so-called computerized block-chain system allowing anyone to use it thus increasing the craze among the public, Crypto.com Referral Code.

    Common people who are willing to purchase BTC can use an online wallet system for buying them safely in exchange of cash or credit cards and in a comfortable way from the thousands of BTC foundations around the world and keep them as assets for the future. Due to its popularity, many corporate investors are now accepting them as cross-border payments and the rise is unstoppable. With the advent of the internet and mobile devices,information gathering has become quite easy as a result the BTC financial transactions are accessible and its price is set in accordance with people’s choice and preferences thus leading to a profitable investment with Crypto.com Referral Code Code. Recent surveys have also proved that instability is good for BTC exchange as if there is instability and political unrest in the country due to which banks suffer then investing in BTC can surely be a better option. Again bit-coin transaction fees are pretty cheaper and a more convenient technology for making contracts thus attracting the crowd. The BTC can also be converted into different fiat currencies and is used for trading of securities, for land titles, document stamping, public rewards and vice versa.

    Another advanced block-chain project is Ethereumor the ETH which has served much more than just a digital form of crypto-currency Crypto.com Referral Code and its popularity in the last few decades have allowed billions of people to hold wallets for them. With the ease of the online world,the ETH have allowed the retailers and business organizations to accept them for trading purposes, therefore, can serve as the future of the financial system.

    ReplyDelete
  6. Our full Lace Front Wigs are all hand made with a lace cap. They are manufactured with thin lace sewn on top of the cap. Individual hairs are then sewn onto the thin lace. Each lace wig has lace all around the unit which will need to be cut prior to securing the wig to your head. You will need to cut along the hairline around your entire head. By doing so, you will be able to wear your hair anyway you like. You can even style ponytails, up-dos, etc. Once the Lace Wigs is successfully applied, it will appear that all the hair is growing directly from your head!

    Lace front wigs are hand-made with lace front cap & machine weft at back. Lace front wigs are manufactured with a thin lace that extends from ear to ear across the hairline. When you receive the wig, the lace will be quite long in the front. Cut and style according to your preference, as you will need to apply adhesive along the front of the wig. Once the wig is applied, you will still have Lace Wigs with a very natural appearance.
    TeamWigz Provide the Best Lace Front Wigs and Lace Wigs in Johannesburg and South Africa.

    ReplyDelete
  7. 우리카지노 에 오신 것을 환영합니다. 국내 최고의 카지노사이트 에 가입하여 바카라사이트 에서 다양한 게임을 즐기시면서 대박의 기회를 놓치지마세요! 우리 카지노는 한국의 바카라 산업을 지배하는 카지노 사이트입니다. 우리 카지노는 한국 바카라 시장 점유율의 50 % 이상을 차지하는 10 년 이상 온라인 바카라 시장을 지배 해 왔기 때문에 우리 카지노를 모르는 사람은 거의 없습니다.

    ARTICLE: 우리카지노는 대한민국의 바카라 업계를 장악하고 있는 카지노사이트 입니다. 우리카지노가 대한 민국에서 장악한 바카라 시장점유율이 50%가 넘고 10년 넘게 온라인 바카라 시장을 장악해왔기 때문에 대한민국에서는 우리카지노를 모르는 사람은 드뭅니다. 이런 바카라 업계의 독보적인 입지 때문에 늘 유명하거나 최고만을 찾는 사람들이 카지노사이트를 찾을때는 늘 우리카지노를 찾습니다.바카라를 처음 시작하시는 초보자분들에게도 우리카지노에서 카지노사이트를 시작하시기 좋은 환경입니다. 우리카지노사이트에서는 신규가입시 3만쿠폰을 지급 해주기 때문입니다. 사람들이 늘 1등만을 찾는 이유는 분명 있습니다. 다른 카지노사이트와는 달리 우리카지노를 이용하실시 에이전트를 끼고 게임을 하신다면 본사 이외에 활동쿠폰 및 오링쿠폰을 별도로 제공해주고 있기 때문입니다. 이러한 이유들 때문에 카지노사이트 업계에서 바카라를 즐기신다면 다들 우리카지노를 선호 하십니다. 카지노사이트에서 바카라를 이기기 물론 어렵습니다. 하지만 우리카지노의 에이전트를 끼고 바카라를 즐기신다면 승산이 있다고 봅니다. 우리카지노 에이전트의 연락처는 홈페이지로 연락하시면 언제든지 부담없이 소통가능 합니다. 카지노사이트를 선정할때는 바카라를 다른곳보다 유리하게 즐길 수 있는 카지노를 선택해야한다고 생각합니다. 그것이 바로 우리카지노 입니다. 이상으로 우리카지노와 바카라 카지노사이트 사이의 상관관계를 알아보았습니다바카라사이트.

    ReplyDelete