2024 Q3 Release Notes

Release Notes for Q4 2024 are now available. Check out the most recent changes and updates. For a complete overview of all Totogi releases, visit the Release Notes Archive.

 

New Functionality

• September 27, 2024 Totogi’s Automated Plan Migration feature, which simplifies and accelerates the process of moving subscribers between plan versions, is now generally available through Plan Design, our self-service plan configuration tool. This feature allows the entire subscriber base to be migrated to the same version simultaneously at the specified activation time,  streamlining billing and reconciliation.

For help activating automated migrations for your existing subscriber base, contact Totogi Customer Support. Additional details can be found in our API Documentation .

• September 19, 2024  Totogi introduced an enhancement to its location determination process for roaming users. This update integrates the Access-Transfer-Information AVP under IMS-Information into existing Credit Requests, enabling more precise and reliable location identification for users while roaming.

  In addition to the Access-Transfer-Information AVP, Totogi’s location determination for roaming in 4G can leverage a variety of AVPs, including:

  • MCC and MNC Codes: Utilizing the 3GPP-SGSN-MCC-MNC AVP and any other valid AVP carrying the MCC+MNC combination.

  • SMS Information: Extracting the Originator-SCCP-Address in E.164 format.

  • Legacy Systems with VCS Information: Leveraging the VLR-Number and MSC-Address in E.164 format.

This enhancement is seamlessly enabled upon deployment, with no need for additional configuration or operational changes.

• September 04, 2024 Totogi now supports automatic sub-tenant identification using device information from the charging request. Previously, sub-tenant identification was handled through Field Mapping, which relied on IMSI ranges. However, this approach may not be ideal in cases where IMSI ranges are unavailable or the IMSI itself is not provided in the request. The new feature ensures reliable sub-tenant identification for each request, simplifying the setup process for managing multiple MVNOs or product lines.

  Important Notes:

  • Existing configurations using Field Mapping remain supported and will override this feature when applicable.
  • For devices created under the sub-tenant before this feature's introduction, an updateDevice API call is required to ensure proper sub-tenant identification.

• Please contact Totogi Support to learn more about enabling this feature for your tenant and sub-tenants.

• August 13, 2024 Totogi now supports Automated Daylight Savings Time (DST) adjustments in postpaid accounts through the use of Location Format in timezone. When location format is used, billing will be processed at midnight local time, automatically adjusting for seasonal time changes. 

For example, accounts with a timezone set to “Pacific/Auckland” will be billed at +13 UTC during DST and +12 UTC otherwise. Please refer to API documentation for supported formats.

• July 26, 2024  Totogi has a new plan migration approach that expedites and simplifies the process of moving subscribers from one plan version to another. Now, it is possible to migrate the entire subscriber base to the same version simultaneously, making billing and reconciliation more straightforward. It is currently available for a select customer base through APIs. Upcoming releases will offer the same capabilities in Plan Design, our self-service plan configuration tool.

  Please contact your sales or service account manager to learn more about this feature and how to enable it.

 

Changed Functionality

• July 22, 2024  The recurring first usage fee charge of Roam Like Home plan has been enhanced by triggering notifications for charges and failures, and dedicated Event Data Records (EDRs) facilitating efficient billing and reconciliation processes. Learn more... 
• July 22, 2024  The prioritization logic for plans and balances has been enhanced to use expiry or next renewal date if plans or balances have the same priority. 

 

Fixes and Improvements

• September 24, 2024 Resolved an issue where recurring plan charges, particularly for hourly plans, were not processed consistently, leading to outdated balance and renewal dates. This fix ensures reliable processing of plan renewals moving forward.
• September 18, 2024 Resolved an issue where sending an international SMS from the home country, when charged as a one-time event, triggered incorrect recurring fees on the Roam-like Home plan.
• September 17 , 2024 Fixed an issue that triggers incorrect allowance notifications during abandoned session processing.
• September 11, 2024 Resolved an issue where the getEventDataRecordsByAccount API would fail if an updateAccountBalanceTypeCounter EDR were present within the queried period.
• September 10, 2024 Addressed an issue in the job fetching logic that caused some renewing plans to be skipped intermittently, leading to occasional delays in plan renewals. The job fetching mechanism has been improved to ensure consistent processing of recurring jobs.
• September 05, 2024  Fixed issue that resulted in incorrect charging behavior when terminating an individual session in multi-session scenarios. This improvement ensures that terminating one session doesn't affect the rating and charging of other active sessions for the same service.
• August 28, 2024  Fixed issue where the "from" date of the balance created by recurring postpaid plans was not updated after the recent renewal at Billing Day of Month (BillingDoM). This fix ensures that for postpaid plans aligned with BillingDoM, the balance start date is now correctly set at renewals.
• August 28, 2024  Resolved an issue where CCR updates failed with END_USER_SERVICE_DENIED when the Account was migrated from a non-mid-session to a mid-session plan during active sessions. This fix ensures seamless plan migrations without interrupting ongoing sessions.
• August 22, 2024  Fixed updatePlanSubscription API to correctly enable plan alias functionality when transitioning from planId- or planVersionId-based subscriptions to planAliasId.
• August 12, 2024  Now, when a plan service is configured for explicit denial (e.g., for specific B-number patterns), the engine returns "END_USER_SERVICE_DENIED" instead of "QUOTA_LIMIT_REACHED". This change provides a more accurate response to the network, enabling better service management and improved user experience.

• August 07, 2024  GetAccount, SubscribeToPlan, and UpdatePlanSubscription APIs now include an optional renewal field for each subscription. This field provides the next renewal date for recurring plans in UTC. If the plan is non-recurring or has no applicable renewal date, this field will return null.

  Additionally, the renewal field is included in the NewPlanActivated and AutoRenewSuccess notifications, enabling subscribers to be informed about their next plan renewal dates.

• July 11, 2024. purchaseFee and recurringFee BILL Event Data Records (EDRs) are extended to include the planVersionID attribute. This new attribute links the specific plan version purchased or renewed by the Account,  enabling more accurate tracking and analysis of plan versions associated with billing events.