ComCode

Telecom software development Company - ComCode Tech
Menu
Telecom software development Company - ComCode Tech
Menu

OCS- Online Charging System over Diameter Gy

Contact Us

Products

Diameter is the main protocol in the 4G/LTE core network. It uses the services of  SCTP.  The 3GPP and  IETF define various applications over the base diameter protocol (RFC 6733).  Another RFC 4006 defines the Diameter Credit Control application with ID 4. It standardizes messages and AVPs for online changing for the Gy interface.

Gy based OCS for online charging?

At ComCode, we provide a diameter platform for OCS.  It connects to the PGW over SCTP.  Towards the subscribers’ billing database, it has a rich set of HTTP APIs. The operator can integerae API in there business system to do the real time changing.

The OCS over Diameter Gy

How OCS does online charging in LTE network?

The following are the steps the OCS platform takes to enable online charging. 

  • Configuration of SCTP and Diameter for the Gy application.
  • Aligning the SCTP link with the PGW.
  • Diameter signaling alignment using CEA/CER.
  • PGW receives a GTP-V2 Create session request from SGW as part of  UE attach.
  • PGW sends an INITIAL Gy Credit Control Request (CCR) to the OCS.
  • OCS platform sends the JSON-based HTTP API to the billing database;
  • If the user has sufficient balance to roam in the requested network, OCS gets the HTTP response with allowed units with a validity time.
  • OCS responds with allocated units and validity time for the session in CCA to the PGW.
  • PGW sends Create Session Response and starts counting data bytes for the user.
  • Once the allowed bytes/validity expires, PGW sends the UPDATE CCR request to get more quota.
  •  If more bytes are allowed, OCS sends more bytes. 
  • If the session is closes PGW sends TERMINATE CCR, and OCS sends CCA.
OCS Call flow

Example APIs supported by the Gy interface.

CCR (INITIAL) —>

 HTTP Request : {“GyAuthenticateReq”:{“session_id”: 1002,”event”:”begin”,”msisdn”:”1191711002″,”requested_octets”:2000,”imsi”:”421000000000032″}} HTTP Response: {“GyAuthenticateResp”:{“granted_octets”:”1000″,”result”:”success”,”session_id”:169}}

CCR (UPDATE) —>

 HTTP Request : {“GyAuthenticateReq”:{“session_id”: 1002,”event”:”continue”, “msisdn”:”1191711002″,”requested_octets”:2000,”used_octets”:200,”imsi”:”421000000000032″}} HTTP Response: {“GyAuthenticateResp”:{“granted_octets”:”1000″,”result”:”success”,”session_id”:169}}

CCR (TERMINATE) —>

 HTTP Request : {“GyAuthenticateReq”:{“session_id”: 1002,”event”:”begin”,”msisdn”:”1191711002″,”used_octets”:200,”imsi”:”421000000000032″}} HTTP Response: {“GyAuthenticateResp”:{“result”:”success”,”session_id”:169}}

Benefits of using ComCode's OCS

  • The platform is a light process the enable hogh TPS over minimal hardware.
  • Each user is to use file-based/GUI-based configurations.
  • Available on our commercial Diamater stack as well as on the open source jDiamater stack.
  • Having an open source option enables telecom service providers to scale at low cost and with no vendor lock.
  • ComCode provides end-to-end installation and integration support.  We are experts in full mobile core.
  • Open for customization.
Scroll to Top