2025 Q2 Release Notes

This topic will be updated throughout the quarter as we improve the product. For a complete overview of all Totogi releases, visit the Release Notes Archive.

Additionally, to stay ahead of future releases, check out Upcoming Changes . This topic provides detailed information on expected changes, helping you to plan and adapt your systems and integrations effectively.

New Functionality

• May 13, 2025 Totogi introduces Customer DB Exports that gives you daily access to a full snapshot of your subscriber and device data, securely delivered to your AWS account. The exported data supports reconciliation, revenue assurance reporting, and business analytics. You can query historical snapshots of your data using Amazon Athena.

Key Features

• Daily Subscriber Database Snapshot:   Each day, a full export of your data is delivered to your AWS account. The dataset includes accounts, devices, provisioned plans, balance values, and more. The snapshot reflects your customer data as of  midnight UTC  .
• Access Your Data in Your AWS Account:   The data is securely delivered to your AWS S3 bucket and can be queried directly using Amazon Athena.
• Cross-Account Synchronization:   You provide a Role ARN and define the target database, table name, and S3 folder. Totogi manages the secure delivery of your daily data to your AWS account.
• Time-Travel Queries:   Query historical snapshots of your data using standard SQL queries in Amazon Athena.

How to Activate Customer DB Exports

To activate this feature, please contact the  Totogi Customer Support   and provide:

• Your AWS Glue database name
• The table name for your exported data
• The S3 folder path for data delivery
• The IAM Role ARN from your AWS account to allow Totogi to deliver the export

Once your configuration is complete, daily exports will begin automatically. No further action is required from your side.

Changed Functionality

• May 14, 2025 Totogi introduces several enhancements to EDRs to improve traceability, interoperability, and reporting.

What has changed:

• Additional metadata: EDR files stored on S3 now include providerID and eventType fields within the file content. This ensures EDRs remain informative even when moved outside their original folder structure in the S3 bucket.
• Correlation ID: When a transaction results in multiple EDRs (e.g., firstUsageFee and Charge EDRs generated when usage is first reported for the plan,) all related EDRs now include the same correlationID to simplify grouping and analysis. Transactions that produce only a single EDR will not include a correlationID.
• Session statistics: Billing EDRs now include a new sessionStatistics section. This includes the session startTime and endTime, as well as usage details by ratingGroup (e.g., time, dataTotalVolume, and serviceSpecificUnits). The endTime also represents the voice call end time; the "start time of the voice call" can be derived by subtracting the voice usage duration from the session endTime. All usage values in this section reflect unrounded amounts.
• 4G to 5G mapping improvements:
  • Event-Timestamp is now accurately mapped from 4G to 5G.
  • User-Equipment-Info of type IMEISV (type 0) is now mapped to the appropriate 5G field and placed in the EDR as one of the following, depending on its location in the 4G Diameter request:
    • pDUSessionChargingInformation/userInformation/servedPEI
    • iMSChargingInformation/userInformation/servedPEI
    • iMSChargingInformation/accessTransferInformation/userEquipmentInfo

Please review and update any downstream systems or reporting pipelines that consume EDRs to ensure compatibility with these changes and avoid any disruption.

• May 14, 2025 Totogi now  allows multiple active subscriptions to the same plan version. Previously, attempts to subscribe to the same plan version more than once resulted in a DuplicatePlanVersion error. With this change, it is possible to implement key use cases—such as allowing users to subscribe to the same add-on multiple times alongside a main plan.

  As part of this change:

• Subscribing to the same plan version multiple times now proceeds successfully, creating a new and distinct planSubscription for each request. The DuplicatePlanVersion error will no longer be raised in this scenario.
• Plan notifications sent to EventBridge (e.g., expiry, renewal, cancellation) includes a planSubscriptionId alongside the planVersionId. Please refer planSubscriptionId to distinguish between multiple subscriptions to the same plan version when needed.
• In cases where there are multiple subscriptions to the same plan version, only one instance of the plan counters is be included in the N28/Sy response. If your system relies on plan counters in these responses, please review and update your logic to avoid inconsistencies. Policy counters are NOT affected by this change and will continue to function as before.

Fixes and Improvements 

• April 02, 2025 We've simplified the format of Account customData field retrieved via Account Management APIs. 

  What has changed:

  Previously, the customData field was double-stringified in the response:

  • Current: "\"{\\\"Language\\\":\\\"English\\\"}\""
  • Future: "{\"Language\": \"English\"}"

With this change, customData is returned as a standard stringified JSON—making it easier to handle without requiring additional parsing logic.

Please ensure your systems are updated accordingly to avoid any impact from this change. No action is needed for create or update requests.