View a markdown version of this page

Totogi Charging-as-a-Service for On-Premises 4G/5G - Totogi Charging-as-a-Service for On-Premises 4G/5G

Totogi Charging-as-a-Service for On-Premises 4G/5G

Publication date: November 16, 2022 (Diagram history)

With this architecture, you can connect your on-premises 4G/5G network to the Totogi Charging-as-a-Service engine on AWS. Totogi is an AWS-native multi-tenant 4G/5G charging engine and plan-design tool that enables telecom operators to connect and monetize their core network. The solution uses AWS Direct Connect, Amazon Elastic Compute Cloud Auto Scaling, and Amazon DynamoDB.

Totogi Charging-as-a-Service diagram

Reference architecture diagram showing how to connect on-premises 4G/5G to Totogi charging on AWS by using AWS Direct Connect, Amazon EC2 Auto Scaling, DynamoDB, and Amazon Cognito.

The following steps describe the charging flow and network connectivity for this architecture:

  1. Connect 4G/5G network devices through the Radio Access Network (RAN) to the telco data center.

  2. Register the subscriber through the core network control plane over the N2 interface for 5G and S1 for 4G subscribers.

  3. Validate 4G/5G charging over N40 (5G REST) and Gy (4G Diameter) towards the multi-tenant Totogi charging engine on AWS.

  4. Connect to AWS through AWS Direct Connect to AWS Transit Gateway in the Amazon VPC that hosts the tenant Totogi charging engine.

  5. Deploy the Diameter adapter on Amazon EC2 Auto Scaling to transform requests and responses between 5G REST and 4G Diameter protocols.

  6. Direct 5G REST requests to decision engines through the Network Load Balancer. Get the tenant ID from the Amazon Cognito access token.

  7. Handle the rating request on the Amazon EC2 Auto Scaling instance decision engine. Look up balances and rating rules in DynamoDB. Partition data by tenant ID and subscriber ID.

  8. Customize the handling of notifications and event detail records (EDRs) by using Amazon EventBridge and Amazon Simple Storage Service buckets.

  9. Deliver quotas from the charging engine to validated subscribers for the user session.

  10. Allow subscribers to access data and voice services over the customer network based on the provisioned plan and available credit in Totogi Charging-as-a-Service.

Further reading

For additional information, see the following resources:

Diagram history

To receive updates about this reference architecture diagram, subscribe to the RSS feed.

ChangeDescriptionDate

Initial publication

Reference architecture diagram first published.

November 16, 2022

RSS subscription requirement

To subscribe to RSS updates, you must have an RSS plugin enabled for the browser you are using.