Usage Engine is the latest generation of DigitalRoute's usage data processing software. It is an enterprise-grade data processing platform, combining integration capabilities with class-leading data processing functionality to derive useful information and drive real-time decision-making for a large number of applications such as: billing, operations, revenue assurance, service assurance, entitlement enforcement, service control and business intelligence.

Usage Engine has been designed for a modern cloud-native architecture and associated operational model, focusing on the following areas:

• Cloud-native design, with a clear separation between application and infrastructure, elasticity, and automated Life Cycle Management

• Operational framework, using best of breed industry standards for non-core functions, using a plug-n-play approach

• CI/CD support, with package management for solutions and test framework for automated test suite execution

• Usability, with  clearly defined user interfaces for different user personas

New Functionality

This release contains no new features, or enhancements. For information about features in the 3.0 main release, see New Features and Functionality (3.0).

System Requirements

For information about system requirements, see /wiki/spaces/UEPE3D/pages/1900667.

Important Information and Known Issues

Configurations can be imported from MediationZone 8.x, but since there are different agent sets in the two products, a black box agent will replace any agents not available in your workflows, allowing you to retain your routes and other workflow configurations, see /wiki/spaces/UEPE3D/pages/1901044 for more information.

Other important information is:

• Removed Values from the Helm Chart
• Changed Values in the Helm Chart
• Action Required for Rollback from 3.x to 2.x
• Deprecated Ingress Controller

See Important Information (3.0.2) for full details.

And the following are known issues:

• EC Pod Fails to Start With Custom Service Account
• Encrypted Workflows Cannot be Viewed in MZOnline
• Documentation for System Properties Not Up-to-Date
• GET Method issue when using HTTP/2 Client with OpenAPI profile
• mzcli Commands Do Not Provide Return Codes
• Pico Details Not Entirely Correct
• Removing Dynamic Fields May Cause Problems in the Web Interface
• OpenAPI Validation Error for Type enum
• The property for limiting password changes needs the property "reset.enabled" to be set
• AWS Terraform Template does not Support M1 Mac with darwin_arm64 Architecture
• Importing Old Data Veracity Collection Agent Workflow Configurations Returned Validation Errors
• 5G Profile Not Backward Compatible

See Known Issues (3.0.2) for full  details.

Installation, Upgrade and Downgrade

For instructions on how to install, uppgrade and downgrade, refer to Installation and Setup(3.0), Upgrade/Downgrade/Removal(3.0).